Re: [MMUSIC] BUNDLE Weekly Summary: Assumptions

Christer Holmberg <christer.holmberg@ericsson.com> Fri, 03 May 2013 17:44 UTC

Return-Path: <prvs=783586931d=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 DB8CD21F85DB for <mmusic@ietfa.amsl.com>; Fri, 3 May 2013 10:44:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.35
X-Spam-Level:
X-Spam-Status: No, score=-3.35 tagged_above=-999 required=5 tests=[AWL=0.300, 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 93iY2L9HdUNh for <mmusic@ietfa.amsl.com>; Fri, 3 May 2013 10:44:12 -0700 (PDT)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id 284A521F882A for <mmusic@ietf.org>; Fri, 3 May 2013 10:41:10 -0700 (PDT)
X-AuditID: c1b4fb30-b7f3a6d0000007a4-bc-5183f6b5573d
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id C8.75.01956.5B6F3815; Fri, 3 May 2013 19:41:10 +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; Fri, 3 May 2013 19:41:09 +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 Weekly Summary: Assumptions
Thread-Index: Ac5H/Rv/zjNZSPPjTceQWRJyHaV9rQAAF6iAAAnhX7Y=
Date: Fri, 3 May 2013 17:41:08 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C36B6A6@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1C36B485@ESESSMB209.ericsson.se>, <5183CFDD.90203@alum.mit.edu>
In-Reply-To: <5183CFDD.90203@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.19]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrCLMWRmVeSWpSXmKPExsUyM+Jvre62b82BBk3z2SymLn/MYrFiwwFW ByaPv+8/MHksWfKTKYApitsmKbGkLDgzPU/fLoE7Y/ruHawFu7gr2p7ENTB+4+hi5OSQEDCR WPRyLyOELSZx4d56ti5GLg4hgcOMEtOOHmeGcBYzSjRNX8fSxcjBwSZgIdH9TxukQUTAV+LZ 49tsILYwUPjDocVgJSIClhKr73tBlFhJ7Js4mwXEZhFQkehY2cMKYvMCtc7ec50JxBYSyJY4 v/w82A2cAloSyw9fZgaxGYHu+X5qDVgNs4C4xK0n85kg7hSQWLLnPDOELSrx8vE/VghbUaL9 aQMjRL2BxPtz85khbG2JZQtfM0PsFZQ4OfMJywRG0VlIxs5C0jILScssJC0LGFlWMbLnJmbm pJebb2IERsLBLb8NdjBuui92iFGag0VJnDeZqzFQSCA9sSQ1OzW1ILUovqg0J7X4ECMTByeI 4JJqYGSbzLhVR2JGSM2MfGaulWddkvPXFh3t6v3mvESSt/TZPlXVwqoLdcELZ5nXLDg1WYfn ihCzQWi3lfazlN6j30R+25w0nD31WUjOtBfB+p8/Xu9RP56XsmHixnkb2D2ePs5K1i1nsD0m cWrjiVkuvnoyWzkvrT51SX5h2+4WhxvOt/43vH3XM0WJpTgj0VCLuag4EQBH+9TzVwIAAA==
Subject: Re: [MMUSIC] BUNDLE Weekly Summary: Assumptions
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, 03 May 2013 17:44:24 -0000

Hi,

>> In order to try to close issues on BUNDLE, based on the discussions
>> we’ve had, I intend to update the BUNDLE draft based on the following
>> assumptions:
>>
>> 1.We mandate usage of rtcp-mux when BUNDLE is used.
>
> Are you going to include the possibility of bundling non-RTP m-lines?
> (Needed if we are to include DTLS/SCTP.)

Yes.

I guess I should have listed that as a third assumption.

> If so, then of course the use of rtcp-mux only applies to RTP m-lines.

Correct.

> (Of course, if only one DTLS/SCTP line can be included, a bundle without
> RTP is not very interesting. But it doesn't hurt to make this ready for
> future bundling of other things.)

Agree. My intention is not to mandate a BUNDLE group to contain RTP media.

>> 2.SDP m- lines with a zero port value MUST NOT be put inside a BUNDLE
>> group (not in an offer, nor in an answer). There will be a note
>> indicating that, due to this, the number of m- lines associated with a
>> BUNDLE group may differ between the offer and the associated answer.
>> There will also be a note indicating that this is due to RFC 5888, in
>> case people later start to wonder where the “MUST NOT” comes from.
>>
>> Please indicate if you OBJECT to any of these assumptions.
>
> Aside from the above comment I have no objections.

And, the zero port value restriction would of course apply to any media type (not only RTP).

Regards,

Christer