Extensible Authentication Protocol (EAP)
draft-arkko-emu-rfc3748bis-00

Document Type Active Internet-Draft (individual)
Authors Bernard Aboba  , Larry Blunk  , John Vollbrecht  , James Carlson  , Henrik Levkowetz  , Jari Arkko  , John Preuß Mattsson 
Last updated 2021-02-21
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
On Agenda emu at IETF-110
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           B. Aboba
Internet-Draft                                     Microsoft Corporation
Obsoletes: 3748 (if approved)                                   L. Blunk
Intended status: Standards Track                      Merit Network, Inc
Expires: August 26, 2021                                   J. Vollbrecht
                                               Vollbrecht Consulting LLC
                                                              J. Carlson
                                                   Sun Microsystems, Inc
                                                            H. Levkowetz
                                                          ipUnplugged AB
                                                          J. Arkko (Ed.)
                                                       J. Mattsson (Ed.)
                                                                Ericsson
                                                       February 22, 2021

                Extensible Authentication Protocol (EAP)
                     draft-arkko-emu-rfc3748bis-00

Abstract

   This document defines the Extensible Authentication Protocol (EAP),
   an authentication framework which supports multiple authentication
   methods.  EAP typically runs directly over data link layers such as
   Point-to-Point Protocol (PPP), IEEE 802, or 3GPP 5G without requiring
   IP.  EAP provides its own support for duplicate elimination and
   retransmission, but is reliant on lower layer ordering guarantees.
   Fragmentation is not supported within EAP itself; however, individual
   EAP methods may support this.

   This document obsoletes RFC 3748, which in turn obsoleted RFC 2284.
   This document updates some of the security considerations, terms,
   references, the IANA considerations, and few other minor updates.  A
   summary of the changes between this document and RFC 3748 is in
   Appendix A, and the changes from RFC 2284 were listed in RFC 3748.

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 http://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

Aboba, et al.            Expires August 26, 2021                [Page 1]
Internet-Draft                     EAP                     February 2021

   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 August 26, 2021.

Copyright Notice

   Copyright (c) 2021 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
   (http://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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Specification of Requirements . . . . . . . . . . . . . .   5
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   5
     1.3.  Applicability . . . . . . . . . . . . . . . . . . . . . .   7
   2.  Extensible Authentication Protocol (EAP)  . . . . . . . . . .   8
     2.1.  Support for Sequences . . . . . . . . . . . . . . . . . .  10
     2.2.  EAP Multiplexing Model  . . . . . . . . . . . . . . . . .  11
     2.3.  Pass-Through Behavior . . . . . . . . . . . . . . . . . .  13
     2.4.  Peer-to-Peer Operation  . . . . . . . . . . . . . . . . .  15
   3.  Lower Layer Behavior  . . . . . . . . . . . . . . . . . . . .  16
     3.1.  Lower Layer Requirements  . . . . . . . . . . . . . . . .  16
     3.2.  EAP Usage Within PPP  . . . . . . . . . . . . . . . . . .  19
       3.2.1.  PPP Configuration Option Format . . . . . . . . . . .  19
     3.3.  EAP Usage Within IEEE 802 . . . . . . . . . . . . . . . .  20
     3.4.  Lower Layer Indications . . . . . . . . . . . . . . . . .  20
   4.  EAP Packet Format . . . . . . . . . . . . . . . . . . . . . .  21
     4.1.  Request and Response  . . . . . . . . . . . . . . . . . .  22
     4.2.  Success and Failure . . . . . . . . . . . . . . . . . . .  24
     4.3.  Retransmission Behavior . . . . . . . . . . . . . . . . .  27
   5.  Initial EAP Request/Response Types  . . . . . . . . . . . . .  28
Show full document text