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

Benjamin Kaduk <kaduk@mit.edu> Fri, 26 April 2019 01:10 UTC

Return-Path: <kaduk@mit.edu>
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 265D01201CC for <ietf@ietfa.amsl.com>; Thu, 25 Apr 2019 18:10:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 TJckj5B25EfR for <ietf@ietfa.amsl.com>; Thu, 25 Apr 2019 18:10:18 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 036C2120158 for <ietf@ietf.org>; Thu, 25 Apr 2019 18:10:17 -0700 (PDT)
Received: from kduck.mit.edu (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x3Q19eWZ017628 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 25 Apr 2019 21:09:42 -0400
Date: Thu, 25 Apr 2019 20:09:40 -0500
From: Benjamin Kaduk <kaduk@mit.edu>
To: "Andrew G. Malis" <agmalis@gmail.com>
Cc: Stewart Bryant <stewart.bryant@gmail.com>, IETF Discussion <ietf@ietf.org>, S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: AD Sponsorship of draft-moonesamy-recall-rev
Message-ID: <20190426010940.GQ36553@kduck.mit.edu>
References: <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> <20F28A58-4D1D-40D7-8513-2DA7A4A8778C@akamai.com> <07b301d4fb40$84b0b940$8e122bc0$@olddog.co.uk> <c5040945-c4a6-7bee-2a65-715341931712@gmail.com> <CAA=duU0qCx5okt_norQOB7GAJs0UZswS_6rZ5mshEu1KkSM_5w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAA=duU0qCx5okt_norQOB7GAJs0UZswS_6rZ5mshEu1KkSM_5w@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JgJNp9P5qbdC7iXQWxNBWmaXvjY>
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 01:10:21 -0000

On Thu, Apr 25, 2019 at 10:47:42AM -0400, Andrew G. Malis wrote:
> I agree with Stewart, I think a BOF is overkill for this particular short

I'm not sure that we need to focus too much on "BoF" -- I don't see many
people specifically pushing for a BoF, whether virtual or in Montreal, when
work could get done on a non-WG mailing list as well.

> and focused draft. Even absent current AD sponsorship, discussion and
> refinement of the draft can continue on this list. If general community

I respectfully disagree: RFC 3005 is pretty explicit that the general
discussion list is only for "initial discussion only [...] unless the issue
is one for which the working group needs wider input or direction".  The
IESG is working on a place to continue this discussion and work through any
complications and/or subtleties of this and related topics, before it
returns to the general list for IETF LC and the wider input from the
community.

> consensus around a future revision of the draft can be shown on the list
> (as usual, by the absence of continued commenting following a new
> revision), it may then be more difficult for the IESG to not find at least
> one member to sponsor the publication process, including IETF last call.

Indeed.  I note that, per my understanding of
https://trac.ietf.org/trac/iesg/wiki/AreasDescription, an AD sponsoring a
draft should have personally reviewed that document and believe it ready
for publication as-is.  Given the continued discussion regarding this
document, I believe that a conclusion that the document is not ready for
publication "as-is" is justified, but I'm happy to see the discussion
progress.

-Ben