IETF Logo Mail Archive

Re: [rtcweb] How to multiplex between peers

Matthew Kaufman <matthew.kaufman@skype.net> Thu, 21 July 2011 04:06 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 78F8321F85C7 for <rtcweb@ietfa.amsl.com>; Wed, 20 Jul 2011 21:06:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 OwqZT5XFJohR for <rtcweb@ietfa.amsl.com>; Wed, 20 Jul 2011 21:06:19 -0700 (PDT)
Received: from mx.skype.net (mx.skype.net [78.141.177.88]) by ietfa.amsl.com (Postfix) with ESMTP id 41ABA21F85C4 for <rtcweb@ietf.org>; Wed, 20 Jul 2011 21:06:19 -0700 (PDT)
Received: from mx.skype.net (localhost [127.0.0.1]) by mx.skype.net (Postfix) with ESMTP id 2D3C6170C; Thu, 21 Jul 2011 06:06:18 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=skype.net; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=mx; bh=KnksLI/VShSJ0m flwitI/2kToUY=; b=xC9epDjQ+fUBKK6fZMVJN5CXePBGgo3oK3lQ01sOrZ4xZI ruxsYzUXU1wp7nbct7qzpQNjzzSorS1/xWVUoWewuRFrN9Kc/pwbpFtMJTV4xhqr sieCyrBOmVMXBJFZ9jzDP929nqDhdxG15JhcnusWkL0wVn0LkhiaGKeF0Wqb4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=skype.net; h=message-id:date:from :mime-version:to:cc:subject:references:in-reply-to:content-type: content-transfer-encoding; q=dns; s=mx; b=XeAs3PMAkc0/JezdeFq0iX ewMc/evUvs3tx/t60NOVB2lcyniaRkxdHCB/sYCNYOlzu1eG+aXuXjuFPvB/Bl1n Eec4ejZvZwj+OQ7Qrw5vxCEels9JGcDvY75X3MUbhbDxbB9Kdyp5Fow7ycjyULnx WGIPXsOCrIM1rubmEzGo8=
Received: from zimbra.skype.net (zimbra.skype.net [78.141.177.82]) by mx.skype.net (Postfix) with ESMTP id 2BB7C7FC; Thu, 21 Jul 2011 06:06:18 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by zimbra.skype.net (Postfix) with ESMTP id 0C1C435078B1; Thu, 21 Jul 2011 06:06:18 +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 xKyi9cA+QDXb; Thu, 21 Jul 2011 06:06:17 +0200 (CEST)
Received: from [10.10.155.2] (unknown [198.202.199.254]) by zimbra.skype.net (Postfix) with ESMTPSA id 0236C3507895; Thu, 21 Jul 2011 06:06:16 +0200 (CEST)
Message-ID: <4E27A5AF.3010009@skype.net>
Date: Wed, 20 Jul 2011 21:06:07 -0700
From: Matthew Kaufman <matthew.kaufman@skype.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: igor.faynberg@alcatel-lucent.com
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> <03887CB7-98FE-47F0-ACEF-105B3E7917A6@skype.net> <4E279E30.40604@alcatel-lucent.com>
In-Reply-To: <4E279E30.40604@alcatel-lucent.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: 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: Thu, 21 Jul 2011 04:06:23 -0000

On 7/20/2011 8:34 PM, Igor Faynberg wrote:
>
> I think the decision on whether to ignore backward compatibility ought 
> to be made when there is an agreement on core use cases and it is 
> understood that none of them would be broken by lack of backward 
> compatibility.

It is trivial to demonstrate that an RTCWEB endpoint talking to another 
RTCWEB endpoint has no issues with backward compatibility.

The deceptive conflation of (possible) real issues with using SSRC as a 
multiplexing point for A+V over RTP for RTCWEB to RTCWEB and the class 
of issues that are ONLY relevant when talking RTCWEB to something that 
requires backwards compatibility is taking us farther, rather than 
closer, to a resolution on this issue. Once we agree to RTCWEB to Legacy 
will not use SSRC for multiplexing, there is no need, whatsoever, to 
bring up the potential backwards compatibility issues again.

Matthew Kaufman

v2.23.0 | Report a Bug | By Email