RFC 6455: The WebSocket Protocol

The WebSocket Protocol enables two-way communication between a client running untrusted code in a controlled environment to a remote host that has opted-in to…

Read RFC 6455 on the RFC Editor

Incoming relationships (19 related RFCs)

Updated by — RFC 8441: Bootstrapping WebSockets with HTTP/2
Updated by — RFC 7936: Clarifying Registry Procedures for the WebSocket Subprotocol Name Registry
Updated by, Normatively referenced by — RFC 8307: Well-Known URIs for the WebSocket Protocol
Normatively referenced by — RFC 9460: Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)
Normatively referenced by — RFC 9220: Bootstrapping WebSockets with HTTP/3
Normatively referenced by — RFC 7692: Compression Extensions for WebSocket
Normatively referenced by — RFC 7977: The WebSocket Protocol as a Transport for the Message Session Relay Protocol (MSRP)
Normatively referenced by — RFC 8857: The WebSocket Protocol as a Transport for the Binary Floor Control Protocol (BFCP)
Normatively referenced by — RFC 8887: A JSON Meta Application Protocol (JMAP) Subprotocol for WebSocket
Informatively referenced by — RFC 6454: The Web Origin Concept
Informatively referenced by — RFC 8827: WebRTC Security Architecture
Informatively referenced by — RFC 8864: Negotiation Data Channels Using the Session Description Protocol (SDP)
Informatively referenced by — RFC 9298: Proxying UDP in HTTP
Informatively referenced by — RFC 8404: Effects of Pervasive Encryption on Operators
Informatively referenced by — RFC 8170: Planning for Protocol Adoption and Subsequent Transitions
Informatively referenced by — RFC 9297: HTTP Datagrams and the Capsule Protocol
Informatively referenced by — RFC 8743: Multiple Access Management Services Multi-Access Management Services (MAMS)
Informatively referenced by — RFC 8963: Evaluation of a Sample of RFCs Produced in 2018
Informatively referenced by — RFC 9931: Security Considerations for Optimistic Protocol Transitions in HTTP/1.1