References from rfc8792
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 215 |
YANG Tree Diagrams References Referenced by |
Best Current Practice | informatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels References Referenced by |
Best Current Practice | normatively references | |
RFC 6020 |
YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF) References Referenced by |
Proposed Standard | informatively references | |
RFC 7749 |
The "xml2rfc" Version 2 Vocabulary References Referenced by |
Informational | informatively references | |
RFC 7950 |
The YANG 1.1 Data Modeling Language References Referenced by |
Proposed Standard | informatively references | |
RFC 7991 |
The "xml2rfc" Version 3 Vocabulary References Referenced by |
Informational | normatively references | |
RFC 7994 |
Requirements for Plain-Text RFCs 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 8340 |
YANG Tree Diagrams References Referenced by |
Best Current Practice | informatively references |