References from draft-ietf-alto-path-vector
This is an experimental product. 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 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | normatively references | |
| draft-amante-i2rs-topology-use-cases |
Topology API Use Cases Refs Ref'd by |
informatively references | ||
| draft-bernstein-alto-topo |
ALTO Topology Service: Uses Cases, Requirements, and Framework Refs Ref'd by |
informatively references | ||
| draft-ietf-alto-cost-calendar |
ALTO Cost Calendar Refs Ref'd by |
Proposed Standard | informatively references | |
| draft-ietf-alto-incr-update-sse |
ALTO Incremental Updates Using Server-Sent Events (SSE) Refs Ref'd by |
Proposed Standard | informatively references | |
| draft-ietf-alto-unified-props-new |
Unified Properties for the ALTO Protocol Refs Ref'd by |
informatively references | ||
| draft-lee-alto-app-net-info-exchange |
ALTO Extensions to Support Application and Network Resource Information Exchange for High Bandwidth Applications in TE networks Refs Ref'd by |
informatively references | ||
| draft-yang-alto-topology |
ALTO Topology Extensions: Node-Link Graphs Refs Ref'd by |
informatively references | ||
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | normatively references | |
| RFC 7285 |
Application-Layer Traffic Optimization (ALTO) Protocol Refs Ref'd by |
Proposed Standard | informatively references | |
| RFC 8189 |
Multi-Cost Application-Layer Traffic Optimization (ALTO) Refs Ref'd by |
Proposed Standard | informatively references |