References from draft-whh-pce-capability-advertize
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 | normatively references | |
| RFC 4657 |
Path Computation Element (PCE) Communication Protocol Generic Requirements
References Referenced by |
Informational | normatively references | |
| RFC 5440 |
Path Computation Element (PCE) Communication Protocol (PCEP)
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 | normatively references | |
| RFC 8042 |
OSPF Two-Part Metric
References Referenced by |
Proposed Standard | normatively 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 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 9059 |
Path Computation Element Communication Protocol (PCEP) Extensions for Associated Bidirectional Label Switched Paths (LSPs)
References Referenced by |
Proposed Standard | normatively references |