RFC 8591: SIP-Based Messaging with S/MIME
In plain English — editorial summary, not part of the RFC
Mobile messaging applications used with the Session Initiation Protocol (SIP) commonly use some combination of the SIP MESSAGE method and the Message Session Relay Protocol (MSRP). While these provide mechanisms for hop-by-hop security, neither natively provides end-to-end protection. This document offers guidance on how to provide end-to-end authentication, integrity protection, and confidentiality using the Secure/Multipurpose Internet Mail Extensions (S/MIME). It updates and provides clarifications for RFCs 3261, 3428, and 4975.
Document record
- Document ID
- RFC8591
- Published
- April 2019
- Authors
- B. Campbell; R. Housley
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 39
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8266Preparation, Enforcement, and Comparison of Internationalized Strings Representing NicknamesCurrent
October 2017
- RFC 7977The WebSocket Protocol as a Transport for the Message Session Relay Protocol (MSRP)Current
September 2016
- 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 7573Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): One-to-One Text Chat SessionsCurrent
June 2015
- RFC 5547A Session Description Protocol (SDP) Offer/Answer Mechanism to Enable File TransferCurrent
May 2009
- RFC 5438Instant Message Disposition Notification (IMDN)Current
February 2009
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?