Re: [Eligibility-discuss] AD Sponsorship of draft-moonesamy-recall-rev

Andrew Sullivan <ajs@anvilwalrusden.com> Sat, 27 April 2019 22:19 UTC

Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: eligibility-discuss@ietfa.amsl.com
Delivered-To: eligibility-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EE311200F4 for <eligibility-discuss@ietfa.amsl.com>; Sat, 27 Apr 2019 15:19:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yitter.info header.b=HnEAJjjs; dkim=pass (1024-bit key) header.d=yitter.info header.b=UAh/hPzN
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UhZRa-SoB-pW for <eligibility-discuss@ietfa.amsl.com>; Sat, 27 Apr 2019 15:19:01 -0700 (PDT)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E62D5120121 for <eligibility-discuss@ietf.org>; Sat, 27 Apr 2019 15:19:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id 8B894BCC66; Sat, 27 Apr 2019 22:18:59 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1556403539; bh=OBUlEKfGnQoAmhtlJvxlmdbowiNmeW8oKiSofXFQYqM=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=HnEAJjjsn3r+p442h3wOGpW7lnYETLtqPj6oHhalkbo5je+uEj0DdW6Vgl/ZUK58J wc5FYqSKP/zXjzFSKNaxgFGYVRjhUDc+uTYgaG0vP9kOXpkmVIDMZm+YGgWCRNoxMG o0IIrXeBK5Hmi6XmSFAuOCikAXyVYQEyTqux9tfM=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WV0c13HoG9Vw; Sat, 27 Apr 2019 22:18:57 +0000 (UTC)
Date: Sat, 27 Apr 2019 18:18:56 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1556403537; bh=OBUlEKfGnQoAmhtlJvxlmdbowiNmeW8oKiSofXFQYqM=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=UAh/hPzNsJIexypZB4FJrbPcimvZ21cDwForJ1SAOCIc/s1AgjcHZX7ZUZlyq7Dv/ IxPDs9D4IU5P04qsvNpB4Q43AJh+UJZ+piGl3wB878/exQfzg5lI6rTN8RlWXP/bZ0 iHxwddsB0m+4THFVO1hrPcXNdZhHYsfnL7NnRw4o=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Cc: eligibility-discuss@ietf.org, Adrian Farrel <adrian@olddog.co.uk>, John C Klensin <john-ietf@jck.com>
Message-ID: <20190427221856.sxr46qr7j5niwrk4@mx4.yitter.info>
References: <20190424201939.GM3137@localhost> <6.2.5.6.2.20190424134823.0c9faf68@elandnews.com> <20190424211123.GO3137@localhost> <6.2.5.6.2.20190424144539.0cabcde0@elandnews.com> <20190424234334.GQ3137@localhost> <11F97591808485C30AD98A22@PSB> <20190426150436.v4svwa67xja6267r@mx4.yitter.info> <0a1e01d4fc6c$10b93df0$322bb9d0$@olddog.co.uk> <20190427155921.i32pftxdbkvv7ist@isoc.org> <6.2.5.6.2.20190427094440.12099d10@elandnews.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <6.2.5.6.2.20190427094440.12099d10@elandnews.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/Tk_MBcPhSy8q7z1U_o0PrO-KA7M>
Subject: Re: [Eligibility-discuss] AD Sponsorship of draft-moonesamy-recall-rev
X-BeenThere: eligibility-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <eligibility-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/eligibility-discuss/>
List-Post: <mailto:eligibility-discuss@ietf.org>
List-Help: <mailto:eligibility-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Apr 2019 22:19:04 -0000

Hi,

I've changed the destination list on this.  Again, no hat.

On Sat, Apr 27, 2019 at 12:16:45PM -0700, S Moonesamy wrote:
> 
> The draft does not make any change to the section about the Internet Society
> President.

Yes, I'm aware.

> There is the following sentence in the Note Well: "By participating in the
> IETF, you agree to follow IETF processes and policies".  Signatories are
> "expected to be familiar with the IETF processes and procedures, which are
> readily learned by active participation ..."  It is the up to a signatory to
> show that he or she participated in those IETF meetings.

That does not clarify the issue of "participation" at all.  We can't
have it be a criterion of eligibility if it does not have a
well-defined public meaning.

> Please see draft-sullivan-mtgvenue-decisions-00 as it discusses about
> different types of attendees.

I don't see how that is relevant.
 
> From what I recall, it only took one appointee to negatively impact the work
> of the administrative support activity.  Russ explained why it was not
> possible for the body to exercise the recall process option.

Sure, and in the end we solved that problem and then did not actually
have a problem gettinh the signatures together, from what I recall.
In any case, the evidence is that we were in fact able to persuade the
person to leave which meant that we didn't actually need to exercise
the entire procedure.

> There are 10 random persons who choose the so-called "leadership" each year.

Actually, there are 10 randomly-chosen people from a pool of people
who have been qualified from a well-defined meaning of having
participated in the processes of the organization.  Whether that
definition is adequate might be up for debate, but it is a clear and
complete definition, which is not what's in the current draft.

> The persons  do not have to have to participate on this mailing list even
> though this is usually the place where IETF policies are discussed.  What is
> the difference between them and 10 random persons who participate remotely?

One difference is how they are qualified.  Another difference is that
their decisions are subject to confirming bodies.  A third difference
is that they are selecting among possible candidates or none in a
process that has multiple turn off points.
 
> Is an accountability mechanism a way to hold the so-called "leadership" to
> ransom?

It can be, if it is poorly suited to purpose.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com