References from draft-crabbe-pce-pce-initiated-lsp
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 |
|---|---|---|---|---|
| BCP 14 |
Key words for use in RFCs to Indicate Requirement Levels References Referenced by |
Best Current Practice | normatively references | |
| BCP 26 |
Guidelines for Writing an IANA Considerations Section in RFCs References Referenced by |
Best Current Practice | normatively references | |
| draft-ietf-pce-stateful-pce |
Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE References Referenced by |
Proposed Standard | normatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels References Referenced by |
Best Current Practice | normatively references | |
| RFC 2205 |
Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification References Referenced by |
Proposed Standard | normatively references | |
| RFC 2702 |
Requirements for Traffic Engineering Over MPLS References Referenced by |
Informational | informatively references | |
| RFC 3031 |
Multiprotocol Label Switching Architecture References Referenced by |
Proposed Standard | informatively references | |
| RFC 3209 |
RSVP-TE: Extensions to RSVP for LSP Tunnels References Referenced by |
Proposed Standard | normatively references | |
| RFC 3346 |
Applicability Statement for Traffic Engineering with MPLS References Referenced by |
Informational | informatively references | |
| RFC 3630 |
Traffic Engineering (TE) Extensions to OSPF Version 2 References Referenced by |
Proposed Standard | informatively references | |
| RFC 4090 |
Fast Reroute Extensions to RSVP-TE for LSP Tunnels References Referenced by |
Proposed Standard | normatively references | |
| RFC 4655 |
A Path Computation Element (PCE)-Based Architecture References Referenced by |
Informational | informatively references | |
| RFC 4657 |
Path Computation Element (PCE) Communication Protocol Generic Requirements References Referenced by |
Informational | informatively references | |
| RFC 5088 |
OSPF Protocol Extensions for Path Computation Element (PCE) Discovery References Referenced by |
Proposed Standard | normatively references | |
| RFC 5089 |
IS-IS Protocol Extensions for Path Computation Element (PCE) Discovery References Referenced by |
Proposed Standard | normatively references | |
| RFC 5226 |
Guidelines for Writing an IANA Considerations Section in RFCs References Referenced by |
Best Current Practice | normatively references | |
| RFC 5305 |
IS-IS Extensions for Traffic Engineering References Referenced by |
Proposed Standard | informatively references | |
| RFC 5394 |
Policy-Enabled Path Computation Framework References Referenced by |
Informational | informatively references | |
| RFC 5440 |
Path Computation Element (PCE) Communication Protocol (PCEP) References Referenced by |
Proposed Standard | normatively references | |
| RFC 5511 |
Routing Backus-Naur Form (RBNF): A Syntax Used to Form Encoding Rules in Various Routing Protocol Specifications 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 | informatively references | |
| RFC 6982 |
Improving Awareness of Running Code: The Implementation Status Section References Referenced by |
Experimental | informatively references |