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

Christer Holmberg <christer.holmberg@ericsson.com> Tue, 11 February 2014 17:50 UTC

Return-Path: <christer.holmberg@ericsson.com>
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 A618E1A0689 for <rtcweb@ietfa.amsl.com>; Tue, 11 Feb 2014 09:50:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.85
X-Spam-Level:
X-Spam-Status: No, score=-3.85 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 G7FLOawMgUkL for <rtcweb@ietfa.amsl.com>; Tue, 11 Feb 2014 09:50:40 -0800 (PST)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id E9B481A0691 for <rtcweb@ietf.org>; Tue, 11 Feb 2014 09:50:39 -0800 (PST)
X-AuditID: c1b4fb25-b7f038e000005d01-d1-52fa62ee6287
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id B5.E8.23809.EE26AF25; Tue, 11 Feb 2014 18:50:38 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.99]) by ESESSHC013.ericsson.se ([153.88.183.57]) with mapi id 14.02.0387.000; Tue, 11 Feb 2014 18:50:38 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: RTCWEB Data Channel Protocol: Label vs Protocol glare
Thread-Index: Ac8nUY8MdmECwmXERwuUTRwOK9mRzA==
Date: Tue, 11 Feb 2014 17:50:38 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D16D248@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.146]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D16D248ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrGLMWRmVeSWpSXmKPExsUyM+Jvje67pF9BBntnWlus/dfO7sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujJ1PtzAWfFSsOHO5nbmBcZZsFyMnh4SAiUTn5v/sELaYxIV7 69m6GLk4hAQOMUqc3XiWFcJZzCixv+M7UBUHB5uAhUT3P22QBhEBdYnLDy+ANQsL2ElMWP2G CSLuLPH2z1IoW09i/ZszjCA2i4CqxM2p88HivAK+Eh27P4DFGYEWfz+1BizOLCAucesJRI2E gIDEkj3nmSFsUYmXj/+xQthKEj82XGKBqM+XmHV8JjPETEGJkzOfsExgFJqFZNQsJGWzkJRB xHUkFuz+xAZha0ssW/iaGcY+c+AxE7L4Akb2VYzsuYmZOenlRpsYgWF/cMtv1R2Md86JHGKU 5mBREuf98NY5SEggPbEkNTs1tSC1KL6oNCe1+BAjEwenVAPjiv6nC17XHPGyFd/YzcciK3wu ySvBJvHJp5rOhzIm/bfXnMsSWHX7zIW8P7lXUqOMDac1aUm9265V2GM2I/fB5l8ncq9NnpZ8 gtHrTrbg8v2BSR+uZe48pM/Z/Njgy5psfYkF9//Nakp7tq6+NMXjs8tUlz9/V2zqPLFc0yX9 +PV/F8syPTf+V2Ipzkg01GIuKk4EADhD74xJAgAA
Subject: [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: Tue, 11 Feb 2014 17:50:42 -0000

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.

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).

Regards,

Christer