References from draft-ietf-teas-yang-sr-te-topo
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 | |
| draft-ietf-idr-bgp-ls-segment-routing-ext |
BGP Link-State extensions for Segment Routing References Referenced by |
Proposed Standard | informatively references | |
| draft-ietf-spring-sr-yang |
YANG Data Model for Segment Routing References Referenced by |
Proposed Standard | normatively references | |
| draft-ietf-teas-yang-te-topo |
YANG Data Model for Traffic Engineering (TE) Topologies References Referenced by |
Proposed Standard | informatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels References Referenced by |
Best Current Practice | normatively references | |
| RFC 3688 |
The IETF XML Registry 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 | normatively references | |
| RFC 6241 |
Network Configuration Protocol (NETCONF) References Referenced by |
Proposed Standard | normatively references | |
| RFC 6242 |
Using the NETCONF Protocol over Secure Shell (SSH) References Referenced by |
Proposed Standard | normatively references | |
| RFC 7752 |
North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP References Referenced by |
Proposed Standard | informatively references | |
| RFC 7950 |
The YANG 1.1 Data Modeling Language References Referenced by |
Proposed Standard | normatively references | |
| RFC 7951 |
JSON Encoding of Data Modeled with YANG References Referenced by |
Proposed Standard | informatively references | |
| RFC 8040 |
RESTCONF Protocol References Referenced by |
Proposed Standard | normatively 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 | |
| RFC 8341 |
Network Configuration Access Control Model References Referenced by |
Internet Standard | normatively references | |
| RFC 8342 |
Network Management Datastore Architecture (NMDA) References Referenced by |
Proposed Standard | normatively references | |
| RFC 8345 |
A YANG Data Model for Network Topologies References Referenced by |
Proposed Standard | normatively references | |
| RFC 8346 |
A YANG Data Model for Layer 3 Topologies References Referenced by |
Proposed Standard | normatively references | |
| RFC 8446 |
The Transport Layer Security (TLS) Protocol Version 1.3 References Referenced by |
Proposed Standard | normatively references | |
| RFC 8665 |
OSPF Extensions for Segment Routing References Referenced by |
Proposed Standard | informatively references | |
| RFC 8666 |
OSPFv3 Extensions for Segment Routing References Referenced by |
Proposed Standard | informatively references | |
| RFC 8667 |
IS-IS Extensions for Segment Routing References Referenced by |
Proposed Standard | informatively references | |
| STD 91 |
Network Configuration Access Control Model References Referenced by |
Internet Standard | normatively references |