References from draft-xu-idr-performce-routing
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 26 |
References Referenced by |
normatively references | ||
draft-ietf-idr-add-paths |
Advertisement of Multiple Paths in BGP
References Referenced by |
Proposed Standard | informatively references | |
draft-ietf-ospf-te-metric-extensions |
OSPF Traffic Engineering (TE) Metric Extensions
References Referenced by |
Proposed Standard | informatively references | |
draft-previdi-isis-te-metric-extensions |
IS-IS Traffic Engineering (TE) Metric Extensions
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 3107 |
Carrying Label Information in BGP-4
References Referenced by |
Proposed Standard | informatively references | |
RFC 3630 |
Traffic Engineering (TE) Extensions to OSPF Version 2
References Referenced by |
Proposed Standard | informatively references | |
RFC 4271 |
A Border Gateway Protocol 4 (BGP-4)
References Referenced by |
Draft Standard | normatively references | |
RFC 4760 |
Multiprotocol Extensions for BGP-4
References Referenced by |
Draft Standard | informatively 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 5492 |
Capabilities Advertisement with BGP-4
References Referenced by |
Draft Standard | informatively references |