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.
| Document | Title | Status | Type | Downref |
|---|---|---|---|---|
| RFC 2046 |
Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
References Referenced by |
Draft Standard | normatively 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 4271 |
A Border Gateway Protocol 4 (BGP-4)
References Referenced by |
Draft Standard | informatively references | |
| RFC 5322 |
Internet Message Format
References Referenced by |
Draft Standard | normatively references | |
| RFC 7285 |
Application-Layer Traffic Optimization (ALTO) Protocol
References Referenced by |
Proposed Standard | normatively 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 |