Using TCP DSACKs and SCTP Duplicate TSNs to Detect Spurious Retransmissions
draft-blanton-dsack-use-02
| Document | Type |
Expired Internet-Draft
(individual in gen area)
Expired & archived
|
|
|---|---|---|---|
| Authors | Ethan Blanton , Mark Allman | ||
| Last updated | 2015-10-14 (Latest revision 2002-11-04) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | WG state | (None) | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Action Holders |
(None)
|
||
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Jon Peterson | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
TCP and SCTP provide notification of duplicate segment receipt through DSACK and Duplicate TSN notification, respectively. This document presents a conservative method of using this information to identify unnecessary retransmissions.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)