RFC 8257 on Data Center TCP (DCTCP): TCP Congestion Control for Data Centers
rfc-editor@rfc-editor.org Tue, 17 October 2017 23:28 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 CA0571331E3; Tue, 17 Oct 2017 16:28:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 J6PpMgX93KEM; Tue, 17 Oct 2017 16:28:10 -0700 (PDT)
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 1CE1F13319E; Tue, 17 Oct 2017 16:28:10 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id E24A1B812E7; Tue, 17 Oct 2017 16:27:48 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8257 on Data Center TCP (DCTCP): TCP Congestion Control for Data Centers
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
Message-Id: <20171017232748.E24A1B812E7@rfc-editor.org>
Date: Tue, 17 Oct 2017 16:27:48 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/iwdPYzQskUq7neV3G49Xuk9zKbc>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
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, 17 Oct 2017 23:28:12 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8257
Title: Data Center TCP (DCTCP): TCP Congestion Control
for Data Centers
Author: S. Bensley,
D. Thaler,
P. Balasubramanian,
L. Eggert,
G. Judd
Status: Informational
Stream: IETF
Date: October 2017
Mailbox: sbens@microsoft.com,
dthaler@microsoft.com,
pravb@microsoft.com,
lars@netapp.com,
glenn.judd@morganstanley.com
Pages: 17
Characters: 37357
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-tcpm-dctcp-10.txt
URL: https://www.rfc-editor.org/info/rfc8257
DOI: 10.17487/RFC8257
This Informational RFC describes Data Center TCP (DCTCP): a TCP
congestion control scheme for data-center traffic. DCTCP extends the
Explicit Congestion Notification (ECN) processing to estimate the
fraction of bytes that encounter congestion rather than simply
detecting that some congestion has occurred. DCTCP then scales the
TCP congestion window based on this estimate. This method achieves
high-burst tolerance, low latency, and high throughput with shallow-
buffered switches. This memo also discusses deployment issues
related to the coexistence of DCTCP and conventional TCP, discusses
the lack of a negotiating mechanism between sender and receiver, and
presents some possible mitigations. This memo documents DCTCP as
currently implemented by several major operating systems. DCTCP, as
described in this specification, is applicable to deployments in
controlled environments like data centers, but it must not be
deployed over the public Internet without additional measures.
This document is a product of the TCP Maintenance and Minor Extensions 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