Network Working Group J. Levine Internet-Draft Taughannock Networks Updates: 2606 (if approved) December 29, 2009 Intended status: Standards Track Expires: July 2, 2010 Reserved and Special Names Registry draft-levine-reserved-names-registry-00 Abstract Within the Domain Name System, several names have been reserved or used for special purposes, some at the top level and some at other levels. RFC 2606 identified An IANA registry of Reserved and Special Names is established to reduce the likelihood of conflict of names and the consequent ambiguity. This specification establishes that registry. Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on July 2, 2010. Copyright Notice Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Levine Expires July 2, 2010 [Page 1] Internet-Draft Reserved and Special Names Registry December 2009 Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Discussion List . . . . . . . . . . . . . . . . . . . . . . 3 2. Registry Definition . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Registry Name . . . . . . . . . . . . . . . . . . . . . . . 3 2.2. Registry Format . . . . . . . . . . . . . . . . . . . . . . 3 2.3. Criteria for Registration . . . . . . . . . . . . . . . . . 4 2.4. Initial Contents of Registry . . . . . . . . . . . . . . . 4 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 5.1. Normative References . . . . . . . . . . . . . . . . . . . 6 5.2. Informative References . . . . . . . . . . . . . . . . . . 7 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 7 Levine Expires July 2, 2010 [Page 2] Internet-Draft Reserved and Special Names Registry December 2009 1. Introduction The Domain Name System[RFC1034] [RFC1035] provides a tree-structured name space with subtrees delegated to different organizations for management. Other than the root, usually written as ".", no name has characteristics technically different from any other. Nevertheless, some names in the DNS have historically been reserved for specific purposes, and have not been made available for delegation. Other names do appear within delegated subtrees, but have by convention had a specialized interpretation. The specialized and reserved names have hitherto been identified in a variety of documents but never listed in one place. This document creates a registry for these reserved and specialized names. This document does _not_ attempt to describe rules or practices for delegation of subtrees of the DNS. 1.1. Discussion List [[ RFC Editor: please remove this section before publication. ]] Until and unless a WG is created, this proposal will be discussed on the list ietf@ietf.org 2. Registry Definition 2.1. Registry Name The recommended name of this registry is "DNS Reserved and Special Names". 2.2. Registry Format IANA is requested to establish a registry for DNS reserved and special names. Registration requests and registry entries should include the following: Name - The reserved or special name. Category - Reserved, for names not intended to be used on the public Internet, or Special, for names intended to be used in specified ways. Level - The level in the DNS where this name is reserved, or special, at the top level of the DNS, in a leaf name, or at any level. Levine Expires July 2, 2010 [Page 3] Internet-Draft Reserved and Special Names Registry December 2009 Description - A brief description of the name and, where appropriate, its usage. Reference - A reference to an RFC or other definition of the name. 2.3. Criteria for Registration This registry is intended to collect reserved and special names defined in RFCs. For reserved or special names defined at any particular point in the DNS namespace, the organization managing that point in the namespace must also concur such as ICANN or its successor for the top level. 2.4. Initial Contents of Registry As a service to users of the registry and the authors of existing specifications, all currently known reserved and special names are to be included into the registry upon creation. +-------------+-----+-------+--------------------+------------------+ | Name | Cat | Level | Description | RFC#s/References | | | | | | and Notes | +-------------+-----+-------+--------------------+------------------+ | TEST | R | Top | Reserved for | [RFC2606] | | | | | testing | | | EXAMPLE | R | Top | Examples for | [RFC2606] | | | | | documentation | | | INVALID | R | Top | Names known to be | [RFC2606] | | | | | invalid | | | LOCALHOST | R | Top | Name for loopback | [RFC2606] | | | | | address | | | EXAMPLE.COM | R | Top | Examples for | [RFC2606] | | | | | documentation | | | EXAMPLE.NET | R | Top | Examples for | [RFC2606] | | | | | documentation | | | EXAMPLE.ORG | R | Top | Examples for | [RFC2606] | | | | | documentation | | | INADDR.ARPA | R | Top | IPv4 inverse name | [RFC1034] | | | | | lookup | | | IP6.ARPA | R | Top | IPv6 inverse name | [RFC3596] | | | | | lookup | | | E164.ARPA | R | Top | ENUM E.164 numbers | [RFC3026] | | URI.ARPA | R | Top | DDDS URI | [RFC3405] | | | | | resolution | | | URN.ARPA | R | Top | DDDS URN | [RFC3406] | | | | | resolution | | | IRIS.ARPA | R | Top | IRIS address | [RFC4698] | | | | | registries | | Levine Expires July 2, 2010 [Page 4] Internet-Draft Reserved and Special Names Registry December 2009 | _service | S | Leaf | SRV service names | [RFC2782](#1) | | _proto | S | (#2) | SRV protocol names | [RFC2782](#3) | | _domainkey | S | Any | DKIM signature | [RFC4871] | | | | | verification keys | | | _adsp | S | Leaf | DKIM ADSP policy | [RFC5617] | | | | | records | | | _vouch | S | Any | VBR certification | [RFC5518] | | | | | records | | +-------------+-----+-------+--------------------+------------------+ Table 1 Notes: Cat Category: R is Reserved, S is Special Level Level: Top is Top Level, Leaf is Leaf names only, Any is Anywhere other than the top level. #1 "_service" means the name of any service, preceded by an underscore, such as _LDAP. #2 This name appears as the penultimate name of a SRV record, where the leaf name is a "_service" name, or as a leaf name. #3 "_protocol" means the name of any protocol, preceded by an underscore, such as _TCP. RFC 3861 [RFC3861] created the "Instant Messaging SRV Protocol Label Registry" for protocols used in Instant Messaging. 3. IANA Considerations IANA is requested to establish the registry described in Section 2 using the initial content specified in Section 2.4. New entries should be added to this registry when defined in an RFC and, if required, the relevant manager for the position in the DNS concurs. See Section 2.3 for specifics. 4. Security Considerations The creation of this registry provides improved documentation and protection against interoperability problems. It introduces no new security issues. Levine Expires July 2, 2010 [Page 5] Internet-Draft Reserved and Special Names Registry December 2009 5. References 5.1. Normative References [RFC1034] Mockapetris, P., "Domain names - concepts and facilities", STD 13, RFC 1034, November 1987. [RFC1035] Mockapetris, P., "Domain names - implementation and specification", STD 13, RFC 1035, November 1987. [RFC2606] Eastlake, D. and A. Panitz, "Reserved Top Level DNS Names", BCP 32, RFC 2606, June 1999. [RFC2782] Gulbrandsen, A., Vixie, P., and L. Esibov, "A DNS RR for specifying the location of services (DNS SRV)", RFC 2782, February 2000. [RFC3026] Blane, R., "Liaison to IETF/ISOC on ENUM", RFC 3026, January 2001. [RFC3405] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part Five: URI.ARPA Assignment Procedures", BCP 65, RFC 3405, October 2002. [RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, "Uniform Resource Names (URN) Namespace Definition Mechanisms", BCP 66, RFC 3406, October 2002. [RFC3596] Thomson, S., Huitema, C., Ksinant, V., and M. Souissi, "DNS Extensions to Support IP Version 6", RFC 3596, October 2003. [RFC3861] Peterson, J., "Address Resolution for Instant Messaging and Presence", RFC 3861, August 2004. [RFC4698] Gunduz, E., Newton, A., and S. Kerr, "IRIS: An Address Registry (areg) Type for the Internet Registry Information Service", RFC 4698, October 2006. [RFC4871] Allman, E., Callas, J., Delany, M., Libbey, M., Fenton, J., and M. Thomas, "DomainKeys Identified Mail (DKIM) Signatures", RFC 4871, May 2007. [RFC5518] Hoffman, P., Levine, J., and A. Hathcock, "Vouch By Reference", RFC 5518, April 2009. [RFC5617] Allman, E., Fenton, J., Delany, M., and J. Levine, "DomainKeys Identified Mail (DKIM) Author Domain Signing Levine Expires July 2, 2010 [Page 6] Internet-Draft Reserved and Special Names Registry December 2009 Practices (ADSP)", RFC 5617, August 2009. 5.2. Informative References [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008. Author's Address John R. Levine Taughannock Networks PO Box 727 Trumansburg, NY 14886 Email: standards@taugh.com Levine Expires July 2, 2010 [Page 7]