RFC 6564 on A Uniform Format for IPv6 Extension Headers

rfc-editor@rfc-editor.org Tue, 10 April 2012 02:31 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E9EB11E8099; Mon, 9 Apr 2012 19:31:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.15
X-Spam-Level:
X-Spam-Status: No, score=-102.15 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aIFfcV9nkh+a; Mon, 9 Apr 2012 19:31:49 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id E2AB511E8074; Mon, 9 Apr 2012 19:31:49 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id ADC596218A; Mon, 9 Apr 2012 19:31:19 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6564 on A Uniform Format for IPv6 Extension Headers
From: rfc-editor@rfc-editor.org
Message-Id: <20120410023119.ADC596218A@rfc-editor.org>
Date: Mon, 9 Apr 2012 19:31:19 -0700 (PDT)
Cc: ipv6@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 10 Apr 2012 02:31:50 -0000

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

        
        RFC 6564

        Title:      A Uniform Format for IPv6 
                    Extension Headers 
        Author:     S. Krishnan, J. Woodyatt,
                    E. Kline, J. Hoagland,
                    M. Bhatia
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2012
        Mailbox:    suresh.krishnan@ericsson.com, 
                    jhw@apple.com, 
                    ek@google.com,  
                    Jim_Hoagland@symantec.com, 
                    manav.bhatia@alcatel-lucent.com
        Pages:      6
        Characters: 12879
        Updates:    RFC2460

        I-D Tag:    draft-ietf-6man-exthdr-06.txt

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

In IPv6, optional internet-layer information is encoded in separate
headers that may be placed between the IPv6 header and the transport-layer
header.  There are a small number of such extension headers
currently defined.  This document describes the issues that can arise
when defining new extension headers and discusses the alternate
extension mechanisms in IPv6.  It also provides a common format for
defining any new IPv6 extension headers, if they are needed.  
[STANDARDS-TRACK]

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

This is now a Proposed Standard Protocol.

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/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
Association Management Solutions, LLC