Browse Prior Art Database

The Benefits of Using Explicit Congestion Notification (ECN) (RFC8087) Disclosure Number: IPCOM000249617D
Original Publication Date: 2017-Mar-01
Included in the Prior Art Database: 2017-Mar-08
Document File: 38 page(s) / 46K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

G. Fairhurst: AUTHOR [+1]


Internet transports (such as TCP and Stream Control Transmission Protocol (SCTP)) are implemented in endpoints (Internet hosts) and are designed to detect and react to network congestion. Congestion may be detected by loss of an IP packet or, if Explicit Congestion Notification (ECN) [RFC3168] is enabled, by the reception of a packet with a Congestion Experienced (CE) marking in the IP header. Both of these are treated by transports as indications of congestion. ECN may also be enabled by other transports: UDP applications that provide congestion control may enable ECN when they are able to correctly process the ECN signals [RFC8085] (e.g., ECN with RTP [RFC6679]).

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 6% of the total text.

Internet Engineering Task Force (IETF)                      G. Fairhurst Request for Comments: 8087                        University of Aberdeen Category: Informational                                         M. Welzl ISSN: 2070-1721                                       University of Oslo                                                               March 2017

       The Benefits of Using Explicit Congestion Notification (ECN)


   The goal of this document is to describe the potential benefits of    applications using a transport that enables Explicit Congestion    Notification (ECN).  The document outlines the principal gains in    terms of increased throughput, reduced delay, and other benefits when    ECN is used over a network path that includes equipment that supports    Congestion Experienced (CE) marking.  It also discusses challenges    for successful deployment of ECN.  It does not propose new algorithms    to use ECN nor does it describe the details of implementation of ECN    in endpoint devices (Internet hosts), routers, or other network    devices.

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for informational purposes.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Not all documents    approved by the IESG are a candidate for any level of Internet    Standard; see Section 2 of RFC 7841.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at

 Fairhurst & Welzl             Informational                     [Page 1]
 RFC 8087                     Benefits of ECN                  March 2017

 Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    ( in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Provisions and are provided without warranty as    described in the Simplified BSD License.

Table of Contents