[33002] in North American Network Operators' Group
Re: RFC Outlines
daemon@ATHENA.MIT.EDU (Andrew Brown)
Wed Dec 20 13:06:55 2000
Date: Wed, 20 Dec 2000 13:04:51 -0500
From: Andrew Brown <twofsonet@graffiti.com>
To: Pete Rohrman <prohrman@internap.com>
Cc: nanog@merit.edu
Message-ID: <20001220130451.B22631@noc.untraceable.net>
Reply-To: Andrew Brown <atatat@atatdot.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.21.0012191642110.21428-100000@prohrman.nyc.internap.com>; from prohrman@internap.com on Tue, Dec 19, 2000 at 04:53:44PM -0500
Errors-To: owner-nanog-outgoing@merit.edu
>Can anyone refer me to an RFC or similar documentation that outlines
>how an RFC should be written?
>
>I've heard rumors that there is something out there called "RFC
>Writer" that helps RFC authors keep consistent structure. If this thing
>exists, can someone tell me where to get it?
i dunno about that, but there are rfcs on it.
rfc2223.txt
rfc2360.txt
for historical interest only
rfc0825.txt
rfc1111.txt
rfc1543.txt
and maybe even (if you like xml)
rfc2629.txt
--
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org * "ah! i see you have the internet
twofsonet@graffiti.com (Andrew Brown) that goes *ping*!"
andrew@crossbar.com * "information is power -- share the wealth."
