Re: [rtcweb] Plan A, respun

Adam Roach <adam@nostrum.com> Mon, 20 May 2013 12:19 UTC

Return-Path: <adam@nostrum.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 2D70621F859B for <rtcweb@ietfa.amsl.com>; Mon, 20 May 2013 05:19:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level:
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
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 Nao8sC-hI+JF for <rtcweb@ietfa.amsl.com>; Mon, 20 May 2013 05:19:29 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 9A9DA21F856D for <rtcweb@ietf.org>; Mon, 20 May 2013 05:19:29 -0700 (PDT)
Received: from Orochi.local (203-69-99-17.HINET-IP.hinet.net [203.69.99.17] (may be forged)) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r4KCJIvO085997 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 20 May 2013 07:19:20 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <519A14C6.7000009@nostrum.com>
Date: Mon, 20 May 2013 20:19:18 +0800
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Colin Perkins <csp@csperkins.org>
References: <51894846.3090102@nostrum.com> <518A304A.1030609@alvestrand.no> <518F6338.8070903@jitsi.org> <518F83E5.4060209@alvestrand.no> <519519DB.6050702@nostrum.com> <519524EA.3000509@alvestrand.no> <51952860.5030906@nostrum.com> <5195304B.10706@alvestrand.no> <CABcZeBO+miF-euyyKFDrpMUdnV-Ej2QaZgKmiMc2Yp08QUyz7A@mail.gmail.com> <5195CEDF.9040109@alvestrand.no> <CABkgnnWbkX-+mLU+o6MfwTB3nyD2weudGg6tOR-U8zXrctm7_A@mail.gmail.com> <5199F0A0.8020406@nostrum.com> <A5A19E8A-01BB-4925-BD54-B5381ECA3E42@csperkins.org>
In-Reply-To: <A5A19E8A-01BB-4925-BD54-B5381ECA3E42@csperkins.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 203.69.99.17 is authenticated by a trusted mechanism)
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Plan A, respun
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, 20 May 2013 12:19:30 -0000

On 5/20/13 19:17, Colin Perkins wrote:
> On 20 May 2013, at 10:45, Adam Roach wrote:
>> On 5/18/13 00:10, Martin Thomson wrote:
>>
>>> Let's be very, very precise about this.
>>>
>>> Demultiplexing is *always* performed based on SSRC.  It's just that
>>> correlation with signaling components (the m-line in this case) might
>>> use of PT in the absence of prior knowledge of SSRC.
>>>
>>> We didn't get this quite right in Plan A.
>> Yeah, that's a valid point. It's not really being proposed as a demux point as much as a correlation token. Thanks for clearing that up -- we should definitely clear that up in the next version of the document.
>
> Rather than try to overload the PT, I would suggest we define an explicit correlation token that can be sent. Put something in RTCP SDES and/or RTP header extensions, and in the SDP, to signal what RTP flow corresponds to what m-line.
>

That kind of defeats some of the purpose here, which includes working 
with existing deployed implementations.

/a