References from draft-mirsky-ippm-stamp
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 26 |
References Referenced by |
normatively references | ||
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 4656 |
A One-way Active Measurement Protocol (OWAMP)
References Referenced by |
Proposed Standard | normatively references | |
RFC 5357 |
A Two-Way Active Measurement Protocol (TWAMP)
References Referenced by |
Proposed Standard | normatively references | |
RFC 5905 |
Network Time Protocol Version 4: Protocol and Algorithms Specification
References Referenced by |
Proposed Standard | normatively references | |
RFC 6038 |
Two-Way Active Measurement Protocol (TWAMP) Reflect Octets and Symmetrical Size Features
References Referenced by |
Proposed Standard | normatively references | |
RFC 8126 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | normatively references | |
RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
RFC 8186 |
Support of the IEEE 1588 Timestamp Format in a Two-Way Active Measurement Protocol (TWAMP)
References Referenced by |
Proposed Standard | normatively references |