References from draft-aguado-opsawg-l3sm-l3nm
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 215 |
References Referenced by |
informatively references | ||
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 6241 |
Network Configuration Protocol (NETCONF)
References Referenced by |
Proposed Standard | informatively references | |
RFC 7950 |
The YANG 1.1 Data Modeling Language
References Referenced by |
Proposed Standard | informatively references | |
RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | informatively references | |
RFC 8299 |
YANG Data Model for L3VPN Service Delivery
References Referenced by |
Proposed Standard | informatively references | |
RFC 8309 |
Service Models Explained
References Referenced by |
Informational | informatively references | |
RFC 8340 |
YANG Tree Diagrams
References Referenced by |
Best Current Practice | informatively references | |
RFC 8453 |
Framework for Abstraction and Control of TE Networks (ACTN)
References Referenced by |
Informational | informatively references | |
RFC 8466 |
A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) Service Delivery
References Referenced by |
Proposed Standard | informatively references |