Using EAP-TLS with TLS 1.3
draft-ietf-emu-eap-tls13-00

Document Type Active Internet-Draft (emu WG)
Last updated 2018-05-30
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                        J. Mattsson
Internet-Draft                                                  M. Sethi
Updates: 5216 (if approved)                                     Ericsson
Intended status: Standards Track                            May 29, 2018
Expires: November 30, 2018

                       Using EAP-TLS with TLS 1.3
                      draft-ietf-emu-eap-tls13-00

Abstract

   This document specifies the use of EAP-TLS with TLS 1.3 while
   remaining backwards compatible with existing implementations of EAP-
   TLS.  TLS 1.3 provides significantly improved security, privacy, and
   reduced latency when compared to earlier versions of TLS.  This
   document updates RFC 5216.

Status of This Memo

   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 November 30, 2018.

Copyright Notice

   Copyright (c) 2018 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 Simplified BSD License text as described in Section 4.e of

Mattsson & Sethi        Expires November 30, 2018               [Page 1]
Internet-Draft            EAP-TLS with TLS 1.3                  May 2018

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements and Terminology  . . . . . . . . . . . . . .   3
   2.  Protocol Overview . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Overview of the EAP-TLS Conversation  . . . . . . . . . .   3
       2.1.1.  Base Case . . . . . . . . . . . . . . . . . . . . . .   3
       2.1.2.  Resumption  . . . . . . . . . . . . . . . . . . . . .   6
       2.1.3.  Termination . . . . . . . . . . . . . . . . . . . . .   7
       2.1.4.  Privacy . . . . . . . . . . . . . . . . . . . . . . .  10
       2.1.5.  Fragmentation . . . . . . . . . . . . . . . . . . . .  12
     2.2.  Identity Verification . . . . . . . . . . . . . . . . . .  12
     2.3.  Key Hierarchy . . . . . . . . . . . . . . . . . . . . . .  12
     2.4.  Parameter Negotiation and Compliance Requirements . . . .  13
   3.  Detailed Description of the EAP-TLS Protocol  . . . . . . . .  13
   4.  IANA considerations . . . . . . . . . . . . . . . . . . . . .  13
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
     5.1.  Security Claims . . . . . . . . . . . . . . . . . . . . .  14
     5.2.  Peer and Server Identities  . . . . . . . . . . . . . . .  14
     5.3.  Certificate Validation  . . . . . . . . . . . . . . . . .  14
     5.4.  Certificate Revocation  . . . . . . . . . . . . . . . . .  14
     5.5.  Packet Modification Attacks . . . . . . . . . . . . . . .  15
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  15
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .  15
     6.2.  Informative references  . . . . . . . . . . . . . . . . .  16
   Appendix A.  Updated references . . . . . . . . . . . . . . . . .  17
   Appendix B.  Acknowledgments  . . . . . . . . . . . . . . . . . .  18
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  18

1.  Introduction

   The Extensible Authentication Protocol (EAP), defined in [RFC3748],
   provides a standard mechanism for support of multiple authentication
   methods.  EAP-Transport Layer Security (EAP-TLS) [RFC5216] specifies
   an EAP authentication method with certificate-based mutual
   authentication and key derivation utilizing the TLS handshake
   protocol for cryptographic algorithms and protocol version
   negotiation, mutual authentication, and establishment of shared
   secret keying material.  EAP-TLS is widely supported for
   authentication in IEEE 802.11 [IEEE-802.11] networks (Wi-Fi) using
   IEEE 802.1X [IEEE-802.1X] and it's the default mechanism for
   certificate based authentication in MulteFire [MulteFire] and 3GPP 5G
   [TS.33.501] networks.  EAP-TLS [RFC5216] references TLS 1.0 [RFC2246]
Show full document text