Re: [rtcweb] How to multiplex between peers

Dzonatas Sol <dzonatas@gmail.com> Mon, 17 October 2011 20:58 UTC

Return-Path: <dzonatas@gmail.com>
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 34F0E21F8BA8 for <rtcweb@ietfa.amsl.com>; Mon, 17 Oct 2011 13:58:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.156
X-Spam-Level:
X-Spam-Status: No, score=-3.156 tagged_above=-999 required=5 tests=[AWL=-0.442, BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 R-sAr85fF1gQ for <rtcweb@ietfa.amsl.com>; Mon, 17 Oct 2011 13:58:13 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 13FD521F8B9F for <rtcweb@ietf.org>; Mon, 17 Oct 2011 13:58:12 -0700 (PDT)
Received: by vcbfo1 with SMTP id fo1so3554437vcb.31 for <rtcweb@ietf.org>; Mon, 17 Oct 2011 13:58:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=2kaL5BllWpsE6eizemPnU4prBsOp38N12dUm+N1hxSA=; b=HH9W0n+C45rQsa6xPZ9vXo5o9vuioDWTeKVWW2C1V+8MOKEgCBbgzXpZssRwmI32Vw AcJ1ZrJbm0cLdgEzqHmbvDNkrPhnCy/DGYDlY4Mi8I5sLR0MGC+rjKKJey5xJCjuslyD uZgS64MRYDaVsJZyTZF9Yr5UPN+ZHsaX/wSzU=
MIME-Version: 1.0
Received: by 10.52.37.72 with SMTP id w8mr21878108vdj.32.1318885092363; Mon, 17 Oct 2011 13:58:12 -0700 (PDT)
Received: by 10.52.107.202 with HTTP; Mon, 17 Oct 2011 13:58:11 -0700 (PDT)
In-Reply-To: <4E27EE6E.30600@alvestrand.no>
References: <CA4CDFF2.1C5A3%henry.sinnreich@gmail.com> <4E27EE6E.30600@alvestrand.no>
Date: Mon, 17 Oct 2011 13:58:11 -0700
Message-ID: <CAAPAK-50B74tmrvZ+75aYsiwxfvv41akCXOtnrNOdL6jimazGQ@mail.gmail.com>
From: Dzonatas Sol <dzonatas@gmail.com>
To: rtcweb@ietf.org
Content-Type: multipart/alternative; boundary=20cf307ac7836e0bb104af84ddb9
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: Mon, 17 Oct 2011 20:58:14 -0000

I got this Quantum Vibe link from an /. ad:
http://shar.es/bqNgs<http://t.co/RprNtB3k>

I think that be a link-in-a-link, a meta-link, or a canonical multiplexer in
pix#4; it applies to B2B and the server-to-server paradigm is not obvious.

...anymore. ;)

On Thu, Jul 21, 2011 at 2:16 AM, Harald Alvestrand <harald@alvestrand.no>wrote;wrote:

> 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.
>
>
>