![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
A new Request for Comments is now available in online RFC libraries.
BCP 22:
RFC 2360:
Title: Guide for Internet Standards Writers
Author(s): G. Scott, Editor
Status: Best Current Practice
Date: June 1998
Mailbox: scottg at ftm.disa.mil
Pages: 20
Characters: 47280
Updates/Obsoletes: None
URL: ftp://ftp.isi.edu/in-notes/rfc2360.txt
This document is a guide for Internet standard writers. It defines
those characteristics that make standards coherent, unambiguous, and
easy to interpret. In addition, it singles out usage believed to
have led to unclear specifications, resulting in non-interoperable
interpretations in the past. These guidelines are to be used with
RFC 2223, "Instructions to RFC Authors".
This document is a product of the Guide for Internet Standards Writers
Working Group of the IETF.
This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. Distribution of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at ISI.EDU.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at ISI.EDU with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info at ISI.EDU
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at ISI.EDU. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR at ISI.EDU. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Alegre Ramos
USC/Information Sciences Institute
...
Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.