Added reference to Requirements for Encrypted Sessions
Added reference to Requirements for Encrypted Sessions; modified namespaces to reflect XMPP Registrar procedures regarding URN issuance.
After sending &formB; to Alice, Bob can assume that the ESession negotiation is complete.
This document requires no interaction with &IANA;.
+This document requires no interaction with &IANA;.
The ®ISTRAR; shall add 'urn:xmpp:esession#subscription' to its registry of protocol namespaces.
+Until this specification advances to a status of Draft, its associated namespace shall be "http://www.xmpp.org/extensions/xep-0187.html#ns"; upon advancement of this specification, the ®ISTRAR; shall issue a permanent namespace in accordance with the process defined in Section 4 of &xep0053;.
+Clarified error handling and recommended against sending to bare JIDs.
As specified in &rfc3920;, the XML streams used in XMPP are bound to TCP. Unfortunately, TCP connections can go down without the application (XMPP) layer knowing about it. The traditional approach to solving this issue has been to periodically send so-called "whitespace pings" over the XML stream. This document recommends a more XML-friendly approach, which can also be used with other bindings such as the &xep0124; method for which &xep0206; is the XMPP profile.
+As specified in &rfc3920;, the XML streams used in XMPP are bound to TCP. Unfortunately, TCP connections can go down without the application (XMPP) layer knowing about it. The traditional approach to solving this issue has been to periodically send so-called "whitespace pings" over the XML stream. This document recommends a more XML-friendly approach, which can be used over more than one hop in the communication path (e.g., from one client to another) and can also be used with other bindings such as the &xep0124; method for which &xep0206; is the XMPP profile.
This specification addresses the following requirements:
@@ -72,11 +78,11 @@If the client supports the ping namespace, it MUST return an IQ result:
+If the client supports the ping namespace, it MUST return an IQ-result, which functions as a "pong":
If the client does not support the ping namespace, it MUST return an IQ error, which SHOULD be &unavailable;:
+If the client does not support the ping namespace, it MUST return a &unavailable; error:
The other error conditions defined in RFC 3920 could also be returned if appropriate.
A client may also ping its server by sending an &IQ; get over the stream between the two entities.
+A client may also ping its server by sending an IQ-get over the stream between the two entities.
Note: The client MAY include a 'to' address of the client's bare JID (&BAREJID;, in this instance "juliet@capulet.lit" or MAY include no 'to' address (this signifies that the stanza shall be handled by the server on behalf of the connected user's bare JID, which in the case of &IQ; stanzas is equivalent to directing the IQ-get to the server itself).
-If the server supports the ping namespace, it MUST return an IQ result:
+If the server supports the ping namespace, it MUST return an IQ-result:
If the server does not support the ping namespace, it MUST return an IQ error, which SHOULD be &unavailable;:
+If the server does not support the ping namespace, it MUST return a &unavailable; error:
The other error conditions defined in RFC 3920 could also be returned if appropriate.
Pings can also be used to test a server-to-server connection. This is done by sending an &IQ; get over the stream from one server to another.
+Pings can also be used to test a server-to-server connection. This is done by sending an IQ-get over the stream from one server to another.
If the other party to the stream supports the ping namespace, it MUST return an IQ result:
+If the other party to the stream supports the ping namespace, it MUST return an IQ-result:
If the other party to the stream does not support the ping namespace, it MUST return an IQ error, which SHOULD be &unavailable;:
+If the other party to the stream does not support the ping namespace, it MUST return a &unavailable; error:
If the pinged entity supports the ping namespace, it SHOULD return an IQ result:
+Note: The 'to' address should be a full JID (&FULLJID;), since a ping sent to a bare JID (&BAREJID;) will be handled by the server on behalf of the client.
+If the pinged entity supports the ping namespace, it SHOULD return an IQ-result:
If the pinged entity does not support the ping namespace, it SHOULD return an IQ error, which SHOULD be &unavailable;:
+If the pinged entity does not support the ping namespace, it MUST return a &unavailable; error:
If the pinged entity supports the ping namespace, it SHOULD return an IQ result:
+Note: The 'to' address should be a full JID (&FULLJID;), since a ping sent to a bare JID (&BAREJID;) will be handled by the server on behalf of the client.
+If the pinged entity supports the ping namespace, it SHOULD return an IQ-result:
If the pinged entity does not support the ping namespace, it SHOULD return an IQ error, which SHOULD be &unavailable;:
+If the pinged entity does not support the ping namespace, it MUST return a &unavailable; error: