References from draft-zhang-alto-multipart

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.

Reference type help

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-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-path-vector ALTO Extension: Path Vector Cost Type
Refs Ref'd by
informatively references
draft-ietf-alto-unified-props-new Unified Properties for the ALTO Protocol
Refs Ref'd by
informatively references
RFC 2046 Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
Refs Ref'd by
Draft Standard informatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
Refs Ref'd by
Best Current Practice normatively references
RFC 2387 The MIME Multipart/Related Content-type
Refs Ref'd by
Proposed Standard normatively references
RFC 7285 Application-Layer Traffic Optimization (ALTO) Protocol
Refs Ref'd by
Proposed Standard normatively references
RFC 8189 Multi-Cost Application-Layer Traffic Optimization (ALTO)
Refs Ref'd by
Proposed Standard informatively references
RFC 8259 The JavaScript Object Notation (JSON) Data Interchange Format
Refs Ref'd by
Internet Standard informatively references
STD 90 The JavaScript Object Notation (JSON) Data Interchange Format
Refs Ref'd by
Internet Standard informatively references