Re: [rfc-i] acknowledging reviewers name in RFCs

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 31 May 2019 15:17 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BAAE120074 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 31 May 2019 08:17:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 mhA8P-tyZdOk for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 31 May 2019 08:17:51 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDB0C120052 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Fri, 31 May 2019 08:17:51 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 98821B80E53; Fri, 31 May 2019 08:17:46 -0700 (PDT)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id B46FAB80E53; Fri, 31 May 2019 08:17:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cbR1LNWYJwf5; Fri, 31 May 2019 08:17:43 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by rfc-editor.org (Postfix) with ESMTPS id C226DB80E51; Fri, 31 May 2019 08:17:42 -0700 (PDT)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:56b2:3ff:fe0b:d84]) by tuna.sandelman.ca (Postfix) with ESMTP id D6A5D38185; Fri, 31 May 2019 11:16:38 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id AD0CFE0A; Fri, 31 May 2019 11:17:45 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id AB502DAF; Fri, 31 May 2019 11:17:45 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Heather Flanagan <rse@rfc-editor.org>
In-Reply-To: <A66BF8D9-58AE-43A5-88D5-C6867E622B08@rfc-editor.org>
References: <30895.1559243194@localhost> <A66BF8D9-58AE-43A5-88D5-C6867E622B08@rfc-editor.org>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Date: Fri, 31 May 2019 11:17:45 -0400
Message-ID: <17301.1559315865@localhost>
Subject: Re: [rfc-i] acknowledging reviewers name in RFCs
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Cc: rfc-interest@rfc-editor.org
Content-Type: multipart/mixed; boundary="===============2905039690379476210=="
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: "rfc-interest" <rfc-interest-bounces@rfc-editor.org>

Heather Flanagan <rse@rfc-editor.org> wrote:
    > Are you thinking of something that would appear

    > A) in the document
    > B) in the metadata for the document (so, on the info pages or in the data tracker)
    > C) in the index
    > D) All or some combination of the above

(D), probably not much in (C).

    > Is what you’re looking for already on the data tracker pages for RFCs?
    > I know that shows things like doc shepherd, but I don’t recall if it
    > shows GenART or SecDir reviewers.

It needs to be in the document.
The official rfc-editor (info/XYZ) pages do not contain all the DT info, and of
course, mirrors of RFCs often do not even know to point at those pages,
although we now have that URL in the abstract.

GenART and SecDIR reviews are stored on the DT, assuming that the review
uploades them that way and does it that way.  I'm not sure if the DT can
handle more than one slot.   And it doesn't cover non-directorate reviews.

It's not currently possible from the DT page for an RFC to find out who the
WG chair was when the document was published.  We keep track of who was AD
and who the Shephard was. (Often a WG chair is a shepherd, so some info is there)


--
Michael Richardson <mcr+IETF@sandelman.ca>ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-



_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest