Section Ordering in RFCs (Abstract Placement)

RFC Editor <> Sat, 20 June 2009 01:25 UTC

Return-Path: <rfc-ed@ISI.EDU>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C22523A6AB3; Fri, 19 Jun 2009 18:25:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -17.167
X-Spam-Status: No, score=-17.167 tagged_above=-999 required=5 tests=[AWL=0.432, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id uOyBgymVYI0D; Fri, 19 Jun 2009 18:25:16 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 004333A6849; Fri, 19 Jun 2009 18:25:15 -0700 (PDT)
Received: from (localhost []) by (8.13.8/8.13.8) with ESMTP id n5K1OTHi013007 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 19 Jun 2009 18:24:29 -0700 (PDT)
Received: (from rfc-ed@localhost) by (8.13.8/8.13.8/Submit) id n5K1OSwx013005; Fri, 19 Jun 2009 18:24:28 -0700 (PDT)
Date: Fri, 19 Jun 2009 18:24:28 -0700
From: RFC Editor <>
Subject: Section Ordering in RFCs (Abstract Placement)
Message-ID: <>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
X-ISI-4-43-8-MailScanner: Found to be clean
Cc: IAB <>, IESG <>, RFC Editor <>
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 20 Jun 2009 01:25:16 -0000

Greetings All,

The recent changes to the copyright for RFCs (RFC 5378), and the
changes that will be required when
draft-iab-streams-headers-boilerplates-08.txt is published, often
result in the abstract not appearing on the front page of the RFC.
We concur with the IETF-list comments that expressed a desire to
keep the abstract on the front page of the RFC.  For this reason, the
RFC Editor recommends the following section order as the initial
contents of an RFC.  

RFC header/Author information
RFC Title
Status of this Memo
[IESG Note - when required]

The RFC Editor will implement this change as of 1 July 2009.

We will make requests with the appropriate individuals for the
templates and tools to be updated accordingly.  However, we will
reorder the sections manually during the final publication stage until
the updated tools are available.

Thank you.

RFC Editor