Re: [MMUSIC] BUNDLE (pre-5): New Answerer text

Harald Alvestrand <harald@alvestrand.no> Sat, 21 September 2013 06:38 UTC

Return-Path: <harald@alvestrand.no>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AAB111E810E for <mmusic@ietfa.amsl.com>; Fri, 20 Sep 2013 23:38:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.132
X-Spam-Level:
X-Spam-Status: No, score=-110.132 tagged_above=-999 required=5 tests=[AWL=-0.134, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_56=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B-nLdoJIfMhS for <mmusic@ietfa.amsl.com>; Fri, 20 Sep 2013 23:38:31 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 4207F11E810B for <mmusic@ietf.org>; Fri, 20 Sep 2013 23:38:21 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id A45EF39E128 for <mmusic@ietf.org>; Sat, 21 Sep 2013 08:38:19 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id drVIxtCBCR9u for <mmusic@ietf.org>; Sat, 21 Sep 2013 08:38:17 +0200 (CEST)
Received: from [IPv6:2001:470:de0a:27:1003:d74f:d593:c954] (unknown [IPv6:2001:470:de0a:27:1003:d74f:d593:c954]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 53F5939E062 for <mmusic@ietf.org>; Sat, 21 Sep 2013 08:38:17 +0200 (CEST)
Message-ID: <523D3F31.8050204@alvestrand.no>
Date: Sat, 21 Sep 2013 08:39:45 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130804 Thunderbird/17.0.8
MIME-Version: 1.0
To: mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1C4A787B@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C4A787B@ESESSMB209.ericsson.se>
Content-Type: multipart/alternative; boundary="------------010405040000080400080206"
Subject: Re: [MMUSIC] BUNDLE (pre-5): New Answerer text
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Sep 2013 06:38:51 -0000

On 09/19/2013 12:23 PM, Christer Holmberg wrote:
>
> Hi,
>
> Based on the new BUNDLE Offerer text, I also modified (and, hopefully 
> clarified) the Answerer text.
>
> In addition, the new text also covers 'bundle-only' m- lines.
>
> Comments are welcome.
>
Some grammar nits.
>
> Regards,
>
> Christer
>
> ---------------------
>
> 6.5. SDP Answerer Procedures
>
> 6.5.1. Answerer Bundle Address Selection and Usage
>
> 6.5.1.1. Offerer Bundle Address Selection
>
> When an Answerer generates an Answer that contains a BUNDLE group,
>
> the Answer MUST select the Offerer's BUNDLE address. The first mid
>
> value in the SDP group:BUNDLE attribute mid list of the Offer
>
> represents the address which the Offerer wishes the Answer to
>
> select as the Offerer's BUNDLE address [ref-to-offer-prec].
>
> The Answerer SHOULD select the address represented by the first mid
>
> value, unless the Answerer in the associated Answer will rejects the
>
> "m=" line associated with the mid value [ref], or remove the "m=" line
>
> from the BUNDLE group [ref] from the BUNDLE group. In such case the
>
"from the BUNDLE group" is repeated twice.
>
> Answerer MUST select an address associated with the next mid value in
>
> the SDP group:BUNDLE attribute mid list of the Offer.
>
This should be "an address associated with the first unrejected MID that 
remains in the BUNDLE group".
Otherwise, rejecting MID #1 and #2 would leave you in an undefined state.

> In the SDP Answer, the Answerer MUST place the mid value associated with
>
> the selected Offerer's BUNDLE address first in the SDP group:BUNDLE
>
> attribute mid list associated with the BUNDLE group.
>
> Section 10.1 shows an example of an Offerer's BUNDLE address
>
> selection.
>
> 6.5.1.2. Anwerer Bundle Address Selection
>
> When an Answerer creates an Answer that contains a BUNDLE group,
>
> the Answerer MUST assign a local shared address, the Answerer's BUNDLE
>
> address, to each "m=" line within the BUNDLE group.
>
> The Answerer is allowed to change its BUNDLE address in any SDP
>
> Answer.
>
> The Answerer MUST NOT assign a shared address, that it has assigned
>
> to an "m=" line within a BUNDLE group, to an "m=" line outside
>
> the BUNDLE group.
>
> Section 10.1 shows an example of an Answerer's local BUNDLE address
>
> selection.
>
> 6.5.2. Moving A Media Description Out Of A BUNDLE Group
>
> When an Answerer generates an Answer, in which an "m=" line is moved
>
> out of a BUNDLE group, the Answerer assigns an address to the moved
>
> "m=" line based on the type of address that the Offerer assigned
>
> to the associated "m=" line in the associated Offer, as described below.
>
> If the Offerer assigned a shared address to the "m=" line, the
>
> answerer MUST reject the moved "m=" line, according to the procedures
>
> in Section 6.5.3.
>
> If the Offerer assigned a 'bundle-only' attribute to the "m=" line,
>
> the Answerer MUST reject the moved "m=" line, according to the procedures
>
> in Section 6.5.3.
>
> If the Offerer assigned a unique address to the "m=" line, the Answer
>
> MUST assign a unique address to the moved "m=" line.
>
> In addition, in either case above, the Answerer MUST NOT anymore
>
> include a mid value, representing the "m=" line, in the SDP
>
> group:BUNDLE attribute list associated with the BUNDLE group.
>
> 6.5.3. Rejecting A Media Description In A BUNDLE Group
>
> When an Answerer generates an Answer, in which an "m=" line associated
>
> with a BUNDLE group is rejected, the Answerer MUST assign an address
>
> with a zero port value to the rejected "m=" line, according to the
>
> procedures in [RFC3264]. In addition, the Answerer MUST NOT anymore
>
> include a mid value, representing the "m=" line, in the SDP group:BUNDLE
>
> attribute midlist associated with the BUNDLE group.
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic