Instructions to RFC Authors
RFC 2223

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions

Network Working Group                                          J. Postel
Request for Comments: 2223                                   J. Reynolds
Obsoletes: 1543, 1111, 825                                           ISI
Category: Informational                                     October 1997

                      Instructions to RFC Authors

Status of this Memo

   This memo provides information for the Internet community.  This memo
   does not specify an Internet standard of any kind.  Distribution of
   this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (1997).  All Rights Reserved.

Table of Contents

   1.   Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
   2.   Editorial Policy . . . . . . . . . . . . . . . . . . . . . . 3
   3.   Format Rules . . . . . . . . . . . . . . . . . . . . . . . . 4
   3a.   ASCII Format Rules  . . . . . . . . . . . . . . . . . . . . 5
   3b.   PostScript Format Rules . . . . . . . . . . . . . . . . . . 6
   4.   Header . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
   4a.   First Page Heading  . . . . . . . . . . . . . . . . . . . . 7
   4b.   Running Header  . . . . . . . . . . . . . . . . . . . . . . 8
   4c.   Running Footer  . . . . . . . . . . . . . . . . . . . . . . 8
   5.   Status Section . . . . . . . . . . . . . . . . . . . . . . . 8
   6.   Copyright Notice . . . . . . . . . . . . . . . . . . . . . . 9
   7.   Introduction Section . . . . . . . . . . . . . . . . . . . . 9
   8.   References Section . . . . . . . . . . . . . . . . . . . .  11
   9.   Security Considerations Section  . . . . . . . . . . . . .  11
   10.  Author's Address Section . . . . . . . . . . . . . . . . .  11
   11.  Copyright Section  . . . . . . . . . . . . . . . . . . . .  11
   12.  Relation to other RFCs . . . . . . . . . . . . . . . . . .  12
   13.  Protocol Standards Process . . . . . . . . . . . . . . . .  13
   14.  Contact  . . . . . . . . . . . . . . . . . . . . . . . . .  13
   15.  Distribution Lists . . . . . . . . . . . . . . . . . . . .  14
   16.  RFC Index  . . . . . . . . . . . . . . . . . . . . . . . .  14
   17.  Security Considerations  . . . . . . . . . . . . . . . . .  14
   18.  References . . . . . . . . . . . . . . . . . . . . . . . .  14
   19.  Authors' Addresses . . . . . . . . . . . . . . . . . . . .  15
   20.  Appendix - RFC "nroff macros"  . . . . . . . . . . . . . .  16
   21.  Full Copyright Statement . . . . . . . . . . . . . . . . .  20

Postel & Reynolds            Informational                      [Page 1]
RFC 2223              Instructions to RFC Authors           October 1997

1.  Introduction

   This Request for Comments (RFC) provides information about the
   preparation of RFCs, and certain policies relating to the publication
   of RFCs.

   The RFC series of notes covers a broad range of interests.  The core
   topics are the Internet and the TCP/IP protocol suite.  However, any
   topic related to computer communication may be acceptable at the
   discretion of the RFC Editor.

   Memos proposed to be RFCs may be submitted by anyone.  One large
   source of memos that become RFCs is the Internet Engineering Task
   Force (IETF).  The IETF working groups (WGs) evolve their working
   memos (known as Internet Drafts or I-Ds) until they feel they are
   ready for publication, then the memos are reviewed by the Internet
   Engineering Steering Group (IESG), and if approved sent by the IESG
   to the RFC Editor.

   Most of the memos submitted to the RFC Editor from independent
   sources will be reviewed by the IESG for possible relationship to
   work in progress in the IETF Working Groups.

   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.  This means that the
   format of the online files must meet the constraints of a wide
   variety of printing and display equipment.  (RFCs may also be
   returned via e-mail in response to an e-mail query, or RFCs may be
   found using information and database searching tools such as Gopher,
   Wais, or the World Wide Web (WWW).

   RFCs have been traditionally published and continue to be published
   in ASCII text.

   While the primary RFCs is always an ASCII text file, secondary or
   alternative versions of RFC may be provided in PostScript.  This
   decision is motivated by the desire to include diagrams, drawings,
   and such in RFCs.  PostScript documents (on paper only, so far) are
   visually more appealing and have better readability.

   PostScript was chosen for the fancy form of RFC publication over
   other possible systems (e.g., impress, interpress, oda) because of
   the perceived wide spread availability of PostScript capable
   printers.

Postel & Reynolds            Informational                      [Page 2]