IETF Logo Mail Archive

Re: [Cfrg] New draft on the transition from classical to post-quantum cryptography

"Salz, Rich" <rsalz@akamai.com> Mon, 08 May 2017 12:46 UTC

Return-Path: <rsalz@akamai.com>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C57DB129461 for <cfrg@ietfa.amsl.com>; Mon, 8 May 2017 05:46:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.com
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 ybqsHyUMXw1q for <cfrg@ietfa.amsl.com>; Mon, 8 May 2017 05:46:19 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7130129459 for <cfrg@irtf.org>; Mon, 8 May 2017 05:46:19 -0700 (PDT)
Received: from pps.filterd (m0050102.ppops.net [127.0.0.1]) by m0050102.ppops.net-00190b01. (8.16.0.21/8.16.0.21) with SMTP id v48C702Z028349; Mon, 8 May 2017 13:46:18 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-transfer-encoding : mime-version; s=jan2016.eng; bh=tupL+Mew9PRaXqa0m3iFLSdbIeESnetx7x02xQ1XhFk=; b=GYUDbtnZz9rsX+BW6jf4LPj6hhv3ltar/LE9UMCAg403hwk7Rojs+VvkyjFDIZpWAeRJ APX64Oi+S+GoHQz7ouihbja7dp/xKAPtG8XKN8+W/HFsZXxOIjb1SHUcfrBmaTUaLZZR FFoQeuC4NBnOfb2azsDepNyKDBoCpNk6zDeMwdEP41H6KP9ejXqxOoeoGtejVwp07BNW uMGdBl+CeyBw1fyiXoh/W0OqzC/ZYq6jQ3nY9ykOP+tbXS6UASF0UXwf5wT0kOMSFcap 7j0yHNrVs6QVGHMaQsjIjQPtgYRz3oJl4WvceEudz8QL+a8u42CcUTj/g8h2JByw2eUp cA==
Received: from prod-mail-ppoint4 ([96.6.114.87]) by m0050102.ppops.net-00190b01. with ESMTP id 2aaqp8rcsk-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 08 May 2017 13:46:18 +0100
Received: from pps.filterd (prod-mail-ppoint4.akamai.com [127.0.0.1]) by prod-mail-ppoint4.akamai.com (8.16.0.17/8.16.0.17) with SMTP id v48CBbBR029263; Mon, 8 May 2017 08:46:17 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.30]) by prod-mail-ppoint4.akamai.com with ESMTP id 2a99tvv7sy-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 08 May 2017 08:46:17 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb1.msg.corp.akamai.com (172.27.123.101) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Mon, 8 May 2017 08:46:16 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([172.27.123.101]) by usma1ex-dag1mb1.msg.corp.akamai.com ([172.27.123.101]) with mapi id 15.00.1263.000; Mon, 8 May 2017 08:46:16 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>, "Tams, Benjamin" <Benjamin.Tams@secunet.com>
CC: "cfrg@irtf.org" <cfrg@irtf.org>
Thread-Topic: [Cfrg] New draft on the transition from classical to post-quantum cryptography
Thread-Index: AQHSxFym/EWb0YnqLEyGCC6sAdbti6HkSl2AgAWRToCAAI0kAA==
Date: Mon, 08 May 2017 12:46:15 +0000
Message-ID: <0d785b8b616846e9aa0eda962d1aade5@usma1ex-dag1mb1.msg.corp.akamai.com>
References: <BAE7613D-D89C-4F19-8FA5-1D3BCC55DCCB@vpnc.org> <78B0B91A8FEB2E43B20BCCE132613181399287CA@mail-essen-01.secunet.de> <9E0DFD44-3000-4E5B-BAE6-2EF74DB3EA4E@vpnc.org>
In-Reply-To: <9E0DFD44-3000-4E5B-BAE6-2EF74DB3EA4E@vpnc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.43.53]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-05-08_08:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1705080069
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-05-08_08:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1705080069
Archived-At: <https://mailarchive.ietf.org/arch/msg/cfrg/pB8JRzrzChb_yrWKuF1aAwdH52k>
Subject: Re: [Cfrg] New draft on the transition from classical to post-quantum cryptography
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cfrg/>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 May 2017 12:46:21 -0000

> And I completely want to avoid any discussion of such a specification in this
> document; I consider "when you want to move to post-quantum"
> orthogonal to "at the time you move, here are your best options".

Well, it's not of course.  What you do when you move depends on what is available at that time and options are likely to improve as Science Marches Forward.

I also think when to move depends on what you're trying to do. The protection you need for online ecommerce buying razor blades is very different from launching missles is very different from long-term archival storage of official documents.

I think both of these things should at least be touched on.

v2.20.3 | Report a Bug | By Email