InnovationQ/InnovationQ Plus content will be updated on Sunday, June 25, 10am ET, with new patent and non-patent literature collections. Click here to learn more.
Browse Prior Art Database

Request for comments on Requests For Comments (RFC0825)

IP.com Disclosure Number: IPCOM000003873D
Original Publication Date: 1982-Nov-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 2 page(s) / 4K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Postel: AUTHOR


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.

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 75% of the total text.

Network Working Group J. Postel

Request for Comments: 825 ISI

November 1982

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

this standard.


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



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

be indicated including (but not limited to) policy issues,

technical topics discussed and problems needing further work.

Of course these paragraphs need not be followed word for word, but

the general intent of the RFC must be made clear.

RFCs are distributed online by being stored as public access files, and

a short messages is sent to the distribution ...