References from rfc5553
This is an experimental product. 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 Refs Ref'd by |
Best Current Practice | normatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | normatively references | |
| RFC 3209 |
RSVP-TE: Extensions to RSVP for LSP Tunnels Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 3473 |
Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 4655 |
A Path Computation Element (PCE)-Based Architecture Refs Ref'd by |
Informational | informatively references | |
| RFC 4726 |
A Framework for Inter-Domain Multiprotocol Label Switching Traffic Engineering Refs Ref'd by |
Informational | informatively references | |
| RFC 5394 |
Policy-Enabled Path Computation Framework Refs Ref'd by |
Informational | informatively references | |
| RFC 5440 |
Path Computation Element (PCE) Communication Protocol (PCEP) Refs Ref'd by |
Proposed Standard | informatively references | |
| RFC 5520 |
Preserving Topology Confidentiality in Inter-Domain Path Computation Using a Path-Key-Based Mechanism Refs Ref'd by |
Proposed Standard | informatively references | |
| STD 1 |
Internet Official Protocol Standards Refs Ref'd by |
Historic | Possible Reference | Possible Downref |