RFC 4058: Protocol for Carrying Authentication for Network Access (PANA) Requirements

It is expected that future IP devices will have a variety of access technologies to gain network connectivity. Currently there are access-specific mechanisms…

Read RFC 4058 on the RFC Editor

Outgoing relationships (15 related RFCs)

Informative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Informative reference — RFC 3315: Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
Informative reference — RFC 2131: Dynamic Host Configuration Protocol
Informative reference — RFC 1661: The Point-to-Point Protocol (PPP)
Informative reference — RFC 3748: Extensible Authentication Protocol (EAP)
Informative reference — RFC 826: An Ethernet Address Resolution Protocol: Or Converting Network Protocol Addresses to 48.bit Ethernet Address for Transmission on Ethernet Hardware
Informative reference — RFC 3775: Mobility Support in IPv6
Informative reference — RFC 2461: Neighbor Discovery for IP Version 6 (IPv6)
Informative reference — RFC 3344: IP Mobility Support for IPv4
Informative reference — RFC 1256: ICMP Router Discovery Messages
Informative reference — RFC 3041: Privacy Extensions for Stateless Address Autoconfiguration in IPv6
Informative reference — RFC 2794: Mobile IP Network Access Identifier Extension for IPv4
Informative reference — RFC 2716: PPP EAP TLS Authentication Protocol
Informative reference — RFC 3012: Mobile IPv4 Challenge/Response Extensions
Informative reference — RFC 4016: Protocol for Carrying Authentication and Network Access (PANA) Threat Analysis and Security Requirements

Incoming relationships (2 related RFCs)

Normatively referenced by — RFC 5193: Protocol for Carrying Authentication for Network Access (PANA) Framework
Informatively referenced by — RFC 4739: Multiple Authentication Exchanges in the Internet Key Exchange (IKEv2) Protocol