[153194] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Accuracy of RFCs (was: Re: HE.net BGP origin attribute rewriting)

daemon@ATHENA.MIT.EDU (John Curran)
Fri Jun 1 07:47:18 2012

X-Report-Abuse-To: abuse@dyndns.com (see
 http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse
 reporting information)
From: John Curran <jcurran@istaff.org>
In-Reply-To: <20120601082800.GA19206@pob.ytti.fi>
Date: Fri, 1 Jun 2012 07:46:30 -0400
To: Saku Ytti <saku@ytti.fi>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

On Jun 1, 2012, at 4:28 AM, Saku Ytti wrote:

> It's extremely hard to find RFC which does not contain incorrect
> information or practically undeployable data.

Actual errors in RFC's (typos, incorrect references, etc.) - 
<http://www.rfc-editor.org/errata.php>

Differing views regarding RFC subject material; feel free to 
work with others of similar to write up your perspective - 
<http://www.rfc-editor.org/rfc/rfc2223.txt>

The RFC series is an Internet-wide community effort.

Thanks!
/John



home help back first fref pref prev next nref lref last post