RFC 8164: Opportunistic Security for HTTP/2

This document describes how "http" URIs can be accessed using Transport Layer Security (TLS) and HTTP/2 to mitigate pervasive monitoring attacks. This…

Read RFC 8164 on the RFC Editor

Outgoing relationships (13 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2
Normative reference — RFC 2818: HTTP Over TLS
Normative reference — RFC 7230: Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
Normative reference — RFC 7159: The JavaScript Object Notation (JSON) Data Interchange Format
Normative reference — RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): Caching
Normative reference — RFC 6454: The Web Origin Concept
Normative reference — RFC 7540: Hypertext Transfer Protocol Version 2 (HTTP/2)
Normative reference — RFC 5785: Defining Well-Known Uniform Resource Identifiers (URIs)
Normative reference — RFC 7232: Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests
Normative reference — RFC 7838: HTTP Alternative Services
Informative reference — RFC 7258: Pervasive Monitoring Is an Attack
Informative reference — RFC 7435: Opportunistic Security: Some Protection Most of the Time

Incoming relationships (2 related RFCs)

Informatively referenced by — RFC 8404: Effects of Pervasive Encryption on Operators
Informatively referenced by — RFC 8280: Research into Human Rights Protocol Considerations