Re: AD Sponsorship of draft-moonesamy-recall-rev

Andrew Sullivan <ajs@anvilwalrusden.com> Fri, 26 April 2019 15:04 UTC

Return-Path: <ajs@anvilwalrusden.com>
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 F15AE12043C for <ietf@ietfa.amsl.com>; Fri, 26 Apr 2019 08:04:41 -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=i4lzD3nn; dkim=pass (1024-bit key) header.d=yitter.info header.b=C+lpmgMH
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 i1MudrUK03dM for <ietf@ietfa.amsl.com>; Fri, 26 Apr 2019 08:04:39 -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 99D42120437 for <ietf@ietf.org>; Fri, 26 Apr 2019 08:04:39 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id 94FBCBCC66 for <ietf@ietf.org>; Fri, 26 Apr 2019 15:04:38 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1556291078; bh=//ItihGPjnhsb+lDI2esCEsk3G9fsztHmo/i+tuSnO0=; h=Date:From:To:Subject:References:In-Reply-To:From; b=i4lzD3nnGlfu6Yairf+uqCNalMMexCAjxsRRYYzT3rp0/UHzqESKTj9dbl1NRJNmw 4IqMJ6unb7B4qzAmYB4mOiS1tLLCyYCVW+BQycVlO/EbmTJ5fBSNP4gQjwZlWaKExl il9lB/oubXW80fjTmJVpkDlYgLC6tsOuHl5KGRTs=
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 mhkWu6UGva_K for <ietf@ietf.org>; Fri, 26 Apr 2019 15:04:37 +0000 (UTC)
Date: Fri, 26 Apr 2019 11:04:36 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1556291077; bh=//ItihGPjnhsb+lDI2esCEsk3G9fsztHmo/i+tuSnO0=; h=Date:From:To:Subject:References:In-Reply-To:From; b=C+lpmgMHR7q9aZiRrttQdrfX54LeWOBuekrHeeCA8CMs5tkDNY2HeFzWbbbARiUl3 h0w1kX/liFKgmRuPOjqVZKgXSYKAMpG4tidawhL/wzA2f4OFFJ1pBUsQ8krFqCpK5Y aO7GqK7tT4+vmq95aTa/H9FCXopeq7NUB4XUgqug=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: AD Sponsorship of draft-moonesamy-recall-rev
Message-ID: <20190426150436.v4svwa67xja6267r@mx4.yitter.info>
References: <CABcZeBNdaWU4wwOK_MnWC5hOr7Lu3osmC_6_KKxB5fHuHVHyTw@mail.gmail.com> <23d54797-5c94-aa00-ec55-3f2c4fdfcfae@comcast.net> <6.2.5.6.2.20190424095017.13cdadc8@elandnews.com> <51068F13-E90F-42A2-8AE2-627D5E18B145@akamai.com> <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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <11F97591808485C30AD98A22@PSB>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Ju_yr8jkXzHTlUT8VFfu6e_M1Yo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 26 Apr 2019 15:04:42 -0000

Hi John,

I note that I am posting as an individual, and certainly not in any
capacity on behalf of the Internet Society, but that my thoughts below
are informed by my experience.

On Thu, Apr 25, 2019 at 01:24:11PM -0400, John C Klensin wrote:

> It seems to me that, unless you (or others) are ready to claim
> that all of the documents listed above other than 3777 are not
> legitimate, arguing that this I-D must go through a WG and WG
> Last Call (with or without a BOF) prior to IETF Last Call as a
> matter of our normal procedure with no other path permitted, is,
> to use your term, "strange".   There is, of course, an IETF Last
> Call and IETF review inherent in the AD-sponsored Individual
> Submission process: no one has proposed to eliminate or bypass
> either of those steps.

My concern about this document is rather different.  It lays out a
bunch of reasons to make adjustments, and does not in fact address
most of those reasons.  The main thing it does is make the procedure
easier to start, but it also doesn't adjust the procedure at all.

The procedure, however, is not itself inexpensive, it entails a degree
of collegial damage to the organization that ought to be taken quite
seriously, and it does not have a lot of clean exit procedures (so,
for instance, the procedure can't AFAICT be called off once it has
been initiated, if the petitioners pull out).  It seems to me to be
worth some pretty careful, even-tempered discussion. Perhaps the
procedure as designed is so designed because of an implicit
understanding that it would be somewhat hard to inititate.  Perhaps it
was designed in a cultural context of much greater social cohesion and
cultural homogeneity of the IETF than may be the case today.  The
present age is fractious and divided everywhere, and the IETF does not
appear, to me, to be resisting that zeitgeist.

Speaking selfishly, the procedure also imposes a burden on the
Internet Society President to find and appoint a Recall Committee
Chair.  As the incumbent who'd have to do that, my first problem is to
write a job description, then to find a suitable candidate who has the
time and motivation and reputation to do this.  Making this burden
easier to impose on me at surprising intervals is something that,
quite frankly, I would be inclined to resist were someone to ask me in
my professional capacity what I thought.  That suggests to me that the
procedure would need some additional modifications in order to make
the changes practical, and once the worm-can is open who knows what
additional red wrigglers will start moving around?

I just don't see how to treat this change as "fine tuning".  It's an
effort to make a nuclear option easier to use, and I do not understand
how that could be understood as anything other than a fundamental,
community-altering decision.  That kind of decision seems to me to
warrant the use of every mechanism one has to ensure one proceeds
with the right care.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com