Browse Prior Art Database

Request for comments on Request for Comments: Instructions to RFC authors (RFC1111) Disclosure Number: IPCOM000001921D
Original Publication Date: 1989-Aug-01
Included in the Prior Art Database: 2000-Sep-12
Document File: 5 page(s) / 11K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Postel: AUTHOR


RFCs are distributed online by being stored as public access files, and a short message is sent to the distribution list indicating the availability of the memo.

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

Network Working Group J. Postel

Request for Comments: 1111 ISI

Obsoletes: 825 August 1989

Request for Comments on Request for Comments

Instructions to RFC Authors

Status of this Memo

This RFC specifies a standard for the Internet community. Authors of

RFCs are expected to adopt and implement this standard. Distribution

of this memo is unlimited.

1. Introduction

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

and a short message is sent to the distribution list indicating the

availability of the memo.

The online files are copied by the interested people and printed or

displayed at their site on their equipment. (An RFC may also be

returned via email in response to an email query.) This means that

the format of the online files must meet the constraints of a wide

variety of printing and display equipment.

2. Format Rules

To meet the distribution constraints the following rules are

established for the two allowed formats for RFCs: ASCII and


The RFC Editor attempts to ensure a consistent RFC style. To do this

the RFC Editor may choose reformat the RFC submitted. It is much

easier to do this if the submission matches the style of the most

recent RFCs. Please do look at some recent RFCs and prepare yours in

the same style.

You must submit an editable online document to the RFC Editor. The

RFC Editor may require minor changes in format or style and will

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 a

line by itself.

Each line must be limited to 72 characters followed by carriage

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 right


Do not do hyphenation of words at the right margin.

Do not use footnotes. If such notes are necessary, put them at

the end of a section, or at the end of the document.

Use single spaced text within a paragraph, and one blank line

between paragraphs.

RFCs in ASCII Format may be submitted to the RFC Editor in email

messages (or as online files) in either the finished publication

format or in NROFF. If you plan to submit a document in NROFF,

please consult the RFC Editor first.

2b. PostScript Format Rules

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 with

a line spacing of 12 points.

Footnotes and graph notations no smaller than 8 points with a line