WARNING: This information has not been updated since October, 1997!

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
INDEX ENTRY FOR RFCS:
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Name: RFCs - Internet Requests for Comment

Version: N/A

Author(s): many and varied

Ftp source: ds.internic.net:/rfc/

Description:

   RFC stands for Request for Comment, and was originally used in that
   fashion to discuss technical issues among developers.  Today the name
   and spirit are still there, but the RFC series has become the definition
   of the protocols and standards used on the Internet.  The RFC process
   is managed by the IETF (Internet Engineering Task Force) and the IESG
   (Internet Engineering Steering Group).  The site ds.internic.net also
   contains draft documents that are the potential RFCs of tomorrow; they
   are in the directory internet-drafts, but are so volatile that we did
   not include them on the CD. The file rfc-index.txt is a good starting
   point; the RFCs themselves are numbered sequentially with the filename
   typically rfcXXXX.txt for RFC number XXXX. There are few RFCs which
   have supplemental PostScript or tar files. 

Advertised architectures: N/A

Prerequisites: Most RFCs are plain text format; a PostScript previewer/printer
   is required for a few of them.

UNIX System Administration Handbook	|  Tools for UNIX System Administrators
FAQ  |  Errors  |  Goodies  |  Purchase  |  Register  |  Send Email