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.

Reference type help

Document	Title	Status	Type
BCP 14	Key words for use in RFCs to Indicate Requirement Levels References Referenced by	Best Current Practice	Possible Reference
draft-acee-rtgwg-yang-rib-extend	RIB YANG Data Model References Referenced by		informatively references
draft-ietf-i2rs-usecase-reqs-summary	Summary of I2RS Use Case Requirements References Referenced by		informatively references
draft-ietf-i2rs-yang-network-topo	A YANG Data Model for Network Topologies References Referenced by	Proposed Standard	normatively references
draft-ietf-netmod-revised-datastores	Network Management Datastore Architecture (NMDA) References Referenced by	Proposed Standard	informatively references
draft-ietf-netmod-yang-tree-diagrams	YANG Tree Diagrams References Referenced by	Best Current Practice	informatively references
draft-ietf-teas-yang-te-topo	YANG Data Model for Traffic Engineering (TE) Topologies References Referenced by	Proposed Standard	informatively references
RFC 1195	Use of OSI IS-IS for routing in TCP/IP and dual environments References Referenced by	Proposed Standard	normatively references
RFC 2119	Key words for use in RFCs to Indicate Requirement Levels References Referenced by	Best Current Practice	normatively references
RFC 2328	OSPF Version 2 References Referenced by	Internet Standard	normatively references
RFC 2863	The Interfaces Group MIB References Referenced by	Draft Standard	normatively references
RFC 3688	The IETF XML Registry References Referenced by	Best Current Practice	normatively references
RFC 5246	The Transport Layer Security (TLS) Protocol Version 1.2 References Referenced by	Proposed Standard	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 6536	Network Configuration Protocol (NETCONF) Access Control Model References Referenced by	Proposed Standard	normatively references
RFC 6991	Common YANG Data Types References Referenced by	Proposed Standard	normatively references
RFC 7223	A YANG Data Model for Interface Management 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 8022	A YANG Data Model for Routing Management References Referenced by	Proposed Standard	informatively references
RFC 8040	RESTCONF Protocol 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 8242	Interface to the Routing System (I2RS) Ephemeral State Requirements References Referenced by	Informational	informatively references
RFC 8294	Common YANG Data Types for the Routing Area References Referenced by	Proposed Standard	normatively references