[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.

Christer Holmberg <christer.holmberg@ericsson.com> Fri, 23 August 2013 10:39 UTC

Return-Path: <christer.holmberg@ericsson.com>
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 EBE7911E80F7 for <mmusic@ietfa.amsl.com>; Fri, 23 Aug 2013 03:39:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.688
X-Spam-Level:
X-Spam-Status: No, score=-5.688 tagged_above=-999 required=5 tests=[AWL=-0.040, BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, J_CHICKENPOX_56=0.6, RCVD_IN_DNSWL_MED=-4]
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 kqcJE5qRmvOU for <mmusic@ietfa.amsl.com>; Fri, 23 Aug 2013 03:39:40 -0700 (PDT)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id B5E6011E80E7 for <mmusic@ietf.org>; Fri, 23 Aug 2013 03:39:39 -0700 (PDT)
X-AuditID: c1b4fb30-b7f9a8e000005620-fb-52173be7f186
Received: from ESESSHC008.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 19.78.22048.7EB37125; Fri, 23 Aug 2013 12:39:36 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.146]) by ESESSHC008.ericsson.se ([153.88.183.42]) with mapi id 14.02.0328.009; Fri, 23 Aug 2013 12:39:35 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: mmusic <mmusic@ietf.org>
Thread-Topic: 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.
Thread-Index: Ac6f7OG1P0YUwhF6Remol1dqLcLlOQ==
Date: Fri, 23 Aug 2013 10:39:34 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C47762C@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.19]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1C47762CESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrJLMWRmVeSWpSXmKPExsUyM+Jvje4La/Egg59BFlOXP2ZxYPRYsuQn UwBjFJdNSmpOZllqkb5dAlfG5z/nWQq6djJWfP7wg7mB8dt8xi5GTg4JAROJyUcnQNliEhfu rWfrYuTiEBI4zCgxa/ERVghnCaPE9M79LF2MHBxsAhYS3f+0QRpEBGQk9m7azAxSIyxwiFHi 6txpYA0iAscZJT5+f8YEUaUncXPPLXYQm0VAVWLunSdgNq+Ar8TCznnMIDYj0Orvp9aA1TML iEvcejKfCeIkAYkle84zQ9iiEi8f/2OFsBUl2p82MELU50scu70RaqagxMmZT1gmMArNQjJq FpKyWUjKIOI6Egt2f2KDsLUlli18zQxjnznwmAlZfAEj+ypG9tzEzJz0cvNNjMDgP7jlt8EO xk33xQ4xSnOwKInzbtY7EygkkJ5YkpqdmlqQWhRfVJqTWnyIkYmDU6qBMTRpk+rXU5u3HLn3 WUnjxoK4/XyKZmK2HzesrN+7OTn48M0CyQ8K/40Evxz984WPM1/+Nd8au1dHzhvqVG0KnJb1 fHn6LKXs2hk7flhbrtVvuF/mdTA2NFRZeooA917F+Bdf1uzTkFpf4KO9xvq2Ji/XR6tFil2M 6dP22HDcU5z+9upWN+spf5VYijMSDbWYi4oTAR6SZ4RMAgAA
Subject: [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: Fri, 23 Aug 2013 10:39:47 -0000

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.