Re: [hybi] Issue tracker

SM <sm@resistor.net> Sun, 23 May 2010 17:47 UTC

Return-Path: <sm@resistor.net>
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 B897F3A6C68 for <hybi@core3.amsl.com>; Sun, 23 May 2010 10:47:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.914
X-Spam-Level:
X-Spam-Status: No, score=-0.914 tagged_above=-999 required=5 tests=[AWL=-0.915, BAYES_50=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 vwNs6tCmXRyT for <hybi@core3.amsl.com>; Sun, 23 May 2010 10:47:14 -0700 (PDT)
Received: from ns1.qubic.net (ns1.qubic.net [208.69.177.116]) by core3.amsl.com (Postfix) with ESMTP id 476533A67FB for <hybi@ietf.org>; Sun, 23 May 2010 10:47:13 -0700 (PDT)
Received: from SUBMAN.resistor.net ([10.0.0.1]) (authenticated bits=0) by ns1.qubic.net (8.14.5.Alpha0/8.14.5.Alpha0) with ESMTP id o4NHkt1s001324 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <hybi@ietf.org>; Sun, 23 May 2010 10:47:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1274636823; x=1274723223; bh=xIn1KbVcGmVzlK40we2JunZAvmROy4ZOTGki7k63AIs=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=wvibWazprqdAaoTJlyiPE7mHNFdDJZiwOoYgcNxDait9eJ5m1wAXZDtEFdYr3siFI wzbrSGKJMdhq5Y0ObnMy8fIzgPQoDeHIgdicja6gjCbglN2BpsD3J468al50IHKBkM y5vRIW22xOLQnY6vwqV6IhPqVIpWym1QavIweaCg=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1274636823; x=1274723223; bh=xIn1KbVcGmVzlK40we2JunZAvmROy4ZOTGki7k63AIs=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=L4HuQs/4vYvVyz5uYv1odM6E8nJNAmURpgY2N00RonJjVnVMdWjTvIXT2+gtuduzj XlZfCZf5rwRSDw05IdGcxC+G/czRI1A/x8WDcdZ94s+T4Mu4aJKRI7x2aHQ0G2q8yO 3xoFQHGlK1z9zvmq98rHDg2wV96h5O7INH03q5qI=
DomainKey-Signature: a=rsa-sha1; s=mail; d=resistor.net; c=simple; q=dns; b=LBXe1WXXJSWWfTy+W5FKjVPzHSJRyE7By1zRBGEJEf7S8Fvykcnhj8XQpfhK6TE1v whedSH44sxnmJOw2shBxKsvebQlpeMm4leBrw692yNGUXvWkTmDoN4R7gMEjeUKDe5Y 5cGltS7blS2JUgQRjq1Zqu/OQGrtv3HM6+zulkM=
Message-Id: <6.2.5.6.2.20100523100245.060168a0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 23 May 2010 10:42:32 -0700
To: hybi@ietf.org
From: SM <sm@resistor.net>
In-Reply-To: <Pine.LNX.4.64.1005230558070.22838@ps20323.dreamhostps.com>
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>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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 17:47:15 -0000

At 23:29 22-05-10, Ian Hickson wrote:
>Do you mean all the subscribers to the mailing list, or all those posting?
>If the latter, over what time period?

The IETF uses "an open process in which any technical opinion will be 
heard and any participant's concerns addressed".  Any subscriber to 
this mailing list can post comments.    The period is announced at 
the time of the consensus call.

>How large a majority is "very large"?

There is no such thing as majority as that is akin to voting.  Based 
on your questions, it seems that you have some difficult grasping the 
concept of consensus.

>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.

People outside an IETF mailing list are not IETF participants.  There 
is the question of BCP 78 and BCP 79 which might affect external 
"specifications".  Some participants in this working group could invoke that.

>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.

Nobody suggested ignoring any feedback which conforms to BCP 78 and BCP 79.

At 08:43 23-05-10, Scott Ferguson wrote:
>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 doubt that the specification would be published as a RFC if it does 
not reflect the consensus of the IETF.

Regards,
-sm