Re: [rtcweb] Comments on draft-miniero-rtcweb-http-fallback

Lorenzo Miniero <lorenzo@meetecho.com> Thu, 18 October 2012 17:30 UTC

Return-Path: <lorenzo@meetecho.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 2B6BF21F8766 for <rtcweb@ietfa.amsl.com>; Thu, 18 Oct 2012 10:30:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.189
X-Spam-Level: *
X-Spam-Status: No, score=1.189 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_ILLEGAL_IP=1.908]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jHtcJqhgo0fL for <rtcweb@ietfa.amsl.com>; Thu, 18 Oct 2012 10:30:31 -0700 (PDT)
Received: from smtplq03.aruba.it (smtplqs-out31.aruba.it [62.149.158.71]) by ietfa.amsl.com (Postfix) with SMTP id 2A52021F8757 for <rtcweb@ietf.org>; Thu, 18 Oct 2012 10:30:30 -0700 (PDT)
Received: (qmail 22574 invoked by uid 89); 18 Oct 2012 17:30:28 -0000
Received: from unknown (HELO smtp1.aruba.it) (62.149.158.221) by smtplq03.aruba.it with SMTP; 18 Oct 2012 17:30:28 -0000
Received: (qmail 29569 invoked by uid 89); 18 Oct 2012 17:30:28 -0000
Received: from unknown (HELO localhost) (lorenzo@meetecho.com@2.196.0.110) by smtp1.ad.aruba.it with SMTP; 18 Oct 2012 17:30:26 -0000
Date: Thu, 18 Oct 2012 19:30:59 +0200
Message-ID: <8i6fnmcv0sk8fx1ay2w18wcw.1350581459437@email.android.com>
From: Lorenzo Miniero <lorenzo@meetecho.com>
To: Martin Thomson <martin.thomson@gmail.com>, rtcweb@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
X-Spam-Rating: smtp1.ad.aruba.it 1.6.2 0/1000/N
X-Spam-Rating: smtplq03.aruba.it 1.6.2 0/1000/N
Subject: Re: [rtcweb] Comments on draft-miniero-rtcweb-http-fallback
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, 18 Oct 2012 17:30:32 -0000

Martin,

it looks like you missed this:

http://www.ietf.org/mail-archive/web/rtcweb/current/msg05035.html 

The draft was not at all meant as a proposed solution (as "grossly inefficient" as it is), but just as a way to poll for interest about work in that direction in the group, and discuss whether or not something like that would be needed in first place.

Feel free to take it from there and revive the discussion, if needed.

Lorenzo

Martin Thomson <martin.thomson@gmail.com> ha scritto:

>This seems grossly inefficient.  Even if you assume that we have to
>tolerate the head-of-line blocking properties of a stream transport,
>the overhead of HTTP headers is immense.
>
>What is wrong with WebSockets for this use case?
>
>Why is there so much discussion on topology?  It seems that the
>topology used for TURN is perfectly good and would require the least
>disruption.
>_______________________________________________
>rtcweb mailing list
>rtcweb@ietf.org
>https://www.ietf.org/mailman/listinfo/rtcweb