Re: [rtcweb] RTCWEB Data Channel Protocol: Label vs Protocol glare

Paul Kyzivat <pkyzivat@alum.mit.edu> Wed, 12 February 2014 03:56 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4387C1A0814 for <rtcweb@ietfa.amsl.com>; Tue, 11 Feb 2014 19:56:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZaMieHUvxLjn for <rtcweb@ietfa.amsl.com>; Tue, 11 Feb 2014 19:56:11 -0800 (PST)
Received: from qmta06.westchester.pa.mail.comcast.net (qmta06.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:56]) by ietfa.amsl.com (Postfix) with ESMTP id CF5641A0806 for <rtcweb@ietf.org>; Tue, 11 Feb 2014 19:56:10 -0800 (PST)
Received: from omta01.westchester.pa.mail.comcast.net ([76.96.62.11]) by qmta06.westchester.pa.mail.comcast.net with comcast id RFVe1n0020EZKEL56Fw9TR; Wed, 12 Feb 2014 03:56:09 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta01.westchester.pa.mail.comcast.net with comcast id RFw91n00V3ZTu2S3MFw9Fn; Wed, 12 Feb 2014 03:56:09 +0000
Message-ID: <52FAF0D9.6040703@alum.mit.edu>
Date: Tue, 11 Feb 2014 22:56:09 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1D16D248@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D16D248@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1392177369; bh=LO4l1ynSGHGm50fTr1x2mdhmI3VvReXpYUj2wXH92u8=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=XL4ZtfIhMrWiVQNnIxuzA8SyZ9LWl0yGKvjaqd1/jPc++uMw/j/+Vkk3DEBdV+RaH UV4W9MTLQJHySkgYdm+mNI8f0WrwdeMk7XefIKs//W9DU51M28mG8XvmsM0TDOJoq3 urHEbXZWkeaDdUDM5yxgxLKGi1w15BW/JcRGsv7Dzow6QY89BVzCOo1MQ3on37lsdg PvXgXMlSGtLw4Nr4IeNiHwalnOlgDPEOpjy2pdjNdYl0S1Mlwys4z1HElqEcX7IF7t ctgfSGXlH4ITKyucxV2VD671Io72nIwx+zxmgRXC0E0RpEMctyKyllGEB4H5JZyVhj S/+WcAJiYlyIw==
Subject: Re: [rtcweb] RTCWEB Data Channel Protocol: Label vs Protocol glare
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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, 12 Feb 2014 03:56:12 -0000

On 2/11/14 12:50 PM, Christer Holmberg wrote:
> Hi,
>
> The draft says:
>
> “Note: There is no attempt to resolve label glare; if both sides open
>
>                  a Channel labeled "x" at the same time, there will be
> two Channels
>
>                  labeled "x" - one on an even Stream pair, one on an odd
> pair.”
>
> I think the text shall be extended to also cover the Protocol, i.e. both
> ends can try to open a channel for protocol X at the same time.

And that should be fine.

Having two channels with the same protocol is analogous to having two 
audio rtp m-lines.

> Also, even if there is a label glare, it doesn’t have to be for the same
> protocol. As far as I know, endpoints can choose whatever label value
> they want, and they don’t even need to be for the same protcol (unless
> specific protocols define what label value(s) must be used for channels
> associated with that protocol).

IIUC the point is for applications to manage the label namespace as they 
wish.

	Thanks,
	Paul

> Regards,
>
> Christer
>
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>