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

'Andrew Sullivan' <ajs@anvilwalrusden.com> Tue, 30 April 2019 22:46 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 E7BC812031D for <eligibility-discuss@ietfa.amsl.com>; Tue, 30 Apr 2019 15:46:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=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=AS9BLW30; dkim=pass (1024-bit key) header.d=yitter.info header.b=H1ErZOzp
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 kPmVO3NBLoEn for <eligibility-discuss@ietfa.amsl.com>; Tue, 30 Apr 2019 15:46:02 -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 C34751200A0 for <eligibility-discuss@ietf.org>; Tue, 30 Apr 2019 15:46:02 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id D0932BCC66; Tue, 30 Apr 2019 22:46:01 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1556664361; bh=OjCvXxR1XX9dZggVw8DhYJlRAiyBNKpKBhpqq/QVJmQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=AS9BLW30h8Pf1XxULnUeGNH3nYJ6nqJhtu3gQ6rCQHB//hw5jlbpbSpVK7tm9+MtT ct3t+BIWgFjKTmB41Q8mkcKr1DhR4xjcIuVgLY4YJ6YXcQhHNcU7KXxD+pKWOkUbR6 iDLmVHDX0gFQk2HnIh3IXLYtRcoCfPH/Fa2OEjRc=
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 M1ROxi6tBfPA; Tue, 30 Apr 2019 22:46:00 +0000 (UTC)
Date: Tue, 30 Apr 2019 18:45:57 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1556664360; bh=OjCvXxR1XX9dZggVw8DhYJlRAiyBNKpKBhpqq/QVJmQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=H1ErZOzp3hLjKWQkntpnIzF0VSKp1SPc/27u52t7ldGnP/0qywKfBWuInC6ENZg+j ch5tjqp/ZMqd7VRmULTmBhWCxIWtE51r6GcGk2SKZpMaF4QtinRKsugG8GyL1v3JfK Eq6OX1kNkNjVsbCMkVG36KiI6VVnC99ylac+7UwM=
From: 'Andrew Sullivan' <ajs@anvilwalrusden.com>
To: Adrian Farrel <adrian@olddog.co.uk>
Cc: eligibility-discuss@ietf.org
Message-ID: <20190430224557.gxbfioixczabatnz@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> <024701d4feca$c9fae920$5df0bb60$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <024701d4feca$c9fae920$5df0bb60$@olddog.co.uk>
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/NuLJ2ZfD_-Hcx9LWiE88Zh86-mc>
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: Tue, 30 Apr 2019 22:46:05 -0000

Hi,

I dropped ietf@.  No hat.

Apologies for the short post, but I'm unfortunately quite pressed for
time this week & can't devote the cycles to this it deserves.  But I
think there's one critical point I ought to make.

On Mon, Apr 29, 2019 at 09:33:21PM +0100, Adrian Farrel wrote:

> I wonder whether we need to break up this discussion into different topics
> (threads?) so that the bleed-over doesn't get in the way of our
> conversation.

We could definitely figure out a way to tease these different issues
apart.  Nevertheless, I think the overall point I was originally
trying to make is amply demonstrated:

> The topics are:
> 
> 1. Should members of the IESG and IAB (and other Nomcom-appointed people) be
> allowed to sign recall petitions?
> 2. Should seated Nomcom members be allowed to sign recall petitions?
> 3. How do we qualify "participation" at IETF meetings?
> 4. Should remote participants at IETF meetings be qualified to sign recall
> petitions?
> 5. What should be the number of signatories on a recall petition?
> 6. What is the right number of recall petitions?

This is a list of topics of sufficient breadth and sensitivity that I
think it needs unpacking and exploration.  I am not sure I agree with
your conclusions about obvious changes, but that's the sort of
discussion that I think is best had across the community.  And that
was really the point I was originally trying to make: this requires
the kind of care this community takes when it is going to make
sensitive or fundamental changes.  The way one does that in the IETF,
usually, as I understand it, is to form a working group, so that seems
to me to be the best path for this.

> One last point from me that might be applicable to the discussion of
> fractiousness. I don't think any of this discussion comes about because
> anyone is trying to form a recall petition. I don't think there is anyone
> expressing such extreme discontent or agitating to remove anyone. To the
> contrary: the best time to discuss and work on the backstop procedures is
> precisely when they are not needed.

I could not agree more, and I think it would be entirely correct that
now, at a time when the IETF has started to work out its new path for
administrative arrangements and with a newly-arrived IESG, the WG to
undertake this effort be formed and get to work.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com