Re: [rtcweb] Isolating data channels (Re: Asking TLS for help with media isolation)

"Matthew Kaufman (SKYPE)" <matthew.kaufman@skype.net> Mon, 07 April 2014 19:40 UTC

Return-Path: <matthew.kaufman@skype.net>
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 74D621A082B for <rtcweb@ietfa.amsl.com>; Mon, 7 Apr 2014 12:40:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_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 caPs4dQJGUv9 for <rtcweb@ietfa.amsl.com>; Mon, 7 Apr 2014 12:40:14 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1blp0182.outbound.protection.outlook.com [207.46.163.182]) by ietfa.amsl.com (Postfix) with ESMTP id 7B07F1A07F4 for <rtcweb@ietf.org>; Mon, 7 Apr 2014 12:40:13 -0700 (PDT)
Received: from BY2PR03CA046.namprd03.prod.outlook.com (10.141.249.19) by BY2PR03MB025.namprd03.prod.outlook.com (10.255.240.39) with Microsoft SMTP Server (TLS) id 15.0.913.9; Mon, 7 Apr 2014 19:40:03 +0000
Received: from BY2FFO11FD057.protection.gbl (2a01:111:f400:7c0c::193) by BY2PR03CA046.outlook.office365.com (2a01:111:e400:2c5d::19) with Microsoft SMTP Server (TLS) id 15.0.913.9 via Frontend Transport; Mon, 7 Apr 2014 19:40:04 +0000
Received: from mail.microsoft.com (131.107.125.37) by BY2FFO11FD057.mail.protection.outlook.com (10.1.15.185) with Microsoft SMTP Server (TLS) id 15.0.918.6 via Frontend Transport; Mon, 7 Apr 2014 19:40:01 +0000
Received: from TK5EX14MBXC298.redmond.corp.microsoft.com ([169.254.1.124]) by TK5EX14MLTC103.redmond.corp.microsoft.com ([157.54.79.174]) with mapi id 14.03.0174.002; Mon, 7 Apr 2014 19:39:23 +0000
From: "Matthew Kaufman (SKYPE)" <matthew.kaufman@skype.net>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Thread-Topic: [rtcweb] Isolating data channels (Re: Asking TLS for help with media isolation)
Thread-Index: AQHPUjfRb53lyS9CtEOLJeBSW/E7VJsGYYMAgAAFe4CAAADocIAAINQAgAABNqCAAAHBAIAAAI7g
Date: Mon, 7 Apr 2014 19:39:22 +0000
Message-ID: <AE1A6B5FD507DC4FB3C5166F3A05A484504B5133@TK5EX14MBXC298.redmond.corp.microsoft.com>
References: <CABkgnnWWuU63Vd=gw+wrh2ADgVYtQzhoRzRE1sv5azJE=MhWDg@mail.gmail.com> <533F191D.8050109@alum.mit.edu> <CABkgnnVht5EmJ7a2LDh50ivjUdoTpJ8GannQKReBSJbVGQGmgA@mail.gmail.com> <53425BAF.4070105@alvestrand.no> <CABkgnnXKe65-30qkuhkCLmaUYVfe8vrWv9BCJzOvC7KaRwUH=g@mail.gmail.com> <5342DE6F.6040306@alvestrand.no> <AE1A6B5FD507DC4FB3C5166F3A05A484504B4D9C@TK5EX14MBXC298.redmond.corp.microsoft.com> <5342FABC.4080200@alum.mit.edu> <AE1A6B5FD507DC4FB3C5166F3A05A484504B505E@TK5EX14MBXC298.redmond.corp.microsoft.com> <CAHBDyN4N4T+xj_fMUQeYAL0Z=+iQ2z0uMbuDDg+ASV3mgceq3A@mail.gmail.com>
In-Reply-To: <CAHBDyN4N4T+xj_fMUQeYAL0Z=+iQ2z0uMbuDDg+ASV3mgceq3A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [157.54.51.37]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10009001)(6009001)(438001)(199002)(377454003)(189002)(51704005)(50986001)(49866001)(20776003)(98676001)(95666003)(54316002)(99396002)(94316002)(84676001)(23756003)(33656001)(81542001)(79102001)(92726001)(93136001)(97186001)(6806004)(86362001)(90146001)(85306002)(63696002)(76796001)(87936001)(47776003)(2009001)(97336001)(44976005)(94946001)(97736001)(77096001)(54356001)(87266001)(77982001)(55846006)(83322001)(81686001)(19580395003)(80976001)(65816001)(56816005)(19580405001)(31966008)(74662001)(74502001)(74366001)(74706001)(81816001)(92566001)(47446002)(80022001)(66066001)(50466002)(74876001)(53806001)(15975445006)(81342001)(47976001)(47736001)(69226001)(93516002)(4396001)(76786001)(56776001)(46102001)(85852003)(2656002)(76482001)(59766001)(95416001)(83072002); DIR:OUT; SFP:1101; SCL:1; SRVR:BY2PR03MB025; H:mail.microsoft.com; FPR:4C96F2F5.A5FAD7E5.3DD03D53.4CF69869.202A3; MLV:sfv; PTR:InfoDomainNonexistent; A:1; MX:1; LANG:en;
X-O365ENT-EOP-Header: Message processed by - O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 0174BD4BDA
Received-SPF: Pass (: domain of skype.net designates 131.107.125.37 as permitted sender) receiver=; client-ip=131.107.125.37; helo=mail.microsoft.com;
X-OriginatorOrg: skype.net
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/cu6rlXVytkJOpRFfplJRpK-OmSQ
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Isolating data channels (Re: Asking TLS for help with media isolation)
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: Mon, 07 Apr 2014 19:40:18 -0000

From: rtcweb [mailto:rtcweb-bounces@ietf.org] On Behalf Of Paul Kyzivat
> Sent: Monday, April 7, 2014 12:22 PM
> To: rtcweb@ietf.org
> Subject: Re: [rtcweb] Isolating data channels (Re: Asking TLS for help with
> media isolation)
> > RFC 7016 documents such an approach.
>
> I see that the title starts with "Adobe's". Sigh.
Yes, but there's little stopping many of these ideas from becoming the basis for an IETF-developed transport protocol that actually meets the needs we have here.

[MB] Except, maybe, IPR: 
 https://datatracker.ietf.org/ipr/search/?option=document_search&id=draft-thornburgh-adobe-rtmfp
[/MB]

Conveniently, RTMFP was preceded by an open-source project which had no patents filed. so to the extent the "ideas" are present there (and many of them are), that's easily worked around, if one needed a starting place.

But my point wasn't to start discussing the merits of the specific approach described in that particular RFC... rather to note that the cobbled-together collection of choices that have been made, specifically gluing SCTP on to the side of RTCWEB as a way of transporting data, is highly suboptimal and that other solutions do exist.

In fact, simply allowing the data we need to be sent unsolicited as another SRTP stream would be an improvement over doing 2 round trips of SCTP setup for the problem space we are discussing in this thread.

Matthew Kaufman