RFC 6437 on IPv6 Flow Label Specification

rfc-editor@rfc-editor.org Tue, 01 November 2011 23:18 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 D452C21F9D90; Tue, 1 Nov 2011 16:18:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.055
X-Spam-Level:
X-Spam-Status: No, score=-104.055 tagged_above=-999 required=5 tests=[AWL=1.022, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, J_CHICKENPOX_93=0.6, RCVD_IN_DNSWL_MED=-4, 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 5DlsXWG7lJyY; Tue, 1 Nov 2011 16:18:55 -0700 (PDT)
Received: from rfc-editor.org (rfcpa.amsl.com [12.22.58.47]) by ietfa.amsl.com (Postfix) with ESMTP id 5F1C221F9D89; Tue, 1 Nov 2011 16:18:55 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 680ABB1E016; Tue, 1 Nov 2011 16:14:34 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6437 on IPv6 Flow Label Specification
From: rfc-editor@rfc-editor.org
Message-Id: <20111101231434.680ABB1E016@rfc-editor.org>
Date: Tue, 01 Nov 2011 16:14:34 -0700
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, 01 Nov 2011 23:18:55 -0000

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

        
        RFC 6437

        Title:      IPv6 Flow Label Specification 
        Author:     S. Amante, B. Carpenter,
                    S. Jiang, J. Rajahalme
        Status:     Standards Track
        Stream:     IETF
        Date:       November 2011
        Mailbox:    shane@level3.net, 
                    brian.e.carpenter@gmail.com, 
                    jiangsheng@huawei.com,
                    jarno.rajahalme@nsn.com
        Pages:      15
        Characters: 35269
        Obsoletes:  RFC3697
        Updates:    RFC2205, RFC2460

        I-D Tag:    draft-ietf-6man-flow-3697bis-07.txt

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

This document specifies the IPv6 Flow Label field and the minimum
requirements for IPv6 nodes labeling flows, IPv6 nodes forwarding
labeled packets, and flow state establishment methods.  Even when
mentioned as examples of possible uses of the flow labeling, more
detailed requirements for specific use cases are out of the scope for
this document.

The usage of the Flow Label field enables efficient IPv6 flow
classification based only on IPv6 main header fields in fixed
positions.  [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