References from rfc8242

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 Downref
BCP 14 Key words for use in RFCs to Indicate Requirement Levels
References Referenced by
Best Current Practice informatively references
draft-ietf-i2rs-protocol-security-requirements Interface to the Routing System (I2RS) Security-Related Requirements
References Referenced by
Informational normatively references
draft-ietf-i2rs-security-environment-reqs I2RS Environment Security Requirements
References Referenced by
normatively references
draft-ietf-netconf-restconf RESTCONF Protocol
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 informatively references
RFC 6241 Network Configuration Protocol (NETCONF)
References Referenced by
Proposed Standard normatively references
RFC 6614 Transport Layer Security (TLS) Encryption for RADIUS
References Referenced by
Experimental normatively references
RFC 6733 Diameter Base Protocol
References Referenced by
Proposed Standard normatively references
RFC 7920 Problem Statement for the Interface to the Routing System
References Referenced by
Informational normatively references
RFC 7921 An Architecture for the Interface to the Routing System
References Referenced by
Informational normatively references
RFC 7922 Interface to the Routing System (I2RS) Traceability: Framework and Information Model
References Referenced by
Informational normatively references
RFC 7923 Requirements for Subscription to YANG Datastores
References Referenced by
Informational normatively references
RFC 7950 The YANG 1.1 Data Modeling Language
References Referenced by
Proposed Standard normatively references