References from draft-li-pce-pcep-srv6-yang

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	normatively references
BCP 215	YANG Tree Diagrams References Referenced by	Best Current Practice	normatively references
draft-ietf-pce-pcep-yang	A YANG Data Model for Path Computation Element Communications Protocol (PCEP) References Referenced by		normatively references
draft-ietf-pce-segment-routing-ipv6	PCEP Extensions for Segment Routing leveraging the IPv6 data plane References Referenced by		normatively references
draft-ietf-spring-sr-policy-yang	YANG Data Model for Segment Routing Policy References Referenced by		normatively references
draft-raza-spring-srv6-yang	YANG Data Model for SRv6 Base and Static References Referenced by		normatively 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 4655	A Path Computation Element (PCE)-Based Architecture References Referenced by	Informational	informatively references
RFC 5440	Path Computation Element (PCE) Communication Protocol (PCEP) 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 7420	Path Computation Element Communication Protocol (PCEP) Management Information Base (MIB) Module References Referenced by	Proposed Standard	informatively references
RFC 7950	The YANG 1.1 Data Modeling Language References Referenced by	Proposed Standard	normatively 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
RFC 8231	Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE References Referenced by	Proposed Standard	normatively references
RFC 8281	Path Computation Element Communication Protocol (PCEP) Extensions for PCE-Initiated LSP Setup in a Stateful PCE Model References Referenced by	Proposed Standard	normatively references
RFC 8340	YANG Tree Diagrams References Referenced by	Best Current Practice	normatively references
RFC 8341	Network Configuration Access Control Model References Referenced by	Internet Standard	normatively references
RFC 8342	Network Management Datastore Architecture (NMDA) References Referenced by	Proposed Standard	informatively references
RFC 8349	A YANG Data Model for Routing Management (NMDA Version) References Referenced by	Proposed Standard	normatively references
RFC 8408	Conveying Path Setup Type in PCE Communication Protocol (PCEP) Messages References Referenced by	Proposed Standard	normatively references
RFC 8446	The Transport Layer Security (TLS) Protocol Version 1.3 References Referenced by	Proposed Standard	normatively references
RFC 8664	Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing References Referenced by	Proposed Standard	normatively references
RFC 8776	Common YANG Data Types for Traffic Engineering References Referenced by	Proposed Standard	normatively references
STD 91	Network Configuration Access Control Model References Referenced by	Internet Standard	normatively references