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

Iñaki Baz Castillo <ibc@aliax.net> Tue, 07 August 2012 18:04 UTC

Return-Path: <ibc@aliax.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 6F9E011E809A for <rtcweb@ietfa.amsl.com>; Tue, 7 Aug 2012 11:04:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.656
X-Spam-Level:
X-Spam-Status: No, score=-2.656 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
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 jWyFXtDTpCQz for <rtcweb@ietfa.amsl.com>; Tue, 7 Aug 2012 11:04:21 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5F16B11E8099 for <rtcweb@ietf.org>; Tue, 7 Aug 2012 11:04:21 -0700 (PDT)
Received: by lbbgg6 with SMTP id gg6so11041lbb.31 for <rtcweb@ietf.org>; Tue, 07 Aug 2012 11:04:20 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type :content-transfer-encoding:x-gm-message-state; bh=8a1sFeq/ZkkWrJKBXwycU/cE6EiAlZ1uWVSgKUrNkmA=; b=PfQeDWTmcmo5mttxzsQZOLYE6YQaCfIG+QVEM9iHHrbnAWzyuJGkrBDBx19nDJkSVC DJw2HmleUvKsA7ydU1MJXcI1/nE+8O/sfY9UAS0/q2htHkEhDCLuI8ZspOVgpIIsFSGh kiasFvmNxiopDWtiel4rCSwa/pSr4DAyIT5+bVhDZ2pvLXd1oBYRq+Ymd3kww5Cp46FS g9aIyaHYk7Vl3uE3FK3IwzXdtlVx6FqVYK/iRNStMX5t5AWoehLBc3bSuCaLA1vinsOY 7L16FDM7n7/JJDnPiAu6tpg+WqxkwNrDIOp+q5fTdfh1/raejIQN4MFatJ8pQBeAKOCt /G5Q==
Received: by 10.112.23.200 with SMTP id o8mr6857578lbf.9.1344362660305; Tue, 07 Aug 2012 11:04:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.114.23.2 with HTTP; Tue, 7 Aug 2012 11:04:00 -0700 (PDT)
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Tue, 07 Aug 2012 20:04:00 +0200
Message-ID: <CALiegf=GqR+J3YcAgpRtxid+aDsKeiQttRm8JbjT6RrQWaMG=w@mail.gmail.com>
To: rtcweb@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQmV4ulSoioSFwtEad6ZYv6lSCgr26MLrxQPWceHi6O9M4UTOALAwQUqXt+9DKMBoXFxNU1/
Subject: [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:04:22 -0000

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?

-- 
Iñaki Baz Castillo
<ibc@aliax.net>