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

Paul Kyzivat <pkyzivat@alum.mit.edu> Mon, 10 June 2013 16:50 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 DA27721F96C2 for <mmusic@ietfa.amsl.com>; Mon, 10 Jun 2013 09:50:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.41
X-Spam-Level:
X-Spam-Status: No, score=-0.41 tagged_above=-999 required=5 tests=[AWL=0.027, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, 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 2pr+7bVuqESJ for <mmusic@ietfa.amsl.com>; Mon, 10 Jun 2013 09:50:46 -0700 (PDT)
Received: from qmta07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:64]) by ietfa.amsl.com (Postfix) with ESMTP id 3A74F21F96C6 for <mmusic@ietf.org>; Mon, 10 Jun 2013 09:50:44 -0700 (PDT)
Received: from omta23.westchester.pa.mail.comcast.net ([76.96.62.74]) by qmta07.westchester.pa.mail.comcast.net with comcast id mam31l00A1c6gX857gqjNT; Mon, 10 Jun 2013 16:50:43 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta23.westchester.pa.mail.comcast.net with comcast id mgqj1l00u3ZTu2S3jgqjXf; Mon, 10 Jun 2013 16:50:43 +0000
Message-ID: <51B603E2.6030306@alum.mit.edu>
Date: Mon, 10 Jun 2013 12:50:42 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B1C383F1E@ESESSMB209.ericsson.se> <51B0BCA8.6050304@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1C3872B7@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C3872B7@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1370883043; bh=m/RhkFi7j1nRAS9Rgo74VwT5CYUCU85hbQI9gtcSPbQ=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=fWpdzpEBaltnAT8dDff78Hk3faFoEUXYhcsvs1XWUbCtlclowoBI02R8OCYa/mCb6 fdwRY/bVu/gDH8TYIKsiixt/Ql4yiA4DzqbCnGUeUVN8Dc05JXCSx5dfJ8R5poOiLi 9JKKveyZnANsCAk3AbQj9sszjQHFntgWSVDVTwmhE+bPoyDTHsRLXGhj9rGqoaLX9q YhaTqk8M+6USy06eelmapF7svGRrW8xjSIGRw6vFiSeHNaNQLWoKxvKvmKd0oiWsop RpUsb7VJGhot9ojGRy5Tf3f8HTD930JuOhdmdCQTfefcFrXNqpjFpN6vrXxXhMunxe 7PDzCth2Dz3lA==
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: Mon, 10 Jun 2013 16:50:52 -0000

On 6/10/13 8:47 AM, Christer Holmberg wrote:
> 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.

OK, I didn't think of that case.
So I guess that constraint should be removed.

	Thanks,
	Paul