<?xml version='1.0' encoding='utf-8'?> version="1.0" encoding="UTF-8"?>

<!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>

<rfc xmlns:xi="http://www.w3.org/2001/XInclude"
      category="bcp"
     docName="draft-hardie-dispatch-rfc3405-update-04" number="8958"
     updates="3405" ipr="trust200902" submissionType="IETF" category="bcp"
     consensus="true" xml:lang="en" tocInclude="true" tocDepth="4"
     symRefs="true" sortRefs="true" version="3">

 <front>
   <title abbrev="RFC 3405 Update">Updated registration rules abbrev="Updated Registration Rules for URI.ARPA">Updated Registration Rules for
   URI.ARPA</title>

   <seriesInfo name="Internet-Draft" value="draft-ietf-xml2rfc-template-06"/> name="RFC" value="8958"/>
   <seriesInfo name="BCP" value="65" />
   <author fullname="Ted Hardie" surname="Hardie">
      <address>
        <email>ted.ietf@gmail.com</email>
     </address>
    </author>
   <date year="2020"/>

   <!-- Meta-data Declarations --> year="2020" month="December" />

   <area>ART</area>
    <workgroup>DISPATCH</workgroup>
   <abstract>
     <t>
       This document updates RFC 3405 by removing
       references to the IETF tree from the procedures for requesting
       that a URI scheme be inserted into the uri.arpa URI.ARPA zone. </t>
   </abstract>
  </front>
  <middle>
    <section numbered="true" toc="default">
      <name>Introduction</name>

      <t> Part five Five of the Dynamic Delegation Discovery System (DDDS), (DDDS)
      <xref target="RFC3405" format="default">RFC 3405</xref>, format="default"/>
      describes the registration procedures for assignments in
      URI.ARPA.  The document requires that registrations be in the
      "IETF tree" of URI registrations.  The use of URI scheme name
      trees was defined in <xref target ="RFC2717" format="default">
      RFC 2717 </xref> target="RFC2717"
      format="default">RFC 2717</xref>
      but discontinued by <xref target="RFC4395"
      format="default">RFC 4395</xref> and its successors.  Since the
      use of trees was discontinued, there is no way in the current
      process set out in <xref target="RFC7595" format="default">BCP 35</xref> to meet the requirement to register within that
      tree. </t>

      <section numbered="true" toc="default">
        <name>Requirements Language</name>
        <t>The
        <t>
    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
    NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
    "<bcp14>MAY</bcp14>", and
   "OPTIONAL" "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
    described in BCP
   14 BCP&nbsp;14 <xref target ="RFC2119" /><xref target ="RFC8174" /> target="RFC2119"/> <xref target="RFC8174"/>
    when, and only when, they appear in all capitals, as shown here.</t> here.
        </t>
      </section>
    </section>
    <section numbered="true" toc="default">
      <name>Updated Requirements</name>
      <t>This document removes the normative requirement
      from RFC 3405 <xref target="RFC3405">RFC 3405</xref> for registrations in URI.ARPA to be from the IETF URI Tree.</t> tree.</t>
      <t>All registrations in URI.ARPA MUST <bcp14>MUST</bcp14> now be for schemes which that
      are permanent registrations, as they are described in BCP 35.
      </t>
    </section>

    <section numbered="true" toc="default">
      <name>IANA Considerations</name>
      <t>This entire document is updated instructions to IANA.
      </t>
    </section>
    <section numbered="true" toc="default">
      <name>Security Considerations</name>
      <t>This update does not change the Security Considerations security considerations in RFC 3405
      <xref target="RFC3405">RFC 3405</xref>.
      </t>
    </section>

  </middle>
  <!--  *****BACK MATTER ***** -->

 <back>

   <references>
      <name>References</name>
      <references>
        <name>Normative References</name>
     <reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <seriesInfo name="DOI" value="10.17487/RFC2119"/>
            <seriesInfo name="RFC" value="2119"/>
            <seriesInfo name="BCP" value="14"/>
            <author initials="S." surname="Bradner" fullname="S. Bradner">
              <organization/>
            </author>
            <date year="1997" month="March"/>
	    <abstract>
              <t>In many standards track documents several words are used to signify the requirements in the specification.  These words are often capitalized. This document defines these words as they should be interpreted in IETF documents.  This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
     </reference>
	    <reference anchor="RFC8174" target="https://www.rfc-editor.org/info/rfc8174">
	      <front>
		<title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
		<author initials="B." surname="Leiba" fullname="B. Leiba">
		  <organization/>
		</author>
		<date year="2017" month="May"/>
		<abstract>
		  <t>
		    RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.
		  </t>
		</abstract>
	      </front>
	      <seriesInfo name="BCP" value="14"/>
	      <seriesInfo name="RFC" value="8174"/>
	      <seriesInfo name="DOI" value="10.17487/RFC8174"/>
	    </reference>
    <reference anchor="RFC3405" target="https://www.rfc-editor.org/info/rfc3405">
      <front>
	<title>Dynamic Delegation Discovery System (DDDS) Part Five: URI.ARPA Assignment Procedures</title>
	<author initials="M." surname="Mealling" fullname="M. Mealling">
	  <organization/>
	</author>
	<date year="2002" month="October"/>
	<abstract>
	  <t>
	    This document is fifth in a series that is completely specified in "Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS" (RFC 3401). It is very important to note that it is impossible to read and understand any document in this series without reading the others. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
	  </t>
	</abstract>
      </front>
      <seriesInfo name="BCP" value="65"/>
      <seriesInfo name="RFC" value="3405"/>
      <seriesInfo name="DOI" value="10.17487/RFC3405"/>
    </reference>
    <reference anchor="RFC7595" target="https://www.rfc-editor.org/info/rfc7595">
      <front>
	<title>Guidelines and Registration Procedures for URI Schemes</title>
	<author initials="D." surname="Thaler" fullname="D. Thaler" role="editor">
	  <organization/>
	</author>
	<author initials="T." surname="Hansen" fullname="T. Hansen">
	  <organization/>
	</author>
	<author initials="T." surname="Hardie" fullname="T. Hardie">
	  <organization/>
	</author>
	<date year="2015" month="June"/>
	<abstract>
	  <t>
	    This document updates the guidelines and recommendations, as well as the IANA registration processes, for the definition of Uniform Resource Identifier (URI) schemes. It obsoletes RFC 4395.
	  </t>
	</abstract>
      </front>
      <seriesInfo name="BCP" value="35"/>
      <seriesInfo name="RFC" value="7595"/>
      <seriesInfo name="DOI" value="10.17487/RFC7595"/>
    </reference>

<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3405.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7595.xml"/>

      </references>
      <references>
        <name>Informative References</name>

      <reference anchor="RFC2717" target="https://www.rfc-editor.org/info/rfc2717">
	<front>
	  <title>Registration Procedures for URL Scheme Names</title>
	  <author initials="R." surname="Petke" fullname="R. Petke">
	    <organization/>
	  </author>
	  <author initials="I." surname="King" fullname="I. King">
	    <organization/>
	  </author>
	  <date year="1999" month="November"/>
	  <abstract>
	    <t>
	      This document defines the process by which new URL scheme names are registered. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
	    </t>
	  </abstract>
	</front>
	<seriesInfo name="RFC" value="2717"/>
	<seriesInfo name="DOI" value="10.17487/RFC2717"/>
      </reference>
      <reference anchor="RFC4395" target="https://www.rfc-editor.org/info/rfc4395">
	<front>
	  <title>
	    Guidelines and Registration Procedures for New URI Schemes
	  </title>
	  <author initials="T." surname="Hansen" fullname="T. Hansen">
	    <organization/>
	  </author>
	  <author initials="T." surname="Hardie" fullname="T. Hardie">
	    <organization/>
	  </author>
	  <author initials="L." surname="Masinter" fullname="L. Masinter">
	    <organization/>
	  </author>
	  <date year="2006" month="February"/>
	  <abstract>
	    <t>
	      This document provides guidelines and recommendations for the definition of Uniform Resource Identifier (URI) schemes. It also updates the process and IANA registry for URI schemes. It obsoletes both RFC 2717 and RFC 2718. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
	    </t>
	  </abstract>
	</front>
	<seriesInfo name="RFC" value="4395"/>
	<seriesInfo name="DOI" value="10.17487/RFC4395"/>
      </reference>

<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2717.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4395.xml"/>

      </references>
    </references>
 </back>

</rfc>