Update to the IPv6 flow label specification
draft-carpenter-6man-flow-update-04
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Shane Amante , Brian Carpenter , Sheng Jiang | ||
| Last updated | 2011-03-14 (latest revision 2010-09-16) | ||
| Replaced by | RFC 6436 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-6man-flow-update | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-carpenter-6man-flow-update-04.txt
Abstract
Various published proposals for use of the IPv6 flow label are incompatible with its existing 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 proposes changes to the specification in order to clarify it, making it clear what types of usage are possible, and to introduce some additional flexibility.
Authors
Shane Amante
(shane@level3.net)
Brian Carpenter
(brian.e.carpenter@gmail.com)
Sheng Jiang
(shengjiang@huawei.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)