Browse Prior Art Database

State Machines for Extensible Authentication Protocol (EAP) Peer and Authenticator (RFC4137)

IP.com Disclosure Number: IPCOM000127256D
Original Publication Date: 2005-Aug-01
Included in the Prior Art Database: 2005-Sep-08

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Vollbrecht: AUTHOR [+4]

Abstract

This document describes a set of state machines for Extensible Authentication Protocol (EAP) peer, EAP stand-alone authenticator (non-pass-through), EAP backend authenticator (for use on Authentication, Authorization, and Accounting (AAA) servers), and EAP full authenticator (for both local and pass-through). This set of state machines shows how EAP can be implemented to support deployment in either a peer/authenticator or peer/authenticator/AAA Server environment. The peer and stand-alone authenticator machines are illustrative of how the EAP protocol defined in RFC 3748 may be implemented. The backend and full/pass-through authenticators illustrate how EAP/AAA protocol support defined in RFC 3579 may be implemented. Where there are differences, RFC 3748 and RFC 3579 are authoritative.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 2% of the total text.

Network Working Group                                      J. Vollbrecht
Request for Comments: 4137              Meetinghouse Data Communications
Category: Informational                                        P. Eronen
                                                                   Nokia
                                                              N. Petroni
                                                  University of Maryland
                                                                 Y. Ohba
                                                                    TARI
                                                             August 2005


      State Machines for Extensible Authentication Protocol (EAP)
                         Peer and Authenticator

Status of This Memo

   This memo provides information for the Internet community.  It does
   not specify an Internet standard of any kind.  Distribution of this
   memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2005).

Abstract

   This document describes a set of state machines for Extensible
   Authentication Protocol (EAP) peer, EAP stand-alone authenticator
   (non-pass-through), EAP backend authenticator (for use on
   Authentication, Authorization, and Accounting (AAA) servers), and EAP
   full authenticator (for both local and pass-through).  This set of
   state machines shows how EAP can be implemented to support deployment
   in either a peer/authenticator or peer/authenticator/AAA Server
   environment.  The peer and stand-alone authenticator machines are
   illustrative of how the EAP protocol defined in RFC 3748 may be
   implemented.  The backend and full/pass-through authenticators
   illustrate how EAP/AAA protocol support defined in RFC 3579 may be
   implemented.  Where there are differences, RFC 3748 and RFC 3579 are
   authoritative.

   The state machines are based on the EAP "Switch" model.  This model
   includes events and actions for the interaction between the EAP
   Switch and EAP methods.  A brief description of the EAP "Switch"
   model is given in the Introduction section.

   The state machine and associated model are informative only.
   Implementations may achieve the same results using different methods.


Vollbrecht, et al.           Informational                      [Page 1]
RFC 4137                   EAP State Machines                A...