References from draft-nottingham-binary-structured-headers
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 14 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| draft-ietf-httpbis-header-structure |
Structured Field Values for HTTP
References Referenced by |
Proposed Standard | normatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 6265 |
HTTP State Management Mechanism
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 7540 |
Hypertext Transfer Protocol Version 2 (HTTP/2)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 7541 |
HPACK: Header Compression for HTTP/2
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 8288 |
Web Linking
References Referenced by |
Proposed Standard | normatively references |