As per Relevance of the word distribution, we have this rfc below:
Network Working Group J.
Request for Comments: 1111
Obsoletes: 825 August 1989
Request for Comments on Request for
Instructions to RFC
Status of this
This RFC specifies a standard for the Internet community. Authors
RFCs are expected to adopt and implement this standard.
of this memo is unlimited
1.
RFCs are distributed online by being stored as public access files
and a short message is sent to the distribution list indicating
availability of the memo
The online files are copied by the interested people and printed
displayed at their site on their equipment. (An RFC may also
returned via email in response to an email query.) This means
the format of the online files must meet the constraints of a
variety of printing and display equipment
2. Format
To meet the distribution constraints the following rules
established for the two allowed formats for RFCs: ASCII
PostScript
The RFC Editor attempts to ensure a consistent RFC style. To do
the RFC Editor may choose reformat the RFC submitted. It is
easier to do this if the submission matches the style of the
recent RFCs. Please do look at some recent RFCs and prepare yours
the same style
You must submit an editable online document to the RFC Editor.
RFC Editor may require minor changes in format or style and
insert the actual RFC number
2a. ASCII Format Rules
The character codes are ASCII
Each page must be limited to 58 lines followed by a form feed on
Postel [Page 1]
RFC 1111 RFC Instructions August 1989
line by itself
Each line must be limited to 72 characters followed by
return and line feed
No overstriking (or underlining) is allowed
These "height" and "width" constraints include any headers
footers, page numbers, or left side indenting
Do not fill the text with extra spaces to provide a straight
margin
Do not do hyphenation of words at the right margin
Do not use footnotes. If such notes are necessary, put them
the end of a section, or at the end of the document
Use single spaced text within a paragraph, and one blank
between paragraphs
RFCs in ASCII Format may be submitted to the RFC Editor in
messages (or as online files) in either the finished
format or in NROFF. If you plan to submit a document in NROFF
please consult the RFC Editor first
2b. PostScript Format
Standard page size is 8 1/2 by 11 inches
Margin of 1 inch on all sides (top, bottom, left, and right).
Main text should have a point size of no less than 10 points
a line spacing of 12 points
Footnotes and graph notations no smaller than 8 points with a
spacing of 9.6 points
Three fonts are acceptable: Helvetica, Times Roman and
Plus their bold-face and italic versions. These are the
standard fonts on most PostScript printers
Prepare diagrams and images based on lowest common
PostScript. Consider common PostScript printer functionality
memory requirements
The following PostScript commands should not be used
initgraphics, erasepage, copypage, grestoreall, initmatrix
Postel [Page 2]
RFC 1111 RFC Instructions August 1989
initclip, banddevice, framedevice, nulldevice and renderbands
These PostScript rules are likely to changed and expanded
experience is gained
RFCs in PostScript Format may be submitted to the RFC Editor
email messages (or as online files). Since PostScript is
editable, an editable source version of the document must also
submitted. If you plan to submit a document in PostScript,
consult the RFC Editor first
3. Status
Each RFC must include on its first page the "Status of this Memo
section which contains a paragraph describing the intention of
RFC. This section is meant to convey the status granted by the
Editor and the Internet Activities Board (IAB). There are
reasons for publishing a memo as an RFC, for example, to
available some information for interested people, or to begin
continue a discussion of an interesting idea, or to make
the specification of a protocol
The following sample paragraphs may be used to satisfy
requirement
Proposed
This RFC suggests a proposed protocol for the
community, and requests discussion and suggestions
improvements
This RFC specifies a standard for the Internet community
Hosts on the Internet are expected to adopt and
this standard
The purpose of this RFC is to focus discussion on
problems in the Internet and possible methods of solution
No proposed solutions this document are intended
standards for the Internet. Rather, it is hoped that
general consensus will emerge as to the appropriate
to such problems, leading eventually to the adoption
standards
Postel [Page 3]
RFC 1111 RFC Instructions August 1989
This RFC is being distributed to members of the
community in order to solicit their reactions to
proposals contained in it. While the issues discussed
not be directly relevant to the research problems of
Internet, they may be interesting to a number of
and implementers
In response to the need for maintenance of
information about the status and progress of
projects in the Internet community, this RFC is issued
the benefit of community members. The information
in this document is accurate as of the date of publication
but is subject to change. Subsequent RFCs will reflect
changes
These paragraphs need not be followed word for word, but
general intent of the RFC must be made clear
4. Distribution
Each RFC is to also include a "distribution statement". In general
RFCs have unlimited distribution. There may be a few cases in
it is appropriate to restrict the distribution in some way
Typically, the distribution statement will simply be the
"Distribution of this memo is unlimited." appended to the "Status
this Memo" section
5. Author's
Each RFC must have at the very end a section giving the author'
address, including the name and postal address, the telephone number
and the Internet email address
6. Relation to other
Sometimes an RFC adds information on a topic discussed in a
RFC or completely replaces an earlier RFC. There are two terms
for these cases respectively, UPDATES and OBSOLETES. A document
obsoletes an earlier document can stand on its own. A document
merely updates an earlier document cannot stand on its own; it
something that must be added to or inserted into the
document, and has limited usefulness independently. The
SUPERSEDES and REPLACES are no longer used
Postel [Page 4]
RFC 1111 RFC Instructions August 1989
To be used as a reference from a new item that cannot be
alone (i.e., one that supplements a previous document), to
to the previous document. The newer publication is a part
will supplement or be added on to the existing document; e.g.,
addendum, or separate, extra information that is to be added
the original document
To be used to refer to an earlier document that is replaced
this document. This document contains either revised information
or else all of the same information plus some new information
however extensive or brief that new information is; i.e.,
document can be used alone, without reference to the
document
For example
On the Assigned Numbers RFCs, the term OBSOLETES should be
since the new document actually incorporates new
(however brief) into the text of existing information and
more up-to-date than the older document, and hence, replaces
and makes it OBSOLETE
In lists of RFCs or the RFC-Index (but not on the RFCs themselves),
the following may be used with early documents to point to
documents
OBSOLETED-
To be used to refer to the newer document that replaces the
document
UPDATED-
To be used to refer to the newer document that adds information
the existing, still useful, document
Postel [Page 5]
RFC 1111 RFC Instructions August 1989
7. The RFC
The RFC Editor is Jon Postel
8. The RFC Announcement
New RFCs are announced to the RFC distribution list maintained by
SRI Network Information Center (NIC). Contact the SRI-NIC to
added or deleted from this mailing list by sending an email
to RFC-REQUEST@NIC.DDN.MIL
9. Obtaining
RFCs can be obtained via FTP from NIC.DDN.MIL, with the
RFC:RFCnnnn.TXT (where "nnnn" refers to the number of the RFC).
Login with FTP, username ANONYMOUS and password GUEST
The NIC also provides an automatic mail service for those sites
cannot use FTP. Address the request to SERVICE@NIC.DDN.MIL and
the subject field of the message indicate the RFC number, as
"Subject: RFC nnnn".
Requests for special distribution (for example, hardcopy) should
addressed to either the author of the RFC in question, or
NIC@NIC.DDN.MIL
Unless specifically noted otherwise on the RFC itself, all RFCs
for unlimited distribution
The RFCs may also be obtained from other information centers
including the CSNET Information Center (INFO@SH.CS.NET), the
Information Service (INFO@NIS.NSF.NET).
Author's
Jon
USC Information Sciences
4676 Admiralty
Marina del Rey, California 90292-6695
Phone: 213-822-1511
EMail: POSTEL@ISI.
Postel [Page 6]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
