One document matched: draft-ellermann-idnabis-test-tlds-00.xml

<?xml version="1.0" encoding="US-ASCII" ?>
<!DOCTYPE rfc SYSTEM "http://xml.resource.org/authoring/rfc2629.dtd" [
    <!ENTITY rfc1034 PUBLIC ''
    'http://xml.resource.org/public/rfc/bibxml/reference.RFC.1034.xml'>
    <!ENTITY rfc1035 PUBLIC ''
    'http://xml.resource.org/public/rfc/bibxml/reference.RFC.1035.xml'>
    <!ENTITY rfc1591 PUBLIC ''
    'http://xml.resource.org/public/rfc/bibxml/reference.RFC.1591.xml'>
    <!ENTITY rfc2119 PUBLIC ''
    'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml'>
    <!ENTITY rfc2606 PUBLIC ''
    'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2606.xml'>
    <!ENTITY rfc2860 PUBLIC ''
    'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2860.xml'>
    <!ENTITY rfc3696 PUBLIC ''
    'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3696.xml'>
    <!ENTITY rfc3490 PUBLIC ''
    'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3490.xml'>
    <!ENTITY rfc5226 PUBLIC ''
    'http://xml.resource.org/public/rfc/bibxml/reference.RFC.5226.xml'>
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>

<!-- no I-D - >
    <?rfc private="Creative Commons License:      Attributions + ShareAlike" ?>
    <?rfc header="Interim draft" ?>
    <?rfc footer="draft-ellermann-idnabis-test-tlds-00" ?>
<! - no I-D -->

<?rfc toc="yes" ?>
<?rfc compact="yes" ?>
<?rfc subcompact="no" ?>
<?rfc symrefs="yes" ?>
<?rfc strict="yes" ?>
<?rfc rfcprocack="yes" ?>

<rfc docName="draft-ellermann-idnabis-test-tlds-00" obsoletes="2606" category="bcp"
     ipr="full3978" xml:lang="en-GB-oed" ><front>
    <title> Reserved Top Level DNS Names </title>
    <author initials="F." surname="Ellermann" fullname="Frank Ellermann">
        <organization>xyzzy</organization>
        <address>
            <postal>
                <street></street>
                <city>Hamburg</city>
                <region>Germany</region>
            </postal>
            <email>hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com</email>
            <uri>http://purl.net/xyzzy/</uri>
        </address>
    </author>
    <date />
    <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>

    <note title="Editorial note"><t>
        This note and the
        <xref target="history">document history</xref>
        should be removed before publication.
    </t></note>
</front><middle>

<section title="Introduction"><t>
    The global Internet Domain Name System is documented in
    <xref target="RFC1034" />,
    <xref target="RFC1035" />,
    <xref target="RFC1591" />,
    <xref target="RFC3696" />,
    and numerous additional Requests for Comments. It defines a tree
    of names starting with root, ".", immediately below which are
    top level domain names such as ".com" and ".us". Below top level
    domain names there are normally additional levels of names.
</t><t>
    The key words "MAY", "RECOMMENDED", and "SHOULD" in this memo
    are to be interpreted as described in <xref target="RFC2119" />.
</t></section>

<section title="TLDs for Testing, & Documentation Examples"><t>
    There is a need for top level domain (TLD) names that can be used for
    creating names which, without fear of conflicts with current or
    future actual TLD names in the global DNS, can be used for private
    testing of existing DNS related code, examples in documentation, DNS
    related experimentation, invalid DNS names, or other similar uses.
</t><t>
    For example, without guidance, a site might set up some local
    additional unused top level domains for testing of its local DNS code
    and configuration. Later, these TLDs might come into actual use on
    the global Internet.  As a result, local attempts to reference the
    real data in these zones could be thwarted by the local test
    versions.  Or test or example code might be written that accesses a
    TLD that is in use with the thought that the test code would only be
    run in a restricted testbed net or the example never actually run.
    Later, the test code could escape from the testbed or the example be
    actually coded and run on the Internet. Depending on the nature of
    the test or example, it might be best for it to be referencing a TLD
    permanently reserved for such purposes.
</t><t>
    To safely satisfy these needs, four domain names are reserved as
    listed and described below.

</t><section title='".example"' anchor="example"><t>
    ".example" is RECOMMENDED for use in documentation or as examples.

</t></section><section title='".invalid"'><t>
    ".invalid" is intended for use in online construction of domain
    names that are sure to be invalid, and for which it is obvious at
    a glance that they are invalid. Applications MAY treat ".invalid"
    as what the name says.

</t></section><section title='".localhost"'><t>
    The ".localhost" TLD has traditionally been statically defined in
    host DNS implementations as having an A record pointing to the
    loop back IP address and is reserved for such use.  Any other use
    would conflict with widely deployed code which assumes this use.

</t></section><section title='".test"' anchor="test"><t>
    ".test" is RECOMMENDED for use in testing of current or new DNS
    related code. Applications SHOULD treat ".test" like any other
    TLD, a special handling could defeat the purpose of a test.

</t></section></section>

<section title="Reserved Example Second Level Domain Names"><t>
    The Internet Assigned Numbers Authority (IANA) also reserves the
    three second level domain names ".example.com", ".example.net",
    and ".example.org" which can be used in examples as explained
    in <xref target="example" />.
</t><t>
    When TLDs offer further second level domains for examples, the
    TLD administrators are encouraged to publish the relevant policies
    in their TLD as informational RFC.
</t><t>
    The second level domain names "nic", "whois", and "www" are often
    reserved or used for the purposes of the TLD administration. As
    with second level domains for examples this can be an issue in
    the case of a transfer to a new administration.
</t></section>

<section title="Acknowledgments"><t>
    This memo contains major parts of <xref target="RFC2606" /> written
    by Donald E. Eastlake and Aliza R. Panitz. John C. Klensin suggested
    to clarify the guidelines for examples in RFCs.
</t></section>

<section title="Internationalization Considerations" anchor="i18n"><t>
    In 2007 IANA created eleven TLDs for tests of Internationalized
    Domain Names (IDN). The A-labels and corresponding languages are
    listed below, see <xref target="RFC3490" /> or its successor for
    details about IDN. Applications SHOULD treat these IDN test TLDs
    as explained in <xref target="test" />.
</t><figure><artwork>
    ".xn--0zwm56d"        Chinese (simplified)
    ".xn--11b5bs3a9aj6g"  Hindi
    ".xn--80akhbyknj4f"   Russian
    ".xn--9t4b11yi5a"     Korean
    ".xn--deba0ad"        Yiddish
    ".xn--g6w251d"        Chinese (traditional)
    ".xn--hgbk6aj7f53bba" Persian
    ".xn--hlcj6aya9esc7a" Tamil
    ".xn--jxalpdlp"       Greek
    ".xn--kgbechtv"       Arabic
    ".xn--zckzah"         Japanese
</artwork></figure></section>

<section title="Security Considerations"><t>
    Confusion and conflict can be caused by the use of a current or
    future top level domain name in experimentation or testing, as an
    example in documentation, to indicate invalid names, or as a synonym
    for the loop back address.  Test and experimental software can escape
    and end up being run against the global operational DNS.  Even
    examples used "only" in documentation can end up being coded and
    released or cause conflicts due to later real use and the possible
    acquisition of intellectual property rights in such "example" names.
</t><t>
    The reservation of several top level domain names for these purposes
    minimizes such confusion and conflict.
</t></section>

<section title="IANA Considerations" anchor="iana"><t>
    IANA reserves the TLDs ".example", ".invalid", ".localhost", ".test",
    and eleven IDN test TLDs as noted above. IANA reserves the second
    level domains ".example.com", ".example.net", and ".example.org".
</t><t>
    IANA creates a public registry of reserved TLDs, this can be done
    alongside existing IANA TLD registries at the discretion of IANA.
    Additional reserved TLDs require IETF review as specified in
    <xref target="RFC5226" /> in conjunction with <xref target="RFC2860" />.
</t></section>

</middle><back>
    <references title="Normative References">
        &rfc2119;
        &rfc5226;
    </references>

    <references title="Informative References">
        &rfc1034;
        &rfc1035;
        &rfc1591;
        &rfc2606;
        &rfc2860;
        &rfc3490;
        &rfc3696;
    </references>

    <section title="Document History" anchor="history"><t>
        Changes in version 00:
    </t><t>
        <list style="symbols"><t>
            Derived from <xref target="RFC2606" /> to resolve a dispute
            about the use of e-mail addresses in RFC examples, adding
            the eleven new IDN test TLDs.
        </t></list>
    </t></section>
</back></rfc>