Re: Status of this memo

Donald Eastlake <d3e3e3@gmail.com> Tue, 27 April 2021 18:20 UTC

Return-Path: <d3e3e3@gmail.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 CEF183A1AD0 for <ietf@ietfa.amsl.com>; Tue, 27 Apr 2021 11:20:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level:
X-Spam-Status: No, score=-1.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 j8lLZ-5uA7Sp for <ietf@ietfa.amsl.com>; Tue, 27 Apr 2021 11:20:23 -0700 (PDT)
Received: from mail-il1-x135.google.com (mail-il1-x135.google.com [IPv6:2607:f8b0:4864:20::135]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28A033A1ACF for <ietf@ietf.org>; Tue, 27 Apr 2021 11:20:23 -0700 (PDT)
Received: by mail-il1-x135.google.com with SMTP id e14so26551881ils.12 for <ietf@ietf.org>; Tue, 27 Apr 2021 11:20:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=BtFbcfGBSCMiEGK/Fu6SdHUf78zUfv3Ps578pX4ikZE=; b=V41MoNkFwTAg/RJR4qcLsZYVOUQtvkwdzHgyfgBVLGLZgLHyK0dZd6AX2dp2ZiTuqD EIqF/MThQRXZRgfDNlcrsHRM8k5DmXUQe3l9A55ryx4tQi7ppnC7zQvA9ZI/Y97h7Z+L s3BzEbFGmgTLSHVaICeXnGCTXjTlUDB+ko4PIH+y49GuOlGBZWFF6V+gnypnRJ00JKRl rxWnlKUtjHWDvBNv69H3+WoenxwLLCNrOus3d/Cgc30Gk0qra/0lF31vTXBhnhZXaEDT N2S3YvAqmz0JJ/tkmCNjgxYYY8blGfGwSt90dkFadOkHBHWodg32W8zHMksfpTxtp8D6 sgGg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=BtFbcfGBSCMiEGK/Fu6SdHUf78zUfv3Ps578pX4ikZE=; b=JbwO+NSqBDJIcRV2UbS8teexWv1MkdkYinBPXOzV9d6n6H+zTAVU+V0hj7zMxeFE9X nHKW036B+6xmYQeDTUp2PKzJodsOd092lmqXee0zgCdtnJZiJt28KVw3pJBphZjsXBXU Aahq91S9L242+apQ1txpLwYPsWkOLn0GTXoxgAu5CXBhk+Ax9h8yU+b9SZlg7QeUjJF5 zkCDtogkJTDmT5KJHyHi1tGGkHwyrlOYpBmLAlJtbBecaTuxq0WJOLyzI29bZpRk5hoz YFh4OuztXDaUqi00dY0IRC6OZ4WihvZA2AgMk4LQxyxPPiRUYMJN7x7rhnNVURUo2sWN N2mg==
X-Gm-Message-State: AOAM532fTVJL2UviKGkoPhUlGtuu+PktiXC3wFdvp93UIQwAl/COaMmB UMCfcjCktLmKpdAxjB2pmldYn8b3bCnDBHbQmR4=
X-Google-Smtp-Source: ABdhPJx55veWcmIDJ0AdNJNsDXGMsWaDi3+54djTyGwXukfMadFJ4mcOb67vk5NfkN9CXrSI93m/0AuQUtynn+2crhM=
X-Received: by 2002:a05:6e02:12c9:: with SMTP id i9mr20120517ilm.276.1619547622281; Tue, 27 Apr 2021 11:20:22 -0700 (PDT)
MIME-Version: 1.0
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> <620f38e4-94f7-2b8c-54f0-1895ce2dded2@network-heretics.com> <1B2562DF-A451-4FFE-BDFD-84BB31CC96DD@eggert.org>
In-Reply-To: <1B2562DF-A451-4FFE-BDFD-84BB31CC96DD@eggert.org>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 27 Apr 2021 14:20:11 -0400
Message-ID: <CAF4+nEF_unKQJH77DEk-tak6ioJYqEeyjj3-3yB8BVzwjy2mZw@mail.gmail.com>
Subject: Re: Status of this memo
To: Lars Eggert <lars@eggert.org>
Cc: Keith Moore <moore@network-heretics.com>, ietf@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-T1xqa0iYB6Om1KFyQH5-YX-d_M>
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 18:20:28 -0000

On Tue, Apr 27, 2021 at 9:02 AM Lars Eggert <lars@eggert.org> wrote:
>
> Hi,
>
> On 2021-4-27, at 15:40, Keith Moore <moore@network-heretics.com> wrote:
> > The very notion of "adoption" of a draft by the IETF (or at least by a working group) is a Bad Idea, as it tends to indicate an assumed direction for the WG that isn't yet reflected by a deep understanding of the draft or its implications, and makes it harder for a WG to change direction.
>
> I'm not sure I follow. WGs have adopted I-Ds for decades; it's the usual way in which the IETF works, and is what causes I-D names to change from draft-yourname to draft-ietf.
>
> This process is central to our way of working; we even commissioned specific datatracker functionality for it ten years ago (RFC6174) and discussed the common practice in RFC7221.

I agree. Indeed, becoming a WG draft represents a fundamental change
in the status and process for a draft in that before that the
author(s) can change the body of the draft however they want and
add/remove authors as they want but after it is a WG draft the WG is
in charge of the content and the WG Chairs how the power to appoint
and remove authors/editors. Thus it is reasonable and beneficial that
there be some difference in marking and/or draft name between these
two cases.

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 2386 Panoramic Circle, Apopka, FL 32703 USA
 d3e3e3@gmail.com

> Thanks,
> Lars