References from rfc8346
This is an experimental product. 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 Refs Ref'd by |
Best Current Practice | Possible Reference | |
| draft-acee-rtgwg-yang-rib-extend |
RIB YANG Data Model Refs Ref'd by |
informatively references | ||
| draft-ietf-i2rs-usecase-reqs-summary |
Summary of I2RS Use Case Requirements Refs Ref'd by |
informatively references | ||
| draft-ietf-i2rs-yang-network-topo |
A YANG Data Model for Network Topologies Refs Ref'd by |
Proposed Standard | normatively references | |
| draft-ietf-netmod-revised-datastores |
Network Management Datastore Architecture (NMDA) Refs Ref'd by |
Proposed Standard | informatively references | |
| draft-ietf-netmod-yang-tree-diagrams |
YANG Tree Diagrams Refs Ref'd by |
Best Current Practice | informatively references | |
| draft-ietf-teas-yang-te-topo |
YANG Data Model for Traffic Engineering (TE) Topologies Refs Ref'd by |
Proposed Standard | informatively references | |
| RFC 1195 |
Use of OSI IS-IS for routing in TCP/IP and dual environments Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | normatively references | |
| RFC 2328 |
OSPF Version 2 Refs Ref'd by |
Internet Standard | normatively references | |
| RFC 2863 |
The Interfaces Group MIB Refs Ref'd by |
Draft Standard | normatively references | |
| RFC 3688 |
The IETF XML Registry Refs Ref'd by |
Best Current Practice | normatively references | |
| RFC 5246 |
The Transport Layer Security (TLS) Protocol Version 1.2 Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 6020 |
YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF) Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 6241 |
Network Configuration Protocol (NETCONF) Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 6242 |
Using the NETCONF Protocol over Secure Shell (SSH) Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 6536 |
Network Configuration Protocol (NETCONF) Access Control Model Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 6991 |
Common YANG Data Types Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 7223 |
A YANG Data Model for Interface Management Refs Ref'd by |
Proposed Standard | informatively references | |
| RFC 7950 |
The YANG 1.1 Data Modeling Language Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 7951 |
JSON Encoding of Data Modeled with YANG Refs Ref'd by |
Proposed Standard | informatively references | |
| RFC 8022 |
A YANG Data Model for Routing Management Refs Ref'd by |
Proposed Standard | informatively references | |
| RFC 8040 |
RESTCONF Protocol Refs Ref'd by |
Proposed Standard | informatively references | |
| RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words Refs Ref'd by |
Best Current Practice | informatively references | |
| RFC 8242 |
Interface to the Routing System (I2RS) Ephemeral State Requirements Refs Ref'd by |
Informational | informatively references | |
| RFC 8294 |
Common YANG Data Types for the Routing Area Refs Ref'd by |
Proposed Standard | normatively references |