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) | |
|---|---|---|---|
| Authors | Ethan Blanton , Mark Allman | ||
| Last updated | 2015-10-14 (latest revision 2002-11-04) | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | WG state | (None) | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Action Holders |
(None)
|
||
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Jon Peterson | ||
| Send notices to | (None) | ||
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-blanton-dsack-use-02.txt
https://www.ietf.org/archive/id/draft-blanton-dsack-use-02.txt
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
Ethan Blanton
(eblanton@cs.purdue.edu)
Mark Allman
(mallman@bbn.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)