From 825cf1bfa513d5992edba495da3e383f72875d64 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Mon, 6 Oct 2008 19:28:27 +0000 Subject: [PATCH] 0.2: namespace update git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@2325 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0225.xml | 46 +++++++++++++++++++++++++++++++--------------- 1 file changed, 31 insertions(+), 15 deletions(-) diff --git a/xep-0225.xml b/xep-0225.xml index d4c1e06d..a46ea59e 100644 --- a/xep-0225.xml +++ b/xep-0225.xml @@ -19,8 +19,14 @@ - NOT YET ASSIGNED + component &stpeter; + + 0.2 + 2008-10-06 + psa +

Modified namespace to incorporate namespace versioning; clarified that the value of the <hostname/> element can be either <domain> or <domain/resource>.

 + 0.1 2007-08-08 @@ -63,7 +69,7 @@

The protocol defined in XEP-0114 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.

-

If a server offers component binding over a stream, it MUST advertise a feature of "urn:xmpp:tmp:component".

+

If a server offers component binding over a stream, it MUST advertise a feature of "urn:xmpp:component:0".

S: - + @@ -83,19 +89,25 @@ S:

In order to bind a hostname, the component sends a bind request to the server.

- + chat.example.com ]]> -

If the hostname can be bound, the server MUST return an IQ-result.

+

If the hostname can be bound, the server MUST return an IQ-result specifying the exact hostname that was bound.

+S: + + chat.example.com + + ]]> +

If the hostname cannot be bound, the server MUST return an IQ-error, which SHOULD be &badrequest;, &conflict;, ¬allowed;, or &constraint;, just as with client resource binding as specified in RFC 3920.

+

Note: Although the JID asserted during STARTTLS and SASL negotiation MUST be of the form <domain> (i.e., an XMPP domain identifier), the <hostname/> element MAY be of the form <domain/resource>. This form can be used for application-specific functionality (e.g., load balancing), but such functionality is out of scope for this specification.

A component can send a subsequent bind request to bind another hostname (a server MUST support binding of multiple hostnames).

- + foo.example.com @@ -104,7 +116,7 @@ C:

A component can also unbind a resource that has already been bound (a server MUST support unbinding).

- + foo.example.com @@ -114,9 +126,6 @@ C: S: ]]> - -

Further examples to follow.

-

This protocol improves upon the earlier component protocol defined in XEP-0114 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.

 @@ -124,8 +133,15 @@ S:

This document requires no interaction with &IANA;.

- -

Until this specification advances to a status of Draft, its associated namespace shall be "urn:xmpp:tmp:component"; upon advancement of this specification, the ®ISTRAR; shall issue a permanent namespace in accordance with the process defined in Section 4 of &xep0053;.

+ +

This specification defines the following XML namespace:

+
    +
  • urn:xmpp:component:0
    • +
+

Upon advancement of this specification from a status of Experimental to a status of Draft, the ®ISTRAR; shall add the foregoing namespace to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.

+ + +

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 XEP-0053.

 @@ -134,8 +150,8 @@ S: