Layered Encapsulation of Congestion Notification
draft-briscoe-tsvwg-ecn-tunnel-01

 
Document Type Replaced Internet-Draft (individual)
Last updated 2008-07-14
Replaced by draft-ietf-tsvwg-ecn-tunnel
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-tsvwg-ecn-tunnel
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-briscoe-tsvwg-ecn-tunnel-01.txt

Abstract

This document redefines how the explicit congestion notification (ECN) field of the outer IP header of a tunnel should be constructed. It brings all IP in IP tunnels (v4 or v6) into line with the way IPsec tunnels now construct the ECN field. It includes a thorough analysis of the reasoning for this change and the implications. It also gives guidelines on the encapsulation of IP congestion notification by any outer header, whether encapsulated in an IP tunnel or in a lower layer header. Following these guidelines should help interworking, if the IETF or other standards bodies specify any new encapsulation of congestion notification.

Authors

Bob Briscoe (bob.briscoe@bt.com)

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