IETF Logo Mail Archive

Re: [MMUSIC] BUNDLE DECISSION: SDP Answer Restrictions

"Cullen Jennings (fluffy)" <fluffy@cisco.com> Mon, 27 May 2013 13:31 UTC

Return-Path: <fluffy@cisco.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 1E10721F9696 for <mmusic@ietfa.amsl.com>; Mon, 27 May 2013 06:31:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.299
X-Spam-Level:
X-Spam-Status: No, score=-110.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 EMuGa+63vWkJ for <mmusic@ietfa.amsl.com>; Mon, 27 May 2013 06:31:38 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 424D721F95EF for <mmusic@ietf.org>; Mon, 27 May 2013 06:31:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2408; q=dns/txt; s=iport; t=1369661498; x=1370871098; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=jg0yjP1Kx3813GcGTpyRpLxnRBD1xr2SX7kXBClxvPg=; b=DYzP1XsIWawYnuAM51NWpvoxLZhEyyVFidTwjTyeYZXrJD1uGztzaMip Nf6+FVTzjWPDkSDurQ/aC5wT1xs3xU1PuZ9QVlPkHo+JGo2XBgIF49clb V1Hosevx/U/Csd5A2mgCEB7wv3GZzUgcjX4v4n6phLhAGyJ2n+ZzTCl83 Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AncFAEJfo1GtJXG+/2dsb2JhbABagwgwwgSBBRZ0giMBAQEDAQEBAWsLBQsCAQgiJCcLJQIEDgUIh38GDL1sBI5qAjEHgnNhA4wwhzqKYYowgw+CJw
X-IronPort-AV: E=Sophos;i="4.87,751,1363132800"; d="scan'208";a="215380960"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-5.cisco.com with ESMTP; 27 May 2013 13:31:37 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r4RDVbV7030835 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 27 May 2013 13:31:37 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.36]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.02.0318.004; Mon, 27 May 2013 08:31:37 -0500
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Thread-Topic: [MMUSIC] BUNDLE DECISSION: SDP Answer Restrictions
Thread-Index: AQHOWt6DXXiL+A3G8kewvn8ifQrPzg==
Date: Mon, 27 May 2013 13:30:55 +0000
Message-ID: <C5E08FE080ACFD4DAE31E4BDBF944EB11351850D@xmb-aln-x02.cisco.com>
References: <7594FB04B1934943A5C02806D1A2204B1C377967@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C377967@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <8D10D614B08ADA4289C4B6ACAF187725@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
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 13:31:43 -0000

4 and 5 are very confusing and do not match the notes I had from the call. I'm pretty sure I disagree with both of them. 

>From a requirement point of view, I think it is very important that the answer be able to reject any m-line by setting it's port to zero.




On May 24, 2013, at 6:32 AM, Christer Holmberg <christer.holmberg@ericsson.com> 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
>  
>  
> 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