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

Christer Holmberg <christer.holmberg@ericsson.com> Sat, 15 June 2013 08:55 UTC

Return-Path: <prvs=78786d6c08=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 284F721F9B17 for <mmusic@ietfa.amsl.com>; Sat, 15 Jun 2013 01:55:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.608
X-Spam-Level:
X-Spam-Status: No, score=-5.608 tagged_above=-999 required=5 tests=[AWL=0.641, 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 cIMQw926El8a for <mmusic@ietfa.amsl.com>; Sat, 15 Jun 2013 01:55:21 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 767ED21F9ACC for <mmusic@ietf.org>; Sat, 15 Jun 2013 01:55:21 -0700 (PDT)
X-AuditID: c1b4fb25-b7f4c6d000004656-c6-51bc2bf5a925
Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 8F.C6.18006.5FB2CB15; Sat, 15 Jun 2013 10:55:17 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.6]) by ESESSHC017.ericsson.se ([153.88.183.69]) with mapi id 14.02.0328.009; Sat, 15 Jun 2013 10:55:17 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Thread-Topic: VS: [MMUSIC] BUNDLE TEXT: Offerer procedures (June 12th)
Thread-Index: Ac5nc6hv2h/XxszpTAuUKcpTd0hH9AA24L0AABt8NdAAF/qngAAH50mwAAElZgAAGOPAkA==
Date: Sat, 15 Jun 2013 08:55:16 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C393AFA@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1C388BD8@ESESSMB209.ericsson.se> <51BA08D0.3030301@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1C38AA73@ESESSMB209.ericsson.se> <51BB622F.60007@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1C38AF86@ESESSMB209.ericsson.se> <51BB9EEA.7050009@alum.mit.edu>
In-Reply-To: <51BB9EEA.7050009@alum.mit.edu>
Accept-Language: en-US
Content-Language: fi-FI
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.148]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrILMWRmVeSWpSXmKPExsUyM+Jvre5X7T2BBhcW6FtMXf6YxWLFhgOs Dkwef99/YPJYsuQnUwBTFLdNUmJJWXBmep6+XQJ3xo45j5kLZrBX7Nw5kb2B8TJrFyMnh4SA icS6F9cYIWwxiQv31rN1MXJxCAkcZpT41/qaCcJZxChxasEhoCoODjYBC4nuf9ogpoiAhsSk rWogJrOAusTVxUEgY4QFXCUmvTjJAmKLCLhJPH/9nhXCDpN4Ma0XzGYRUJU48PooG4jNK+Ar 8frRZhaITTuZJHYeXwJ2D6eAjsTzDZ1ggxiBbvt+ag0TiM0sIC7x4eB1ZoibBSSW7DkPZYtK vHz8D+ovJYnGJU9YIep1JBbs/sQGYWtLLFv4mhlisaDEyZlPWCYwis1CMnYWkpZZSFpmIWlZ wMiyipE9NzEzJ73caBMjMEYObvmtuoPxzjmRQ4zSHCxK4rwfT+0KFBJITyxJzU5NLUgtii8q zUktPsTIxMEJIrikGhjDjr2XesvOIZvd8fxQX98xp7sGq27yl/N+unm6SDT0Q726QtH9ggMz U1vv3zRyOLw9o7u3x+r43u4Xnuzv29wX5p/9vdYyYU7HNuO3OyK5t9yZ5H0sdgqPsV7kBLkd 4Qx7/0k/2PymPOzrYxHeR/1RP12TVI6k78hKblz+KeJp0tLLD+uVjfcosRRnJBpqMRcVJwIA IUekpmQCAAA=
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] BUNDLE TEXT: Offerer procedures (June 12th)
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: Sat, 15 Jun 2013 08:55:28 -0000

Hi,

> (The quoting here is getting rather unmanageable.
> I'm trimming, but maybe we need to start over fresh.)

I think the only technical issue is whether it's allowed to:

1) Assign an address to multiple m- line before it has been selected as a bundle address; and

2) Whether it's allowed to assign an address to multiple m- line before the Answerer has indicated *in the SDP Answer* whether it supports BUNDLE.

The two are of course related, because in order to allow 2) we also need to allow 1) :)

I personally don't have any problems with you suggestion (it will require some editorial work, but technically there should be no issues). 

However, it does sound very much like my original BUNDLE proposal (where the Offerer ALWAYS assigned the bundle address to all m- lines), so I'd like to hear what others - especially Cullen - thinks about it.

Regards,

Christer