moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-12-21 23:28:51 -05:00
Code Issues Releases Wiki Activity

0.3

Browse Source
This commit is contained in:
stpeter 2011-06-22 08:15:18 -06:00
parent 760d3bae27
commit 766d5ea232
1 changed files with 14 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
xep-0233.xml
View File

@ -25,6 +25,12 @@
&linuxwolf;
&stpeter;
&hildjj;
<revision>
<version>0.3</version>
<date>2011-06-22</date>
<initials>psa</initials>
<remark><p>Tightened the conformance terminology in several places; updated references.</p></remark>
</revision>
<revision>
<version>0.2</version>
<date>2010-06-10</date>
@ -52,21 +58,21 @@
</header>
<section1 topic='Introduction' anchor='intro'>
<p>In certain kinds of XMPP deployments, multiple connection managers associated with the XMPP server can be used to handle requests from connecting clients. In such an architecture, the connection manager might need to communicate the hostname to which the client has connected, or information about alternative connection manager.</p>
<p>This is especially true in environments that make use of Kerberos V and negotiation of Simple Authentication and Security Layer (SASL) over XMPP, because the client might need additional information about the Kerberos principal so that it can obtain a proper ticket for authentication.</p>
<p>This scenario was not addressed in &rfc3920; or &rfc6120;. However, the problem can now be solved using the concept of domain-based service names as described in &rfc5178;. In particular, because XMPP servers typically use the Kerberos V5 ("GSSAPI") SASL mechanism as described in &rfc4752;, they can communicate domain-based names as Kerberos V service principal names as described in &rfc5179;.</p>
<p>Therefore this document defines a method for communication of authentication hostnames (especially Kerberos V domain-based service names) in the context of SASL negotiation by XMPP entities.</p>
<p>In certain kinds of XMPP deployments, multiple connection managers associated with the XMPP server can be used to handle requests from connecting clients. In such an architecture, the connection manager might need to communicate the hostname to which the client has connected, or information about alternative connection managers.</p>
<p>This is especially true in environments that make use of Kerberos V5 (&rfc4120;) and negotiation of Simple Authentication and Security Layer or SASL (&rfc4422;) over XMPP, because the client might need additional information about the Kerberos principal so that it can obtain a proper ticket for authentication.</p>
<p>This scenario was not addressed in &rfc3920; or &rfc6120;. However, the problem can be solved using the concept of domain-based service names as described in &rfc5178;. In particular, because XMPP servers typically use the Kerberos V5 ("GSSAPI") SASL mechanism as described in &rfc4752;, they can communicate domain-based names as Kerberos V5 service principal names as described in &rfc5179;.</p>
<p>Therefore this document defines a method for communication of authentication hostnames (especially Kerberos V5 domain-based service names) in the context of SASL negotiation by XMPP entities.</p>
</section1>
<section1 topic='Use with Kerberos' anchor='kerberos'>
<p>When a connection manager associated with an XMPP server needs to communicate additional information about its service principal name to a connecting client, it can do so by including a child element of the &lt;mechanisms/&gt; element during SASL negotation, as specified in &rfc6120;. In the case of the Kerberos V SASL mechanism, the child element is a &lt;hostname/&gt; element qualified by the 'urn:xmpp:domain-based-name:0' namespace &NSNOTE;. In the context of Kerberos, the &lt;hostname/&gt; element MUST include a 'mechanism' attribute, where the value MUST be "GSSAPI". The XML character data of the &lt;hostname/&gt; element shall specify the fully-qualified name of the connection manager (known as the hostname). The client then generates a domain-based service name from the provided hostname, following the format specified in <cite>RFC 5179</cite> (i.e., "protocol/hostname/domainname@REALM"):</p>
<p>When a connection manager associated with an XMPP server needs to communicate additional information about its service principal name to a connecting client, it can do so by including a child element of the &lt;mechanisms/&gt; element during SASL negotation, as allowed by <cite>RFC 6120</cite> (see Section 6.3.5 and the schema for the 'urn:ietf:params:xml:ns:xmpp-sasl' namespace in Appendix A.4). In the case of the Kerberos V5 SASL mechanism, the child element is a &lt;hostname/&gt; element qualified by the 'urn:xmpp:domain-based-name:0' namespace &NSNOTE;. In the context of Kerberos, the &lt;hostname/&gt; element MUST include a 'mechanism' attribute, where the value MUST be "GSSAPI". The XML character data of the &lt;hostname/&gt; element shall specify the fully-qualified name of the connection manager (known as the hostname). The client then generates a domain-based service name from the provided hostname, following the format specified in <cite>RFC 5179</cite> (i.e., "protocol/hostname/domainname@REALM") and setting the values as follows:</p>
<ul>
<li>The <strong>protocol</strong> string MUST be "xmpp"</li>
<li>The <strong>hostname</strong> string MUST be the XML character data of the &lt;hostname/&gt; element</li>
<li>The <strong>domainname</strong> string MUST be the canonical name of the service</li>
<li>The <strong>REALM</strong> string SHOULD be determined according to the network policies in effect (usually the domain name, in an uppercase mapping)</li>
</ul>
<p>Consider the example of an XMPP service whose canonical name is "example.com". A user may in fact connect to the physical machine "cm7.us.example.com". The hostname would be communicated as follows.</p>
<p>Consider the example of an XMPP service whose canonical name is "example.com". A user might in fact connect to the physical machine "cm7.us.example.com". The hostname would be communicated as follows.</p>
<example caption="Communicating the hostname"><![CDATA[
<mechanisms xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>
<mechanism>GSSAPI</mechanism>
@ -80,7 +86,7 @@
</section1>
<section1 topic='Non-Kerberos Use Cases' anchor='other'>
<p>This protocol can also be used to communicate connection manager hostnames outside the context of Kerberos. In this case, the &lt;hostname/&gt; element will not include the 'mechanism' attribute, and multiple instances of the &lt;hostname/&gt; element can be included. An example follows.</p>
<p>This protocol can also be used to communicate connection manager hostnames outside the context of Kerberos. In this case, the &lt;hostname/&gt; element MUST NOT include the 'mechanism' attribute, and multiple instances of the &lt;hostname/&gt; element MAY be included. An example follows.</p>
<example caption="Communicating hostnames"><![CDATA[
<mechanisms xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>
<mechanism>GSSAPI</mechanism>
@ -94,7 +100,7 @@
</section1>
<section1 topic='Security Considerations' anchor='security'>
<p>The communication of hostnames during SASL negotiation is not known to introduce new security vulnerabilities. Communication of hostnames SHOULD NOT occur until after the underlying channel has been secured using Transport Layer Security (TLS; &rfc5246;) as described for XMPP in <cite>RFC 6120</cite> and <cite>RFC 6120</cite>. For additional security considerations, refer to <cite>RFC5178</cite> and <cite>RFC 5179</cite>.</p>
<p>The communication of hostnames during SASL negotiation is not known to introduce new security vulnerabilities, as long as it is done after the underlying channel has been secured using Transport Layer Security (TLS; &rfc5246;) as described for XMPP in <cite>RFC 6120</cite>. For additional security considerations, refer to <cite>RFC5178</cite> and <cite>RFC 5179</cite>.</p>
</section1>
<section1 topic='IANA Considerations' anchor='iana'>