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

[Brian E Carpenter <[e-mail]>]

Hi Mukund, two comments below...

On 30-Apr-22 08:27, Mukund Sivaraman wrote:
> On Fri, Apr 29, 2022 at 10:05:10PM +0200, Benno Overeinder wrote:
>> Hi Lars, WG,
>>
>> On 29/04/2022 12:54, Lars Eggert wrote:
>>> On 2022-4-29, at 0:30, Cindy Morgan <[e-mail]> wrote:
>>>> The rest of this is a bit of a tangle, and I've referred it to the IESG for further guidance on what steps the Secretariat should take next.
>>>
>>> the IESG is reviewing what has happened.
>>>
>>> (My personal first impression is that this might be a case where a contributor intended to revive an expired document by a different set of authors, and was unsure how to best go about this.)
>>
>> 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?
> 
> The fact that the document is expired or not is a different matter.
> 
> 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.

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

Regards
    Brian

> 
> https://www.ietf.org/archive/id/draft-hsyu-message-fragments-00.txt
> 
> 		Mukund
>