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

"Sabahattin Gucukoglu" <mail@sabahattin-gucukoglu.com> Fri, 18 April 2008 20:20 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 4A8983A6ECA; Fri, 18 Apr 2008 13:20:39 -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 B55923A6CE2 for <ietf@core3.amsl.com>; Fri, 18 Apr 2008 12:14:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
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 rDNJuruON9dX for <ietf@core3.amsl.com>; Fri, 18 Apr 2008 12:14:16 -0700 (PDT)
Received: from bloodstone.sabahattin-gucukoglu.com (bloodstone.sabahattin-gucukoglu.com [83.146.49.241]) by core3.amsl.com (Postfix) with ESMTP id 7E5013A6945 for <ietf@ietf.org>; Fri, 18 Apr 2008 12:14:15 -0700 (PDT)
Received: FROM amethyst.sabahattin-gucukoglu.com (amethyst.sabahattin-gucukoglu.com [83.146.49.248]) (authenticated sgucukoglu) BY bloodstone.sabahattin-gucukoglu.com (Sendmail 8.13.8) WITH ESMTP ID m3IJEGr9022682 FOR <ietf@ietf.org>; Fri, 18 Apr 2008 20:14:16 +0100
From: Sabahattin Gucukoglu <mail@sabahattin-gucukoglu.com>
To: ietf@ietf.org, iesg@ietf.org
Date: Fri, 18 Apr 2008 20:13:52 +0100
MIME-Version: 1.0
Subject: Re: Proposed IESG Statement Regarding RFC Errata for IETF Sream RFCs
Message-ID: <48090100.9485.33ACF444@mail.sabahattin-gucukoglu.com>
Priority: normal
In-reply-to: <20080416151659.F075C3A6C0B@core3.amsl.com>
References: <20080416151659.F075C3A6C0B@core3.amsl.com>
X-PM-Encryptor: QDPGP, 4
X-mailer: Pegasus Mail for Windows (4.41)
Content-description: Mail message body
X-Mailman-Approved-At: Fri, 18 Apr 2008 13:20:34 -0700
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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

How does Joe Implementer become aware of RFC errata available?  I don't 
recall seeing anything in the standard boilerplate to point them out.  
(And although I'm aware of them myself, I'd quite forgotten about them.)

Cheers,
Sabahattin

- -- 
Sabahattin Gucukoglu <mail<at>sabahattin<dash>gucukoglu<dot>com>
Address harvesters, snag this: feedme@yamta.org
Phone: +44 20 88008915
Mobile: +44 7986 053399
http://sabahattin-gucukoglu.com/


-----BEGIN PGP SIGNATURE-----
Version: PGP 8
Comment: QDPGP - http://community.wow.net/grt/qdpgp.html

iQA/AwUBSAjy8CNEOmEWtR2TEQJsoACgr7hRHar3Z/gz3cs6eFR2YgDF70wAniY1
7xMsA13D57fMxZlERk2rcO3S
=SM9g
-----END PGP SIGNATURE-----
_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf