Re: [MMUSIC] BUNDLE: no reason por payload type to be unique within bundled m= lines

Colin Perkins <csp@csperkins.org> Thu, 17 March 2016 10:30 UTC

Return-Path: <csp@csperkins.org>
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 E9E0612D636 for <mmusic@ietfa.amsl.com>; Thu, 17 Mar 2016 03:30:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GMOhRBQoo0HU for <mmusic@ietfa.amsl.com>; Thu, 17 Mar 2016 03:30:47 -0700 (PDT)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E3ECF12D5BF for <mmusic@ietf.org>; Thu, 17 Mar 2016 03:30:46 -0700 (PDT)
Received: from [130.209.247.112] (port=63247 helo=mangole.dcs.gla.ac.uk) by balrog.mythic-beasts.com with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <csp@csperkins.org>) id 1agVCT-0006vA-6L; Thu, 17 Mar 2016 10:30:44 +0000
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <CALiegfmzO_1nuQmE3SYJk-OtYZ2GHzjfTzkgJ=1zwoRcD+NmCw@mail.gmail.com>
Date: Thu, 17 Mar 2016 10:30:37 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <CF1984E6-C1C8-41C5-8B7F-02988342E930@csperkins.org>
References: <CALiegfm7Rb4e5DFGycr=EsdigE1XFCUiqNL6+GpRSyrGe=_RWg@mail.gmail.com> <56DED735.1000101@ericsson.com> <CALiegf=G77JOcoR6DORnPsMx4OCgy=_dYQ_r8KfjMy_33vn89A@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37E9EA74@ESESSMB209.ericsson.se> <CALiegf=F4z9r+oCO1DMW_nXq7TBJjf-n3N1r6yr5tLoksXtUqg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37E9FDAB@ESESSMB209.ericsson.se> <CALiegf=kzThQ3n+Z-=E8G=ivyL1W=Q4gUcQenihAJ3pmv8udKQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37EA257B@ESESSMB209.ericsson.se> <CALiegfnLMUZnA=AQEnvFhxKKbwUeg=sFHRiC9R2MxisY-43UFg@mail.gmail.com> <D31037D8.5B90%christer.holmberg@ericsson.com> <CALiegfmWPrai9a1hkj5rpLeyowspAcpr3jNZpNyc4HatXGfo9Q@mail.gmail.com> <D3103E3F.5BBE%christer.holmberg@ericsson.com> <CALiegfmzO_1nuQmE3SYJk-OtYZ2GHzjfTzkgJ=1zwoRcD+NmCw@mail.gmail.com>
To: Iñaki Baz Castillo <ibc@aliax.net>
X-Mailer: Apple Mail (2.3112)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold = On =
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/Qb2CQgEnYCLryq2qVNaQCH_p-mU>
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] BUNDLE: no reason por payload type to be unique within bundled m= lines
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 17 Mar 2016 10:30:52 -0000

> On 17 Mar 2016, at 09:30, Iñaki Baz Castillo <ibc@aliax.net> wrote:
> 
> 2016-03-17 10:09 GMT+01:00 Christer Holmberg <christer.holmberg@ericsson.com>:
>>> I just hope that BUNDLE is a required step in order to separate each
>>> RTP "sender" and RTP "receiver" within a RTP session, so in the future
>>> we can get rid of SDP and design a proper RTP parameters based API for
>>> WebRTC.
>> 
>> 
>> That is not the purpose of BUNDLE. The purpose is to be able to negotiate
>> multiplexed media on a single RTP session
> 
> - "RTP session" == stuff carried over a single transport (let's assume
> rtcp-mux always).

No, RTP session == shared SSRC space [RFC 3550, Section 3, Page 10]. RTCP mux is irrelevant for whether there is a single RTP session or not, and an RTP session can span multiple transports.

> - "media" == audio / video / data, which can be sent and/or received.
> 
> So yes, BUNDLE somehow allows defining each RTP sender and/or receiver
> in a separate m= section.
> 
> 
>> If we want to change the rule saying that PT values must be unique per
>> codec/codec configuration, I think that¹s a separate task.
> 
> We can't do that because there are a lot of legacy and very expensive
> RTP middleboxes made in 20th century that miraculously are suitable
> for WebRTC even if they don't even know what a SSRC is. And they must
> work without any code update!
> 
> 
> -- 
> Iñaki Baz Castillo
> <ibc@aliax.net>
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic



-- 
Colin Perkins
https://csperkins.org/