Using the Flow Label for Transport Signaling
draft-donley-6man-flowlabel-transport-sig-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Chris Donley , Kirk Erichsen | ||
| Last updated | 2010-03-01 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
This document extends the use of the IPv6 Flow Label to include transport header and port information. The inclusion of these details allows for the application of Quality of Service (QoS) classification and prioritization, and permits hardware acceleration of IP traffic flows encapsulated within other protocols such as Dual- Stack Lite, Generic Routing Encapsulation (GRE) and Layer 2 Tunneling Protocol version 3 (L2TPv3).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)