Re: On the tradition of I-D "Acknowledgements" sections

"Joel M. Halpern" <jmh@joelhalpern.com> Mon, 25 March 2013 02:23 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBC6F21F8C49 for <ietf@ietfa.amsl.com>; Sun, 24 Mar 2013 19:23:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.507
X-Spam-Level:
X-Spam-Status: No, score=-102.507 tagged_above=-999 required=5 tests=[AWL=0.092, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WyrTnleneeEM for <ietf@ietfa.amsl.com>; Sun, 24 Mar 2013 19:23:31 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by ietfa.amsl.com (Postfix) with ESMTP id 8023021F8BCF for <ietf@ietf.org>; Sun, 24 Mar 2013 19:23:31 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 566F7240042; Sun, 24 Mar 2013 19:23:31 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [10.10.10.104] (pool-70-106-135-233.clppva.east.verizon.net [70.106.135.233]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 5A577240044; Sun, 24 Mar 2013 19:23:28 -0700 (PDT)
Message-ID: <514FB516.6050702@joelhalpern.com>
Date: Sun, 24 Mar 2013 22:23:18 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: On the tradition of I-D "Acknowledgements" sections
References: <20130320104353.27601.24590.idtracker@ietfa.amsl.com> <76F7932F-CABE-4825-80DB-461E95288402@jiaziyi.com> <CADnDZ89mBrJAHQOHegSXFacC_DHSn5R34BpMtbkQ1qjOF+vZYA@mail.gmail.com> <1227E12F-9593-4A8C-A54D-B210A61060D2@jiaziyi.com> <CADnDZ8-NN0pWh5WuoJg3Jmgw_MtLpw51mrhiW2=P8i8hXJoL0g@mail.gmail.com> <5E51EF77-3D8E-4D22-A753-329CEB53CD59@istaff.org> <6.2.5.6.2.20130324123511.0abd0878@resistor.net> <CADnDZ893B70g3i0rTTiy6JMH26SVkwyZwGS9vhY8DqEn0CU8NA@mail.gmail.com> <CADnDZ88Gs1VvvpEsEoPyMLyHV1JeTWVXtsfs4NgYrncCdvjZ7Q@mail.gmail.com>
In-Reply-To: <CADnDZ88Gs1VvvpEsEoPyMLyHV1JeTWVXtsfs4NgYrncCdvjZ7Q@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Mar 2013 02:23:32 -0000

I think I at least partly disagree.  The acknowledgements section of 
RFCs was not, and to the best of my knowledge is not, concerned with 
capturing the history of where specific changes or ideas came from.  It 
ought to be concerned with giving credit to folks who made particularly 
large, but not authorship level, contributions to the document.

I have seen I-Ds which included change logs which made an effort to 
capture the major changes to a document and their cause.  these were, at 
best, ungainly.  And are, as far as I know, always removed before 
publicaiton as an RFC.

Yours,
Joel

On 3/24/2013 8:55 PM, Abdussalam Baryun wrote:
>   Just to make things clear that the intention of documents
> acknowledging is to reflect the truth of any document process and
> connect information or resources. IMHO, it is not the purpose to show
> credit to any person including authors, it is to show how changes were
> developed and show true document-history.
>
>   So when I read a RFC I may go through the document process and its
> draft versions, while going through the drafts related I see
> acknowledged names so I may find the input on the list for such name.
> In this way we have connections between inputs otherwise the IETF
> system has no connection between its important information.
>
> AB
>