RFC 6436 on Rationale for Update to the 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 9A2BB21F9D3E; Tue, 1 Nov 2011 16:18:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.186
X-Spam-Level:
X-Spam-Status: No, score=-102.186 tagged_above=-999 required=5 tests=[AWL=0.414, BAYES_00=-2.599, 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 hFymnB+QSBWg; Tue, 1 Nov 2011 16:18:43 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 72C6C21F9CBB; Tue, 1 Nov 2011 16:18:41 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 7B777B1E012; Tue, 1 Nov 2011 16:14:20 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6436 on Rationale for Update to the IPv6 Flow Label Specification
From: rfc-editor@rfc-editor.org
Message-Id: <20111101231420.7B777B1E012@rfc-editor.org>
Date: Tue, 01 Nov 2011 16:14:20 -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:43 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6436
Title: Rationale for Update to the
IPv6 Flow Label Specification
Author: S. Amante, B. Carpenter,
S. Jiang
Status: Informational
Stream: IETF
Date: November 2011
Mailbox: shane@level3.net,
brian.e.carpenter@gmail.com,
shengjiang@huawei.com
Pages: 13
Characters: 28062
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-6man-flow-update-07.txt
URL: http://www.rfc-editor.org/rfc/rfc6436.txt
Various published proposals for use of the IPv6 flow label are
incompatible with its original specification in RFC 3697.
Furthermore, very little practical use is made of the flow label,
partly due to some uncertainties about the correct interpretation of
the specification. This document discusses and motivates changes to
the specification in order to clarify it and to introduce some
additional flexibility. This document is not an Internet Standards
Track specification; it is published for informational purposes.
This document is a product of the IPv6 Maintenance Working Group of the IETF.
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
Association Management Solutions, LLC