Re: IAOC Request for community feedback
Doug Barton <dougb@dougbarton.us> Tue, 23 October 2012 19:04 UTC
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C062321F865E for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 12:04:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level:
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[AWL=0.464, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ke6kESH6PS1r for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 12:04:31 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 0874921F864A for <ietf@ietf.org>; Tue, 23 Oct 2012 12:04:30 -0700 (PDT)
Received: (qmail 10746 invoked by uid 399); 23 Oct 2012 19:04:13 -0000
Received: from unknown (HELO ?192.168.0.102?) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 23 Oct 2012 19:04:13 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <5086EA38.6020806@dougbarton.us>
Date: Tue, 23 Oct 2012 12:04:24 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: IAOC Request for community feedback
References: <20121023184229.9FCA418C0A4@mercury.lcs.mit.edu>
In-Reply-To: <20121023184229.9FCA418C0A4@mercury.lcs.mit.edu>
X-Enigmail-Version: 1.4.5
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 19:04:31 -0000
On 10/23/2012 11:42 AM, Noel Chiappa wrote: > > From: Michael StJohns <mstjohns@comcast.net> > > >> The IAOC is requesting feedback from the community concerning a > >> vacancy that the IAOC feels is not adequately covered by existing IETF > >> rules. > > > I'm not sure why the IAOC thinks that the recall procedure shouldn't be > > followed. > > Because it's a fairly lengthy, complex, and effort-consuming, process to use > in this kind of case - rather like using a pile-driver to crack a nut? The procedures are what they are, and the recall procedure provides a reasonable safeguard against abuse. By not following them you set a dangerous precedent. > I hear you, and understand the concern about ignoring established procedures, > but at the same time, calling for a hum from the IETF community is sufficient > to get the _entire procedure_ changed, a far more consequential act, so > asking for a hum to temporarily bypass them seems to me to be acting in the > general spirit. I here you, and understand your desire for expedience. But at the same time, the larger community has already expressed their will in establishing the procedure we have. It is neither safe, nor appropriate, to assume that the subset of people humming about this issue overlaps sufficiently with the subset that hummed about establishing the procedure to justify this decision. There is also the risk of how abrogating our own procedures makes us look to those observing us from the outside. > And of course we do need to update our procedures so that if this ever > happens again, we don't face the choice of rolling out the pile-driver, or > proceeding in an ad hoc way, but that's a separate point. No, it's a very cogent point, and one that should be pursued by interested parties who wish to modify the procedure for the next instance. To put this another way, if you think it is easy to get the hums you need to abrogate the procedure, it should be just as easy to accomplish the recall process. And actually doing it will greatly inform those who wish to improve the procedure for the future. Doug
- Re: IAOC Request for community feedback Barry Leiba
- Re: IAOC Request for community feedback Barry Leiba
- Re: IAOC Request for community feedback Eggert, Lars
- Re: IAOC Request for community feedback Alessandro Vesely
- Re: IAOC Request for community feedback Yoav Nir
- RE: IAOC Request for community feedback Adrian Farrel
- Re: IAOC Request for community feedback Rumbidzayi Gadhula
- Re: IAOC Request for community feedback Pelletier Ray
- Re: IAOC Request for community feedback Noel Chiappa
- Re: IAOC Request for community feedback Rumbidzayi Gadhula
- Re: IAOC Request for community feedback Jari Arkko
- Re: IAOC Request for community feedback Stephen Farrell
- Re: IAOC Request for community feedback John Leslie
- Re: IAOC Request for community feedback Bob Hinden
- Re: IAOC Request for community feedback Michael StJohns
- Re: IAOC Request for community feedback Noel Chiappa
- Re: IAOC Request for community feedback SM
- Re: IAOC Request for community feedback Olafur Gudmundsson
- Re: IAOC Request for community feedback Michael StJohns
- Re: IAOC Request for community feedback Doug Barton
- Re: IAOC Request for community feedback Tobias Gondrom
- Re: IAOC Request for community feedback Noel Chiappa
- Re: IAOC Request for community feedback Doug Barton
- Re: IAOC Request for community feedback David Kessens
- Re: IAOC Request for community feedback Doug Barton
- Re: IAOC Request for community feedback Paul Hoffman
- Re: IAOC Request for community feedback Henk Uijterwaal
- Re: IAOC Request for community feedback Michael StJohns
- Re: IAOC Request for community feedback Bob Hinden
- Re: IAOC Request for community feedback joel jaeggli
- Re: IAOC Request for community feedback joel jaeggli
- Re: IAOC Request for community feedback SM
- Re: IAOC Request for community feedback Doug Barton
- Just so I'm clear (was: IAOC Request for communit… Andrew Sullivan
- Re: Just so I'm clear Doug Barton
- Re: Just so I'm clear Eliot Lear
- Re: Just so I'm clear Doug Barton
- Re: Just so I'm clear Melinda Shore
- Re: IAOC Request for community feedback Brian E Carpenter
- Re: IAOC Request for community feedback edj.etc
- Re: IAOC Request for community feedback David Morris
- Re: Just so I'm clear Margaret Wasserman
- Re: IAOC Request for community feedback Bob Hinden
- Just so I'm clear (was: IAOC Request for communit… Andrew Sullivan
- RE: IAOC Request for community feedback Tony Hain
- Re: Just so I'm clear Doug Barton
- Re: Just so I'm clear Martin Rex
- Re: Just so I'm clear Mark Andrews
- Re: rules for the sake of rules, was Just so I'm … John Levine
- Re: Just so I'm clear Yoav Nir
- Re: Just so I'm clear Brian E Carpenter
- Re: IAOC Request for community feedback Tina TSOU
- RE: Just so I'm clear Tony Hain
- Re: Just so I'm clear Doug Barton
- Re: Just so I'm clear Michael StJohns
- Re: Just so I'm clear Melinda Shore
- Re: Just so I'm clear Michael StJohns
- Re: Just so I'm clear Brian E Carpenter
- Re: Just so I'm clear Doug Barton
- Re: Just so I'm clear David Morris
- Re: IAOC Request for community feedback Olaf Kolkman
- Re: IAOC Request for community feedback Dale R. Worley
- Re: IAOC Request for community feedback Turchanyi Geza
- Re: IAOC Request for community feedback Bob Hinden
- Re: IAOC Request for community feedback Bob Hinden
- Re: IAOC Request for community feedback Doug Barton