rfc8958xml2.original.xml   rfc8958.xml 
<?xml version='1.0' encoding='utf-8'?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent"> <!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<rfc <rfc xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xi="http://www.w3.org/2001/XInclude" docName="draft-hardie-dispatch-rfc3405-update-04" number="8958"
category="bcp" updates="3405" ipr="trust200902" submissionType="IETF" category="bcp"
docName="draft-hardie-dispatch-rfc3405-update-04" consensus="true" xml:lang="en" tocInclude="true" tocDepth="4"
updates="3405" symRefs="true" sortRefs="true" version="3">
ipr="trust200902"
submissionType="IETF"
xml:lang="en"
tocInclude="true"
tocDepth="4"
symRefs="true"
sortRefs="true"
version="3">
<front> <front>
<title abbrev="RFC 3405 Update">Updated registration rules for URI.ARPA</titl <title abbrev="Updated Registration Rules for URI.ARPA">Updated Registration
e> Rules for
<seriesInfo name="Internet-Draft" value="draft-ietf-xml2rfc-template-06"/> URI.ARPA</title>
<seriesInfo name="RFC" value="8958"/>
<seriesInfo name="BCP" value="65" />
<author fullname="Ted Hardie" surname="Hardie"> <author fullname="Ted Hardie" surname="Hardie">
<address> <address>
<email>ted.ietf@gmail.com</email> <email>ted.ietf@gmail.com</email>
</address> </address>
</author> </author>
<date year="2020"/> <date year="2020" month="December" />
<!-- Meta-data Declarations -->
<area>ART</area> <area>ART</area>
<workgroup>DISPATCH</workgroup> <workgroup>DISPATCH</workgroup>
<abstract> <abstract>
<t> <t>
This document updates RFC 3405 by removing This document updates RFC 3405 by removing
references to the IETF tree from the procedures for requesting references to the IETF tree from the procedures for requesting
that a URI scheme be inserted into the uri.arpa zone. </t> that a URI scheme be inserted into the URI.ARPA zone. </t>
</abstract> </abstract>
</front> </front>
<middle> <middle>
<section numbered="true" toc="default"> <section numbered="true" toc="default">
<name>Introduction</name> <name>Introduction</name>
<t> Part five of the Dynamic Delegation Discovery System (DDDS), <t> Part Five of the Dynamic Delegation Discovery System (DDDS)
<xref target="RFC3405" format="default">RFC 3405</xref>, <xref target="RFC3405" format="default"/>
describes the registration procedures for assignments in describes the registration procedures for assignments in
URI.ARPA. The document requires that registrations be in the URI.ARPA. The document requires that registrations be in the
"IETF tree" of URI registrations. The use of URI scheme name "IETF tree" of URI registrations. The use of URI scheme name
trees was defined in <xref target ="RFC2717" format="default"> trees was defined in <xref target="RFC2717"
RFC 2717 </xref> but discontinued by <xref target="RFC4395" format="default">RFC 2717</xref>
but discontinued by <xref target="RFC4395"
format="default">RFC 4395</xref> and its successors. Since the format="default">RFC 4395</xref> and its successors. Since the
use of trees was discontinued, there is no way in the current use of trees was discontinued, there is no way in the current
process set out in <xref target="RFC7595" format="default">BCP process set out in <xref target="RFC7595" format="default">BCP 35</xref> t
35</xref> to meet the requirement to register within that o meet the requirement to register within that
tree. </t> tree. </t>
<section numbered="true" toc="default"> <section numbered="true" toc="default">
<name>Requirements Language</name> <name>Requirements Language</name>
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", <t>
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQU
"OPTIONAL" in this document are to be interpreted as described in BCP IRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
14 <xref target ="RFC2119" /><xref target ="RFC8174" /> when, and only NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>
when, they appear in all capitals, as shown here.</t> 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> </section>
<section numbered="true" toc="default"> <section numbered="true" toc="default">
<name>Updated Requirements</name> <name>Updated Requirements</name>
<t>This document removes the normative requirement <t>This document removes the normative requirement
from RFC 3405 for registrations in URI.ARPA to be from the IETF URI Tree.< from <xref target="RFC3405">RFC 3405</xref> for registrations in URI.ARPA
/t> to be from the IETF URI tree.</t>
<t>All registrations in URI.ARPA MUST now be for schemes which <t>All registrations in URI.ARPA <bcp14>MUST</bcp14> now be for schemes th
are permanent registrations, as they are described in BCP 35. at
are permanent registrations, as described in BCP 35.
</t> </t>
</section> </section>
<section numbered="true" toc="default"> <section numbered="true" toc="default">
<name>IANA Considerations</name> <name>IANA Considerations</name>
<t>This entire document is updated instructions to IANA. <t>This entire document is updated instructions to IANA.
</t> </t>
</section> </section>
<section numbered="true" toc="default"> <section numbered="true" toc="default">
<name>Security Considerations</name> <name>Security Considerations</name>
<t>This update does not change the Security Considerations in RFC 3405 <t>This update does not change the security considerations in
<xref target="RFC3405">RFC 3405</xref>.
</t> </t>
</section> </section>
</middle> </middle>
<!-- *****BACK MATTER ***** -->
<back> <back>
<references> <references>
<name>References</name> <name>References</name>
<references> <references>
<name>Normative References</name> <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. <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.
xml"> xml"/>
<front> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.
<title>Key words for use in RFCs to Indicate Requirement Levels</tit xml"/>
le> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3405.
<seriesInfo name="DOI" value="10.17487/RFC2119"/> xml"/>
<seriesInfo name="RFC" value="2119"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7595.
<seriesInfo name="BCP" value="14"/> xml"/>
<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 sig
nify the requirements in the specification. These words are often capitalized.
This document defines these words as they should be interpreted in IETF document
s. 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/r
fc8174">
<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 proto
col specifications. This document aims to reduce the ambiguity by clarifying tha
t 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 Ass
ignment 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 "D
ynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS" (RFC
3401). It is very important to note that it is impossible to read and understan
d any document in this series without reading the others. This document specifie
s an Internet Best Current Practices for the Internet Community, and requests di
scussion 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 Identifi
er (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>
</references> </references>
<references> <references>
<name>Informative References</name> <name>Informative References</name>
<reference anchor="RFC2717" target="https://www.rfc-editor.org/info/rfc271 <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2717.
7"> xml"/>
<front> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4395.
<title>Registration Procedures for URL Scheme Names</title> xml"/>
<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/rfc439
5">
<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 defin
ition 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 Communit
y, and requests discussion and suggestions for improvements.
</t>
</abstract>
</front>
<seriesInfo name="RFC" value="4395"/>
<seriesInfo name="DOI" value="10.17487/RFC4395"/>
</reference>
</references> </references>
</references> </references>
</back> </back>
</rfc> </rfc>
 End of changes. 16 change blocks. 
185 lines changed or deleted 56 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/