Options for Conex marking in IPv6 packets
draft-krishnan-conex-ipv6-02
| Document | Type |
Expired Internet-Draft
(individual in tsv area)
Expired & archived
|
|
|---|---|---|---|
| Authors | Suresh Krishnan , Mirja Kühlewind , Carlos Ucendo | ||
| Last updated | 2015-10-14 (Latest revision 2011-03-14) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | WG state | (None) | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Action Holders |
(None)
|
||
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Wesley Eddy | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Conex is a mechanism by which senders inform the network about the congestion encountered by packets earlier in the same flow. This document describes the requirements for conex markings in IPv6 datagrams and describes the various options for performing conex markings in IPv6.
Authors
Suresh Krishnan
Mirja Kühlewind
Carlos Ucendo
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)