From aeacdcae830e037d6e3981b133e374caa987a839 Mon Sep 17 00:00:00 2001
From: stpeter <stpeter@stpeter.im>
Date: Wed, 31 Aug 2011 12:59:23 -0600
Subject: [PATCH] 0.8

---
 xep-0261.xml | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/xep-0261.xml b/xep-0261.xml
index 39622f9d..9eead6f7 100644
--- a/xep-0261.xml
+++ b/xep-0261.xml
@@ -23,6 +23,12 @@
   <shortname>jingle-ibb</shortname>
   <discuss>jingle</discuss>
   &stpeter;
+  <revision>
+    <version>0.8</version>
+    <date>2011-08-31</date>
+    <initials>psa</initials>
+    <remark><p>Per feedback from the XMPP Council, modified the security considerations to remove the recommendation to use XTLS (since it is not longer being actively developed).</p></remark>
+  </revision>
   <revision>
     <version>0.7</version>
     <date>2011-05-16</date>
@@ -323,9 +329,9 @@ Initiator                   Responder
   <p>In order for an application to determine whether an entity supports this protocol, where possible it SHOULD use the dynamic, presence-based profile of service discovery defined in &xep0115;. However, if an application has not received entity capabilities information from an entity, it SHOULD use explicit service discovery instead.</p>
 </section1>
 
-<section1 topic='Security Considerations' anchor='sec'>
+<section1 topic='Security Considerations' anchor='security'>
   <section2 topic='Encryption of Media' anchor='security-media'>
-    <p>A Jingle implementation SHOULD support security preconditions that are enforced before application media is allowed to flow over the bytestream, such as those described in &xtls;.</p>
+    <p>This specification, like <cite>XEP-0047</cite> before it, does not directly support end-to-end encryption of the media sent over the transport.</p>
   </section2>
   <section2 topic='Use of Base64' anchor='security-base64'>
     <p>See <cite>XEP-0047</cite> for security considerations related to the use of Base64.</p>