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

Donald Eastlake <d3e3e3@gmail.com> Thu, 28 April 2022 18:16 UTC

Return-Path: <d3e3e3@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 B4648C157B40; Thu, 28 Apr 2022 11:16:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level:
X-Spam-Status: No, score=-1.847 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 BX24iw13oJlH; Thu, 28 Apr 2022 11:16:30 -0700 (PDT)
Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) (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 0D3B8C157B35; Thu, 28 Apr 2022 11:16:30 -0700 (PDT)
Received: by mail-lf1-x12b.google.com with SMTP id k12so10052397lfr.9; Thu, 28 Apr 2022 11:16:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ulFYp/GBYAzmRjx/qiRNsLP75aEJIuWrJVfJbOHNRT0=; b=fqwPW3xoAJWWi9rTA7CaA9y34Rph2ytmpXW1+r6aKi0aWp2atQIJreev/kvhOra+Lp up3Ov5KFvfMrG/MLSIc05awDvhnASpQ5SBUODFtPJiopOb0FlPF2QUOuvHAJW/SyDwOO u0j1zQAkMjYNsr8OjVQlXr0Ys3txrZPWKUawjSeTnTgqn7jmDgDjow5Li8lujCh8miQT INcKJxf4H6ri2u2oH3cgHThQalS7vgej+ns4OwueS/+egLySOCmpuX7C9frMQ7FhTRcr 5ZXBVo2H3ZfqBd8beYOY6lwU6dSGq+lbV9AfdV0gCP7TaJYugpMbu2eX9Z2lhMdzL2KM ZWSQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ulFYp/GBYAzmRjx/qiRNsLP75aEJIuWrJVfJbOHNRT0=; b=TLVDKtidbhjeKIh9CPYUvT1fS/ezrKSBCBIstxODcKykbUMa/xipCYno6opt1LRsnU leX/FL2ZglN1mBmilyrS12zRGPBWz4t03pR5C5v/TlipI9lY097M3KofW8UHCKny17l3 2CJDw1xq9rd/FIzdDikkyGoxfePzoRj/iy02oKvkveNNV6J9vwN5ZknzFIx6lWiv8Lv+ T5tWOEnD9ATVX+wRIOHhbVB2cYjllPdQiYOteIL661vKDC3SFVgV/XjylyazfiDMa3+M RvRhFa2nBzzuQuoFAqaxESoij2DHwJW1d+Om5Efcuf3M2THOYaacaWHPJg+BCBS/s1c9 w9xg==
X-Gm-Message-State: AOAM533h0fNaX8YirL97uqmkVoxQDsWxnX1fI1RZiGabSDon0vMKgKXa Cjj0iyP+lu/fW+ZGzTxuLsjdt85yE88pa6LMBorUrBii+0U=
X-Google-Smtp-Source: ABdhPJxpxtCqUECkyVVMMgw8rEEafvd9epgqDpfng2qgYoz97eezbGwnF11NqReOM1DjdQtf+xttaIUx7ozkk/VDvbs=
X-Received: by 2002:a05:6512:22c1:b0:46b:a2b7:2edd with SMTP id g1-20020a05651222c100b0046ba2b72eddmr26096401lfu.133.1651169787600; Thu, 28 Apr 2022 11:16:27 -0700 (PDT)
MIME-Version: 1.0
References: <165116358815.5877.9244565954759130167@ietfa.amsl.com> <YmrKSN5OSQh2/SQf@d1>
In-Reply-To: <YmrKSN5OSQh2/SQf@d1>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 28 Apr 2022 14:16:16 -0400
Message-ID: <CAF4+nEE0AJSjUfYXLjxUE94k544k_cK2v7HxNRS1XmSVOnQRPg@mail.gmail.com>
To: Mukund Sivaraman <muks@mukund.org>
Cc: shane@time-travellers.org, IETF Discussion <ietf@ietf.org>, "<dnsop@ietf.org>" <dnsop@ietf.org>, yliu@cfiec.net, hsyu@cfiec.net, hsyu@biigroup.cn, Cindy Morgan <cmorgan@amsl.com>
Content-Type: multipart/alternative; boundary="000000000000a763c705ddbaec2d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/2pSbz6JZ2z9GpQkIjv8Ff61FhmU>
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 18:16:30 -0000

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/) 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


On Thu, Apr 28, 2022 at 1:10 PM Mukund Sivaraman <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/
> >
> > 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
>