0.2: namespace update

git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@2325 4b5297f7-1745-476d-ba37-a9c6900126ab

xep-0225.xml

@@ -19,8 +19,14 @@
   </dependencies>
   <supersedes/>
   <supersededby/>
-  <shortname>NOT YET ASSIGNED</shortname>
+  <shortname>component</shortname>
   &stpeter;
+  <revision>
+    <version>0.2</version>
+    <date>2008-10-06</date>
+    <initials>psa</initials>
+    <remark><p>Modified namespace to incorporate namespace versioning; clarified that the value of the &lt;hostname/&gt; element can be either &lt;domain&gt; or &lt;domain/resource&gt;.</p></remark>
+  </revision>
   <revision>
     <version>0.1</version>
     <date>2007-08-08</date>
@@ -63,7 +69,7 @@
 </section1>
 <section1 topic='Hostname Binding' anchor='bind'>
   <p>The protocol defined in <cite>XEP-0114</cite> depended on use of the 'to' address in the stream header to specify the hostname of the component. By contrast, client-to-server connections use stream establishment is followed by binding of a resource to the stream (in fact multiple resources can be bound to the stream). This protocol emulates client-to-server connections by using a hostname binding process that is similar to the resource binding process specified in XMPP Core.</p>
-  <p>If a server offers component binding over a stream, it MUST advertise a feature of "urn:xmpp:tmp:component".</p>
+  <p>If a server offers component binding over a stream, it MUST advertise a feature of "urn:xmpp:component:0".</p>
   <example caption='Stream Feature'><![CDATA[
 S: <stream:stream
        from='example.com'
@@ -75,7 +81,7 @@ S: <stream:stream
        xmlns:stream='http://etherx.jabber.org/streams'>
 
 S: <stream:features>
-     <bind xmlns='urn:xmpp:tmp:component'>
+     <bind xmlns='urn:xmpp:component:0'>
        <required/>
      </bind>
    </stream:features>
@@ -83,19 +89,25 @@ S: <stream:features>
   <p>In order to bind a hostname, the component sends a bind request to the server.</p>
   <example caption='Bind Request'><![CDATA[
 C: <iq id='bind_1' type='set'>
-     <bind xmlns='urn:xmpp:tmp:component'>
+     <bind xmlns='urn:xmpp:component:0'>
        <hostname>chat.example.com</hostname>
      </bind>
    </iq>
   ]]></example>
-  <p>If the hostname can be bound, the server MUST return an IQ-result.</p>
+  <p>If the hostname can be bound, the server MUST return an IQ-result specifying the exact hostname that was bound.</p>
   <example caption='Bind Result'><![CDATA[
-S: <iq id='bind_1' type='result'/>
+S: <iq id='bind_1' type='result'>
+     <bind xmlns='urn:xmpp:component:0'>
+       <hostname>chat.example.com</hostname>
+     </bind>
+   </iq>
   ]]></example>
+  <p>If the hostname cannot be bound, the server MUST return an IQ-error, which SHOULD be &badrequest;, &conflict;, &notallowed;, or &constraint;, just as with client resource binding as specified in <cite>RFC 3920</cite>.</p>
+  <p>Note: Although the JID asserted during STARTTLS and SASL negotiation MUST be of the form &lt;domain&gt; (i.e., an XMPP domain identifier), the &lt;hostname/&gt; element MAY be of the form &lt;domain/resource&gt;. This form can be used for application-specific functionality (e.g., load balancing), but such functionality is out of scope for this specification.</p>
   <p>A component can send a subsequent bind request to bind another hostname (a server MUST support binding of multiple hostnames).</p>
   <example caption='Another Bind Request'><![CDATA[
 C: <iq id='bind_2' type='set'>
-     <bind xmlns='urn:xmpp:tmp:component'>
+     <bind xmlns='urn:xmpp:component:0'>
        <hostname>foo.example.com</hostname>
      </bind>
    </iq>
@@ -104,7 +116,7 @@ C: <iq id='bind_2' type='set'>
   <p>A component can also unbind a resource that has already been bound (a server MUST support unbinding).</p>
   <example caption='Unbind Request'><![CDATA[
 C: <iq id='unbind_1' type='set'>
-     <unbind xmlns='urn:xmpp:tmp:component'>
+     <unbind xmlns='urn:xmpp:component:0'>
        <hostname>foo.example.com</hostname>
      </unbind>
    </iq>
@@ -114,9 +126,6 @@ C: <iq id='unbind_1' type='set'>
 S: <iq id='unbind_1' type='result'/>
   ]]></example>
 </section1>
-<section1 topic='Examples' anchor='examples'>
-  <p>Further examples to follow.</p>
-</section1>
 <section1 topic='Security Considerations' anchor='security'>
   <p>This protocol improves upon the earlier component protocol defined in <cite>XEP-0114</cite> by specifying the use of Transport Layer Security (TLS) for channel encryption and the Simple Authentication and Security Layer (SASL) for authentication. Because this protocol re-uses the XML stream establishment processes defined in XMPP Core, the security considerations from RFC 3920 and rfc3920bis apply to this protocol as well.</p> 
 </section1>
@@ -124,8 +133,15 @@ S: <iq id='unbind_1' type='result'/>
   <p>This document requires no interaction with &IANA;.</p>
 </section1>
 <section1 topic='XMPP Registrar Considerations' anchor='registrar'>
-  <section2 topic='Protocol Namespaces' anchor='ns'>
-    <p>Until this specification advances to a status of Draft, its associated namespace shall be "urn:xmpp:tmp:component"; upon advancement of this specification, the &REGISTRAR; shall issue a permanent namespace in accordance with the process defined in Section 4 of &xep0053;.</p>
+  <section2 topic='Protocol Namespaces' anchor='registrar-ns'>
+    <p>This specification defines the following XML namespace:</p>
+    <ul>
+      <li>urn:xmpp:component:0</li>
+    </ul>
+    <p>Upon advancement of this specification from a status of Experimental to a status of Draft, the &REGISTRAR; shall add the foregoing namespace to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.</p>
+  </section2>
+  <section2 topic='Protocol Versioning' anchor='registrar-versioning'>
+    <p>If the protocol defined in this specification undergoes a major revision that is not fully backward-compatible with an older version, or that contains significant new features, the XMPP Registrar shall increment the protocol version number found at the end of the XML namespaces defined herein, as described in Section 4 of <cite>XEP-0053</cite>.</p>
   </section2>
 </section1>
 <section1 topic='XML Schema' anchor='schema'>
@@ -134,8 +150,8 @@ S: <iq id='unbind_1' type='result'/>
 
 <xs:schema
     xmlns:xs='http://www.w3.org/2001/XMLSchema'
-    targetNamespace='urn:xmpp:tmp:component'
-    xmlns='urn:xmpp:tmp:component'
+    targetNamespace='urn:xmpp:component:0'
+    xmlns='urn:xmpp:component:0'
     elementFormDefault='qualified'>
 
   <xs:element name='bind'>