Re: [DNSOP] draft-hsyu-message-fragments replacement status updated by Cindy Morgan

Benno Overeinder <benno@NLnetLabs.nl> Fri, 29 April 2022 20:54 UTC

Return-Path: <benno@NLnetLabs.nl>
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 15381C1594B4; Fri, 29 Apr 2022 13:54:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8gW7UQ8g4CWa; Fri, 29 Apr 2022 13:54:24 -0700 (PDT)
Received: from outbound.soverin.net (outbound.soverin.net [116.202.126.228]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27334C14F725; Fri, 29 Apr 2022 13:54:22 -0700 (PDT)
Received: from smtp.soverin.net (unknown [10.10.3.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) by outbound.soverin.net (Postfix) with ESMTPS id BBF4A298; Fri, 29 Apr 2022 20:54:18 +0000 (UTC)
Received: from smtp.soverin.net (smtp.soverin.net [10.10.4.99]) by soverin.net
Message-ID: <aba0f124-8074-30f2-975e-525fb61ebc7e@NLnetLabs.nl>
Date: Fri, 29 Apr 2022 22:54:13 +0200
MIME-Version: 1.0
Content-Language: en-GB
To: Mukund Sivaraman <muks@mukund.org>
Cc: Lars Eggert <lars@eggert.org>, Cindy Morgan <cmorgan@amsl.com>, Shane Kerr <shane@time-travellers.org>, IETF Discussion <ietf@ietf.org>, yliu@cfiec.net, hsyu@cfiec.net, hsyu@biigroup.cn, DNSOP Working Group <dnsop@ietf.org>, DNSOP WG Chairs <dnsop-chairs@ietf.org>
References: <165116358815.5877.9244565954759130167@ietfa.amsl.com> <YmrKSN5OSQh2/SQf@d1> <CAF4+nEE0AJSjUfYXLjxUE94k544k_cK2v7HxNRS1XmSVOnQRPg@mail.gmail.com> <YmrlXv1/L6Ina504@d1> <2AD4D97C-3CAE-476C-B257-6AC7BD8F7F93@amsl.com> <7000069C-15D4-444F-89D1-79B0C89DFBB7@eggert.org> <57d6f6da-a88a-8c84-e5a2-cf956530c64a@NLnetLabs.nl> <YmxKIYi7l2bN2u2F@d1>
From: Benno Overeinder <benno@NLnetLabs.nl>
Subject: Re: [DNSOP] draft-hsyu-message-fragments replacement status updated by Cindy Morgan
In-Reply-To: <YmxKIYi7l2bN2u2F@d1>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CIAPk8mSHic7pmXGs2EdClJsj5E>
X-Mailman-Approved-At: Sat, 30 Apr 2022 17:36:33 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.34
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, 29 Apr 2022 20:54:28 -0000

Mukund,

On 29/04/2022 22:27, Mukund Sivaraman wrote:
>>
>> This is indeed how the DNSOP chairs see it and have guided the (new set of)
>> authors in this way.  We have also asked Haisheng to contact the secretariat
>> to correct the situation as we cannot withdraw individual drafts or change
>> status.
> 
> With the way this is worded, is it accepted practice for the names of
> authors of a document to be removed to make way for another set of
> authors?

No, certainly not.  If you interpret it that way, I have chosen the 
wrong words.

What I meant to say is that we made suggestions or try to guide the 
practical procedure for changing the status of document to indicate that 
it is not an active document.

The broader discussion of whether it is an accepted practice or not was 
not the subject of my answer to the list.  As I understand there is a 
discussion in the IESG now, and with the email thread on the list and 
Brian's draft, 
https://datatracker.ietf.org/doc/html/draft-carpenter-whats-an-author-02, we 
can make progress to better define the process and provide guidance to 
authors and IETF participants.


-- Benno