References from draft-wilde-accept-post

This is an experimental product. 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.

Reference type help

Document Title Status Type Downref
BCP 90 Registration Procedures for Message Header Fields
Refs Ref'd by
Best Current Practice normatively references
draft-nottingham-link-hint HTTP Link Hints
Refs Ref'd by
informatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
Refs Ref'd by
Best Current Practice normatively references
RFC 2616 Hypertext Transfer Protocol -- HTTP/1.1
Refs Ref'd by
Draft Standard Possible Reference
RFC 3864 Registration Procedures for Message Header Fields
Refs Ref'd by
Best Current Practice normatively references
RFC 4287 The Atom Syndication Format
Refs Ref'd by
Proposed Standard informatively references
RFC 5023 The Atom Publishing Protocol
Refs Ref'd by
Proposed Standard informatively references
RFC 5234 Augmented BNF for Syntax Specifications: ABNF
Refs Ref'd by
Internet Standard informatively references
RFC 5789 PATCH Method for HTTP
Refs Ref'd by
Proposed Standard informatively references
RFC 6982 Improving Awareness of Running Code: The Implementation Status Section
Refs Ref'd by
Experimental informatively references
RFC 7231 Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
Refs Ref'd by
Proposed Standard informatively references
STD 68 Augmented BNF for Syntax Specifications: ABNF
Refs Ref'd by
Internet Standard informatively references