References from draft-ietf-alto-path-vector

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.

Reference type help

Document Title Status Type Downref
BCP 14 Key words for use in RFCs to Indicate Requirement Levels
References Referenced by
Best Current Practice normatively references
draft-contreras-alto-service-edge Use of ALTO for Determining Service Edge
References Referenced by
informatively references
draft-huang-alto-mowie-for-network-aware-app MoWIE for Network Aware Application
References Referenced by
informatively references
draft-ietf-alto-performance-metrics ALTO Performance Cost Metrics
References Referenced by
Proposed Standard informatively references
draft-ietf-alto-unified-props-new ALTO extension: Entity Property Maps
References Referenced by
normatively references
draft-ietf-dmm-5g-uplane-analysis User Plane Protocol and Architectural Analysis on 3GPP 5G System
References Referenced by
informatively references
draft-ietf-quic-http Hypertext Transfer Protocol Version 3 (HTTP/3)
References Referenced by
Proposed Standard informatively references
draft-yang-alto-deliver-functions-over-networks Delivering Functions over Networks: Traffic and Performance Optimization for Edge Computing using ALTO
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 2216 Network Element Service Specification Template
References Referenced by
Informational informatively references
RFC 2387 The MIME Multipart/Related Content-type
References Referenced by
Proposed Standard normatively references
RFC 7285 Application-Layer Traffic Optimization (ALTO) Protocol
References Referenced by
Proposed Standard normatively references
RFC 7540 Hypertext Transfer Protocol Version 2 (HTTP/2)
References Referenced by
Proposed Standard informatively references
RFC 8174 Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by
Best Current Practice normatively references
RFC 8189 Multi-Cost Application-Layer Traffic Optimization (ALTO)
References Referenced by
Proposed Standard normatively references
RFC 8895 Application-Layer Traffic Optimization (ALTO) Incremental Updates Using Server-Sent Events (SSE)
References Referenced by
Proposed Standard normatively references
RFC 8896 Application-Layer Traffic Optimization (ALTO) Cost Calendar
References Referenced by
Proposed Standard normatively references