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

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 28 April 2022 20:01 UTC

Return-Path: <brian.e.carpenter@gmail.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 0155EC1594AF; Thu, 28 Apr 2022 13:01:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.955
X-Spam-Level:
X-Spam-Status: No, score=-2.955 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, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, NICE_REPLY_A=-1.857, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 YRpvqBGXWp4x; Thu, 28 Apr 2022 13:01:49 -0700 (PDT)
Received: from mail-pl1-x632.google.com (mail-pl1-x632.google.com [IPv6:2607:f8b0:4864:20::632]) (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 4680DC157B45; Thu, 28 Apr 2022 13:01:49 -0700 (PDT)
Received: by mail-pl1-x632.google.com with SMTP id n8so5312367plh.1; Thu, 28 Apr 2022 13:01:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=Duwf9dSeJvoh2L8u7rB7ytZmEGfE2JSPQwLEXWaroNs=; b=Aup2e1IujR9G5bDcFzsWHDV1ew0DEU60wW33n/fJ6w+GE1MMkmElBc2tvxL5o5Pu/w iuiyTeIpe2MzOCHvKWfoIj4vD9Tk9hzg5AUfUKJPwqQ7YlDBU78PsmH8NrR71z3iAJVq Al2HPcRi+G2v5Q09Oia4lPW1GyQC+vuS8hDdxBtLP59Ppy9ienp3DwDQf1diUz9eewRV a4G+F3hd0PnirPZ/C2EqvCRxQpx5KzyxPedYw+zCliXG75NX17QAkBOuy4VcJ++klSt8 Bv84e8l7sYxZg+wfXgc/c04DnOBVLqji2I/nRKhHTIrm38y1InutVdVwWCd5b9K6uGax ayhA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=Duwf9dSeJvoh2L8u7rB7ytZmEGfE2JSPQwLEXWaroNs=; b=Sv+WjmGHFDEcNLVkGgoDbOTzVXisLymuCdIYdMuVkGeoYez2iVp6X9qZ/Z/FJOJJJM p748z3rayP3ga6nZJICQM0mkAnYvdcaOIWQ5pyaWR6EgMs+J+o+blQ2XJP6XL2sakXCa uhZqg2WKX3Yq5S5cUGMpXe0ldaFyLCzizqCYoaoGEkVJ7O4MVBIDsy8wlu6vHHBves3O OccZolnyzR+wIzjzTGllFwFxghrtSevytSzVbPTwZpelRTVP8gKcZY3k3YBEaJxOtWzN 7Ba/pa1jNt7R+DznYrq3ZgtRWo8tVpOfb0Vxw5sKEA4cIwJ1xi9P08dz8tNeaVR0YbJ/ ZKJg==
X-Gm-Message-State: AOAM531VxHQRxiIjAndNyIo7usXCLPsXA3j8u5KNovS2TVbR0gLXWUZx Y0LfLd3vP65/pVJ8q16TvFA=
X-Google-Smtp-Source: ABdhPJy0KbJ7wxM2pyDKRBQWZHjHbbEeN98GvhnC9VSf7RsEzcqC9ciPxbhHaUuiECkleJPzJqdZGA==
X-Received: by 2002:a17:902:a987:b0:158:b020:e5b8 with SMTP id bh7-20020a170902a98700b00158b020e5b8mr35348800plb.103.1651176108354; Thu, 28 Apr 2022 13:01:48 -0700 (PDT)
Received: from ?IPv6:2406:e003:1005:b501:80b2:5c79:2266:e431? ([2406:e003:1005:b501:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id k10-20020a056a00168a00b004f7e2a550ccsm631891pfc.78.2022.04.28.13.01.44 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 28 Apr 2022 13:01:47 -0700 (PDT)
To: Donald Eastlake <d3e3e3@gmail.com>, Mukund Sivaraman <muks@mukund.org>
Cc: shane@time-travellers.org, IETF Discussion <ietf@ietf.org>, dnsop@ietf.org, yliu@cfiec.net, hsyu@cfiec.net, hsyu@biigroup.cn, Cindy Morgan <cmorgan@amsl.com>
References: <165116358815.5877.9244565954759130167@ietfa.amsl.com> <YmrKSN5OSQh2/SQf@d1> <CAF4+nEE0AJSjUfYXLjxUE94k544k_cK2v7HxNRS1XmSVOnQRPg@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <fecf521f-cf04-4b6a-7e72-93c607f93ae7@gmail.com>
Date: Fri, 29 Apr 2022 08:01:42 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <CAF4+nEE0AJSjUfYXLjxUE94k544k_cK2v7HxNRS1XmSVOnQRPg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/3dV5NeN7FSvsl8c3V5gDsbW59mY>
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: Thu, 28 Apr 2022 20:01:53 -0000

There was https://datatracker.ietf.org/doc/html/draft-carpenter-whats-an-author-02

My hope is to revive that draft as an RFC Editor policy issue once the RSWG is established, because it's broader than just an IETF issue.

Regards
    Brian Carpenter

On 29-Apr-22 06:16, Donald Eastlake wrote:
> What you describe is completely improper but I'm not sure it's exactly accurate. When you said you were "removed" as an author, I assumed that a 
new revision of a draft was posted where you were a first page author for 
version N but not listed as an author for version N+1. That would also be 
improper if there was no effort to consult with you.
> 
> But what seems to have happened is that a new draft was created with you omitted from the author list and (given the reference to Cindy Morgan in the Subject line), the Secretariat was asked to record this new draft as replacing the previous draft where you were an author (indeed, the first listed author). I think this sort of thing is extremely rare. You could certainly ask the Secretariat to reverse the database update so your draft (https://datatracker.ietf.org/doc/draft-muks-dnsop-message-fragments/ <https://datatracker.ietf.org/doc/draft-muks-dnsop-message-fragments/>) is no longer shown as being replaced by any other draft.
> 
> Thanks,
> Donald
> ===============================
>   Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>   2386 Panoramic Circle, Apopka, FL 32703 USA
> d3e3e3@gmail.com <mailto:d3e3e3@gmail.com>
> 
> 
> On Thu, Apr 28, 2022 at 1:10 PM Mukund Sivaraman <muks@mukund.org <mailto:muks@mukund.org>> wrote:
> 
>     On Thu, Apr 28, 2022 at 09:33:08AM -0700, DraftTracker Mail System wrote:
>      >
>      > Please DO NOT reply to this email.
>      >
>      > I-D: <draft-hsyu-message-fragments-00.txt>
>      > Datatracker URL: https://datatracker.ietf.org/doc/draft-hsyu-message-fragments/ <https://datatracker.ietf.org/doc/draft-hsyu-message-fragments/>
>      >
>      > This document now replaces draft-muks-dnsop-message-fragments
>      >     draft-hsyu-dnsop-message-fragments instead of 
draft-hsyu-dnsop-message-fragments
> 
>     This is the second time in recent years that, in a DNS draft I'd
>     primarily authored, I've noticed my name was removed from the list of
>     authors with no prior consultation with the document mostly the same.
> 
>     I understand that we assign co-copyright to the IETF when publishing
>     drafts, but it feels unreasonable that after effort is put in writing a
>     draft, the authorship is completely deleted. In the previous case, I was
>     moved to "Acknowledgements" without consultation, and in this case my
>     name has been deleted fully.
> 
>     New author(s) who want to take over could instead:
> 
>     * Ask to be co-author(s).
> 
>     * Say that they'd leave the original author(s) as-is, but that they
>        would like to have control over the draft's future, and if the old
>        author(s) don't like it, they may ask to be deleted.
> 
>     * If content were significantly modified, they could say "This draft is
>        significantly different from your old draft, and so we'd like to claim
>        full ownership, is that OK?".
> 
>     Instead, what happened with both drafts is akin to taking a book that's
>     mostly written by one author, contributing a few sentences, and deleting
>     the previous authors' names and calling it your own.
> 
>                      Mukund
>