Explicit Congestion Notification (ECN) and Congestion Feedback Using the Network Service Header (NSH)
draft-eastlake-sfc-nsh-ecn-support-03

Document Type Replaced Internet-Draft (sfc WG)
Last updated 2019-02-05
Replaced by draft-ietf-sfc-nsh-ecn-support
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state Candidate for WG Adoption
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-sfc-nsh-ecn-support
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-eastlake-sfc-nsh-ecn-support-03.txt

Abstract

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 back information about congestion 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) domain through use of the Network Service Header (NSH, RFC 8300) and IP Flow Information Export (IPFIX, draft-ietf-tsvwg-tunnel-congestion-feedback).

Authors

Donald Eastlake (d3e3e3@gmail.com)
Bob Briscoe (ietf@bobbriscoe.net)
Andrew Malis (agmalis@gmail.com)

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