SIP-Based Messaging with S/MIME
RFC 8591, “SIP-Based Messaging with S/MIME”, is a Proposed Standard document published in April 2019 by B. Campbell, R. Housley. It updates RFC 3261, RFC 3428, RFC 4975. The canonical text is published by the RFC Editor.
Abstract
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.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 8591 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 8590 Change Poll Extension for the Extensible Provisioning Protocol
- RFC 8592 Key Performance Indicator Stamping for the Network Service Header
- RFC 8589 The 'leaptofrogans' URI Scheme
- RFC 8593 Video Traffic Models for RTP Congestion Control Evaluations
- RFC 8588 Personal Assertion Token Extension for Signature-based Handling of Asserted information using toKENs
- RFC 8594 The Sunset HTTP Header Field
- RFC 8587 NFS Version 4.0 Trunking Update
- RFC 8595 An MPLS-Based Forwarding Plane for Service Function Chaining