[aqm] RFC 8087 on The Benefits of Using Explicit Congestion Notification (ECN)
rfc-editor@rfc-editor.org Tue, 07 March 2017 22:18 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1115112961E; Tue, 7 Mar 2017 14:18:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GN94iaKrzFtz; Tue, 7 Mar 2017 14:18:33 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C071B12963E; Tue, 7 Mar 2017 14:18:16 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 387A5B819B3; Tue, 7 Mar 2017 14:18:15 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170307221815.387A5B819B3@rfc-editor.org>
Date: Tue, 07 Mar 2017 14:18:15 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/aqm/P9HLeKnYIIXdW2ounjQsEKwEeNQ>
Cc: drafts-update-ref@iana.org, aqm@ietf.org, rfc-editor@rfc-editor.org
Subject: [aqm] RFC 8087 on The Benefits of Using Explicit Congestion Notification (ECN)
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discussion list for active queue management and flow isolation." <aqm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aqm>, <mailto:aqm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Mar 2017 22:18:35 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8087
Title: The Benefits of Using Explicit
Congestion Notification (ECN)
Author: G. Fairhurst, M. Welzl
Status: Informational
Stream: IETF
Date: March 2017
Mailbox: gorry@erg.abdn.ac.uk,
michawe@ifi.uio.no
Pages: 19
Characters: 46449
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-aqm-ecn-benefits-08.txt
URL: https://www.rfc-editor.org/info/rfc8087
DOI: 10.17487/RFC8087
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.
This document is a product of the Active Queue Management and Packet Scheduling Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC