Re: [rtcweb] Data channel comments and questions

<Markus.Isomaki@nokia.com> Thu, 29 March 2012 20:54 UTC

Return-Path: <Markus.Isomaki@nokia.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 4590721F8731 for <rtcweb@ietfa.amsl.com>; Thu, 29 Mar 2012 13:54:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.599
X-Spam-Level:
X-Spam-Status: No, score=-7.599 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 Vvpf9NrnOPAE for <rtcweb@ietfa.amsl.com>; Thu, 29 Mar 2012 13:54:00 -0700 (PDT)
Received: from mgw-da02.nokia.com (smtp.nokia.com [147.243.128.26]) by ietfa.amsl.com (Postfix) with ESMTP id 1712421F8732 for <rtcweb@ietf.org>; Thu, 29 Mar 2012 13:53:59 -0700 (PDT)
Received: from vaebh104.NOE.Nokia.com (vaebh104.europe.nokia.com [10.160.244.30]) by mgw-da02.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id q2TKrqwV020218; Thu, 29 Mar 2012 23:53:55 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.25]) by vaebh104.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Thu, 29 Mar 2012 23:53:51 +0300
Received: from 008-AM1MPN1-042.mgdnok.nokia.com ([169.254.2.245]) by 008-AM1MMR1-009.mgdnok.nokia.com ([65.54.30.25]) with mapi id 14.01.0355.003; Thu, 29 Mar 2012 22:53:51 +0200
From: Markus.Isomaki@nokia.com
To: ekr@rtfm.com
Thread-Topic: [rtcweb] Data channel comments and questions
Thread-Index: Ac0N59ezjOXJpyb5S8y3N1bZlLMXyP//45QA///dtwCAACgHgP//3iZg
Date: Thu, 29 Mar 2012 20:53:51 +0000
Message-ID: <E44893DD4E290745BB608EB23FDDB7621B136D@008-AM1MPN1-042.mgdnok.nokia.com>
References: <E44893DD4E290745BB608EB23FDDB7621B12D4@008-AM1MPN1-042.mgdnok.nokia.com> <CABcZeBNF2UFdinTDWJy1Tet5yh1=CsiMt3YHZYAXWJLDvPgNSg@mail.gmail.com> <E44893DD4E290745BB608EB23FDDB7621B1300@008-AM1MPN1-042.mgdnok.nokia.com> <CABcZeBOYGT5GEuaes-4FcysZf+tOVHvse4fXWQbP3AZMd8wBMA@mail.gmail.com>
In-Reply-To: <CABcZeBOYGT5GEuaes-4FcysZf+tOVHvse4fXWQbP3AZMd8wBMA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [93.158.46.72]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 29 Mar 2012 20:53:51.0970 (UTC) FILETIME=[0C151C20:01CD0DEE]
X-Nokia-AV: Clean
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Data channel comments and questions
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, 29 Mar 2012 20:54:01 -0000

Hi,

Eric Rescorla <ekr@rtfm.com> wrote:
>
>I had sort of assumed that people would use that HTTP/HTTPS encapsulation
>only to a relay which emitted UDP, so that that encapsulation wouldn't be
>end-to-end in the general case.
>

Makes sense and now that I think of it, it's actually quite clear that it can be done in the same way as with TURN. But SCTP/DTLS would be e2e in any case, and they'd be tunneled over HTTP/HTTPS (and TCP). Well, perhaps that's not so bad for the last resort case.

>-Ekr

Markus