RFC 7702: Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Groupchat
In plain English — editorial summary, not part of the RFC
This document defines a bidirectional protocol mapping for the exchange of instant messages in the context of a multi-party chat session among users of the Session Initiation Protocol (SIP) and users of the Extensible Messaging and Presence Protocol (XMPP). Specifically, this document defines a mapping between the SIP-based Message Session Relay Protocol (MSRP) and the XMPP Multi-User Chat (MUC) extension.
Document record
- Document ID
- RFC7702
- Published
- December 2015
- Authors
- P. Saint-Andre; S. Ibarra; S. Loreto
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 43
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- 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 8048Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): PresenceCurrent
December 2016
- RFC 7700Preparation, Enforcement, and Comparison of Internationalized Strings Representing NicknamesObsoleted
December 2015
- RFC 7622Extensible Messaging and Presence Protocol (XMPP): Address FormatUpdated
September 2015
- RFC 7248Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): PresenceObsoleted
May 2014
- RFC 8266Preparation, Enforcement, and Comparison of Internationalized Strings Representing NicknamesCurrent
October 2017
- RFC 6121Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and PresenceCurrent
March 2011
- RFC 6120Extensible Messaging and Presence Protocol (XMPP): CoreUpdated
March 2011
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?