1.2rc3

git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@3442 4b5297f7-1745-476d-ba37-a9c6900126ab

xep-0175.xml

@@ -22,7 +22,7 @@
   <shortname>N/A</shortname>
   &stpeter;
   <revision>
-    <version>1.2rc2</version>
+    <version>1.2rc3</version>
     <date>in progress, last updated 2009-08-31</date>
     <initials>psa</initials>
     <remark><p>Provided more detailed recommendations regarding usage restrictions for anonymous users; added note about user/anonymous service discovery identity.</p></remark>
@@ -53,22 +53,28 @@
   </revision>
 </header>
 <section1 topic='Introduction' anchor='intro'>
-  &RFC3920BISNOTE;
+  <p>&xmppcore; allows XMPP server implementations to support any SASL mechanism (see &rfc4422;) when authenticating clients. This document provides recommendations regarding use of the SASL ANONYMOUS mechanism (see &rfc4505;) in XMPP systems.</p>
-  <p><cite>RFC 3920</cite> allows the use of any SASL mechanism (see &rfc4422;) in XMPP authentication, including the SASL ANONYMOUS mechanism (see &rfc4505;). This document specifies a recommended protocol flow for such use.</p>
-  <p>Note: This document is provided for discussion purposes in order to clarify the usage of SASL ANONYMOUS in XMPP systems. It is not meant to supersede the text in <cite>RFC 3920</cite>, <cite>RFC 4422</cite>, or <cite>RFC 4505</cite>. However, the recommendations in this document may be folded into <cite>rfc3920bis</cite>.</p>
 </section1>
-<section1 topic='Recommendations' anchor='rec'>
+<section1 topic='Deployment Types' anchor='deployments'>
-  <p>An XMPP server implementation SHOULD NOT enable the SASL ANONYMOUS mechanism by default, but instead SHOULD force an administrator to explicitly enable support in any given deployment.</p>
+  <p>XMPP server implementations can be deployed in a variety of settings. Although it is difficult to provide recommendations for every kind of XMPP deployment, this document attempts to strike a balance between more and less controlled settings by defining three different deployment types:</p>
-  <p>An XMPP server SHOULD assign a temporary, unique bare JID &LOCALBARE; to a client that authenticates with SASL ANONYMOUS. Although the method for ensuring the uniqueness of localpart is a matter of implementation, it is RECOMMENDED for the localpart to be a UUID as specified in &rfc4122;.</p>
+  <ul>
-  <p>After a client authenticates using the SASL ANONYMOUS mechanism, it MUST bind a resource. On public servers where the same JID is reused for multiple anonymous sessions, the server MAY ignore the resource identifier provided by the client (if any) and instead assign a resource identifier that it generates on behalf of the client.</p>
+    <li>Public deployments, such as well-known instant messaging (IM) services on the open Internet.</li>
-  <p>Because an anonymous user is unknown to the server, the server SHOULD appropriately restrict the user's access in order to limit the possibility of malicious behavior, such as denial of service attacks as described in &xep0205;. The following restrictions are encouraged:</p>
+    <li>Private deployments, such as enterprise IM services, technical support departments, and helplines.</li>
+    <li>Specialized deployments that typically will be accessed in a controlled fashion, such as gaming services, members-only websites, and applications that are not used directly by human users.</li>
+  </ul>
+</section1>
+<section1 topic='Recommendations' anchor='recommendations'>
+  <p>An XMPP server implementation SHOULD NOT enable the SASL ANONYMOUS mechanism by default, but instead SHOULD force the administrator of a given service to explicitly enable support in the context of that deployment.</p>
+  <p>When a client authenticates using SASL ANONYMOUS, an XMPP server SHOULD assign a temporary, unique bare JID &LOCALBARE; to the client. Although the method for ensuring the uniqueness of the localpart is a matter of implementation, it is RECOMMENDED for the localpart to be a UUID as specified in &rfc4122;.</p>
+  <p>Although <cite>RFC 4505</cite> allows the client to provide so-called "trace data" when authenticating via SASL ANONYMOUS, it is NOT RECOMMENDED for the client to include trace data as the XML character data of the &lt;auth/&gt; element (instead, the &lt;auth/&gt; element SHOULD be empty). However, if trace data is included, the server MUST NOT use it for any purpose other than tracing (e.g., not use it as the resource identifier of the anonymous user's full JID).</p>
+  <p>Because an anonymous user is unknown to the server, the server SHOULD appropriately restrict the user's access in order to limit the possibility of malicious behavior (such as denial of service attacks as described in &xep0205;), especially on public deployments. The following restrictions are encouraged on public deployments. Administrators of private deployments and specialized deployments are advised to take these restrictions into account when configuring their services, but can reasonably relax these restrictions if they have appropriate access controls in place or their deployment requirements cannot be met using the more restrictive profile applied in public deployments.</p>
   <ol start='1'>
-    <li><p>The user SHOULD NOT be allowed to initiate communication with entities hosted at remote servers.</p></li>
+    <li><p>During resource binding, the server MAY ignore the resource identifier provided by the client (if any) and instead assign a resource identifier that it generates on behalf of the client.</p></li>
-    <li><p>The user SHOULD NOT be allowed to establish long-term relationships such as presence subscriptions, &xep0045; registrations, or &xep0060; subscriptions; however, if the server allows this, it MUST cancel such relationships when the user's session ends.</p></li>
+    <li><p>The server SHOULD NOT allow the client to initiate communication with entities hosted at remote servers.</p></li>
-    <li><p>The user SHOULD NOT be allowed to permanently store information on the server (e.g., via &xep0049;); however, if the server allows this, it MUST remove such information when the user's session ends.</p></li>
+    <li><p>The server MAY allow the client to establish relationships with local services and users; such relationships might include presence subscriptions and roster additions (see &xmppim;), &xep0045; registrations, and &xep0060; subscriptions. (Note that allowing presence subscriptions and roster additions can create a sub-optimal user experience for the added contacts.) However, if the server permits such relationships, it MUST cancel them when the client's session ends.</p></li>
-    <li><p>The user SHOULD NOT be allowed to send large numbers of XMPP stanzas or otherwise use large amounts of system resources (e.g., by binding multiple resource identifiers or creating multiple &xep0065; sessions).</p></li>
+    <li><p>The server MAY allow the client to store information on the server for the purpsoe of providing an optimal user experience (e.g., storage of client preferences using &xep0049;). However, if the server allows this, it SHOULD remove such information when the client's session ends.</p></li>
+    <li><p>The server SHOULD NOT allow the client to send large numbers of XMPP stanzas or otherwise use large amounts of system resources (e.g., by binding multiple resource identifiers or creating multiple &xep0065; sessions).</p></li>
   </ol>
-  <p>Although <cite>RFC 4505</cite> allows the initiating entity (client) to provide so-called "trace data" when authenticating via SASL ANONYMOUS, it is NOT RECOMMENDED for the client to include trace data as the XML character data of the &lt;auth/&gt; element (instead, the &lt;auth/&gt; element SHOULD be empty). However, if trace data is included, the server MUST NOT use it for any purpose other than tracing (e.g., in server logs).</p>
 </section1>
 <section1 topic='Protocol Flow' anchor='flow'>
   <p>The RECOMMENDED protocol flow following TLS negotiation (refer to <cite>RFC 3920</cite>) is as follows:</p>
@@ -185,4 +191,7 @@
 <section1 topic='XMPP Registrar Considerations' anchor='registrar'>
   <p>This document requires no interaction with the &REGISTRAR;.</p>
 </section1>
+<section1 topic='Acknowledgements' anchor='ack'>
+  <p>Thanks to Dave Cridland, Tuomas Koski, Jack Moffitt, Andy Skelton, and Kurt Zeilenga for their feedback.</p>
+</section1>
 </xep>