diff --git a/xep-0206.xml b/xep-0206.xml
index a20ed984..f1e641ab 100644
--- a/xep-0206.xml
+++ b/xep-0206.xml
@@ -27,10 +27,10 @@
   &ianpaterson;
   &stpeter;
   <revision>
-    <version>1.2pre1</version>
-    <date>in progress, last updated 2008-08-14</date>
+    <version>1.2rc2</version>
+    <date>in progress, last updated 2008-10-01</date>
     <initials>psa</initials>
-    <remark><p>Clarified handling of restart: client MUST send and body MUST be empty; removed IM session establishment examples; corrected XML schema.</p></remark>
+    <remark><p>Clarified handling of xmpp:restart -- client MUST send the restart and the body MUST be empty; removed IM session establishment examples because that protocol is deprecated in rfc3921bis; corrected XML schema.</p></remark>
   </revision>
   <revision>
     <version>1.1</version>
@@ -217,7 +217,7 @@ Content-Length: 121
   <success xmlns='urn:ietf:params:xml:ns:xmpp-sasl'/>
 </body>
   ]]></example>
-  <p>Upon receiving the &lt;success/&gt; element, the client MUST then ask the connection manager to restart the stream. It does this by setting to "true" the 'xmpp:restart' attribute (qualified by the 'urn:xmpp:xbosh' namespace) of the BOSH &lt;body/&gt; element. When sending the restart request, the client SHOULD also include the 'to' and 'xml:lang' attributes. In addition the &lt;body/&gt; SHOULD be empty (if the client includes an XML stanza in the body, the connection manager might send that stanza when the stream is restarted, but there is no guarantee that a connection manager will do so).</p>
+  <p>Upon receiving the &lt;success/&gt; element, the client MUST then ask the connection manager to restart the stream. It does this by setting to "true" the 'xmpp:restart' attribute (qualified by the 'urn:xmpp:xbosh' namespace) of the BOSH &lt;body/&gt; element. When sending the restart request, the client SHOULD also include the 'to' and 'xml:lang' attributes. In addition the &lt;body/&gt; MUST be empty (if the client includes an XML stanza in the body, the connection manager SHOULD ignore it but MAY send that stanza when the stream is restarted; however there is no guarantee that a connection manager will send the stanza so a client cannot rely on this behavior).</p>
   <example caption="Restart a stream request">
 <![CDATA[POST /webclient HTTP/1.1
 Content-Type: text/xml; charset=utf-8
@@ -231,7 +231,7 @@ Content-Length: 240
       xmlns='http://jabber.org/protocol/httpbind'
       xmlns:xmpp='urn:xmpp:xbosh'/>
   ]]></example>
-  <p>Upon receiving any request with the 'xmpp:restart' attribute set to "true" the connection manager MUST consider the original stream with the XMPP server to be closed. It MUST then initiate a new stream by sending an opening &lt;stream:stream&gt; tag over the same TCP connection to the XMPP server. Upon receiving the response from the XMPP server, it MUST forward any available features (or an empty <features/> element) to the client:</p>
+  <p>Upon receiving any request with the 'xmpp:restart' attribute set to "true" the connection manager MUST consider the original stream with the XMPP server to be closed. It MUST then initiate a new stream by sending an opening &lt;stream:stream&gt; tag over the same TCP connection to the XMPP server. If the connection manager receives a &lt;stream:features/&gt; element from the XMPP server, it MUST forward that element to the client:</p>
   <example caption="Restart a stream result">
 <![CDATA[HTTP/1.1 200 OK
 Content-Type: text/xml; charset=utf-8