Using the IPv6 flow label for equal cost multipath routing and link aggregation in tunnels
draft-carpenter-flow-ecmp-03
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Shane Amante , Brian E. Carpenter | ||
| Last updated | 2011-03-28 (Latest revision 2010-10-07) | ||
| Replaced by | draft-ietf-6man-flow-ecmp | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-6man-flow-ecmp | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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 tunneled traffic.
Authors
Shane Amante
Brian E. Carpenter
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)