References from draft-ietf-ippm-stamp-option-tlv
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 | |
| BCP 26 |
Guidelines for Writing an IANA Considerations Section in RFCs References Referenced by |
Best Current Practice | normatively references | |
| RFC 2104 |
HMAC: Keyed-Hashing for Message Authentication References Referenced by |
Informational | informatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels References Referenced by |
Best Current Practice | normatively references | |
| RFC 4868 |
Using HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512 with IPsec References Referenced by |
Proposed Standard | informatively 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 | informatively 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 8762 |
Simple Two-Way Active Measurement Protocol References Referenced by |
Proposed Standard | normatively references |