RFC 7765 on TCP and Stream Control Transmission Protocol (SCTP) RTO Restart
rfc-editor@rfc-editor.org Thu, 11 February 2016 19:12 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC83B1B394F; Thu, 11 Feb 2016 11:12:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.903
X-Spam-Level:
X-Spam-Status: No, score=-106.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 cD9ia-uevMbq; Thu, 11 Feb 2016 11:12:35 -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 E24D21B3958; Thu, 11 Feb 2016 11:12:34 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id D7109180471; Thu, 11 Feb 2016 11:11:56 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7765 on TCP and Stream Control Transmission Protocol (SCTP) RTO Restart
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160211191156.D7109180471@rfc-editor.org>
Date: Thu, 11 Feb 2016 11:11:56 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/zt3nHvjT8l8bA84VgO7LhHyP_qE>
Cc: tcpm@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
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: Thu, 11 Feb 2016 19:12:36 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7765
Title: TCP and Stream Control Transmission
Protocol (SCTP) RTO Restart
Author: P. Hurtig, A. Brunstrom,
A. Petlund, M. Welzl
Status: Experimental
Stream: IETF
Date: February 2016
Mailbox: per.hurtig@kau.se,
anna.brunstrom@kau.se,
apetlund@simula.no,
michawe@ifi.uio.no
Pages: 15
Characters: 35361
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-tcpm-rtorestart-10.txt
URL: https://www.rfc-editor.org/info/rfc7765
DOI: http://dx.doi.org/10.17487/RFC7765
This document describes a modified sender-side algorithm for managing
the TCP and Stream Control Transmission Protocol (SCTP)
retransmission timers that provides faster loss recovery when there
is a small amount of outstanding data for a connection. The
modification, RTO Restart (RTOR), allows the transport to restart its
retransmission timer using a smaller timeout duration, so that the
effective retransmission timeout (RTO) becomes more aggressive in
situations where fast retransmit cannot be used. This enables faster
loss detection and recovery for connections that are short lived or
application limited.
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