Browse Prior Art Database

Instructions to RFC Authors (RFC1543)

IP.com Disclosure Number: IPCOM000002375D
Original Publication Date: 1993-Oct-01
Included in the Prior Art Database: 2000-Sep-12
Document File: 14 page(s) / 29K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Postel: AUTHOR

Abstract

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

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

Network Working Group J. Postel

Request for Comments: 1543 ISI

Obsoletes: RFCs 1111, 825 October 1993

Category: Informational

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.

Table of Contents

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 1

2. Editorial Policy . . . . . . . . . . . . . . . . . . . . . . 3

3. Format Rules . . . . . . . . . . . . . . . . . . . . . . . . 4

3a. ASCII Format Rules . . . . . . . . . . . . . . . . . . . . 4

3b. PostScript Format Rules . . . . . . . . . . . . . . . . . . 5

4. Header . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

4a. First Page Heading . . . . . . . . . . . . . . . . . . . . 6

4b. Running Header . . . . . . . . . . . . . . . . . . . . . . 7

4c. Running Footer . . . . . . . . . . . . . . . . . . . . . . 7

5. Status Section . . . . . . . . . . . . . . . . . . . . . . . 5

6. Introduction Section . . . . . . . . . . . . . . . . . . . . 8

7. References Section . . . . . . . . . . . . . . . . . . . . . 9

8. Security Considerations Section . . . . . . . . . . . . . 10

9. Author's Address Section . . . . . . . . . . . . . . . . . 10

10. Relation to other RFCs . . . . . . . . . . . . . . . . . . 10

11. Protocol Standards Process . . . . . . . . . . . . . . . . 11

12. Contact . . . . . . . . . . . . . . . . . . . . . . . . . 11

13. Distribution Lists . . . . . . . . . . . . . . . . . . . . 11

14. RFC Index . . . . . . . . . . . . . . . . . . . . . . . . 12

15. Security Considerations . . . . . . . . . . . . . . . . . 12

16. References . . . . . . . . . . . . . . . . . . . . . . . . 12

17. Author's Address . . . . . . . . . . . . . . . . . . . . . 12

18. Appendix - RFC "nroff macros" . . . . . . . . . . . . . . 13

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.

RFCs are distributed online by being stored as public acces...