Re: [rtcweb] How to multiplex between peers

Colin Perkins <csp@csperkins.org> Wed, 20 July 2011 22:48 UTC

Return-Path: <csp@csperkins.org>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8644921F8509 for <rtcweb@ietfa.amsl.com>; Wed, 20 Jul 2011 15:48:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level:
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Q1RfOEc5FiS for <rtcweb@ietfa.amsl.com>; Wed, 20 Jul 2011 15:48:18 -0700 (PDT)
Received: from lon1-msapost-1.mail.demon.net (lon1-msapost-1.mail.demon.net [195.173.77.180]) by ietfa.amsl.com (Postfix) with ESMTP id 55F4921F8AEA for <rtcweb@ietf.org>; Wed, 20 Jul 2011 15:48:18 -0700 (PDT)
Received: from starkperkins.demon.co.uk ([80.176.158.71] helo=[192.168.0.26]) by lon1-post-1.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1QjfYv-00025b-X1; Wed, 20 Jul 2011 22:48:17 +0000
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <4E275900.1@skype.net>
Date: Wed, 20 Jul 2011 23:48:16 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <B369B7F3-2691-4E4B-8022-5465AD70086A@csperkins.org>
References: <4E259EAD.3060505@ericsson.com> <FAE78F7C-8C51-41C4-B3D7-6497396E12A5@cisco.com> <4E26C5CF.1080007@ericsson.com> <BLU152-W54BE1A03753680FF0094C4934C0@phx.gbl> <CAOJ7v-2kwiCipJSHmNT9GuGJJzEjPV-X00TLnf-LwbsJ1ADwDw@mail.gmail.com> <896BDC4C-849C-4553-89C8-7EFEF9FFEC6B@skype.net> <38DF8F00ABAB77498A75469448CB081B3AE69BEBC4@BE235.mail.lan> <CAB+e8F6dbTEDDorimVgKuFq5EAXGyy6FFKXC7JQ3=qieqnOnpQ@mail.gmail.com> <CD928305-E886-431E-8CC8-5A0F85B44D23@csperkins.org> <4E275900.1@skype.net>
To: Matthew Kaufman <matthew.kaufman@skype.net>
X-Mailer: Apple Mail (2.1084)
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] How to multiplex between peers
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jul 2011 22:48:22 -0000

On 20 Jul 2011, at 23:38, Matthew Kaufman wrote:
> On 7/20/2011 3:31 PM, Colin Perkins wrote:
>> On 20 Jul 2011, at 22:15, Aron Rosenberg wrote:
>>> Another +1 for multiplexing everything together. My only worry is that the base spec for RTCP doesn't mandate that SSRC is included in every RTCP message type, and thus you could end up with the multiplexing layer needing to understand every  RTCP messaged used for video (TMMBR, TMMBN, etc)
>> 
>> ...which is another reason why this doesn't work in all cases, in addition to the reasons we document in draft-perkins-rtcweb-rtp-usage-02
>> 
> 
> So let me get this straight... RTP and RTCP is broken and inflexible and therefore we must use it, and use it in the broken and inflexible way?
> 
> If anything this is an argument for ignoring RTP and RTCP and doing something entirely new that is actually appropriate for what we're trying to build, not living with crap just because there's an RFC for it.


You're free to re-invent that wheel, if you wish. However, if you want to use RTP for RTCWeb, then you need to accept that doing so has both some advantages and some disadvantages. One of those disadvantages, for this application domain, is that it requires an explicit demultiplexing layer for distinct RTP sessions. Whether that demultiplexing layer is UDP, or some yet-to-be defined shim layer is a question for this working group, but something is needed if RTP is used.

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