]> Taughannock Networks

PO Box 727 Trumansburg 14886 NY +1 831 480 2300 standards@taugh.com

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. IANA registries of Reserved and Special Names can reduce the likelihood of conflict of names and the consequent ambiguity. This specification establishes those registries.

The Domain Name System 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 registries for these reserved and specialized names. This document does not attempt to describe rules or practices for delegation of subtrees of the DNS.

[[ 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

The recommended name of this registry is "DNS Reserved and Special Top Level Names".

IANA is requested to establish a registry for names that are reserved and special at the top level of the DNS. Registration requests and registry entries should include the following: The reserved or special name. Reserved, for names not intended to be delegated on the public Internet, or Special, for names intended to be used in specified ways. A brief description of the name and, where appropriate, its usage. A reference to an RFC or other definition of the name.

This registry is intended to collect reserved and special names defined in RFCs and defined by designated managers. For names at the top level, ICANN or its successor as manager must concur with any additions or deletions.

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 Description RFC#s/References and Notes TEST R Reserved for testing (#1) EXAMPLE R Examples for documentation (#1) INVALID R Names known to be invalid LOCALHOST R Name for loopback address LOCAL R Name for loopback address ARPA S Internet infrastructure AFRINIC R Reserved top level domain name ALAC R Reserved top level domain name APNIC R Reserved top level domain name ARIN R Reserved top level domain name ASO R Reserved top level domain name CCNSO R Reserved top level domain name GAC R Reserved top level domain name GNSO R Reserved top level domain name GTLD-SERVERS R Reserved top level domain name IAB R Reserved top level domain name IANA R Reserved top level domain name IANA-SERVERS R Reserved top level domain name ICANN R Reserved top level domain name IESG R Reserved top level domain name IETF R Reserved top level domain name INTERNIC R Reserved top level domain name IRTF R Reserved top level domain name ISTF R Reserved top level domain name LACNIC R Reserved top level domain name LOCAL R Reserved top level domain name NIC R Reserved top level domain name NRO R Reserved top level domain name RFC-EDITOR R Reserved top level domain name RIPE R Reserved top level domain name ROOT-SERVERS R Reserved top level domain name RSSAC R Reserved top level domain name SSAC R Reserved top level domain name TLD R Reserved top level domain name WHOIS R Reserved top level domain name WWW R Reserved top level domain name Notes: Category: R is Reserved, S is Special The ICANN Draft gTLD Applicant Guidebook states in section 2.1.1.2 that "ICANN will reserve translations of the terms 'test' and 'example' in multiple languages."

The recommended name of this registry is "Reserved or Special Second Level Domain Names".

IANA is requested to establish a registry for names that are reserved or special at the second level of the DNS. Registration requests and registry entries should include the following: The reserved or special name. Reserved, for names not intended to be delegated on the public Internet, or Special, for names intended to be used in specified ways. A brief description of the name and, where appropriate, its usage. A reference to an RFC or other definition of the name.

This registry is intended to collect reserved and special names defined in RFCs and defined by designated managers. The manager of the relevant top-level domain must concur with any additions or deletions to entries within that top-level domain.

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 Description RFC#s/References and Notes EXAMPLE.COM R Examples for documentation EXAMPLE.NET R Examples for documentation EXAMPLE.ORG R Examples for documentation Notes: Category: R is Reserved, S is Special

The recommended name of this registry is ".ARPA Domain Names".

IANA is requested to establish a registry for names that are used within the .ARPA internet infrastructure top level domain. Registration requests and registry entries should include the following: The reserved or special name. Reserved, for names not intended to be delegated on the public Internet, or Special, for names intended to be used in specified ways. A brief description of the name and, where appropriate, its usage. A reference to an RFC or other definition of the name.

This registry is intended to collect reserved and special names defined in RFCs and defined by the designated manager, currently the Internet Architecture Board.

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 Description RFC#s/References and Notes IN-ADDR.ARPA S IPv4 inverse name lookup IN-ADDR-SERVERS.ARPA S Name servers for IN-ADDR.ARPA IP6.ARPA S IPv6 inverse name lookup IP6-SERVERS.ARPA S Name servers for IP6.ARPA E164.ARPA S ENUM E.164 numbers URI.ARPA S DDDS URI resolution URN.ARPA S DDDS URN resolution IRIS.ARPA S IRIS address registries Notes: Category: R is Reserved, S is Special

The recommended name of this registry is "Special Domain Name Components".

IANA is requested to establish a registry for names that have a special interpretation within the DNS. Registration requests and registry entries should include the following: The special name. Reserved, for names not intended to be delegated on the public Internet, or Special, for names intended to be used in specified ways. A brief description of the name and, where appropriate, its usage. A reference to an RFC or other definition of the name.

This registry is intended to collect special name components defined in RFCs.

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 Description RFC#s/References and Notes _service SRV service names (#2) _proto SRV protocol names (#3, #4) _DOMAINKEY DKIM signature verification keys _ADSP DKIM ADSP policy records _VOUCH VBR certification records Notes: _service means the name of any service, preceded by an underscore, such as _LDAP. This name appears as the penultimate name of a SRV record, where the leaf name is a _service name, or as a leaf name. _protocol means the name of any protocol, preceded by an underscore, such as _TCP. RFC 3861 created the "Instant Messaging SRV Protocol Label Registry" for labels corresponding to protocols used in Instant Messaging.

IANA is requested to establish the registries described in , , , and , using the initial content specified in each of those sections of this document. 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.

The creation of this registry provides improved documentation and protection against interoperability problems. It introduces no new security issues.

&rfc1034; &rfc1035; &rfc2606; &rfc2782; &rfc3172; &rfc3405; &rfc3406; &rfc3026; &rfc3596; &rfc3861; &rfc4698; &rfc4871; &rfc5518; &rfc5617; Internet Corporation for Assigned Names and Numbers Internet Corporation for Assigned Names and Numbers &rfc5226; Internet Corporation for Assigned Names and Numbers

4676 Admiralty Way, Suite 330 Marina del Rey CA 90292 US +1 310 823 9358 http://www.icann.org/

NOTE TO RFC EDITOR: This section may be removed upon publication of this document as an RFC.

Break into three registries Add proposed new .ARPA domain servers Add more references