ECN Interactions with IP Tunnels
draft-floyd-ecn-tunnels-01

Document Type Expired Internet-Draft (individual)
Authors Sally Floyd , K. Ramakrishnan 
Last updated 2000-10-30
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-floyd-ecn-tunnels-01.txt

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 with 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 (floyd@icir.org)
K. Ramakrishnan (kkrama@research.att.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)