Browse Prior Art Database

Relaxing Restrictions on Explicit Congestion Notification (ECN) Experimentation (RFC8311)

IP.com Disclosure Number: IPCOM000252462D
Original Publication Date: 2018-Jan-01
Included in the Prior Art Database: 2018-Jan-13
Document File: 40 page(s) / 48K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

D. Black: AUTHOR

Abstract

This memo updates RFC 3168 [RFC3168], which specifies Explicit Congestion Notification (ECN) as an alternative to packet drops for indicating network congestion to endpoints. It relaxes restrictions in RFC 3168 that hinder experimentation towards benefits beyond just removal of loss. This memo summarizes the proposed areas of experimentation and updates RFC 3168 to enable experimentation in these areas. An Experimental RFC in the IETF document stream [RFC4844] is required to take advantage of any of these enabling updates. Putting all of these updates into a single document enables experimentation to proceed without requiring a standards process exception for each Experimental RFC that needs changes to RFC 3168, a Proposed Standard RFC.

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)                          D. Black Request for Comments: 8311                                      Dell EMC Updates: 3168, 4341, 4342, 5622, 6679                       January 2018 Category: Standards Track ISSN: 2070-1721

                         Relaxing Restrictions on          Explicit Congestion Notification (ECN) Experimentation

Abstract

   This memo updates RFC 3168, which specifies Explicit Congestion    Notification (ECN) as an alternative to packet drops for indicating    network congestion to endpoints.  It relaxes restrictions in RFC 3168    that hinder experimentation towards benefits beyond just removal of    loss.  This memo summarizes the anticipated areas of experimentation    and updates RFC 3168 to enable experimentation in these areas.  An    Experimental RFC in the IETF document stream is required to take    advantage of any of these enabling updates.  In addition, this memo    makes related updates to the ECN specifications for RTP in RFC 6679    and for the Datagram Congestion Control Protocol (DCCP) in RFCs 4341,    4342, and 5622.  This memo also records the conclusion of the ECN    nonce experiment in RFC 3540 and provides the rationale for    reclassification of RFC 3540 from Experimental to Historic; this    reclassification enables new experimental use of the ECT(1)    codepoint.

Status of This Memo

   This is an Internet Standards Track document.

   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).  Further information on    Internet Standards is available in 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    https://www.rfc-editor.org/info/rfc8311.

 Black                        Standards Track                    [Page 1]
 RFC 8311                   ECN Experimentation              January 2018

 Copyright Notice

   Copyright (c) 2018 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    (https://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.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Lega...