References from draft-nottingham-http-patch-status
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 |
informatively references | ||
| draft-ietf-httpbis-http2 |
Hypertext Transfer Protocol Version 2 (HTTP/2)
References Referenced by |
Proposed Standard | informatively references | |
| draft-ietf-httpbis-p2-semantics |
Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
References Referenced by |
Proposed Standard | informatively references | |
| draft-ietf-httpbis-p4-conditional |
Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests
References Referenced by |
Proposed Standard | normatively references | |
| draft-ietf-httpbis-p6-cache |
Hypertext Transfer Protocol (HTTP/1.1): Caching
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 | informatively references | |
| RFC 5246 |
The Transport Layer Security (TLS) Protocol Version 1.2
References Referenced by |
Proposed Standard | normatively references | |
| RFC 5789 |
PATCH Method for HTTP
References Referenced by |
Proposed Standard | normatively references |