Re: [hybi] Issue tracker

Scott Ferguson <ferg@caucho.com> Sun, 23 May 2010 15:43 UTC

Return-Path: <ferg@caucho.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 08F123A6C69 for <hybi@core3.amsl.com>; Sun, 23 May 2010 08:43:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.311
X-Spam-Level:
X-Spam-Status: No, score=0.311 tagged_above=-999 required=5 tests=[AWL=0.309, BAYES_50=0.001, UNPARSEABLE_RELAY=0.001]
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 9tCCFzKxRfsD for <hybi@core3.amsl.com>; Sun, 23 May 2010 08:43:46 -0700 (PDT)
Received: from smtp111.biz.mail.mud.yahoo.com (smtp111.biz.mail.mud.yahoo.com [209.191.68.76]) by core3.amsl.com (Postfix) with SMTP id 25E9D3A6A7D for <hybi@ietf.org>; Sun, 23 May 2010 08:43:46 -0700 (PDT)
Received: (qmail 81824 invoked from network); 23 May 2010 15:43:36 -0000
Received: from scott-fergusons-macbook-pro-3.local (ferg@70.231.144.150 with plain) by smtp111.biz.mail.mud.yahoo.com with SMTP; 23 May 2010 08:43:36 -0700 PDT
X-Yahoo-SMTP: L1_TBRiswBB5.MuzAo8Yf89wczFo0A2C
X-YMail-OSG: K14ykHsVM1nDuDZedh8nbAGWwlqs3wZsg23hMkkkVjjlXBr4_y1OrVsoNkI7aaYSw.37NEZe7ag6IbZC3x0rcVtPeXt5aLY_JIqFlF2iuI3Voceqi0YyNZe3UpbDPMxkdgwMenFOlW9jm9lvFWjt5feQE2g5PqgFJ7U1cnV5SJSyVKfipJrjl6y0dbYozvvKtV5c1YR_na0L0S0OUt.YTwoDcTiVhClfQ4IgKDUCmqr4NDG8lgiG_sDRN2he_CNHfzfF1Gd5O8Bdd3efiZqPRa4OnZvV1P4j4ne8VCZjyh7GLE9NCT8Ou0A-
X-Yahoo-Newman-Property: ymail-3
Message-ID: <4BF94D27.9080904@caucho.com>
Date: Sun, 23 May 2010 08:43:35 -0700
From: Scott Ferguson <ferg@caucho.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Ian Hickson <ian@hixie.ch>
References: <4BEA99E9.5050308@ericsson.com> <20100512165946.GC19314@shareable.org> <4BEAF8F6.80709@ericsson.com> <Pine.LNX.4.64.1005130134240.8532@ps20323.dreamhostps.com> <4BEBC177.3030201@ericsson.com> <Pine.LNX.4.64.1005132116210.12269@ps20323.dreamhostps.com> <4BF27670.1000607@ericsson.com> <Pine.LNX.4.64.1005182055280.22838@ps20323.dreamhostps.com> <4BF3A31B.5090208@ericsson.com> <Pine.LNX.4.64.1005230558070.22838@ps20323.dreamhostps.com>
In-Reply-To: <Pine.LNX.4.64.1005230558070.22838@ps20323.dreamhostps.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] Issue tracker
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: Sun, 23 May 2010 15:43:47 -0000

Ian Hickson wrote:
> On Wed, 19 May 2010, Salvatore Loreto wrote:
>   
> It's actually very easy to determine their opinion; we can just ask them, 
> or follow their discussions elsewhere. For example, I regularly partake in 
> discussions about HTML5 on Reddit, on IRC, and in other forums, even 
> though many people there aren't in the HTML working group. Indeed, using 
> Google alerts and Backtype alerts one is able to get a very good sense of 
> where people outside the working group stand.
>
> However, while I obviously will continue to look at those sources of 
> input, I understand that we'd want to ignore this feedback when 
> determining "consensus", if we're going to use a consensus-based approach.
>
>   
We have representatives from at least 3 HTTP browser implementors here, 
at least 2 HTTP server implementors, and others with extensive 
networking experience, and the IETF is the proper venue for internet 
protocol specifications.

It's clear that you're planning to ignore the IETF working group in 
favor of selected voices in the HTML community who agree with you, but 
lets at least be honest about that intent, instead of pretending 
confusion over the concept of consensus. It's always possible to shop 
around to find people who agree with you, especially if you ask people 
with with the wrong expertise.
>   
>>> Should consensus be considered more important than technical 
>>> correctness and interoperability with implementations, or should 
>>> making the spec technically sound and making the spec match reality be 
>>> considered more important than consensus?
>>>       
>> it is quite unlikely that the consensus does not match a solution that 
>> is technically correct and interoperable with implementations.
>>     

Correct.  However, since you've also selected an editor who's opposed to 
the IETF entirely (opposing to conforming  the HTTP spec when using the 
HTTP port), there's only a slim chance that the specification will 
reflect the consensus.
>
> I wish I could share your optimism.
>   

Correct. It's clear the spec will not reflect the consensus.

-- Scott