References from draft-reschke-http-oob-encoding
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 13 |
References Referenced by |
informatively references | ||
| BCP 14 |
References Referenced by |
normatively references | ||
| draft-eriksson-http-resource-map |
Resource Maps
References Referenced by |
informatively references | ||
| draft-thomson-http-content-signature |
Content-Signature Header Field for HTTP
References Referenced by |
informatively references | ||
| draft-thomson-http-mice |
Merkle Integrity Content Encoding
References Referenced by |
informatively references | ||
| draft-thomson-http-scd |
An Architecture for Secure Content Delegation using HTTP
References Referenced by |
informatively references | ||
| RFC 2017 |
Definition of the URL MIME External-Body Access-Type
References Referenced by |
Proposed Standard | informatively references | |
| 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 4483 |
A Mechanism for Content Indirection in Session Initiation Protocol (SIP) Messages
References Referenced by |
Proposed Standard | informatively references | |
| RFC 4648 |
The Base16, Base32, and Base64 Data Encodings
References Referenced by |
Proposed Standard | informatively references | |
| RFC 5246 |
The Transport Layer Security (TLS) Protocol Version 1.2
References Referenced by |
Proposed Standard | informatively references | |
| RFC 5988 |
Web Linking
References Referenced by |
Proposed Standard | informatively references | |
| RFC 6265 |
HTTP State Management Mechanism
References Referenced by |
Proposed Standard | informatively references | |
| RFC 6454 |
The Web Origin Concept
References Referenced by |
Proposed Standard | informatively references | |
| RFC 6838 |
Media Type Specifications and Registration Procedures
References Referenced by |
Best Current Practice | informatively references | |
| RFC 7159 |
The JavaScript Object Notation (JSON) Data Interchange Format
References Referenced by |
Proposed Standard | normatively references | |
| RFC 7230 |
Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
References Referenced by |
Proposed Standard | normatively references | |
| RFC 7231 |
Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
References Referenced by |
Proposed Standard | informatively references | |
| RFC 7232 |
Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests
References Referenced by |
Proposed Standard | informatively references | |
| RFC 7233 |
Hypertext Transfer Protocol (HTTP/1.1): Range Requests
References Referenced by |
Proposed Standard | informatively references | |
| RFC 7235 |
Hypertext Transfer Protocol (HTTP/1.1): Authentication
References Referenced by |
Proposed Standard | normatively references | |
| RFC 8188 |
Encrypted Content-Encoding for HTTP
References Referenced by |
Proposed Standard | informatively references | |
| STD 66 |
References Referenced by |
normatively references |