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

Alissa Cooper <> Fri, 26 April 2019 19:57 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 198711204BE; Fri, 26 Apr 2019 12:57:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key) header.b=To4+CqHQ; dkim=pass (2048-bit key) header.b=yVclJM7z
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 4yh7YfNk1Kq6; Fri, 26 Apr 2019 12:57:49 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 67A9E1204B0; Fri, 26 Apr 2019 12:57:49 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal []) by mailout.nyi.internal (Postfix) with ESMTP id 834F1220B8; Fri, 26 Apr 2019 15:57:48 -0400 (EDT)
Received: from mailfrontend1 ([]) by compute7.internal (MEProxy); Fri, 26 Apr 2019 15:57:48 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; h= from:message-id:content-type:mime-version:subject:date :in-reply-to:cc:to:references; s=fm2; bh=G+VPDqchlMjGmTHjlPuvWVQ Ta0vcKNjCZG2A3BVjNHY=; b=To4+CqHQiVLgoqNqx26OhGLWn9+rlbx8+BbjBr1 agWGQ/egCKqkxx3Nv70uURPsCU4LvB5WicKw5UiHY1dkp17CCGDpMY6NbveGlUNT pbSyu10HHFN1EUWjKOrwjfvMAwRskGWGYuLXFW6Qnr1xmn1fPtRMqP3/M1NjBVAP NKexcDxJzfSaaDfiMfjS32ixRzRJGJluW2+UaV/n/tOt02Mhw3L1AmQDWuKQmU5Y Hbrw9HHJjvsYvCAcQr85stIbKkPqVOmbDYeiRlkU6mRnnKWjyZ/XtQsheeyHHrz0 HaTMqPqfpstIvQSgl15kR2qH4OPzoamYJAL4ehgbsW6VDGA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=G+VPDq chlMjGmTHjlPuvWVQTa0vcKNjCZG2A3BVjNHY=; b=yVclJM7zaDV65uaIQD5vcP OjfZEYAGDSV2zg9yCoYgBDQSxeRrI/j8oNrcue3P3T0k6Z8TE8+PG4Pjj7O3VCeq iJDBk/F46HUwxAv7d5Ep636bTu2dbKkoyBjakCpP+U+mBwuvRXAtyZXWiSaSiqgv Dp1Hs/mix6GpopXNqZPXXs/0X4rus90g19RQX/UMzkGkIvDlpRS8LgOwvMP9VwF5 FR1zKdMwj25AOErcsaXv51KBkH1ujr8YrwMOGnRUrJX7a7lqq61njU4L/ACOD7Na HWjioAtyO3wEhyhbvoWqbQE7D+BkgWBgNvhXeHgiPPpvye1BiShAwQ2Qm94TeB8A ==
X-ME-Sender: <xms:u2LDXOinwGv8qiq0w0vWXoH4CnOYoTCgy6ap21KicTmJ4d-Y-gdubA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrheeigddugeehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefhkfgtggfuffgjvfhfofesrgdtmh erhhdtjeenucfhrhhomheptehlihhsshgrucevohhophgvrhcuoegrlhhishhsrgestgho ohhpvghrfidrihhnqeenucfkphepudejfedrfeekrdduudejrdekjeenucfrrghrrghmpe hmrghilhhfrhhomheprghlihhsshgrsegtohhophgvrhifrdhinhenucevlhhushhtvghr ufhiiigvpedt
X-ME-Proxy: <xmx:u2LDXDTj5pKn8vEzsk39mzTa4kQpw0uS4BpMd_Auhz8w9kjBH2LSqw> <xmx:u2LDXBFiCkouWOpLHVBq_ETcGQsVw5HmYzqXMdrX7juM20tnOScerw> <xmx:u2LDXLkQMg_Dxif6Cvew08hb8au9G3bSvzURe5Qo1fNTfqaqPYMmJg> <xmx:vGLDXOxkXEGPr_p874DWYoBAC3DXOAVm8QMhmOy0SF6edrjToMppzQ>
Received: from (unknown []) by (Postfix) with ESMTPA id 445A8E4176; Fri, 26 Apr 2019 15:57:47 -0400 (EDT)
From: Alissa Cooper <>
Message-Id: <>
Content-Type: multipart/alternative; boundary="Apple-Mail=_EB722525-3C38-41E5-BFE9-F2041AFB7D49"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: Re: AD Sponsorship of draft-moonesamy-recall-rev
Date: Fri, 26 Apr 2019 15:57:45 -0400
In-Reply-To: <>
Cc: John C Klensin <>, S Moonesamy <>, IESG <>
To: "<>" <>
References: <> <> <033d01d4f52f$c6f2dca0$54d895e0$> <>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 26 Apr 2019 19:57:53 -0000

Hi all,

Responding to my own mail now that the IESG retreat has concluded.

> On Apr 18, 2019, at 12:31 PM, Alissa Cooper <>; wrote:
> Hi Adrian,
>> On Apr 17, 2019, at 11:10 AM, Adrian Farrel <>; wrote:
>> Thanks for this email, Alissa. It's interesting. I presume it means that the IESG is unanimous, because it only takes one AD to AD sponsor a draft.
> I asked the IESG. I did not get responses from everyone, but of the people who did respond none of them volunteered to AD-sponsor.
>> BoFs are very good forums for debating stuff. Good for focussing in on requirements. Good for scoping work. Good for establishing a community to do the work.
>> But:
>> - why wait until Montreal to discuss this?
>> - why use a predominantly face-to-face meeting to discuss an issue that is considerably about non-attendance at face-to-face meetings?
>> - what more work is needed beyond debating the content of the current draft?
>> Can I suggest:
>> - An AD needs to "adopt" this idea. That doesn't mean support it, but it does mean facilitation
>> - A mailing list venue is needed (either this list or a new specific list)
>> - A virtual/interim BoF be held in (say) four weeks from now.
> A virtual or physical BOF is certainly possible. We did a virtual BOF for LURK, and I think one other one recently that I’m failing to remember. And typically a successful BOF is preceded by active discussion on a mailing list, which of course anyone can request (or re-use ietf-nomcom as Spencer suggested).
> The IESG will discuss at our retreat next week if there is an AD available to shepherd this effort right now. 

The IESG discussed this topic at our retreat. We have setup <> to be the home for the discussions of draft-moonesamy-recall-rev and related discussions about recall and nomcom elgibility criteria, the recall process, and remote participation. If you’re interested in these topics, please subscribe to that list. 

Alexey, Warren, and Suresh will be guiding discussions on that mailing list and will be reaching out to the draft authors about next steps. We have also requested a shepherd from the IAB to help with this.

I will send to my own responses to some outstanding emails in this thread that were addressed to me and deal with the substance of the draft.

for the IESG

> Alissa
>> Why rush? We've lasted this long with the current system, why do a few extra months matter?
>> Well, the answer is that the energy to do the work is there now. Let's use that energy to discuss and (if agreed) make changes. Let's not risk anyone suggesting that we are deferring discussions in the hope that the issue goes away :-)
>> Thanks,
>> Adrian
>> -----Original Message-----
>> From: ietf <>; On Behalf Of Alissa Cooper
>> Sent: 17 April 2019 15:46
>> To: S Moonesamy <>;
>> Cc: John C Klensin <>;; IESG <>;;
>> Subject: Re: AD Sponsorship of draft-moonesamy-recall-rev
>> Hi SM,
>>> On Apr 5, 2019, at 12:08 PM, S Moonesamy <>; wrote:
>>> Dear General Area Director,
>>> In March, I sent a message to the IETF discussion list about the recall process.  As you are probably aware, there was a lively discussion on the subject.  I submitted an I-D [1] about the subject.  There were a comments on the I-D and they were addressed in draft-moonesamy-recall-rev-01
>>> I am enquiring about whether you, or any other Area Director, would like to sponsor the I-D or whether you would like a proposal for a working group to look into the draft and other related issues.
>> I discussed this with the IESG and our recommendation is for you to submit a BOF proposal if you’d like to pursue this further. We think these kinds of changes to the IETF’s governance structure need the more in-depth problem statement discussion and broader review that a chartering process and working group would provide.
>> Thanks,
>> Alissa
>>> Regards,
>>> S. Moonesamy
>>> 1.