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

"Matthew Kaufman (SKYPE)" <matthew.kaufman@skype.net> Sat, 16 February 2013 15:30 UTC

Return-Path: <matthew.kaufman@skype.net>
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 3F8C521F8457 for <rtcweb@ietfa.amsl.com>; Sat, 16 Feb 2013 07:30:27 -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=[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 ITESDdH7gEPa for <rtcweb@ietfa.amsl.com>; Sat, 16 Feb 2013 07:30:26 -0800 (PST)
Received: from na01-bl2-obe.outbound.protection.outlook.com (na01-bl2-obe.ptr.protection.outlook.com [65.55.169.29]) by ietfa.amsl.com (Postfix) with ESMTP id 8F6D021F8A09 for <rtcweb@ietf.org>; Sat, 16 Feb 2013 07:30:26 -0800 (PST)
Received: from BL2FFO11FD026.protection.gbl (10.173.161.202) by BL2FFO11HUB034.protection.gbl (10.173.161.114) with Microsoft SMTP Server (TLS) id 15.0.620.12; Sat, 16 Feb 2013 15:30:21 +0000
Received: from TK5EX14HUBC106.redmond.corp.microsoft.com (131.107.125.37) by BL2FFO11FD026.mail.protection.outlook.com (10.173.161.105) with Microsoft SMTP Server (TLS) id 15.0.620.12 via Frontend Transport; Sat, 16 Feb 2013 15:30:21 +0000
Received: from TK5EX14MBXC273.redmond.corp.microsoft.com ([169.254.1.200]) by TK5EX14HUBC106.redmond.corp.microsoft.com ([157.54.80.61]) with mapi id 14.02.0318.003; Sat, 16 Feb 2013 15:30:18 +0000
From: "Matthew Kaufman (SKYPE)" <matthew.kaufman@skype.net>
To: Randell Jesup <randell-ietf@jesup.org>
Thread-Topic: [rtcweb] Data Channel Negotiation and reopening of decisions
Thread-Index: AQHOCdZYMz/8j5wte0qYTJYB9U+v5ph4WFUAgADD1ACAANcTgIAABrmAgAAlkICAAB2rAIAA7tYAgAA94wCAAAWzAIAAC0EbgACQ2QCAAJWqRw==
Date: Sat, 16 Feb 2013 15:30:18 +0000
Message-ID: <3A70CC40-2BB4-40FD-A1B0-3257EC973757@skype.net>
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> <A0FDFC7C-2C85-431C-A03E-0E486F9378D1@lurchi.franken.de>, <CABkgnnWdjV7F9jkbap91q-pLygzWJsTvAOh-m=-9q4VrU9DGUg@mail.gmail.com> <DA07C056-3E80-4E30-B078-5547A174549D@skype.net>, <511F287E.8030500@jesup.org>
In-Reply-To: <511F287E.8030500@jesup.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(189002)(199002)(51704002)(24454001)(479174001)(377454001)(5343655001)(77982001)(74502001)(4396001)(23726001)(74662001)(56816002)(59766001)(63696002)(47776003)(47446002)(56776001)(20776003)(54316002)(44976002)(31966008)(33656001)(54356001)(79102001)(80022001)(51856001)(46406002)(50466001)(16406001)(47976001)(49866001)(50986001)(76482001)(46102001)(65816001)(47736001)(53806001); DIR:OUT; SFP:; SCL:1; SRVR:BL2FFO11HUB034; H:TK5EX14HUBC106.redmond.corp.microsoft.com; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en;
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 0759F7A50A
Cc: "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: Sat, 16 Feb 2013 15:30:27 -0000

You're right of course... I just can't keep straight which of the things are poor choices and which are reasonable choices that have been bastardized to the point of being poor choices.

If we're going to use SCTP, and it has perfectly good unidirectional channels, why can't we just expose those to users of the W3C WEBRTC API?

Apparently this "we built a simple protocol to allow us to set up bidirectional pairs of SCTP streams to create channels" isn't as simple as it first looked, so we should be revisiting the original assumption, not creating a complicated protocol just because we can.

Matthew Kaufman

Sent from my iPad

On Feb 15, 2013, at 10:40 PM, "Randell Jesup" <randell-ietf@jesup.org> wrote:

> On 2/15/2013 4:56 PM, Matthew Kaufman (SKYPE) wrote:
>> None if this would be a problem if we weren't making the mistake of using SCTP, which itself made the mistake of doing full-duplex channels instead of unidirectional channels with optional one-to-one or even many-to-one associations (as RTMFP has, as an example)
> 
> SCTP only has unidirectional streams.
> 
> If you're referring to the DataChannel protocol, there was a strong wish on the mailing list (and W3) for websockets-like bidirectional channels, so we built a simple protocol to allow us to set up bidirectional pairs of SCTP streams to create channels.
> 
> -- 
> Randell Jesup
> randell-ietf@jesup.org
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>