RFC 4975: The Message Session Relay Protocol (MSRP)
In plain English — editorial summary, not part of the RFC
This document describes the Message Session Relay Protocol, a protocol for transmitting a series of related instant messages in the context of a session. Message sessions are treated like any other media stream when set up via a rendezvous or session creation protocol such as the Session Initiation Protocol. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4975
- Published
- September 2007
- Authors
- B. Campbell; R. Mahy; C. Jennings
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 63
- Also known as
- —
Topics
Referenced by
4 later RFCs formally update or obsolete part of this document.
- RFC 7977The WebSocket Protocol as a Transport for the Message Session Relay Protocol (MSRP)Current
September 2016
- RFC 8591SIP-Based Messaging with S/MIMECurrent
April 2019
- RFC 8873Message Session Relay Protocol (MSRP) over Data ChannelsCurrent
January 2021
- RFC 8996Deprecating TLS 1.0 and TLS 1.1Current
March 2021
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7572Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Instant MessagingCurrent
June 2015
- RFC 4976Relay Extensions for the Message Sessions Relay Protocol (MSRP)Updated
September 2007
- RFC 4979IANA Registration for Enumservice 'XMPP'Updated
August 2007
- RFC 4969IANA Registration for vCard EnumserviceUpdated
August 2007
- RFC 4958A Framework for Supporting Emergency Telecommunications Services (ETS) within a Single Administrative DomainCurrent
July 2007
- RFC 5018Connection Establishment in the Binary Floor Control Protocol (BFCP)Updated
September 2007
- RFC 5025Presence Authorization RulesCurrent
December 2007
- RFC 5028A Telephone Number Mapping (ENUM) Service Registration for Instant Messaging (IM) ServicesUpdated
October 2007
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?