Propagating Explicit Congestion Notification Across IP Tunnel Headers Separated by a Shim
draft-briscoe-tsvwg-rfc6040bis-01

Document Type Replaced Internet-Draft (tsvwg WG)
Last updated 2016-08-08 (latest revision 2016-07-08)
Replaced by draft-ietf-tsvwg-rfc6040update-shim, draft-briscoe-tsvwg-rfc6040update-shim
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state Adopted by a WG
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-tsvwg-rfc6040update-shim, draft-briscoe-tsvwg-rfc6040update-shim
Consensus Boilerplate Unknown
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-rfc6040bis-01.txt

Abstract

RFC 6040 on "Tunnelling of Explicit Congestion Notification" made the rules for propagation of ECN consistent for all forms of IP in IP tunnel. This specification extends the scope of RFC 6040 to include tunnels where two IP headers are separated by a shim header that cannot stand alone.

Authors

Bob Briscoe (ietf@bobbriscoe.net)

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