Re: The RFC Acknowledgement
Eric Burger <eburger-l@standardstrack.com> Sat, 09 February 2013 12:13 UTC
Return-Path: <eburger-l@standardstrack.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 723A521F86C3 for <ietf@ietfa.amsl.com>; Sat, 9 Feb 2013 04:13:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2nCFJv6+B--Y for <ietf@ietfa.amsl.com>; Sat, 9 Feb 2013 04:13:04 -0800 (PST)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.215.15]) by ietfa.amsl.com (Postfix) with ESMTP id 9C14221F85D7 for <ietf@ietf.org>; Sat, 9 Feb 2013 04:13:04 -0800 (PST)
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8]:53317 helo=[192.168.15.177]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80) (envelope-from <eburger-l@standardstrack.com>) id 1U49Ia-0004aL-LN; Sat, 09 Feb 2013 04:12:52 -0800
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: The RFC Acknowledgement
From: Eric Burger <eburger-l@standardstrack.com>
In-Reply-To: <CADnDZ8_E-cDqhXWV-f3MjoDo9hFeCVAdVTmRQ+McA--_3smyJQ@mail.gmail.com>
Date: Sat, 09 Feb 2013 07:13:05 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <3EDB772E-A3FE-403C-B5EE-2ED69F7FDDBA@standardstrack.com>
References: <CADnDZ8_E-cDqhXWV-f3MjoDo9hFeCVAdVTmRQ+McA--_3smyJQ@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
X-Mailer: Apple Mail (2.1499)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source:
X-Source-Args:
X-Source-Dir:
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: Sat, 09 Feb 2013 12:13:05 -0000
Abduussalam - You probably have seen many responses to your message talking about who goes into the Acknowledgements section. However, I am not sure your original question was answered. In short, it is the document editor that puts the acknowledgments section in. In most cases it will be obvious who gets listed there. That is the substance of the other messages on this thread. In rare cases a work group chair may get involved. As you are new, if you are a document editor, you can always ask your work group chair for guidance. Conversely, if you feel you should be in an acknowledgements section for your contributions, feel free to talk with the document editor (first) and work group chair (second) - Eric On Feb 8, 2013, at 10:11 PM, Abdussalam Baryun <abdussalambaryun@gmail.com> wrote: > Hi folks, > > I am wondering how author/ietf-editor fill in the acknowledgement > section in the RFCs or I-Ds. Does it make sense in IETF, or left for > author opinion? I am getting requests from IETF WGs, IESG, and IAB for > comments. My question is do you *make acknowledgements* in I-Ds or > just *take comments* for I-Ds? > > IMO we get last call request for comments because RFC production is > all about getting volunteering comments from Internet community to > make I-Ds better, so does all I-Ds acknowledge (ACK) to any input > comment before the last call and after or it is only before last > call?, and if it gets submitted to IESG/IAB, and we comment does that > have no ACK in I-D? > > I sometimes feel discouraged to participate in any world work if the > process does not involve my existance, just used with ignoring ACK of > the reviewers. IMO any comment has value to the authors (e.g. some > think only experts' comments are important to ACK) and to IETF, > otherwise, we may delete valuable ACKs in IETF, which is not right. > > Best Regards > > AB > A participant that still did not complete a year working for IETF, but > trying to continue :)
- Re: The RFC Acknowledgement Melinda Shore
- The RFC Acknowledgement Abdussalam Baryun
- Re: The RFC Acknowledgement Donald Eastlake
- Re: The RFC Acknowledgement John C Klensin
- Re: The RFC Acknowledgement Abdussalam Baryun
- Re: The RFC Acknowledgement ned+ietf
- Re: The RFC Acknowledgement Melinda Shore
- Re: The RFC Acknowledgement Fred Baker (fred)
- Re: The RFC Acknowledgement Brian E Carpenter
- Re: The RFC Acknowledgement Eric Burger
- Re: The RFC Acknowledgement Dale R. Worley
- Re: The RFC Acknowledgement Abdussalam Baryun
- Re: The RFC Acknowledgement Barry Leiba
- Re: The RFC Acknowledgement Hector Santos
- Re: The RFC Acknowledgement Michael StJohns
- Re: The RFC Acknowledgement Abdussalam Baryun
- Re: The RFC Acknowledgement Dean Willis
- Re: The RFC Acknowledgement SM
- Re: The RFC Acknowledgement Bradner, Scott
- Re: The RFC Acknowledgement Ulrich Herberg
- Re: The RFC Acknowledgement Barry Leiba
- Re: The RFC Acknowledgement Abdussalam Baryun
- Re: The RFC Acknowledgement Ulrich Herberg
- Re: The RFC Acknowledgement joel jaeggli
- Re: The RFC Acknowledgement Abdussalam Baryun
- Re: The RFC Acknowledgement joel jaeggli
- Re: The RFC Acknowledgement (off-topic) SM
- Re: The RFC Acknowledgement (off-topic) Ulrich Herberg
- Re: The RFC Acknowledgement Bob Hinden