datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

Using the IPv6 Flow Label for Equal Cost Multipath Routing and Link Aggregation in Tunnels
draft-ietf-6man-flow-ecmp-05

RFC
Document Stream: IETF
Last updated: 2011-07-22
Replaces: draft-carpenter-flow-ecmp
Intended RFC status: Proposed Standard
Other versions: (expired, archived): plain text, pdf, html
IETF State: WG Document (6man)
Document shepherd:(None)
Shepherd writeup
Consensus:Unknown
IESG State: RFC 6438
IANA Action State: No IC 
Responsible AD: Jari Arkko
IESG Note: Brian Haberman (brian@innovationslab.net) is the document shepherd for this document.
Send notices to: 6man-chairs@tools.ietf.org, draft-ietf-6man-flow-ecmp@tools.ietf.org

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-6man-flow-ecmp.

Abstract:
The IPv6 flow label has certain restrictions on its use. This document describes how those restrictions apply when using the flow label for load balancing by equal cost multipath routing and for link aggregation, particularly for IP-in-IPv6 tunneled traffic. [STANDARDS-TRACK]

Authors:
Brian Carpenter <brian.e.carpenter@gmail.com>
Shane Amante <shane@level3.net>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)