From 7828f1d12f5d740e79293211d5c5bff8fa4dae09 Mon Sep 17 00:00:00 2001
From: Peter Saint-Andre <stpeter@jabber.org>
Date: Wed, 6 May 2009 19:30:40 +0000
Subject: [PATCH] media testing tweaks

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

diff --git a/xep-0177.xml b/xep-0177.xml
index b4b21103..c3b06941 100644
--- a/xep-0177.xml
+++ b/xep-0177.xml
@@ -286,7 +286,7 @@ INITIATOR                            RESPONDER
   </section2>
 
   <section2 topic='Sending Media' anchor='media'>
-    <p>Upon sending the session-accept action, the responder MUST immediately attempt to send media to the initiator. Upon receiving the session-accept action, the initiator MUST immediately attempt to send media to the responder. The exact media to send is out of scope for this specification; however, it is RECOMMENDED to send comfort noise as specified in &rfc3389;.</p>
+    <p>Upon sending the session-accept action, the responder MUST immediately attempt to send media to the initiator. Upon receiving the session-accept action, the initiator MUST immediately attempt to send media to the responder. The exact media to send depends on the application type being negotiated and therefore is out of scope for this specification (e.g., for Jingle RTP Sessions it would be appropriate to send comfort noise as specified in &rfc3389;).</p>
     <p>An implementation SHOULD enforce a timeout on receipt of media, such that if no media is received from the other party within a reasonable period of time, the implementation will consider the session to have failed and therefore send to the other party a Jingle "session-terminate" action with a reason code of &lt;timeout/&gt;.</p>
     <example caption="Responder terminates the session"><![CDATA[
 <iq from='juliet@capulet.lit/balcony'
@@ -342,7 +342,7 @@ INITIATOR                            RESPONDER
 <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 a UDP association, such as those described in &xtls;.</p>
-    <p>Application types that use the Jingle Raw UDP transport method MAY also define their own application-specific encryption methods, such as the Secure Real-time Transport Protocol (SRTP) for RTP exchanges as described in &xep0167;.</p>
+    <p>Application types that use the Jingle Raw UDP transport method MAY also define their own application-specific encryption methods, such as the Secure Real-time Transport Protocol (SRTP) for RTP exchanges as described in <cite>XEP-0167: Jingle RTP Sessions</cite>.</p>
   </section2>
 </section1>