References from draft-dugeon-pce-stateful-interdomain

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	informatively references
draft-dong-pce-discovery-proto-bgp	BGP Extensions for Path Computation Element (PCE) Discovery References Referenced by		informatively references
draft-ietf-idr-bgpls-segment-routing-epe	BGP-LS extensions for Segment Routing BGP Egress Peer Engineering References Referenced by	Proposed Standard	informatively references
draft-ietf-pce-association-group	Path Computation Element Communication Protocol (PCEP) Extensions for Establishing Relationships between Sets of Label Switched Paths (LSPs) References Referenced by	Proposed Standard	informatively references
draft-ietf-pce-segment-routing	Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing References Referenced by	Proposed Standard	informatively references
draft-ietf-pce-stateful-hpce	Hierarchical Stateful Path Computation Element (PCE) References Referenced by	Informational	informatively references
RFC 2119	Key words for use in RFCs to Indicate Requirement Levels References Referenced by	Best Current Practice	informatively references
RFC 3209	RSVP-TE: Extensions to RSVP for LSP Tunnels 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 4003	GMPLS Signaling Procedure for Egress Control References Referenced by	Proposed Standard	informatively references
RFC 4206	Label Switched Paths (LSP) Hierarchy with Generalized Multi-Protocol Label Switching (GMPLS) Traffic Engineering (TE) References Referenced by	Proposed Standard	informatively references
RFC 4655	A Path Computation Element (PCE)-Based Architecture References Referenced by	Informational	informatively references
RFC 5150	Label Switched Path Stitching with Generalized Multiprotocol Label Switching Traffic Engineering (GMPLS TE) 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 5520	Preserving Topology Confidentiality in Inter-Domain Path Computation Using a Path-Key-Based Mechanism 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 8231	Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE References Referenced by	Proposed Standard	informatively references
RFC 8253	PCEPS: Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP) 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 8408	Conveying Path Setup Type in PCE Communication Protocol (PCEP) Messages References Referenced by	Proposed Standard	informatively references
RFC 8453	Framework for Abstraction and Control of TE Networks (ACTN) References Referenced by	Informational	informatively references