RFC 4058: Protocol for Carrying Authentication for Network Access (PANA) Requirements
In plain English — editorial summary, not part of the RFC
It is expected that future IP devices will have a variety of access technologies to gain network connectivity. Currently there are access-specific mechanisms for providing client information to the network for authentication and authorization purposes. In addition to being limited to specific access media (e.g., 802.1X for IEEE 802 links), some of these protocols are limited to specific network topologies (e.g., PPP for point-to-point links). The goal of this document is to identify the requirements for a link-layer agnostic protocol that allows a host and a network to authenticate each other for network access. This protocol will run between a client's device and an agent in the network where the agent might be a client of the AAA infrastructure. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4058
- Published
- May 2005
- Authors
- A. Yegin; Y. Ohba; R. Penno; G. Tsirtsis; C. Wang
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4064Experimental Message, Extensions, and Error Codes for Mobile IPv4Current
May 2005
- RFC 4068Fast Handovers for Mobile IPv6Obsoleted
July 2005
- RFC 4075Simple Network Time Protocol (SNTP) Configuration Option for DHCPv6Current
May 2005
- RFC 4076Renumbering Requirements for Stateless Dynamic Host Configuration Protocol for IPv6 (DHCPv6)Current
May 2005
- RFC 4039Rapid Commit Option for the Dynamic Host Configuration Protocol version 4 (DHCPv4)Current
March 2005
- RFC 4035Protocol Modifications for the DNS Security ExtensionsUpdated
March 2005
- RFC 4034Resource Records for the DNS Security ExtensionsUpdated
March 2005
- RFC 4033DNS Security Introduction and RequirementsUpdated
March 2005
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?