[tcpm] RFC 5827 on Early Retransmit for and Stream Control Transmission Protocol (SCTP)

rfc-editor@rfc-editor.org Mon, 26 April 2010 23:50 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 869FB28C194; Mon, 26 Apr 2010 16:50:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.328
X-Spam-Level:
X-Spam-Status: No, score=-2.328 tagged_above=-999 required=5 tests=[AWL=0.272, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KxZhy+l1vRTC; Mon, 26 Apr 2010 16:50:27 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 4BF513A69EA; Mon, 26 Apr 2010 16:50:26 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A8B1BE07E8; Mon, 26 Apr 2010 16:50:14 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20100426235014.A8B1BE07E8@rfc-editor.org>
Date: Mon, 26 Apr 2010 16:50:14 -0700 (PDT)
Cc: tcpm@ietf.org, rfc-editor@rfc-editor.org
Subject: [tcpm] RFC 5827 on Early Retransmit for and Stream Control Transmission Protocol (SCTP)
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Mon, 26 Apr 2010 23:50:28 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5827

        Title:      Early Retransmit for and Stream 
                    Control Transmission Protocol (SCTP) 
        Author:     M. Allman, K. Avrachenkov,
                    U. Ayesta, J. Blanton,
                    P. Hurtig
        Status:     Experimental
        Stream:     IETF
        Date:       April 2010
        Mailbox:    mallman@icir.org, 
                    k.avrachenkov@sophia.inria.fr, 
                    urtzi@laas.fr,  jblanton@irg.cs.ohiou.edu, 
                    per.hurtig@kau.se
        Pages:      15
        Characters: 35383
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tcpm-early-rexmt-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5827.txt

This document proposes a new mechanism for TCP and Stream Control 
Transmission Protocol (SCTP) that can be used to recover lost segments 
when a connection's congestion window is small.  The "Early Retransmit" 
mechanism allows the transport to reduce, in certain special 
circumstances, the number of duplicate acknowledgments required to trigger 
a fast retransmission.  This allows the transport to use fast retransmit 
to recover segment losses that would otherwise require a lengthy 
retransmission timeout.  [STANDARDS TRACK]

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
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

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