Re: [rtcweb] Plan A, respun

Cullen Jennings <fluffy@iii.ca> Fri, 10 May 2013 20:03 UTC

Return-Path: <fluffy@iii.ca>
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 58E0221F909A for <rtcweb@ietfa.amsl.com>; Fri, 10 May 2013 13:03:37 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ld4Cu-85HnUU for <rtcweb@ietfa.amsl.com>; Fri, 10 May 2013 13:03:31 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id 7A57121F8EAD for <rtcweb@ietf.org>; Fri, 10 May 2013 13:03:31 -0700 (PDT)
Received: from [10.1.4.202] (unknown [75.159.25.213]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 8CA1B509B5; Fri, 10 May 2013 16:03:30 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <FB4F7998-0228-4859-A330-E3D725B5BCCF@csperkins.org>
Date: Fri, 10 May 2013 14:03:28 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <FB13DC39-D7DD-4832-AD2C-9315D278636B@iii.ca>
References: <51894846.3090102@nostrum.com> <518A304A.1030609@alvestrand.no> <D579F433-4E94-4B0D-A281-9BA3C1120C08@csperkins.org> <6C9EAB0E-7E53-4035-9561-2474CD97D50C@iii.ca> <FB4F7998-0228-4859-A330-E3D725B5BCCF@csperkins.org>
To: Colin Perkins <csp@csperkins.org>
X-Mailer: Apple Mail (2.1503)
Cc: 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: Fri, 10 May 2013 20:03:37 -0000

On May 10, 2013, at 12:59 PM, Colin Perkins <csp@csperkins.org> wrote:

> On 10 May 2013, at 17:39, Cullen Jennings wrote:
>> On May 8, 2013, at 4:33 AM, Colin Perkins <csp@csperkins.org> wrote:
>>> I agree: the PT was never intended to be used as a demultiplexing point for different flows in RT
>> 
>> I'm not sure I really agree on this point. Lots of implications use the PT along with the port received on to decide which codec to pass to the RTP packet on to. I think, in practice, the PT has been a very key demux pony for a  long time in RTP. 
> 
> 
> To identify the codec, sure, that's what the PT is designed to do. That's logically separate to identifying the source, which is the role of the SSRC.

But I am not trying to identify the source, if I wanted to do that I agree CSRC would be one of things to use. I am trying to figure out which codec to pass the incoming packet to. I don't mind using SSRC when they are around but when they are not, PT seems perfectly reasonable to use if uniquely identifiers which codec to pass the packet to. I realize that you prefer the shim approach but when there is not a shim, I'm not seeing the problem with using PT. Adam's draft also allows use of SSRC for folks that want to overlap the PT from different m lines. 

Consider a normal SIP call with only single speaker of G.711 audio with early media where two sources are both sending to the same port and PT on that phone. That's normal. It does not need to figure out the sources to render the audio. Sure the codec probably might want to note that a SSRC changed and retrain the jitter buffer but the phone does not care about who the sources are in this case to play them. In more complicated conferring cases the phone could use SSRC/CSRC info to map to roster information received over some other protocol than SDP to display a name for the active speaker or something. But thats a case where who the sources are matters - this is just about getting the media to the right codec on the right m line.