RFC 5191: Protocol for Carrying Authentication for Network Access (PANA)
In plain English — editorial summary, not part of the RFC
This document defines the Protocol for Carrying Authentication for Network Access (PANA), a network-layer transport for Extensible Authentication Protocol (EAP) to enable network access authentication between clients and access networks. In EAP terms, PANA is a UDP-based EAP lower layer that runs between the EAP peer and the EAP authenticator. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5191
- Published
- May 2008
- Authors
- D. Forsberg; Y. Ohba; B. Patil; H. Tschofenig; A. Yegin
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 46
- Also known as
- —
- Updated by:
- RFC 5872
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5609State Machines for the Protocol for Carrying Authentication for Network Access (PANA)Current
August 2009
- 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 2716PPP EAP TLS Authentication ProtocolObsoleted
October 1999
- RFC 5281Extensible Authentication Protocol Tunneled Transport Layer Security Authenticated Protocol Version 0 (EAP-TTLSv0)Updated
August 2008
- RFC 5433Extensible Authentication Protocol - Generalized Pre-Shared Key (EAP-GPSK) MethodCurrent
February 2009
- RFC 5448Improved Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement (EAP-AKA')Updated
May 2009
- RFC 4851The Flexible Authentication via Secure Tunneling Extensible Authentication Protocol Method (EAP-FAST)Updated
May 2007
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?