Re: [rtcweb] How to multiplex between peers

Harald Alvestrand <harald@alvestrand.no> Thu, 21 July 2011 11:05 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 2910121F8B0A for <rtcweb@ietfa.amsl.com>; Thu, 21 Jul 2011 04:05:33 -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=[AWL=0.000, 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 KDVX4uL-S4DL for <rtcweb@ietfa.amsl.com>; Thu, 21 Jul 2011 04:05:32 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 878E721F8A4E for <rtcweb@ietf.org>; Thu, 21 Jul 2011 04:05:32 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id D662D39E13B for <rtcweb@ietf.org>; Thu, 21 Jul 2011 13:04:25 +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 84vOC53FBXDb for <rtcweb@ietf.org>; Thu, 21 Jul 2011 13:04: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 45E7E39E0FC for <rtcweb@ietf.org>; Thu, 21 Jul 2011 13:04:25 +0200 (CEST)
Message-ID: <4E2807FA.7020405@alvestrand.no>
Date: Thu, 21 Jul 2011 13:05: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: <CD06E3C9-8AE3-406C-BE7B-587FE331263A@csperkins.org> <CA4D1E42.2EB93%stewe@stewe.org> <EDC0A1AE77C57744B664A310A0B23AE21FD07B86@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE21FD07B86@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.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 11:05:33 -0000

On 07/21/11 12:44, DRAGE, Keith (Keith) wrote:
> This discussion seems to be hovering in some sort of middle ground.
>
> Either 1)
>
> It has not decided what transport to use for real time data, in which case it should document the requirements for such a transport protocol, and then evaluate whether existing solutions meet those requirements, versus developing an entirely new protocol.
>
> Or 2)
>
> I has decided that RTP should be used, in which case it should identify the shortcomings (i.e. a set of requirements on how it needs to be further developed) and send these to the AVTCORE working group.
Don't forget

3)

It has decided that RTP should be used, with no changes and no new 
extensions, and is going through the ritual of swearing at the resulting 
shortcomings while figuring out which parts of RTP it can say "we don't 
need them, so it's OK to do things that mean we can't use them" to.

If this group gets lined up behind an 1-year dependency on another group 
before it can deliver its initial work products, this group is going to 
be irrelevant.

               Harald