References from draft-www-opsawg-yang-vpn-service-pm

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 215 YANG Tree Diagrams
References Referenced by
Best Current Practice normatively references
draft-ietf-netconf-yang-push Subscription to YANG Notifications for Datastore Updates
References Referenced by
Proposed Standard informatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
References Referenced by
Best Current Practice normatively references
RFC 3393 IP Packet Delay Variation Metric for IP Performance Metrics (IPPM)
References Referenced by
Proposed Standard normatively references
RFC 3688 The IETF XML Registry
References Referenced by
Best Current Practice normatively references
RFC 4176 Framework for Layer 3 Virtual Private Networks (L3VPN) Operations and Management
References Referenced by
Informational 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 6370 MPLS Transport Profile (MPLS-TP) Identifiers
References Referenced by
Proposed Standard normatively references
RFC 6374 Packet Loss and Delay Measurement for MPLS Networks
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 7471 OSPF Traffic Engineering (TE) Metric Extensions
References Referenced by
Proposed Standard informatively references
RFC 7810 IS-IS Traffic Engineering (TE) Metric Extensions
References Referenced by
Proposed Standard informatively 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
RFC 7952 Defining and Using Metadata with YANG
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
RFC 8233 Extensions to the Path Computation Element Communication Protocol (PCEP) to Compute Service-Aware Label Switched Paths (LSPs)
References Referenced by
Proposed Standard informatively references
RFC 8299 YANG Data Model for L3VPN Service Delivery
References Referenced by
Proposed Standard informatively references
RFC 8340 YANG Tree Diagrams
References Referenced by
Best Current Practice normatively references
RFC 8345 A YANG Data Model for Network Topologies
References Referenced by
Proposed Standard normatively references
RFC 8532 Generic YANG Data Model for the Management of Operations, Administration, and Maintenance (OAM) Protocols That Use Connectionless Communications
References Referenced by
Proposed Standard normatively references
RFC 8571 BGP - Link State (BGP-LS) Advertisement of IGP Traffic Engineering Performance Metric Extensions
References Referenced by
Proposed Standard informatively references