Re: [rtcweb] Data Channel Negotiation and reopening of decisions

Michael Tuexen <Michael.Tuexen@lurchi.franken.de> Fri, 15 February 2013 20:55 UTC

Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 D9CEC21F8609 for <rtcweb@ietfa.amsl.com>; Fri, 15 Feb 2013 12:55:35 -0800 (PST)
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=[AWL=0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hj9IXIKdsdi0 for <rtcweb@ietfa.amsl.com>; Fri, 15 Feb 2013 12:55:35 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by ietfa.amsl.com (Postfix) with ESMTP id 21DF721F844F for <rtcweb@ietf.org>; Fri, 15 Feb 2013 12:55:34 -0800 (PST)
Received: from [192.168.1.101] (p508F9134.dip.t-dialin.net [80.143.145.52]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id DE6941C0C069C; Fri, 15 Feb 2013 21:55:32 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset="us-ascii"
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <CABkgnnWzX2tpbadnB3DjhmB7cm6poCDvmxdAW2Z_stMbovJ3gw@mail.gmail.com>
Date: Fri, 15 Feb 2013 21:55:32 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <A0FDFC7C-2C85-431C-A03E-0E486F9378D1@lurchi.franken.de>
References: <CABkgnnWUpMSBLioSD2+p82vGszX9R0Q4WFfME5j-DuK+B7KVJw@mail.gmail.com> <5113CD16.6090806@jesup.org> <CABkgnnW792o76t9dKhidOMJpa21VcbPQZFU1HYnY_yjTPCWhYw@mail.gmail.com> <51166A3C.4000604@jesup.org> <CABkgnnV2m=m+qtM1YR4CPse=gyekvWThon_Nxbf8YMVaNuvq6Q@mail.gmail.com> <511B6C9A.4090904@jesup.org> <CABkgnnUiCKuv_=mgLFf4sRnOb1bY190N7E_+V8gfTbKEUTBnDw@mail.gmail.com> <511CB20C.7020003@jesup.org> <CABkgnnU0idt+ntpKjTCMUCVFO9=_fSjGRPikD6Nk_Uem3L7E8g@mail.gmail.com> <89FAFB5C-9D03-4B76-A306-01F9E4EC4105@lurchi.franken.de> <CABkgnnXFrqTo2QpLhjWt5CmcQc6Kv4=vAgd3DgyndNtL1ewm7g@mail.gmail.com> <8E2722E7-F82A-48D4-80FB-C76929A2E324@lurchi.franken.de> <CABkgnnWzX2tpbadnB3DjhmB7cm6poCDvmxdAW2Z_stMbovJ3gw@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
X-Mailer: Apple Mail (2.1283)
Cc: Randell Jesup <randell-ietf@jesup.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Data Channel Negotiation and reopening of decisions
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, 15 Feb 2013 20:55:36 -0000

On Feb 15, 2013, at 6:14 PM, Martin Thomson wrote:

> On 14 February 2013 18:59, Michael Tuexen
> <Michael.Tuexen@lurchi.franken.de> wrote:
>> You register at IANA PPID X for binary and PPID Y (Y != X) for text.
>> No signaling required.
> 
> Great!  That removes the need for an in-band protocol entirely. (I
> missed the IANA bit when I read through the description.)
> 
>> I expect each data channel consisting of a pair of streams. Each stream
>> is contained in at most one data channel.
> 
> Correct. The difference between what you have now and what I am
> proposing is simple: you match arbitrary stream X to arbitrary stream
> Y in the opposite direction through signaling or control messages.  I
> am proposing to match stream X to stream X always.  Thus, if you send
> on stream 7, this creates a data channel on the other end that also
> sends on stream 7.
I think I understand what you are proposing. But what happens, if
both sides at about the same time open want to open a data channel.
For both sides outgoing stream X is free, so they use this. So the
endpoints end up with one data channel instead of two.

For me, the endpoints trying to set up two data channels, and finally
having only a single one is a bad thing. You could argue, that this
comes up only in specific situations. That might be true, but for
an application writer this would mean that his code works most
of the time, but sometimes not. This is a bad thing for me.

Best regards
Michael
>