[Forward: RFC 5741 on RFC Streams, Headers, and Boilerplates]

RFC Editor <rfc-editor@rfc-editor.org> Mon, 28 December 2009 04:20 UTC

Return-Path: <rfc-ed@ISI.EDU>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 926313A67C2 for <ietf-announce@core3.amsl.com>; Sun, 27 Dec 2009 20:20:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.952
X-Spam-Level:
X-Spam-Status: No, score=-16.952 tagged_above=-999 required=5 tests=[AWL=-0.436, BAYES_00=-2.599, URIBL_RHS_DOB=1.083, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WpIr6UuAmkUr for <ietf-announce@core3.amsl.com>; Sun, 27 Dec 2009 20:20:52 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 847043A6403 for <ietf-announce@ietf.org>; Sun, 27 Dec 2009 20:20:52 -0800 (PST)
Received: from boreas.isi.edu (localhost [127.0.0.1]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id nBS4ET9e027863; Sun, 27 Dec 2009 20:14:29 -0800 (PST)
Received: (from rfc-ed@localhost) by boreas.isi.edu (8.13.8/8.13.8/Submit) id nBS4ETCq027862; Sun, 27 Dec 2009 20:14:29 -0800 (PST)
Date: Sun, 27 Dec 2009 20:14:29 -0800
From: RFC Editor <rfc-editor@rfc-editor.org>
To: ietf-announce@ietf.org
Subject: [Forward: RFC 5741 on RFC Streams, Headers, and Boilerplates]
Message-ID: <20091228041429.GC25206@isi.edu>
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
X-MailScanner-From: rfc-ed@boreas.isi.edu
Cc: RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Dec 2009 04:20:55 -0000

Forwarding because this announcement hasn't appeared in the IETF
archives yet.

----- Forwarded message from rfc-editor@rfc-editor.org -----

To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5741 on RFC Streams, Headers, and Boilerplates
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org
Date: Thu, 24 Dec 2009 11:37:07 -0800 (PST)


A new Request for Comments is now available in online RFC libraries.

        
        RFC 5741

        Title:      RFC Streams, Headers, and Boilerplates 
        Author:     L. Daigle, Ed.,
                    O. Kolkman, Ed.,
                    IAB
        Status:     Informational
        Date:       December 2009
        Mailbox:    leslie@thinkingcat.com, 
                    olaf@nlnetlabs.nl, 
                    iab@iab.org
        Pages:      16
        Characters: 32160
        Updates:    RFC2223, RFC4844

        I-D Tag:    draft-iab-streams-headers-boilerplates-08.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5741.txt

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 is not an Internet Standards 
Track specification; it is published for informational purposes.

This document is a product of the Internet Architecture Board.


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

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute


----- End forwarded message -----