References from draft-reschke-http-jfv
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 166 |
Terminology Used in Internationalization in the IETF References Referenced by |
Best Current Practice | informatively references | |
| draft-ietf-httpbis-jfv |
A JSON Encoding for HTTP Header Field Values References Referenced by |
informatively references | ||
| draft-ietf-httpbis-key |
The Key HTTP Response Header Field References Referenced by |
Proposed Standard | informatively references | |
| draft-ietf-httpbis-semantics |
HTTP Semantics References Referenced by |
Internet Standard | normatively references | |
| RFC 20 |
ASCII format for network interchange References Referenced by |
Internet Standard | normatively references | |
| RFC 5234 |
Augmented BNF for Syntax Specifications: ABNF References Referenced by |
Internet Standard | normatively references | |
| RFC 5987 |
Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters References Referenced by |
Historic | informatively references | |
| RFC 6365 |
Terminology Used in Internationalization in the IETF References Referenced by |
Best Current Practice | informatively references | |
| RFC 7493 |
The I-JSON Message Format References Referenced by |
Proposed Standard | normatively references | |
| RFC 8259 |
The JavaScript Object Notation (JSON) Data Interchange Format References Referenced by |
Internet Standard | normatively references | |
| RFC 8941 |
Structured Field Values for HTTP References Referenced by |
Proposed Standard | informatively references | |
| STD 68 |
Augmented BNF for Syntax Specifications: ABNF References Referenced by |
Internet Standard | normatively references |