From 81509563eefef4fc95c7d819342bee03a0405082 Mon Sep 17 00:00:00 2001 From: stpeter Date: Thu, 14 Apr 2011 11:18:55 -0600 Subject: [PATCH] 0.7 --- xep-0220.xml | 40 ++++++++++++++++++++++------------------ 1 file changed, 22 insertions(+), 18 deletions(-) diff --git a/xep-0220.xml b/xep-0220.xml index db097937..cd66becd 100644 --- a/xep-0220.xml +++ b/xep-0220.xml @@ -27,6 +27,12 @@ Hancke fippo@psyced.org + + 0.7 + 2011-04-14 + ph/psa +

Removed stream feature for advertising mere protocol support, using it only for advertising support for enhanced error handling.

 + 0.6 2011-04-13 @@ -391,30 +397,28 @@ send: -

Support for the server dialback protocol can be indicated in two ways:

-
    -
  • By inclusion of the server dialback feature in a given set of stream features.
    • -
  • By inclusion of the dialback namespace declaration in the stream header.
    • -
-

The former method is preferred, and XMPP 1.0 servers MUST support and send the stream feature. However, the latter method is also specified herein for the purpose of backward-compatibility with older "XMPP 0.9" deployments.

-

The server dialback stream feature is advertised by including in any given set of stream features a <dialback/> element qualified by the 'urn:xmpp:features:dialback' namespace; the element MAY also include an empty <errors/> element, indicating that the entity sending the stream features supports graceful handling of dialback errors as described in Section 2.4.

- - - - - - ]]> -

Note: If the Sender Domain was authenticated using SASL, the <dialback/> element SHOULD NOT be present in stream features. If a server offers both SASL and dialback, dialback SHOULD be mandatory-to-negotiate and SASL SHOULD be voluntary-to-negotiate as those terms are described in RFC 6120.

-

As mentioned, support for the server dialback protocol can also be advertised by including the dialback namespace declaration in a stream header.

- +

Support for the server dialback protocol is indicated by inclusion of the dialback namespace declaration in the stream header.

+ - ]]> + ]]> +

Although this method of advertising protocol support has been superseded by the use of stream features as originally defined in RFC 3920, the server dialback protocol predates the existence of stream features and therefore the namespace declaration method is still used in this instance.

+ + +

If a server supports graceful handling of dialback errors as described in Section 2.4, it MUST advertise that via a stream feature which is a <dialback/> element qualified by the 'urn:xmpp:features:dialback' namespace, including an empty <errors/> element.

+ + + + + + ]]> +