idnits 2.17.1 draft-ietf-kitten-tls-channel-bindings-for-tls13-01.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 draft header indicates that this document updates RFC5802, but the abstract doesn't seem to mention this, which it should. -- The draft header indicates that this document updates RFC8446, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (18 November 2020) is 1248 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) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Transport Layer Security S. Whited 3 Internet-Draft 18 November 2020 4 Updates: 5802, 8446 (if approved) 5 Intended status: Standards Track 6 Expires: 22 May 2021 8 Channel Bindings for TLS 1.3 9 draft-ietf-kitten-tls-channel-bindings-for-tls13-01 11 Abstract 13 This document defines a channel binding type, tls-exporter, that is 14 compatible with TLS 1.3 in accordance with RFC 5056, On Channel 15 Binding. 17 Status of This Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF). Note that other groups may also distribute 24 working documents as Internet-Drafts. The list of current Internet- 25 Drafts is at https://datatracker.ietf.org/drafts/current/. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 This Internet-Draft will expire on 22 May 2021. 34 Copyright Notice 36 Copyright (c) 2020 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 41 license-info) in effect on the date of publication of this document. 42 Please review these documents carefully, as they describe your rights 43 and restrictions with respect to this document. Code Components 44 extracted from this document must include Simplified BSD License text 45 as described in Section 4.e of the Trust Legal Provisions and are 46 provided without warranty as described in the Simplified BSD License. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 51 1.1. Conventions and Terminology . . . . . . . . . . . . . . . 2 52 2. The 'tls-exporter' Channel Binding Type . . . . . . . . . . . 2 53 3. Security Considerations . . . . . . . . . . . . . . . . . . . 3 54 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 55 4.1. Registration of Channel Binding Type . . . . . . . . . . 3 56 4.2. Registration of Channel Binding TLS Exporter Label . . . 4 57 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 58 5.1. Normative References . . . . . . . . . . . . . . . . . . 4 59 5.2. Informative References . . . . . . . . . . . . . . . . . 4 60 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5 62 1. Introduction 64 The channel binding types defined in [RFC5929] were found to be 65 vulnerable to the "triple handshake vulnerability" [TRIPLE-HANDSHAKE] 66 without the extended master secret extension defined in [RFC7627]. 67 Because of this they were not defined for TLS 1.3 (see [RFC8446] 68 section C.5). To facilitate channel binding with TLS 1.3, a new 69 channel binding type is needed. 71 1.1. Conventions and Terminology 73 Throughout this document the acronym "EKM" is used to refer to 74 Exported Keying Material as defined in [RFC5705]. 76 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 77 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 78 "OPTIONAL" in this document are to be interpreted as described in BCP 79 14 [RFC2119] [RFC8174] when, and only when, they appear in all 80 capitals, as shown here. 82 2. The 'tls-exporter' Channel Binding Type 84 Channel binding mechanisms are not useful until TLS implementations 85 expose the required data. To facilitate this, "tls-exporter" uses 86 exported keying material (EKM) which is already widely exposed by TLS 87 implementations. The EKM is obtained using the keying material 88 exporters for TLS as defined in [RFC5705] and [RFC8446] section 7.5 89 by supplying the following inputs: 91 Label: The ASCII string "EXPORTER-Channel-Binding" with no 92 terminating NUL. 94 Context value: Empty context value. 96 Length: 32 bytes. 98 When TLS renegotiation is enabled the "tls-exporter" channel binding 99 type is not defined and implementations MUST NOT support it. 101 3. Security Considerations 103 While it is possible to use this channel binding mechanism with TLS 104 versions below 1.3, extra precaution must be taken to ensure that the 105 chosen cipher suites always result in unique master secrets. For 106 more information see the Security Considerations section of 107 [RFC5705]. 109 The Security Considerations sections of [RFC5056], [RFC5705], and 110 [RFC8446] apply to this document. 112 4. IANA Considerations 114 4.1. Registration of Channel Binding Type 116 This document adds the following registration in the "Channel-Binding 117 Types" registry: 119 Subject: Registration of channel binding tls-exporter 121 Channel binding unique prefix: tls-exporter 123 Channel binding type: unique 125 Channel type: TLS [RFC8446] 127 Published specification: draft-ietf-kitten-tls-channel-bindings-for- 128 tls13-01 130 Channel binding is secret: no 132 Description: The EKM value obtained from the current TLS connection. 134 Intended usage: COMMON 136 Person and email address to contact for further information: Sam 137 Whited . 139 Owner/Change controller name and email address: IESG. 141 Expert reviewer name and contact information: IETF KITTEN or TLS WG 142 (kitten@ietf.org or tls@ietf.org, failing that, ietf@ietf.org). 144 Note: See the published specification for advice on the 145 applicability of this channel binding type. 147 4.2. Registration of Channel Binding TLS Exporter Label 149 This document adds the following registration in the "TLS Exporter 150 Labels" registry: 152 Value: EXPORTER-Channel-Binding 154 DTLS-OK: Y 156 Recommended: N 158 Reference: This document 160 5. References 162 5.1. Normative References 164 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 165 Requirement Levels", BCP 14, RFC 2119, 166 DOI 10.17487/RFC2119, March 1997, 167 . 169 [RFC5056] Williams, N., "On the Use of Channel Bindings to Secure 170 Channels", RFC 5056, DOI 10.17487/RFC5056, November 2007, 171 . 173 [RFC5705] Rescorla, E., "Keying Material Exporters for Transport 174 Layer Security (TLS)", RFC 5705, DOI 10.17487/RFC5705, 175 March 2010, . 177 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 178 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 179 May 2017, . 181 [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol 182 Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, 183 . 185 5.2. Informative References 187 [RFC5929] Altman, J., Williams, N., and L. Zhu, "Channel Bindings 188 for TLS", RFC 5929, DOI 10.17487/RFC5929, July 2010, 189 . 191 [RFC7627] Bhargavan, K., Ed., Delignat-Lavaud, A., Pironti, A., 192 Langley, A., and M. Ray, "Transport Layer Security (TLS) 193 Session Hash and Extended Master Secret Extension", 194 RFC 7627, DOI 10.17487/RFC7627, September 2015, 195 . 197 [TRIPLE-HANDSHAKE] 198 Bhargavan, K., Delignat-Lavaud, A., Fournet, C., Pironti, 199 A., and P. Strub, "Password Storage", March 2014, 200 . 202 Author's Address 204 Sam Whited 205 Atlanta, GA 206 United States of America 208 Email: sam@samwhited.com 209 URI: https://blog.samwhited.com/