draft-ietf-dnsop-attrleaf-09.txt   draft-ietf-dnsop-attrleaf-10.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 June 5, 2018
Expires: November 23, 2018 Expires: December 7, 2018
DNS Scoped Data Through '_Underscore' Naming of Attribute Leaves DNS Scoped Data Through '_Underscore' Naming of Attribute Leaves
draft-ietf-dnsop-attrleaf-09 draft-ietf-dnsop-attrleaf-10
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 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 November 23, 2018. This Internet-Draft will expire on December 7, 2018.
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 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. RRset Use Registration Template . . . . . . . . . . . . . . . 5 3. RRset Use Registration Template . . . . . . . . . . . . . . . 6
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
4.1. DNS Underscore Global Scoped Entry Registry . . . . . . . 6 4.1. DNS Underscore Global Scoped Entry Registry . . . . . . . 6
4.2. DNS Underscore Global Scoped Entry Registry Definition . 7 4.2. DNS Underscore Global Scoped Entry Registry Definition . 7
4.3. Initial entries . . . . . . . . . . . . . . . . . . . . . 7 4.3. Initial entries . . . . . . . . . . . . . . . . . . . . . 7
5. Guidance for Expert Review . . . . . . . . . . . . . . . . . 9 5. Guidance for Expert Review . . . . . . . . . . . . . . . . . 9
6. Security Considerations . . . . . . . . . . . . . . . . . . . 9 6. Security Considerations . . . . . . . . . . . . . . . . . . . 9
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
7.1. Normative References . . . . . . . . . . . . . . . . . . 9 7.1. Normative References . . . . . . . . . . . . . . . . . . 9
7.2. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 11 7.2. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 11 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 11
skipping to change at page 4, line 11 skipping to change at page 4, line 11
NOTE TO RFC EDITOR: Please remove "Discussion Venue" paragraph NOTE TO RFC EDITOR: Please remove "Discussion Venue" paragraph
prior to publication. prior to publication.
1.2. Scaling Benefits 1.2. Scaling Benefits
Some resource record types are used in a fashion that can create Some resource record types are used in a fashion that can create
scaling problems, if an entire RRset associated with a domain name is scaling problems, if an entire RRset associated with a domain name is
aggregated in the leaf node for that name. An increasingly-popular aggregated in the leaf node for that name. An increasingly-popular
approach, with excellent scaling properties, places the RRset under a approach, with excellent scaling properties, places the RRset under a
node having an underscore-based name, at a defined place in the DNS specially named branch, which is in turn under the node name that
tree under the 'parent' name. This constrains the use of particular would otherwise contain the RRset. The rules for naming that branch
"RR" types associated with that parent name. A direct lookup to the define the context for interpreting the RRset. That is, rather than:
subordinate leaf node produces only the desired record types, at no
greater cost than a typical DNS lookup.
The definition of a underscore global registry, provided in this domain-name.example
/
RRset
the arrangement is:
_branch.domain-name.example
/
RRset
A direct lookup to the subordinate leaf node produces only the
desired record types, at no greater cost than a typical DNS lookup.
The definition of an underscore global registry, provided in this
specification, primarily attends to the top-most names used for specification, primarily attends to the top-most names used for
scoping an RR type; that is the _underscore "global" names. scoping an RR type; that is the _underscore "global" names.
2. DNS Underscore Scoped Entry Registries Function 2. DNS Underscore Scoped Entry Registries Function
A global registry for DNS nodes names that begin with an _underscore A global registry for 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.
 End of changes. 6 change blocks. 
11 lines changed or deleted 22 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/