Requirements for Time-Based Loss Detection
Metadata
- Publisher
- IETF
- Doc Type
- Best Practice
- Pages
- 12
- Abstract
- Many protocols must detect packet loss for various reasons (e.g., to ensure reliability using retransmissions or to understand the level of congestion along a network path). While many mechanisms have been designed to detect loss, ultimately, protocols can only count on the passage of time without delivery confirmation to declare a packet "lost". Each implementation of a time-based loss detection mechanism represents a balance between correctness and timeliness; therefore, no implementation suits all situations. This document provides high-level requirements for time-based loss detectors appropriate for general use in unicast communication across the Internet. Within the requirements, implementations have latitude to define particulars that best address each situation.
- Publication Date
- 2020-11-01
- Status Note
- Best Current Practice
- DOI
10.17487/RFC8961- Link
- https://doi.org/10.17487/RFC8961
- Author(s)
- Mark Allman
- Keyword(s)
- RTO, Packet Loss, Loss Detection
Latest version of IETF RFC 8961
Document Versions — IETF RFC 8961
-
▶ IETF RFC 8961 (2020-11-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 8174 [Active*]
Bibliographic Reference(s)
- 10.1145-52325.52356 — Jac88 EXTERNAL
- IETF.draft-dukkipati-tcpm-tcp-loss-probe-01 — I-D.dukkipati-tcpm-tcp-loss-probe EXTERNAL
- IETF.draft-ietf-quic-recovery-32 — I-D.ietf-quic-recovery EXTERNAL
- IETF.draft-ietf-tcpm-rack-13 — I-D.ietf-tcpm-rack EXTERNAL
- Allman, M. and V. Paxson, "On Estimating End-to-End Network Path Properties", Proceedings of the ACM SIGCOMM Technical Symposium, September 1999. EXTERNAL
- Karn, P. and C. Partridge, "Improving Round-Trip Time Estimates in Reliable Transport Protocols", SIGCOMM 87. EXTERNAL
- IETF RFC 1034 [Active*]
- IETF RFC 1035 [Active, Amended*]
- IETF RFC 2018 [Active*]
- IETF RFC 2140 [Superseded*]
- IETF RFC 2883 [Active*]
- IETF RFC 3124 [Active*]
- IETF RFC 3261 [Active*]
- IETF RFC 3522 [Active*]
- IETF RFC 3708 [Active*]
- IETF RFC 4960 [Superseded*]
- IETF RFC 5681 [Active*]
- IETF RFC 5682 [Active*]
- IETF RFC 5740 [Active*]
- IETF RFC 6182 [Active*]
- IETF RFC 6298 [Active*]
- IETF RFC 6675 [Active*]
- IETF RFC 7323 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC8961.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 8961, Requirements for Time-Based Loss Detection. Available at https://doi.org/10.17487/RFC8961
Snippet:
IETF RFC 8961, Requirements for Time-Based Loss Detection. Available at https://doi.org/10.17487/RFC8961
HTML (ISO 690 compliant)
Preview:
IETF RFC 8961, Requirements for Time-Based Loss Detection. Available at https://doi.org/10.17487/RFC8961
Snippet:
<span class="citation"><cite>IETF RFC 8961</cite>, Requirements for Time-Based Loss Detection. Available at <a href="https://doi.org/10.17487/RFC8961" target="_blank" rel="noopener">https://doi.org/10.17487/RFC8961</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 8961, Requirements for Time-Based Loss Detection
doi: 10.17487/RFC8961
url: https://doi.org/10.17487/RFC8961
doi: 10.17487/RFC8961
url: https://doi.org/10.17487/RFC8961
Snippet:
<li> <cite id="bib-rfc8961">IETF RFC 8961</cite>, Requirements for Time-Based Loss Detection <span class="doi">10.17487/RFC8961</span> </li>
Referenced By
- IETF RFC 9028 [Active*]
- IETF RFC 9293 [Active*]
- IETF RFC 9743 [Active*]