Request for comments on Requests For Comments (RFC0825)
Original Publication Date: 1982-Nov-01
Included in the Prior Art Database: 2000-Sep-13
Internet Society Requests For Comment (RFCs)
This RFC is intended to clarify the status of RFCs and to provide some guidance for the authors of RFCs in the future. It is in a sense a specification for RFCs.
Network Working Group J. Postel
Request for Comments: 825 ISI
Request for Comments on Requests for Comments
This RFC is intended to clarify the status of RFCs and to provide some
guidance for the authors of RFCs in the future. It is in a sense a
specification for RFCs.
There are several reasons for publishing a memo as an RFC, for example,
to make available some information for interested people, or to begin or
continue a discussion of an interesting idea, or to specify a protocol.
Each RFC is to include on its title page or in the first or second
paragraph a statement describing the intention of the RFC.
The following sample paragraphs may be used to satisfy this
This RFC specifies a standard for the ARPA Internet community.
Hosts on the ARPA Internet are expected to adopt and implement
The purpose of this RFC is to focus discussion on particular
problems in the ARPA Internet and possible methods of solution.
No proposed solutions this document are intended as standards
at this time. Rather, it is hoped that a general consensus
will emerge as to the appropriate solution to such problems,
leading eventually to the adoption of standards.
This RFC is presented to members of the ARPA Internet community
in order to solicit their reactions to the proposals contained
in it. While perhaps the issues discussed are not directly
relevant to the research problems of the ARPA Internet, they
may be particularly interesting to some researchers and
RFC 825 November 1982
RFC on RFCs
This RFC is issued in response to the need for current
information about the status and progress of various projects
in the ARPA Internet community. The information contained in
this document is accurate as of the date of publication, but is
subject to change. Subsequent RFCs may reflect such changes.
This RFC is issued to report on the results of a meeting. It
may document significant decisions made that impact the
implementation of network protocols, or limit or expand the use
of optional features of protocols. Other meeting results may