draft-ietf-dnsop-attrleaf-fix-01.txt   draft-ietf-dnsop-attrleaf-fix-02.txt 
dnsop D. Crocker dnsop D. Crocker
Internet-Draft Brandenburg InternetWorking Internet-Draft Brandenburg InternetWorking
Updates: 2782, 3263, 3404, 3529, 3620, May 22, 2018 Updates: 2782, 3263, 3404, 3529, 3620, July 15, 2018
3832, 3887, 3958, 4120, 4227, 3832, 3861, 3887, 3958, 4120,
4386, 4387, 4976, 5026, 5328, 4227, 4386, 4387, 4976, 5026,
5389, 5415, 5555, 5679, 5766, 5328, 5389, 5415, 5518, 5555,
5780, 5804, 6011, 6120, 6186, 5617, 5679, 5766, 5780, 5804,
6733 (if approved) 5864, 5928, 6011, 6120, 6186,
6376, 6733, 7208, 7489 (if
approved)
Intended status: Best Current Practice Intended status: Best Current Practice
Expires: November 23, 2018 Expires: January 16, 2019
DNS Attrleaf Changes: Fixing Specifications with _Underscored Node Name DNS Attrleaf Changes: Fixing Specifications with Underscored Node Name
Use Use
draft-ietf-dnsop-attrleaf-fix-01 draft-ietf-dnsop-attrleaf-fix-02
Abstract Abstract
Original uses of an _underscore character as a domain node name Original uses of an underscore character as a domain node name
prefix, which creates a space for constrained interpretation of prefix, which creates a space for constrained interpretation of
resource records, were specified without the benefit of an IANA resource records, were specified without the benefit of an IANA
registry. This produced an entirely uncoordinated set of name- registry. This produced an entirely uncoordinated set of name-
creation activities, all drawing from the same namespace. A registry creation activities, all drawing from the same namespace. A registry
now has been defined. However the existing specifications that use now has been defined. However the existing specifications that use
_underscore naming need to be modified, to be in line with the new underscore naming need to be modified, to be in line with the new
registry. This document specifies those changes. The changes registry. This document specifies those changes. The changes
preserve existing software and operational practice, while adapting preserve existing software and operational practice, while adapting
the specifications for those practices to the newer _underscore the specifications for those practices to the newer underscore
registry model. registry model.
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
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 November 23, 2018. This Internet-Draft will expire on January 16, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 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
(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
skipping to change at page 2, line 35 skipping to change at page 2, line 35
2.2. SRV RRset Use . . . . . . . . . . . . . . . . . . . . . . 4 2.2. SRV RRset Use . . . . . . . . . . . . . . . . . . . . . . 4
2.3. URI RRset Use . . . . . . . . . . . . . . . . . . . . . . 5 2.3. URI RRset Use . . . . . . . . . . . . . . . . . . . . . . 5
3. Underscored Template Specifications . . . . . . . . . . . . . 6 3. Underscored Template Specifications . . . . . . . . . . . . . 6
3.1. SRV Specification Changes . . . . . . . . . . . . . . . . 6 3.1. SRV Specification Changes . . . . . . . . . . . . . . . . 6
3.2. URI Specification Changes . . . . . . . . . . . . . . . . 7 3.2. URI Specification Changes . . . . . . . . . . . . . . . . 7
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
5. Security Considerations . . . . . . . . . . . . . . . . . . . 9 5. Security Considerations . . . . . . . . . . . . . . . . . . . 9
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
6.1. Normative References . . . . . . . . . . . . . . . . . . 9 6.1. Normative References . . . . . . . . . . . . . . . . . . 9
6.2. References -- Informative . . . . . . . . . . . . . . . . 10 6.2. References -- Informative . . . . . . . . . . . . . . . . 10
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 13 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 12
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 13 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 13
1. Introduction 1. Introduction
Original uses of an _underscore character as a domain node name Original uses of an underscore character as a domain node name
[RFC1035] prefix, which creates a space for constrained [RFC1035] prefix, which creates a space for constrained
interpretation of resource records, were specified without the interpretation of resource records, were specified without the
benefit of an [IANA-reg] registry. This produced an entirely benefit of an [IANA-reg] registry. This produced an entirely
uncoordinated set of name-creation activities, all drawing from the uncoordinated set of name-creation activities, all drawing from the
same namespace. A registry has been now defined, and that document same namespace. A registry has been now defined, and that document
discusses the background for _underscore domain name use [Attrleaf]. discusses the background for underscored domain name use [Attrleaf].
The basic model for underscored name registration, as specified in The basic model for underscored name registration, as specified in
[Attrleaf], is to have each registry entry be unique in terms of the [Attrleaf], is to have each registry entry be unique in terms of the
combination of a resource record type and a 'global' (ie, right-most) combination of a resource record type and a 'global' (highest-level)
underscore name. underscored name; that is, the node name beginning with an
underscore, which is the closest to the DNS root.
The existing uses of _underscore naming have specifications that do The existing uses of underscored naming have specifications that do
not reflect the existence of this integrated registry. For the new not reflect the existence of this integrated registry. For the new
reader or the new editor of one of those documents, there is reader or the new editor of one of those documents, there is
currently nothing signaling that the underscore name(s) defined in currently nothing signaling that the underscore name(s) defined in
the document are now processed through an IANA registry. This the document are now processed through an IANA registry. This
document remedies that, by marking such a published document with an document remedies that, by marking such a published document with an
update, indicating the nature of the change. update, indicating the nature of the change.
The documents that define the SRV [RFC2782] and URI [RFC7553] DNS Further, the documents that define the SRV [RFC2782] and URI
resource records provide a meta-template for underscore assignments, [RFC7553] DNS resource records provide a meta-template for
partially based on separate registries [RFC6335]. For the portion underscored name assignments, partially based on separate registries
that selects the global (right-most) underscore name, this [RFC6335]. For the portion that selects the global (highest-level)
perpetuates uncoordinated assignment activities by separate technical underscored name, this perpetuates uncoordinated assignment
specifications, out of the same name space. This document remedies activities by separate technical specifications, out of the same name
that by providing detail for revisions to the SRV and URI space. This document remedies that by providing detail for revisions
specifications, to bring their use in line with the single, to the SRV and URI specifications, to bring their use in line with
integrated global underscore registry. the single, integrated global underscore registry.
The result of these changes preserves existing software and The result of these changes preserves existing software and
operations practices, while adapting the technical specifications to operations practices, while adapting the technical specifications to
the newer _underscore registry model. the newer underscore registry model.
2. Underscored RRset Use in Specifications 2. Underscored RRset Use in Specifications
The use of underscored node names is specific to each RRTYPE that is The use of underscored node names is specific to each RRTYPE that is
being scoped. Each name defines a place, but does not define the being scoped. Each name defines a place, but does not define the
rules for what appears underneath that place, either as additional rules for what appears underneath that place, either as additional
underscored naming or as a leaf node with resource records. Details underscored naming or as a leaf node with resource records. Details
for those rules are provided by specifications for individual for those rules are provided by specifications for individual
RRTYPEs. The sections below describe the way that existing RRTYPEs. The sections below describe the way that existing
underscore labels are used with the RRTYPEs that they name. underscore labels are used with the RRTYPEs that they name.
2.1. TXT RRset Use 2.1. TXT RRset Use
This section provides a generic approach for changes to existing This section provides a generic approach for changes to existing
specifications that define straightforward use of _underscored node specifications that define straightforward use of underscored node
names, when scoping the use of a "TXT" RR. The approach provides the names, when scoping the use of a "TXT" RRset. The approach provides
information needed for adapting such specifications to the use of the the information needed for adapting such specifications to the use of
IANA DNS Underscore Global Scoped Entry Registry [Attrleaf]. Hence the IANA DNS Underscore Global Scoped Entry Registry [Attrleaf].
the approach is meant both as an update to these existing Hence the approach is meant both as an update to these existing
specifications, and as guidance for changes when those documents are specifications, and as guidance for changes when those documents are
revised. revised.
For any document that specifies the use of a "TXT" RRset under an For any document that specifies the use of a "TXT" RRset under one or
underscored name, that name is expected to be registered in the IANA more underscored names, that 'global' name is expected to be
DNS Underscore Global Scoped Entry Registry [Attrleaf]. An effort registered in the IANA DNS Underscore Global Scoped Entry Registry
has been made to locate existing drafts that do this, register the [Attrleaf]. An effort has been made to locate existing drafts that
global underscored name, and list them in this document. do this, register the global underscored names, and list them in this
document.
If a public specification that defines use of a "TXT" record within If a public specification that defines use of a "TXT" calls for the
an underscore-scoped name is revised, it MUST add an entry to the use of an underscore-prefixed domain name, the global underscored
global underscored name registry, if one does not already exist. name -- the one closest to the root -- MUST be entered into this
registry, if it is not already registered.
Here is a template of suggested text for this to appear in the IANA Here is a template of suggested text for this to appear in the IANA
Considerations section of the specification: Considerations section of the specification:
"Per" [Attrleaf] "please add the following entry to the DNS "Per" [Attrleaf] "please add the following entry to the DNS
Underscore Global Scoped Entry Registry:" Underscore Global Scoped Entry Registry:"
+--------+----------------+-----------------------------------------+ +--------+----------------+-----------------------------------------+
| RR | _NODE NAME | REFERENCE | | RR | _NODE NAME | REFERENCE |
| Type | | | | Type | | |
+--------+----------------+-----------------------------------------+ +--------+----------------+-----------------------------------------+
| TXT | _{DNS node | {citation for the document making the | | TXT | _{DNS node | {citation for the document making the |
| | name} | addition.} | | | name} | addition.} |
+--------+----------------+-----------------------------------------+ +--------+----------------+-----------------------------------------+
Table 1: Underscore Global Registry Entry Table 1: Underscore Global Registry Entry
2.2. SRV RRset Use 2.2. SRV RRset Use
Specification for the SRV [RFC2782] resource record provides a Specification for the SRV [RFC2782] resource record provides a
template for use of underscored node names. The global (right-most) template for use of underscored node names. The global name is
name, is characterised as naming the 'protocol' that is associated characterised as referencing the 'protocol' that is associated with
with "SRV" RR usage. "SRV" RRset usage.
This section provides a generic approach for changes to existing This section provides a generic approach for changes to existing
specifications that define the use of an "SRV" RR. The approach specifications that define the use of an "SRV" RRset. The approach
provides the information needed for adapting such specifications to provides the information needed for adapting such specifications to
the use of the IANA DNS Underscore Global Scoped Entry Registry the use of the IANA DNS Underscore Global Scoped Entry Registry
[Attrleaf]. Hence the approach is meant both as an update to these [Attrleaf]. Hence the approach is meant both as an update to these
existing specifications, and as guidance for changes when those existing specifications, and as guidance for changes when those
documents are revised. documents are revised.
For any document that specifies the use of a "SRV" RRset, the global For any document that specifies the use of an "SRV" RRset, the global
('protocol', right-most) underscored name is expected to be ('protocol') underscored name is expected to be registered in the
registered in the IANA DNS Underscore Global Scoped Entry Registry IANA DNS Underscore Global Scoped Entry Registry [Attrleaf]. An
[Attrleaf]. An effort has been made to locate existing drafts that effort has been made to locate existing drafts that do this, register
do this, register the global underscored name, and list them in this the global underscored names, and list them in this document.
document.
If a public specification that defines use of an "SRV" record is If a public specification that defines use of a "SRV" calls for the
revised, and the right-most underscored name above the record is not use of an underscore-prefixed domain name, the global underscored
already registered, an entry for the name MUST be added to the global name -- the one closest to the root -- MUST be entered into this
underscored name registry. registry, if it is not already registered.
Here is a template of suggested text for this to appear in the IANA Here is a template of suggested text for this to appear in the IANA
Considerations section of the specification: Considerations section of the specification:
"Per" [Attrleaf] "please add the following entry to the DNS "Per" [Attrleaf] "please add the following entry to the DNS
Underscore Global Scoped Entry Registry:" Underscore Global Scoped Entry Registry:"
+--------+----------------------+-----------------------------------+ +--------+----------------------+-----------------------------------+
| RR | _NODE NAME | REFERENCE | | RR | _NODE NAME | REFERENCE |
| Type | | | | Type | | |
+--------+----------------------+-----------------------------------+ +--------+----------------------+-----------------------------------+
| SRV | _{DNS 'protocol' | {citation for the document making | | SRV | _{DNS 'protocol' | {citation for the document making |
| | node name} | the addition.} | | | node name} | the addition.} |
+--------+----------------------+-----------------------------------+ +--------+----------------------+-----------------------------------+
Table 2: Underscore Global Registry Entry Table 2: Underscore Global Registry Entry
2.3. URI RRset Use 2.3. URI RRset Use
Specification for the URI [RFC7553] resource record provides a Specification for the URI [RFC7553] resource record provides a
template for use of underscored node names. The global (right-most) template for use of underscored node names. The global name is
name, is characterised as naming the 'protocol' that is associated characterised as naming the 'protocol' that is associated with "URI"
with "URI" RR usage or by reversing an Enumservice sequence. RR usage or by reversing an Enumservice sequence [RFC6117].
This section provides a generic approach for changes to existing This section provides a generic approach for changes to existing
specifications that define use of a "URI" RRset. The approach specifications that define use of a "URI" RRset. The approach
provides the information needed for adapting such specifications to provides the information needed for adapting such specifications to
the use of the IANA DNS Underscore Global Scoped Entry Registry the use of the IANA DNS Underscore Global Scoped Entry Registry
[Attrleaf]. Hence the approach is meant both as an update to these [Attrleaf]. Hence the approach is meant both as an update to these
existing specifications, and as guidance for changes when those existing specifications, and as guidance for changes when those
documents are revised. documents are revised.
For any RFC that specifies the use of a "URI" RR, the global For any document that specifies the use of a "URI" RRset, the global
('protocol' or right-most enumservice) underscored name is expected ('protocol' or highest-level enumservice) underscored name is
to be registered in the IANA DNS Underscore Global Scoped Entry expected to be registered in the IANA DNS Underscore Global Scoped
Registry [Attrleaf]. An effort has been made to locate existing Entry Registry [Attrleaf]. An effort has been made to locate
drafts that do this and register the associated 'protocol' name. existing drafts that do this and register the associated 'protocol'
names.
If a public specification that defines use of a "URI" record is If a public specification that defines use of a "URI" calls for the
revised, when the right-most underscored name used by it is not use of an underscore-prefixed domain name, the global underscored
already registered, an entry for the name MUST be added to the global name -- the one closest to the root -- MUST be entered into this
underscored name registry. registry, if it is not already registered.
Here is a template of suggested text for this to appear in the IANA Here is a template of suggested text for this to appear in the IANA
Considerations section of the specification: Considerations section of the specification:
"Per" [Attrleaf] "please add the following entry to the DNS "Per" [Attrleaf] "please add the following entry to the DNS
Underscore Global Scoped Entry Registry:" Underscore Global Scoped Entry Registry:"
+-------+---------------------------+-------------------------------+ +-------+---------------------------+-------------------------------+
| RR | _NODE NAME | REFERENCE | | RR | _NODE NAME | REFERENCE |
| Type | | | | Type | | |
skipping to change at page 6, line 19 skipping to change at page 6, line 22
| URI | _{DNS 'protocol' or | {citation for the document | | URI | _{DNS 'protocol' or | {citation for the document |
| | Enumservice node name} | making the addition.} | | | Enumservice node name} | making the addition.} |
+-------+---------------------------+-------------------------------+ +-------+---------------------------+-------------------------------+
Table 3: Underscore Global Registry Entry Table 3: Underscore Global Registry Entry
3. Underscored Template Specifications 3. Underscored Template Specifications
3.1. SRV Specification Changes 3.1. SRV Specification Changes
The specification for a domain name under which an SRV [RFC2782] The specification for a domain name under, which an SRV [RFC2782]
resource record appears provides a template for use of underscored resource record appears, provides a template for use of underscored
node names. The global (right-most) underscored name, is node names. The global underscored name, is characterised as
characterised as indicating the 'protocol' that is associated with indicating the 'protocol' that is associated with "SRV" RR usage.
"SRV" RR usage.
The text of that existing specification is hereby updated from: The text of that existing specification is hereby updated from:
The format of the SRV RR The format of the SRV RR
Here is the format of the SRV RR, whose DNS type code is 33: Here is the format of the SRV RR, whose DNS type code is 33:
_Service._Proto.Name TTL Class SRV Priority Weight Port Target _Service._Proto.Name TTL Class SRV Priority Weight Port Target
... ...
Proto Proto
The symbolic name of the desired protocol, with an underscore The symbolic name of the desired protocol, with an underscore
skipping to change at page 7, line 12 skipping to change at page 7, line 12
Here is the format of the SRV RR, whose DNS type code is 33: Here is the format of the SRV RR, whose DNS type code is 33:
"_Service._Proto.Name TTL Class SRV Priority Weight Port "_Service._Proto.Name TTL Class SRV Priority Weight Port
Target" _..._ Target" _..._
Proto Proto
The symbolic name of the desired protocol, with an The symbolic name of the desired protocol, with an
underscore (_) prepended to prevent collisions with DNS underscore (_) prepended to prevent collisions with DNS
labels that occur in nature. _tcp and _udp are at present labels that occur in nature. _TCP and _UDP are at present
the most useful values for this field. The Proto is case the most useful values for this field. The Proto is case
insensitive. insensitive.
The SRV RRset protocol (global, right-most) underscored name The SRV RRset protocol (global) underscored name SHOULD be
SHOULD be registered in the IANA DNS Underscore Global registered in the IANA DNS Underscore Global Scoped Entry
Scoped Entry Registry [Attrleaf]. Registry [Attrleaf].
3.2. URI Specification Changes 3.2. URI Specification Changes
Specification for the domain name under which a URI [RFC7553] Specification for the domain name under which a URI [RFC7553]
resource record occurs is similar to that for the SRV [RFC2782] resource record occurs is similar to that for the SRV [RFC2782]
resource record, although the text refers only to 'service' name, resource record, although the text refers only to 'service' name,
rather than distinguishing 'service' from 'protocol'. Further, the rather than distinguishing 'service' from 'protocol'. Further, the
URI RR specification permits alternative underscored naming schemes: URI RR specification permits alternative underscored naming schemes:
One matches what is used for "SRV", with the global (right-most) One matches what is used for "SRV", with the global underscored
underscored name calls "protocol'. name called "protocol'.
The other is based on a reversing of an Enumservice [RFC6117] The other is based on a reversing of an Enumservice [RFC6117]
sequence. sequence.
The text of the existing specification is hereby updated from: The text of the existing specification is hereby updated from:
4.1. Owner Name, Class, and Type 4.1. Owner Name, Class, and Type
The URI owner name is subject to special conventions. The URI owner name is subject to special conventions.
skipping to change at page 8, line 38 skipping to change at page 8, line 38
with Service Name "A" and Transport Protocol "B" for host with Service Name "A" and Transport Protocol "B" for host
example.com. Then we would query for example.com. Then we would query for
(QNAME,QTYPE)=("_A._B.example.com","URI"). (QNAME,QTYPE)=("_A._B.example.com","URI").
And is to be updated to the new text: And is to be updated to the new text:
4.1. Owner Name, Class, and Type 4.1. Owner Name, Class, and Type
The URI owner name is subject to special conventions. The URI owner name is subject to special conventions.
As for the SRV RRset [RFC2782], the URI RRset global (right- As for the SRV RRset [RFC2782], the URI RRset global (highest-
most) underscored name SHOULD be registered in the IANA DNS level) underscored name SHOULD be registered in the IANA DNS
Underscore Global Scoped Entry Registry [Attrleaf]. Underscore Global Scoped Entry Registry [Attrleaf].
Just like the SRV RRset, the URI RRset has service information Just like the SRV RRset, the URI RRset has service information
encoded in its owner name. In order to encode the service for encoded in its owner name. In order to encode the service for
a specific owner name, one uses service parameters. Valid a specific owner name, one uses service parameters. Valid
service parameters are: service parameters are:
+ Those registered by IANA in the "Service Name and Transport + Those registered by IANA in the "Service Name and Transport
Protocol Port Number Registry [RFC6335]" The underscore is Protocol Port Number Registry [RFC6335]" The underscore is
prepended to the service parameters to avoid collisions with prepended to the service parameters to avoid collisions with
DNS labels that occur in nature, and the order is reversed DNS labels that occur in nature, and the order is reversed
to make it possible to do delegations, if needed, to to make it possible to do delegations, if needed, to
different zones (and therefore providers of DNS). different zones (and therefore providers of DNS).
+ Those listed in "Enumservice Registrations [RFC6117]. The + Those listed in "Enumservice Registrations [RFC6117]. The
Enumservice Registration parameters are reversed (i.e., Enumservice Registration parameters are reversed (i.e.,
subtype(s) before type), prepended with an underscore (_), subtype(s) before type), prepended with an underscore (_),
and prepended to the owner name in separate labels. The and prepended to the owner name in separate labels. The
right-most underscored Enumservice name becomes the global highest-level (global) underscored Enumservice name becomes
Attrleaf name to register. the global Attrleaf name to register.
For example, suppose we are looking for the URI for a service For example, suppose we are looking for the URI for a service
with ENUM Service Parameter "A:B:C" for host example.com. Then with ENUM Service Parameter "A:B:C" for host example.com. Then
we would query for we would query for
(QNAME,QTYPE)=("_C._B._A.example.com","URI"). (QNAME,QTYPE)=("_C._B._A.example.com","URI").
As another example, suppose we are looking for the URI for a As another example, suppose we are looking for the URI for a
service with Service Name "A" and Transport Protocol "B" for service with Service Name "A" and Transport Protocol "B" for
host example.com. Then we would query for host example.com. Then we would query for
(QNAME,QTYPE)=("_A._B.example.com","URI"). (QNAME,QTYPE)=("_A._B.example.com","URI").
skipping to change at page 9, line 38 skipping to change at page 9, line 38
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
[Attrleaf] [Attrleaf]
Crocker, D., "DNS Scoped Data Through '_Underscore' Naming Crocker, D., "DNS Scoped Data Through 'Underscore' Naming
of Attribute Leaves", I-D draft-ietf-dnsop-attrleaf, 2018. of Attribute Leaves", I-D draft-ietf-dnsop-attrleaf, 2018.
[RFC6117] Hoeneisen, B., Mayrhofer, A., and J. Livingood, "IANA [RFC6117] Hoeneisen, B., Mayrhofer, A., and J. Livingood, "IANA
Registration of Enumservices: Guide, Template, and IANA Registration of Enumservices: Guide, Template, and IANA
Considerations", RFC 6117, March 2011. Considerations", RFC 6117, March 2011.
[RFC6335] Cotton, M., Eggert, L., Tpuch, J., Westerlund, M., and S. [RFC6335] Cotton, M., Eggert, L., Tpuch, J., Westerlund, M., and S.
Cheshire, "Internet Assigned Numbers Authority (IANA) Cheshire, "Internet Assigned Numbers Authority (IANA)
Procedures for the Management of the Service Name and Procedures for the Management of the Service Name and
Transport Protocol Port Number Registry", RFC 6335, Aug Transport Protocol Port Number Registry", RFC 6335, Aug
skipping to change at page 11, line 36 skipping to change at page 11, line 36
Namespace for the Digital Video Broadcasting Project Namespace for the Digital Video Broadcasting Project
(DVB)", RFC 5328, September 2008. (DVB)", RFC 5328, September 2008.
[RFC5389] Rosenberg, Mahy, Matthews, and Wing, "Session Traversal [RFC5389] Rosenberg, Mahy, Matthews, and Wing, "Session Traversal
Utilities for NAT (STUN)", RFC 5389, October 2008. Utilities for NAT (STUN)", RFC 5389, October 2008.
[RFC5415] Calhoun, P., Ed., Montemurro, M., Ed., and D. Stanley, [RFC5415] Calhoun, P., Ed., Montemurro, M., Ed., and D. Stanley,
Ed., "Control And Provisioning of Wireless Access Points Ed., "Control And Provisioning of Wireless Access Points
(CAPWAP) Protocol Specification", RFC 5415, March 2009. (CAPWAP) Protocol Specification", RFC 5415, March 2009.
[RFC5507] Faltstrom, P., Ed. and R. Austein, Ed., "Design Choices
When Expanding the DNS", RFC 5507, April 2009.
[RFC5509] Loreto, S., "Internet Assigned Numbers Authority (IANA)
Registration of Instant Messaging and Presence DNS SRV RRs
for the Session Initiation Protocol (SIP)", RFC 5509,
April 2009.
[RFC5518] Hoffman, P., Levine, J., and A. Hathcock, "Vouch By [RFC5518] Hoffman, P., Levine, J., and A. Hathcock, "Vouch By
Reference", RFC 5518, April 2009. Reference", RFC 5518, April 2009.
[RFC5555] Soliman, H., Ed., "Mobile IPv6 Support for Dual Stack [RFC5555] Soliman, H., Ed., "Mobile IPv6 Support for Dual Stack
Hosts and Routers", RFC 5555, June 2009. Hosts and Routers", RFC 5555, June 2009.
[RFC5617] Sendmail, Inc., Cisco Systems, Inc., Yahoo! Inc., and [RFC5617] Sendmail, Inc., Cisco Systems, Inc., Yahoo! Inc., and
Taughannock Networks, "DomainKeys Identified Mail (DKIM) Taughannock Networks, "DomainKeys Identified Mail (DKIM)
Author Domain Signing Practices (ADSP)", RFC 5617, August Author Domain Signing Practices (ADSP)", RFC 5617, August
2009. 2009.
skipping to change at page 13, line 7 skipping to change at page 12, line 44
[RFC7208] Kitterman, S., "Sender Policy Framework (SPF) for [RFC7208] Kitterman, S., "Sender Policy Framework (SPF) for
Authorizing Use of Domains in E-Mail, Version 1", Authorizing Use of Domains in E-Mail, Version 1",
RFC 7208, April 2014. RFC 7208, April 2014.
[RFC7489] Kucherawy, M., Ed. and E. Zwicky, Ed., "Domain-based [RFC7489] Kucherawy, M., Ed. and E. Zwicky, Ed., "Domain-based
Message Authentication, Reporting, and Conformance Message Authentication, Reporting, and Conformance
(DMARC)", RFC 7489, March 2015. (DMARC)", RFC 7489, March 2015.
Appendix A. Acknowledgements Appendix A. Acknowledgements
Thanks go to Bill Fenner, Tony Hansen, Peter Koch, Olaf Kolkman, and Thanks go to Bill Fenner, Dick Franks, Tony Hansen, Peter Koch, Olaf
Andrew Sullivan for diligent review of the (much) earlier drafts. Kolkman, and Andrew Sullivan for diligent review of the (much)
For the later enhancements, thanks to: Tim Wicinski, John Levine, Bob earlier drafts. For the later enhancements, thanks to: Tim Wicinski,
Harold, Joel Jaeggli, Ondřej Sury and Paul Wouters. John Levine, Bob Harold, Joel Jaeggli, Ondřej Sury and Paul
Wouters.
Special thanks to Ray Bellis for more than 10 years of persistent Special thanks to Ray Bellis for his persistent encouragement to
encouragement to continue this effort, as well as the suggestion for continue this effort, as well as the suggestion for an essential
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
USA USA
Phone: +1.408.246.8253 Phone: +1.408.246.8253
 End of changes. 35 change blocks. 
99 lines changed or deleted 96 lines changed or added

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