Browse Prior Art Database

Really Explicit Congestion Notification (RECN) (RFC7514)

IP.com Disclosure Number: IPCOM000241188D
Original Publication Date: 2015-Apr-01
Included in the Prior Art Database: 2015-Apr-02
Document File: 10 page(s) / 10K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Luckie: AUTHOR

Abstract

The deployment of Explicit Congestion Notification (ECN) [RFC3168] remains stalled. While most operating systems support ECN, it is currently disabled by default because of fears that enabling ECN will break transport protocols. This document proposes a new ICMP message that a router or host may use to advise a host to reduce the rate at which it sends, in cases where the host ignores other signals such as packet loss and ECN. We call this message the "Really Explicit Congestion Notification" (RECN) message because it delivers a less subtle indication of congestion than packet loss and ECN.

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

Independent Submission                                         M. Luckie Request for Comments: 7514                                         CAIDA Category: Experimental                                      1 April 2015 ISSN: 2070-1721

              Really Explicit Congestion Notification (RECN)

Abstract

   This document proposes a new ICMP message that a router or host may    use to advise a host to reduce the rate at which it sends, in cases    where the host ignores other signals provided by packet loss and    Explicit Congestion Notification (ECN).

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for examination, experimental implementation, and    evaluation.

   This document defines an Experimental Protocol for the Internet    community.  This is a contribution to the RFC Series, independently    of any other RFC stream.  The RFC Editor has chosen to publish this    document at its discretion and makes no statement about its value for    implementation or deployment.  Documents approved for publication by    the RFC Editor are not a candidate for any level of Internet    Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7514.

Copyright Notice

   Copyright (c) 2015 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    (http://trustee.ietf.org/license-info) 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.

Luckie                        Experimental                      [Page 1]
 RFC 7514                          RECN                      1 April 2015

 Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2      1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   2    2.  RECN Message Format . . . . . . . . . . . . . . . . . . . . .   2      2.1.  Advice to Implementers  . . . . . . . . . . . . . . . . .   3      2.2.  Relationship to ICMP Source Quench  . . . . . . . . . . .   4    3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4    4.  Security Considerations . . . . . . . . . . . . . . . . . . .   4    5.  Normative References  . . . . . . . . . . . . . . . . . . . .   4    Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

...