Re: [hybi] Ticket#1 Http Compliance

Greg Wilkins <gregw@webtide.com> Thu, 13 May 2010 13:11 UTC

Return-Path: <gregw@webtide.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 8F3663A6A02 for <hybi@core3.amsl.com>; Thu, 13 May 2010 06:11:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.69
X-Spam-Level:
X-Spam-Status: No, score=-0.69 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_20=-0.74]
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 jhZQdQuXLkbq for <hybi@core3.amsl.com>; Thu, 13 May 2010 06:11:36 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 355AC3A6AFA for <hybi@ietf.org>; Thu, 13 May 2010 06:11:36 -0700 (PDT)
Received: by wwb28 with SMTP id 28so946688wwb.31 for <hybi@ietf.org>; Thu, 13 May 2010 06:11:22 -0700 (PDT)
Received: by 10.227.157.205 with SMTP id c13mr8422876wbx.136.1273756282229; Thu, 13 May 2010 06:11:22 -0700 (PDT)
Received: from [192.168.0.100] (host116-234-static.43-88-b.business.telecomitalia.it [88.43.234.116]) by mx.google.com with ESMTPS id z33sm8834175wbd.19.2010.05.13.06.11.20 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 13 May 2010 06:11:21 -0700 (PDT)
Message-ID: <4BEBFA74.6040204@webtide.com>
Date: Thu, 13 May 2010 15:11:16 +0200
From: Greg Wilkins <gregw@webtide.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100411)
MIME-Version: 1.0
To: "hybi@ietf.org" <hybi@ietf.org>
References: <4BEAB021.5030600@webtide.com> <op.vcmr0hge64w2qv@annevk-t60> <4BEBB81F.4010506@webtide.com> <op.vcm3kopz64w2qv@annevk-t60> <4BEBF190.1050301@webtide.com> <op.vcm93lv964w2qv@annevk-t60>
In-Reply-To: <op.vcm93lv964w2qv@annevk-t60>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Subject: Re: [hybi] Ticket#1 Http Compliance
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: Thu, 13 May 2010 13:11:38 -0000

Anne van Kesteren wrote:
> On Thu, 13 May 2010 14:33:20 +0200, Greg Wilkins <gregw@webtide.com> wrote:
>> Is it a requirement to have a requirements document?
> 
> I don't know, but in my experience going back to requirements when there
> already is a draft specification is counter-productive. We'll get the
> same debates, only now with more meta. I, for one, am not looking
> forward to it.

Anne,

Personally, I'm not advocating that the WHATWG delay the their
work on the protocol or it's deployment while waiting for the IETF
processes.   There is no requirement that a deployed protocol
is an IETF standard.

I would prefer to see a clear distinction between the spec
as it is being currently deployed and the spec as it is
currently being standardized.

Given the time frames of the IETF processes, my expectation is
that a consensus standard should aim to be the 1.1 version of
the protocol (or maybe an entirely different 2.0 protocol?).

But conversely, just because the browser vendors are further along
their process, it does not mean that the IETF should make an
exception to it's processes when formulating a standard.


regards