RFC 8591 on SIP-Based Messaging with S/MIME

rfc-editor@rfc-editor.org Wed, 01 May 2019 01:08 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 17B1E120446 for <ietf-announce@ietfa.amsl.com>; Tue, 30 Apr 2019 18:08:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id zg9ZOE1UwfgC for <ietf-announce@ietfa.amsl.com>; Tue, 30 Apr 2019 18:08:34 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE1C8120432 for <ietf-announce@ietf.org>; Tue, 30 Apr 2019 18:08:34 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 22EB4B81C45; Tue, 30 Apr 2019 18:08:23 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg1OTEgb24gU0lQLUJhc2VkIE1lc3NhZ2luZyB3aXRoIFMvTUlNRQ==?=
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20190501010823.22EB4B81C45@rfc-editor.org>
Date: Tue, 30 Apr 2019 18:08:23 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/Qyump5VzyK0s73ymHugxI5Ua9CU>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 May 2019 01:08:42 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 8591

        Title:      SIP-Based Messaging with S/MIME 
        Author:     B. Campbell,
                    R. Housley
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2019
        Mailbox:    ben@nostrum.com, 
        Pages:      39
        Characters: 91547
        Updates:    RFC 3261, RFC 3428, RFC 4975

        I-D Tag:    draft-campbell-sip-messaging-smime-05.txt

        URL:        https://www.rfc-editor.org/info/rfc8591

        DOI:        10.17487/RFC8591

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.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC