[Disman] Fwd: RFC Errata Update for Working Group Chairs

"Randy Presuhn" <randy_presuhn@mindspring.com> Sat, 10 January 2009 00:30 UTC

Return-Path: <disman-bounces@ietf.org>
X-Original-To: disman-archive@megatron.ietf.org
Delivered-To: ietfarch-disman-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5AD9D28C130; Fri, 9 Jan 2009 16:30:40 -0800 (PST)
X-Original-To: disman@core3.amsl.com
Delivered-To: disman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E2FBB28C130; Fri, 9 Jan 2009 16:30:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.571
X-Spam-Level:
X-Spam-Status: No, score=-2.571 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tLQf3ItsYfNG; Fri, 9 Jan 2009 16:30:37 -0800 (PST)
Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by core3.amsl.com (Postfix) with ESMTP id BC91C3A6767; Fri, 9 Jan 2009 16:30:37 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=akH8GhjMpgI7uFDIuo0WxyyQEX7KCf/zZl3cX6OLwTubgPJqzfc+BaaDOI8YKmO3; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [68.165.5.216] (helo=oemcomputer) by elasmtp-banded.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1LLRk7-0005qQ-Ro; Fri, 09 Jan 2009 19:30:24 -0500
Message-ID: <001701c972bb$07177b40$6801a8c0@oemcomputer>
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: Disman <disman@ietf.org>, agentx@ietf.org, LTRU Working Group <ltru@ietf.org>
References: <20090108203120.GC29175@isi.edu> <ca722a9e0901091123m8d6c8een1d696ae6e9590201@mail.gmail.com>
Date: Fri, 09 Jan 2009 16:33:14 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8886924630f8852f173508c2e6a4479aa42046374945d92b3f8350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 68.165.5.216
Subject: [Disman] Fwd: RFC Errata Update for Working Group Chairs
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/disman>, <mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/disman>, <mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

Hi -

Updated information on RFC errata ....

Randy
===========================================

From: RFC Editor <rfc-editor@rfc-editor.org>
Date: Thu, Jan 8, 2009 at 12:31 PM
Subject: RFC Errata Update for Working Group Chairs
To: wgchairs@ietf.org
Cc: RFC Editor <rfc-editor@rfc-editor.org>


WG chairs,

We have made some updates to the RFC errata system and would like to
inform you of the new features and explain how these features may
impact your working group.

1) We'd like to bring your attention to the improved search for RFC
errata on http://www.rfc-editor.org/errata.php. You can search by WG
acronym and other information.

Please contact your Area Director if you find errata reports that need
correction.  For example, the Type (Editorial/Technical) may be
incorrect.  Area Directors can log in to verify errata in RFCs
produced by the IETF stream, so if you want to to recommend that a
report be Verified/Rejected/Held, then please let the relevant AD
know. (For the meanings of Status and Type for RFC errata, please see
http://www.rfc-editor.org/status_type_desc.html.)

2) Previously, the initial report message was sent to the authors of
the RFC and the relevant WG chairs and ADs when the RFC was a product
of a WG.  The IESG has suggested that the WG mailing list be CC'ed on
these messages, and we have implemented this feature.  For example,
grow@ietf.org would now be CC'ed on the message below.  The idea is to
notify the WG of the new report and potentially initiate a discussion
of the validity of the report among those who are familiar with the
content.  This will allow the verifier to update the erratum so that
its Status and Notes capture the conclusion of any discussion.

Please distribute this information to your working groups as you see
fit, and let us know if you have any comments or concerns.

Thank you.

RFC Editor