References from rfc6349
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 |
Key words for use in RFCs to Indicate Requirement Levels References Referenced by |
Best Current Practice | normatively references | |
| RFC 1191 |
Path MTU discovery References Referenced by |
Draft Standard | normatively references | |
| RFC 1323 |
TCP Extensions for High Performance References Referenced by |
Proposed Standard | normatively references | |
| RFC 2018 |
TCP Selective Acknowledgment Options References Referenced by |
Proposed Standard | normatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels References Referenced by |
Best Current Practice | normatively references | |
| RFC 2544 |
Benchmarking Methodology for Network Interconnect Devices References Referenced by |
Informational | normatively references | |
| RFC 4656 |
A One-way Active Measurement Protocol (OWAMP) References Referenced by |
Proposed Standard | normatively references | |
| RFC 4821 |
Packetization Layer Path MTU Discovery References Referenced by |
Proposed Standard | normatively references | |
| RFC 4898 |
TCP Extended Statistics MIB References Referenced by |
Proposed Standard | normatively references | |
| RFC 5136 |
Defining Network Capacity References Referenced by |
Informational | normatively references | |
| RFC 5357 |
A Two-Way Active Measurement Protocol (TWAMP) References Referenced by |
Proposed Standard | normatively references | |
| RFC 5741 |
RFC Streams, Headers, and Boilerplates References Referenced by |
Informational | Possible Reference |