Re: [rtcweb] How to multiplex between peers

Harald Alvestrand <harald@alvestrand.no> Thu, 21 July 2011 09:16 UTC

Return-Path: <harald@alvestrand.no>
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 6DD2521F89C1 for <rtcweb@ietfa.amsl.com>; Thu, 21 Jul 2011 02:16:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 MEfAuM2gTVOk for <rtcweb@ietfa.amsl.com>; Thu, 21 Jul 2011 02:16:36 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 679D621F88DC for <rtcweb@ietf.org>; Thu, 21 Jul 2011 02:16:36 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 457F739E0FC for <rtcweb@ietf.org>; Thu, 21 Jul 2011 11:15:29 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1pRVQz6ZWf5Q for <rtcweb@ietf.org>; Thu, 21 Jul 2011 11:15:25 +0200 (CEST)
Received: from hta-dell.lul.corp.google.com (62-20-124-50.customer.telia.com [62.20.124.50]) by eikenes.alvestrand.no (Postfix) with ESMTPS id 31EBA39E0FA for <rtcweb@ietf.org>; Thu, 21 Jul 2011 11:15:25 +0200 (CEST)
Message-ID: <4E27EE6E.30600@alvestrand.no>
Date: Thu, 21 Jul 2011 11:16:30 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <CA4CDFF2.1C5A3%henry.sinnreich@gmail.com>
In-Reply-To: <CA4CDFF2.1C5A3%henry.sinnreich@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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: Thu, 21 Jul 2011 09:16:40 -0000

On 07/21/11 02:41, Henry Sinnreich wrote:
> +1
>
>> 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.
> Not to forget disposing of ancient SDP as well.
> Use standard metadata instead, since it is equally usable for all apps, not
> only for RTC apps.
Henry, which standard?
http://www.xkcd.com/927/ applies to metadata too, I think.

> Thanks, Henry
>
>
> On 7/20/11 5:38 PM, "Matthew Kaufman"<matthew.kaufman@skype.net>  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.
>>
>> Matthew Kaufman
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>