Browse Source

change states to match IANA / RFC 7595

Peter Saint-Andre 2 years ago
parent
commit
bcb2938ff8
2 changed files with 10 additions and 3 deletions
  1. 9
    3
      xep-0053.xml
  2. 1
    0
      xep.ent

+ 9
- 3
xep-0053.xml View File

@@ -19,6 +19,12 @@
19 19
   <supersededby/>
20 20
   <shortname>N/A</shortname>
21 21
   &stpeter;
22
+  <revision>
23
+    <version>1.7</version>
24
+    <date>2016-12-01</date>
25
+    <initials>psa</initials>
26
+    <remark><p>Modify registration status names to be consistent with IANA terminology (Provisional, Permanent, Historical).</p></remark>
27
+  </revision>
22 28
   <revision>
23 29
     <version>1.6</version>
24 30
     <date>2016-11-04</date>
@@ -100,7 +106,7 @@
100 106
 </section1>
101 107
 <section1 topic='Registry Creation and Maintenance' anchor='registries'>
102 108
   <p>Every XMPP Extension Protocol specification (XEP) must contain a section devoted to "XMPP Registrar Considerations", detailing the namespaces and parameters to be registered with the XMPP Registrar, as well as any new registries to be created as a result of the XEP.</p>
103
-  <p>Registry entries have a status of 'Proposed', 'Standard', or 'Deprecated'. Entries of an experimental XEP are added by the XMPP Registar to the registry in the 'Proposed' Status. The registry additions or creations specified in a XEP shall not transition to 'Standard' status until the document advances to a status of Draft (Standards-Track XEPs) or Active (Informational and Historical XEPs). When an XEP transitions to a status of 'Deprecated' or 'Obsolete' the editor will transition its registry entries to a status of 'Deprecated'. Registration of namespaces shall be handled as described in the <link url='#namespaces'>Namespace Issuance</link> section of this document. Registration of particular parameters used within a specification shall be initiated by the XMPP Extensions Editor if specified in the XEP, and may also be initiated by implementors of the XEP after it has advanced to Active, Draft, or Final. Creation of new registries shall be initiated by the XMPP Registrar; if a document specifies the creation of a new registry, the author is strongly encouraged to consult with the XMPP Registrar before seeking a Last Call on the XEP.</p>
109
+  <p>Registry entries have a status of 'Provisional', 'Permanent', or 'Historical' (as with certain IANA registries, such as the URI schemes registry governed by &rfc7595;). Entries of an experimental XEP are added by the XMPP Registar to the registry in the 'Provisional' Status. The registry additions or creations specified in a XEP shall not transition to 'Permanent' status until the document advances to a status of Draft (Standards-Track XEPs) or Active (Informational and Historical XEPs). When an XEP transitions to a status of 'Deprecated' or 'Obsolete' the editor will transition its registry entries to a status of 'Historical'. Registration of namespaces shall be handled as described in the <link url='#namespaces'>Namespace Issuance</link> section of this document. Registration of particular parameters used within a specification shall be initiated by the XMPP Extensions Editor if specified in the XEP, and may also be initiated by implementors of the XEP after it has advanced to Active, Draft, or Final. Creation of new registries shall be initiated by the XMPP Registrar; if a document specifies the creation of a new registry, the author is strongly encouraged to consult with the XMPP Registrar before seeking a Last Call on the XEP.</p>
104 110
   <p>Requests for parameter assignments must be sent to the XMPP Registrar in accordance with the process specified in the document (usually a XEP) that defines the relevant registry, normally by sending an appropriately formatted email message to the URI &lt;mailto:registrar&#64;xmpp.org&gt;. If, in the Registrar's judgment, discussion of a request is required, the Registrar shall initiate such discussion within the &SSIG;. The Registrar shall add registry items at its discretion based on discussion within the Standards SIG if necessary, but shall not unduly restrict registration of parameter values. If a document author or implementor thinks that a request was unfairly denied by the Registrar, an appeal of the decision may be directed to the XMPP Council.</p>
105 111
   <p>The XMPP Registrar shall maintain registries of assigned namespaces and parameters at &lt;<link url="http://www.xmpp.org/registrar/">http://www.xmpp.org/registrar/</link>&gt; and shall update those registries in a timely fashion. Changes to the registries shall be announced on the &lt;standards&#64;xmpp.org&gt; mailing list.</p>
106 112
 </section1>
@@ -108,13 +114,13 @@
108 114
   <p>The XMPP Registrar shall be responsible for issuing namespaces to be used in XMPP Extension Protocols (XEPs) developed through the XMPP Standards Foundation's standards process as specified in <cite>XEP-0001</cite>. The policies and procedures for namespace issuance shall be as follows:</p>
109 115
   <ol start='1'>
110 116
     <li>
111
-      <p>When a XEP is first published in the Experimental state, the XMPP Registrar shall work with the author(s) to mint an appropriate namespace name, which shall be of the form "urn:xmpp:ShortName:0" or, where appropriate, "urn:xmpp:ShortName:SubName:0". The newly minted name shall be added by the XMPP Registrar as 'Proposed' to the registry. The following considerations apply:</p>
117
+      <p>When a XEP is first published in the Experimental state, the XMPP Registrar shall work with the author(s) to mint an appropriate namespace name, which shall be of the form "urn:xmpp:ShortName:0" or, where appropriate, "urn:xmpp:ShortName:SubName:0". The newly minted name shall be added by the XMPP Registrar as 'Provisional' to the registry. The following considerations apply:</p>
112 118
       <ol style='list-style: lower-alpha'>
113 119
         <li>Each name shall adhere to the format defined in &rfc4854;.</li>
114 120
         <li>Each name shall be of the form "urn:xmpp:ShortName[:SubName]".</li>
115 121
         <li>The "ShortName" string shall be unique within the XMPP URN tree and any "SubName" strings shall be unique within the scope of the ShortName.</li>
116 122
         <li>Each name should be relevant and memorable. Names may be determined in consultation with the author(s) of the XEP and may be requested by the author(s) in the XMPP Registrar Considerations section of the XEP; however, the issuance of namespace names is the sole responsibility of the XMPP Registrar, which may modify or ignore any names requested.</li>
117
-        <li>To ensure that no duplicate names are issued, each name to be minted shall be checked against the registry of registered names issued in both states: 'Proposed' and 'Standard'.</li>
123
+        <li>To ensure that no duplicate names are issued, each name to be minted shall be checked against the registry of registered names issued in all states ('Provisional', 'Permanent', and 'Historical').</li>
118 124
         <li>The XMPP Registrar shall issue all XMPP URNs directly and shall not assign secondary responsibility for management of any sub-trees.</li>
119 125
       </ol>
120 126
     </li>

+ 1
- 0
xep.ent View File

@@ -651,6 +651,7 @@ THE SOFTWARE.
651 651
 <!ENTITY rfc6920 "<span class='ref'><link url='http://tools.ietf.org/html/rfc6920'>RFC 6920</link></span> <note>RFC 6920: Naming Things with Hashes &lt;<link url='http://tools.ietf.org/html/rfc6920'>http://tools.ietf.org/html/rfc6920</link>&gt;.</note>" >
652 652
 <!ENTITY rfc7081 "<span class='ref'><link url='http://tools.ietf.org/html/rfc7081'>RFC 7081</link></span> <note>RFC 7081: CUSAX: Combined Use of the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP) &lt;<link url='http://tools.ietf.org/html/rfc7081'>http://tools.ietf.org/html/rfc7081</link>&gt;.</note>" >
653 653
 <!ENTITY rfc7572 "<span class='ref'><link url='http://tools.ietf.org/html/rfc7572'>RFC 7572</link></span> <note>RFC 7572: Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Instant Messaging &lt;<link url='http://tools.ietf.org/html/rfc7572'>http://tools.ietf.org/html/rfc7572</link>&gt;.</note>" >
654
+<!ENTITY rfc7595 "<span class='ref'><link url='http://tools.ietf.org/html/rfc7595'>RFC 7595</link></span> <note>RFC 7595: Guidelines and Registration Procedures for URI Schemes &lt;<link url='http://tools.ietf.org/html/rfc7595'>http://tools.ietf.org/html/rfc7595</link>&gt;.</note>" >
654 655
 <!ENTITY rfc7613 "<span class='ref'><link url='http://tools.ietf.org/html/rfc7613'>RFC 7613</link></span> <note>RFC 7613: Preparation, Enforcement, and Comparison of Internationalized Strings Representing Usernames and Passwords&lt;<link url='http://tools.ietf.org/html/rfc7613'>http://tools.ietf.org/html/rfc7613</link>&gt;.</note>" >
655 656
 <!ENTITY rfc7622 "<span class='ref'><link url='http://tools.ietf.org/html/rfc7622'>RFC 7622</link></span> <note>RFC 7622: Extensible Messaging and Presence Protocol (XMPP): Address Format &lt;<link url='http://tools.ietf.org/html/rfc7622'>http://tools.ietf.org/html/rfc7622</link>&gt;.</note>" >
656 657
 <!ENTITY rfc7627 "<span class='ref'><link url='http://tools.ietf.org/html/rfc7627'>RFC 7627</link></span> <note>RFC 7627: Transport Layer Security (TLS) Session Hash and Extended Master Secret Extension &lt;<link url='http://tools.ietf.org/html/rfc7627'>http://tools.ietf.org/html/rfc7627</link>&gt;.</note>" >

Loading…
Cancel
Save