References from draft-allman-rto-backoff
These dependencies are extracted using heuristics looking for strings with particular prefixes. Notably, this means that references to I-Ds by title only are not reflected here. If it's really important, please inspect the documents' references sections directly.
Document | Title | Status | Type | Downref |
---|---|---|---|---|
BCP 14 |
References Referenced by |
normatively references | ||
BCP 78 |
References Referenced by |
informatively references | ||
RFC 1323 |
TCP Extensions for High Performance
References Referenced by |
Proposed Standard | informatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 2988 |
Computing TCP's Retransmission Timer
References Referenced by |
Proposed Standard | normatively references | |
RFC 3517 |
A Conservative Selective Acknowledgment (SACK)-based Loss Recovery Algorithm for TCP
References Referenced by |
Proposed Standard | informatively references | |
RFC 3522 |
The Eifel Detection Algorithm for TCP
References Referenced by |
Experimental | normatively references | |
RFC 3708 |
Using TCP Duplicate Selective Acknowledgement (DSACKs) and Stream Control Transmission Protocol (SCTP) Duplicate Transmission Sequence Numbers (TSNs) to Detect Spurious Retransmissions
References Referenced by |
Experimental | normatively references | |
RFC 3782 |
The NewReno Modification to TCP's Fast Recovery Algorithm
References Referenced by |
Proposed Standard | informatively references | |
RFC 4015 |
The Eifel Response Algorithm for TCP
References Referenced by |
Proposed Standard | informatively references | |
RFC 4138 |
Forward RTO-Recovery (F-RTO): An Algorithm for Detecting Spurious Retransmission Timeouts with TCP and the Stream Control Transmission Protocol (SCTP)
References Referenced by |
Experimental | normatively references |