Re: [MMUSIC] DECISION (BERLIN-Q5): When the BUNDLE address is RE-negotiated, the Offerer can assign the requsted new address to all m- lines immediately, without first offering unique addresses.
Paul Kyzivat <pkyzivat@alum.mit.edu> Tue, 27 August 2013 13:42 UTC
Return-Path: <pkyzivat@alum.mit.edu>
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 9F59D21E8094 for <mmusic@ietfa.amsl.com>; Tue, 27 Aug 2013 06:42:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.01
X-Spam-Level:
X-Spam-Status: No, score=-0.01 tagged_above=-999 required=5 tests=[AWL=-0.173, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, J_CHICKENPOX_56=0.6, RDNS_NONE=0.1]
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 l+iogXDIS1jT for <mmusic@ietfa.amsl.com>; Tue, 27 Aug 2013 06:42:46 -0700 (PDT)
Received: from qmta14.westchester.pa.mail.comcast.net (qmta14.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:212]) by ietfa.amsl.com (Postfix) with ESMTP id D307221E80B9 for <mmusic@ietf.org>; Tue, 27 Aug 2013 06:42:45 -0700 (PDT)
Received: from omta13.westchester.pa.mail.comcast.net ([76.96.62.52]) by qmta14.westchester.pa.mail.comcast.net with comcast id HnSK1m00717dt5G5Epiluc; Tue, 27 Aug 2013 13:42:45 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta13.westchester.pa.mail.comcast.net with comcast id Hpik1m0153ZTu2S3ZpikAf; Tue, 27 Aug 2013 13:42:45 +0000
Message-ID: <521CACD4.6060904@alum.mit.edu>
Date: Tue, 27 Aug 2013 09:42:44 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1C47762C@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C47762C@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1377610965; bh=OJeGCeQibAnD5gq1Lqiz7Z+mF5DfMi8eYwzBpDxPwoM=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=JFcyy7NqMcSziUZMjC8mUiVmAM0xQ5VdYSMaEsk2o941xK8J7i4Gt9GIaHNV7wB4P trx+nG9o5pK6mMv9Vy9qzFyKo61rhJP4mVbG8jlijGEWT09fdDdZ0JKLTwg82tvEG0 5wlxqDM5SbZmW8j0WPVRtFYPb7LNq+EHHqGy0c7rn5hT1P4X/nyPvHUMIcJkdKOCUP EiH+7kXsybmg7OcXHkTrQc2M2kBxHakwHQd1sJP7WSY5kna8C3/4MvR9RBJZTqJQqI Krd0FidnRXPqZovxj8R2wMlxugMrXL/GkTvLu7/pH27RjJPWah2TdrYrYp78uOemxf Wj3eaztKIh+oQ==
Subject: Re: [MMUSIC] DECISION (BERLIN-Q5): When the BUNDLE address is RE-negotiated, the Offerer can assign the requsted new address to all m- lines immediately, without first offering unique addresses.
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: Tue, 27 Aug 2013 13:42:51 -0000
This seems reasonable to me. Thanks, Paul On 8/23/13 6:39 AM, Christer Holmberg wrote: > Hi, > > One of the open issues related to BUNDLE presented in Berlin (Q5 in my > slides) was whether, once a BUNDLE address is re-negotiated (i.e. the > usage of BUNDLE etc has already been negotiated), it is allowed to > assign the new suggested BUNDLE address to all “m=” lines immediately, > instead of doing the 2-step Offer/Answer procedure. The outcome was that > it shall be allowed. > > So, based on that, I am suggesting the change below to section 6.1.4 of > BUNDLE. > > NOTE that this only applies to the case where a BUNDLE address is > RE-negotiated (e.g. in a re-INVITE). There is still a discussion about > the initial Offer, and that outcome of that (and the outcome of the UP > discussions) may obviously also impact the text. But, let’s keep that > separate for now, and only focus on the case when a BUNDLE address is > RE-negotiated :) > > Regards, > > Christer > > ------------------------------------------- > > OLD TEXT (BUNDLE-04): > > ==================== > > 6.4.1. SDP Offerer Bundle Address Request and Usage > > An Offerer can assign a BUNDLE address to multiple "m=" lines in a > > BUNDLE group, once the Answerer has selected the BUNDLE address for > > the Offerer. An Offerer MUST NOT assign a BUNDLE address to multiple > > "m=" lines until the Answerer has selected the BUNDLE address. > > OPEN ISSUE: Should it be allowed to assign a new BUNDLE address to > > multiple "m=" lines in a BUNDLE group, before the Answerer has > > selected the BUNDLE address? > > In order to negotiate (or, to re-negotiate) the BUNDLE address > > associated with a BUNDLE group, the Offerer, in the SDP Offer, > > assigns a unique address to each "m=" line in the BUNDLE group. In > > addition, the Offerer indicates which unique address it wishes the > > Answerer to select as the Offerer's BUNDLE address. The Offerer > > places the mid, associated with the unique address requested to be > > selected as the BUNDLE address, first in the SDP group:BUNDLE > > attribute mid list. The Answerer will then select the BUNDLE address > > for the Offerer ([ref-to-be-added]). > > If the Offerer, in a subsequent SDP Offer, wants to re-negotiate the > > BUNDLE address associated with a BUNDLE group, it MAY assign the > > previously negotiated BUNDLE address as a unique address to one of > > the "m=" lines in the BUNDLE group. > > If the Offerer assigns the previously selected BUNDLE address to more > > than one "m=" line in a BUNDLE group, the first mid in the SDP > > group:BUNDLE attribute mid list MUST represent an "m=" line to which > > the BUNDLE address is assigned. Hence, in order to re-negotiate the > > BUNDLE address, the Offerer needs to assign a unique address to each > > "m=" line in the BUNDLE group, as described above. > > An Offerer MUST NOT assign a BUNDLE address to an "m=" line that is > > not associated with a BUNDLE group. An Offerer MUST NOT assign a > > BUNDLE address, that has been negotiated for a BUNDLE group, to an > > "m=" line that is associated with another BUNDLE group. > > Section 10.1 shows an example of a Bundle Address Request. > > SUGGESTED NEW TEXT: > > =================== > > 6.4.1. SDP Offerer Bundle Address Request and Usage > > > > An Offerer can assign a BUNDLE address to multiple "m=" lines in a > > BUNDLE group, once the Answerer has selected the BUNDLE address for > > the Offerer. An Offerer MUST NOT assign a BUNDLE address to multiple > > "m=" lines until the Answerer has selected the BUNDLE address. > > > > Before the Answerer has selected a BUNDLE address for the Offerer, > > in order to negotiate the BUNDLE address associated with a BUNDLE > > group, the Offerer, in the SDP Offer, assigns a unique address to > > each "m=" line in the BUNDLE group. In addition, the Offerer indicates > > which unique address it wishes the Answerer to select as the > > Offerer's BUNDLE address. The Offerer places the mid, associated > > with the unique address requested to be selected as the BUNDLE address, > > first in the SDP group:BUNDLE attribute mid list. The Answerer will > > then select the BUNDLE address for the Offerer ([ref-to-be-added]). > > > > If an Offerer, in a subsequent SDP Offer, wants to re-negotiate the > > BUNDLE address associated with a BUNDLE group, it can either: > > > > - Assign the requested new BUNDLE address to all “m=” lines in the > > BUNDLE group; or > > - In the same way as described in the procedures above, assign a > > unique address to each “m=” line in the BUNDLE group (the previously > > negotiated BUNDLE address can also be assigned as a unique address > > to one of the “m=” lines in the BUNDLE group). > > > > In both cases, the Offerer places the mid, associated with the unique > > address requested to be selected as the BUNDLE address, first in the > > SDP group:BUNDLE attribute mid list (if the requested new BUNDLE address > > is assigned to all “m=” lines in the BUNDLE group, all mids in the SDP > > group:BUNDLE attribute mid list will represent that same address). > > > > An Offerer MUST NOT assign a BUNDLE address to an "m=" line that is > > not associated with a BUNDLE group. An Offerer MUST NOT assign a > > BUNDLE address, that has been negotiated for a BUNDLE group, to an > > "m=" line that is associated with another BUNDLE group. > > > > Section 10.1 shows an example of a Bundle Address Request. > > > > _______________________________________________ > mmusic mailing list > mmusic@ietf.org > https://www.ietf.org/mailman/listinfo/mmusic >
- [MMUSIC] DECISION (BERLIN-Q5): When the BUNDLE ad… Christer Holmberg
- Re: [MMUSIC] DECISION (BERLIN-Q5): When the BUNDL… Paul Kyzivat
- Re: [MMUSIC] DECISION (BERLIN-Q5): When the BUNDL… Christer Holmberg
- Re: [MMUSIC] DECISION (BERLIN-Q5): When the BUNDL… Hadriel Kaplan
- Re: [MMUSIC] DECISION (BERLIN-Q5): When the BUNDL… Christer Holmberg
- Re: [MMUSIC] DECISION (BERLIN-Q5): When the BUNDL… Hadriel Kaplan
- Re: [MMUSIC] DECISION (BERLIN-Q5): When the BUNDL… Christer Holmberg
- Re: [MMUSIC] DECISION (BERLIN-Q5): When the BUNDL… Hadriel Kaplan
- Re: [MMUSIC] DECISION (BERLIN-Q5): When the BUNDL… Christer Holmberg
- Re: [MMUSIC] DECISION (BERLIN-Q5): When the BUNDL… Paul Kyzivat
- Re: [MMUSIC] DECISION (BERLIN-Q5): When the BUNDL… Paul Kyzivat
- Re: [MMUSIC] DECISION (BERLIN-Q5): When the BUNDL… Christer Holmberg
- Re: [MMUSIC] DECISION (BERLIN-Q5): When the BUNDL… Paul Kyzivat
- Re: [MMUSIC] DECISION (BERLIN-Q5): When the BUNDL… Mary Barnes
- Re: [MMUSIC] DECISION (BERLIN-Q5): When the BUNDL… Christer Holmberg