Re: [rtcweb] Data channel setup: scalability, user experience, labels

Martin Thomson <martin.thomson@gmail.com> Thu, 07 March 2013 20:00 UTC

Return-Path: <martin.thomson@gmail.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 76E0021F8C7C for <rtcweb@ietfa.amsl.com>; Thu, 7 Mar 2013 12:00:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level:
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, NO_RELAYS=-0.001]
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 BSrONnxc1aow for <rtcweb@ietfa.amsl.com>; Thu, 7 Mar 2013 12:00:48 -0800 (PST)
Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) by ietfa.amsl.com (Postfix) with ESMTP id A843821F8C2C for <rtcweb@ietf.org>; Thu, 7 Mar 2013 12:00:26 -0800 (PST)
Received: by mail-wg0-f41.google.com with SMTP id ds1so7393329wgb.0 for <rtcweb@ietf.org>; Thu, 07 Mar 2013 12:00:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=BosxONkfJUAMyC0vBKgJ4MAGeMH+scmqKCIjsnG1ooI=; b=z0A3PB9f4WRtI18t8BdqM9+DbvAsI2R7wDr/AAabEiiw8WZ5AkuGseZsiPf4Fp8giT o8pE99xXFK44oqodzFjxa3K2HLJJ4JH4OYILM5yyx9KRxhtZ/EycXmmO1LIw0BUeyw3P sQNCIQxAyHA6AMbZlDRVPUcckm7jh3TMbVKP6++h5fFVknsrf7c3E0LIUmkV32pFde79 MgWeHU6hrLqPmYEeWWQSYH1Bn7WhzjA8yKGLr9gcFTBcHBjoFG6/uSsIe0g27H/HfS3+ lg8R35Q52CPwToQUenMOh/vZE5ArcfgdIqRN7S5KjJNcFJCSI+skUAadeCH9uBzKEVsm hv/Q==
MIME-Version: 1.0
X-Received: by 10.194.76.37 with SMTP id h5mr57706779wjw.21.1362686425035; Thu, 07 Mar 2013 12:00:25 -0800 (PST)
Received: by 10.194.5.135 with HTTP; Thu, 7 Mar 2013 12:00:24 -0800 (PST)
In-Reply-To: <5137333C.2000602@alvestrand.no>
References: <39821B4C400EC14DAD4DB25330A9271A01929A@FR711WXCHMBA03.zeu.alcatel-lucent.com> <5137333C.2000602@alvestrand.no>
Date: Thu, 07 Mar 2013 12:00:24 -0800
Message-ID: <CABkgnnVZ6P-S-=b2epFYw86wYfZrxnaDiUdaHbxpqXXvAjKupg@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Content-Type: text/plain; charset="UTF-8"
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Data channel setup: scalability, user experience, labels
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: Thu, 07 Mar 2013 20:00:51 -0000

On 6 March 2013 04:14, Harald Alvestrand <harald@alvestrand.no> wrote:
> Exercise for the reader: Write an application that uses multiple data
> channels, and does not force channel numbers. Try it with and without
> labels.

Yes, it's a problem.  Of course, labels are just one possible solution
to that problem.  Exposing stream ID (i.e., channel.id) achieves the
same end.  So does strict ordering.  So does in-band application
messages.