IETF Logo Mail Archive

Re: Proposed IESG Statement Regarding RFC Errata for IETF Sream RFCs

Alexey Melnikov <alexey.melnikov@isode.com> Thu, 17 April 2008 10:33 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6930A3A7016; Thu, 17 Apr 2008 03:33:31 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6BB8B3A6909; Thu, 17 Apr 2008 03:33:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.509
X-Spam-Level:
X-Spam-Status: No, score=-2.509 tagged_above=-999 required=5 tests=[AWL=0.091, 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 LBjp0Lcs2Zer; Thu, 17 Apr 2008 03:33:28 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 699B93A700F; Thu, 17 Apr 2008 03:33:28 -0700 (PDT)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPA id <SAcnnAA4EZZH@rufus.isode.com>; Thu, 17 Apr 2008 11:34:05 +0100
Message-ID: <48071027.8030806@isode.com>
Date: Thu, 17 Apr 2008 09:53:59 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Jeffrey Hutzelman <jhutz@cmu.edu>
Subject: Re: Proposed IESG Statement Regarding RFC Errata for IETF Sream RFCs
References: <20080416151659.F075C3A6C0B@core3.amsl.com> <15DF6ADF1AA8AE0496765BFF@sirius.fac.cs.cmu.edu>
In-Reply-To: <15DF6ADF1AA8AE0496765BFF@sirius.fac.cs.cmu.edu>
MIME-Version: 1.0
Cc: rfc-editor@rfc-editor.org, iaoc@ietf.org, iab@iab.org, ietf@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Jeffrey Hutzelman wrote:

>I support adoption of these proposed guidelines, but have a couple of minor 
>comments...
>  
>
>>   After an erratum is reported, a report will be sent to the authors and
>>
>>   Area Directors (ADs) of the WG in which it originated.  If the WG has
>>   closed or the document was not associated with a WG, then the
>>   report will be sent to the ADs for the Area most closely associated
>>   to the subject matter.
>>    
>>
>If the document was produced by a WG that is not closed, the report should 
>be copied to the WG chairs as well.
>  
>
+1.


_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email