Proposal for a New Flow Label Definition
draft-chakravorty-bcc-flowlabel-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Sham Chakravorty | ||
Last updated | 2005-04-18 | ||
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
The IPv6 header includes a 20-bit Flow Label field. RFC 3697, "IPv6 Flow Label Specification" [1] specified this field and minimum requirements for using the field. This document first identifies several issues related to the current Flow Label specification; then it discusses the limitations of the current specification and the need for extending the definition to accommodate emerging applications and protocols; finally, a new Flow Label specification is proposed that enables more effective usage of this field.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)