References from draft-chen-pce-h-connect-access
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 3630 |
Traffic Engineering (TE) Extensions to OSPF Version 2
References Referenced by |
Proposed Standard | normatively references | |
| RFC 5305 |
IS-IS Extensions for Traffic Engineering
References Referenced by |
Proposed Standard | informatively references | |
| RFC 5316 |
ISIS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering
References Referenced by |
Proposed Standard | informatively references | |
| RFC 5392 |
OSPF Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering
References Referenced by |
Proposed Standard | informatively references | |
| RFC 5440 |
Path Computation Element (PCE) Communication Protocol (PCEP)
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 | |
| RFC 7752 |
North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP
References Referenced by |
Proposed Standard | informatively references |