References from rfc8531

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 normatively references
BCP 161 Guidelines for the Use of the "OAM" Acronym in the IETF
References Referenced by
Best Current Practice informatively references
draft-ietf-lime-yang-connectionless-oam Generic YANG Data Model for the Management of Operations, Administration, and Maintenance (OAM) Protocols That Use Connectionless Communications
References Referenced by
Proposed Standard informatively 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-trill-yang TRILL YANG Data Model
References Referenced by
Proposed Standard informatively references
draft-ietf-trill-yang-oam YANG Data Model for TRILL Operations, Administration, and Maintenance (OAM)
References Referenced by
Proposed Standard informatively references
draft-zhang-mpls-tp-yang-oam YANG Data Model for MPLS-TP Operations, Administration, and Maintenance (OAM)
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 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 6291 Guidelines for the Use of the "OAM" Acronym in the IETF
References Referenced by
Best Current Practice informatively references
RFC 6325 Routing Bridges (RBridges): Base Protocol Specification
References Referenced by
Proposed Standard informatively references
RFC 6370 MPLS Transport Profile (MPLS-TP) Identifiers
References Referenced by
Proposed Standard normatively references
RFC 6371 Operations, Administration, and Maintenance Framework for MPLS-Based Transport Networks
References Referenced by
Informational informatively references
RFC 6536 Network Configuration Protocol (NETCONF) Access Control Model
References Referenced by
Proposed Standard normatively references
RFC 6905 Requirements for Operations, Administration, and Maintenance (OAM) in Transparent Interconnection of Lots of Links (TRILL)
References Referenced by
Informational informatively references
RFC 6991 Common YANG Data Types
References Referenced by
Proposed Standard normatively references
RFC 7174 Transparent Interconnection of Lots of Links (TRILL) Operations, Administration, and Maintenance (OAM) Framework
References Referenced by
Informational informatively references
RFC 7276 An Overview of Operations, Administration, and Maintenance (OAM) Tools
References Referenced by
Informational informatively references
RFC 7455 Transparent Interconnection of Lots of Links (TRILL): Fault Management
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