RFC 7977: The WebSocket Protocol as a Transport for the Message Session Relay Protocol (MSRP)
In plain English — editorial summary, not part of the RFC
The WebSocket protocol enables two-way real-time communication between clients and servers in situations where direct access to TCP and UDP is not available (for example, from within JavaScript in a web browser). This document specifies a new WebSocket subprotocol as a reliable transport mechanism between Message Session Relay Protocol (MSRP) clients and relays to enable usage of MSRP in new scenarios. This document normatively updates RFCs 4975 and 4976.
Document record
- Document ID
- RFC7977
- Published
- September 2016
- Authors
- P. Dunkley; G. Llewellyn; V. Pascual; G. Salgueiro; R. Ravindranath
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 28
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7702Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): GroupchatCurrent
December 2015
- RFC 7701Multi-party Chat Using the Message Session Relay Protocol (MSRP)Current
December 2015
- RFC 7700Preparation, Enforcement, and Comparison of Internationalized Strings Representing NicknamesObsoleted
December 2015
- RFC 8266Preparation, Enforcement, and Comparison of Internationalized Strings Representing NicknamesCurrent
October 2017
- RFC 8307Well-Known URIs for the WebSocket ProtocolCurrent
January 2018
- RFC 7573Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): One-to-One Text Chat SessionsCurrent
June 2015
- RFC 7478Web Real-Time Communication Use Cases and RequirementsCurrent
March 2015
- RFC 7395An Extensible Messaging and Presence Protocol (XMPP) Subprotocol for WebSocketCurrent
October 2014
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?