Re: [rtcweb] How to multiplex between peers

Matthew Kaufman <matthew.kaufman@skype.net> Wed, 20 July 2011 23:15 UTC

Return-Path: <matthew.kaufman@skype.net>
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 F3C7221F8A80 for <rtcweb@ietfa.amsl.com>; Wed, 20 Jul 2011 16:15:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.584
X-Spam-Level:
X-Spam-Status: No, score=-2.584 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599]
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 Jtb6I5-UA1QO for <rtcweb@ietfa.amsl.com>; Wed, 20 Jul 2011 16:15:11 -0700 (PDT)
Received: from mx.skype.net (mx.skype.net [78.141.177.88]) by ietfa.amsl.com (Postfix) with ESMTP id DE4D621F8A4E for <rtcweb@ietf.org>; Wed, 20 Jul 2011 16:15:10 -0700 (PDT)
Received: from mx.skype.net (localhost [127.0.0.1]) by mx.skype.net (Postfix) with ESMTP id 83B11170B; Thu, 21 Jul 2011 01:15:09 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=skype.net; h=subject :mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=mx; bh=eX PF3Q4OFGP5oE7Vswdjupu9uxs=; b=QdTiD23U7LHaw3fu7c76IqWjslbzd1Beih W8AoxozK7f1zrjzlTOsRR48OCTS6Cp4yo3qLRDsKkbgTGBRTpUZPtzeBZFEZ1CBg O+XVR91KPZ9T5rR3EQD+v94X35XA3Qgck2Qa5MCil3BLkJMdu6XxpnPuISAVz2nu pcGSkRhzY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=skype.net; h=subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to; q=dns; s=mx; b=B1vK7G7G5MvNqHE75m7NPB hbeyvPq/SJk62r8Czmv4tjhy5P7l85MfhE1+ZDGX3Wn8CAl4ecFAmFHVgDJW3Pr6 ElrSDqSTiVWVv24IyNq9LLNUJA4eVCcHL4/KiX8WjL+BBT9ckZIIVC0NgUk2V/8i B+ywCLmwl4Kvp6yrkZykc=
Received: from zimbra.skype.net (zimbra.skype.net [78.141.177.82]) by mx.skype.net (Postfix) with ESMTP id 820E87F6; Thu, 21 Jul 2011 01:15:09 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by zimbra.skype.net (Postfix) with ESMTP id 1E91835074D8; Thu, 21 Jul 2011 01:15:07 +0200 (CEST)
X-Virus-Scanned: amavisd-new at lu2-zimbra.skype.net
Received: from zimbra.skype.net ([127.0.0.1]) by localhost (zimbra.skype.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QCs0iaJGlgO5; Thu, 21 Jul 2011 01:15:07 +0200 (CEST)
Received: from [172.17.61.96] (50-0-2-20.static.sonic.net [50.0.2.20]) by zimbra.skype.net (Postfix) with ESMTPSA id 4BCDB350796D; Thu, 21 Jul 2011 01:15:02 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset="us-ascii"
From: Matthew Kaufman <matthew.kaufman@skype.net>
In-Reply-To: <DB9A2414-CE23-4F6E-811D-DEEBAF6E0280@csperkins.org>
Date: Wed, 20 Jul 2011 16:15:01 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <03887CB7-98FE-47F0-ACEF-105B3E7917A6@skype.net>
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> <DB9A2414-CE23-4F6E-811D-DEEBAF6E0280@csperkins.org>
To: Colin Perkins <csp@csperkins.org>
X-Mailer: Apple Mail (2.1082)
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 23:15:15 -0000

On Jul 20, 2011, at 3:31 PM, Colin Perkins wrote:

> Except that it doesn't work in all cases: please read the discussion in draft-perkins-rtpweb-rtp-usage-02. You may argue that you don't think the breakage is important, but there *is* breakage in doing this, and it is not backwards compatible.
> 

It doesn't need to be "backwards compatible" in order for two RTCWEB endpoints to communicate. And the muxing can be disabled in order to talk to a legacy endpoint.

Could we confine the claims about breakage to only ones that are NOT backwards compatibility issues?

Matthew Kaufman