References from draft-ietf-httpapi-idempotency-key-header
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 |
|---|---|---|---|---|
| RFC 2119 | Key words for use in RFCs to Indicate Requirement Levels References Referenced by | Best Current Practice | normatively references | |
| RFC 4122 | A Universally Unique IDentifier (UUID) URN Namespace References Referenced by | Proposed Standard | normatively references | |
| RFC 5234 | Augmented BNF for Syntax Specifications: ABNF References Referenced by | Internet Standard | normatively references | |
| RFC 7231 | Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content References Referenced by | Proposed Standard | normatively references | |
| RFC 7807 | Problem Details for HTTP APIs References Referenced by | Proposed Standard | normatively references | |
| RFC 7942 | Improving Awareness of Running Code: The Implementation Status Section References Referenced by | Best Current Practice | informatively references | |
| RFC 8174 | Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words References Referenced by | Best Current Practice | normatively references | |
| RFC 8941 | Structured Field Values for HTTP References Referenced by | Proposed Standard | normatively references | |
| RFC 9110 | HTTP Semantics References Referenced by | Internet Standard | normatively references |