One document matched: draft-jabley-reserved-domain-names-00.xml
<?xml version="1.0" encoding="UTF-8"?><?rfc linefile="1:draft-jabley-reserved-domain-names.xml"?>
<!-- automatically generated by xml2rfc v1.35 on 2011-02-04T13:54:59Z -->
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!--
--><!-- xml2rfc-processed-entity rfc1034 -->
<!--
--><!-- xml2rfc-processed-entity rfc1035 -->
<!--
--><!-- xml2rfc-processed-entity rfc2606 -->
<!--
--><!-- xml2rfc-processed-entity I-D.cheshire-dnsext-multicastdns -->
<!-- xml2rfc-processed-entity FRONT -->
]>
<rfc category="bcp" ipr="trust200902"
docName="draft-jabley-reserved-domain-names-00">
<?rfc toc="no" ?>
<?rfc symrefs="yes" ?>
<?rfc sortrefs="yes"?>
<?rfc iprnotified="no" ?>
<?rfc strict="yes" ?>
<?rfc linefile="1:draft-jabley-reserved-domain-names.front"?> <front>
<title>Reserved Domain Names</title>
<author initials='J.' surname="Abley" fullname='Joe Abley'>
<organization>ICANN</organization>
<address>
<postal>
<street>4676 Admiralty Way, Suite 330</street>
<city>Marina del Rey</city>
<region>CA</region>
<code>90292</code>
<country>USA</country>
</postal>
<phone>+1 519 670 9327</phone>
<email>joe.abley@icann.org</email>
</address>
</author>
<date month="February" year="2011"/>
<abstract>
<t>The Domain Name System (DNS) makes use of a hierarchical
naming scheme. The validity of a particular name in the DNS
is governed by protocol, operational and policy considerations.</t>
<t>The IETF has identified particular domain names to have
special considerations associated with their use. These
domain names have been identified in various documents in
the RFC series. This document describes the creation of an
IANA registry to catalogue such domain names and provides
direction about how this registry should be maintained.</t>
<t>This document does not identify any new domain name as
having special considerations associated with its use.</t>
</abstract>
</front>
<?rfc linefile="25:draft-jabley-reserved-domain-names.xml"?>
<middle>
<section title="Introduction">
<t>The Domain Name System (DNS) is described in <xref
target="RFC1034"/> and <xref target="RFC1035"/>.</t>
<t>The DNS makes use of a hierarchical naming scheme. The
validity of a particular name in the DNS is governed by
protocol, operational and policy considerations.</t>
<t>The IETF has identified particular domain names to have
special considerations associated with their use. Examples
of such domain names are "LOCALHOST" and "EXAMPLE.ORG"
which are discussed in <xref target="RFC2606"/>, and
"LOCAL" and "254.169.IN-ADDR.ARPA" which are described in
<xref target="I-D.cheshire-dnsext-multicastdns"/>.</t>
<t>This document describes the creation of an
IANA registry to catalogue such domain names and provides
direction about how this registry should be maintained.</t>
<t>This document does not identify any new domain name as
having special considerations associated with its use.</t>
</section>
<section title="IANA Considerations" anchor="iana">
<t>This document directs the IANA to create a registry as
follows:</t>
<texttable>
<ttcol>Parameter</ttcol>
<ttcol>Value</ttcol>
<c>Registry Name</c>
<c>Reserved Domain Names</c>
<c>Reference</c>
<c>This document (RFC&rfc.number;)</c>
<c>Registration Procedures</c>
<c>Document Published with IAB Approval</c>
</texttable>
<t>The initial registry contents should be as follows:</t>
<texttable>
<ttcol>Domain Name</ttcol>
<ttcol>Description</ttcol>
<ttcol>Reference</ttcol>
<c>TEST</c>
<c>Recommended for use in testing of current or new DNS related
code</c>
<c><xref target="RFC2606"/></c>
<c>EXAMPLE</c>
<c>Recommended for use in documentation or as examples</c>
<c><xref target="RFC2606"/></c>
<c>INVALID</c>
<c>Recommended for use in documentation or as examples</c>
<c><xref target="RFC2606"/></c>
<c>LOCALHOST</c>
<c>Traditionally statically defined in host DNS implementations
as having an A record pointing to the loop back IP address,
and reserved for such use</c>
<c><xref target="RFC2606"/></c>
<c>EXAMPLE.COM</c>
<c>Available for use as examples</c>
<c><xref target="RFC2606"/></c>
<c>EXAMPLE.NET</c>
<c>Available for use as examples</c>
<c><xref target="RFC2606"/></c>
<c>EXAMPLE.ORG</c>
<c>Available for use as examples</c>
<c><xref target="RFC2606"/></c>
</texttable>
</section>
<section title="Security Considerations">
<t>This document poses no new security issues.</t>
</section>
</middle>
<back>
<references title="Informative References">
<?rfc linefile="1:http://xml.resource.org/public/rfc/bibxml/reference.RFC.1034.xml"?>
<reference anchor='RFC1034'>
<front>
<title abbrev='Domain Concepts and Facilities'>Domain names - concepts and facilities</title>
<author initials='P.' surname='Mockapetris' fullname='P. Mockapetris'>
<organization>Information Sciences Institute (ISI)</organization></author>
<date year='1987' day='1' month='November' /></front>
<seriesInfo name='STD' value='13' />
<seriesInfo name='RFC' value='1034' />
<format type='TXT' octets='129180' target='http://www.rfc-editor.org/rfc/rfc1034.txt' />
</reference>
<?rfc linefile="106:draft-jabley-reserved-domain-names.xml"?>
<?rfc linefile="1:http://xml.resource.org/public/rfc/bibxml/reference.RFC.1035.xml"?>
<reference anchor='RFC1035'>
<front>
<title abbrev='Domain Implementation and Specification'>Domain names - implementation and specification</title>
<author initials='P.' surname='Mockapetris' fullname='P. Mockapetris'>
<organization>USC/ISI</organization>
<address>
<postal>
<street>4676 Admiralty Way</street>
<city>Marina del Rey</city>
<region>CA</region>
<code>90291</code>
<country>US</country></postal>
<phone>+1 213 822 1511</phone></address></author>
<date year='1987' day='1' month='November' /></front>
<seriesInfo name='STD' value='13' />
<seriesInfo name='RFC' value='1035' />
<format type='TXT' octets='125626' target='http://www.rfc-editor.org/rfc/rfc1035.txt' />
</reference>
<?rfc linefile="107:draft-jabley-reserved-domain-names.xml"?>
<?rfc linefile="1:http://xml.resource.org/public/rfc/bibxml/reference.RFC.2606.xml"?>
<reference anchor='RFC2606'>
<front>
<title>Reserved Top Level DNS Names</title>
<author initials='D.E.' surname='Eastlake' fullname='Donald E. Eastlake 3rd'>
<organization>IBM</organization>
<address>
<postal>
<street>65 Shindegan Hill Road</street>
<street>RR #1</street>
<city>Carmel</city>
<region>NY</region>
<code>10512</code>
<country>US</country></postal>
<phone>+1 914 276 1668</phone>
<facsimile>+1 914 784 3833</facsimile>
<email>dee3@us.ibm.com</email></address></author>
<author initials='A.' surname='Panitz' fullname='Aliza R. Panitz'>
<organization />
<address>
<postal>
<street>500 Stamford Dr. No. 310</street>
<city>Newark</city>
<region>DE</region>
<code>19711</code>
<country>US</country></postal>
<phone>+1 302 738 1554</phone>
<email>buglady@fuschia.net</email></address></author>
<date year='1999' month='June' />
<abstract>
<t>To reduce the likelihood of conflict and confusion, a few top level domain names are reserved for use in private testing, as examples in documentation, and the like. In addition, a few second level domain names reserved for use as examples are documented.</t></abstract></front>
<seriesInfo name='BCP' value='32' />
<seriesInfo name='RFC' value='2606' />
<format type='TXT' octets='8008' target='http://www.rfc-editor.org/rfc/rfc2606.txt' />
</reference>
<?rfc linefile="108:draft-jabley-reserved-domain-names.xml"?>
<?rfc linefile="1:http://xml.resource.org/public/rfc/bibxml3/reference.I-D.cheshire-dnsext-multicastdns.xml"?>
<reference anchor='I-D.cheshire-dnsext-multicastdns'>
<front>
<title>Multicast DNS</title>
<author initials='S' surname='Cheshire' fullname='Stuart Cheshire'>
<organization />
</author>
<author initials='M' surname='Krochmal' fullname='Marc Krochmal'>
<organization />
</author>
<date month='January' day='12' year='2011' />
<abstract><t>As networked devices become smaller, more portable, and more ubiquitous, the ability to operate with less configured infrastructure is increasingly important. In particular, the ability to look up DNS resource record data types (including, but not limited to, host names) in the absence of a conventional managed DNS server is useful. Multicast DNS (mDNS) provides the ability to perform DNS-like operations on the local link in the absence of any conventional unicast DNS server. In addition, mDNS designates a portion of the DNS namespace to be free for local use, without the need to pay any annual fee, and without the need to set up delegations or otherwise configure a conventional DNS server to answer for those names. The primary benefits of mDNS names are that (i) they require little or no administration or configuration to set them up, (ii) they work when no infrastructure is present, and (iii) they work during infrastructure failures.</t></abstract>
</front>
<seriesInfo name='Internet-Draft' value='draft-cheshire-dnsext-multicastdns-13' />
<format type='TXT'
target='http://www.ietf.org/internet-drafts/draft-cheshire-dnsext-multicastdns-13.txt' />
</reference>
<?rfc linefile="109:draft-jabley-reserved-domain-names.xml"?>
</references>
<section title="Editorial Notes">
<t>This section (and sub-sections) to be removed prior to
publication.</t>
<section title="Change History">
<t>
<list style="hanging">
<t hangText="00">Initial draft, submitted long after it was
written as an aid to last-call discussion of
draft-cheshire-dnsext-special-names-01.</t>
</list>
</t>
</section>
</section>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-24 04:24:48 |