Re: IESG Statement on surprised authors

S Moonesamy <sm+ietf@elandsys.com> Mon, 01 June 2015 00:37 UTC

Return-Path: <sm@elandsys.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 DFDDD1A8913 for <ietf@ietfa.amsl.com>; Sun, 31 May 2015 17:37:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level:
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_RP_MATCHES_RCVD=-0.01] 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 naLLRYJvTXXS for <ietf@ietfa.amsl.com>; Sun, 31 May 2015 17:37:22 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id CA3B11A8912 for <ietf@ietf.org>; Sun, 31 May 2015 17:37:22 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.227.200.47]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id t510bBdJ009156 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Sun, 31 May 2015 17:37:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1433119042; x=1433205442; bh=iKAW6mMDPRxrP7ttTgA+GMycXO6hulgYlD03473SkG0=; h=Date:To:From:Subject:In-Reply-To:References; b=JAuf6EGz23q8gsFyZKYow8/w2ZlsnlOXquzHxEfkKFXkZTmxOOPBGGRRRakF1hoC6 Kymr/F4jIdS5YanV9BZF+ob2Spmbc2nHcugYraRNUvyj6waJH62PGtH/C44iBP9ONI KE5gzUMrMnKCMSjlWRKQNip+L2Ex1H0KAovAHglo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1433119042; x=1433205442; i=@elandsys.com; bh=iKAW6mMDPRxrP7ttTgA+GMycXO6hulgYlD03473SkG0=; h=Date:To:From:Subject:In-Reply-To:References; b=ENOmHvNbjie9JdCTnOnm2lKauLxPHdbmPzP5TzCXMq9dg6jZxWegnFRdX/OivSU4v 4uJKGOAcu+u8oUyfMWhXgzsTBkiGV8zZyS9bFKEUJoZYI4esPsyyx7Z5iuzncYp4AP ZLncuTmZx8g6iYxdgF07TL4DSg/Z3RO/cTGkF5KQ=
Message-Id: <6.2.5.6.2.20150531165129.0d5b5b78@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 31 May 2015 17:35:40 -0700
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: IESG Statement on surprised authors
In-Reply-To: <5568F568.9060407@bogus.com>
References: <20150529205551.22495.73800.idtracker@ietfa.amsl.com> <2F99A0C05DFEE698A643FC97@JcK-HP8200.jck.com> <938E070C-A69A-4D37-9B33-3CB07E09595C@piuha.net> <5568F568.9060407@bogus.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/IZIu5PREN0Bxhd8Gpq58CATgcoo>
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: Mon, 01 Jun 2015 00:37:24 -0000

At 16:25 29-05-2015, joel jaeggli wrote:
>Writing acknowledgments sections is largely a matter of editorial
>discretion, where good sense and general attribution practices are the
>primary guidelines, although RFC 2026 Section 10.3.1 has some specific
>rules regarding acknowledgment of major contributors, copyright, and IPR.

That section in RFC 2026 is no longer applicable.  The above might be 
covered by the following text in a BCP:

    "The Contribution properly acknowledges all Contributors, including
     Indirect Contributors."

The proposed "surprised authorship" statement covers:

   (a) Authorship

   (b) Acknowledgements

   (c) Contributor

   (d) Indirect Contributor

   (e) Ethics

   (f) IPR

It's better to withdraw a problematic Internet-Draft as if one of the 
listed authors has not agreed to "enter into [the] legally-binding 
agreement".  I suggest not issuing an IESG statement about this 
matter as it is not a document which the IETF will be publishing.  If 
the IESG would like to have a statement it might have to figure out 
whether it is a good idea to cover (a) to (f) in a statement.

Regards,
S. Moonesamy