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

Alissa Cooper <alissa@cooperw.in> Thu, 18 April 2019 16:31 UTC

Return-Path: <alissa@cooperw.in>
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 1BBCD120365; Thu, 18 Apr 2019 09:31:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=Zf/Oy/PW; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=6kWC/U33
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 qkN_ZGiVtH_A; Thu, 18 Apr 2019 09:31:47 -0700 (PDT)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78FF91201BB; Thu, 18 Apr 2019 09:31:47 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id A66952629F; Thu, 18 Apr 2019 12:31:46 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Thu, 18 Apr 2019 12:31:46 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm2; bh=I uve7XXySfGKFgmPuVUe8AhguBBGqUOwBri762ywxJA=; b=Zf/Oy/PWJSoyAFfuF oVybx6UnWyuzoNwUQp1DlplEvV0HEyIyWwBVou9qCb6FtysHNbvz79KJX8y8UQIE 9I+FkzAzTS1iiln5VrCi5aoKL9szmNrcvMlEQk0EIxakecy9yf30q15QAzUMT40Q BLkEMXvCcV6ZGHPY3VA1uDXVEo2Npp+h3pBvwc+gRogOMjTnXsnn61jVOzkuQ20e K19IHqtq4ez1f1jpJ+pykaBazKpZ8v+RjEKOvi0E9UQnBwHnnVpCQB3wGg7Ky3N7 ksQHFNJpu0RR7J6x4V84H0RpZp2P27vRLWocNCFlCcwFts3eeOmS0/GngI23hEdA 99v9g==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding: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=Iuve7XXySfGKFgmPuVUe8AhguBBGqUOwBri762ywx JA=; b=6kWC/U339t+q6gNDMgx22xNFCT0nwci2KPE6B5etfDb2/bTGQl7RPX14U SzUOj83PgjAsjz+wbrDeb6jzF/eH0O05m2AV9TzazqQI+E9j45w0o7q+QZAzOacN 4SGSVb4nzoH1N4g0Jl3tOugniYdrR7EnpaviQShgjHK4V8VAJQlIMMREpcXrvQmv VhbsN6FiC4weExGid9Cstf/y3l3QvWL2mT9dxG/CvDRtieCCrFaCoBePQsZqWOoS kPIheHXYwKt3UPV2ywBQ4kyagzmeHugUW1krkoXgbIxX7KaCdA8f9EDYNclHjv98 XJUjt0oLiqk36+UiMp3CeLc7ousiA==
X-ME-Sender: <xms:caa4XBY5jBnXObUDF8wFOpnzF3uKJ2cu26qXKNLzPALfCfH2w37SLg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrfeehgdegvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtdejnecuhfhrohhmpeetlhhishhs rgcuvehoohhpvghruceorghlihhsshgrsegtohhophgvrhifrdhinheqnecuffhomhgrih hnpehivghtfhdrohhrghenucfkphepudejfedrfeekrdduudejrdekjeenucfrrghrrghm pehmrghilhhfrhhomheprghlihhsshgrsegtohhophgvrhifrdhinhenucevlhhushhtvg hrufhiiigvpedt
X-ME-Proxy: <xmx:caa4XOgWdSsXa7UEvBw3ZecJFDRRpBD2BXkuXnOSTNnkCkFpMyR65Q> <xmx:caa4XJjYCqzxIl_vQwWoN3zf7l_CBSLviOXHsxj07OOoObXWm0gL8Q> <xmx:caa4XDBmfMHClHot0qP2woWELXchc54aZTC7FXm4B8UjnidWyOBAUA> <xmx:cqa4XBTNjdaUrUM1Kyg-RNcO_v17Z5k4NeTigBr4riEjMpraEDlHOA>
Received: from rtp-alcoop-nitro5.cisco.com (unknown [173.38.117.87]) by mail.messagingengine.com (Postfix) with ESMTPA id 02F00E4472; Thu, 18 Apr 2019 12:31:44 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: Re: AD Sponsorship of draft-moonesamy-recall-rev
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <033d01d4f52f$c6f2dca0$54d895e0$@olddog.co.uk>
Date: Thu, 18 Apr 2019 12:31:37 -0400
Cc: S Moonesamy <sm+ietf@elandsys.com>, John C Klensin <john-ietf@jck.com>, IESG <iesg@ietf.org>, ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <C7274EAB-7DDC-491F-9DD2-0CFFADB13CA9@cooperw.in>
References: <6.2.5.6.2.20190405085139.0d5c39b0@elandnews.com> <54510B49-175B-4CE6-9319-1F9A4803940E@cooperw.in> <033d01d4f52f$c6f2dca0$54d895e0$@olddog.co.uk>
To: Adrian Farrel <adrian@olddog.co.uk>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/c0R0oB77p0-o1Xmh5Lq-YrO9QiY>
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: Thu, 18 Apr 2019 16:31:49 -0000

Hi Adrian,

> On Apr 17, 2019, at 11:10 AM, Adrian Farrel <adrian@olddog.co.uk> 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. 

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 <ietf-bounces@ietf.org> On Behalf Of Alissa Cooper
> Sent: 17 April 2019 15:46
> To: S Moonesamy <sm+ietf@elandsys.com>
> Cc: John C Klensin <john-ietf@jck.com>; IESG <iesg@ietf.org>; ietf@ietf.org
> Subject: Re: AD Sponsorship of draft-moonesamy-recall-rev
> 
> Hi SM,
> 
>> On Apr 5, 2019, at 12:08 PM, S Moonesamy <sm+ietf@elandsys.com> 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. https://tools.ietf.org/html/draft-moonesamy-recall-rev-01
>> 
>