RFC 7045 on Transmission and Processing of IPv6 Extension Headers

rfc-editor@rfc-editor.org Fri, 06 December 2013 18:54 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BD5E1AE016; Fri, 6 Dec 2013 10:54:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.953
X-Spam-Level:
X-Spam-Status: No, score=0.953 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 srnDGB4fZ0oJ; Fri, 6 Dec 2013 10:54:12 -0800 (PST)
Received: from rfc-editor.org (unknown [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id B0E431ADEB4; Fri, 6 Dec 2013 10:54:12 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 2A6917FC158; Fri, 6 Dec 2013 10:54:05 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7045 on Transmission and Processing of IPv6 Extension Headers
From: rfc-editor@rfc-editor.org
Message-Id: <20131206185405.2A6917FC158@rfc-editor.org>
Date: Fri, 06 Dec 2013 10:54:05 -0800
Cc: drafts-update-ref@iana.org, ipv6@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Dec 2013 18:54:14 -0000

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

        
        RFC 7045

        Title:      Transmission and Processing of IPv6 
                    Extension Headers 
        Author:     B. Carpenter, S. Jiang
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2013
        Mailbox:    brian.e.carpenter@gmail.com, 
                    jiangsheng@huawei.com
        Pages:      10
        Characters: 21852
        Updates:    RFC 2460, RFC 2780

        I-D Tag:    draft-ietf-6man-ext-transmit-05.txt

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

Various IPv6 extension headers have been standardised since the IPv6
standard was first published.  This document updates RFC 2460 to
clarify how intermediate nodes should deal with such extension
headers and with any that are defined in the future.  It also
specifies how extension headers should be registered by IANA, with a
corresponding minor update to RFC 2780.

This document is a product of the IPv6 Maintenance Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  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/search/rfc_search.php
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
Association Management Solutions, LLC