[dispatch] draft-campbell-sip-messaging-smime

Ben Campbell <ben@nostrum.com> Thu, 07 December 2017 19:01 UTC

Return-Path: <ben@nostrum.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B63CA1294CE for <dispatch@ietfa.amsl.com>; Thu, 7 Dec 2017 11:01:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.879
X-Spam-Level:
X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xMYGsYQTvsrF for <dispatch@ietfa.amsl.com>; Thu, 7 Dec 2017 11:01:43 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D6601241F5 for <dispatch@ietf.org>; Thu, 7 Dec 2017 11:01:43 -0800 (PST)
Received: from [10.0.1.92] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id vB7J1dfr096668 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 7 Dec 2017 13:01:40 -0600 (CST) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.92]
From: Ben Campbell <ben@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_A424D2DD-DFD7-47BF-8221-DEA1CF07B690"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Message-Id: <5876660C-0F28-4906-B815-FEA8EDBF7127@nostrum.com>
Date: Thu, 07 Dec 2017 13:01:38 -0600
Cc: Cullen Jennings <fluffy@iii.ca>, Mary Barnes <mary.ietf.barnes@gmail.com>, "Murray S. Kucherawy" <superuser@gmail.com>, Russ Housley <housley@vigilsec.com>
To: DISPATCH <dispatch@ietf.org>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/LjQ32_whtKlTPALVzyLiRtT_aFw>
Subject: [dispatch] draft-campbell-sip-messaging-smime
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Dec 2017 19:01:44 -0000

(as an individual contributor)

Hi,

Russ and I submitted a revision of the S/MIME for SIP Messaging clarification draft last week. We request that this version be run through the dispatch process:

https://tools.ietf.org/html/draft-campbell-sip-messaging-smime-01

We’ve tried to clarify the problem statement and scope of the work in section 3, and to address most of the other feedback we received in the meeting or on the mail list. There are still some open issues, but I don’t think those should preclude making some plans about how to progress the work.

My personal opinion is that this should progress as an AD sponsored draft if Adam or Alexey are willing. I don’t think this is a large enough effort to justify a new WG (mini or otherwise). Parts of it seem to fit the SIPCORE charter, but the MSRP related bits don’t really have a home. (unless we want to restart SIMPLE ;-)  )

We recognize that there is skepticism about the relevance of both SIMPLE based messaging and S/MIME. However, a number of wireless operators are showing a renewed interest in the GSMA RCS, which uses both SIP MESSAGE and MSRP, and at least some of that community is interested in the secure notification use case.

Thanks!

Ben.