Re: Status of <draft-ietf-6man-default-iids-16.txt> in AUTH48

Alissa Cooper <alissa@cooperw.in> Mon, 13 February 2017 02:43 UTC

Return-Path: <alissa@cooperw.in>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 730AF129527 for <ipv6@ietfa.amsl.com>; Sun, 12 Feb 2017 18:43:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level:
X-Spam-Status: No, score=-2.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cooperw.in header.b=b4FtpJYy; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=YFxTzO8J
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GUllRpTkTiNT for <ipv6@ietfa.amsl.com>; Sun, 12 Feb 2017 18:42:59 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D3091294E4 for <ipv6@ietf.org>; Sun, 12 Feb 2017 18:42:59 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 47B662069A; Sun, 12 Feb 2017 21:42:56 -0500 (EST)
Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Sun, 12 Feb 2017 21:42:56 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=aB+QifJcilPmN8Q PI78hESotX8k=; b=b4FtpJYyrm0AJ1Q3XFC2LYBCrmh5wShaw1tCL6Jq07eSTDx u0jbDE4ba1nQxa1/YtNSP/YWadsE6kDMxdJGjIWd41pPQX7PjV2l5SNA/r5OtZis wdGmE2BptT+ayfS95LFis0PUnQ41U3ZfNkyI+YdnKQSnv0RfV5eCrA+SkoX4=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= smtpout; bh=aB+QifJcilPmN8QPI78hESotX8k=; b=YFxTzO8JX/NGdjralHNm 8XuSQRZfFFab2wZD6BgKG6hI3kh2jCjhGcVitovdTOHrkMZRrIqHy6Nckp622qAm +aK6WrHYGTdAOuelkr13YHspNaj540T39m03J8ML0kDT2ZzJCBmVxB3ugD4/ziEd ks31g9lLwc4vOcS+Ns1B3ZE=
X-ME-Sender: <xms:MB2hWITHgAZ2ffvbtI5sf3jSiUgm1AJtuKMSB29jJss8zT2OqQjg5w>
X-Sasl-enc: IYx3xrW1K5kBTTcfcNe/NfhdVn33cwkZwI415cUy9KyS 1486953774
Received: from [10.24.0.65] (unknown [128.107.241.169]) by mail.messagingengine.com (Postfix) with ESMTPA id 9245A241BC; Sun, 12 Feb 2017 21:42:51 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Status of <draft-ietf-6man-default-iids-16.txt> in AUTH48
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <C9FDAEB9-9F79-4186-9C48-5F44E5E07235@gmail.com>
Date: Sun, 12 Feb 2017 21:42:42 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <980BD16B-DAFD-4B1B-B36E-436DD4A8CA07@cooperw.in>
References: <C9FDAEB9-9F79-4186-9C48-5F44E5E07235@gmail.com>
To: Bob Hinden <bob.hinden@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/r3myxZaACPylj06lxWN3A808Xz8>
Cc: IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 02:43:01 -0000

Hi,

I had been refraining from commenting on this so that the rest of the WG could have a chance to do so without hearing from the authors, but at this point I feel it’s probably better to represent my own line of thinking on this. Here are the relevant excerpts from my messages to the rest of the authors and document approval chain during AUTH48:

   Message 1:

> I don’t believe thanking family members is an appropriate addition to the Acknowledgments during AUTH48. If this text had been in the document when it was still up for IETF consensus, we could have had a proper discussion with the full community about whether we want to start adding family member acknowledgments to RFCs. But that didn’t happen, so it’s not appropriate to add this text now. I think there is a long-standing precedent that Acknowledgments is a place to recognize people who made technical or editorial contributions or who reviewed the document for technical content or editorial style, or to provide transparency about where authors’ funding comes from if that is not otherwise clear.

   Message 2:

> My main objection to this text is that it was added during AUTH48. Since RFCs are consensus documents of the IETF, I think it’s important for the community to have the opportunity to review the substantive content of the document before it gets approved. I think the content you added is substantive in that it can set a precedent for what gets published in the RFC series going forward. I don’t recall previously seeing a standards track RFC where individuals are acknowledged for their love of the author. If you have examples, please share them.

> 
> If this text had been added prior to the document’s approval, I would have argued during community discussion that it makes me uncomfortable as a co-author to have people thanked in the document for their love. As I said before, I think the scope of acknowledgments is more limited than that, and by having you thank people for their love it raises the question of why I am not doing the same, or conversely it puts the burden on me to have to explain to the people who love me why I am not acknowledging them in this document. That is not a predicament that I care to be in as the author of an RFC. But we didn’t have that discussion with the community because the document is already approved.

Subsequent to sending message 2, I learned that this is at least the 10th document in which Fernando has inserted similar acknowledgment text during AUTH48. Those documents and the associated text are listed at the bottom of this message. The bulk of these documents were single-author documents, so no other IETF participant would have been alerted to the text prior to publication since it was not included in the versions of the documents that were put out for community review. Nor were they all working group documents, as default-iids is. But since to my eye this raises a novel question of editorial style for which the community has not provided guidance to the RFC Editor, I thought it would be important to surface it to the community in some way.

Of course, people in the WG and the community are free to disagree with any of the premises stated above — that this is a substantive change to the document content, that even non-technical content deserves community review, that what gets written in acknowledgments is not precedent-setting, that the existing precedent is what I think it is, etc. But I did not feel comfortable approving the document without having that discussion in the community. It was up to Suresh, Bob, and Ole to decide what to do from there. I will certainly go along with whatever the rough consensus ends up being.

Alissa

   ---

   1) RFC 6528:

   Fernando Gont wishes to thank Jorge Oscar Gont, Nelida Garcia, and
     Guillermo Gont for their love and support

   2) RFC 6633:

   Fernando Gont wishes to thank Jorge Oscar Gont, Nelida Garcia, and
     Guillermo Gont for their love and support.

   3) RFC 6946:

   Finally, the author wishes to thank Nelida Garcia and Guillermo Gont
     for their love and support.

   4) RFC 6980:

   Finally, the author would like to thank his brother, friend, and
     colleague, Guillermo Gont, for his love and support.

   5) RFC 7217:

   Finally, the author wishes to thank Nelida Garcia and Guillermo Gont
     for their love and support.

   6) RFC 7359:

   The author wishes to express deep and heartfelt gratitude to Enrique
     Garcia and Vicenta Tejedo, for their precious love and support.

   7) RFC 7739:

   The author would like to thank Buffy for her love and support.

   8) RFC 7872:

   Fernando Gont would like to thank Nelida Garcia and Guillermo Gont
     for their love and support.

   9) RFC 7943 (independent stream):

   Fernando Gont would like to thank Nelida Garcia and Guillermo Gont
     for their love and support, and Diego Armando Maradona for his magic
     and inspiration.