RFC 4976: Relay Extensions for the Message Sessions Relay Protocol (MSRP)
In plain English — editorial summary, not part of the RFC
Two separate models for conveying instant messages have been defined. Page-mode messages stand alone and are not part of a Session Initiation Protocol (SIP) session, whereas session-mode messages are set up as part of a session using SIP. The Message Session Relay Protocol (MSRP) is a protocol for near real-time, peer-to-peer exchanges of binary content without intermediaries, which is designed to be signaled using a separate rendezvous protocol such as SIP. This document introduces the notion of message relay intermediaries to MSRP and describes the extensions necessary to use them. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4976
- Published
- September 2007
- Authors
- C. Jennings; R. Mahy; A. B. Roach
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 36
- Also known as
- —
Topics
Referenced by
3 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4975The Message Session 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
- RFC 4916Connected Identity in the Session Initiation Protocol (SIP)Current
June 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?