References from draft-tissa-lime-yang-oam-model

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
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 4379 Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures
References Referenced by
Proposed Standard informatively references
RFC 4443 Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification
References Referenced by
Internet Standard informatively references
RFC 4656 A One-way Active Measurement Protocol (OWAMP)
References Referenced by
Proposed Standard informatively references
RFC 5357 A Two-Way Active Measurement Protocol (TWAMP)
References Referenced by
Proposed Standard informatively 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 6371 Operations, Administration, and Maintenance Framework for MPLS-Based Transport Networks
References Referenced by
Informational informatively references
RFC 6374 Packet Loss and Delay Measurement for MPLS Networks
References Referenced by
Proposed Standard informatively references
RFC 6428 Proactive Connectivity Verification, Continuity Check, and Remote Defect Indication for the MPLS Transport Profile
References Referenced by
Proposed Standard Possible Reference
RFC 6536 Network Configuration Protocol (NETCONF) Access Control Model
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 7456 Loss and Delay Measurement in Transparent Interconnection of Lots of Links (TRILL)
References Referenced by
Proposed Standard informatively references
RFC 792 Internet Control Message Protocol
References Referenced by
Internet Standard normatively references