Tunnelling of Explicit Congestion Notification
RFC 6040, “Tunnelling of Explicit Congestion Notification”, is a Proposed Standard document published in November 2010 by B. Briscoe. It updates RFC 3168, RFC 4301, RFC 4774. It has since been updated by RFC 9601. The canonical text is published by the RFC Editor.
Abstract
This document redefines how the explicit congestion notification (ECN) field of the IP header should be constructed on entry to and exit from any IP-in-IP tunnel. On encapsulation, it updates RFC 3168 to bring all IP-in-IP tunnels (v4 or v6) into line with RFC 4301 IPsec ECN processing. On decapsulation, it updates both RFC 3168 and RFC 4301 to add new behaviours for previously unused combinations of inner and outer headers. The new rules ensure the ECN field is correctly propagated across a tunnel whether it is used to signal one or two severity levels of congestion; whereas before, only one severity level was supported. Tunnel endpoints can be updated in any order without affecting pre-existing uses of the ECN field, thus ensuring backward compatibility. Nonetheless, operators wanting to support two severity levels (e.g., for pre-congestion notification -- PCN) can require compliance with this new specification. A thorough analysis of the reasoning for these changes and the implications is included. In the unlikely event that the new rules do not meet a specific need, RFC 4774 gives guidance on designing alternate ECN semantics, and this document extends that to include tunnelling issues. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 6040 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6039 Issues with Existing Cryptographic Protection Methods for Routing Protocols
- RFC 6041 Forwarding and Control Element Separation Applicability Statement
- RFC 6038 Two-Way Active Measurement Protocol Reflect Octets and Symmetrical Size Features
- RFC 6042 Transport Layer Security Authorization Using KeyNote
- RFC 6037 Cisco Systems' Solution for Multicast in BGP/MPLS IP VPNs
- RFC 6036 Emerging Service Provider Scenarios for IPv6 Deployment
- RFC 6044 Mapping and Interworking of Diversion Information between Diversion and History-Info Headers in the Session Initiation Protocol
- RFC 6035 Session Initiation Protocol Event Package for Voice Quality Reporting