Re: Status of this memo

Benjamin Kaduk <kaduk@mit.edu> Tue, 27 April 2021 21:54 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 4FC433A222A for <ietf@ietfa.amsl.com>; Tue, 27 Apr 2021 14:54:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.498
X-Spam-Level:
X-Spam-Status: No, score=-1.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.4, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no 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 DGw5kAb13q1N for <ietf@ietfa.amsl.com>; Tue, 27 Apr 2021 14:54:23 -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 623C03A2229 for <ietf@ietf.org>; Tue, 27 Apr 2021 14:54:22 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 13RLsGYP000891 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 27 Apr 2021 17:54:20 -0400
Date: Tue, 27 Apr 2021 14:54:15 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: Keith Moore <moore@network-heretics.com>
Cc: IETF Discussion <ietf@ietf.org>
Subject: Re: Status of this memo
Message-ID: <20210427215415.GK79563@kduck.mit.edu>
References: <376f83f0-89a3-cd0e-1792-c8434bd8a5d2@gmail.com> <9ACE59FA-30B6-475A-AF6B-4B874E4A2788@eggert.org> <1804294246.5904.1619512137931@appsuite-gw2.open-xchange.com> <D653D3B2-7666-409A-B856-2A4B1BA958CA@eggert.org> <3DBB64B1-40B8-4BC3-B66C-7F9B7F395874@akamai.com> <b5210c71-9500-3dba-05d2-4ae1c6ad16e9@network-heretics.com> <CAA=duU1VJs2vCE=uCF=fXO7FNedn9yPAaZWTgcaAiHTexA8uWA@mail.gmail.com> <CAF4+nEEz4x3HtUhWQ0ONYCpyHy27E4u7_chVEuHi3rDr+sc39A@mail.gmail.com> <b3762d56-bff2-6f71-caa2-69d34e81b9dc@network-heretics.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <b3762d56-bff2-6f71-caa2-69d34e81b9dc@network-heretics.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FjJoC-aiujQGurZuw57bU7Np4gk>
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: Tue, 27 Apr 2021 21:54:25 -0000

Hi Keith,

On Tue, Apr 27, 2021 at 03:03:20PM -0400, Keith Moore wrote:
> On 4/27/21 2:55 PM, Donald Eastlake wrote:
> 
> > I agree with Andy below but just to be clear, WG draft has a formal
> > standing as a starting point for work -- they are a draft over which
> > the WG has taken control.
> 
> emphatically disagree, and I believe that's a particularly harmful 
> concept to promote.

Could you elaborate more on how your position relates to the BCP 25
description of "Document Editor"?  ยง6.3 of RFC 2418 has:

   Most IETF working groups focus their efforts on a document, or set of
   documents, that capture the results of the group's work.  A working
   group generally designates a person or persons to serve as the Editor
   for a particular document.  The Document Editor is responsible for
   ensuring that the contents of the document accurately reflect the
   decisions that have been made by the working group.

Thanks,

Ben