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

Mukund Sivaraman <muks@mukund.org> Fri, 29 April 2022 21:24 UTC

Return-Path: <muks@mukund.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1F46C1595E5; Fri, 29 Apr 2022 14:24:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mukund.org
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 hexH0ZzdiMsi; Fri, 29 Apr 2022 14:23:58 -0700 (PDT)
Received: from mx.mukund.org (mx.mukund.org [IPv6:2a01:4f8:252:2ade:1::78]) (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 9946EC159521; Fri, 29 Apr 2022 14:23:58 -0700 (PDT)
Date: Sat, 30 Apr 2022 02:53:51 +0530
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mukund.org; s=mail; t=1651267434; bh=Gzur2rnJH2CbLM6tUgmS26cosMhKXgdsVYb2ZTKCqYg=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=SmbjQ19potNBAvvmJrl5BJRcf7JsjoNgV/LWW5dWRrwHYeXwwZ9aw3n/UEyiuPHAU NM2tOCMn9D9rENvQHFaQqRJGCrMLMoDQoaKgxaSXE0HoN5PfL2hT9zIbnHnjuFnGJj Ot1pATzgocorrPuVaDH5p2W+L7GDVEZwb7PBsJ14=
From: Mukund Sivaraman <muks@mukund.org>
To: Benno Overeinder <benno@nlnetlabs.nl>
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>
Message-ID: <YmxXZ/jQkwXODmy+@d1>
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> <aba0f124-8074-30f2-975e-525fb61ebc7e@NLnetLabs.nl>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="GmHToBrYYyGHCI+b"
Content-Disposition: inline
In-Reply-To: <aba0f124-8074-30f2-975e-525fb61ebc7e@NLnetLabs.nl>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/QMaXffb_n7e015uyJe2xYO-rRbo>
Subject: Re: [DNSOP] draft-hsyu-message-fragments replacement status updated by Cindy Morgan
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Apr 2022 21:24:02 -0000

On Fri, Apr 29, 2022 at 10:54:13PM +0200, Benno Overeinder wrote:
> 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.

OK, I think I have misunderstood the last 2 emails in this thread.

> 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.

That sounds good. I browsed through Carpenter's draft. Section 7 in it
is about how to fork (which is welcome), and it sounds reasonable.

		Mukund