Re: [Eligibility-discuss] Discussion at gendispatch?

John C Klensin <john-ietf@jck.com> Thu, 07 November 2019 01:20 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: eligibility-discuss@ietfa.amsl.com
Delivered-To: eligibility-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B063512008F for <eligibility-discuss@ietfa.amsl.com>; Wed, 6 Nov 2019 17:20:09 -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 YsBR2On8cH2c for <eligibility-discuss@ietfa.amsl.com>; Wed, 6 Nov 2019 17:20:07 -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 55BDC120045 for <eligibility-discuss@ietf.org>; Wed, 6 Nov 2019 17:20:07 -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 1iSWSv-00052F-LC; Wed, 06 Nov 2019 20:20:01 -0500
Date: Wed, 06 Nov 2019 20:19:56 -0500
From: John C Klensin <john-ietf@jck.com>
To: Pete Resnick <resnick@episteme.net>
cc: S Moonesamy <sm+ietf@elandsys.com>, eligibility-discuss@ietf.org
Message-ID: <AD938437D76F8DFB62E88E54@PSB>
In-Reply-To: <1753CDF1-7944-4BBA-8E73-DA8E731D786E@episteme.net>
References: <A809A60C-D235-479D-8239-85332AC0569B@episteme.net> <6.2.5.6.2.20191106061852.12a70190@elandnews.com> <1A26C4AF-E579-4215-AC2C-0E470616DC63@episteme.net> <779A84AD78B58E0DD0729F1C@PSB> <1753CDF1-7944-4BBA-8E73-DA8E731D786E@episteme.net>
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/eligibility-discuss/vIQSMSqHctgIRh9lEJJ_8GKIikY>
Subject: Re: [Eligibility-discuss] Discussion at gendispatch?
X-BeenThere: eligibility-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <eligibility-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/eligibility-discuss/>
List-Post: <mailto:eligibility-discuss@ietf.org>
List-Help: <mailto:eligibility-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Nov 2019 01:20:10 -0000


--On Wednesday, November 6, 2019 18:12 -0600 Pete Resnick
<resnick@episteme.net> wrote:

> On 6 Nov 2019, at 15:21, John C Klensin wrote:
> 
>> Pete,
>> 
>> This is fine with me with, as is my wont, a few qualifications
>> and concerns:
>> 
>> (1) It seems to me that the call and the (very few) email
>> notes that followed suggested some changes we might want to
>> make in the document.  I don't think we are even close to
>> consensus on them but, if we are going to reopen the
>> discussion in a different forum, I think it would be very
>> helpful to put discussion placeholders in the document.
> 
> It would be fine to put placeholders in the document, but I'm
> inclined not to "reopen the discussion in a different forum".
> That is, the purpose of gendispatch is to dispatch: Do a short
> review of the issues that are open, get a sense on the amount
> of work required to move it forward (if at all), and recommend
> whether to form a WG, have it AD sponsored, etc. In
> particular, gendispatch has no charter to "get the work done",
> so the only thing getting such a list into the document will
> do is give a better idea as to how to handle the document. (Of
> course, when we discuss such things, people are bound to ask
> questions and discuss some of the issues in the document, but
> the plan is to keep that discussion very limited.)
> 
> Whether the below should go into the document are entirely for
> a discussion on this list.

That is more or less exactly what I hoped you would say.  I
think it makes an gendispatch presentation or discussion
informational, not a request for action from that group.  Right?

   john