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

Christer Holmberg <christer.holmberg@ericsson.com> Mon, 10 June 2013 12:49 UTC

Return-Path: <prvs=78731f4a8f=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 B86B821F88AC for <mmusic@ietfa.amsl.com>; Mon, 10 Jun 2013 05:49:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.077
X-Spam-Level:
X-Spam-Status: No, score=-6.077 tagged_above=-999 required=5 tests=[AWL=0.172, 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 crtL4O-kgJP7 for <mmusic@ietfa.amsl.com>; Mon, 10 Jun 2013 05:49:32 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id C5A6421F9349 for <mmusic@ietf.org>; Mon, 10 Jun 2013 05:47:57 -0700 (PDT)
X-AuditID: c1b4fb25-b7f4c6d000004656-9c-51b5cafc6331
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 86.B5.18006.CFAC5B15; Mon, 10 Jun 2013 14:47:56 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.167]) by ESESSHC013.ericsson.se ([153.88.183.57]) with mapi id 14.02.0328.009; Mon, 10 Jun 2013 14:47:56 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] BUNDLE TEXT: Offerer procedures (June 6th)
Thread-Index: Ac5iprZaCgBOn7ljRxaMYhEaRiO+KgAHcYEAAMTTumA=
Date: Mon, 10 Jun 2013 12:47:55 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C3872B7@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1C383F1E@ESESSMB209.ericsson.se> <51B0BCA8.6050304@alum.mit.edu>
In-Reply-To: <51B0BCA8.6050304@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.17]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrCLMWRmVeSWpSXmKPExsUyM+Jvre6fU1sDDc4/1bWYuvwxi8WKDQdY HZg8/r7/wOSxZMlPpgCmKG6bpMSSsuDM9Dx9uwTujF+H1jAWPOKouNTzjLGB8QlbFyMnh4SA icSO/nnsELaYxIV764HiXBxCAocZJVbv/MoO4SxhlLg7rYmli5GDg03AQqL7nzZIg4iAr8Sz x7fBBgkLOEhs2TCJFSLuKHHg1xY2kHIRASuJ/3czQMIsAqoSqy58YQaxeYFap247A1YuJJAv MWfuSxYQm1NAR+L//cVgNYxA93w/tYYJxGYWEJe49WQ+E8SdAhJL9pxnhrBFJV4+/scKskpC QFFieb8cRLmOxILdn9ggbG2JZQtfQ60VlDg58wnLBEbRWUimzkLSMgtJyywkLQsYWVYxsucm ZuaklxttYgRGwsEtv1V3MN45J3KIUZqDRUmcV493caCQQHpiSWp2ampBalF8UWlOavEhRiYO ThDBJdXAuO1CwpldVU6R7/996I82u1LB82DH1ujctjv5XV9cp/4sD/iwwHvxgpZvuorhUy5M OeBa6p/nLcWwZ0eKY7yVeOLe/mvLLQ2nTm8TKjOptdn6QvOpxiWJq/2B6ybMqL/+xk7shtfF Kfe31+/sU7gvbbHg28YpExUCwi2F0yZNeXXgyq/Z7NtdliqxFGckGmoxFxUnAgCwpdpeVwIA AA==
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: Mon, 10 Jun 2013 12:49:39 -0000

Hi Paul,

A comment on some of the stuff you sent earlier.

> ISTM that all bundle offers must meet some constraints:
> - some of the m-lines may have *unique* addresses
> - all the rest, if any, must have a single *common* address.
> - if any share a common address, then the first mid in the
    bundle group must identify one of them

What is the reason for the third bullet?

For example, assume I am adding a new "m=" line, with a unique address, and I would like that address to become the new bundle address.

In the existing "m=" lines, I couldn't keep the previously negotiated bundle address, because based on the third bullet the first mid would have to identity one of those. So, I would have to either:

1) Assign a unique address to each of the existing "m=" lines, which would then allow me to request the address of the new "m=" line to become the new bundle address; or

2) I would have to assign the suggested new bundle address to ALL "m=" lines (the existing ones and the new one).

Note that both 1) and 2) are allowed today.

Regards,

Christer