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

Mukund Sivaraman <muks@mukund.org> Sun, 01 May 2022 06:26 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 786ACC15948F; Sat, 30 Apr 2022 23:26:43 -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 FhW71EQ4-MS9; Sat, 30 Apr 2022 23:26:39 -0700 (PDT)
Received: from mx.mukund.org (mx.mukund.org [144.76.148.120]) (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 5F83BC157B55; Sat, 30 Apr 2022 23:26:37 -0700 (PDT)
Date: Sun, 01 May 2022 11:56:30 +0530
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mukund.org; s=mail; t=1651386395; bh=jrESgaaSj5LW7sQ1v2pkCqxdaPwKuYTG9b59NoMiCoo=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=k5FaGXzCZq1UwL/C7h2E2Th9s68LMirq5diyYktwbMfImW9HNQ7LeSdvqlr3obIED xHU8Fz4/rJvc9X6gnT8ZTwq4vGP5SA1qX6X6Pbacc0YYnj8nToemcaqPf+5EvyioQI vbcepLlpdjnweHb5PQJpPt/KGeCc+IfDmBPWP7oQ=
From: Mukund Sivaraman <muks@mukund.org>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Benno Overeinder <benno@nlnetlabs.nl>, Shane Kerr <shane@time-travellers.org>, DNSOP WG Chairs <dnsop-chairs@ietf.org>, IETF Discussion <ietf@ietf.org>, DNSOP Working Group <dnsop@ietf.org>, yliu@cfiec.net, hsyu@cfiec.net, hsyu@biigroup.cn, Cindy Morgan <cmorgan@amsl.com>
Message-ID: <Ym4oFmDzYFz1JRkV@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> <978fef52-c6d8-7f97-9ec3-75ca7dad0f46@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="R/gnNY653FEa+wLD"
Content-Disposition: inline
In-Reply-To: <978fef52-c6d8-7f97-9ec3-75ca7dad0f46@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/HAzdEbd4h4q9Y53OXZ1utGrrbH4>
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: Sun, 01 May 2022 06:26:43 -0000

Hi Brian

On Sun, May 01, 2022 at 02:11:11PM +1200, Brian E Carpenter wrote:
[snip]
> > The copyright notice on the document says:
> > 
> >     Copyright (c) 2022 IETF Trust and the persons identified as the
> >     document authors.  All rights reserved.
> > 
> > By way of this, by removing the names of authors, isn't the copyright
> > notice attributed to the (original) document authors also being removed?
> 
> I am not a lawyer, but I believe it's true that *nobody* can remove the
> original authors' copyright (although the details might differ in each
> country's laws). However, the point here is that when an IETF I-D is
> submitted, it is done so under the IETF's conditions, including the
> IETF's right to produce "derivative works". The details are in BCP98
> (RFC5378) and in the IETF Trust's Legal Provisions, but basically it
> means that the text can be re-used in future IETF drafts and RFCs.

The permission to modify and/or redistribute is not being
questioned. It's the removal of authors, and what appears to be removal
of copyright attribution also. Your draft's text sounds reasonable on
this topic.

> > Clearly the text is not copyright of the new authors in this document:
> 
> I wonder if the conventional sentence "Copyright (c) 2022 IETF Trust and
> the persons identified as the document authors" needs to be tuned to
> also cover previous authors when the authorship team for a draft changes?
> But that question is for the IETF Trust and its lawyer.

Nod, this has to be examined.

		Mukund