Re: IESG Statement on surprised authors
Benoit Claise <bclaise@cisco.com> Sat, 30 May 2015 06:54 UTC
Return-Path: <bclaise@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D7711A92E7 for <ietf@ietfa.amsl.com>; Fri, 29 May 2015 23:54:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 WgscLUG8j0mQ for <ietf@ietfa.amsl.com>; Fri, 29 May 2015 23:54:39 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CAC781A92DD for <ietf@ietf.org>; Fri, 29 May 2015 23:54:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7434; q=dns/txt; s=iport; t=1432968878; x=1434178478; h=message-id:date:from:mime-version:to:subject:references: in-reply-to; bh=ed8Yqpfe2sdw5GISCDl1Y9SnbLUbQmoyVDuQ9YDMWBk=; b=F7ezj2RU0LdIruS+XNfEyDeAv7khUJ6Crrau5M1kmkZtITsoyM+vTfsH A2S8rZrHKQEXOnU4rTLWX24IU1/33vA3+5M2hKWUXmS0Nt0MPbDi9PUpK nM2NpT0uUxCfyI7gfkzTUpLfDQA9ImweNJ+HYxFnXto8tl08ExyzKq8wq Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CtAwB2XWlV/xbLJq1cg2ReviwJgVqFdwKBdRQBAQEBAQEBgQqEIwEBBIEJCxgJJQ8CRgYBDAYCAQGIKQ3UcAEBAQEBAQEDAQEBAQEBHItDhQ2ELQEElz+GXYFnhhGPOiNhgxk8MQGCRgEBAQ
X-IronPort-AV: E=Sophos;i="5.13,521,1427760000"; d="scan'208,217";a="498418384"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 30 May 2015 06:54:36 +0000
Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t4U6saU9030312; Sat, 30 May 2015 06:54:36 GMT
Message-ID: <55695EAC.80002@cisco.com>
Date: Sat, 30 May 2015 08:54:36 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
Subject: Re: IESG Statement on surprised authors
References: <20150529205551.22495.73800.idtracker@ietfa.amsl.com> <2F99A0C05DFEE698A643FC97@JcK-HP8200.jck.com>
In-Reply-To: <2F99A0C05DFEE698A643FC97@JcK-HP8200.jck.com>
Content-Type: multipart/alternative; boundary="------------050004070506030207000706"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/mHR64by9GReew2jyWhEfl7CUQEg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 May 2015 06:54:41 -0000
John, One reason why a pointer to the surprised acknowledgment was added is for statements such as Thanks to <insert names> for their valuable comments and support on the initial idea of this document Regards, Benoit > > --On Friday, May 29, 2015 13:55 -0700 IESG Secretary > <iesg-secretary@ietf.org> wrote: > >> The IESG is planning to publish an IESG statement concerning >> the authorship of Internet drafts. This statement is only >> focused on the situation where an IETF participant feels >> he/she has been erroneously listed as an author on a draft. >> The statement can be seen here: >> >> http://trac.tools.ietf.org/group/iesg/trac/wiki/SurprisedAutho >> rs > Hi. > > I hope this does not turn into a long discussion, but I believe > the parenthetical note about "surprised acknowledgment" either > needs to be removed (since this statement isn't really about it > and does not provide a remedy, default or otherwise) or > clarified. Acknowledgments raise several issues that have > caused controversy in the past. In summary, our IPR policies > are usually interpreted as requiring acknowledgment when someone > has made a significant Contribution to a document [1]. Those > policies are about Contributions, not about whether someone > agrees with all, part, or none of the resulting document. > Certainly an acknowledgment should not claim endorsement or > support for a document that the person involved does not > support, but the presumed requirement to acknowledge > Contributions may not allow a Contributor to opt out entirely > from being acknowledged. > > My sense is that we have not been consistent about resolution of > cases in which people have objected to having their > Contributions acknowledged in a document that they do not > support. If this statement is going to address the "surprised" > acknowledgment issue [2], it is going to be necessary to > establish policy in that area, policy that may require opening > and either clarifying our fundamental IPR policies and the RFC > Editor's interpretation of them or trying to produce a detailed > policy on acknowledgments [3]. > > best, > john > > > > [1] There have also been controversies associated with people > not being acknowledged who think they should be. Those > controversies and associated questions do not appear to interact > with this proposed statement. > > [2] I believe that "surprised acknowledgments" are > indistinguishable in practice from "unwanted" ones. With both > acknowledgments and authorship, if actual editors notify the > offended party in advance about what they are going to do and > that party objects, the same issues exist whether there is > actual surprise or not. > > [3] Personally, I would discourage the latter in favor of > continued reliance on author discretion, discussion within WGs, > etc., and application of courtesy and good sense. Trying to > formulate a specific policy would probably take us on a tour of > ratholes and special cases and end up satisfying no one and > leaving other cases unresolved. > > . >
- Re: IESG Statement on surprised authors Toerless Eckert
- Re: IESG Statement on surprised authors John C Klensin
- Re: IESG Statement on surprised authors Jari Arkko
- Re: IESG Statement on surprised authors joel jaeggli
- Re: IESG Statement on surprised authors Brian E Carpenter
- Re: IESG Statement on surprised authors John C Klensin
- Re: IESG Statement on surprised authors Eliot Lear
- Re: IESG Statement on surprised authors Benoit Claise
- Re: IESG Statement on surprised authors Carsten Bormann
- Re: IESG Statement on surprised authors Spencer Dawkins at IETF
- Re: IESG Statement on surprised authors John C Klensin
- Re: IESG Statement on surprised authors Benoit Claise
- Re: IESG Statement on surprised authors John C Klensin
- Re: IESG Statement on surprised authors Harald Alvestrand
- Re: IESG Statement on surprised authors David Farmer
- Re: IESG Statement on surprised authors John C Klensin
- Re: IESG Statement on surprised authors Brian E Carpenter
- Re: IESG Statement on surprised authors Spencer Dawkins at IETF
- Re: IESG Statement on surprised authors John C Klensin
- Re: IESG Statement on surprised authors Eliot Lear
- Re: IESG Statement on surprised authors Eliot Lear
- Re: IESG Statement on surprised authors Harald Alvestrand
- Re: IESG Statement on surprised authors Larry Kreeger (kreeger)
- Re: IESG Statement on surprised authors Alexandru Petrescu
- Re: IESG Statement on surprised authors Eliot Lear
- Re: IESG Statement on surprised authors John C Klensin
- Re: IESG Statement on surprised authors John C Klensin
- Re: IESG Statement on surprised authors John Levine
- Re: IESG Statement on surprised authors Melinda Shore
- Re: IESG Statement on surprised authors Melinda Shore
- Re: IESG Statement on surprised authors John C Klensin
- Re: IESG Statement on surprised authors Spencer Dawkins at IETF
- Re: IESG Statement on surprised authors Randy Bush
- Re: IESG Statement on surprised authors Spencer Dawkins at IETF
- Re: IESG Statement on surprised authors Brian E Carpenter
- Re: IESG Statement on surprised authors John Levine
- Re: IESG Statement on surprised authors Ted Lemon
- Re: IESG Statement on surprised authors John R Levine
- Re: IESG Statement on surprised authors S Moonesamy
- Re: IESG Statement on surprised authors Larry Kreeger (kreeger)
- Re: IESG Statement on surprised authors Larry Kreeger (kreeger)
- Re: IESG Statement on surprised authors Larry Kreeger (kreeger)
- Re: IESG Statement on surprised authors Larry Kreeger (kreeger)
- Re: IESG Statement on surprised authors Joe Abley
- RE: IESG Statement on surprised authors Tony Hain
- Re: IESG Statement on surprised authors Ted Lemon
- Re: IESG Statement on surprised authors John Levine
- RE: IESG Statement on surprised authors Tony Hain
- Re: IESG Statement on surprised authors Warren Kumari
- Re: IESG Statement on surprised authors Ted Lemon
- Re: IESG Statement on surprised authors Warren Kumari
- Re: IESG Statement on surprised authors Stewart Bryant
- Re: IESG Statement on surprised authors Loa Andersson
- Re: proposed surprise hack, was IESG Statement on… John Levine
- Re: proposed surprise hack, was IESG Statement on… Ted Lemon
- Re: proposed surprise hack, was IESG Statement on… Warren Kumari
- Re: proposed surprise hack, was IESG Statement on… John R Levine