SDP correction per RFC 4568

git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@3091 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2009-04-23 19:02:02 +00:00
parent 0049e182b9
commit 6d554e93cd
1 changed files with 3 additions and 3 deletions

View File

@ -579,7 +579,7 @@ delivery-method=inline; configuration=somebase16string;
<crypto
crypto-suite='AES_CM_128_HMAC_SHA1_80'
key-params='inline:WVNfX19zZW1jdGwgKCkgewkyMjA7fQp9CnVubGVz|2^20|1:32'
session-params='KDR=1;UNENCRYPTED_SRTCP'
session-params='KDR=1 UNENCRYPTED_SRTCP'
tag='1'/>
</encryption>
]]></code>
@ -587,7 +587,7 @@ delivery-method=inline; configuration=somebase16string;
<code><![CDATA[
a=crypto:1 AES_CM_128_HMAC_SHA1_80
inline:WVNfX19zZW1jdGwgKCkgewkyMjA7fQp9CnVubGVz|2^20|1:32
session-params:KDR=1;UNENCRYPTED_SRTCP
KDR=1 UNENCRYPTED_SRTCP
]]></code>
<p>When the responder receives a session-initiate message containing an &lt;encryption/&gt; element with the 'required' attribute set to TRUE, the responder MUST either (1) accept the offer by denoting one of the &lt;crypto/&gt; elements as acceptable (it does this by mirroring that &lt;crypto/&gt; element in its session acceptance) or (2) reject the offer by sending a session-terminate message with a Jingle reason of &lt;security-error/&gt; (typically with an RTP-specific condition of &lt;invalid-crypto/&gt;).</p>
<p>If the 'required' attribute is set to FALSE (this is the default), depending on personal security policies or client configuration the responder SHOULD accept the offer if possible, but MAY simply proceed without encryption.</p>
@ -1134,7 +1134,7 @@ Romeo Juliet
<crypto
crypto-suite='AES_CM_128_HMAC_SHA1_80'
key-params='inline:WVNfX19zZW1jdGwgKCkgewkyMjA7fQp9CnVubGVz|2^20|1:32'
session-params='KDR=1;UNENCRYPTED_SRTCP'
session-params='KDR=1 UNENCRYPTED_SRTCP'
tag='1'/>
</encryption>
</description>