References from draft-dunglas-vulcain
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 |
References Referenced by |
normatively references | ||
| BCP 90 |
References Referenced by |
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 3864 |
Registration Procedures for Message Header Fields
References Referenced by |
Best Current Practice | normatively references | |
| RFC 3986 |
Uniform Resource Identifier (URI): Generic Syntax
References Referenced by |
Internet Standard | normatively references | |
| RFC 4287 |
The Atom Syndication Format
References Referenced by |
Proposed Standard | informatively references | |
| RFC 5988 |
Web Linking
References Referenced by |
Proposed Standard | normatively references | |
| RFC 6901 |
JavaScript Object Notation (JSON) Pointer
References Referenced by |
Proposed Standard | normatively references | |
| RFC 6982 |
Improving Awareness of Running Code: The Implementation Status Section
References Referenced by |
Experimental | informatively references | |
| RFC 7240 |
Prefer Header for HTTP
References Referenced by |
Proposed Standard | normatively references | |
| RFC 7540 |
Hypertext Transfer Protocol Version 2 (HTTP/2)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 8297 |
An HTTP Status Code for Indicating Hints
References Referenced by |
Experimental | normatively references | |
| STD 66 |
References Referenced by |
normatively references |