References from RFC 8453

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 206	References Referenced by		informatively references
draft-ietf-teas-actn-requirements	Requirements for Abstraction and Control of TE Networks References Referenced by	Informational	informatively references
draft-ietf-teas-actn-vn-yang	A YANG Data Model for Virtual Network (VN) Operations References Referenced by	Proposed Standard	informatively references
draft-ietf-teas-yang-te-topo	YANG Data Model for Traffic Engineering (TE) Topologies References Referenced by	Proposed Standard	informatively references
RFC 2702	Requirements for Traffic Engineering Over MPLS References Referenced by	Informational	informatively references
RFC 3945	Generalized Multi-Protocol Label Switching (GMPLS) Architecture References Referenced by	Proposed Standard	informatively references
RFC 4655	A Path Computation Element (PCE)-Based Architecture References Referenced by	Informational	informatively references
RFC 5654	Requirements of an MPLS Transport Profile References Referenced by	Proposed Standard	informatively references
RFC 7149	Software-Defined Networking: A Perspective from within a Service Provider Environment References Referenced by	Informational	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 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 8309	Service Models Explained References Referenced by	Informational	informatively references