Re: [MMUSIC] BUNDLE DECISSION: SDP Answer Restrictions

Christer Holmberg <christer.holmberg@ericsson.com> Mon, 27 May 2013 10:53 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 7D53421F8EA5 for <mmusic@ietfa.amsl.com>; Mon, 27 May 2013 03:53:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.861
X-Spam-Level:
X-Spam-Status: No, score=-5.861 tagged_above=-999 required=5 tests=[AWL=0.388, 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 jFkv6Fv4-x3P for <mmusic@ietfa.amsl.com>; Mon, 27 May 2013 03:53:46 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id CFD9D21F8D70 for <mmusic@ietf.org>; Mon, 27 May 2013 03:53:45 -0700 (PDT)
X-AuditID: c1b4fb2d-b7fe36d000007102-a1-51a33b38df3b
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 18.BB.28930.83B33A15; Mon, 27 May 2013 12:53:44 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.167]) by ESESSHC007.ericsson.se ([153.88.183.39]) with mapi id 14.02.0328.009; Mon, 27 May 2013 12:53:44 +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 DECISSION: SDP Answer Restrictions
Thread-Index: Ac5YdJNWNYfYqobOTueV815jNgS21wAB15gAAJLnc9A=
Date: Mon, 27 May 2013 10:53:43 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C3797E8@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1C377967@ESESSMB209.ericsson.se> <519F7BFC.2040008@alum.mit.edu>
In-Reply-To: <519F7BFC.2040008@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+NgFtrLLMWRmVeSWpSXmKPExsUyM+Jvra6F9eJAgytdmhZTlz9msVix4QCr A5PH3/cfmDyWLPnJFMAUxWWTkpqTWZZapG+XwJXx+mA7c8ECgYqvm54xNjB+4eli5OSQEDCR ePxqBQuELSZx4d56ti5GLg4hgcOMEsd2v2cDSQgJLGGUuP5ZsouRg4NNwEKi+582SFhEwFfi 2ePbYCXCAvYSN//1M0PEHSSmHV/MDlIuImAlcXy/PEiYRUBV4tGsI2CreIFaVxx4wAgxPV/i 3NI/YHFOAR2Jcwv7weKMQOd8P7WGCcRmFhCXuPVkPhPEmQISS/acZ4awRSVePv7HCrJKQkBR Ynm/HES5jsSC3Z/YIGxtiWULXzNDrBWUODnzCcsERtFZSKbOQtIyC0nLLCQtCxhZVjGy5yZm 5qSXG25iBEbBwS2/dXcwnjoncohRmoNFSZxXj3dxoJBAemJJanZqakFqUXxRaU5q8SFGJg5O qQbGCeyJrxvWXJWsPOvgGzLlT+8m67pjexIe+pW+v2Zyqb9D+FZKsfCkY/qqr2W1N78zaMtc LbG4eaPcZ/ZJH4orW5fJVb7c6KoiqNss5VRzaPXk/aYJESqNQlIhp575bVNXNtsk5sHnp2b+ qKm/357H0azYLqm/4k+gcaS5v7SmzLkYyeVdXkosxRmJhlrMRcWJAIHHu2lQAgAA
Subject: Re: [MMUSIC] BUNDLE DECISSION: SDP Answer Restrictions
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, 27 May 2013 10:53:52 -0000

Hi,

>> At the interim meeting yesterday, we agreed on some restrictions 
>> regarding creating SDP answers containing bundle group(s).
>>
>> Note that the restrictions 1-3 are simply alignments with RFC 5888, 
>> and are listed simply for clarification purpose. Restrictions 4 is 
>> BUNDLE specific. Restriction 5 is also alignment with RFC 5888, as m- 
>> lines with port zero are not allowed within groups, but we will need 
>> some clarification text saying that a new offer will have to be sent 
>> in order to remove a stream (either from a bundle group, or completely 
>> from the session).
>>
>> (Note that the text below is not necessarily the wording that will go 
>> into the draft)
>>
>> In an SDP answer:
>>
>> 1)a BUNDLE group MUST NOT be created, unless it was included in the 
>> associated offer
>>
>> 2)an m- line MUST NOT be added to a BUNDLE group, unless it was 
>> included in a BUNDLE group in the associated offer
>>
>> 3)an m- line MUST NOT be added to another BUNDLE group than the group 
>> in which was included in the associated offer
>>
>> 4)an m- line MUST NOT be removed from a BUNDLE group if, in the 
>> associated offer, an identical port number was indicated for all m- 
>> lines in a BUNDLE group
>>
>> 5)an m- line MUST NOT be rejected if, in the associated offer, an 
>> identical port number was indicated for all m- lines in a BUNDLE group
>
> Where did (5) come from? And what is the justification for it?
> I can see no good reason to impose this restriction.

I was checking my notes, but could not find anything justifying it. Maybe I mixed it up with the offer restrictions we were discussing...

> Note that there is also a discussion regarding bundle offers, e.g. 
> when restrictions when adding new m- lines to a bundle. Based on the 
> outcome of that, there may be some additional answer restrictions, e.g.
> regarding the change of bundle transport parameters. But, let's deal 
> with that in the offer thread.

Yes.

Regards,

Christer