[rtcweb] Appropriateness of bypass mechanisms (Re: HTTP Fallback draft)

Harald Alvestrand <harald@alvestrand.no> Wed, 08 August 2012 15:28 UTC

Return-Path: <harald@alvestrand.no>
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 CED3821F86BB for <rtcweb@ietfa.amsl.com>; Wed, 8 Aug 2012 08:28:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.333
X-Spam-Level:
X-Spam-Status: No, score=-110.333 tagged_above=-999 required=5 tests=[AWL=0.266, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 DBvSEz77obC6 for <rtcweb@ietfa.amsl.com>; Wed, 8 Aug 2012 08:28:54 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id D426F21F86B9 for <rtcweb@ietf.org>; Wed, 8 Aug 2012 08:28:53 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id A750039E106 for <rtcweb@ietf.org>; Wed, 8 Aug 2012 17:28:51 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cf9q6QM1DCY6 for <rtcweb@ietf.org>; Wed, 8 Aug 2012 17:28:50 +0200 (CEST)
Received: from hta-dell.lul.corp.google.com (unknown [IPv6:2620:0:1043:1:be30:5bff:fede:bcdc]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id C665F39E058 for <rtcweb@ietf.org>; Wed, 8 Aug 2012 17:28:50 +0200 (CEST)
Message-ID: <502285B2.8080007@alvestrand.no>
Date: Wed, 08 Aug 2012 17:28:50 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <20120807180156.286e74d2@rainpc> <D5BDA7BE-FE55-47FA-99FD-1645084370B0@gmx.net> <20120807191226.5b8e7f32@rainpc> <BLU401-EAS2566333A7F4DEA0D3BFDBE593CD0@phx.gbl> <913383AAA69FF945B8F946018B75898A1477EDB9@xmb-rcd-x10.cisco.com> <CAD6AjGSU8mzbcdbOkgGtAms1tdHhjiuQn_NFXELwO2kjegJkCQ@mail.gmail.com>
In-Reply-To: <CAD6AjGSU8mzbcdbOkgGtAms1tdHhjiuQn_NFXELwO2kjegJkCQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [rtcweb] Appropriateness of bypass mechanisms (Re: HTTP Fallback draft)
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: Wed, 08 Aug 2012 15:28:56 -0000

Forking thread....

On 08/08/2012 05:05 PM, Cameron Byrne wrote:
>
>
> Is this thread  really about the ietf engineering a way to by-pass 
> network policy set by network operators?
>
It's about getting stuff done in the presence of rules that hinder the 
"simple way".
Those rules may be set that way deliberately, by ignorance, because of 
implementation limitations, or in error; there's no way to know.

> I do not believe that is acceptable.
>
We've already done TURN, including TURN over TLS.

Old quote: "This is not about starting down the slippery slope; this is 
about how far we slide into the muck at the bottom".