Skip to main content

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 Downref
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 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 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
RFC 8955 Dissemination of Flow Specification Rules
References Referenced by
Proposed Standard informatively references
RFC 8969 A Framework for Automating Service and Network Management with YANG
References Referenced by
Informational informatively references
RFC 9050 Path Computation Element Communication Protocol (PCEP) Procedures and Extensions for Using the PCE as a Central Controller (PCECC) of LSPs
References Referenced by
Proposed Standard informatively references
RFC 9168 Path Computation Element Communication Protocol (PCEP) Extension for Flow Specification
References Referenced by
Proposed Standard informatively references
RFC 9182 A YANG Network Data Model for Layer 3 VPNs
References Referenced by
Proposed Standard informatively references