From 9fc5315295438c8ec64bb143a9565341dae75841 Mon Sep 17 00:00:00 2001
From: Peter Saint-Andre <stpeter@jabber.org>
Date: Fri, 31 Oct 2008 19:55:11 +0000
Subject: [PATCH] moved sentence to reduce confusion

git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@2477 4b5297f7-1745-476d-ba37-a9c6900126ab
---
 xep-0206.xml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/xep-0206.xml b/xep-0206.xml
index 0e123b2a..a24a6cb3 100644
--- a/xep-0206.xml
+++ b/xep-0206.xml
@@ -86,7 +86,7 @@ Content-Length: 104
 </section1>
 
 <section1 topic="Session Creation Response" anchor='create'>
-  <p>The connection manager SHOULD include an 'xmpp:version' attribute (qualified by the 'urn:xmpp:xbosh' namespace) and a &lt;stream:features/&gt; element (qualified by the 'http://etherx.jabber.org/streams' namespace) in a response as soon as they are available, either in its session creation response, or (if it has not yet received them from the XMPP server) in any subsequent response. If no &lt;stream:features/&gt; element is included in the connection manager's session creation response, then the client SHOULD send empty request elements until it receives a response containing a &lt;stream:features/&gt; element.</p>
+  <p>The connection manager SHOULD include an 'xmpp:version' attribute (qualified by the 'urn:xmpp:xbosh' namespace) and a &lt;stream:features/&gt; element (qualified by the 'http://etherx.jabber.org/streams' namespace) in a response as soon as they are available, either in its session creation response, or (if it has not yet received them from the XMPP server) in any subsequent response.</p>
   <p>Note: The same procedure applies to the <em>obsolete</em> XMPP-specific 'authid' attribute of the BOSH &lt;body/&gt; element, which contains the value of the XMPP stream ID generated by the XMPP server. This value is needed only by legacy XMPP clients in order to complete digest authentication using the <em>obsolete</em>&#32;&xep0078; protocol. <note>Separate 'sid' and 'authid' attributes are required because the connection manager is not necessarily part of a single XMPP server (e.g., it may handle HTTP connections on behalf of multiple XMPP servers).</note></p>
   <example caption="Session creation response with stream features">
 <![CDATA[HTTP/1.1 200 OK
@@ -115,6 +115,7 @@ Content-Length: 674
   </stream:features>
 </body>
   ]]></example>
+  <p>If no &lt;stream:features/&gt; element is included in the connection manager's session creation response, then the client SHOULD send empty request elements until it receives a response containing a &lt;stream:features/&gt; element.</p>
   <example caption="Subsequent response with stream features">
 <![CDATA[HTTP/1.1 200 OK
 Content-Type: text/xml; charset=utf-8