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

<!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">

<rfc xmlns:xi="http://www.w3.org/2001/XInclude"
     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="Updated Registration Rules for URI.ARPA">Updated Registration Rules for
   URI.ARPA</title>

   <seriesInfo 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" 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 zone. </t>
   </abstract>
  </front>
  <middle>
    <section numbered="true" toc="default">
      <name>Introduction</name>
      
      <t> Part Five of the Dynamic Delegation Discovery System (DDDS)
      <xref target="RFC3405" 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>
      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 key words "<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 "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
    described in BCP&nbsp;14 <xref target="RFC2119"/> <xref target="RFC8174"/> 
    when, and only when, they appear in all capitals, as shown here.
        </t>
      </section>
    </section>
    <section numbered="true" toc="default">
      <name>Updated Requirements</name>
      <t>This document removes the normative requirement 
      from <xref target="RFC3405">RFC 3405</xref> for registrations in URI.ARPA to be from the IETF URI tree.</t>
      <t>All registrations in URI.ARPA <bcp14>MUST</bcp14> now be for schemes that
      are permanent registrations, as 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 in
      <xref target="RFC3405">RFC 3405</xref>.
      </t>
    </section>

  </middle>

 <back>


   <references>
      <name>References</name>
      <references>
        <name>Normative References</name>

<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>
 
<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>
