References from draft-ietf-pce-pcep-stateful-pce-gmpls

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
draft-ietf-pce-gmpls-pcep-extensions	Path Computation Element Communication Protocol (PCEP) Extensions for GMPLS References Referenced by	Proposed Standard	normatively references
RFC 2119	Key words for use in RFCs to Indicate Requirement Levels References Referenced by	Best Current Practice	normatively references
RFC 3471	Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description References Referenced by	Proposed Standard	informatively references
RFC 3473	Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions References Referenced by	Proposed Standard	informatively references
RFC 3477	Signalling Unnumbered Links in Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE) References Referenced by	Proposed Standard	informatively references
RFC 4208	Generalized Multiprotocol Label Switching (GMPLS) User-Network Interface (UNI): Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Support for the Overlay Model References Referenced by	Proposed Standard	informatively references
RFC 4655	A Path Computation Element (PCE)-Based Architecture References Referenced by	Informational	informatively references
RFC 4872	RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) Recovery References Referenced by	Proposed Standard	informatively references
RFC 4873	GMPLS Segment Recovery References Referenced by	Proposed Standard	informatively references
RFC 5440	Path Computation Element (PCE) Communication Protocol (PCEP) References Referenced by	Proposed Standard	normatively references
RFC 5511	Routing Backus-Naur Form (RBNF): A Syntax Used to Form Encoding Rules in Various Routing Protocol Specifications References Referenced by	Proposed Standard	informatively references
RFC 5520	Preserving Topology Confidentiality in Inter-Domain Path Computation Using a Path-Key-Based Mechanism References Referenced by	Proposed Standard	informatively references
RFC 5521	Extensions to the Path Computation Element Communication Protocol (PCEP) for Route Exclusions References Referenced by	Proposed Standard	normatively references
RFC 6387	GMPLS Asymmetric Bandwidth Bidirectional Label Switched Paths (LSPs) References Referenced by	Proposed Standard	informatively references
RFC 7025	Requirements for GMPLS Applications of PCE References Referenced by	Informational	informatively references
RFC 7399	Unanswered Questions in the Path Computation Element Architecture References Referenced by	Informational	informatively references
RFC 8051	Applicability of a Stateful Path Computation Element (PCE) References Referenced by	Informational	informatively 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 8232	Optimizations of Label Switched Path State Synchronization Procedures for a 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	normatively references
RFC 8282	Extensions to the Path Computation Element Communication Protocol (PCEP) for Inter-Layer MPLS and GMPLS Traffic Engineering References Referenced by	Proposed Standard	informatively references