draft-ietf-dnsop-attrleaf-00.txt   draft-ietf-dnsop-attrleaf-01.txt 
Network Working Group D. Crocker Network Working Group D. Crocker
Internet-Draft Brandenburg InternetWorking Internet-Draft Brandenburg InternetWorking
Intended status: Best Current Practice March 14, 2016 Intended status: Best Current Practice March 5, 2017
Expires: September 15, 2016 Expires: September 6, 2017
DNS Scoped Data Through '_Underscore' Attribute Leaves DNS Scoped Data Through '_Underscore' Attribute Leaves
draft-ietf-dnsop-attrleaf-00 draft-ietf-dnsop-attrleaf-01
Abstract Abstract
Historically, any DNS RR may occur for any domain name. Recent Historically, any DNS RR may occur for any domain name. Recent
additions have defined DNS leaf nodes that contain a reserved node additions have defined DNS leaf nodes that contain a reserved node
name, beginning with an underscore. The underscore construct is used name, beginning with an underscore. The underscore construct is used
to define a semantic scope for DNS records that are associated with to define a semantic scope for DNS records that are associated with
the parent domain. This specification explores the nature of this the parent domain. This specification explores the nature of this
DNS usage and defines the "underscore names" registry with IANA. DNS usage and defines the "underscore names" registry with IANA.
skipping to change at page 1, line 35 skipping to change at page 1, line 35
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 September 15, 2016. This Internet-Draft will expire on September 6, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2017 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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
skipping to change at page 2, line 25 skipping to change at page 2, line 25
7. Security Considerations . . . . . . . . . . . . . . . . . . . 9 7. Security Considerations . . . . . . . . . . . . . . . . . . . 9
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
8.1. Normative References . . . . . . . . . . . . . . . . . . 9 8.1. Normative References . . . . . . . . . . . . . . . . . . 9
8.2. References -- Informative . . . . . . . . . . . . . . . . 9 8.2. References -- Informative . . . . . . . . . . . . . . . . 9
8.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 12 8.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 12 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 12
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 12 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction 1. Introduction
** This is merely a re-submission of the -00 version, to re-initiate
discussion. /Dave
The core DNS technical specifications assign no semantics to domain The core DNS technical specifications assign no semantics to domain
names or their parts, and no constraints upon which resource records names or their parts, and no constraints upon which resource records
(RRs) are permitted to be associated with particular names. Over (RRs) are permitted to be associated with particular names. Over
time, some leaf node names, such as "www" and "ftp" have come to time, some leaf node names, such as "www" and "ftp" have come to
imply support for particular services, but this is a matter of imply support for particular services, but this is a matter of
operational convention, rather than defined protocol semantics . operational convention, rather than defined protocol semantics .
This freedom in the basic technology has permitted a wide range of This freedom in the basic technology has permitted a wide range of
administrative and semantic policies to be used -- in parallel. Data administrative and semantic policies to be used -- in parallel. Data
semantics have been limited to the specification of particular semantics have been limited to the specification of particular
resource records, on the expectation that new ones would be added as resource records, on the expectation that new ones would be added as
 End of changes. 5 change blocks. 
5 lines changed or deleted 8 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/