RFC 7540: Hypertext Transfer Protocol Version 2 (HTTP/2)

This specification describes an optimized expression of the semantics of the Hypertext Transfer Protocol (HTTP), referred to as HTTP version 2 (HTTP/2).…

Read RFC 7540 on the RFC Editor

Outgoing relationships (25 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 5226: Guidelines for Writing an IANA Considerations Section in RFCs
Normative reference — RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2
Normative reference — RFC 5234: Augmented BNF for Syntax Specifications: ABNF
Normative reference — RFC 3986: Uniform Resource Identifier (URI): Generic Syntax
Normative reference — RFC 793: Transmission Control Protocol
Normative reference — RFC 4648: The Base16, Base32, and Base64 Data Encodings
Normative reference — RFC 2818: HTTP Over TLS
Normative reference — RFC 7230: Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
Normative reference — RFC 6066: Transport Layer Security (TLS) Extensions: Extension Definitions
Normative reference — RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
Normative reference — RFC 6265: HTTP State Management Mechanism
Normative reference — RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): Caching
Normative reference — RFC 7301: Transport Layer Security (TLS) Application-Layer Protocol Negotiation Extension
Normative reference — RFC 7235: Hypertext Transfer Protocol (HTTP/1.1): Authentication
Normative reference — RFC 7232: Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests
Normative reference — RFC 5289: TLS Elliptic Curve Cipher Suites with SHA-256/384 and AES Galois Counter Mode (GCM)
Normative reference — RFC 7233: Hypertext Transfer Protocol (HTTP/1.1): Range Requests
Normative reference — RFC 7541: HPACK: Header Compression for HTTP/2
Informative reference — RFC 7525: Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)
Informative reference — RFC 3864: Registration Procedures for Message Header Fields
Informative reference — RFC 7323: TCP Extensions for High Performance
Informative reference — RFC 4492: Elliptic Curve Cryptography (ECC) Cipher Suites for Transport Layer Security (TLS)
Informative reference — RFC 3749: Transport Layer Security Protocol Compression Methods
Informative reference — RFC 6585: Additional HTTP Status Codes

Incoming relationships (20 related RFCs)

Updated by, Normatively referenced by — RFC 8740: Using TLS 1.3 with HTTP/2
Obsoleted by — RFC 9113: HTTP/2
Normatively referenced by — RFC 7838: HTTP Alternative Services
Normatively referenced by — RFC 7541: HPACK: Header Compression for HTTP/2
Normatively referenced by — RFC 8164: Opportunistic Security for HTTP/2
Normatively referenced by — RFC 8297: An HTTP Status Code for Indicating Hints
Normatively referenced by — RFC 8336: The ORIGIN HTTP/2 Frame
Normatively referenced by — RFC 8887: A JSON Meta Application Protocol (JMAP) Subprotocol for WebSocket
Informatively referenced by — RFC 8941: Structured Field Values for HTTP
Informatively referenced by — RFC 8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets
Informatively referenced by — RFC 8404: Effects of Pervasive Encryption on Operators
Informatively referenced by — RFC 8895: Application-Layer Traffic Optimization (ALTO) Incremental Updates Using Server-Sent Events (SSE)
Informatively referenced by — RFC 9040: TCP Control Block Interdependence
Informatively referenced by — RFC 8170: Planning for Protocol Adoption and Subsequent Transitions
Informatively referenced by — RFC 8744: Issues and Requirements for Server Name Identification (SNI) Encryption in TLS
Informatively referenced by — RFC 8801: Discovering Provisioning Domain Names and Data
Informatively referenced by — RFC 8188: Encrypted Content-Encoding for HTTP
Informatively referenced by — RFC 8280: Research into Human Rights Protocol Considerations
Informatively referenced by — RFC 7694: Hypertext Transfer Protocol (HTTP) Client-Initiated Content-Encoding
Informatively referenced by — RFC 9006: TCP Usage Guidance in the Internet of Things (IoT)