RFC 5609: State Machines for the Protocol for Carrying Authentication for Network Access (PANA)
In plain English — editorial summary, not part of the RFC
This document defines the conceptual state machines for the Protocol for Carrying Authentication for Network Access (PANA). The state machines consist of the PANA Client (PaC) state machine and the PANA Authentication Agent (PAA) state machine. The two state machines show how PANA can interface with the Extensible Authentication Protocol (EAP) state machines. The state machines and associated models are informative only. Implementations may achieve the same results using different methods. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5609
- Published
- August 2009
- Authors
- V. Fajardo; Y. Ohba; R. Marin-Lopez
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 30
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5191Protocol for Carrying Authentication for Network Access (PANA)Updated
May 2008
- RFC 6840Clarifications and Implementation Notes for DNS Security (DNSSEC)Updated
February 2013
- RFC 7458Extensible Authentication Protocol (EAP) Attributes for Wi-Fi Integration with the Evolved Packet CoreCurrent
February 2015
- RFC 7550Issues and Recommendations with Multiple Stateful DHCPv6 OptionsObsoleted
May 2015
- RFC 2716PPP EAP TLS Authentication ProtocolObsoleted
October 1999
- RFC 5749Distribution of EAP-Based Keys for Handover and Re-AuthenticationCurrent
March 2010
- RFC 5448Improved Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement (EAP-AKA')Updated
May 2009
- RFC 5433Extensible Authentication Protocol - Generalized Pre-Shared Key (EAP-GPSK) MethodCurrent
February 2009
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?