Re: [rtcweb] Why http://www.ietf.org/id/draft-miniero-rtcweb-http-fallback-00.txt ?

Marc Petit-Huguenin <petithug@acm.org> Tue, 07 August 2012 18:12 UTC

Return-Path: <petithug@acm.org>
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 78EEC21F86EB for <rtcweb@ietfa.amsl.com>; Tue, 7 Aug 2012 11:12:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.411
X-Spam-Level:
X-Spam-Status: No, score=-102.411 tagged_above=-999 required=5 tests=[AWL=-0.111, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001, 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 plrLcVKyBEGK for <rtcweb@ietfa.amsl.com>; Tue, 7 Aug 2012 11:12:43 -0700 (PDT)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id D334321F86E5 for <rtcweb@ietf.org>; Tue, 7 Aug 2012 11:12:43 -0700 (PDT)
Received: from [IPv6:2001:470:1f05:616:213:d4ff:fe04:3e08] (shalmaneser.org [IPv6:2001:470:1f05:616:213:d4ff:fe04:3e08]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 478DD20491; Tue, 7 Aug 2012 18:12:41 +0000 (UTC)
Message-ID: <50215A96.20604@acm.org>
Date: Tue, 07 Aug 2012 11:12:38 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.6esrpre) Gecko/20120805 Icedove/10.0.6
MIME-Version: 1.0
To: =?UTF-8?B?ScOxYWtpIEJheiBDYXN0aWxsbw==?= <ibc@aliax.net>
References: <CALiegf=GqR+J3YcAgpRtxid+aDsKeiQttRm8JbjT6RrQWaMG=w@mail.gmail.com>
In-Reply-To: <CALiegf=GqR+J3YcAgpRtxid+aDsKeiQttRm8JbjT6RrQWaMG=w@mail.gmail.com>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Why http://www.ietf.org/id/draft-miniero-rtcweb-http-fallback-00.txt ?
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: Tue, 07 Aug 2012 18:12:44 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 08/07/2012 11:04 AM, Iñaki Baz Castillo wrote:
> Hi, I'm reading 
> http://www.ietf.org/id/draft-miniero-rtcweb-http-fallback-00.txt:
> 
> This draft describes a way to implement an HTTP Fallback for RTP media
> streams, that is, a way to effectively encapsulate RTP packets in HTTP
> messages in order to traverse proxies and firewalls.
> 
> Well, why does WebRTC need it at all? don't we have TURN over TCP/TLS?
> 

Or TURN over Websocket.

- -- 
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: http://blog.marc.petit-huguenin.org
Profile: http://www.linkedin.com/in/petithug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJQIVqJAAoJECnERZXWan7EXkQP/3+6ZhsmUNRy2GCwOHlCutdF
cVTPhFMuNTi4ZTO4EIYQ7rxTiWyGJFCdPI6j24wl1+JmflxmSPQXTJOph8c0rmDr
tPF3WJ2ayn29rpOvUYp+Yp190EUaDt+awgWLo8RTEL9QNNR2hO1G0Jff2ux6AfC+
mbrIS/FJQtuiDlllLH2Xgxq5vUf4oP/sZowoB7bLhp+4MZWD0p/JscYr3+lNbRme
DrbFODfzYYLuPvW0T4OYMzN7hkVKL0M0Hwx7NYN+RBSR184wUrhmFdgmAL61oAzP
SkMNjNs585C/6wUK1un1o2QxppPOUlf/vMCs+XYS45rovOprAmsf6UrrayzMg8Y3
SDfKCtIaCWg5F+LVq+p90KVgP39nQwjY/v6IEQf9egOFFh8pf2KaP8UR1Z7mP8ss
zpLkzJSg7+YNSF7dM+k8PTq1GqdZoWr0YRxAN5xh0zWUdyoOfycYLGWNaD3edjwa
2cTQ9AkAZFfjvVpjAVBdo20c0Gm7mqgngEzrccZyMoVIKoEUC6cPPSfW+etiUYbs
KDWad4n4TbWUDmROohiB7fVlWJdHWxW8oB6rCGkf0ta8RrVFmUDZqoCA8E4AAcjj
E8h0gWnurn2uX9jj6dQB/Q+YApzL+Z11wKvzOzeMnSovCaOg9H0uSs2ezmVuAUA6
uQDV5qElSRqcBvktCWoJ
=hBDl
-----END PGP SIGNATURE-----