ECN Interactions with IP Tunnels
draft-ietf-tsvwg-ecn-tunnels-00
| Document | Type |
Expired Internet-Draft
(tsvwg WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Sally Floyd, Dr. K. K. Ramakrishnan | ||
| Last updated | 2023-03-01 (Latest revision 2000-11-07) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Dead WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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 encapsulation of IP packet headers in tunnels is used in many places, including IPsec and IP in IP [RFC2003]. Explicit Congestion Notification (ECN) is an experimental addition to the IP architecture that uses the ECN field in the IP header to provide an indication of the onset of congestion to applications. ECN provides this congestion indication to enable end-node adaptation to network conditions without the use of dropped packets [RFC 2481]. Currently, the ECN specification does not accommodate the constraints imposed by some of these pre-existing specifications for tunnels. This document considers issues related to interactions between ECN and IP tunnels, and proposes two alternative solutions
Authors
Sally Floyd
Dr. K. K. Ramakrishnan
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)