IETF Logo Mail Archive

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

"Frank Ellermann" <nobody@xyzzy.claranet.de> Sat, 19 April 2008 19:31 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 0E0973A6DD0; Sat, 19 Apr 2008 12:31:58 -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 22A4E3A6C5B for <ietf@core3.amsl.com>; Sat, 19 Apr 2008 12:31:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 1yn-p4xnICjt for <ietf@core3.amsl.com>; Sat, 19 Apr 2008 12:31:56 -0700 (PDT)
Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by core3.amsl.com (Postfix) with ESMTP id 503493A6923 for <ietf@ietf.org>; Sat, 19 Apr 2008 12:31:56 -0700 (PDT)
Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JnImy-00089X-2v for ietf@ietf.org; Sat, 19 Apr 2008 19:31:56 +0000
Received: from hmbg-d9b88e30.pool.mediaways.net ([217.184.142.48]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Sat, 19 Apr 2008 19:31:56 +0000
Received: from nobody by hmbg-d9b88e30.pool.mediaways.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Sat, 19 Apr 2008 19:31:56 +0000
X-Injected-Via-Gmane: http://gmane.org/
To: ietf@ietf.org
From: Frank Ellermann <nobody@xyzzy.claranet.de>
Subject: Re: Proposed IESG Statement Regarding RFC Errata for IETF Sream RFCs
Date: Sat, 19 Apr 2008 21:34:37 +0200
Organization: <http://purl.net/xyzzy>
Lines: 15
Message-ID: <fudhb0$avg$1@ger.gmane.org>
References: <20080416151659.F075C3A6C0B@core3.amsl.com> <48090100.9485.33ACF444@mail.sabahattin-gucukoglu.com>
Mime-Version: 1.0
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: hmbg-d9b88e30.pool.mediaways.net
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1914
X-Mimeole: Produced By Microsoft MimeOLE V6.00.2800.1914
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
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

Sabahattin Gucukoglu wrote:
 
> How does Joe Implementer become aware of RFC errata available?

1 - Joe found an RFC 4567 link in a default MediaWiki.  These
    links go to a page <http://tools.ietf.org/html/rfc4567>
    with a link to the errata at the end of the "tools" header.
2 - Joe found a <http://purl.net/net/rfc/4567> link somewhere,
    arriving at the RFC editor search form showing the meta
    data for RFC 4567, including a link to the (same) errata.
3 - Joe ran out of luck...

Abusing 4567, because 1234, 2345, and 3456 have no errata :-)

 Frank

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

v2.23.0 | Report a Bug | By Email