<?xml version="1.0" encoding="US-ASCII"?>
<!-- This template is for creating an Internet Draft using xml2rfc,
     which is available here: http://xml.resource.org. -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!-- One method to get references from the online citation libraries.
     There has to be one entity for each item to be referenced. 
     An alternate method (rfc include) is described in the references. -->
<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC4180 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4180.xml">
<!ENTITY RFC7111 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7111.xml">
<!ENTITY I-D.narten-iana-considerations-rfc2434bis SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.narten-iana-considerations-rfc2434bis.xml">
]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<!-- used by XSLT processors -->
<!-- For a complete list and description of processing instructions (PIs), 
     please see http://xml.resource.org/authoring/README.html. -->
<!-- Below are generally applicable Processing Instructions (PIs) that most I-Ds might want to use.
     (Here they are set differently than their defaults in xml2rfc v1.32) -->
<?rfc strict="yes" ?>
<!-- give errors regarding ID-nits and DTD validation -->
<!-- control the table of contents (ToC) -->
<?rfc toc="yes"?>
<!-- generate a ToC -->
<?rfc tocdepth="4"?>
<!-- the number of levels of subsections in ToC. default: 3 -->
<!-- control references -->
<?rfc symrefs="yes"?>
<!-- use symbolic references tags, i.e, [RFC2119] instead of [1] -->
<?rfc sortrefs="yes" ?>
<!-- sort the reference entries alphabetically -->
<!-- control vertical white space 
     (using these PIs as follows is recommended by the RFC Editor) -->
<?rfc compact="yes" ?>
<!-- do not start each main section on a new page -->
<?rfc subcompact="yes" ?>
<!-- keep one blank line between list items -->
<?rfc comments="yes" ?>
<!-- show cref output -->
<?rfc inline="yes" ?>
<!-- inline cref output -->
<!-- end of list of popular I-D processing instructions -->
<rfc category="std" docName="draft-carney-regext-unavailable-domains-00" ipr="trust200902">
  <!-- category values: std, bcp, info, exp, and historic
     ipr values: full3667, noModification3667, noDerivatives3667
     you can add the attributes updates="NNNN" and obsoletes="NNNN" 
     they will automatically be output with "(if approved)" -->

  <!-- ***** FRONT MATTER ***** -->

  <front>
    <!-- The abbreviated title is used in the page header - it is only necessary if the 
         full title is longer than 39 characters -->

    <title abbrev="Unavailable Domains">
    Unavailable Domain Name File Format Specification</title>

    <author fullname="Roger Carney" initials="R.C." surname="Carney">
      <organization>GoDaddy Inc.</organization>

      <address>
        <postal>
          <street>14455 N. Hayden Rd. #219</street>

          <city>Scottsdale</city>

          <region>AZ</region>

          <code>85260</code>

          <country>US</country>
        </postal>

        <email>rcarney@godaddy.com</email>

        <uri>http://www.godaddy.com</uri>
      </address>
    </author>

    <author fullname="James Galvin" initials="J.G." surname="Galvin">
      <organization>Afilias USA</organization>

      <address>
        <postal>
          <street>300 Welsh Road, Building 3, Suite 105</street>

          <city>Horsham</city>

          <region>PA</region>

          <code>19044</code>

          <country>US</country>
        </postal>

        <email>jgalvin@afilias.info</email>

        <uri>http://www.afilias.info</uri>
      </address>
    </author>

    <date year="2016"/>

    <!-- Meta-data Declarations -->

    <area>Applications and Real-Time</area>

    <workgroup>Registration Protocols Extensions</workgroup>

    <abstract>
      <t>This document defines the file format for the storage of unavailable
      domain names and related details for a top level domain name registry.</t>
    </abstract>
    
  </front>

  <middle>
    <section title="Introduction">
      <t>This document specifies a file format for the storage of unavailable
      domain names and related details for a top level domain (TLD) name
      registry, designed to facilitate interoperability and reusability among
      domain name registries and registrars.</t>

      <t>The increased number of domain name registries and registrars, the
      greater number of reasons for domain names not being available, and to
      make accommodations for possible real-time communications issues between
      registries and registrars has driven the need for this standard sharable
      file.</t>

      <section title="Conventions Used in This Document">
        <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
        "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
        document are to be interpreted as described in <xref
        target="RFC2119">RFC 2119</xref>.</t>

      </section>
    </section>

    <section title="General File Format Elements">
      <t>File format will be a comma separated values (CSV) file and MUST use
      the US-ASCII character set. See informational RFC 4180 and RFC 7111 for
      details on the CSV file format.</t>
      
      <t>Filename has two forms depending on content. For a file containing only
      a list of unavailable domain names in one Top Level Domain (TLD) the
      filename MUST be &lt;TLD&gt;-unavailablenames-&lt;YYYY-MM-DDThhmmss&gt;.csv.
      For a file containing a list of unavailable domain names in multiple Top
      Level Domains (TLDs) the filename MUST be unavailablenames-&lt;YYYY-MM-DDThhmmss&gt;.csv.
      For an IDN TLD &lt;TLD&gt; MUST be ace-encoded (i.e. in the "xn--" format).
      &lt;YYYY-MM-DDThhmmss&gt; MUST be the date and time (in UTC) the file was
      created indicating that all the names in the file were unavailable on that
      date at the time the file was created.</t>
      
      <t>The first row MUST be the column headings:  TLD, Domain Name, Status.
      The remaining rows will contain the data (all unavailable names) from the
      registry in the following structure: &lt;TLD&gt;, &lt;Domain Name&gt;,
      &lt;Status&gt;. Where &lt;TLD&gt; is the TLD of the domain name,
      &lt;Domain Name&gt; is the string of characters that represent the
      unavailable name, and &lt;Status&gt; is one of four values (REGISTERED,
      REGISTRY RESERVED, POLICY RESERVED, IDN VARIANT RESERVED). If the
      &lt;TLD&gt; and/or &lt;Domain Name&gt; is an IDN it MUST be ace-encoded
      (i.e. in the "xn--" format).</t>
      
      <t>All domain name labels that are not available for registration in the
      SRS, for any reason, to the registrar channel MUST be included in this
      file.</t>

    </section>

    <section title="Examples">
      <section title="Single TLD File Example">
      
        <t>Example of a file that contains unavailable domain names from a single
        TLD.</t>
        
        <t>FileName: example-unavailablenames-2016-05-01T010000.csv</t>

        <t><list>
          <t>TLD,Domain Name,Status</t>
          <t>example,e.example,REGISTRY RESERVED</t>
          <t>example,ex.example,POLICY RESERVED</t>
          <t>example,example.example,REGISTERED</t>
          <t>example,xn--4gqvdy3r.example,REGISTERED</t>
        </list></t>

      </section>

      <section title="Multiple TLDs File Example">

        <t>Example of a file that contains unavailable domain names from
        multiple TLDs.</t>

        <t>FileName: unavailablenames-2016-05-01T010000.csv</t>

        <t><list>
          <t>TLD,Domain Name,Status</t>
          <t>example,e.example,REGISTRY RESERVED</t>
          <t>test,ex.test,POLICY RESERVED</t>
          <t>another,xn--4gqvdy3r.another,REGISTERED</t>
        </list></t>

      </section>

    </section>

    <section anchor="Security" title="Security Considerations">
      <t>The file format described in this document does not provide any
      security services.</t>
    </section>

    <section title="Acknowledgements">
      <t>The authors wish to thank the following persons for their feedback and
      suggestions:</t>
      <t><list style="symbols">
        <t>Christine Turner of GoDaddy Inc.</t>
        <t>Jody Kolker of GoDaddy Inc.</t>
        <t>Richard Merdinger of GoDaddy Inc.</t>
        <t>Mike Runcieman of Afilias Canada</t>
        <t>Wayne Beaver of Afilias USA</t>
      </list></t>
    </section>

    <section title="Change History">
    </section>

  </middle>

  <!--  *****BACK MATTER ***** -->

  <back>
    <!-- References split into informative and normative -->

    <!-- There are 2 ways to insert reference entries from the citation libraries:
     1. define an ENTITY at the top, and use "ampersand character"RFC2629; here (as shown)
     2. simply use a PI "less than character"?rfc include="reference.RFC.2119.xml"?> here
        (for I-Ds: include="reference.I-D.narten-iana-considerations-rfc2434bis.xml")

     Both are cited textually in the same manner: by using xref elements.
     If you use the PI option, xml2rfc will, by default, try to find included files in the same
     directory as the including file. You can also define the XML_LIBRARY environment variable
     with a value containing a set of directories to search.  These can be either in the local
     filing system or remote ones accessed by http (http://domain/dir/... ).-->

    <references title="Normative References">

      &RFC2119;

      &RFC4180;

      &RFC7111;

    </references>

  </back>
</rfc>






