Skip to main content

Explicit Congestion Notification (ECN) and Congestion Feedback Using the Network Service Header (NSH) and IPFIX

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
Authors Donald E. Eastlake 3rd , Bob Briscoe , Yizhou Li , Andrew G. Malis , Xinpeng Wei
Last updated 2023-04-03 (Latest revision 2022-09-30)
Replaces draft-eastlake-sfc-nsh-ecn-support
RFC stream Internet Engineering Task Force (IETF)
Additional resources Mailing list discussion
Stream WG state 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:


Explicit Congestion Notification (ECN) allows a forwarding element to notify downstream devices of the onset of congestion without having to drop packets. Coupled with a means to feed information about congestion back to upstream nodes, this can improve network efficiency through better congestion control, frequently without packet drops. This document specifies ECN and congestion feedback support within a Service Function Chaining (SFC) enabled domain through use of the Network Service Header (NSH, RFC 8300) and IP Flow Information Export (IPFIX, RFC 7011) protocol.


Donald E. Eastlake 3rd
Bob Briscoe
Yizhou Li
Andrew G. Malis
Xinpeng Wei

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