rfc8552.txt   test8552.v2v3.txt 
Internet Engineering Task Force (IETF) D. Crocker Internet Engineering Task Force (IETF) D. Crocker
Request for Comments: 8552 Brandenburg InternetWorking Request for Comments: 8552 Brandenburg InternetWorking
BCP: 222 March 2019 Category: Best Current Practice March 2019
Category: Best Current Practice
ISSN: 2070-1721 ISSN: 2070-1721
Scoped Interpretation of DNS Resource Records through Scoped Interpretation of DNS Resource Records through "Underscored"
"Underscored" Naming of Attribute Leaves Naming of Attribute Leaves
Abstract Abstract
Formally, any DNS Resource Record (RR) may occur under any domain Formally, any DNS Resource Record (RR) may occur under any domain
name. However, some services use an operational convention for name. However, some services use an operational convention for
defining specific interpretations of an RRset by locating the records defining specific interpretations of an RRset by locating the records
in a DNS branch under the parent domain to which the RRset actually in a DNS branch under the parent domain to which the RRset actually
applies. The top of this subordinate branch is defined by a naming applies. The top of this subordinate branch is defined by a naming
convention that uses a reserved node name, which begins with the convention that uses a reserved node name, which begins with the
underscore character (e.g., "_name"). The underscored naming underscore character (e.g., "_name"). The underscored naming
skipping to change at page 2, line 22 skipping to change at line 57
(https://trustee.ietf.org/license-info) in effect on the date of (https://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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction
1.1. Underscore-Based Scoping . . . . . . . . . . . . . . . . 3 1.1. Underscore-Based Scoping
1.2. Scaling Benefits . . . . . . . . . . . . . . . . . . . . 4 1.2. Scaling Benefits
1.3. Global Underscored Node Names . . . . . . . . . . . . . . 4 1.3. Global Underscored Node Names
1.4. Interaction with DNS Wildcards . . . . . . . . . . . . . 5 1.4. Interaction with DNS Wildcards
1.5. History . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.5. History
2. "Underscored and Globally Scoped DNS Node Names" Registry . . 6 2. "Underscored and Globally Scoped DNS Node Names" Registry
3. Guidance for Registering RRset Use . . . . . . . . . . . . . 7 3. Guidance for Registering RRset Use
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 4. IANA Considerations
4.1. "Underscored and Globally Scoped DNS Node Names" Registry 8 4.1. "Underscored and Globally Scoped DNS Node Names"
4.2. Enumservices Registrations Registry . . . . . . . . . . . 11 Registry
5. Security Considerations . . . . . . . . . . . . . . . . . . . 11 4.1.1. Contents of an Entry in the "Underscored
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 and Globally Scoped DNS Node Names" Registry
6.1. Normative References . . . . . . . . . . . . . . . . . . 12 4.1.2. Initial Node Names
6.2. Informative References . . . . . . . . . . . . . . . . . 15 4.1.3. _ta
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 15 4.1.4. _example
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 15 4.1.5. Guidance for Expert Review
4.2. Enumservices Registrations Registry
5. Security Considerations
6. References
6.1. Normative References
6.2. Informative References
Acknowledgements
Author's Address
1. Introduction 1. Introduction
The core Domain Name System (DNS) technical specifications ([RFC1035] The core Domain Name System (DNS) technical specifications ([RFC1035]
and [RFC2181]) assign no semantics to domain names or their parts, and [RFC2181]) assign no semantics to domain names or their parts,
and no constraints upon which resource record (RR) types are and no constraints upon which resource record (RR) types are
permitted to be stored under particular names [RFC1035] [RFC2181]. permitted to be stored under particular names [RFC1035] [RFC2181].
Over time, some leaf node names, such as "www" and "ftp", have come Over time, some leaf node names, such as "www" and "ftp", have come
to imply support for particular services, but this is a matter of to imply support for particular services, but this is a matter of
operational convention rather than defined protocol semantics. This operational convention rather than defined protocol semantics. This
skipping to change at page 6, line 23 skipping to change at line 251
name, the global underscored node name -- the underscored name name, the global underscored node name -- the underscored name
that is closest to the DNS root -- MUST be entered into this that is closest to the DNS root -- MUST be entered into this
registry. registry.
An underscored name defines the scope of use for specific resource An underscored name defines the scope of use for specific resource
record types, which are associated with the domain name that is the record types, which are associated with the domain name that is the
"parent" to the branch defined by the underscored name. A given name "parent" to the branch defined by the underscored name. A given name
defines a specific, constrained context for one or more RR TYPEs, defines a specific, constrained context for one or more RR TYPEs,
where use of such record types conforms to the defined constraints. where use of such record types conforms to the defined constraints.
o Within a leaf that is underscore scoped, other RRsets that are not * Within a leaf that is underscore scoped, other RRsets that are not
specified as part of the scope MAY be used. specified as part of the scope MAY be used.
Structurally, the registry is defined as a single, flat table of RR Structurally, the registry is defined as a single, flat table of RR
TYPEs, under node names beginning with underscore. In some cases, TYPEs, under node names beginning with underscore. In some cases,
such as for use of an SRV record, the full scoping name might be such as for use of an SRV record, the full scoping name might be
multi-part, as a sequence of underscored names. Semantically, that multi-part, as a sequence of underscored names. Semantically, that
sequence represents a hierarchical model, and it is theoretically sequence represents a hierarchical model, and it is theoretically
reasonable to allow reuse of a subordinate underscored name in a reasonable to allow reuse of a subordinate underscored name in a
different, global underscored context; that is, a subordinate name is different, global underscored context; that is, a subordinate name is
meaningful only within the scope of the global underscored node name. meaningful only within the scope of the global underscored node name.
Therefore, they are ignored by this "Underscored and Globally Scoped Therefore, they are ignored by this "Underscored and Globally Scoped
DNS Node Names" registry. This registry is for the definition of DNS Node Names" registry. This registry is for the definition of
highest-level -- that is, global -- underscored node name used. highest-level -- that is, global -- underscored node name used.
+----------------------------+ +----------------------------+
| NAME | | NAME |
+----------------------------+ +============================+
| _service1 | | _service1 |
+----------------------------+
| _protoB._service2 | | _protoB._service2 |
+----------------------------+
| _protoB._service3 | | _protoB._service3 |
+----------------------------+
| _protoC._service3 | | _protoC._service3 |
+----------------------------+
| _useX._protoD._service4 | | _useX._protoD._service4 |
+----------------------------+
| _protoE._region._authority | | _protoE._region._authority |
+----------------------------+ +----------------------------+
Table 1: Examples of Underscored Names Table 1: Examples of
Underscored Names
Only global underscored node names are registered in the "Underscored Only global underscored node names are registered in the "Underscored
and Globally Scoped DNS Node Names" registry. From the example and Globally Scoped DNS Node Names" registry. From the example
above, that would mean _service1, _service2, _service3, _service 4, above, that would mean _service1, _service2, _service3, _service 4,
and _authority would be listed in the IANA registry. and _authority would be listed in the IANA registry.
o The use of underscored node names is specific to each RR TYPE that * The use of underscored node names is specific to each RR TYPE that
is being scoped. Each name defines a place but does not define is being scoped. Each name defines a place but does not define
the rules for what appears underneath that place, either as the rules for what appears underneath that place, either as
additional underscored naming or as a leaf node with resource additional underscored naming or as a leaf node with resource
records. Details for those rules are provided by specifications records. Details for those rules are provided by specifications
for individual RR TYPEs. The sections below describe the way that for individual RR TYPEs. The sections below describe the way that
existing underscored names are used with the RR TYPEs that they existing underscored names are used with the RR TYPEs that they
name. name.
o Definition and registration of subordinate underscored node names * Definition and registration of subordinate underscored node names
are the responsibility of the specification that creates the are the responsibility of the specification that creates the
global underscored node name registry entry. global underscored node name registry entry.
That is, if a scheme using a global underscored node name has one or That is, if a scheme using a global underscored node name has one or
more subordinate levels of underscored node naming, the namespaces more subordinate levels of underscored node naming, the namespaces
from which names for those lower levels are chosen are controlled by from which names for those lower levels are chosen are controlled by
the parent underscored node name. Each registered global underscored the parent underscored node name. Each registered global underscored
node name owns a distinct, subordinate namespace. node name owns a distinct, subordinate namespace.
3. Guidance for Registering RRset Use 3. Guidance for Registering RRset Use
This section provides guidance for specification writers, with a This section provides guidance for specification writers, with a
basic template they can use, to register new entries in the basic template they can use, to register new entries in the
"Underscored and Globally Scoped DNS Node Names" registry. The text "Underscored and Globally Scoped DNS Node Names" registry. The text
can be added to specifications using RR TYPE / _NODE NAME can be added to specifications using RR TYPE / _NODE NAME
combinations that have not already been registered: combinations that have not already been registered:
Per RFC 8552, please add the following entry to the "Underscored Per RFC 8552, please add the following entry to the "Underscored
and Globally Scoped DNS Node Names" registry: and Globally Scoped DNS Node Names" registry:
+---------+-------------------+-------------------------------------+ +-----------+-------------------------+----------------------------+
| RR Type | _NODE NAME | Reference | | RR Type | _NODE NAME | Reference |
+---------+-------------------+-------------------------------------+ +===========+=========================+============================+
| {RR | _{DNS global node | {citation for the document making | | {RR TYPE} | _{DNS global node name} | {citation for the document |
| TYPE} | name} | the addition.} | | | | making the addition.} |
+---------+-------------------+-------------------------------------+ +-----------+-------------------------+----------------------------+
Table 2: Template for Entries in the Table 2: Template for Entries in the "Underscored and Globally
"Underscored and Globally Scoped DNS Node Names" Registry Scoped DNS Node Names" Registry
4. IANA Considerations 4. IANA Considerations
IANA has established the "Underscored and Globally Scoped DNS Node IANA has established the "Underscored and Globally Scoped DNS Node
Names" registry. This section describes the registry, the Names" registry. This section describes the registry, the
definitions, the initial entries, the use of_ta and _example, and the definitions, the initial entries, the use of_ta and _example, and the
use of [RFC8126] as guidance for expert review. IANA has also use of [RFC8126] as guidance for expert review. IANA has also
updated the "Enumservices Registrations" registry with a pointer to updated the "Enumservices Registrations" registry with a pointer to
this document. this document.
4.1. "Underscored and Globally Scoped DNS Node Names" Registry 4.1. "Underscored and Globally Scoped DNS Node Names" Registry
The "Underscored and Globally Scoped DNS Node Names" registry The "Underscored and Globally Scoped DNS Node Names" registry
includes any DNS node name that begins with the underscore character includes any DNS node name that begins with the underscore character
("_", ASCII 0x5F) and is the underscored node name closest to the ("_", ASCII 0x5F) and is the underscored node name closest to the
root; that is, it defines the highest level of a DNS branch under a root; that is, it defines the highest level of a DNS branch under a
"parent" domain name. "parent" domain name.
o This registry operates under the IANA rules for "Expert Review" * This registry operates under the IANA rules for "Expert Review"
registration; see Section 4.1.5. registration; see Section 4.1.5.
o The contents of each entry in the registry are defined in * The contents of each entry in the registry are defined in
Section 4.1.1. Section 4.1.1.
o Each entry in the registry MUST contain values for all of the * Each entry in the registry MUST contain values for all of the
fields specified in Section 4.1.1. fields specified in Section 4.1.1.
o Within the registry, the combination of RR Type and _NODE NAME * 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 * 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 * 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.
4.1.1. Contents of an Entry in the "Underscored and Globally Scoped DNS 4.1.1. Contents of an Entry in the "Underscored and Globally Scoped DNS Node
Node Names" Registry Names" Registry
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, underscored name that defines a _NODE NAME: Specifies a single, underscored name that defines a
reserved name; this name is the global entry name for reserved name; this name is the global entry name for
the scoped resource record types that are associated the scoped resource record types that are associated
with that name. For characters in the name that have with that name. For characters in the name that have
an uppercase form and a lowercase form, the character an uppercase form and a lowercase form, the character
MUST be recorded as lowercase to simplify name MUST be recorded as lowercase to simplify name
comparisons. comparisons.
Reference: Lists the specification that defines a record type and Reference: Lists the specification that defines a record type and
its use under this _Node Name. The organization its use under this _Node Name. The organization
producing the specification retains control over the producing the specification retains control over the
skipping to change at page 9, line 35 skipping to change at line 395
Each RR TYPE that is to be used with a _Node Name MUST have a Each RR TYPE that is to be used with a _Node Name MUST have a
separate registry entry. separate registry entry.
4.1.2. Initial Node Names 4.1.2. Initial Node Names
The initial entries in the registry are as follows: The initial entries in the registry are as follows:
+------------+-----------------------+---------------+ +------------+-----------------------+---------------+
| RR Type | _NODE NAME | Reference | | RR Type | _NODE NAME | Reference |
+------------+-----------------------+---------------+ +============+=======================+===============+
| * | _example | Section 4.1.4 | | * | _example | Section 4.1.4 |
+------------+-----------------------+---------------+
| NULL | _ta-* {Section 4.1.3} | [RFC8145] | | NULL | _ta-* {Section 4.1.3} | [RFC8145] |
+------------+-----------------------+---------------+
| OPENPGPKEY | _openpgpkey | [RFC7929] | | OPENPGPKEY | _openpgpkey | [RFC7929] |
+------------+-----------------------+---------------+
| SMIMEA | _smimecert | [RFC8162] | | SMIMEA | _smimecert | [RFC8162] |
+------------+-----------------------+---------------+
| SRV | _dccp | [RFC2782] | | SRV | _dccp | [RFC2782] |
+------------+-----------------------+---------------+
| SRV | _http | [RFC4386] | | SRV | _http | [RFC4386] |
+------------+-----------------------+---------------+
| SRV | _ipv6 | [RFC5026] | | SRV | _ipv6 | [RFC5026] |
+------------+-----------------------+---------------+
| SRV | _ldap | [RFC4386] | | SRV | _ldap | [RFC4386] |
+------------+-----------------------+---------------+
| SRV | _ocsp | [RFC4386] | | SRV | _ocsp | [RFC4386] |
+------------+-----------------------+---------------+
| SRV | _sctp | [RFC2782] | | SRV | _sctp | [RFC2782] |
+------------+-----------------------+---------------+
| SRV | _sip | [RFC5509] | | SRV | _sip | [RFC5509] |
+------------+-----------------------+---------------+
| SRV | _tcp | [RFC2782] | | SRV | _tcp | [RFC2782] |
+------------+-----------------------+---------------+
| SRV | _udp | [RFC2782] | | SRV | _udp | [RFC2782] |
+------------+-----------------------+---------------+
| SRV | _xmpp | [RFC3921] | | SRV | _xmpp | [RFC3921] |
+------------+-----------------------+---------------+
| TLSA | _dane | [RFC7671] | | TLSA | _dane | [RFC7671] |
+------------+-----------------------+---------------+
| TLSA | _sctp | [RFC6698] | | TLSA | _sctp | [RFC6698] |
+------------+-----------------------+---------------+
| TLSA | _tcp | [RFC6698] | | TLSA | _tcp | [RFC6698] |
+------------+-----------------------+---------------+
| TLSA | _udp | [RFC6698] | | TLSA | _udp | [RFC6698] |
+------------+-----------------------+---------------+
| TXT | _acme-challenge | [RFC8555] | | TXT | _acme-challenge | [RFC8555] |
+------------+-----------------------+---------------+
| TXT | _dmarc | [RFC7489] | | TXT | _dmarc | [RFC7489] |
+------------+-----------------------+---------------+
| TXT | _domainkey | [RFC6376] | | TXT | _domainkey | [RFC6376] |
+------------+-----------------------+---------------+
| TXT | _mta-sts | [RFC8461] | | TXT | _mta-sts | [RFC8461] |
+------------+-----------------------+---------------+
| TXT | _spf | [RFC7208] | | TXT | _spf | [RFC7208] |
+------------+-----------------------+---------------+
| TXT | _sztp | [ZEROTOUCH] | | TXT | _sztp | [ZEROTOUCH] |
+------------+-----------------------+---------------+
| TXT | _tcp | [RFC6763] | | TXT | _tcp | [RFC6763] |
+------------+-----------------------+---------------+
| TXT | _udp | [RFC6763] | | TXT | _udp | [RFC6763] |
+------------+-----------------------+---------------+
| TXT | _vouch | [RFC5518] | | TXT | _vouch | [RFC5518] |
+------------+-----------------------+---------------+
| URI | _acct | [RFC6118] | | URI | _acct | [RFC6118] |
+------------+-----------------------+---------------+
| URI | _dccp | [RFC7566] | | URI | _dccp | [RFC7566] |
+------------+-----------------------+---------------+
| URI | _email | [RFC6118] | | URI | _email | [RFC6118] |
+------------+-----------------------+---------------+
| URI | _ems | [RFC6118] | | URI | _ems | [RFC6118] |
+------------+-----------------------+---------------+
| URI | _fax | [RFC6118] | | URI | _fax | [RFC6118] |
+------------+-----------------------+---------------+
| URI | _ft | [RFC6118] | | URI | _ft | [RFC6118] |
+------------+-----------------------+---------------+
| URI | _h323 | [RFC6118] | | URI | _h323 | [RFC6118] |
+------------+-----------------------+---------------+
| URI | _iax | [RFC6118] | | URI | _iax | [RFC6118] |
+------------+-----------------------+---------------+
| URI | _ical-access | [RFC6118] | | URI | _ical-access | [RFC6118] |
+------------+-----------------------+---------------+
| URI | _ical-sched | [RFC6118] | | URI | _ical-sched | [RFC6118] |
+------------+-----------------------+---------------+
| URI | _ifax | [RFC6118] | | URI | _ifax | [RFC6118] |
+------------+-----------------------+---------------+
| URI | _im | [RFC6118] | | URI | _im | [RFC6118] |
+------------+-----------------------+---------------+
| URI | _mms | [RFC6118] | | URI | _mms | [RFC6118] |
+------------+-----------------------+---------------+
| URI | _pres | [RFC6118] | | URI | _pres | [RFC6118] |
+------------+-----------------------+---------------+
| URI | _pstn | [RFC6118] | | URI | _pstn | [RFC6118] |
+------------+-----------------------+---------------+
| URI | _sctp | [RFC6118] | | URI | _sctp | [RFC6118] |
+------------+-----------------------+---------------+
| URI | _sip | [RFC6118] | | URI | _sip | [RFC6118] |
+------------+-----------------------+---------------+
| URI | _sms | [RFC6118] | | URI | _sms | [RFC6118] |
+------------+-----------------------+---------------+
| URI | _tcp | [RFC6118] | | URI | _tcp | [RFC6118] |
+------------+-----------------------+---------------+
| URI | _udp | [RFC6118] | | URI | _udp | [RFC6118] |
+------------+-----------------------+---------------+
| URI | _unifmsg | [RFC6118] | | URI | _unifmsg | [RFC6118] |
+------------+-----------------------+---------------+
| URI | _vcard | [RFC6118] | | URI | _vcard | [RFC6118] |
+------------+-----------------------+---------------+
| URI | _videomsg | [RFC6118] | | URI | _videomsg | [RFC6118] |
+------------+-----------------------+---------------+
| URI | _voice | [RFC6118] | | URI | _voice | [RFC6118] |
+------------+-----------------------+---------------+
| URI | _voicemsg | [RFC6118] | | URI | _voicemsg | [RFC6118] |
+------------+-----------------------+---------------+
| URI | _vpim | [RFC6118] | | URI | _vpim | [RFC6118] |
+------------+-----------------------+---------------+
| URI | _web | [RFC6118] | | URI | _web | [RFC6118] |
+------------+-----------------------+---------------+
| URI | _xmpp | [RFC6118] | | URI | _xmpp | [RFC6118] |
+------------+-----------------------+---------------+ +------------+-----------------------+---------------+
Table 3: Initial Contents of the Table 3: Initial Contents of the "Underscored and
"Underscored and Globally Scoped DNS Node Names" Registry Globally Scoped DNS Node Names" Registry
4.1.3. _ta 4.1.3. _ta
Under the NULL RR Type, the entry "_ta-*" denotes all node names Under the NULL RR Type, the entry "_ta-*" denotes all node names
beginning with the string "_ta-*". It does NOT refer to a DNS beginning with the string "_ta-*". It does NOT refer to a DNS
wildcard specification. wildcard specification.
4.1.4. _example 4.1.4. _example
The node name "_example" is reserved across all RRsets. The node name "_example" is reserved across all RRsets.
skipping to change at page 11, line 25 skipping to change at line 536
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 it does not include review of other aspects in this registry, and it does not include review of other aspects
of the document specifying that entry. For example, such a of the document specifying that entry. For example, such a
document might also contain a definition of the resource record document might also contain a definition of the resource record
type that is referenced by the requested entry. Any required type that is referenced by the requested entry. Any required
review of that definition is separate from the expert review review of that definition is separate from the expert review
required here. required here.
The review is for the purposes of ensuring that: The review is for the purposes of ensuring that:
o The details for creating the registry entry are sufficiently * The details for creating the registry entry are sufficiently
clear, precise, and complete clear, precise, and complete
o The combination of the underscored name, under which the listed * The combination of the underscored 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.
4.2. Enumservices Registrations Registry 4.2. Enumservices Registrations Registry
The following note has been added to the "Enumservice Registrations" The following note has been added to the "Enumservice Registrations"
skipping to change at page 12, line 9 skipping to change at line 564
Scoped DNS Node Names" registry. Scoped DNS Node Names" registry.
5. Security Considerations 5. Security Considerations
This memo raises no security issues. This memo raises no security issues.
6. References 6. References
6.1. Normative References 6.1. Normative References
[RFC0952] Harrenstien, K., Stahl, M., and E. Feinler, "DoD Internet [RFC0952] Harrenstien, K., Stahl, M.K., and E.J. Feinler, "DoD
host table specification", RFC 952, DOI 10.17487/RFC0952, Internet host table specification", RFC 952,
October 1985, <https://www.rfc-editor.org/info/rfc952>. DOI 10.17487/RFC0952, October 1985,
<https://www.rfc-editor.org/info/rfc952>.
[RFC1034] Mockapetris, P., "Domain names - concepts and facilities", [RFC1034] Mockapetris, P.V., "Domain names - concepts and
STD 13, RFC 1034, DOI 10.17487/RFC1034, November 1987, facilities", STD 13, RFC 1034, DOI 10.17487/RFC1034,
<https://www.rfc-editor.org/info/rfc1034>. November 1987, <https://www.rfc-editor.org/info/rfc1034>.
[RFC1035] Mockapetris, P., "Domain names - implementation and [RFC1035] Mockapetris, P.V., "Domain names - implementation and
specification", STD 13, RFC 1035, DOI 10.17487/RFC1035, specification", STD 13, RFC 1035, DOI 10.17487/RFC1035,
November 1987, <https://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, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/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,
skipping to change at page 15, line 15 skipping to change at line 710
6.2. Informative References 6.2. Informative References
[RFC8553] Crocker, D., "DNS Attrleaf Changes: Fixing Specifications [RFC8553] Crocker, D., "DNS Attrleaf Changes: Fixing Specifications
That Use Underscored Node Names", RFC 8553, That Use Underscored Node Names", RFC 8553,
DOI 10.17487/RFC8553, March 2019, DOI 10.17487/RFC8553, March 2019,
<https://www.rfc-editor.org/info/rfc8553>. <https://www.rfc-editor.org/info/rfc8553>.
[ZEROTOUCH] [ZEROTOUCH]
Watsen, K., Abrahamsson, M., and I. Farrer, "Secure Zero Watsen, K., Abrahamsson, M., and I. Farrer, "Secure Zero
Touch Provisioning (SZTP)", Work in Progress, draft-ietf- Touch Provisioning (SZTP)", Work in Progress, draft-ietf-
netconf-zerotouch-29, January 2019. netconf-zerotouch-29, 15 January 2019.
Acknowledgements Acknowledgements
Thanks go to Bill Fenner, Dick Franks, Tony Hansen, Martin Hoffmann, Thanks go to Bill Fenner, Dick Franks, Tony Hansen, Martin Hoffmann,
Paul Hoffman, Peter Koch, Olaf Kolkman, Murray Kucherawy, John Paul Hoffman, Peter Koch, Olaf Kolkman, Murray Kucherawy, John
Levine, Benno Overeinder, and Andrew Sullivan for diligent review of Levine, Benno Overeinder, and Andrew Sullivan for diligent review of
the (much) earlier draft versions. For the later enhancements, the (much) earlier draft versions. For the later enhancements,
thanks to Stephane Bortzmeyer, Alissa Cooper, Bob Harold, Joel thanks to Stephane Bortzmeyer, Alissa Cooper, Bob Harold, Joel
Jaeggli, Benjamin Kaduk, Mirja Kuehlewind, Warren Kumari, John Jaeggli, Benjamin Kaduk, Mirja Kuehlewind, Warren Kumari, John
Levine, Benno Overeinder, Eric Rescorla, Adam Roach, Petr Spacek, Levine, Benno Overeinder, Eric Rescorla, Adam Roach, Petr Spacek,
skipping to change at page 15, line 37 skipping to change at line 732
Special thanks to Ray Bellis for his persistent encouragement to Special thanks to Ray Bellis for his persistent encouragement to
continue this effort, as well as the suggestion for an essential continue this effort, as well as the suggestion for an essential
simplification to the registration model. simplification to the registration model.
Author's Address Author's Address
Dave Crocker Dave Crocker
Brandenburg InternetWorking Brandenburg InternetWorking
675 Spruce Dr. 675 Spruce Dr.
Sunnyvale, CA 94086 Sunnyvale, CA 94086
United States of America United States of America
Phone: +1.408.246.8253 Phone: +1.408.246.8253
Email: dcrocker@bbiw.net Email: dcrocker@bbiw.net
URI: http://bbiw.net/ URI: http://bbiw.net/
 End of changes. 86 change blocks. 
57 lines changed or deleted 124 lines changed or added

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