RFC 8511 on TCP Alternative Backoff with ECN (ABE)
rfc-editor@rfc-editor.org Tue, 18 December 2018 21:48 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98BA71312A8; Tue, 18 Dec 2018 13:48:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 fErFxgTbhHCC; Tue, 18 Dec 2018 13:48:16 -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 1E56A1312A1; Tue, 18 Dec 2018 13:48:15 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 4CED7B80C36; Tue, 18 Dec 2018 13:47:52 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8511 on TCP Alternative Backoff with ECN (ABE)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, tcpm@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20181218214752.4CED7B80C36@rfc-editor.org>
Date: Tue, 18 Dec 2018 13:47:52 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/dKHyRBtZQIo97BsctuqFYpEIK7I>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Dec 2018 21:48:22 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8511
Title: TCP Alternative Backoff with ECN (ABE)
Author: N. Khademi,
M. Welzl,
G. Armitage,
G. Fairhurst
Status: Experimental
Stream: IETF
Date: December 2018
Mailbox: naeemk@ifi.uio.no,
michawe@ifi.uio.no,
garmitage@netflix.com,
gorry@erg.abdn.ac.uk
Pages: 12
Characters: 27408
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-tcpm-alternativebackoff-ecn-12.txt
URL: https://www.rfc-editor.org/info/rfc8511
DOI: 10.17487/RFC8511
Active Queue Management (AQM) mechanisms allow for burst tolerance
while enforcing short queues to minimise the time that packets spend
enqueued at a bottleneck. This can cause noticeable performance
degradation for TCP connections traversing such a bottleneck,
especially if there are only a few flows or their bandwidth-delay
product (BDP) is large. The reception of a Congestion Experienced
(CE) Explicit Congestion Notification (ECN) mark indicates that an
AQM mechanism is used at the bottleneck, and the bottleneck network
queue is therefore likely to be short. Feedback of this signal
allows the TCP sender-side ECN reaction in congestion avoidance to
reduce the Congestion Window (cwnd) by a smaller amount than the
congestion control algorithm's reaction to inferred packet loss.
Therefore, this specification defines an experimental change to the
TCP reaction specified in RFC 3168, as permitted by RFC 8311.
This document is a product of the TCP Maintenance and Minor Extensions Working Group of the IETF.
EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community. It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
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