RFC 3708 on Using TCP Duplicate Selective Acknowledgement (DSACKs) and Stream Control Transmission Protocol (SCTP) Duplicate Transmission Sequence Numbers (TSNs) to Detect Spurious Retransmissions

rfc-editor@rfc-editor.org Thu, 26 February 2004 20:05 UTC

Message-Id: <200402261951.i1QJpbk11264@gamma.isi.edu>
To: IETF-Announce: ;
Subject: RFC 3708 on Using TCP Duplicate Selective Acknowledgement (DSACKs) and Stream Control Transmission Protocol (SCTP) Duplicate Transmission Sequence Numbers (TSNs) to Detect Spurious Retransmissions
Cc: rfc-editor@rfc-editor.org, tsvwg@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Thu, 26 Feb 2004 11:51:37 -0800
Sender: owner-ietf-announce@ietf.org
Precedence: bulk

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


        RFC 3708

        Title:      Using TCP Duplicate Selective Acknowledgement
                    (DSACKs) and Stream Control Transmission Protocol
                    (SCTP) Duplicate Transmission Sequence Numbers
                    (TSNs) to Detect Spurious Retransmissions
        Author(s):  E. Blanton, M. Allman
        Status:     Experimental
        Date:       February 2004
        Mailbox:    eblanton@cs.purdue.edu, mallman@icir.org
        Pages:      9
        Characters: 20818
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-tsvwg-dsack-use-02.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3708.txt


TCP and Stream Control Transmission Protocol (SCTP) provide
notification of duplicate segment receipt through Duplicate Selective
Acknowledgement (DSACKs) and Duplicate Transmission Sequence Number
(TSN) notification, respectively.  This document presents conservative
methods of using this information to identify unnecessary
retransmissions for various applications.

This document is a product of the Transport Area Working Group Working
Group of the IETF.

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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

ftp://ftp.isi.edu/in-notes/rfc3708.txt"><ftp://ftp.isi.edu/in-notes/rfc3708.txt>

RFC 3708 on Using TCP Duplicate Selective Acknowl… rfc-editor