Re: Just so I'm clear

Doug Barton <dougb@dougbarton.us> Wed, 24 October 2012 19:34 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 B921721F8645 for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 12:34:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.413
X-Spam-Level:
X-Spam-Status: No, score=-3.413 tagged_above=-999 required=5 tests=[AWL=0.186, 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 pzSRU3owXdhK for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 12:34:31 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 171BB21F85A2 for <ietf@ietf.org>; Wed, 24 Oct 2012 12:34:30 -0700 (PDT)
Received: (qmail 20948 invoked by uid 399); 24 Oct 2012 19:34:15 -0000
Received: from unknown (HELO ?192.168.0.102?) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 24 Oct 2012 19:34:15 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <508842C2.4020203@dougbarton.us>
Date: Wed, 24 Oct 2012 12:34:26 -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: Margaret Wasserman <margaretw42@gmail.com>
Subject: Re: Just so I'm clear
References: <20121023192135.203AC18C0A4@mercury.lcs.mit.edu> <5086EF82.9060900@dougbarton.us> <20121023200713.GC1861@nsn.com> <5086FBCE.2070503@dougbarton.us> <20121023213251.GF27557@verdi> <50873AB4.1000905@dougbarton.us> <20121024034736.GC52558@crankycanuck.ca> <50876D39.20502@dougbarton.us> <508773E7.10203@cisco.com> <50877633.1000402@dougbarton.us> <EA9BEA2E-EE96-4E80-B719-652BBD620A79@lilacglade.org>
In-Reply-To: <EA9BEA2E-EE96-4E80-B719-652BBD620A79@lilacglade.org>
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: Wed, 24 Oct 2012 19:34:31 -0000

On 10/24/2012 5:49 AM, Margaret Wasserman wrote:
> 
> On Oct 24, 2012, at 1:01 AM, Doug Barton wrote:
>> I get what you're saying, but this is one of those times where
>> (arguably for the better) we've created a difficult procedure that
>> should be infrequently exercised. We should follow the procedure
>> because it _is_ the procedure. And then use the opportunity to
>> improve it.
> 
> The existence of the recall procedure does not imply that there isn't
> any other way for a seat to become vacant.  For example, a seat can
> become vacant when an I* member resigns or dies, and there is no need
> for a recall in those cases.

The 2 examples you gave are (as someone else pointed out)
incontrovertibly objective criteria, as is the explicit mention of the
use of the recall procedure in BCP 101. Nothing in the text suggests an
unfettered right of creating new definitions of "vacant."

For Melinda's benefit, in _addition_ to the process issue I am also not
in agreement with declaring the position vacant in this manner.

Doug