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

Michael StJohns <msj@nthpermutation.com> Mon, 02 May 2022 02:38 UTC

Return-Path: <msj@nthpermutation.com>
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 2EB06C14F727 for <dnsop@ietfa.amsl.com>; Sun, 1 May 2022 19:38:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.751
X-Spam-Level:
X-Spam-Status: No, score=-3.751 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-1.857, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 (2048-bit key) header.d=nthpermutation-com.20210112.gappssmtp.com
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 1sWQWvw_IHVC for <dnsop@ietfa.amsl.com>; Sun, 1 May 2022 19:38:22 -0700 (PDT)
Received: from mail-qt1-x830.google.com (mail-qt1-x830.google.com [IPv6:2607:f8b0:4864:20::830]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 77DDEC14F722 for <dnsop@ietf.org>; Sun, 1 May 2022 19:38:22 -0700 (PDT)
Received: by mail-qt1-x830.google.com with SMTP id x22so5196508qto.2 for <dnsop@ietf.org>; Sun, 01 May 2022 19:38:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nthpermutation-com.20210112.gappssmtp.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :references:from:in-reply-to:content-transfer-encoding; bh=YWPbw5eyAaVwvuzQkNAYc6heYXZ0c8VUN5BEWaUnoPE=; b=Y2D8Zkrz+xH4DIXlmcpNLtFM/xHLTKz89ERwWFEzN6L4+ShZF02NvftLUKCU3PEAgc bUDCAKQx24vccxdqnR/dhpo+3CLUxtxQk5iB/19agknzKK90Ua+jmO2krtNzi8bzbmdj jsRvhA/idT/hVNbAyQcjHKT0bzEsJ6sVRVIVd8UzzLo4L0gR9+9wlZlWWd0k8S/aQ3hu QA1B1lkFgFl2h9Es0/uU66FcrXBVBPfzhlLKxCZh8Qg2W4azhxsLSqTTLNE5c1+UPAA1 xku0MZIf/qrjtxSLg0/4R72OKrFXilDI2zXCYiWnsU+x4wnna6J6LLIFFggzKRHCzdEu wWwg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:references:from:in-reply-to :content-transfer-encoding; bh=YWPbw5eyAaVwvuzQkNAYc6heYXZ0c8VUN5BEWaUnoPE=; b=oN/CqXEra74DLPlfIJxLHSCBktAbgBd5g3eDtfNz9hJnX4XwIh1mjMl9EdnwM4b6j4 hAh7AfhbfDJXeReWOtQ1/cNJ89VNj3zMJVyAw4do9zJ4aE7LZxOU1yOrjy6B3hCF8ugs +K3+cCMctCPz8c/Y48JOCKQ6tN8V7FaSldta25pw/B12dDXq60IouVvXSJDKfeiDSbjm IP/kzHjk0TWR8puGImLA4x8Jbl9LUuK32JvZKc3TzGeNtiqh9QVMZWhnoIpO+2Nc130m zc+q9nN1S5LzfAzfKozoeu5ju6BUdGAfdcHkglxE7dNW/XpMPEK7mUXs0rFFzxtJt6tK idrw==
X-Gm-Message-State: AOAM533qt46cvHydFa1q74X/334rZLmUPFdeK3ikAt1FEo9Oz2u7yYMb THd+uknQdRzaaPX/fky5EjkuMjTLr6SeOi7WLi8=
X-Google-Smtp-Source: ABdhPJwO9ROogI2VLeTlPF/uXw7Yr1hzdwGzPoOzykJxZTy30qT+Nl85BGs2M3hC5sP5k+GWqtvU+Q==
X-Received: by 2002:a05:622a:1993:b0:2f3:9657:8c74 with SMTP id u19-20020a05622a199300b002f396578c74mr8520518qtc.13.1651459100584; Sun, 01 May 2022 19:38:20 -0700 (PDT)
Received: from [192.168.1.23] (pool-108-51-200-187.washdc.fios.verizon.net. [108.51.200.187]) by smtp.gmail.com with ESMTPSA id i5-20020a37c205000000b0069fc13ce1d3sm3586589qkm.4.2022.05.01.19.38.19 for <dnsop@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 01 May 2022 19:38:19 -0700 (PDT)
Message-ID: <65a7c922-b75f-b653-e2c6-f33ce5181405@nthpermutation.com>
Date: Sun, 01 May 2022 22:38:18 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.8.1
Content-Language: en-US
To: dnsop@ietf.org
References: <20220501174147.EC0353F33EDF@ary.qy>
From: Michael StJohns <msj@nthpermutation.com>
In-Reply-To: <20220501174147.EC0353F33EDF@ary.qy>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/vkRQ9By1t65E1D-AutgddBRYxas>
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: Mon, 02 May 2022 02:38:23 -0000

In line:

On 5/1/2022 1:41 PM, John Levine wrote:
> It appears that Mukund Sivaraman  <muks@mukund.org> said:
>>    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?
>>
>> Clearly the text is not copyright of the new authors in this document: ...

Actually, a derivative work (term of art) has a copyright that is 
distinct from the work from which it is derived.  In this case, the 
authors of the document are the authors for the purposes of copyright 
for the text in the document - regardless of where the text originates, 
and with the caveat for derivative works, that there is an appropriate 
license associated with the original work that allows for derivative 
works.  I could take the original document, change one word and the 
authors, publish it as an ID and, as long as I follow the license terms 
for derivative works, would be considered the author for copyright 
purposes of the new document.

> Hi, trustee of the IETF Trust here. With rare exceptions that don't apply here,
> when anyone submits an I-D or publishes an RFC, they grant a permanent license
> to let anyone use the material in later drafts or RFCs in the IETF process.
> There is no requirement for attribution or notice. We made that decision
> deliberately, so that new drafts and RFCs can build on old ones. It also happens
> that due to a treaty called the Berne Convention, the copyright notice on a
> document no longer has any legal meaning at all.

And that's where the license comes in.  For the referenced documents, 
unless the boilerplate explicitly disclaims the right to produce 
derivative works, anyone who wants can do so - as part of the IETF 
process.  So while I could publish an ID as above, I couldn't file off 
the serial numbers completely (i.e., submit this an original work in 
some space other than the IETF).

>
> While taking someone else's draft and putting your name on it as another draft
> is legal, that's not the question here. It's whether it's ethical and something
> we want to encourage. My impression is that in this case it was a
> misunderstanding and I hope it will be sorted out shortly.

The language of the license reads in part "Copyright (c) 2015 IETF Trust 
and persons identified as the document authors." There may be good - 
legal related - reasons to take off authors who didn't participate in 
the current document and remove them to an Acknowledgement section.  
IANAL, but I wonder not only about rights conferred by a copyright, but 
whether there are also responsibilities that someone may want to 
disclaim or at least explicitly agree to upon publication?

I expect that the IETF is going to have to make a "policy" to cover this.

Later, Mike

>
> R's,
> John
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop