Re: [rtcweb] Data channel comments and questions

Eric Rescorla <ekr@rtfm.com> Thu, 29 March 2012 20:48 UTC

Return-Path: <ekr@rtfm.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 43A0F21F8643 for <rtcweb@ietfa.amsl.com>; Thu, 29 Mar 2012 13:48:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level:
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 9v25FldkxSt4 for <rtcweb@ietfa.amsl.com>; Thu, 29 Mar 2012 13:48:58 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 867C421F863B for <rtcweb@ietf.org>; Thu, 29 Mar 2012 13:48:58 -0700 (PDT)
Received: by vcbfk13 with SMTP id fk13so2106551vcb.31 for <rtcweb@ietf.org>; Thu, 29 Mar 2012 13:48:58 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding :x-gm-message-state; bh=XjeYEIDVPMKaM4pbFle4PiXqhifJRKqEGIyhNFnkFMo=; b=miCl6a0XwcvOYHsr6HFSHHxaueK33RjtSFuuhxfFxaayXwMoNZUjti0IWNUO8N2W1+ 0glcV33nmW0+ccOFkHk75iM2tiTkmb1vR2W6F7HmEHC2EqhRyjQSBj7W4JIdqz0PjmVd Eb1XN8qr+al0Z0XGnhZaDMInyFGlOPQ18rQyuOppUTdIvBtNuKPaewhwFwTbIL+5BKCI A/lHhxWsiYx7/8xZOyfgjU58MbErKYbZQb/AzloqpoJLKSs8UwMmDMJwC9qADZaHmF4R Uce5BZNC6mX/z2ZCg6+wm2b1x4ToTHGH/xnonmWqWEDZkIwF5+1cMsT96kFlm2vsHIYU Fk/w==
Received: by 10.52.26.103 with SMTP id k7mr14208586vdg.26.1333054138072; Thu, 29 Mar 2012 13:48:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.22.195 with HTTP; Thu, 29 Mar 2012 13:48:17 -0700 (PDT)
X-Originating-IP: [81.253.23.112]
In-Reply-To: <E44893DD4E290745BB608EB23FDDB7621B1300@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>
From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 29 Mar 2012 22:48:17 +0200
Message-ID: <CABcZeBOYGT5GEuaes-4FcysZf+tOVHvse4fXWQbP3AZMd8wBMA@mail.gmail.com>
To: Markus.Isomaki@nokia.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQlPQhzTm7e6BWT6nCxRUwa+5IWCsJotRg5ZHS2+0f9bdg7Y9d4QE1kihV8mMpKF6rIvqZ4+
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:48:59 -0000

On Thu, Mar 29, 2012 at 10:36 PM,  <Markus.Isomaki@nokia.com> wrote:
> Hi,
>
> Eric Rescorla [mailto:ekr@rtfm.com] wrote:
>>>
>>> 3. HTTP tunneling: In practice we are going to need HTTP tunneling last-
>>resort option for the data channel as well. If doing so, what will the protocol
>>stack look like? Is it SCTP/DTLS/UDP/HTTP/TLS/TCP? Or can we collapse some
>>of these layers. I think we'd better.
>>
>>I don't think I understand point 3. Why would we need HTTP tunneling?
>>If we can bring
>>up a bidirectional UDP channel, then why would we need to run HTTP over it?
>>
>
> Ah, sorry for not being clear. I mean a situation where we can't setup the UDP channel, if one endpoint is for instance in a corporate network from where only HTTP or HTTPS is allowed. So presumably we'd have to support some kind of HTTP or TLS encapsulation/tunneling for the data channel as well, from the endpoint to some kind of relay. But how would the end-to-end data channel look like then? I.e. what would be sent over the tunnel?

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.

-Ekr