Return-Path: Received: from murder ([unix socket]) by eikenes.alvestrand.no (Cyrus v2.2.8-Mandrake-RPM-2.2.8-4.2.101mdk) with LMTPA; Fri, 06 May 2005 03:29:16 +0200 X-Sieve: CMU Sieve 2.2 Received: from localhost (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id DAB6D61B01 for ; Fri, 6 May 2005 03:29:15 +0200 (CEST) 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 16222-04 for ; Fri, 6 May 2005 03:29:12 +0200 (CEST) X-Greylist: domain auto-whitelisted by SQLgrey-1.4.8 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by eikenes.alvestrand.no (Postfix) with ESMTP id 324CE61AF1 for ; Fri, 6 May 2005 03:29:07 +0200 (CEST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DTraa-0003Ld-6k; Thu, 05 May 2005 21:25:12 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DTraV-0003Kw-1V for ietf@megatron.ietf.org; Thu, 05 May 2005 21:25:09 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA16147 for ; Thu, 5 May 2005 21:25:04 -0400 (EDT) Received: from montage.altserver.com ([63.247.74.122]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DTrot-00007r-Pv for ietf@ietf.org; Thu, 05 May 2005 21:40:00 -0400 Received: from lns-p19-8-idf-82-65-72-134.adsl.proxad.net ([82.65.72.134] helo=jfc.afrac.org) by montage.altserver.com with esmtpa (Exim 4.44) id 1DTraL-00055p-Bu; Thu, 05 May 2005 18:24:57 -0700 Message-Id: <6.2.1.2.2.20050506020255.03a3bcf0@mail.jefsey.com> X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2 Date: Fri, 06 May 2005 02:11:55 +0200 To: Joe Touch From: "JFC (Jefsey) Morfin" In-Reply-To: <427A5648.9020304@isi.edu> References: <482f91815aa54a99c4d772a997e94554@cs.utk.edu> <200505021854.j42IsGe31730@merlot.juniper.net> <20050502160005.334ca9b7.moore@cs.utk.edu> <427A45D7.2040307@isi.edu> <20050505124835.3a05044b.moore@cs.utk.edu> <427A5648.9020304@isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - montage.altserver.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - jefsey.com X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a Cc: ietf@ietf.org Subject: Re: text suggested by ADs X-BeenThere: ietf@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF-Discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: ietf-bounces@ietf.org Errors-To: ietf-bounces@ietf.org X-Virus-Scanned: amavisd-new at alvestrand.no On 19:22 05/05/2005, Joe Touch said: > > The set of people disagreeing with ADs include both technically astute > people > > and egocentric fools. > >Ditto for the ADs themselves. Has this a real importance? The control is by IETF as a whole, _if_ rough consensus is the rule. What is expected from ADs is to make sure that what is proposed meets a rough consensus. This could possibly include commenting their concerns before the Last Call if they feel it necessary. This may include their advise. They should however _never_ consider anything else than consensus. If they have other concerns they should join the WG. Technically astute people and egocentric fools are usually both out of consensus. The only thing expected from IETF as a whole is a permanent consensus never to prevent technically astute fools' solutions from developing outside of the IETF until they may be understood and possibly accepted by its members as part of their consensus. This is why, the IANA registry and Best New Practice question is so important. May be a solution would be to consider an Internet Innovation Task Force to serve as an astute fool's test bed. The rule there would not be consensus but the most astute solution, by participant votes. If you consider Source Forge, it works de facto in this way. jfc _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf