draft-ietf-dnsop-attrleaf-08.txt   draft-ietf-dnsop-attrleaf-09.txt 
dnsop D. Crocker dnsop D. Crocker
Internet-Draft Brandenburg InternetWorking Internet-Draft Brandenburg InternetWorking
Intended status: Best Current Practice May 22, 2018 Intended status: Best Current Practice May 22, 2018
Expires: November 23, 2018 Expires: November 23, 2018
DNS Scoped Data Through '_Underscore' Naming of Attribute Leaves DNS Scoped Data Through '_Underscore' Naming of Attribute Leaves
draft-ietf-dnsop-attrleaf-08 draft-ietf-dnsop-attrleaf-09
Abstract Abstract
Formally, any DNS resource record may occur for any domain name. Formally, any DNS resource record may occur for any domain name.
However some services have defined an operational convention, which However some services have defined an operational convention, which
applies to DNS leaf nodes that are under a DNS branch having one or applies to DNS leaf nodes that are under a DNS branch having one or
more reserved node names, each beginning with an underscore. The more reserved node names, each beginning with an underscore. The
underscore naming construct defines a semantic scope for DNS record underscore naming construct defines a semantic scope for DNS record
types that are associated with the parent domain, above the types that are associated with the parent domain, above the
underscored branch. This specification explores the nature of this underscored branch. This specification explores the nature of this
skipping to change at page 2, line 17 skipping to change at page 2, line 17
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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. _Underscore Scoping . . . . . . . . . . . . . . . . . . . 2 1.1. _Underscore Scoping . . . . . . . . . . . . . . . . . . . 2
1.2. Scaling Benefits . . . . . . . . . . . . . . . . . . . . 4 1.2. Scaling Benefits . . . . . . . . . . . . . . . . . . . . 4
2. DNS Underscore Scoped Entry Registries Function . . . . . . . 4 2. DNS Underscore Scoped Entry Registries Function . . . . . . . 4
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 3. RRset Use Registration Template . . . . . . . . . . . . . . . 5
3.1. DNS Underscore Global Scoped Entry Registry . . . . . . . 6 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
3.2. DNS Underscore Global Scoped Entry Registry Definition . 6 4.1. DNS Underscore Global Scoped Entry Registry . . . . . . . 6
3.3. Initial entries . . . . . . . . . . . . . . . . . . . . . 7 4.2. DNS Underscore Global Scoped Entry Registry Definition . 7
4. Guidance for Expert Review . . . . . . . . . . . . . . . . . 9 4.3. Initial entries . . . . . . . . . . . . . . . . . . . . . 7
5. Security Considerations . . . . . . . . . . . . . . . . . . . 9 5. Guidance for Expert Review . . . . . . . . . . . . . . . . . 9
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 6. Security Considerations . . . . . . . . . . . . . . . . . . . 9
6.1. Normative References . . . . . . . . . . . . . . . . . . 9 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
6.2. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 11 7.1. Normative References . . . . . . . . . . . . . . . . . . 9
7.2. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 11 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 11
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 11 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction 1. Introduction
The core Domain Name System (DNS) technical specifications assign no The core Domain Name System (DNS) technical specifications assign no
semantics to domain names or their parts, and no constraints upon semantics to domain names or their parts, and no constraints upon
which resource record (RR) types are permitted to be stored under which resource record (RR) types are permitted to be stored under
particular names [RFC1035], [RFC2181]. Over time, some leaf node particular names [RFC1035], [RFC2181]. Over time, some leaf node
names, such as "www" and "ftp" have come to imply support for names, such as "www" and "ftp" have come to imply support for
skipping to change at page 5, line 41 skipping to change at page 5, line 41
names is the responsibility of the specification that creates the names is the responsibility of the specification that creates the
highest-level (right-most) global registry entry. highest-level (right-most) global registry entry.
That is, if a scheme using a global underscore node name also has That is, if a scheme using a global underscore node name also has
one or more subordinate levels of underscore node naming, the one or more subordinate levels of underscore node naming, the
namespaces from which names for those lower levels is chosen is namespaces from which names for those lower levels is chosen is
controlled by the parent underscore node name. Each globally- controlled by the parent underscore node name. Each globally-
registered underscore name owns a distinct, subordinate name registered underscore name owns a distinct, subordinate name
space. space.
3. IANA Considerations 3. RRset Use Registration Template
This section provides a basic template that can be used to register
new entries in the IANA DNS Underscore Global Scoped Entry Registry,
if the right-most underscored name above the RRTYPE is not already
registered. The text can be added to specifications using
RRTYPE/_Node-name combinations that have not already been registered.
"Per {RFC Attrleaf} please add the following entry to the DNS
Underscore Global Scoped Entry Registry:"
Note to RFC Editor: Please replace the above "{RFC Attrleaf}" text
with a reference to this document's RFC number. /d
+----------+-------------------+------------------------------------+
| RR Type | _NODE NAME | REFERENCE |
+----------+-------------------+------------------------------------+
| {RRTYPE} | _{DNS global node | {citation for the document making |
| | name} | the addition.} |
+----------+-------------------+------------------------------------+
Table 1: Underscore Global Registry Entry
4. IANA Considerations
Per [RFC8126], IANA is requested to establish the: Per [RFC8126], IANA is requested to establish the:
DNS Underscore Global Scoped Entry Registry DNS Underscore Global Scoped Entry Registry
This section describes actions requested of IANA. The guidance in This section describes actions requested of IANA. The guidance in
[IANA] is used. [IANA] is used.
3.1. DNS Underscore Global Scoped Entry Registry 4.1. DNS Underscore Global Scoped Entry Registry
The DNS Global Underscore Scoped Entry Registry is for DNS node names The DNS Global Underscore Scoped Entry Registry is for DNS node names
that begin with the underscore character (_) and are the right-most that begin with the underscore character (_) and are the right-most
occurrence of any underscored names in a domain name sequence having occurrence of any underscored names in a domain name sequence having
that form; that is they are the "top" of a DNS branch, under a that form; that is they are the "top" of a DNS branch, under a
"parent" domain name. "parent" domain name.
o This registry is to operate under the IANA rules for "Expert o This registry is to operate under the IANA rules for "Expert
Review" registration; see Section 4. Review" registration; see Section 5.
o The contents of each entry in the Global registry are defined in o The contents of each entry in the Global registry are defined in
Section 3.2. Section 4.2.
o Each entry in the registry MUST contain values for all of the o Each entry in the registry MUST contain values for all of the
fields specified in Section 3.2. fields specified in Section 4.2.
o Within the registry, the combination of RR Type and _Node Name o Within the registry, the combination of RR Type and _Node Name
MUST be unique. MUST be unique.
o The table is to be maintained with entries sorted by the first o The table is to be maintained with entries sorted by the first
column (RR Type) and within that the second column (_Node Name). column (RR Type) and within that the second column (_Node Name).
o The required Reference for an entry MUST have a stable resolution o The required Reference for an entry MUST have a stable resolution
to the organization controlling that registry entry to the organization controlling that registry entry
3.2. DNS Underscore Global Scoped Entry Registry Definition 4.2. DNS Underscore Global Scoped Entry Registry Definition
A registry entry contains: A registry entry contains:
RR Type: Lists an RR type that is defined for use within this RR Type: Lists an RR type that is defined for use within this
scope. scope.
_Node Name: Specifies a single _underscore name that defines a _Node Name: Specifies a single _underscore name that defines a
reserved name; this name is the "global" entry name for the reserved name; this name is the "global" entry name for the
scoped resource record types that are associated with that scoped resource record types that are associated with that
name name
References: Lists specification that defines a record type and its References: Lists specification that defines a record type and its
use under this Name. The organization producing the use under this Name. The organization producing the
specification retains control over the registry entry for specification retains control over the registry entry for
the _Node Name. the _Node Name.
Each RR type that is to be used MUST have a separate registry entry. Each RR type that is to be used MUST have a separate registry entry.
3.3. Initial entries 4.3. Initial entries
Initial entries in the registry are: Initial entries in the registry are:
+------------+-----------------+------------+ +------------+-----------------+------------+
| RR Type | _NODE NAME | REFERENCE | | RR Type | _NODE NAME | REFERENCE |
+------------+-----------------+------------+ +------------+-----------------+------------+
| OPENPGPKEY | _openpgpkey | [RFC7929] | | OPENPGPKEY | _openpgpkey | [RFC7929] |
| SMIMEA | _smimecert | [RFC8162] | | SMIMEA | _smimecert | [RFC8162] |
| SRV | _dccp | [RFC2782] | | SRV | _dccp | [RFC2782] |
| SRV | _sctp | [RFC2782] | | SRV | _sctp | [RFC2782] |
skipping to change at page 8, line 52 skipping to change at page 8, line 52
| URI | _udp | [RFC7553] | | URI | _udp | [RFC7553] |
| URI | _unifmsg | [RFC7553] | | URI | _unifmsg | [RFC7553] |
| URI | _vcard | [RFC7553] | | URI | _vcard | [RFC7553] |
| URI | _videomsg | [RFC7553] | | URI | _videomsg | [RFC7553] |
| URI | _voice | [RFC7553] | | URI | _voice | [RFC7553] |
| URI | _voicemsg | [RFC7553] | | URI | _voicemsg | [RFC7553] |
| URI | _vpim | [RFC7553] | | URI | _vpim | [RFC7553] |
| URI | _xmp | [RFC7553] | | URI | _xmp | [RFC7553] |
+------------+-----------------+------------+ +------------+-----------------+------------+
Table 1: Underscore Global Registry (initial entries) Table 2: Underscore Global Registry (initial entries)
4. Guidance for Expert Review 5. Guidance for Expert Review
This section provides guidance for expert review of registration This section provides guidance for expert review of registration
requests in the of DNS Underscore Global Scoped Entry Registry. requests in the of DNS Underscore Global Scoped Entry Registry.
This review is solely to determine adequacy of a requested entry This review is solely to determine adequacy of a requested entry
in this Registry, and does not include review of other aspects of in this Registry, and does not include review of other aspects of
the document specifying that entry. For example such a document the document specifying that entry. For example such a document
might also contain a definition of the resource record type that might also contain a definition of the resource record type that
is referenced by the requested entry. Any required review of that is referenced by the requested entry. Any required review of that
definition is separate from the expert review required here. definition is separate from the expert review required here.
skipping to change at page 9, line 30 skipping to change at page 9, line 30
clear, precise and complete clear, precise and complete
o The combination of the _underscore name, under which the listed o The combination of the _underscore name, under which the listed
resource record type is used, and the resource record type, is resource record type is used, and the resource record type, is
unique in the table unique in the table
For the purposes of this Expert Review, other matters of the For the purposes of this Expert Review, other matters of the
specification's technical quality, adequacy or the like are outside specification's technical quality, adequacy or the like are outside
of scope. of scope.
5. Security Considerations 6. Security Considerations
This memo raises no security issues. This memo raises no security issues.
6. References 7. References
6.1. Normative References 7.1. Normative References
[ACME] Barnes, R., Hoffman-Andrews, J., McCarney, D., and J. [ACME] Barnes, R., Hoffman-Andrews, J., McCarney, D., and J.
Kasten, "Automatic Certificate Management Environment Kasten, "Automatic Certificate Management Environment
(ACME)", I-D draft-ietf-acme-acme-11, March 2018. (ACME)", I-D draft-ietf-acme-acme-11, March 2018.
[IANA] M. Cotton, B. Leiba, and T. Narten, "Guidelines for [IANA] M. Cotton, B. Leiba, and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", RFC 8126, Writing an IANA Considerations Section in RFCs", RFC 8126,
June 2017. June 2017.
[MTA-STS] Margolis, D., Risher, M., Ramakrishnan, B., Brotman, A., [MTA-STS] Margolis, D., Risher, M., Ramakrishnan, B., Brotman, A.,
skipping to change at page 11, line 5 skipping to change at page 11, line 5
Writing an IANA Considerations Section in RFCs", RFC 8126, Writing an IANA Considerations Section in RFCs", RFC 8126,
June 2017. June 2017.
[RFC8162] Hoffman, P. and J. Schlyter, "Using Secure DNS to [RFC8162] Hoffman, P. and J. Schlyter, "Using Secure DNS to
Associate Certificates with Domain Names for S/MIME", Associate Certificates with Domain Names for S/MIME",
RFC 8162, May 2017. RFC 8162, May 2017.
[RFC952] Harrenstien, K., Stahl, M., and E. Feinler, "DOD Internet [RFC952] Harrenstien, K., Stahl, M., and E. Feinler, "DOD Internet
Host Table Specification", RFC 952, October 1985. Host Table Specification", RFC 952, October 1985.
6.2. URIs 7.2. URIs
[1] mailto:dnsop@ietf.org [1] mailto:dnsop@ietf.org
Appendix A. Acknowledgements Appendix A. Acknowledgements
Thanks go to Bill Fenner, Tony Hansen, Martin Hoffmann, Peter Koch, Thanks go to Bill Fenner, Tony Hansen, Martin Hoffmann, Peter Koch,
Olaf Kolkman, and Andrew Sullivan for diligent review of the (much) Olaf Kolkman, and Andrew Sullivan for diligent review of the (much)
earlier drafts. For the later enhancements, thanks to: Stephane earlier drafts. For the later enhancements, thanks to: Stephane
Bortzmeyer, Bob Harold, Warren Kumari, John Levine, Joel Jaeggli, Bortzmeyer, Bob Harold, Warren Kumari, John Levine, Joel Jaeggli,
Petr Špaček, Ondřej Surř, Paul Vixie, Tim Petr Špaček, Ondřej Surř, Paul Vixie, Tim
 End of changes. 15 change blocks. 
23 lines changed or deleted 47 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/