References from draft-li-teas-hierarchy-ip-controllers

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 206	Problem Statement and Architecture for Information Exchange between Interconnected Traffic-Engineered Networks References Referenced by	Best Current Practice	informatively references
draft-dhodylee-pce-pcep-ls	PCEP extensions for Distribution of Link-State and TE Information References Referenced by		informatively references
draft-dugeon-pce-stateful-interdomain	PCEP Extension for Stateful Inter-Domain Tunnels References Referenced by		informatively references
draft-ietf-bess-evpn-yang	Yang Data Model for EVPN References Referenced by		informatively references
draft-ietf-bess-l2vpn-yang	YANG Data Model for MPLS-based L2VPN References Referenced by	Proposed Standard	informatively references
draft-ietf-bess-l3vpn-yang	Yang Data Model for BGP/MPLS L3 VPNs References Referenced by		informatively references
draft-ietf-idr-bgp-model	BGP YANG Model for Service Provider Networks References Referenced by	Proposed Standard	informatively references
draft-ietf-idr-rtc-hierarchical-rr	Extensions to RT-Constrain in Hierarchical Route Reflection Scenarios References Referenced by		informatively references
draft-ietf-mpls-seamless-mpls	Seamless MPLS Architecture References Referenced by	Informational	informatively references
draft-ietf-opsawg-l3sm-l3nm	A Layer 3 VPN Network YANG Model References Referenced by	Proposed Standard	informatively references
draft-ietf-opsawg-model-automation-framework	A Framework for Automating Service and Network Management with YANG References Referenced by	Informational	informatively references
draft-ietf-pce-pcep-extension-for-pce-controller	PCEP Procedures and Protocol Extensions for Using PCE as a Central Controller (PCECC) of LSPs References Referenced by		informatively references
draft-ietf-pce-pcep-flowspec	PCEP Extension for Flow Specification References Referenced by	Proposed Standard	informatively references
draft-ietf-teas-actn-yang	Applicability of YANG models for Abstraction and Control of Traffic Engineered Networks References Referenced by		informatively references
draft-ietf-teas-te-service-mapping-yang	Traffic Engineering (TE) and Service Mapping Yang Model References Referenced by		informatively references
draft-ietf-teas-yang-path-computation	Yang model for requesting Path Computation References Referenced by		informatively references
draft-ietf-teas-yang-te	A YANG Data Model for Traffic Engineering Tunnels, Label Switched Paths and Interfaces References Referenced by		informatively references
draft-luo-grow-bgp-controller-based-ts	Traffic Steering Based on BGP Controller References Referenced by		informatively references
draft-wu-idr-flowspec-yang-cfg	A YANG Data Model for Flow Specification References Referenced by		informatively references
RFC 2238	Definitions of Managed Objects for HPR using SMIv2 References Referenced by	Proposed Standard	informatively references
RFC 3630	Traffic Engineering (TE) Extensions to OSPF Version 2 References Referenced by	Proposed Standard	informatively references
RFC 4110	A Framework for Layer 3 Provider-Provisioned Virtual Private Networks (PPVPNs) References Referenced by	Informational	informatively references
RFC 4271	A Border Gateway Protocol 4 (BGP-4) References Referenced by	Draft Standard	informatively references
RFC 4456	BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP) References Referenced by	Draft Standard	informatively references
RFC 4655	A Path Computation Element (PCE)-Based Architecture References Referenced by	Informational	informatively references
RFC 4664	Framework for Layer 2 Virtual Private Networks (L2VPNs) References Referenced by	Informational	informatively references
RFC 4684	Constrained Route Distribution for Border Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS) Internet Protocol (IP) Virtual Private Networks (VPNs) References Referenced by	Proposed Standard	informatively references
RFC 5152	A Per-Domain Path Computation Method for Establishing Inter-Domain Traffic Engineering (TE) Label Switched Paths (LSPs) References Referenced by	Proposed Standard	informatively references
RFC 5305	IS-IS Extensions for Traffic Engineering References Referenced by	Proposed Standard	informatively references
RFC 5440	Path Computation Element (PCE) Communication Protocol (PCEP) References Referenced by	Proposed Standard	informatively references
RFC 5441	A Backward-Recursive PCE-Based Computation (BRPC) Procedure to Compute Shortest Constrained Inter-Domain Traffic Engineering Label Switched Paths References Referenced by	Proposed Standard	informatively references
RFC 5575	Dissemination of Flow Specification Rules References Referenced by	Proposed Standard	informatively references
RFC 6241	Network Configuration Protocol (NETCONF) References Referenced by	Proposed Standard	informatively references
RFC 6805	The Application of the Path Computation Element Architecture to the Determination of a Sequence of Domains in MPLS and GMPLS References Referenced by	Informational	informatively references
RFC 7432	BGP MPLS-Based Ethernet VPN References Referenced by	Proposed Standard	informatively references
RFC 7491	A PCE-Based Architecture for Application-Based Network Operations References Referenced by	Informational	informatively references
RFC 7752	North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP References Referenced by	Proposed Standard	informatively references
RFC 7854	BGP Monitoring Protocol (BMP) References Referenced by	Proposed Standard	informatively references
RFC 7926	Problem Statement and Architecture for Information Exchange between Interconnected Traffic-Engineered Networks References Referenced by	Best Current Practice	informatively references
RFC 8040	RESTCONF Protocol References Referenced by	Proposed Standard	informatively references
RFC 8051	Applicability of a Stateful Path Computation Element (PCE) References Referenced by	Informational	informatively references
RFC 8231	Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE References Referenced by	Proposed Standard	informatively 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	informatively references
RFC 8283	An Architecture for Use of PCE and the PCE Communication Protocol (PCEP) in a Network with Central Control References Referenced by	Informational	informatively references
RFC 8299	YANG Data Model for L3VPN Service Delivery References Referenced by	Proposed Standard	informatively references
RFC 8309	Service Models Explained References Referenced by	Informational	informatively references
RFC 8345	A YANG Data Model for Network Topologies References Referenced by	Proposed Standard	informatively references
RFC 8453	Framework for Abstraction and Control of TE Networks (ACTN) References Referenced by	Informational	normatively references
RFC 8466	A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) Service Delivery References Referenced by	Proposed Standard	informatively references
RFC 8637	Applicability of the Path Computation Element (PCE) to the Abstraction and Control of TE Networks (ACTN) References Referenced by	Informational	informatively references
RFC 8751	Hierarchical Stateful Path Computation Element (PCE) References Referenced by	Informational	informatively references
RFC 8795	YANG Data Model for Traffic Engineering (TE) Topologies References Referenced by	Proposed Standard	informatively references