From 0049e182b977435a8728344b95ed38f5a07e29fb Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Wed, 22 Apr 2009 20:41:26 +0000 Subject: [PATCH] clarified handling of SRTP negotiation git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@3079 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0167.xml | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/xep-0167.xml b/xep-0167.xml index 0512ef87..e1362283 100644 --- a/xep-0167.xml +++ b/xep-0167.xml @@ -589,7 +589,8 @@ delivery-method=inline; configuration=somebase16string; inline:WVNfX19zZW1jdGwgKCkgewkyMjA7fQp9CnVubGVz|2^20|1:32 session-params:KDR=1;UNENCRYPTED_SRTCP ]]> -

When the responder receives a session-initiate message containing an <encryption/> element, the responder MUST either (1) accept the offer by denoting one of the <crypto/> elements as acceptable (it does this by mirroring that <crypto/> element in its session acceptance) or (2) reject the offer by sending a session-terminate message with a Jingle reason of <security-error/> (typically with an RTP-specific condition of <invalid-crypto/>).

+

When the responder receives a session-initiate message containing an <encryption/> element with the 'required' attribute set to TRUE, the responder MUST either (1) accept the offer by denoting one of the <crypto/> elements as acceptable (it does this by mirroring that <crypto/> element in its session acceptance) or (2) reject the offer by sending a session-terminate message with a Jingle reason of <security-error/> (typically with an RTP-specific condition of <invalid-crypto/>).

+

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.

If the initiator requires encryption but the responder does not include an <encryption/> element in its session acceptance, the initiator MUST terminate the session with a Jingle reason of <security-error/> and an RTP-specific condition of <crypto-required/>.