IETF Logo Mail Archive

Re: [MMUSIC] BUNDLE DECISSION: SDP Answer Restrictions

Paul Kyzivat <pkyzivat@alum.mit.edu> Fri, 24 May 2013 14:41 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 12C2521F9362 for <mmusic@ietfa.amsl.com>; Fri, 24 May 2013 07:41:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.308
X-Spam-Level:
X-Spam-Status: No, score=-0.308 tagged_above=-999 required=5 tests=[AWL=0.129, 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 i9pwBO4Zy7iH for <mmusic@ietfa.amsl.com>; Fri, 24 May 2013 07:41:02 -0700 (PDT)
Received: from qmta15.westchester.pa.mail.comcast.net (qmta15.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:228]) by ietfa.amsl.com (Postfix) with ESMTP id 460AE21F9349 for <mmusic@ietf.org>; Fri, 24 May 2013 07:41:02 -0700 (PDT)
Received: from omta19.westchester.pa.mail.comcast.net ([76.96.62.98]) by qmta15.westchester.pa.mail.comcast.net with comcast id fnXA1l00327AodY5Fqh17t; Fri, 24 May 2013 14:41:01 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta19.westchester.pa.mail.comcast.net with comcast id fqh11l00s3ZTu2S3fqh1eJ; Fri, 24 May 2013 14:41:01 +0000
Message-ID: <519F7BFC.2040008@alum.mit.edu>
Date: Fri, 24 May 2013 10:41:00 -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: mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1C377967@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C377967@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1369406461; bh=eAVgRn0MRRF6arhWP55C2FnCe/OB3a4bb4srYLNWeas=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=J/BwTPk9zpU2+sTx6X5MoshKYJbbbuPjgV7YiREfiFRMAXAtWiJaNI19qdoR/9gwV 82yDLWq2JS9ASg+knf3lJL+C12oDNfP6uj3mswYEN+IxIR2YmD8o8vHv0HRv0EJXYO LRAR654uIBCTnA7xWC9r8zLAaMMfnYdSMkxUPMnsu+554yf6hCf02SQlUWgLx2IwdO pJL6+jOJ6+2/t3Sn70IfLqiGncc/B/47IHX6bOA8Tc91ZDDnk9VFEMxJwkFMdZW1p+ A/WeFq/hjxXHWzx3bTLaBgb1OWu1CRl8Q9tans/qyB6D7ujk7qVl3fDSb4PyzXjbX6 EQE6xVZ+dWXXA==
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: Fri, 24 May 2013 14:41:07 -0000

I object to (5) below (see inline).
Otherwise these seem ok to me.

	Thanks,
	Paul

On 5/24/13 8:32 AM, Christer Holmberg wrote:
> 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.

> 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.
>
> So, if anyone OBJECTS to the restrictions above, please indicate so.
>
> Regards,
>
> Christer
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

v2.23.0 | Report a Bug | By Email