Re: [Pqc] PQ/T Hybrid Terminology - Basic Definitions

[Mike Ounsworth <[e-mail]>]

Thanks Flo!

I'll add a meta-point about 3: I like "thing1 / thing2 hybrid" because it extends nicely to other things: I can talk about a "PQ/PQ hybrid", or a "PSK/Traditional hybrid", or a "PQ/QKD hybrid" and the meaning is clear. It's a nice qualification and disambiguation of the word "hybrid" which by itself can mean many different things within cryptography.

---
Mike Ounsworth

-----Original Message-----
From: Pqc <[e-mail]> On Behalf Of Florence D
Sent: Wednesday, April 26, 2023 9:14 AM
To: [e-mail]
Subject: [EXTERNAL] [Pqc] PQ/T Hybrid Terminology - Basic Definitions

WARNING: This email originated outside of Entrust.
DO NOT CLICK links or attachments unless you trust the sender and know the content is safe.

______________________________________________________________________
Hi PQUIP and friends,

At the PQUIP meeting at IETF 116 I committed to summarising the discussion on algorithm type naming that happened on the mailing list back in March [1].  The email aims to do that, as well as to provide some justification for the choices made in the draft at the moment. The aim here is to come to some consensus on the base level definitions/names in this draft, allowing us to use this terminology to build from there.

I'll focus on the following definitions:
1. Traditional Algorithm: An asymmetric cryptographic algorithm based on integer factorisation, finite field discrete logarithms or elliptic curve discrete logarithms 2. Post-Quantum Algorithm: An asymmetric cryptographic algorithm that is believed to be secure against quantum computers as well as classical computers.
3. Post-Quantum/Traditional (PQ/T) Hybrid Scheme: A cryptographic scheme made up of two or more component algorithms where at least one is a post-quantum algorithm and at least one is a traditional algorithm.

Taking these one at a time:
1. Traditional Algorithm
        - Alternative words that have been suggested are classical, conventional, pre-quantum, vintage, quantum-vulnerable.  Others have suggested alternatives that describe the mathematical problems that these algorithms are based on e.g., discrete-log or integer-factorisation based.
        - The current version uses "traditional", rather than another word, for these reasons:
                a. It doesn't begin with "C" or "PQ" so can form a helpful and non-confusing acronym.  Conventional/classical seem non-ideal because PQC is already taken as an acronym.
                b. Classical describes a type of computer, and PQ algorithms are run on classical computers.
                c. It is a single word and is not too long or technical. I think this is important if we want the terminology to be used.
                d. It doesn't suggest that these types of algorithms are already insecure before the existence of a CRQC (as e.g., vintage might).
        - Arguments against "traditional" include:
                a. In the long term we might expect PQ algorithms to become "traditional", so this may not age well.
                b. Traditional is one of the words highlighted as potentially biased in NIST's inclusive language guidance [2]. I believe that the usage in this document is sufficiently different to the example in the NIST guidance that it is reasonable to use the word here, but it is worth taking into consideration.

2. Post-Quantum Algorithm
        - Alternative words: quantum-safe, quantum-resistant.
        - The current version uses "post-quantum" for these reasons:
                a. It is currently the most widely used term for this algorithm type.
                b. Quantum-safe and quantum-resistant suggest properties of the security achieved by the algorithms, rather than the security goals of the algorithm.  For example, SIKE is a post-quantum algorithm, but calling it a quantum-safe algorithm is (at best) highly misleading.
                c. Quantum-safe has previously been used to include both PQC and QKD (e.g. by ETSI).

3. PQ/T Hybrid Scheme
        - Obviously this decision depends on 1. and 2. above.
        - I am currently using PQ/T hybrid scheme for this concept because I believe it does a good job of describing the components, giving a technical reader who hasn't read this document has a good chance of understanding the meaning.
        - There was previously discussion on this thread about including a forward slash in the name [3], which suggested that the group preferred some separation between the two algorithm types.  This does raise a question about if you pronounce the slash (I think no...).

If you have alternative suggestions for 1,2 and 3 which have fewer compromises than what we've got so far then I'd be very keen to hear them, please do post to the list or email me directly if you'd prefer.  Also, if you'd like to add any more pros/cons to this discussion please do reply.

Flo

[1] https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/msg/pqc/3hKDhB8r8wnbG5M_iTb8JIrIaGc/__;!!FJ-Y8qCqXTj2!baNqQZnmNBjxnnW3uDtQCda9RKDmFgsd8b62BMF8-61eA1Rc3kyJClXvl1d1SbBpoMeTaEGDuqON3dHufyU6r8APdGcmnV6Ho8kb$
[2] https://urldefense.com/v3/__https://www.nist.gov/nist-research-library/nist-technical-series-publications-author-instructions*table1__;Iw!!FJ-Y8qCqXTj2!baNqQZnmNBjxnnW3uDtQCda9RKDmFgsd8b62BMF8-61eA1Rc3kyJClXvl1d1SbBpoMeTaEGDuqON3dHufyU6r8APdGcmndUoEiHs$
[3] https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/msg/pqc/IntVA7nMUcBDqlg2wvV-5YGA-7g/__;!!FJ-Y8qCqXTj2!baNqQZnmNBjxnnW3uDtQCda9RKDmFgsd8b62BMF8-61eA1Rc3kyJClXvl1d1SbBpoMeTaEGDuqON3dHufyU6r8APdGcmnaC7Y89m$
--
Pqc mailing list
[e-mail]
https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/pqc__;!!FJ-Y8qCqXTj2!baNqQZnmNBjxnnW3uDtQCda9RKDmFgsd8b62BMF8-61eA1Rc3kyJClXvl1d1SbBpoMeTaEGDuqON3dHufyU6r8APdGcmnXCw0JUA$
Any email and files/attachments transmitted with it are confidential and are intended solely for the use of the individual or entity to whom they are addressed. If this message has been sent to you in error, you must not copy, distribute or disclose of the information it contains. Please notify Entrust immediately and delete the message from your system.