Subject: [dispatch] Fwd: New Version Notification for draft-campbell-sip-messaging-smime-02.txt

From: Ben Campbell <[email-masked]>
Date: Tue, 26 Dec 2017 17:35:47 -0600

(as an individual contributor)

Hi,

Here’s version 02 of draft-campbell-sip-messaging-smime. This version includes the examples, and attempts to address the feedback we have received so far. As always, further feedback is welcome.

Thanks!

Ben.

> Begin forwarded message:
> 
> From: [email-masked]
> Subject: New Version Notification for draft-campbell-sip-messaging-smime-02.txt
> Date: December 26, 2017 at 5:28:01 PM CST
> To: "Ben Campbell" <[email-masked]>, "Russ Housley" <[email-masked]>
> 
> 
> A new version of I-D, draft-campbell-sip-messaging-smime-02.txt
> has been successfully submitted by Ben Campbell and posted to the
> IETF repository.
> 
> Name:		draft-campbell-sip-messaging-smime
> Revision:	02
> Title:		Securing Session Initiation Protocol (SIP) based Messaging with S/MIME
> Document date:	2017-12-26
> Group:		Individual Submission
> Pages:		36
> URL:            https://www.ietf.org/internet-drafts/draft-campbell-sip-messaging-smime-02.txt
> Status:         https://datatracker.ietf.org/doc/draft-campbell-sip-messaging-smime/
> Htmlized:       https://tools.ietf.org/html/draft-campbell-sip-messaging-smime-02
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-campbell-sip-messaging-smime-02
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-campbell-sip-messaging-smime-02
> 
> 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 RFC
>   3261, RFC 3428, and RFC 4975.
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
>