draft-bellis-dnsext-multi-qtypes-04.txt   draft-bellis-dnsext-multi-qtypes-05.txt 
DNSEXT Working Group R. Bellis DNSEXT Working Group R. Bellis
Internet-Draft ISC Internet-Draft ISC
Intended status: Standards Track July 03, 2017 Intended status: Standards Track January 02, 2018
Expires: January 4, 2018 Expires: July 6, 2018
DNS Multiple QTYPEs DNS Multiple QTYPEs
draft-bellis-dnsext-multi-qtypes-04 draft-bellis-dnsext-multi-qtypes-05
Abstract Abstract
This document specifies a method for a DNS client to request This document specifies a method for a DNS client to request
additional DNS record types to be delivered alongside the primary additional DNS record types to be delivered alongside the primary
record type specified in the question section of a DNS query. record type specified in the question section of a DNS query.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 32 skipping to change at page 1, line 32
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 4, 2018. This Internet-Draft will expire on July 6, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 4, line 29 skipping to change at page 4, line 29
servers which simply echo unknown EDNS options verbatim. If the QTD servers which simply echo unknown EDNS options verbatim. If the QTD
bit in a response is zero the client MUST treat the response as if bit in a response is zero the client MUST treat the response as if
this option is unsupported. this option is unsupported.
The server SHOULD attempt to return any resource records known to it The server SHOULD attempt to return any resource records known to it
that match the additional (QNAME, QTn, QCLASS) tuples. These records that match the additional (QNAME, QTn, QCLASS) tuples. These records
MUST be returned in the Answer Section of the response, but the MUST be returned in the Answer Section of the response, but the
answer for the primary QTYPE from the Question Section MUST be answer for the primary QTYPE from the Question Section MUST be
included first. included first.
For any particular QTn in the query, if the server provides addtional For any particular QTn in the query, if the server provides
answers, or has knowledge that the RR type type does not exist for additional answers, or has knowledge that the RR type type does not
that QNAME (a "negative answer"), it must include that QTn value in exist for that QNAME (a "negative answer"), it must include that QTn
the Multiple QTYPE Option of its response. value in the Multiple QTYPE Option of its response.
A negative answer is therefore indicated by the combination of the A negative answer is therefore indicated by the combination of the
presence of a QTn value in the Multiple QTYPE Option and the absence presence of a QTn value in the Multiple QTYPE Option and the absence
of a matching record in the Answer Section. This is necessary (in of a matching record in the Answer Section. This is necessary (in
the absence of DNSSEC) to differentiate between absence of the record the absence of DNSSEC) to differentiate between absence of the record
from the zone and absence of the record from the response. from the zone and absence of the record from the response.
A server that is authoritative for the specified QNAME on receipt of A server that is authoritative for the specified QNAME on receipt of
a Multiple QTYPE Option MUST attempt to return all specified RR types a Multiple QTYPE Option MUST attempt to return all specified RR types
except where that would result in truncation in which case it may except where that would result in truncation in which case it may
skipping to change at page 6, line 15 skipping to change at page 6, line 15
6. Acknowledgements 6. Acknowledgements
The author wishes to thank the following for their feedback and The author wishes to thank the following for their feedback and
reviews during the initial development of this document: Michael reviews during the initial development of this document: Michael
Graff, Olafur Gudmundsson, Matthijs Mekking, Paul Vixie. Graff, Olafur Gudmundsson, Matthijs Mekking, Paul Vixie.
7. Normative References 7. Normative References
[RFC1035] Mockapetris, P., "Domain names - implementation and [RFC1035] Mockapetris, P., "Domain names - implementation and
specification", STD 13, RFC 1035, DOI 10.17487/RFC1035, specification", STD 13, RFC 1035, DOI 10.17487/RFC1035,
November 1987, <http://www.rfc-editor.org/info/rfc1035>. November 1987, <https://www.rfc-editor.org/info/rfc1035>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
RFC2119, March 1997, RFC2119, March 1997, <https://www.rfc-editor.org/info/
<http://www.rfc-editor.org/info/rfc2119>. rfc2119>.
[RFC2181] Elz, R. and R. Bush, "Clarifications to the DNS [RFC2181] Elz, R. and R. Bush, "Clarifications to the DNS
Specification", RFC 2181, DOI 10.17487/RFC2181, July 1997, Specification", RFC 2181, DOI 10.17487/RFC2181, July 1997,
<http://www.rfc-editor.org/info/rfc2181>. <https://www.rfc-editor.org/info/rfc2181>.
[RFC4034] Arends, R., Austein, R., Larson, M., Massey, D., and S. [RFC4034] Arends, R., Austein, R., Larson, M., Massey, D., and S.
Rose, "Resource Records for the DNS Security Extensions", Rose, "Resource Records for the DNS Security Extensions",
RFC 4034, DOI 10.17487/RFC4034, March 2005, RFC 4034, DOI 10.17487/RFC4034, March 2005,
<http://www.rfc-editor.org/info/rfc4034>. <https://www.rfc-editor.org/info/rfc4034>.
[RFC5155] Laurie, B., Sisson, G., Arends, R., and D. Blacka, "DNS [RFC5155] Laurie, B., Sisson, G., Arends, R., and D. Blacka, "DNS
Security (DNSSEC) Hashed Authenticated Denial of Security (DNSSEC) Hashed Authenticated Denial of
Existence", RFC 5155, DOI 10.17487/RFC5155, March 2008, Existence", RFC 5155, DOI 10.17487/RFC5155, March 2008,
<http://www.rfc-editor.org/info/rfc5155>. <https://www.rfc-editor.org/info/rfc5155>.
[RFC6891] Damas, J., Graff, M., and P. Vixie, "Extension Mechanisms [RFC6891] Damas, J., Graff, M., and P. Vixie, "Extension Mechanisms
for DNS (EDNS(0))", STD 75, RFC 6891, DOI 10.17487/ for DNS (EDNS(0))", STD 75, RFC 6891, DOI 10.17487/
RFC6891, April 2013, RFC6891, April 2013, <https://www.rfc-editor.org/info/
<http://www.rfc-editor.org/info/rfc6891>. rfc6891>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <http://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
Author's Address Author's Address
Ray Bellis Ray Bellis
Internet Systems Consortium, Inc. Internet Systems Consortium, Inc.
950 Charter Street 950 Charter Street
Redwood City CA 94063 Redwood City CA 94063
USA USA
Phone: +1 650 423 1200 Phone: +1 650 423 1200
Email: ray@isc.org Email: ray@isc.org
 End of changes. 12 change blocks. 
18 lines changed or deleted 18 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/