References from draft-ietf-alto-new-transport
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 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 3986 |
Uniform Resource Identifier (URI): Generic Syntax
References Referenced by |
Internet Standard | normatively references | |
| RFC 4122 |
A Universally Unique IDentifier (UUID) URN Namespace
References Referenced by |
Proposed Standard | informatively 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 8259 |
The JavaScript Object Notation (JSON) Data Interchange Format
References Referenced by |
Internet 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 9112 |
HTTP/1.1
References Referenced by |
Internet Standard | normatively references | |
| RFC 9113 |
HTTP/2
References Referenced by |
Proposed Standard | normatively references | |
| RFC 9114 |
HTTP/3
References Referenced by |
Proposed Standard | normatively references | |
| RFC 9205 |
Building Protocols with HTTP
References Referenced by |
Best Current Practice | informatively references | |
| RFC 9325 |
Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)
References Referenced by |
Best Current Practice | normatively references |