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

<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
    <!ENTITY rfc2119 PUBLIC '' 
      'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml'>
]>

<rfc category="bcp" ipr="trust200902" docName="draft-blanchet-urn-ianachange-00.txt" updates="3406">

<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>

<?rfc toc="yes" ?>
<?rfc symrefs="yes" ?>
<?rfc sortrefs="yes"?>
<?rfc iprnotified="no" ?>
<?rfc strict="yes" ?>
<?rfc compact="yes" ?>

<front>
<title abbrev="URN Formal Namespace Registration">Uniform Resource Names (URN) Formal Namespace IANA Registration</title>
<author initials='M.' surname="Blanchet" fullname='Marc Blanchet'>
  <organization>Viagenie</organization>
  <address>
    <postal>
      <street>246 Aberdeen</street>
      <city>Quebec</city>
      <region>QC</region>
      <code>G1R 2E1</code>
      <country>Canada</country>
    </postal>
    <email>Marc.Blanchet@viagenie.ca</email>
    <uri>http://viagenie.ca</uri>
  </address>
</author>
<date/>
<abstract>
<t>Per RFC3406, Uniform Resource Names formal namespace identifier (NID) registration requires the publication of an RFC from the requestor. Experience shows that this requirement is too high. This document updates the IANA registration policy for formal NID to Expert review.</t>
</abstract>
</front>
<middle>
<section title="Introduction">
 <t>Per <xref target="RFC3406"/>, Uniform Resource Names(URN) formal namespace identifier (NID) registration requires the publication of an RFC from the requestor. Experience shows that this requirement is too high. This document updates the IANA registration policy for formal NID.</t>
<t>This document only updates the registration policy of the formal namespace, as described in section 4.3 of <xref target="RFC3406"/>.</t>
</section>
<section title="Formal Namespace Registration Policy">
<t>This section replaces section 4.3 of <xref target="RFC3406"/>.</t>
<t>Formal NIDs are assigned by IANA through Expert Review, as defined in <xref target="RFC5226"/>.</t>
<t>The requested NID string must:
<list>
 <t>not be an already-registered NID</t>
 <t>not start with "x-"</t>
 <t>not start with "urn-"</t>
 <t>not start with "XY-", where XY is any combination of 2 ASCII letters (see NOTE, below)</t>
 <t>be more than 2 letters long</t>
</list>
</t>
<t>NOTE: ALL two-letter combinations, and two-letter combinations
   followed by "-" and any sequence of valid NID characters are reserved
   for potential use as countrycode-based NIDs for eventual national
   registrations of URN namespaces.  The definition and scoping of rules
   for allocation of responsibility for such namespaces is beyond the
   scope of this document.</t>
</section>
<section title="URN Namespace Definition Template">
<t>To request a registration, the requestor fills out the template in Appendix A of <xref target="RFC3406"/> and send it to IANA.</t>
</section>
<section title="IANA Considerations">
 <t>This document updates the registration policy for URN formal namespaces.</t>
</section>
</middle>
<back>
 <references title="Normative References">
  <?rfc include="reference.RFC.3406" ?>
  <?rfc include="reference.RFC.5226" ?>
 </references>
</back>
</rfc>
