References from draft-wilde-accept-post
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 90 |
References Referenced by |
normatively references | ||
| draft-nottingham-link-hint |
HTTP Link Hints
References Referenced by |
informatively 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 | Possible Reference | |
| RFC 3864 |
Registration Procedures for Message Header Fields
References Referenced by |
Best Current Practice | normatively references | |
| RFC 4287 |
The Atom Syndication Format
References Referenced by |
Proposed Standard | informatively references | |
| RFC 5023 |
The Atom Publishing Protocol
References Referenced by |
Proposed Standard | informatively references | |
| RFC 5234 |
Augmented BNF for Syntax Specifications: ABNF
References Referenced by |
Internet Standard | informatively references | |
| RFC 5789 |
PATCH Method for HTTP
References Referenced by |
Proposed Standard | informatively references | |
| RFC 6982 |
Improving Awareness of Running Code: The Implementation Status Section
References Referenced by |
Experimental | informatively references | |
| RFC 7231 |
Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
References Referenced by |
Proposed Standard | informatively references | |
| STD 68 |
References Referenced by |
informatively references |