idnits 2.17.1 draft-mattsson-tls-psk-ke-dont-dont-dont-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The document seems to lack a Security Considerations section. ** The abstract seems to contain references ([RFC8446], [I-D.ietf-emu-aka-pfs], [RFC8447], [RFC7258]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (November 18, 2020) is 1253 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-12) exists of draft-ietf-emu-aka-pfs-05 Summary: 3 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Preuss Mattsson 3 Internet-Draft Ericsson 4 Intended status: Standards Track November 18, 2020 5 Expires: May 22, 2021 7 Key Exchange Without Forward Secrecy is Not Recommended 8 draft-mattsson-tls-psk-ke-dont-dont-dont-00 10 Abstract 12 Key exchange without forward secrecy enables passive monitoring 13 [RFC7258]. Massive pervasive monitoring attacks relying on key 14 exchange without forward secrecy has been reported 15 [I-D.ietf-emu-aka-pfs]. If key exchange without Diffe-Hellan is 16 used, compromise of the long-term authenticatation key enables a 17 passive attacker to compromise past and future sessions. All TLS 1.2 18 cipher suites without forward secrecy has been marked as NOT 19 RECOMMENDED [RFC8447], and static RSA has been forbidden in TLS 1.3 20 [RFC8446]. psk_ke does not provide forward secrecy and is NOT 21 RECOMMENDED. This document sets the IANA registration of psk_ke to 22 NOT RECOMMENDED. 24 Status of This Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at https://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on May 22, 2021. 41 Copyright Notice 43 Copyright (c) 2020 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (https://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2 59 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 60 3. References . . . . . . . . . . . . . . . . . . . . . . . . . 2 61 3.1. Normative References . . . . . . . . . . . . . . . . . . 2 62 3.2. Informative References . . . . . . . . . . . . . . . . . 3 63 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 3 64 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3 66 1. Terminology 68 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 69 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 70 "OPTIONAL" in this document are to be interpreted as described in BCP 71 14 [RFC2119] [RFC8174] when, and only when, they appear in all 72 capitals, as shown here. 74 2. IANA Considerations 76 IANA is requested to update the PskKeyExchangeMode registry under the 77 Transport Layer Security (TLS) Parameters heading. For psk_ke the 78 "Recommended" value has been set to "N". 80 3. References 82 3.1. Normative References 84 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 85 Requirement Levels", BCP 14, RFC 2119, 86 DOI 10.17487/RFC2119, March 1997, 87 . 89 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 90 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 91 May 2017, . 93 3.2. Informative References 95 [I-D.ietf-emu-aka-pfs] 96 Arkko, J., Norrman, K., and V. Torvinen, "Perfect-Forward 97 Secrecy for the Extensible Authentication Protocol Method 98 for Authentication and Key Agreement (EAP-AKA' PFS)", 99 draft-ietf-emu-aka-pfs-05 (work in progress), October 100 2020. 102 [RFC7258] Farrell, S. and H. Tschofenig, "Pervasive Monitoring Is an 103 Attack", BCP 188, RFC 7258, DOI 10.17487/RFC7258, May 104 2014, . 106 [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol 107 Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, 108 . 110 [RFC8447] Salowey, J. and S. Turner, "IANA Registry Updates for TLS 111 and DTLS", RFC 8447, DOI 10.17487/RFC8447, August 2018, 112 . 114 Acknowledgments 116 The authors want to thank Ari Keraenen for their valuable comments 117 and feedback. 119 Author's Address 121 John Preuss Mattsson 122 Ericsson 124 Email: john.mattsson@ericsson.com