Re: [MMUSIC] BUNDLE TEXT: Offerer procedures (June 6th)

Christer Holmberg <christer.holmberg@ericsson.com> Fri, 07 June 2013 19:16 UTC

Return-Path: <prvs=58703c4c02=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 19F7E21F9712 for <mmusic@ietfa.amsl.com>; Fri, 7 Jun 2013 12:16:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.949
X-Spam-Level:
X-Spam-Status: No, score=-5.949 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, HELO_EQ_SE=0.35, 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 cYiFRYy3XJt5 for <mmusic@ietfa.amsl.com>; Fri, 7 Jun 2013 12:16:32 -0700 (PDT)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id 43F8721F96ED for <mmusic@ietf.org>; Fri, 7 Jun 2013 12:16:32 -0700 (PDT)
X-AuditID: c1b4fb30-b7f9e6d000002643-4a-51b2318c136c
Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 0B.69.09795.C8132B15; Fri, 7 Jun 2013 21:16:28 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.167]) by ESESSHC018.ericsson.se ([153.88.183.72]) with mapi id 14.02.0328.009; Fri, 7 Jun 2013 21:16:28 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Martin Thomson <martin.thomson@gmail.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Thread-Topic: [MMUSIC] BUNDLE TEXT: Offerer procedures (June 6th)
Thread-Index: Ac5iprZaCgBOn7ljRxaMYhEaRiO+KgAHcYEAACvn8mAAB7QFAAADmCWAAASCFY4=
Date: Fri, 7 Jun 2013 19:16:27 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C38501C@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1C383F1E@ESESSMB209.ericsson.se> <51B0BCA8.6050304@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1C384E6D@ESESSMB209.ericsson.se> <51B21700.1020709@alum.mit.edu>, <CABkgnnVh+s0moCw3bbeewZYe8ch+BvQ9e1GLrBtHTVwbJ_Zd4Q@mail.gmail.com>
In-Reply-To: <CABkgnnVh+s0moCw3bbeewZYe8ch+BvQ9e1GLrBtHTVwbJ_Zd4Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.16]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrDLMWRmVeSWpSXmKPExsUyM+JvrW6P4aZAgyXrjC2unfnHaDF1+WMW ixUbDrA6MHv8ff+ByWPnrLvsHkuW/GQKYI7itklKLCkLzkzP07dL4M64N+svc8E89oqzhz+z NDDeYO1i5OSQEDCRWN6/ix3CFpO4cG89WxcjF4eQwGFGiV+/mxkhnMWMEktP7mXpYuTgYBOw kOj+pw3SICIQKtF2cR8jSJhZQF3i6uIgkLCwgIPElg2TWCFKHCUO/NrCBmH7SXw62c4CYrMI qEhs27MTzOYV8JW4dug3K8SqWUwSyxdOAktwCgRKHP40hxnEZgQ67vupNUwgNrOAuMStJ/OZ II4WkFiy5zwzhC0q8fLxP6jHFCV2nm1nhqjXkViw+xMbhK0tsWzha2aIxYISJ2c+YZnAKDYL ydhZSFpmIWmZhaRlASPLKkb23MTMnPRy802MwMg5uOW3wQ7GTffFDjFKc7AoifPq8y4OFBJI TyxJzU5NLUgtii8qzUktPsTIxMEJIrikGhh3SP3fkn7mk+Wms1vulyr3qCdyHpD5l9doKyf+ veXm5bX8l3cUlocnrwu9+GPtok+suwxD19lcFky4ttE9P3K1g7tUqOn36wfuPXU+8Ort75Jn etPCvNqdA6u+hUno96/qun5jz/rVHlGa7PYWmfFFgj7qaisYmxYelyxQffvz9Xmnn6evnNBW YinOSDTUYi4qTgQATku+8G8CAAA=
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] BUNDLE TEXT: Offerer procedures (June 6th)
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, 07 Jun 2013 19:16:39 -0000

Hi,

>> Note that offers and answers may contain more than just one set of bundled
>> m-lines. They may contain unbundled m-lines, and multiple bundles. So the
>> purpose of a particular offer may be complex, trying to satisfy different
>> needs for various parts of the SDP. That complicates making such a
>> distinction.
>
> I thought about this, but forgot to followup.  I think that it could
> be possible for a single request to be a BSO for one group, which a
> BRO for another.  The labels are a convenience only, and provide a way
> to provide guidance about how to handle offer/answer creation...scoped
> only to the affected m-lines.  I think that the complication is only a
> complication insofar as it requires some text that highlights this.

I agree. The scope of a BRO or BSO is only per individual BUNDLE group within an SDP Offer - not the whole SDP Offer.

Regards,

Christer