Javascript disabled? Like other modern websites, the IETF Datatracker relies on Javascript. Please enable Javascript for full functionality.

SIP-Based Messaging with S/MIME
RFC 8591

Revision differences

From revision

To revision

Diff format

Document history

Date	By	Action
2019-08-19	Gunter Van de Velde	Closed request for Last Call review by OPSDIR with state 'Overtaken by Events'
2019-08-19	Gunter Van de Velde	Assignment of request for Last Call review by OPSDIR to Tim Wicinski was marked no-response
2019-04-30	(System)	Received changes through RFC Editor sync (created alias RFC 8591, changed title to 'SIP-Based Messaging with S/MIME', changed abstract to 'Mobile messaging applications used … Received changes through RFC Editor sync (created alias RFC 8591, changed title to 'SIP-Based Messaging with S/MIME', changed abstract to '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.', changed pages to 39, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2019-04-30, changed IESG state to RFC Published, created updates relation between draft-campbell-sip-messaging-smime and RFC 3261, created updates relation between draft-campbell-sip-messaging-smime and RFC 3428, created updates relation between draft-campbell-sip-messaging-smime and RFC 4975)
2019-04-30	(System)	RFC published