Skip to main content

References to draft-ietf-pce-questions

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.

Showing RFCs and active Internet-Drafts, sorted by reference type, then document name.

Document Title Status Type Downref
RFC 8051
As rfc7399
Applicability of a Stateful Path Computation Element (PCE)
References Referenced by
Informational normatively references
draft-dhody-pce-pcep-extension-pce-controller-p2mp
As rfc7399
PCE Communication Protocol (PCEP) Extensions for Using the PCE as a Central Controller (PCECC) of point-to-multipoint (P2MP) LSPs
References Referenced by
informatively references
draft-ietf-pce-pcep-extension-pce-controller-sr
As rfc7399
PCE Communication Protocol (PCEP) Extensions for Using PCE as a Central Controller (PCECC) for Segment Routing (SR) MPLS Segment Identifier (SID) Allocation and Distribution.
References Referenced by
informatively references
draft-ietf-pce-pcep-extension-pce-controller-srv6
As rfc7399
PCE Communication Protocol (PCEP) Extensions for Using the PCE as a Central Controller (PCECC) for Segment Routing over IPv6 (SRv6) Segment Identifier (SID) Allocation and Distribution.
References Referenced by
informatively references
draft-ietf-pce-pcep-l2-flowspec
As rfc7399
PCEP Extension for Layer 2 (L2) Flow Specification
References Referenced by
informatively references
draft-ietf-pce-state-sync
As rfc7399
Inter Stateful Path Computation Element (PCE) Communication Procedures.
References Referenced by
informatively references
draft-ietf-teas-enhanced-vpn
As rfc7399
A Framework for NRP-based Enhanced Virtual Private Network
References Referenced by
Informational informatively references
draft-ietf-teas-pcecc-use-cases
As rfc7399
The Use Cases for Path Computation Element (PCE) as a Central Controller (PCECC).
References Referenced by
Informational informatively references
RFC 7926
As rfc7399
Problem Statement and Architecture for Information Exchange between Interconnected Traffic-Engineered Networks
References Referenced by
Best Current Practice informatively references
RFC 8283
As rfc7399
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 8413
As rfc7399
Framework for Scheduled Use of Resources
References Referenced by
Informational informatively references
RFC 8637
As rfc7399
Applicability of the Path Computation Element (PCE) to the Abstraction and Control of TE Networks (ACTN)
References Referenced by
Informational informatively references
RFC 8685
As rfc7399
Path Computation Element Communication Protocol (PCEP) Extensions for the Hierarchical Path Computation Element (H-PCE) Architecture
References Referenced by
Proposed Standard informatively references
RFC 8934
As rfc7399
PCE Communication Protocol (PCEP) Extensions for Label Switched Path (LSP) Scheduling with Stateful PCE
References Referenced by
Proposed Standard informatively references
RFC 9050
As rfc7399
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
As rfc7399
Path Computation Element Communication Protocol (PCEP) Extension for Flow Specification
References Referenced by
Proposed Standard informatively references
RFC 9504
As rfc7399
Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE Usage in GMPLS-Controlled Networks
References Referenced by
Proposed Standard informatively references