idnits 2.17.1 draft-dekok-emu-eap-session-id-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 abstract seems to contain references ([RFC5247], [AKAP]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. -- The abstract seems to indicate that this document updates RFC5247, but the header doesn't have an 'Updates:' line to match this. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (28 January 2019) is 1915 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) ** Obsolete normative reference: RFC 5296 (Obsoleted by RFC 6696) -- Possible downref: Non-RFC (?) normative reference: ref. 'FILS' -- Unexpected draft version: The latest known version of draft-arkko-eap-rfc5448bis is -01, but you're referring to -04. Summary: 2 errors (**), 0 flaws (~~), 2 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group DeKok, Alan 3 INTERNET-DRAFT FreeRADIUS 4 Updates: 5247 5 Category: Standards Track 6 7 28 January 2019 9 EAP Session-Id Derivation 10 draft-dekok-emu-eap-session-id-00.txt 12 Abstract 14 EAP Session-Id derivation has not been defined for EAP-SIM, EAP-AKA, 15 and EAP-AKA' when using the fast re-authentication exchange instead 16 of full authentication. This document updates [RFC5247] to define 17 those derivations for EAP-SIM, and EAP-AKA. [AKAP] defines the 18 Session-ID for EAP-AKA', so the definition for EAP-AKA' is not 19 included here. [RFC5247] also does not define Session-Id derivation 20 for PEAP. A definition is given here which follows the definition 21 for other TLS-based EAP methods. 23 Status of this Memo 25 This Internet-Draft is submitted to IETF in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF), its areas, and its working groups. Note that 30 other groups may also distribute working documents as Internet- 31 Drafts. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 The list of current Internet-Drafts can be accessed at 39 http://www.ietf.org/ietf/1id-abstracts.txt. 41 The list of Internet-Draft Shadow Directories can be accessed at 42 http://www.ietf.org/shadow.html. 44 This Internet-Draft will expire on July 22, 2019. 46 Copyright Notice 48 Copyright (c) 2019 IETF Trust and the persons identified as the 49 document authors. All rights reserved. 51 This document is subject to BCP 78 and the IETF Trust's Legal 52 Provisions Relating to IETF Documents 53 (http://trustee.ietf.org/license-info/) in effect on the date of 54 publication of this document. Please review these documents 55 carefully, as they describe your rights and restrictions with respect 56 to this document. Code Components extracted from this document must 57 include Simplified BSD License text as described in Section 4.e of 58 the Trust Legal Provisions and are provided without warranty as 59 described in the Simplified BSD License. 61 Table of Contents 63 1. Introduction ............................................. 4 64 1.1. Requirements Language ............................... 4 65 2. Updates to RFC 5247 Appendix A ........................... 5 66 2.1. EAP-AKA ............................................. 5 67 2.2. EAP-SIM ............................................. 5 68 2.3. Rationale ........................................... 6 69 2.3.1. Session-Id for PEAP ............................ 7 70 3. Security Considerations .................................. 7 71 4. IANA Considerations ...................................... 7 72 5. References ............................................... 7 73 5.1. Normative References ................................ 7 74 5.2. Informative References .............................. 8 76 1. Introduction 78 EAP [RFC3748] Session-Id derivation has not been defined for EAP-SIM, 79 EAP-AKA, and EAP-AKA' when using the fast re-authentication exchange 80 instead of full authentication. [RFC5247] defines the Session-Id for 81 these EAP methods, but that derivation is only applicable for the 82 full authentication case. 84 The IEEE is defining FILS authentication [FILS], which needs the EAP 85 Session-Id for in order for the EAP Re-authentication Protocol (ERP) 86 [RFC5296] to work, it would be important to get this resolved with a 87 clearly defined and agreed derivation rules to allow fast re- 88 authentication cases to be used to derive ERP key hierarchy. 90 Further, [RFC5247] did not define Session-Id for PEAP. We correct 91 that deficiency here. 93 1.1. Requirements Language 95 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 96 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 97 "OPTIONAL" in this document are to be interpreted as described in BCP 98 14 [RFC2119] [RFC8174] when, and only when, they appear in all 99 capitals, as shown here. 101 2. Updates to RFC 5247 Appendix A 103 This section updates [RFC5247] Appendix A to define Session-Id for 104 fast re-authentication exchange for EAP-AKA and EAP-SIM. It further 105 defines Session-ID derivation for PEAP. 107 2.1. EAP-AKA 109 For EAP-AKA, [RFC5247] Appendix A says: 111 EAP-AKA 113 EAP-AKA is defined in [RFC4187]. The EAP-AKA Session-Id is the 114 concatenation of the EAP Type Code (0x17) with the contents of the 115 RAND field from the AT_RAND attribute, followed by the contents of 116 the AUTN field in the AT_AUTN attribute: 118 Session-Id = 0x17 || RAND || AUTN 120 It should say: 122 EAP-AKA 124 EAP-AKA is defined in [RFC4187]. When using full authentication, 125 the EAP-AKA Session-Id is the concatenation of the EAP Type Code 126 (0x17) with the contents of the RAND field from the AT_RAND 127 attribute, followed by the contents of the AUTN field in the 128 AT_AUTN attribute: 130 Session-Id = 0x17 || RAND || AUTN 132 When using fast re-authentication, the EAP-AKA Session-Id is the 133 concatenation of the EAP Type Code (0x17) with the contents of the 134 NONCE_S field from the AT_NONCE_S attribute, followed by the 135 contents of the MAC field from the AT_MAC attribute from EAP- 136 Request/AKA-Reauthentication: 138 Session-Id = 0x17 || NONCE_S || MAC 140 2.2. EAP-SIM 142 Similarly for EAP-SIM, it says: 144 EAP-SIM 146 EAP-SIM is defined in [RFC4186]. The EAP-SIM Session-Id is the 147 concatenation of the EAP Type Code (0x12) with the contents of the 148 RAND field from the AT_RAND attribute, followed by the contents of 149 the NONCE_MT field in the AT_NONCE_MT attribute: 151 Session-Id = 0x12 || RAND || NONCE_MT 153 The Peer-Id is the contents of the Identity field from the 154 AT_IDENTITY attribute, using only the Actual Identity Length 155 octets from the beginning, however. Note that the contents are 156 used as they are transmitted, regardless of whether the 157 transmitted identity was a permanent, pseudonym, or fast EAP re- 158 authentication identity. The Server-Id is the null string (zero 159 length). 161 It should say: 163 EAP-SIM 165 EAP-SIM is defined in [RFC4186]. The EAP-SIM Session-Id is the 166 concatenation of the EAP Type Code (0x12) with the contents of the 167 RAND field from the AT_RAND attribute, followed by the contents of 168 the NONCE_MT field in the AT_NONCE_MT attribute: 170 Session-Id = 0x12 || RAND || NONCE_MT 172 The Peer-Id is the contents of the Identity field from the 173 AT_IDENTITY attribute, using only the Actual Identity Length 174 octets from the beginning, however. Note that the contents are 175 used as they are transmitted, regardless of whether the 176 transmitted identity was a permanent, pseudonym, or fast EAP re- 177 authentication identity. The Server-Id is the null string (zero 178 length). 180 When using fast re-authentication, the EAP-AKA Session-Id is the 181 concatenation of the EAP Type Code (0x12) with the contents of the 182 NONCE_S field from the AT_NONCE_S attribute, followed by the 183 contents of the MAC field from the AT_MAC attribute from EAP- 184 Request/AKA-Reauthentication: 186 Session-Id = 0x12 || NONCE_S || MAC 188 2.3. Rationale 190 [RFC5247] was supposed to define exported parameters for existing EAP 191 methods in Appendix A. The way Session-Id was defined for EAP-AKA and 192 EAP-SIM works only for the full authentication case, i.e., it cannot 193 be used when the optional fast re-authentication case is used since 194 the used parameters (RAND, AUTN, NONCE_MT) are not used in the fast 195 re-authentication case. Based on [RFC4187] Section 5.2, and similar 196 text in [RFC4186], NONCE_S corresponds to RAND and MAC in EAP- 197 Request/AKA-Reauthentication corresponds to AUTN. That would seem to 198 imply that the Session-Id could be defined using NONCE_S and MAC 199 instead of RAND and AUTN/NONCE_MT. 201 2.3.1. Session-Id for PEAP 203 [RFC5247] id not define Session-Id definition for Microsoft's 204 Protected EAP (PEAP). Similar to the defintion in [RFC5216] Section 205 2.3, we define it as: 207 Session-Id = 0x19 || client.random || server.random). 208 This definition is already in wide-spread use in multiple PEAP 209 implemementations. 211 3. Security Considerations 213 This specification defines EAP Session-Ids for fast re-authentication 214 with EAP-SIM and EAP-AKA. It therefore enables fast re-authenticaton 215 for those protocols. 217 4. IANA Considerations 219 There are no actions for IANA. RFC EDITOR: This section may be 220 removed before publication. 222 5. References 224 5.1. Normative References 226 [RFC2119] 227 Bradner, S., "Key words for use in RFCs to Indicate Requirement 228 Levels", RFC 2119, March, 1997, . 231 [RFC3748] 232 Aboba, B., Blunk, L., Vollbrecht, J., Carlson, J., and H. 233 Levkowetz, "Extensible Authentication Protocol (EAP)", RFC 3748, 234 June 2004. 236 [RFC5216] 237 Simon, D., Aboba, B., and R. Hurst, "The EAP-TLS Authentication 239 Protocol", 241 [RFC5247] 242 Aboba, B., Simon, D., and P. Eronen, "Extensible Authentication 243 Protocol (EAP) Key Management Framework", RFC 5247, August 2008, 245 [RFC5296] 246 Narayanan, V. and L. Dondeti, "EAP Extensions for EAP Re- 247 authentication Protocol (ERP)", RFC 5296, August 2008. 249 [RFC8174] 250 Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key 251 Words", RFC 8174, May 2017, . 254 [FILS] 255 TBD 257 5.2. Informative References 259 [RFC4186] 260 Haverinen, H. (Ed), Salowey, J., "Extensible Authentication 261 Protocol Method for Global System for Mobile Communications (GSM) 262 Subscriber Identity Modules (EAP-SIM)", RFC 4186, January 2006. 264 [RFC4187] 265 Arkko, J., Haverinen, H., "Extensible Authentication Protocol 266 Method for 3rd Generation Authentication and Key Agreement (EAP- 267 AKA)", RFC 4187, January 2006. 269 [AKAP] 270 Arkko, J., et al, "Improved Extensible Authentication Protocol 271 Method for 3rd Generation Authentication and Key Agreement (EAP- 272 AKA')", draft-arkko-eap-rfc5448bis-04.txt, January 2019. 274 Acknowledgments 276 The issue corrected in this specification was first reported by Jouni 277 Malinen in a technical errata at https://www.rfc- 278 editor.org/errata_search.php?rfc=5247 280 The text in this document follows his suggestions. 281 Authors' Addresses 283 Alan DeKok 284 The FreeRADIUS Server Project 286 Email: aland@freeradius.org