References from draft-nottingham-http-problem
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 | ||
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 2616 |
Hypertext Transfer Protocol -- HTTP/1.1
References Referenced by |
Draft Standard | normatively references | |
| RFC 3023 |
XML Media Types
References Referenced by |
Proposed Standard | informatively references | |
| RFC 3986 |
Uniform Resource Identifier (URI): Generic Syntax
References Referenced by |
Internet Standard | normatively references | |
| RFC 4627 |
The application/json Media Type for JavaScript Object Notation (JSON)
References Referenced by |
Informational | normatively references | |
| RFC 5234 |
Augmented BNF for Syntax Specifications: ABNF
References Referenced by |
Internet Standard | normatively references | |
| RFC 5988 |
Web Linking
References Referenced by |
Proposed Standard | informatively references | |
| RFC 6694 |
The "about" URI Scheme
References Referenced by |
Informational | informatively references | |
| RFC 6838 |
Media Type Specifications and Registration Procedures
References Referenced by |
Best Current Practice | informatively references | |
| STD 66 |
References Referenced by |
normatively references | ||
| STD 68 |
References Referenced by |
normatively references |