[tcpm] RFC 8312 on CUBIC for Fast Long-Distance Networks
rfc-editor@rfc-editor.org Thu, 08 February 2018 03:21 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0105212D7E2; Wed, 7 Feb 2018 19:21:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 GjvG_tBNK-Iq; Wed, 7 Feb 2018 19:21:24 -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 05B8412D77D; Wed, 7 Feb 2018 19:21:24 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 3E8A0B816E6; Wed, 7 Feb 2018 19:21: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
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, tcpm@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180208032115.3E8A0B816E6@rfc-editor.org>
Date: Wed, 07 Feb 2018 19:21:15 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/8b6_4zIDG0SomXF7_JXK6mPMyLs>
Subject: [tcpm] RFC 8312 on CUBIC for Fast Long-Distance Networks
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm/>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Feb 2018 03:21:26 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8312
Title: CUBIC for Fast Long-Distance Networks
Author: I. Rhee,
L. Xu,
S. Ha,
A. Zimmermann,
L. Eggert,
R. Scheffenegger
Status: Informational
Stream: IETF
Date: February 2018
Mailbox: rhee@ncsu.edu,
xu@unl.edu,
sangtae.ha@colorado.edu,
alexander.zimmermann@rwth-aachen.de,
lars@netapp.com,
rs.ietf@gmx.at
Pages: 18
Characters: 42194
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-tcpm-cubic-07.txt
URL: https://www.rfc-editor.org/info/rfc8312
DOI: 10.17487/RFC8312
CUBIC is an extension to the current TCP standards. It differs from
the current TCP standards only in the congestion control algorithm on
the sender side. In particular, it uses a cubic function instead of
a linear window increase function of the current TCP standards to
improve scalability and stability under fast and long-distance
networks. CUBIC and its predecessor algorithm have been adopted as
defaults by Linux and have been used for many years. This document
provides a specification of CUBIC to enable third-party
implementations and to solicit community feedback through
experimentation on the performance of CUBIC.
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