Retransmission Timeout Requirements
draft-ietf-tcpm-rto-consider-05
| The information below is for an old version of the document | |||||
|---|---|---|---|---|---|
| Document | Type | Expired Internet-Draft (tcpm WG) | |||
| Author | Mark Allman | ||||
| Last updated | 2017-09-11 (latest revision 2017-03-10) | ||||
| Replaces | draft-allman-tcpm-rto-consider | ||||
| Stream | IETF | ||||
| Intended RFC status | Best Current Practice | ||||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||||
| Reviews | |||||
| Additional Resources |
|
||||
| Stream | WG state | WG Document (wg milestone: May 2020 - Submit document on R... ) | |||
| Document shepherd | No shepherd assigned | ||||
| IESG | IESG state | Expired (IESG: Dead) | |||
| Consensus Boilerplate | Unknown | ||||
| Telechat date | |||||
| Responsible AD | Mirja Kühlewind | ||||
| Send notices to | (None) | ||||
https://www.ietf.org/archive/id/draft-ietf-tcpm-rto-consider-05.txt
Abstract
Ensuring reliable communication often manifests in a timeout and retry mechanism. Each implementation of a retransmission timeout mechanism represents a balance between correctness and timeliness and therefore no implementation suits all situations. This document provides high-level requirements for retransmission timeout schemes appropriate for general use in the Internet. Within the requirements, implementations have latitude to define particulars that best address each situation. Terminology
Authors
Mark Allman (mallman@icir.org)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)