<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE xep SYSTEM 'xep.dtd' [
  <!ENTITY % ents SYSTEM 'xep.ent'>
%ents;
]>
<?xml-stylesheet type='text/xsl' href='xep.xsl'?>
<xep>
<header>
  <title>Extensible SASL Profile</title>
  <abstract>This document describes a replacement for the SASL profile documented in RFC 6120 which allows for greater extensibility.</abstract>
  &LEGALNOTICE;
  <number>0388</number>
  <status>Experimental</status>
  <type>Standards Track</type>
  <sig>Standards</sig>
  <dependencies>
    <spec>XMPP Core</spec>
  </dependencies>
  <supersedes/>
  <supersededby/>
  <shortname>sasl2</shortname>
  &dcridland;
  <revision>
    <version>0.2.1</version>
    <date>2017-08-24</date>
    <initials>dwd</initials>
    <remark>
      <ul>
          <li>That's a lot of XML errors. Sorry.</li>
          <li>Clarified whose additional-data this is.</li>
          <li>&lt;next> uses &lt;initial-response>.</li>
          <li>Added a bunch of example flows.</li>
      </ul>
    </remark>
  </revision>
  <revision>
    <version>0.2.0</version>
    <date>2017-08-14</date>
    <initials>dwd</initials>
    <remark>
      <p>Updated according to implementation experience:</p>
      <ul>
	      <li>Updated namespace</li>
	      <li>Continue "mechanisms" are not; changed these to "tasks".</li>
	      <li>Added stream features after Success.</li>
	      <li>Don't need complexity of "=" encoding; removed.</li>
	      <li>Fixed internal links.</li>
	      <li>Updated examples.</li>
      </ul>
    </remark>
  </revision>
  <revision>
    <version>0.1.0</version>
    <date>2017-03-16</date>
    <initials>XEP Editor (ssw)</initials>
    <remark>
      <ul>
        <li>Move to experimental.</li>
      </ul>
    </remark>
  </revision>
  <revision>
    <version>0.0.1</version>
    <date>2017-02-07</date>
    <initials>dwd</initials>
    <remark>
      <ul>
        <li>Initial Revision</li>
      </ul>
    </remark>
  </revision>
</header>

<section1 topic='Introduction' anchor='intro'>
  <p>While SASL provides an excellent framework that has served us well over the past 18 years, a number of shortcomings in the profile - the syntax binding to XMPP - that is in use.</p>
  <p>This specification addresses a number of shortfalls:</p>
  <ul>
    <li>Number of round trips</li>
    <li>Extensibility</li>
    <li>Support for second factor</li>
    <li>Support for mandatory password changes</li>
  </ul>
  <p>The new SASL profile documented herein is primarily a syntactic change to allow extensibility, combined with removal of the (largely) redundant stream restart, and additional results beyond total success or abject failure.</p>
  <section2 topic="Terminology">
    <p>Although initiating entities, in general, use SASL, and receiving entities offer it, the SASL specification and common parlance both use "Client " and "Server"; this specification uses Client and Server and assumes C2S links. This is not intended to preclude use of this SASL profile on S2S links. The term "SASL2" is used to mean the new SASL profile specified in this document; however the same RFC 4422 definition of SASL (and SASL profiles) applies.</p>
    <p>Examples often use hypothetical SASL mechanisms and sub-extensions; this specification does not intend to make a position on any particular SASL mechanism, and the Mandatory To Implement mechanisms are unaffected.</p>
  </section2>
</section1>

<section1 topic='Overview' anchor="overview">
  <section2 topic="Discovering Support" anchor="feature">
    <p>Servers capable of SASL2 offer a stream feature of &lt;mechanisms/>, qualified by the "urn:xmpp:sasl:1" namespace. This in turn contains one or more &lt;mechanism/> elements in the same namespace, and potentially other elements (for example, the &lt;hostname/> element defined within XEP-0233).</p>
    <p>Note that SASL2 is impossible for clients to initiate without at least one mechanism being available, and therefore MUST NOT be offered.</p>
    <p>The feature so advertised, and its child content, SHOULD be stable for the given stream to and from attributes and encryption state, and therefore MAY be cached by clients for later connections.</p>
    <p>The Service Name used by XMPP is unchanged from RFC 6120.</p>
  </section2>
  <section2 topic="SASL Data Encoding">
    <p>In all cases, both Clients and Servers encode SASL exchanges using Base 64 encoding. This SHOULD NOT include any line wrapping or other whitespace. As the form &lt;element/> is equivalent to &lt;element>&lt;/element>, these both indicate an empty string. Challenges and responses with no data do not occur in SASL, and so require no special handling. To indicate the absence of an initial response, or the absence of success data, the element is simply not included.</p>
  </section2>
  <section2 topic="Initiation">
    <p>Clients, upon observing this stream feature, initiate the authentication by the use of the &lt;authenticate/> top-level element, within the same namespace. The nature of this element is to inform the server about properties of the final stream state, as well as initiate authentication itself. To achieve the latter, it has a single mandatory attribute of "mechanism", with a string value of a mechanism name offered by the Server in the stream feature, and an optional child element of &lt;initial-response/>, containing a base64-encoded SASL Initial Response.</p>
    <p>On subsequent connections, if a Client has previously cache the stream feature, the Client MAY choose to send it before seeing the stream features - sending it "pipelined" with the Stream Open tag for example.</p>
    <example caption="An authentication request"><![CDATA[
<authenticate xmlns='urn:xmpp:sasl:1' mechanism="BLURDLYBLOOP">
  <initial-response>Tm9ib2R5IGV2ZXIgZGVjb2RlcyB0aGUgZXhhbXBsZXMu</initial-response>
</authenticate>
]]>
    </example>
    <p>In order to provide support for other desired stream states beyond authentication, additional child elements are used. For example, a hypothetical XEP-0198 session resumption element might be included, and/or Resource Binding requests.</p>
    <example caption="An authentication request with a (hypothetical) bind request"><![CDATA[
<authenticate xmlns='urn:xmpp:sasl:1' mechanism='BLURDYBLOOP'>
  <initial-response>
    SSBzaG91bGQgbWFrZSB0aGlzIGEgY29tcGV0aXRpb24=
  </initial-response>
  <bind xmlns='urn:xmpp:bind:example'/>
</authenticate>
]]>
    </example>
  </section2>
  <section2 topic="Challenges and Responses" anchor="challenge">
    <p>Server Challenges MAY then be sent. Each Challenge MUST be responded to by a Client in a Client Response. These are not extensible, and contain the corresponding base64 encoded SASL data:</p>
    <example caption="A challenge and response exchange"><![CDATA[
<!-- A server might send: -->
<challenge xmlns='urn:xmpp:sasl:1'>
  U28sIG5leHQgRk9TREVNIC0gMjAxOCwgdGhhdCBpcy4uLg==
</challenge>

<!-- A client might respond: -->
<response xmlns='urn:xmpp:sasl:1'>
  Li4uSSdsbCBidXkgYSBiZWVyIGZvciB0aGUgZmlyc3QgcGVyc29uIHdoby4uLg==
</response>
]]>
    </example>
  </section2>
  <section2 topic="During Authentication">
    <p>At any time while authentication is in progress, neither Client nor Server sends any element (including stanzas) or other data except the top-level elements defined herein. Clients MUST NOT send whitespace, and MUST send only &lt;response/> elements as appropriate or an &lt;abort/> element to immediately cause an error. Servers MUST disconnect Clients immediately if any other traffic is received. Servers are similarly REQUIRED to send no whitespace, and only the &lt;response/> and completion elements from the section below.</p>
  </section2>
  <section2 topic="Completing Authentication">
    <p>Authentication may complete in one of three ways. It may complete successfully, in which case the client is authenticated. It may also fail, in which case the client is not authenticated and the stream and session state remain entirely unchanged.</p>
    <p>Finally, it may have completed successfully, but further interaction is required - for example, a password change or second-factor authentication.</p>
    <section3 topic="Success">
      <p>If the Client is now authenticated, the Server sends a &lt;success/> element, which contains contains an &lt;authorization-identity/> element containing the negotiated identity - this is a bare JID, unless resource binding has occurred, in which case it is a full JID.</p>
      <p>It MAY contain an &lt;additional-data> element, containing additional data from the exchange (task or SASL mechanism) that has just completed.</p>
      <example caption="Successful authentication"><![CDATA[
<success xmlns='urn:xmpp:sasl:1'>
  <additional-data>
    ip/AeIOfZXKBV+fW2smE0GUB3I//nnrrLCYkt0Vj
  </additional-data>
  <authorization-identifier>juliet@montague.example/Balcony/a987dsh9a87sdh</authorization-identifier>
</success>
]]></example>
      <p>Other extension elements MAY also be contained by the &lt;success/> element.</p>
      <example caption="Successful re-authentication and resumption"><![CDATA[
<success xmlns='urn:xmpp:sasl:1'>
  <additional-data>
    SGFkIHlvdSBnb2luZywgdGhlcmUsIGRpZG4ndCBJPw==
  </additional-data>
  <authorization-identifier>juliet@montague.example/Balcony/a987dsh9a87sdh</authorization-identifier>
  <sm:resumed xmlns='urn:xmpp:sm:3:example' h='345' previd='124'/>
</success>
]]></example>
      <p>Any security layer negotiated SHALL take effect after the ">" octet of the closing tag (ie, immediately after "&lt;/success>"), if it has not already taken effect at a &lt;continue> - see <link url='#continue'>Continue</link> below.</p>
      <p>The &lt;success> element is immediately followed by a &lt;features> element containing the applicable stream features of the newly authenticated stream. Note that no stream restart occurs.</p>
    </section3>
    <section3 topic="Failure">
      <p>A &lt;failure/> element is used by the server to terminate the authentication attempt. It MAY contain application-specific error codes, and MAY contain a textual error. It MUST contain one of the SASL error codes from RFC 6120 Section 6.5.</p>
      <example caption="Failure"><![CDATA[
<failure xmlns='urn:xmpp:sasl:1'>
  <aborted xmlns='urn:ietf:params:xml:ns:xmpp-sasl'/>
  <optional-application-specific xmlns='urn:something:else'/>
  <text>This is a terrible example.</text>
</failure>
]]></example>
    </section3>
    <section3 topic="Continue" anchor="continue">
      <p>A &lt;continue/> element is used to indicate that while the SASL exchange was successful, it is insufficient to allow authentication at this time.</p>
      <p>This can be used to indicate that the Client needs to perform a Second Factor Authentication ("2FA"), or is required to change password.</p>
      <p>Such tasks are presented within a &lt;tasks> element, which contains a sequence of &lt;task> elements, each containing a name. These tasks are analogous to a SASL mechanism, but have a number of differences - they may never attempt to negotiate a new authorization identifier, nor a new security layer.</p>
      <p>A client MAY choose any one of the offered tasks; if multiple are required a sequence of &lt;continue> exchanges will occur until all mandatory tasks are complete.</p>
      <p>The &lt;continue element therefore always contains a &lt;tasks/> element, as defined above. It MAY contain an &lt;additional-data/> element, as the &lt;success/> element does.</p>
      <p>Finally, it MAY contain a &lt;text/> element, which can contain human-readable data explaining the nature of the step required.</p>
      <example caption="Continue Required"><![CDATA[
<continue xmlns='urn:xmpp:sasl:1'>
  <additional-data>
   SSdtIGJvcmVkIG5vdy4=
  </additional-data>
  <tasks>
    <task>HOTP-EXAMPLE</task>
    <task>TOTP-EXAMPLE</task>
  </tasks>
  <text>This account requires 2FA</text>
</continue>
]]></example>
      <p>After the final octet of the first &lt;continue> element, any SASL security layer negotiated in the preceding exchange SHALL be immediately in effect.</p>
      <p>Clients respond with a &lt;next/> element, which has a single mandatory attribute of "task", containing the selected task name, and contains an OPTIONAL base64 encoded initial response contained in an &lt;initial-response> element.</p>
      <example caption="Client Continues"><![CDATA[
<next xmlns='urn:xmpp:sasl:1' task='TOTP-EXAMPLE'>
  <initial-response>
    SSd2ZSBydW4gb3V0IG9mIGlkZWFzIGhlcmUu
  </initial-response>
</next-authenticate>
]]></example>
    </section3>
  </section2>
</section1>

  <section1 topic="SASL Profile Definition">
	  <p>This provides pointers and/or clarifications to the <link url="#overview">Overview</link> in the order and manner defined in RFC 4422, section 4.</p>
    <section2 topic="Service Name">
      <p>The service name SHALL be "xmpp", as defined by RFC 6120.</p>
    </section2>
    <section2 topic="Mechanism negotiation">
	    <p>Servers list mechanisms during stream features (See <link url="#features">Discovering Support</link>).</p>
    </section2>
    <section2 topic="Message Definitions">
      <section3 topic="Initiation">
	      <p>Clients initiate using the &lt;authenticate/> top level element (See <link url="#auth">Initiation</link>.</p>
      </section3>
      <section3 topic="Server Challenges and Client Responses">
	      <p>See <link url="#challenge">Challenges and Responses</link>.</p>
      </section3>
      <section3 topic="Outcome">
	      <p>See <link url="#outcome">Completing Authentication</link>.</p>
      </section3>
    </section2>
    <section2 topic="Non-Empty Authorization Strings">
      <p>If a Client specifies an authorization string which is non-empty, the identifier is normalized by treating it as a JID, and performing normalization as described in RFC 7622.</p>
      <p>In general, implementors are advised that a non-empty authorization string MAY be considered an error if the stream's from attribute (if present) does not match.</p>
    </section2>
    <section2 topic="Aborting">
	    <p>Clients MAY abort unilaterally by sending &lt;abort/> as specified in <link url="#abort">Client Aborts</link>.</p>
    <p>Servers MAY abort unliterally by sending &lt;failure/> with the &lt;aborted/> error code as defined in <link url="#failure">Failure</link>.</p>
    </section2>
    <section2 topic="Security Layer Effect">
	    <p>Security Layers take effect after the SASL mechanism itself (ie, the first negotiation) has completed successfully, after the final octet of the server's &lt;success> or &lt;continue>. See <link url="#success">Success</link> and <link url="#continue">Continue</link>.</p>
    </section2>
    <section2 topic="Security Layer Order">
      <p>Option (a) is used - any SASL Security Layer is applied first to data being sent, and TLS applied last.</p>
    </section2>
    <section2 topic="Multiple Authentication">
      <p>Although the &lt;continue/> concept does use tasks analogous to multiple SASL sequences, only the first SASL mechanism used is considered an authentication, and only the first can negotiate a security layer.</p>
      <p>In particular, once &lt;success/> has been sent by the server, any further &lt;authenticate/> element MUST result in a stream error.</p>
    </section2>
  </section1>

  <section1 topic="Example Flows">
    <p>This section provides a fictional example. It is important to note that many of the extensions used wihtin this section do not, in fact, exist and therefore are to be avoided.</p>
    <section2 topic="Syntactic Equivalence">
      <p>Where no additional features that SASL2 makes available are used, the flow of information is identical to the original SASL profile. This example shows the new syntax and draws the reader's attention to the differences.</p>
      <example caption="PLAIN Authentication"><![CDATA[
<!--
  Server sends stream features.
  These are identical to SASL1, but within a different namespace.
-->
<stream:features>
  <mechanisms xmlns='urn:xmpp:sasl:1'>
    <mechanism>PLAIN</mechanism>
    <mechanism>SCRAM-SHA-1</mechanism>
  </mechanisms>
</stream:features>

<!--
  Client intiates authentication.
  Beyond the element local name and namespace,
  the main distinction is that initial-response data is held within an element,
  so the "=" special case no longer applies.
-->
<authenticate xmlns='urn:xmpp:sasl:1' mechanism='PLAIN'>
  <initial-response>AGFsaWNlQGV4YW1wbGUub3JnCjM0NQ==</initial-response>
</authenticate>

<!--
  This completes in one step, so the Server sends a success.
  A SASL2 success always includes the authorization identifier:
-->
<success xmlns='urn:xmpp:sasl:1'>
  <authorization-identifier>alice@example.org</authorization-identifier>
</success>
<!--
  The server immediately sends a new set of stream features at this point.
  There is no stream restart.
-->
<stream:features>
  <bind xmlns='urn:ietf:params:xml:ns:xmpp-bind'>
    <required/>
  </bind>
</stream:features>

<!--
  The client now continues with resource binding.
-->
]]></example>
      <p>Use of SASL2 in this simple scenario saves one round-trip (due to the lack of stream restart).</p>
    </section2>
    <section2 topic="Once More, This Time With CRAM">
      <p>Again, this is an equivalent flow to a common SASL1 flow, although using the CRAM-MD5 mechanism which is (thankfully) rarely used in practise.</p>
      <example caption="CRAM-MD5 Authentication"><![CDATA[
<!--
  Server sends stream features.
-->
<stream:features>
  <mechanisms xmlns='urn:xmpp:sasl:1'>
    <mechanism>PLAIN</mechanism>
    <mechanism>CRAM-MD5</mechanism>
  </mechanisms>
</stream:features>

<!--
  Client intiates authentication.
  Here, no initial response is needed, so none is sent.
-->
<authenticate xmlns='urn:xmpp:sasl:1' mechanism='CRAM-MD5'/>

<!--
  CRAM-MD5 starts with a server challenge:
-->
<challenge xmlns='urn:xmpp:sasl:1'>
  PDE4OTYuNjk3MTcwOTUyQHBvc3RvZmZpY2UucmVzdG9uLm1jaS5uZXQ+
</challenge>

<!--
  And the client responds:
-->
<response xmlns='urn:xmpp:sasl:1>
  dGltIGI5MTNhNjAyYzdlZGE3YTQ5NWI0ZTZlNzMzNGQzODkw
</response>

<!--
  This completes, so the Server sends a success.
-->
<success xmlns='urn:xmpp:sasl:1'>
  <authorization-identifier>tim@example.org</authorization-identifier>
</success>
<!--
  The server immediately sends a new set of stream features at this point.
  There is no stream restart.
-->
<stream:features>
  <bind xmlns='urn:ietf:params:xml:ns:xmpp-bind'>
    <required/>
  </bind>
</stream:features>

<!--
  The client now continues with resource binding.
-->
]]></example>
      <p>Use of SASL2 in this simple scenario again simply saves one round-trip.</p>
    </section2>
    <section2 topic="Advanced Usage">
      <p>This moves into the deeply hypothetical. A binding extension is posited, alongside an unrealistic 2FA mechanism which somehow mutually authenticates because why not.</p>
      <example caption="CRAM-MD5 Authentication"><![CDATA[
<!--
  Server sends stream features.
  Note that whilst megabind is advertised, the unrealistic 2FA mechanism is not.
-->
<stream:features>
  <mechanisms xmlns='urn:xmpp:sasl:1'>
    <mechanism>BLURDYBLOOP</mechanism>
  </mechanisms>
  <megabind xmlns='urn:example:megabind'/>
</stream:features>

<!--
  Client intiates authentication.
-->
<authenticate xmlns='urn:xmpp:sasl:1' mechanism='BLURDYBLOOP'>
  <initial-response>
    SW5pdGlhbCBSZXNwb25zZQ==
  </initial-response>
  <megabind xmlns='urn:example:megabind'>
    <resource>this-one-please</resource>
  </megabind>
</authenticate>

<!--
  Maybe BLURDYBLOOP does this:
-->
<challenge xmlns='urn:xmpp:sasl:1'>
  PDE4OTYuNjk3MTcwOTUyQHBvc3RvZmZpY2UucmVzdG9uLm1jaS5uZXQ+
</challenge>

<!--
  And the client responds:
-->
<response xmlns='urn:xmpp:sasl:1>
  dGltIGI5MTNhNjAyYzdlZGE3YTQ5NWI0ZTZlNzMzNGQzODkw
</response>

<!--
  This completes, so the Server sends a continue, with the
  success data (probably mutual auth) from BLURDYBLOOP.
  The next task required is the unrealistic 2FA.
  Note that the session is - probably - bound at this point, but
  the authorization-identifier is not passed to the client until
  the full authentication sequence is completed.
-->
<continue xmlns='urn:xmpp:sasl:1'>
  <additional-data>
    QWRkaXRpb25hbCBEYXRh
  </additional-data>
  <tasks>
    <task>UNREALISTIC-2FA</task>
  </tasks>
</continue>

<!--
  The client supports the unrealistic 2FA, so can move onto the next task:
-->
<next xmlns='urn:xmpp:sasl:1' task='UNREALISTIC-2FA'>
  <initial-response>
    VW5yZWFsaXN0aWMgMkZBIElS
  </initial-response>
  <!--
    In principle, another option could be negotiated here, but this seems
    unlikely to be useful in practise.
  -->
</next>

<!--
  This 2FA process is both unrealistic and also uses multiple round-trips.
-->
<challenge xmlns='urn:xmpp:sasl:1'>
  PDE4OTYuNjk3MTcwOTUyQHBvc3RvZmZpY2UucmVzdG9uLm1jaS5uZXQ+
</challenge>

<!--
  The client responds here.
-->
<response xmlns='urn:xmpp:sasl:1>
  dGltIGI5MTNhNjAyYzdlZGE3YTQ5NWI0ZTZlNzMzNGQzODkw
</response>

<!--
  Finally, the server sends a success.
  Here, we have an authzid which is a full jid, since the session is now bound.
  The additional-data element here contains the mutual authentication data for the
  unrealistic 2FA, and doesn't refer back to the BLURDYBLOOP exchange.
-->
<success xmlns='urn:xmpp:sasl:1'>
  <additional-data>
    VW5yZWFsaXN0aWMgMkZBIG11dHVhbCBhdXRoIGRhdGE=
  </additional-data>
  <authorization-identifier>
    alice@example.org/this-one-please
  </authorization-identifier>
</success>
<!--
  The Server also sends an (empty) features element.
  The client can simply continue and send stanzas.
-->
<stream:features/>
]]></example>
      <p>Although the unrealistic 2FA here uses 2 round-trips (real ones will probably use one), the embedding of resource binding as shown here means that a second RTT is saved by SASL2, and there's no net change. A more realistic example would see RTTs saved, and additional negotiations could be added to further reduce RTTs.</p>
    </section2>
  </section1>

<section1 topic='Security Considerations' anchor='security'>
  <p>Relative to the SASL profile documented in RFC 6120, this introduces more data unprotected by any security layer negotiated by SASL itself.</p>
  <p>While no actual exchanges are introduced that are unprotected, the nature of this exchange might allow for (for example) a resource binding extension to be introduced.</p>
  <p>SASL security layers are sparingly used in the field, however, so this is thought to be a theoretical, rather than practical, concern.</p>
</section1>

<section1 topic='IANA Considerations' anchor='iana'>
  <p>This XEP requires no interaction with &IANA;. </p>
</section1>

<section1 topic='XMPP Registrar Considerations' anchor='registrar'>
  <p>None.</p>
</section1>

  <section1 topic="XML Schema">
    <code><![CDATA[
<?xml version='1.0' encoding='utf-8'?>
<xs:schema xmlns:xs='http://www.w3.org/2001/XMLSchema'
           targetNamespace="urn:xmpp:sasl:1"
           xmlns="urn:xmpp:sasl:1"
           elementFormDefault="qualified">

    <xs:element name="mechanisms">
        <xs:complexType>
            <xs:sequence>
                <xs:element name="mechanism" type="SaslMechName" minOccurs="1" maxOccurs="unbounded"/>
                <xs:any/>
            </xs:sequence>
        </xs:complexType>
    </xs:element>

    <xs:element name="authenticate">
        <xs:complexType>
            <xs:attribute name="mechanism" type="SaslMechName"/>
            <xs:sequence>
                <xs:element name="initial-response"/>
                <xs:any/>
            </xs:sequence>
        </xs:complexType>
    </xs:element>

    <xs:element name="next">
        <xs:complexType>
            <xs:attribute name="task" type="SaslMechName"/>
            <xs:sequence>
                <xs:element name="initial-response"/>
                <xs:any/>
            </xs:sequence>
        </xs:complexType>
    </xs:element>

    <xs:element name="challenge" type="SaslData"/>

    <xs:element name="response" type="SaslData"/>

    <xs:element name="initial-response" type="SaslData"/>

    <xs:element name="success">
        <xs:complexType>
            <xs:sequence>
                <xs:element name="additional-data" type="SaslData"/>
                <xs:element name="authorization-identifier" type="Jid"/>
            </xs:sequence>
        </xs:complexType>
    </xs:element>

    <xs:element name="continue">
        <xs:complexType>
            <xs:sequence>
                <xs:element name="additional-data" type="SaslData"/>
                <xs:element name="tasks">
                    <xs:complexType>
                        <xs:sequence>
                            <xs:element name="tasK" type="SaslMechName"/>
                        </xs:sequence>
                    </xs:complexType>
                </xs:element>
            </xs:sequence>
        </xs:complexType>
    </xs:element>

    <xs:simpleType name="Jid">
        <xs:restriction base="xs:string">
            <xs:maxLength value="3071"/>
        </xs:restriction>
    </xs:simpleType>

    <xs:simpleType name="SaslMechName">
        <xs:restriction base="xs:string">
            <xs:minLength value="1"/>
            <xs:maxLength value="20"/>
        </xs:restriction>
    </xs:simpleType>

    <xs:simpleType name="SaslData">
        <xs:restriction base="xs:base64Binary"/>
    </xs:simpleType>
</xs:schema>
]]></code>
  </section1>

<section1 topic='Acknowledgements' anchor='ack'>
  <p>The author wishes to share any credit with many members of the community, including Lance Stout, Ralph Meijer, Phil Roberts and Florian Schmaus.</p>
</section1>

</xep>
