[lamps] draft-housley-cms-mix-with-psk-03

Russ Housley <housley@vigilsec.com> Mon, 05 March 2018 20:23 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24F8812D810 for <spasm@ietfa.amsl.com>; Mon, 5 Mar 2018 12:23:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 TRv1qMo2LpkF for <spasm@ietfa.amsl.com>; Mon, 5 Mar 2018 12:23:12 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9963412E8AA for <spasm@ietf.org>; Mon, 5 Mar 2018 12:23:11 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 7D9E2300A14 for <spasm@ietf.org>; Mon, 5 Mar 2018 15:23:09 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id tuHTRwbq3oSA for <spasm@ietf.org>; Mon, 5 Mar 2018 15:23:08 -0500 (EST)
Received: from a860b60074bd.home (pool-108-45-101-150.washdc.fios.verizon.net [108.45.101.150]) by mail.smeinc.net (Postfix) with ESMTPSA id 41589300558 for <spasm@ietf.org>; Mon, 5 Mar 2018 15:23:08 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Message-Id: <836CB2DA-9A82-4DEC-845A-15A7ED195C8A@vigilsec.com>
Date: Mon, 5 Mar 2018 15:23:09 -0500
To: SPASM <spasm@ietf.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/ibpFSO3L0d4WJ0Xnr30EnrpX2sQ>
Subject: [lamps] draft-housley-cms-mix-with-psk-03
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2018 20:23:23 -0000

I would like to make people on this mail list aware of this Internet-Draft.

Russ

= = = = = = = = = =

A new version of I-D, draft-housley-cms-mix-with-psk-03.txt
has been successfully submitted by Russell Housley and posted to the
IETF repository.

Name:		draft-housley-cms-mix-with-psk
Revision:	03
Title:		Using Pre-Shared Key (PSK) in the Cryptographic Message Syntax (CMS)
Document date:	2018-03-05
Group:		Individual Submission
Pages:		13
URL:            https://www.ietf.org/internet-drafts/draft-housley-cms-mix-with-psk-03.txt
Status:         https://datatracker.ietf.org/doc/draft-housley-cms-mix-with-psk/
Htmlized:       https://tools.ietf.org/html/draft-housley-cms-mix-with-psk-03
Htmlized:       https://datatracker.ietf.org/doc/html/draft-housley-cms-mix-with-psk-03
Diff:           https://www.ietf.org/rfcdiff?url2=draft-housley-cms-mix-with-psk-03

Abstract:
  The invention of a large-scale quantum computer would pose a serious
  challenge for the cryptographic algorithms that are widely deployed
  today.  The Cryptographic Message Syntax (CMS) supports key transport
  and key agreement algorithms that could be broken by the invention of
  such a quantum computer.  By storing communications that are
  protected with the CMS today, someone could decrypt them in the
  future when a large-scale quantum computer becomes available.  Once
  quantum-secure key management algorithms are available, the CMS will
  be extended to support them, if current syntax the does not
  accommodated them.  In the near-term, this document describes a
  mechanism to protect today's communication from the future invention
  of a large-scale quantum computer by mixing the output of key
  transport and key agreement algorithms with a pre-shared key.