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

S Moonesamy <sm+ietf@elandsys.com> Sat, 20 April 2019 18:44 UTC

Return-Path: <sm@elandsys.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 33C1A120159; Sat, 20 Apr 2019 11:44:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.2
X-Spam-Level:
X-Spam-Status: No, score=-0.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_SORBS_WEB=1.5] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=qa8fClGA; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=vpWPrhGI
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 fDEiWj203yVr; Sat, 20 Apr 2019 11:44:08 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2611E1200FC; Sat, 20 Apr 2019 11:44:08 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.226.55.174]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id x3KIhpLg015264 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 20 Apr 2019 11:44:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1555785844; x=1555872244; bh=tP7Xim/+n8GQtLWCOH+gfTD54UAJW45ztlTF7wa+f3c=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=qa8fClGAccCk3nrIzvd7Taju4YNlnh8hIo9rvoI+VvcpDqd8JMKEWQ6POEJb7V6hf I25CwsuoUz/IA4Vsx25xzDmTWfnYg9b78Prv5ktgveY7+KP3cRdRFOMbUmDutSy6z+ EHgn7GYyP+Cy8MwyXpBUown4NsTlRmuLKWqY/RGw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1555785844; x=1555872244; i=@elandsys.com; bh=tP7Xim/+n8GQtLWCOH+gfTD54UAJW45ztlTF7wa+f3c=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=vpWPrhGIKwczrLTTYGqxL/sfx7qH9U0FcVtTQ5l2Eto4M+FOlhI8qr3+aMdB8FAfw D78orSqFZdZsGt+KS1u0FbW0fPNARPlhpwgmGQE8V9y07WEaNc/bqQduWaXDUvK9hC cIfDhktGMiOLjsyzvcebLv/erdyBpTiCIA9b4G3A=
Message-Id: <6.2.5.6.2.20190420103359.0f1668d8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 20 Apr 2019 11:43:39 -0700
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: AD Sponsorship of draft-moonesamy-recall-rev
Cc: John C Klensin <john-ietf@jck.com>, IESG <iesg@ietf.org>, Adrian Farrel <adrian@olddog.co.uk>
In-Reply-To: <CAKKJt-eNgUZF8asiP7g3dkLCLauNkAs3rTZh_c4VS8PXUkWz0Q@mail.g mail.com>
References: <6.2.5.6.2.20190405085139.0d5c39b0@elandnews.com> <54510B49-175B-4CE6-9319-1F9A4803940E@cooperw.in> <033d01d4f52f$c6f2dca0$54d895e0$@olddog.co.uk> <CAKKJt-eNgUZF8asiP7g3dkLCLauNkAs3rTZh_c4VS8PXUkWz0Q@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-jmPTjUPqynvgWd8tArWFRYAlSw>
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: Sat, 20 Apr 2019 18:44:09 -0000

Hi Spencer,
At 08:29 PM 17-04-2019, Spencer Dawkins at IETF wrote:
>That could be a fine plan. It assumes that The S is For Steering.

:-)

>Another orthogonal Fine Plan could be for an AD to ask the IAB to 
>provide a BOF Shepherd to help the proponents - which almost 
>certainly means "more people than just SM" - to produce a BOF 
>request that will result in a successful BOF, so participants who 
>rarely if ever see each other face to face don't have to figure that out.
>
>The procedure for this is described at 
>https://www.iab.org/documents/correspondence-reports-documents/2012-2/iab-member-roles-in-evaluating-new-work-proposals/, 
>unless the IAB has changed that procedure since 2012.
>
>And if this discussion is only about the definition of who is 
>eligible to sign recall petitions, whether with or without John 
>Klensin's proposal, I note that 
>https://mailarchive.ietf.org/arch/browse/ietf-nomcom/ is still an 
>active list, and seems to be exactly the right place for limited 
>discussion. If what's wanted is POISED2019, that's another mailing 
>list, of course, which any AD can approve.

Thanks for the helpful suggestions.  Several years ago, you and I had 
a discussion on that mailing list.

BCP 39 is about architectural oversight.  Anyway, a "BOF" is 
described as a session for
"market research" and technical "brainstorming".  There are working 
group which have been formed without a "BOF".  If I am not mistaken, 
I may have chaired that type of working group.  As for a "Fine Plan", 
it will be very difficult to find/justify funding for the subject 
(please see the email from the General Area Director).

Regards,
S. Moonesamy