RFC 7841 on RFC Streams, Headers, and Boilerplates
rfc-editor@rfc-editor.org Wed, 25 May 2016 23:50 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61B8312DE59 for <ietf-announce@ietfa.amsl.com>; Wed, 25 May 2016 16:50:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.328
X-Spam-Level:
X-Spam-Status: No, score=-108.328 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Tpsr0JviRqM for <ietf-announce@ietfa.amsl.com>; Wed, 25 May 2016 16:50:29 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CAFFD12B053 for <ietf-announce@ietf.org>; Wed, 25 May 2016 16:50:03 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 0D40E180013; Wed, 25 May 2016 16:49:28 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7841 on RFC Streams, Headers, and Boilerplates
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160525234928.0D40E180013@rfc-editor.org>
Date: Wed, 25 May 2016 16:49:28 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/SorrEnyRypt86sM745r5TJo9tYc>
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Wed, 25 May 2016 23:50:31 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7841
Title: RFC Streams, Headers, and Boilerplates
Author: J. Halpern, Ed.,
L. Daigle, Ed.,
O. Kolkman, Ed.
Status: Informational
Stream: IAB
Date: May 2016
Mailbox: jmh@joelhalpern.com,
ldaigle@thinkingcat.com,
kolkman@isoc.org
Pages: 14
Characters: 27950
Obsoletes: RFC 5741
I-D Tag: draft-iab-rfc5741bis-02.txt
URL: https://www.rfc-editor.org/info/rfc7841
DOI: http://dx.doi.org/10.17487/RFC7841
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.
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
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
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
Association Management Solutions, LLC