From 48342fbe22fdabf10aa0f0e3ef6a67029d04853e Mon Sep 17 00:00:00 2001
From: stpeter <stpeter@stpeter.im>
Date: Thu, 8 Sep 2011 15:55:44 -0600
Subject: [PATCH] 0.8

---
 xep-0260.xml | 33 ++++++++++++++++++++++++++++++++-
 1 file changed, 32 insertions(+), 1 deletion(-)

diff --git a/xep-0260.xml b/xep-0260.xml
index 7b68f574..4cd326b3 100644
--- a/xep-0260.xml
+++ b/xep-0260.xml
@@ -33,6 +33,12 @@
     <email>klaus.hartke@googlemail.com</email>
     <jid>nx@jabber.org</jid>
   </author>
+  <revision>
+    <version>0.8</version>
+    <date>2011-09-08</date>
+    <initials>psa</initials>
+    <remark><p>More clearly described how to activate the bytestream.</p></remark>
+  </revision>
   <revision>
     <version>0.7</version>
     <date>2011-08-31</date>
@@ -169,6 +175,12 @@ Initiator                        Responder
                    port='5087'
                    priority='8258636'
                    type='direct'/>
+        <candidate cid='xmdh4b7i'
+                   host='123.456.7.8'
+                   jid='streamer.shakespeare.lit'
+                   port='7625'
+                   priority='8258636'
+                   type='proxy'/>
       </transport>
     </content>
   </jingle>
@@ -325,7 +337,26 @@ priority = (2^16)*(type preference) + (local preference)
       <li>If both parties send a candidate-used notification but the candidates have a different priority, then the candidate with the higher priority shall be considered the nominated candidate.</li>
       <li>If both parties send a candidate-used notification with candidates having the same priority, then the candidate chosen by the initiator shall be considered the nominated candidate (this is consistent with the rules in <cite>XEP-0166</cite>).</li>
     </ol>
-    <p>The parties shall use the nominated candidate for the data transfer. If the nominated candidate is of the proxy type, then the peer has no way to know when it can send data. Therefore the party that offered the nominated candidate MUST send an activated notification to the peer once it has activated the bytestream (as described in <cite>XEP-0065</cite>); it does so by sending a transport-info message containing an &lt;activated/&gt; element as follows.</p>
+    <p>The parties shall use the nominated candidate for the data transfer. However, if the nominated candidate is of the "proxy" type, then the peer has no way to know when it can send data. Therefore the party that offered the nominated candidate MUST do two things...</p>
+    <p>First, it activates the bytestream, as described in <cite>XEP-0065</cite>:</p>
+    <example caption="Responder activates the bytestream at proxy"><![CDATA[
+<iq from='juliet@capulet.lit/balcony'
+    id='vy1fa63k'
+    to='streamer.shakespeare.lit'
+    type='set'>
+  <query xmlns='http://jabber.org/protocol/bytestreams'
+         sid='a73sjjvkla37jfea'>
+    <activate>romeo@montague.lit/orchard</activate>
+  </query>
+</iq>
+    ]]></example>
+    <example caption="Proxy informs responder of activation"><![CDATA[
+<iq from='streamer.shakespeare.lit'
+    id='vy1fa63k'
+    to='juliet@capulet.lit/balcony'
+    type='result'/>
+    ]]></example>
+    <p>Second, it sends an activated notification to the peer; it does so by sending a transport-info message containing an &lt;activated/&gt; element:</p>
     <example caption="Responder informs initiator that bytestream has been activated"><![CDATA[
 <iq from='juliet@capulet.lit/balcony'
     id='bv73bs91'