On RFC Streams, Headers, and Boilerplates
draft-iab-rfc5741bis-01

The information below is for an old version of the document
Document Type Active Internet-Draft
Last updated 2015-12-12
Replaces draft-halpern-iab-rfc5741bis
Stream IAB
Intended RFC status Informational
Formats plain text pdf html bibtex
Stream IAB state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)
Network Working Group                                    J. Halpern, Ed.
Internet-Draft
Obsoletes: 5741 (if approved)                             L. Daigle, Ed.
Intended status: Informational
Expires: June 14, 2016                                   O. Kolkman, Ed.
                                                        Internet Society
                                             Internet Architecture Board
                                                                   (IAB)
                                                       December 12, 2015

               On RFC Streams, Headers, and Boilerplates
                        draft-iab-rfc5741bis-01

Abstract

   RFC documents contain a number of fixed elements such as the title
   page header, standard boilerplates and copyright/IPR statements.
   This document describes them and introduces some updates to reflect
   current usage and requirements of RFC publication.  In particular,
   this updated structure is intended to communicate clearly the source
   of RFC creation and review.  This document obsoletes RFC 5741, moving
   detailed content to an IAB web page and preparing for more flexible
   output formats.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on June 14, 2016.

Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Halpern, et al.           Expires June 14, 2016                 [Page 1]
Internet-Draft     RFC Streams, Headers, Boilerplates      December 2015

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  RFC Streams and Internet Standards  . . . . . . . . . . . . .   3
   3.  RFC Structural Elements . . . . . . . . . . . . . . . . . . .   4
     3.1.  The title page header . . . . . . . . . . . . . . . . . .   4
     3.2.  The Status of this Memo . . . . . . . . . . . . . . . . .   5
     3.3.  Paragraph 1 . . . . . . . . . . . . . . . . . . . . . . .   5
     3.4.  Paragraph 2 . . . . . . . . . . . . . . . . . . . . . . .   6
     3.5.  Paragraph 3 . . . . . . . . . . . . . . . . . . . . . . .   6
     3.6.  Noteworthy  . . . . . . . . . . . . . . . . . . . . . . .   6
   4.  Additional Notes  . . . . . . . . . . . . . . . . . . . . . .   6
   5.  Other structural information in RFCs  . . . . . . . . . . . .   7
   6.  Security considerations . . . . . . . . . . . . . . . . . . .   7
   7.  IANA considerations . . . . . . . . . . . . . . . . . . . . .   7
   8.  RFC Editor Considerations . . . . . . . . . . . . . . . . . .   7
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Appendix A.  IAB members at time of approval  . . . . . . . . . .  10
   Appendix B.  Acknowledgements . . . . . . . . . . . . . . . . . .  10
   Appendix C.  Initial Formating Details  . . . . . . . . . . . . .  10
     C.1.  RFC Title Page Header . . . . . . . . . . . . . . . . . .  10
     C.2.  Constructing a "Status of this Memo" Section  . . . . . .  11
       C.2.1.  First Paragraph . . . . . . . . . . . . . . . . . . .  11
       C.2.2.  Second Paragraph  . . . . . . . . . . . . . . . . . .  12
       C.2.3.  Third Paragraph . . . . . . . . . . . . . . . . . . .  13
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

   Previously RFCs (e.g.  [RFC4844]) contained a number of elements that
   were there for historical, practical, and legal reasons.  They also
   contained boilerplate material to clearly indicate the status of the
   document and possibly contained "Notes" to indicate how the document
   interacts with IETF Standards-Track documents.
Show full document text