Skip to main content

Requirements for Time-Based Loss Detection
RFC 8961 also known as BCP 233

Revision differences

Document history

Date By Action
2023-12-12
(System) Imported membership of rfc8961 in bcp233 via sync to the rfc-index
2023-12-12
(System) No history of BCP233 is currently available in the datatracker before this point
2021-04-30
Bernie Volz Closed request for Telechat review by INTDIR with state 'Overtaken by Events'
2021-02-04
Gunter Van de Velde Closed request for Last Call review by OPSDIR with state 'Overtaken by Events'
2020-11-23
(System)
Received changes through RFC Editor sync (created alias RFC 8961, changed abstract to 'Many protocols must detect packet loss for various reasons (e.g., to …
Received changes through RFC Editor sync (created alias RFC 8961, changed abstract to '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.', changed standardization level to Best Current Practice, changed state to RFC, added RFC published event at 2020-11-23, changed IESG state to RFC Published, created alias BCP 233)
2020-11-23
(System) RFC published