Rfc Structure

1.a) Any RCF document that is published will generally have the following sections:

      a.   First-page header: This is normally used when an RFC author produce a document that obsoletes or updates a
                  previously published RFC(s. This should be indicated clearly, preferably in the header.     Stating this information in the header helps call attention to the RFC Editor that other actions are   necessary.This section is required.

      b.   Title: A good title should fairly represent the scope and purpose of the document without being either too general or too specific. RFC title must be centred, preceded by, and followed by at least
  one blank line. This field is required.

      c.   Status of this Memo: This is usually provided by the RFC Editor. It is required.

      d.   IESG Note: This text is normally provided to the RFC Editor by the IESG and will be then inserted into the RFC   text. Thus, it is not mandatory.

      e.   Abstract: This usuall has a maximum of 20 lines. This section should provide a concise and comprehensive
          overview of the purpose and contents of the entire document so that a technically knowledgeable reader   will have a general overview of the function of the document. The abstract section is absolutely required.

      f.   Table of Contents: The section must be positioned after the abstract section, as in this article. It should not be too long or detailed, otherwise it loses its Type Description References
The RFC Editor uses a program to generate and format the TOC at the final stage of editing an RFC. This section is required in RFCs longer than 30 pages and recommended for an RFC longer than 15 pages.

      g.   Body of the Memo: Immediately following the Table of Contents, if any, is the body of the memo.
  Depending upon the length of the TOC, a judicious page break before the body can improve readability.

                The body of the memo... [continues]

Read full essay