References from draft-zhang-pce-hierarchy-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 |
---|---|---|---|---|
BCP 14 |
References Referenced by |
normatively references | ||
draft-dhody-pce-pcep-domain-sequence |
Standard Representation Of Domain Sequence
References Referenced by |
Possible Reference | ||
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 3209 |
RSVP-TE: Extensions to RSVP for LSP Tunnels
References Referenced by |
Proposed Standard | normatively references | |
RFC 4655 |
A Path Computation Element (PCE)-Based Architecture
References Referenced by |
Informational | normatively references | |
RFC 5152 |
A Per-Domain Path Computation Method for Establishing Inter-Domain Traffic Engineering (TE) Label Switched Paths (LSPs)
References Referenced by |
Proposed Standard | normatively references | |
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 5886 |
A Set of Monitoring Tools for Path Computation Element (PCE)-Based Architecture
References Referenced by |
Proposed Standard | normatively references | |
RFC 6805 |
The Application of the Path Computation Element Architecture to the Determination of a Sequence of Domains in MPLS and GMPLS
References Referenced by |
Informational | normatively references |