draft-ietf-dnsop-attrleaf-12.txt   draft-ietf-dnsop-attrleaf-13.txt 
dnsop D. Crocker dnsop D. Crocker
Internet-Draft Brandenburg InternetWorking Internet-Draft Brandenburg InternetWorking
Intended status: Best Current Practice July 21, 2018 Intended status: Best Current Practice August 21, 2018
Expires: January 22, 2019 Expires: February 22, 2019
DNS Scoped Data Through "Underscore" Naming of Attribute Leaves DNS Scoped Data Through "Underscore" Naming of Attribute Leaves
draft-ietf-dnsop-attrleaf-12 draft-ietf-dnsop-attrleaf-13
Abstract Abstract
Formally, any DNS resource record may occur under any domain name. Formally, any DNS resource record may occur under 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
underscored naming construct defines a semantic scope for DNS record underscored 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 1, line 40 skipping to change at page 1, line 40
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 January 22, 2019. This Internet-Draft will expire on February 22, 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 24 skipping to change at page 2, line 24
1.1. Underscore Scoping . . . . . . . . . . . . . . . . . . . 3 1.1. Underscore Scoping . . . . . . . . . . . . . . . . . . . 3
1.2. Scaling Benefits . . . . . . . . . . . . . . . . . . . . 4 1.2. Scaling Benefits . . . . . . . . . . . . . . . . . . . . 4
1.3. "Global" Underscored Node Names . . . . . . . . . . . . . 4 1.3. "Global" Underscored Node Names . . . . . . . . . . . . . 4
1.4. Interaction with DNS wildcards . . . . . . . . . . . . . 5 1.4. Interaction with DNS wildcards . . . . . . . . . . . . . 5
2. DNS Underscore Scoped Entry Registries Function . . . . . . . 5 2. DNS Underscore Scoped Entry Registries Function . . . . . . . 5
3. RRset Use Registration Template . . . . . . . . . . . . . . . 6 3. RRset Use Registration Template . . . . . . . . . . . . . . . 6
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
4.1. DNS Underscore Global Scoped Entry Registry . . . . . . . 7 4.1. DNS Underscore Global Scoped Entry Registry . . . . . . . 7
4.2. DNS Underscore Global Scoped Entry Registry Definition . 7 4.2. DNS Underscore Global Scoped Entry Registry Definition . 7
4.3. Initial entries . . . . . . . . . . . . . . . . . . . . . 8 4.3. Initial entries . . . . . . . . . . . . . . . . . . . . . 8
5. Guidance for Expert Review . . . . . . . . . . . . . . . . . 10 5. Guidance for Expert Review . . . . . . . . . . . . . . . . . 9
6. Security Considerations . . . . . . . . . . . . . . . . . . . 10 6. Security Considerations . . . . . . . . . . . . . . . . . . . 10
6.1. Interaction with DNS wildcards . . . . . . . . . . . . . 10
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
7.1. Normative References . . . . . . . . . . . . . . . . . . 11 7.1. Normative References . . . . . . . . . . . . . . . . . . 10
7.2. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 12 7.2. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 12 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 12
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 12 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 12
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
skipping to change at page 5, line 30 skipping to change at page 5, line 30
A registry for "global" DNS nodes names that begin with an underscore A registry for "global" DNS nodes names that begin with an underscore
is defined here. The purpose of the Underscore Global Registry is to is defined here. The purpose of the Underscore Global Registry is to
avoid collisions resulting from the use of the same underscore-based avoid collisions resulting from the use of the same underscore-based
name, for different applications. name, for different applications.
o If a public specification calls for use of an underscore-prefixed o If a public specification calls for use of an underscore-prefixed
domain node name, the "global" underscored name -- the underscored domain node name, the "global" underscored name -- the underscored
name that is closest to the DNS root -- MUST be entered into this name that is closest to the DNS root -- MUST be entered into this
registry. registry.
An underscored name defines scope of use for specific resource record An underscored name defines the scope of use for specific resource
types, which are associated with the domain name that is the "parent" record types, which are associated with the domain name that is the
to the branch defined by the underscored name. A given name defines "parent" to the branch defined by the underscored name. A given name
a specific, constrained context for one or more RR types, where use defines a specific, constrained context for one or more RR types,
of such record types conforms to the defined constraints. where use of such record types conforms to the defined constraints.
o Within an underscore scoped leaf, other RRsets that are not o Within an underscore scoped leaf, 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 re-use of a subordinate underscored name in a reasonable to allow re-use 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 name. meaningful only within the scope of the global underscored name.
Therefore they are ignored by this DNS Underscore Global Scoped Entry Therefore they are ignored by this DNS Underscore Global Scoped Entry
Registry. This registry is for the definition of highest-level -- Registry. This registry is for the definition of highest-level --
ie, global -- underscored node name used. ie, 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 |
+----------------------------+ +----------------------------+
Examples of Underscored Names Examples of Underscored Names
Only global underscored names are registered in the IANA Underscore Only global underscored names are registered in the IANA Underscore
Global table. Global table.
skipping to change at page 8, line 11 skipping to change at page 8, line 11
4.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, 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 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; for characters in the name that have an upper-case
form and a lower-case form, the character MUST be recorded
as lower-case, to simply name comparisons.
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.
4.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] | | NULL | _ta-* {see note} | [RFC8145] |
| SMIMEA | _smimecert | [RFC8162] | | OPENPGPKEY | _openpgpkey | [RFC7929] |
| SRV | _dccp | [RFC2782] | | SMIMEA | _smimecert | [RFC8162] |
| SRV | _sctp | [RFC2782] | | SRV | _dccp | [RFC2782] |
| SRV | _tcp | [RFC2782] | | SRV | _ipv6 | [RFC5026] |
| SRV | _udp | [RFC2782] | | SRV | _sip | [RFC5509] |
| TLSA | _sctp | [RFC6698] | | SRV | _sctp | [RFC2782] |
| TLSA | _tcp | [RFC6698] | | SRV | _tcp | [RFC2782] |
| TLSA | _udp | [RFC6698] | | SRV | _tls | [RFC6733] |
| TXT | _mta-sts | [MTA-STS] | | SRV | _udp | [RFC2782] |
| TXT | _acme-challenge | [ACME] | | SRV | _xmpp | [RFC3921] |
| TXT | _dmarc | [RFC7489] | | TLSA | _dane | [RFC7671] |
| TXT | _domainkey | [RFC6376] | | TLSA | _sctp | [RFC6698] |
| TXT | _spf | [RFC7208] | | TLSA | _tcp | [RFC6698] |
| TXT | _vouch | [RFC5518] | | TLSA | _udp | [RFC6698] |
| URI | _iax | [RFC7553] | | TXT | _mta-sts | [MTA-STS] |
| URI | _acct | [RFC7553] | | TXT | _acme-challenge | [ACME] |
| URI | _dccp | [RFC7553] | | TXT | _dmarc | [RFC7489] |
| URI | _email | [RFC7553] | | TXT | _domainkey | [RFC6376] |
| URI | _ems | [RFC7553] | | TXT | _spf | [RFC7208] |
| URI | _fax | [RFC7553] | | TXT | _vouch | [RFC5518] |
| URI | _ft | [RFC7553] | | URI | _iax | [RFC7553] |
| URI | _h323 | [RFC7553] | | URI | _acct | [RFC7553] |
| URI | _ical-sched | [RFC7553] | | URI | _dccp | [RFC7553] |
| URI | _ical-access | [RFC7553] | | URI | _email | [RFC7553] |
| URI | _ifax | [RFC7553] | | URI | _ems | [RFC7553] |
| URI | _im | [RFC7553] | | URI | _fax | [RFC7553] |
| URI | _mms | [RFC7553] | | URI | _ft | [RFC7553] |
| URI | _pres | [RFC7553] | | URI | _h323 | [RFC7553] |
| URI | _pstn | [RFC7553] | | URI | _ical-sched | [RFC7553] |
| URI | _sctp | [RFC7553] | | URI | _ical-access | [RFC7553] |
| URI | _sip | [RFC7553] | | URI | _ifax | [RFC7553] |
| URI | _sms | [RFC7553] | | URI | _im | [RFC7553] |
| URI | _tcp | [RFC7553] | | URI | _mms | [RFC7553] |
| URI | _udp | [RFC7553] | | URI | _pres | [RFC7553] |
| URI | _unifmsg | [RFC7553] | | URI | _pstn | [RFC7553] |
| URI | _vcard | [RFC7553] | | URI | _sctp | [RFC7553] |
| URI | _videomsg | [RFC7553] | | URI | _sip | [RFC7553] |
| URI | _voice | [RFC7553] | | URI | _sms | [RFC7553] |
| URI | _voicemsg | [RFC7553] | | URI | _tcp | [RFC7553] |
| URI | _vpim | [RFC7553] | | URI | _udp | [RFC7553] |
| URI | _xmp | [RFC7553] | | URI | _unifmsg | [RFC7553] |
+------------+-----------------+------------+ | URI | _vcard | [RFC7553] |
| URI | _videomsg | [RFC7553] |
| URI | _voice | [RFC7553] |
| URI | _voicemsg | [RFC7553] |
| URI | _vpim | [RFC7553] |
| URI | _xmp | [RFC7553] |
+------------+------------------+------------+
Table 2: Underscore Global Registry (initial entries) Table 2: Underscore Global Registry (initial entries)
NOTE: Under the NULL RR, the entry "_ta-*" is meant to denote all
node names beginning with the string "_ta-". It does NOT refer to
a DNS wildcard specification.
5. 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
skipping to change at page 10, line 34 skipping to change at page 10, line 17
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.
6. Security Considerations 6. Security Considerations
This memo raises no security issues. This memo raises no security issues.
6.1. Interaction with DNS wildcards
DNS wildcards interact poorly with underscored names in two ways.
Since wildcards only are interpreted as leaf names, one cannot create
the equivalent of a wildcard name for prefixed names. A name such as
label.*.example.com is not a wildcard.
Conversely, a wildcard such as *.example.com can match any name
including an underscored name. So, a wildcard might match an
underscored name, returning a record that is the type controlled by
the underscored name but is not intended to be used in the
underscored context and does not conform to its rules.
7. References 7. References
7.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.
skipping to change at page 11, line 34 skipping to change at page 10, line 49
[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, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2181] Elz, R. and R. Bush, "Clarifications to the DNS [RFC2181] Elz, R. and R. Bush, "Clarifications to the DNS
Specification", RFC 2181, July 1997. Specification", RFC 2181, July 1997.
[RFC2782] Gulbrandsen, A., Vixie, P., and L. Esibov, "A DNS RR for [RFC2782] Gulbrandsen, A., Vixie, P., and L. Esibov, "A DNS RR for
specifying the location of services (DNS SRV)", RFC 2782, specifying the location of services (DNS SRV)", RFC 2782,
February 2000. February 2000.
[RFC3921] Saint-Andre, P., Ed., "Extensible Messaging and Presence
Protocol (XMPP): Instant Messaging and Presence",
RFC 3921, DOI 10.17487/RFC3921, October 2004,
<https://www.rfc-editor.org/info/rfc3921>.
[RFC5026] Giaretta, G., Ed., Kempf, J., and V. Devarapalli, Ed.,
"Mobile IPv6 Bootstrapping in Split Scenario", RFC 5026,
DOI 10.17487/RFC5026, October 2007,
<https://www.rfc-editor.org/info/rfc5026>.
[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,
DOI 10.17487/RFC5509, April 2009,
<https://www.rfc-editor.org/info/rfc5509>.
[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.
[RFC6335] Cotton, M., Eggert, L., Tpuch, J., Westerlund, M., and S. [RFC6335] Cotton, M., Eggert, L., Tpuch, J., Westerlund, M., and S.
Cheshire, "nternet Assigned Numbers Authority (IANA) Cheshire, "nternet 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
2011. 2011.
[RFC6376] Crocker, D., Hansen, T., and M. Kucherawy, "DomainKeys [RFC6376] Crocker, D., Hansen, T., and M. Kucherawy, "DomainKeys
Identified Mail (DKIM) Signatures", RFC 6376, Sept 2011. Identified Mail (DKIM) Signatures", RFC 6376, Sept 2011.
[RFC6698] Hoffman, J. and J. Schlyter, "The DNS-Based Authentication [RFC6698] Hoffman, J. and J. Schlyter, "The DNS-Based Authentication
of Named Entities (DANE) Transport Layer Security (TLS) of Named Entities (DANE) Transport Layer Security (TLS)
Protocol: TLSA", RFC 6698, August . Protocol: TLSA", RFC 6698, August .
[RFC6733] Fajardo, V., Ed., Arkko, J., Loughney, J., and G. Zorn,
Ed., "Diameter Base Protocol", RFC 6733,
DOI 10.17487/RFC6733, October 2012,
<https://www.rfc-editor.org/info/rfc6733>.
[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.
[RFC7553] Falstrom, P. and O. Kolkman, "The Uniform Resource [RFC7553] Falstrom, P. and O. Kolkman, "The Uniform Resource
Identifier (URI) DNS Resource Record", RFC 7553, Identifier (URI) DNS Resource Record", RFC 7553,
ISSN 2070-1721, June 2015. ISSN 2070-1721, June 2015.
[RFC7671] Dukhovni, V. and W. Hardaker, "The DNS-Based
Authentication of Named Entities (DANE) Protocol: Updates
and Operational Guidance", RFC 7671, DOI 10.17487/RFC7671,
October 2015, <https://www.rfc-editor.org/info/rfc7671>.
[RFC7929] Wouters, P., , RFC 7929, August 2016. [RFC7929] Wouters, P., , RFC 7929, August 2016.
[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for [RFC8126] Cotton, M., Leiba, B., 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.
[RFC8145] Wessels, D., Kumari, W., and P. Hoffman, "Signaling Trust
Anchor Knowledge in DNS Security Extensions (DNSSEC)",
RFC 8145, April 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.
7.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, Dick Franks, Tony Hansen, Martin Hoffmann, Thanks go to Bill Fenner, Dick Franks, Tony Hansen, Martin Hoffmann,
Peter Koch, Olaf Kolkman, and Andrew Sullivan for diligent review of Paul Hoffman, Peter Koch, Olaf Kolkman, Murray Kucherawy, John
Levine, Benno Overeinder, and Andrew Sullivan for diligent review of
the (much) earlier drafts. For the later enhancements, thanks to: the (much) earlier drafts. For the later enhancements, thanks to:
Stephane Bortzmeyer, Bob Harold, Warren Kumari, John Levine, Joel Stephane Bortzmeyer, Bob Harold, Warren Kumari, John Levine, Joel
Jaeggli, Petr &#352;pa&#269;ek, Ond&#345;ej Sur&#345;, Paul Vixie, Jaeggli, Petr &#352;pa&#269;ek, Ond&#345;ej Sury, Paul Vixie, Tim
Tim Wicinski, and Paul Wouters. Wicinski, and Paul Wouters.
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
USA USA
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. 20 change blocks. 
76 lines changed or deleted 107 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/