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