| Internet-Draft | PQ Guidance for TLS | December 2024 |
| Farrell | Expires 18 June 2025 | [Page] |
We provide guidance on the use of post-quantum algorithms for those deploying applications using TLS.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 18 June 2025.¶
Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
[[This is not an "official" TLS WG work item, but is being proposed as such. The source for this is in https://github.com/sftcd/pqg/ PRs are welcome there too.]]¶
Due to concerns about the possible future existence of a cryptographically relevant quantum computer (CRQC), additional TLS [RFC8446] codepoints have been defined for algorithms that are hoped to remain secure even in the face of a CRQC. Adding code-points for to the relevant IANA registries with the RECOMMENDED column set to 'n' doesn't require IETF consensus. This means that anyone can register code-points for their favoured approach. In particular various government entities in various countries have made contradictory recommendations in this space, leading to potential confusion for those deploying applilcations using TLS.¶
This document sets out a deliberately consise sets of recommendations for typical uses of post-quantum algorithms. This assumes the reader is familiar with the topic.¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
The main recommendation is to move as soon as practical to use of hybrid KEMs, such as X25519MLKEM768.¶
Once it becomes practical to do the above, we do not recommend use of non-hybrid groups.¶
We recommend taking no action at all at this point in time in relation to signatures.¶
TBD¶
TBD¶
TBD, but probably not needed.¶