References from RFC 9451
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 6291 |
Guidelines for the Use of the "OAM" Acronym in the IETF
References Referenced by |
Best Current Practice | informatively references | |
| RFC 7276 |
An Overview of Operations, Administration, and Maintenance (OAM) Tools
References Referenced by |
Informational | informatively references | |
| RFC 7665 |
Service Function Chaining (SFC) Architecture
References Referenced by |
Informational | informatively references | |
| RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
| RFC 8300 |
Network Service Header (NSH)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 8924 |
Service Function Chaining (SFC) Operations, Administration, and Maintenance (OAM) Framework
References Referenced by |
Informational | informatively references | |
| RFC 8979 |
Subscriber and Performance Policy Identifier Context Headers in the Network Service Header (NSH)
References Referenced by |
Proposed Standard | informatively references | |
| RFC 9145 |
Integrity Protection for the Network Service Header (NSH) and Encryption of Sensitive Context Headers
References Referenced by |
Proposed Standard | normatively references | |
| RFC 9263 |
Network Service Header (NSH) Metadata Type 2 Variable-Length Context Headers
References Referenced by |
Proposed Standard | informatively references |