Using TCP Duplicate Selective Acknowledgement (DSACKs) and Stream Control Transmission Protocol (SCTP) Duplicate Transmission Sequence Numbers (TSNs) to Detect Spurious Retransmissions
draft-ietf-tsvwg-dsack-use-02

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>,
    RFC Editor <rfc-editor@rfc-editor.org>
Subject: Document Action: 'Using TCP DSACKs and SCTP Duplicate 
         TSNs to Detect Spurious Retransmissions' to Experimental RFC 

The IESG has approved the following document:

- 'Using TCP DSACKs and SCTP Duplicate TSNs to Detect Spurious 
   Retransmissions '
   <draft-ietf-tsvwg-dsack-use-03.txt> as an Experimental RFC

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

The IESG contact persons are Jon Peterson and Magnus Westerlund.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-dsack-use-03.txt

Ballot Text

Technical Summary
 
TCP and SCTP provide notification of duplicate segment receipt through 
DSACK and Duplicate TSN notification, respectively. This document shows
conservative methods of using this information to identify unnecessary 
retransmissions for various applications. This document does not, however
outline what a TCP or SCTP sender should do after a spurious 
retransmission is detected. It is hoped that future work building on the 
detection of spurious transmissions will make TCP and SCTP more robust
to reordererd packets.
 
Working Group Summary
 
The TSVWG supports this protocol going forward, and is investigating 
several proposals that rely on the detection of spurious retransmissions
which might benefit from this work.
 
Protocol Quality
 
This document was reviewed for the IESG by Allison Mankin and Jon Peterson.

RFC Editor Note