References from draft-wu-alto-json-te
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 |
---|---|---|---|---|
draft-ietf-alto-protocol |
Application-Layer Traffic Optimization (ALTO) Protocol
References Referenced by |
Proposed Standard | normatively references | |
draft-ietf-idr-ls-distribution |
North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP
References Referenced by |
Proposed Standard | normatively references | |
draft-ietf-isis-te-metric-extensions |
IS-IS Traffic Engineering (TE) Metric Extensions
References Referenced by |
Proposed Standard | normatively references | |
draft-ietf-ospf-te-metric-extensions |
OSPF Traffic Engineering (TE) Metric Extensions
References Referenced by |
Proposed Standard | normatively references | |
draft-wu-idr-te-pm-bgp |
BGP attribute for North-Bound Distribution of Traffic Engineering (TE) performance Metrics
References Referenced by |
normatively references | ||
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 | Possible Reference | |
RFC 4627 |
The application/json Media Type for JavaScript Object Notation (JSON)
References Referenced by |
Informational | normatively references | |
RFC 5234 |
Augmented BNF for Syntax Specifications: ABNF
References Referenced by |
Internet Standard | normatively references | |
RFC 6390 |
Guidelines for Considering New Performance Metric Development
References Referenced by |
Best Current Practice | informatively references |