<?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 RFC2860 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2860.xml">
<!ENTITY RFC6761 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6761.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="no" ?>
<!-- keep one blank line between list items -->
<!-- end of list of popular I-D processing instructions -->
<rfc category="info" docName="draft-michaelson-dnsop-rfc6761-is-closed-00" ipr="trust200902" obsoletes="6761">
 <!-- category values: std, bcp, info, exp, and historic
    ipr values: trust200902, noModificationTrust200902, noDerivativesTrust200902,
       or pre5378Trust200902
    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="Abbreviated Title">RFC6761 is now closed</title>

   <author fullname="George Michaelson" initials="G.G."
           surname="Michaelson">
     <organization>APNIC P/L</organization>

     <address>
       <postal>
         <street>6 Cordelia Street</street>

         <!-- Reorder these if your country does things differently -->

         <city>Brisbane</city>

         <region>Queensland</region>

         <code>4101</code>

         <country>Australia</country>
       </postal>

       <phone>+61 3858 3100</phone>

       <email>ggm@apnic.net</email>

       <!-- uri and facsimile elements may also be added -->
     </address>
   </author>

   <date year="2016" />

   <!-- If the month and year are both specified and are the current ones, xml2rfc will fill 
        in the current day for you. If only the current year is specified, xml2rfc will fill 
	 in the current day and month for you. If the year is not the current one, it is 
	 necessary to specify at least a month (xml2rfc assumes day="1" if not specified for the 
	 purpose of calculating the expiry date).  With drafts it is normally sufficient to 
	 specify just the year. -->

   <!-- Meta-data Declarations -->

   <area>General</area>

   <workgroup>Internet Engineering Task Force</workgroup>

   <!-- WG name at the upperleft corner of the doc,
        IETF is fine for individual submissions.  
	 If this element is not present, the default is "Network Working Group",
        which is used by the RFC Editor as a nod to the history of the IETF. -->

   <keyword>template</keyword>

   <!-- Keywords will be incorporated into HTML output
        files in a meta tag but they have no effect on text or nroff
        output. If you submit your draft to the RFC Editor, the
        keywords will be used for the search engine. -->

   <abstract>
     <t>In hindsight, RFC6761 was a mistake. This document formally closes this process.</t>
   </abstract>
 </front>

 <middle>
   <section title="Introduction">
     <t><xref target="RFC6761">RFC&nbsp;6761</xref> specified mechanisms for reserving a top level name in the DNS.</t>
     <t>This reversed a prior decision documented by <xref target="RFC2860">RFC&nbsp;2860</xref> to close off mechanisms for name assignment in the IETF,
        the function being recognized as vesting with ICANN.</t>

     <t>In hindsight, re-opening a registry for special cases of technical merit inside IETF process has turned out to be a
        mistake, and introduces procedural issues which cannot be adequately addressed solely inside a technical process, instead
        instantiating  mechanisms which bypass ICANN process.</t>
     <t>The apparent absence of an appropriate technology driven admission process inside ICANN methods to assign top level domain names is
        regrettable, but the solution does not lie in vesting the IETF with an admissions process. This has invited (and led to) 
        domain squatting, spurious technical arguments, and has destroyed any functional vision of an architecture, replacing it with
        unrelated competing requests for more and more names. This is simply not appropriate use of the IETF process.</t>
     <t>Accordingly, this document formally closes the RFC6761 process. No more requests will be entertained in this process and all
        existing names are grandfathered in, but will be relinquished gracefully should the technical requirement be demonstrated not
        to apply any more at scale.</t>

     <section title="Requirements Language">
       <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 anchor="Acknowledgements" title="Acknowledgements">
     <t>This document was written hurredly. But the intent should be clear.</t>
   </section>

   <!-- Possibly a 'Contributors' section ... -->

   <section anchor="IANA" title="IANA Considerations">
     <t>The IANA is directed to close the Special Use Domain Name registry, and MUST NOT admit any further entries in this registry.</t>
   </section>

   <section anchor="Security" title="Security Considerations">
     <t>No new security considerations are introduced by this document. All existing security considerations from prior names in the
        special-use names registry are assumed to continue to exist.</t>
   </section>
 </middle>

 <!--  *****BACK MATTER ***** -->

 <back>
   <references title="Normative References">
     &RFC2860;
     &RFC6761;

   </references>

   <references title="Informative References">
     <!-- Here we use entities that we defined at the beginning. -->

     &RFC2119;

   </references>

   <!-- Change Log

v00 2016-02-22  GGM   Initial version
    -->

 </back>
</rfc>
