References from draft-fizgeer-pce-redundancy-extensions
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 | informatively references | |
| RFC 5440 |
Path Computation Element (PCE) Communication Protocol (PCEP)
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 8664 |
Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing
References Referenced by |
Proposed Standard | normatively references | |
| RFC 9603 |
Path Computation Element Communication Protocol (PCEP) Extensions for IPv6 Segment Routing
References Referenced by |
Proposed Standard | informatively references | |
| RFC 9604 |
Carrying Binding Label/SID in PCE-Based Networks
References Referenced by |
Proposed Standard | normatively references |