IETF Logo Mail Archive

Re: [rtcweb] Convey "label"

Colin Perkins <csp@csperkins.org> Fri, 09 September 2011 07:18 UTC

Return-Path: <csp@csperkins.org>
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 5B58921F8669 for <rtcweb@ietfa.amsl.com>; Fri, 9 Sep 2011 00:18:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.403
X-Spam-Level:
X-Spam-Status: No, score=-103.403 tagged_above=-999 required=5 tests=[AWL=-0.104, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1, 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 FuugMYDKL79w for <rtcweb@ietfa.amsl.com>; Fri, 9 Sep 2011 00:18:24 -0700 (PDT)
Received: from lon1-msapost-1.mail.demon.net (lon1-msapost-1.mail.demon.net [195.173.77.180]) by ietfa.amsl.com (Postfix) with ESMTP id 991E921F8538 for <rtcweb@ietf.org>; Fri, 9 Sep 2011 00:18:23 -0700 (PDT)
Received: from starkperkins.demon.co.uk ([80.176.158.71] helo=[192.168.0.26]) by lon1-post-1.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1R1vNp-0006Em-Xb; Fri, 09 Sep 2011 07:20:17 +0000
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="iso-8859-1"
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <4E69BB9F.5050802@ericsson.com>
Date: Fri, 09 Sep 2011 08:20:15 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <D60C56CC-FDAB-4953-93D5-48334F80EFD1@csperkins.org>
References: <4E69B77E.7090205@ericsson.com> <DC53C7A0-64E0-4BA1-8111-39B974879DA3@edvina.net> <56C22F41-852F-4B20-A907-1181FE77E854@csperkins.org> <4E69BB9F.5050802@ericsson.com>
To: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
X-Mailer: Apple Mail (2.1084)
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Convey "label"
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, 09 Sep 2011 07:18:25 -0000

On 9 Sep 2011, at 08:09, Stefan Håkansson LK wrote:
> On 2011-09-09 09:07, Colin Perkins wrote:
>> On 9 Sep 2011, at 07:53, Olle E. Johansson wrote:
>>> 9 sep 2011 kl. 08:51 skrev Stefan Håkansson LK:
>>>> there was a discussion yesterday of how to convey the Id (aka "label") of a MediaStream object when it is sent over a PeerConnection. Presumable this info would be in the SDP offer (or whatever we end up using). There was a discussion on if CNAME could be used or if we need something new.
>>>> 
>>>> You mentioned that it would be quite easy to add a new element or attribute if we would need that. Could you explain a bit more?
>>> 
>>> Just a kind reminder that there are application specific fields that we can use in RTCP too...
>> 
>> 
>> I was actually thinking of a new RTCP SDES item type to convey the label.
> 
> Does this mean it would be conveyed by RTCP (and not by e.g. SDP)? (Sorry to ask stupid questions).


I'd guess you'd need something in SDP too, although I haven't followed the API closely enough to be sure. I suggested a new RTCP SDES item because the CNAME didn't seem to have quite the right semantics, but otherwise seemed to be conveyed in the way people wanted.

-- 
Colin Perkins
http://csperkins.org/

v2.23.0 | Report a Bug | By Email