References from draft-ietf-httpbis-bcp56bis

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 13	Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures Refs Ref'd by	Best Current Practice	normatively references
BCP 14	Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by	Best Current Practice	normatively references
BCP 165	Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry Refs Ref'd by	Best Current Practice	informatively references
BCP 178	Deprecating the "X-" Prefix and Similar Constructs in Application Protocols Refs Ref'd by	Best Current Practice	normatively references
BCP 188	Pervasive Monitoring Is an Attack Refs Ref'd by	Best Current Practice	informatively references
BCP 35	Guidelines and Registration Procedures for New URI Schemes Refs Ref'd by	Best Current Practice	informatively references
draft-ietf-httpbis-cache	HTTP Caching Refs Ref'd by		normatively references	Possible Downref
draft-ietf-httpbis-header-structure	Structured Headers for HTTP Refs Ref'd by		informatively references
draft-ietf-httpbis-messaging	HTTP/1.1 Messaging Refs Ref'd by		normatively references	Possible Downref
draft-ietf-httpbis-rfc6265bis	Cookies: HTTP State Management Mechanism Refs Ref'd by		informatively references
draft-ietf-httpbis-semantics	HTTP Semantics Refs Ref'd by		normatively references	Possible Downref
draft-nottingham-rfc5785bis	Well-Known Uniform Resource Identifiers (URIs) Refs Ref'd by	Proposed Standard	informatively references
RFC 2119	Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by	Best Current Practice	normatively references
RFC 2818	HTTP Over TLS Refs Ref'd by	Informational	normatively references	Downref
RFC 3205	On the use of HTTP as a Substrate Refs Ref'd by	Best Current Practice	informatively references
RFC 4367	What's in a Name: False Assumptions about DNS Names Refs Ref'd by	Informational	informatively references
RFC 4791	Calendaring Extensions to WebDAV (CalDAV) Refs Ref'd by	Proposed Standard	informatively references
RFC 4918	HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV) Refs Ref'd by	Proposed Standard	informatively references
RFC 5246	The Transport Layer Security (TLS) Protocol Version 1.2 Refs Ref'd by	Proposed Standard	informatively references
RFC 5861	HTTP Cache-Control Extensions for Stale Content Refs Ref'd by	Informational	informatively references
RFC 6415	Web Host Metadata Refs Ref'd by	Proposed Standard	informatively references
RFC 6454	The Web Origin Concept Refs Ref'd by	Proposed Standard	normatively references	Downref
RFC 6648	Deprecating the "X-" Prefix and Similar Constructs in Application Protocols Refs Ref'd by	Best Current Practice	normatively references
RFC 6797	HTTP Strict Transport Security (HSTS) Refs Ref'd by	Proposed Standard	informatively references
RFC 6838	Media Type Specifications and Registration Procedures Refs Ref'd by	Best Current Practice	normatively references
RFC 7049	Concise Binary Object Representation (CBOR) Refs Ref'd by	Proposed Standard	informatively references
RFC 7258	Pervasive Monitoring Is an Attack Refs Ref'd by	Best Current Practice	informatively references
RFC 7301	Transport Layer Security (TLS) Application-Layer Protocol Negotiation Extension Refs Ref'd by	Proposed Standard	normatively references	Downref
RFC 7320	URI Design and Ownership Refs Ref'd by	Best Current Practice	normatively references
RFC 7538	The Hypertext Transfer Protocol Status Code 308 (Permanent Redirect) Refs Ref'd by	Proposed Standard	informatively references
RFC 7540	Hypertext Transfer Protocol Version 2 (HTTP/2) Refs Ref'd by	Proposed Standard	normatively references	Downref
RFC 7595	Guidelines and Registration Procedures for URI Schemes Refs Ref'd by	Best Current Practice	informatively references
RFC 7605	Recommendations on Using Assigned Transport Port Numbers Refs Ref'd by	Best Current Practice	informatively references
RFC 7616	HTTP Digest Access Authentication Refs Ref'd by	Proposed Standard	informatively references
RFC 7617	The 'Basic' HTTP Authentication Scheme Refs Ref'd by	Proposed Standard	informatively references
RFC 7807	Problem Details for HTTP APIs Refs Ref'd by	Proposed Standard	informatively references
RFC 8174	Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words Refs Ref'd by	Best Current Practice	normatively references
RFC 8259	The JavaScript Object Notation (JSON) Data Interchange Format Refs Ref'd by	Internet Standard	informatively references
RFC 8288	Web Linking Refs Ref'd by	Proposed Standard	normatively references	Downref
RFC 8297	An HTTP Status Code for Indicating Hints Refs Ref'd by	Experimental	informatively references
STD 90	The JavaScript Object Notation (JSON) Data Interchange Format Refs Ref'd by	Internet Standard	informatively references