References from draft-li-ippm-ioam-common-encap-procedures
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 |
|---|---|---|---|---|
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
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 8200 |
Internet Protocol, Version 6 (IPv6) Specification
References Referenced by |
Internet Standard | normatively references | |
| RFC 8300 |
Network Service Header (NSH)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 9197 |
Data Fields for In Situ Operations, Administration, and Maintenance (IOAM)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 9326 |
In Situ Operations, Administration, and Maintenance (IOAM) Direct Exporting
References Referenced by |
Proposed Standard | normatively references | |
| RFC 9378 |
In Situ Operations, Administration, and Maintenance (IOAM) Deployment
References Referenced by |
Informational | normatively references | |
| RFC 9452 |
Network Service Header (NSH) Encapsulation for In Situ OAM (IOAM) Data
References Referenced by |
Proposed Standard | normatively references | |
| RFC 9486 |
IPv6 Options for In Situ Operations, Administration, and Maintenance (IOAM)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 9617 |
A YANG Data Model for In Situ Operations, Administration, and Maintenance (IOAM)
References Referenced by |
Proposed Standard | normatively references |