References from draft-ietf-pce-enhanced-errors
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.
| Document | Title | Status | Type | Downref |
|---|---|---|---|---|
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 4655 |
A Path Computation Element (PCE)-Based Architecture
References Referenced by |
Informational | Possible Reference | |
| RFC 5440 |
Path Computation Element (PCE) Communication Protocol (PCEP)
References Referenced by |
Proposed Standard | normatively 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 | normatively references | |
| RFC 5455 |
Diffserv-Aware Class-Type Object for the Path Computation Element Communication Protocol
References Referenced by |
Proposed Standard | normatively references | |
| RFC 5521 |
Extensions to the Path Computation Element Communication Protocol (PCEP) for Route Exclusions
References Referenced by |
Proposed Standard | normatively references | |
| RFC 5541 |
Encoding of Objective Functions in the Path Computation Element Communication Protocol (PCEP)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 5557 |
Path Computation Element Communication Protocol (PCEP) Requirements and Protocol Extensions in Support of Global Concurrent Optimization
References Referenced by |
Proposed Standard | normatively references | |
| RFC 5886 |
A Set of Monitoring Tools for Path Computation Element (PCE)-Based Architecture
References Referenced by |
Proposed Standard | normatively references | |
| RFC 7470 |
Conveying Vendor-Specific Constraints in the Path Computation Element Communication Protocol
References Referenced by |
Proposed Standard | Possible Reference | |
| RFC 7942 |
Improving Awareness of Running Code: The Implementation Status Section
References Referenced by |
Best Current Practice | Possible Reference | |
| 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 | normatively 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 | normatively 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 8306 |
Extensions to the Path Computation Element Communication Protocol (PCEP) for Point-to-Multipoint Traffic Engineering Label Switched Paths
References Referenced by |
Proposed Standard | normatively references | |
| RFC 8408 |
Conveying Path Setup Type in PCE Communication Protocol (PCEP) Messages
References Referenced by |
Proposed Standard | normatively references | |
| RFC 8697 |
Path Computation Element Communication Protocol (PCEP) Extensions for Establishing Relationships between Sets of Label Switched Paths (LSPs)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 8751 |
Hierarchical Stateful Path Computation Element (PCE)
References Referenced by |
Informational | Possible Reference |