[MMUSIC] BUNDLE DECISSION: Full bundle or no bundle - there aint anything in between

Christer Holmberg <christer.holmberg@ericsson.com> Fri, 24 May 2013 10:28 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 5E1A421F8EA4 for <mmusic@ietfa.amsl.com>; Fri, 24 May 2013 03:28:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.808
X-Spam-Level:
X-Spam-Status: No, score=-5.808 tagged_above=-999 required=5 tests=[AWL=-0.160, BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, J_CHICKENPOX_47=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 Zd7sLrdnipwI for <mmusic@ietfa.amsl.com>; Fri, 24 May 2013 03:28:38 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 9841521F8EFE for <mmusic@ietf.org>; Fri, 24 May 2013 03:28:37 -0700 (PDT)
X-AuditID: c1b4fb25-b7efb6d000007c26-d1-519f40d45a96
Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id A1.7A.31782.4D04F915; Fri, 24 May 2013 12:28:36 +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, 24 May 2013 12:28:35 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: BUNDLE DECISSION: Full bundle or no bundle - there aint anything in between
Thread-Index: Ac5YZ89eNSNKdC6FQhCoA7qw0p8XLA==
Date: Fri, 24 May 2013 10:28:35 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C3777C9@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.17]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1C3777C9ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrMLMWRmVeSWpSXmKPExsUyM+Jvre4Vh/mBBkeeK1tMXf6YxYHRY8mS n0wBjFFcNimpOZllqUX6dglcGduWX2QpuKhasWUVVwPjUYUuRg4OCQETibfbxbsYOYFMMYkL 99azdTFycQgJHGaUuHv2OyOEs4RR4tG1dhaQBjYBC4nuf9ogDSIC6hJf9/Ywg9jCAmESx27s Z4eIR0s8nHIHytaTOLFuGiOIzSKgKvHrx102EJtXwFdiRv8PMJsRaPH3U2uYQGxmAXGJW0/m M0EcJCCxZM95ZghbVOLl43+sEDcrSizvl4Moz5eY2f6OFWKkoMTJmU9YJjAKzUIyaRaSsllI yiDiOhILdn9ig7C1JZYtfM0MY5858JgJWXwBI/sqRvbcxMyc9HKjTYzAgD+45bfqDsY750QO MUpzsCiJ8/ZqTw0UEkhPLEnNTk0tSC2KLyrNSS0+xMjEwSnVwKiwPmbjsr+OmwSdTntbtN/d 9DV5scTvW6Kf37gmPy+bW39P04PPfOKxl2cv7kqz3rznmZDkkWcPGsp/7W2eVl7VNvfRvvtf rYtnOvza7FkzaerBUrmnvNvnJTRaft3Qc6++9tjnRmVZsXlbdwn8S7JUlNcS2/a11TDk4s0N bu3G92XDb+go9i5XYinOSDTUYi4qTgQAg1Hpc0YCAAA=
Subject: [MMUSIC] BUNDLE DECISSION: Full bundle or no bundle - there aint anything in between
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, 24 May 2013 10:28:44 -0000

Hi,

At the interim yesterday, we agreed that an answerer MUST always include identical ports* (usage of port zero within a bundle is a separate topic) for all m- lines within an bundle group.

If the answerer wants to use different ports* for some/all m- lines, it MUST NOT include those m- lines in a bundle group (if they already are in a bundle group, a separate offer is needed to remove them).

WHAT IT MEANS: There is no way for an answerer to tell that the offerer, for certain m- lines, can use the same port*, eventhough the answer will use separate ports*.

I will work on some actual text proposal later, but please indicate if you OBJECT to this approach in general.

Regards,

Christer

NOTE: "port" = port:address combination - we are working on coming up with better terminology :)