References to draft-ietf-pce-stateful-sync-optimizations

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
draft-chen-pce-bier-te-path As rfc8232	PCE for BIER-TE Path References Referenced by		normatively references
draft-dhodylee-pce-pcep-ls As rfc8232	PCEP extensions for Distribution of Link-State and TE Information References Referenced by		normatively references
draft-ietf-pce-pcep-extension-native-ip As rfc8232	Path Computation Element Communication Protocol (PCEP) Extensions for Native IP Networks References Referenced by	Proposed Standard	normatively references
draft-ietf-pce-pcep-yang As rfc8232	A YANG Data Model for Path Computation Element Communications Protocol (PCEP) References Referenced by		normatively references
draft-ietf-pce-sr-path-segment As rfc8232	Path Computation Element Communication Protocol (PCEP) Extension for Path Segment in Segment Routing (SR) References Referenced by		normatively references
draft-ietf-pce-state-sync As rfc8232	Inter Stateful Path Computation Element (PCE) Communication Procedures. References Referenced by		normatively references
draft-ietf-teas-yang-te As rfc8232	A YANG Data Model for Traffic Engineering Tunnels, Label Switched Paths and Interfaces References Referenced by		normatively references
RFC 8281 As rfc8232	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 8623 As rfc8232	Stateful Path Computation Element (PCE) Protocol Extensions for Usage with Point-to-Multipoint TE Label Switched Paths (LSPs) References Referenced by	Proposed Standard	normatively references
RFC 8934 As rfc8232	PCE Communication Protocol (PCEP) Extensions for Label Switched Path (LSP) Scheduling with Stateful PCE References Referenced by	Proposed Standard	normatively references
RFC 9168 As rfc8232	Path Computation Element Communication Protocol (PCEP) Extension for Flow Specification References Referenced by	Proposed Standard	normatively references
draft-ietf-pce-pcep-extension-pce-controller-sr As rfc8232	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 rfc8232	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-kondreddy-pce-pcep-ls-sync-optimizations As rfc8232	Optimizations of PCEP Link-State(LS) Synchronization Procedures References Referenced by		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 8751 As rfc8232	Hierarchical Stateful Path Computation Element (PCE) References Referenced by	Informational	informatively references
RFC 9050 As rfc8232	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 9504 As rfc8232	Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE Usage in GMPLS-Controlled Networks References Referenced by	Proposed Standard	informatively references