Re: [hybi] It's time to ship

Greg Wilkins <gregw@webtide.com> Mon, 10 January 2011 09:13 UTC

Return-Path: <gregw@intalio.com>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3CBAA28C11A for <hybi@core3.amsl.com>; Mon, 10 Jan 2011 01:13:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.93
X-Spam-Level:
X-Spam-Status: No, score=-2.93 tagged_above=-999 required=5 tests=[AWL=0.047, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j-VD7NddSYUg for <hybi@core3.amsl.com>; Mon, 10 Jan 2011 01:12:57 -0800 (PST)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by core3.amsl.com (Postfix) with ESMTP id 2BEBA28C0ED for <hybi@ietf.org>; Mon, 10 Jan 2011 01:12:56 -0800 (PST)
Received: by qyj19 with SMTP id 19so20682975qyj.10 for <hybi@ietf.org>; Mon, 10 Jan 2011 01:15:06 -0800 (PST)
MIME-Version: 1.0
Received: by 10.224.53.213 with SMTP id n21mr26710032qag.399.1294650905892; Mon, 10 Jan 2011 01:15:05 -0800 (PST)
Sender: gregw@intalio.com
Received: by 10.220.160.12 with HTTP; Mon, 10 Jan 2011 01:15:05 -0800 (PST)
In-Reply-To: <AANLkTik0dLB_GKeAr8uKnF8QvOG53gETmTdgVWRaAT_s@mail.gmail.com>
References: <AANLkTim2VGfH2FiJ4iH85wYiuXNKQ1Arh1C1Kg4M58Fs@mail.gmail.com> <AANLkTikTQ98ORhYJEK8LJCcjs9e4r_eKn1xr858mCnBn@mail.gmail.com> <AANLkTik0dLB_GKeAr8uKnF8QvOG53gETmTdgVWRaAT_s@mail.gmail.com>
Date: Mon, 10 Jan 2011 10:15:05 +0100
X-Google-Sender-Auth: y3kVSJHO1w93OK3eLDToTAR1T3s
Message-ID: <AANLkTi=hceS22=_jZk2G0Se0mtShp8bfPOE03-nNXo_4@mail.gmail.com>
From: Greg Wilkins <gregw@webtide.com>
To: Hybi <hybi@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [hybi] It's time to ship
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jan 2011 09:13:28 -0000

On 10 January 2011 01:46, Adam Barth <ietf@adambarth.com> wrote:
> Thanks for your feedback.  I'd encourage you not to implement this
> protocol then.

Note also that this discussion is not about implementation.

If browsers implement some protocol, then the servers and
intermediaries will do their best to support it as we have always
done, no matter how ill conceived the ideas or how little the server
side concerns have been considered.

But implementation is entirely different to standardisation, which is
the point of the discussions here.   The get standardisation at the
IETF, you need consensus from all the main constituencies and from the
wider IETF community.  If the browser vendors chose to ignore the
concerns of the intermediaries and server side, that does not make
those concerns go away - they remain and almost certainly means will
be found to address them that will in all probability be proprietary
and/or disparate, thus making the chances of WS becoming an IETF
standard even less likely.