IETF Logo Mail Archive

Re: [Cfrg] A terminology issue with "post-quantum cryptography"

"Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com> Fri, 18 August 2017 11:36 UTC

Return-Path: <chris.dearlove@baesystems.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 D466313202D for <cfrg@ietfa.amsl.com>; Fri, 18 Aug 2017 04:36:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.92
X-Spam-Level:
X-Spam-Status: No, score=-6.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] 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 mIj8qICv-ntv for <cfrg@ietfa.amsl.com>; Fri, 18 Aug 2017 04:36:06 -0700 (PDT)
Received: from ukmta1.baesystems.com (ukmta1.baesystems.com [20.133.0.55]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1325E126B71 for <cfrg@irtf.org>; Fri, 18 Aug 2017 04:36:05 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.41,392,1498518000"; d="scan'208";a="19401297"
Received: from unknown (HELO baemasmds016.greenlnk.net) ([10.15.207.101]) by ukmta1.baesystems.com with ESMTP; 18 Aug 2017 12:36:04 +0100
X-IronPort-AV: E=Sophos;i="5.41,392,1498518000"; d="scan'208";a="17223608"
Received: from glkxh0005v.greenlnk.net ([10.109.2.36]) by baemasmds016.greenlnk.net with ESMTP; 18 Aug 2017 12:36:04 +0100
Received: from GLKXM0003V.GREENLNK.net ([169.254.4.199]) by GLKXH0005V.GREENLNK.net ([10.109.2.36]) with mapi id 14.03.0361.001; Fri, 18 Aug 2017 12:36:04 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Kyle Rose <krose@krose.org>, Paul Hoffman <paul.hoffman@icann.org>
CC: "cfrg@irtf.org" <cfrg@irtf.org>
Thread-Topic: [Cfrg] A terminology issue with "post-quantum cryptography"
Thread-Index: AQHTFrjlYTwQzQbzSEaiw4aerLAloKKHNOAAgALJX3A=
Date: Fri, 18 Aug 2017 11:36:02 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30DE64F85BA@GLKXM0003v.GREENLNK.net>
References: <5397C02D-A4C5-47CD-9383-E47D3262D8C4@icann.org> <CAJU8_nXSi_8XpvAYm8yBy7gDwUuRw4F6VLTqjcp-5ueDiXuWYQ@mail.gmail.com>
In-Reply-To: <CAJU8_nXSi_8XpvAYm8yBy7gDwUuRw4F6VLTqjcp-5ueDiXuWYQ@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/cfrg/yzVtP7L9NDfamtoxuvbVFY02-Fo>
Subject: Re: [Cfrg] A terminology issue with "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: Fri, 18 Aug 2017 11:36:08 -0000

Kyle Rose
> I wonder if "quantum resistant cryptography" is a better phrasing.

Technically, I think it definitely is. Unfortunately when I last (a few month ago) tried the crude "how many hits in Google" test, Post-Quantum Cryptography won hands down.

(There's also a significant usage of the phrase Quantum Safe cryptography out there.)


********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************

v2.23.0 | Report a Bug | By Email