From 3656b406954d98de7a0d891f5249f61ceb647011 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Fri, 20 Nov 2009 00:50:07 +0000 Subject: [PATCH] 1.1rc2 git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@3649 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0167.xml | 30 +++++++++++++++++++++++++----- 1 file changed, 25 insertions(+), 5 deletions(-) diff --git a/xep-0167.xml b/xep-0167.xml index 2b261480..cc7aeb63 100644 --- a/xep-0167.xml +++ b/xep-0167.xml @@ -42,10 +42,10 @@ &robmcqueen; &diana; - 1.1rc1 - in progress, last updated 2009-11-08 + 1.1rc2 + in progress, last updated 2009-11-19 psa -

Added creator attribute to mute and unmute elements so that these events can be correlated with a particular content type; clarified use of the reason element in cases other than termination.

 +

Added creator attribute to mute and unmute elements so that these events can be correlated with a particular content type; clarified use of the reason element in cases other than termination; defined handling of content-add when none of the offered payload-types are supported, where the signalling uses a content-reject message with a Jingle reason of <failed-application/> and a list of the supported codecs.

 1.0 @@ -496,7 +496,7 @@ Initiator Responder ]]> -

Note: If the responder supports none of the payload-types offered by the initiator, the responder SHOULD terminate the session and include a Jingle reason of <failed-application/>. This reason can also be included in non-termination events, such as content-reject when the other party has tried to add a content-type for which the recipient supports none of the payload types.

+

If the responder supports none of the payload-types offered by the initiator, the responder SHOULD terminate the session and include a Jingle reason of <failed-application/>.

If the responder accepts the session, the initiator acknowledges the session-accept message:

]]> -

Then Juliet accepts video.

+

Note: If the responder supports none of the payload-types offered by the initiator, the responder MUST reply to the content-add request with a content-reject; this message SHOULD include a Jingle reason of <failed-application/> and a list of the payload-types that the responder supports (along with an empty element for the same transport offered by the initiatior), as shown in the following example.

+ + + + + + + + + + + + ]]> +

However, here we assume that Juliet's client supports at least one of the payload-types offered by Romeo's client, and that she Juliet accepts the offer of adding video to the session.