References from RFC 4927
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 | ||
| BCP 78 |
References Referenced by |
informatively references | ||
| BCP 87 |
References Referenced by |
informatively references | ||
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 3785 |
Use of Interior Gateway Protocol (IGP) Metric as a second MPLS Traffic Engineering (TE) Metric
References Referenced by |
Best Current Practice | informatively references | |
| RFC 4105 |
Requirements for Inter-Area MPLS Traffic Engineering
References Referenced by |
Informational | 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 4674 |
Requirements for Path Computation Element (PCE) Discovery
References Referenced by |
Informational | informatively references |