Re: [Gendispatch] Agenda items for gendispatch?

John C Klensin <john-ietf@jck.com> Fri, 28 February 2020 06:09 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F0943A10E3; Thu, 27 Feb 2020 22:09:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 iS5ff0YqCYHy; Thu, 27 Feb 2020 22:09:26 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 584953A10D8; Thu, 27 Feb 2020 22:09:26 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1j7Ypt-000Nlf-KE; Fri, 28 Feb 2020 01:09:21 -0500
Date: Fri, 28 Feb 2020 01:09:14 -0500
From: John C Klensin <john-ietf@jck.com>
To: Adam Roach <adam@nostrum.com>, Pete Resnick <resnick@episteme.net>
cc: gendispatch@ietf.org, IETF discussion list <ietf@ietf.org>
Message-ID: <54F92D50B607699D65BD6239@PSB>
In-Reply-To: <123a6f60-7d9b-f26a-34e8-44c74d0db00d@nostrum.com>
References: <ED3EB3D9-480E-4D58-8767-0B1B4202F6C0@episteme.net> <97866639-e9b5-89b8-ede2-b1abdc79fe5b@nostrum.com> <F2D8D859-724B-4313-88CB-921909FF33A9@episteme.net> <330A44632BE7ED6CC3287178@PSB> <123a6f60-7d9b-f26a-34e8-44c74d0db00d@nostrum.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/6zbSDLzycT10ORQul9Ye0Up4pYw>
Subject: Re: [Gendispatch] Agenda items for gendispatch?
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Feb 2020 06:09:30 -0000


--On Thursday, February 27, 2020 22:40 -0600 Adam Roach
<adam@nostrum.com> wrote:

> John --
> 
> As I mentioned to the chairs privately, I may well run out of
> time to rev this document prior to Vancouver. If I do have
> time to revise it, my plan is to incorporate feedback
> specifically about the draft that was provided on the
> ietf@ietf.org list during the six months of its initial
> validity.
> 
> I'm not going to comment on any supposed interaction between
> the document and your appeal until the IESG has reached
> consensus on a response: doing so would necessarily presuppose
> an outcome (both in disposition and rationale), which would be
> presumptuous on my part.

Adam,

I was not asking for such a comment before the IESG reaches (and
announces) its conclusions.  Your providing one would clearly be
inappropriate (whether presumptuous or not) and I would not make
such a request.  However, given that your document was
specifically mentioned in the appeal (which does not prove there
is any interaction, of course), I was just trying to suggest to
Pete that, _if_ the IESG reaches some sort of conclusion and
that conclusion were to include either agreement that there is
an interaction or that the document action being appealed is
about a problem that your document might lead us into more of,
it might be wise to block out a bit more time for discussion
than might otherwise be the case. 

best,
   john