RFC 3846: Mobile IPv4 Extension for Carrying Network Access Identifiers
In plain English — editorial summary, not part of the RFC
When a mobile node moves between two foreign networks, it has to be re-authenticated. If the home network has both multiple Authentication Authorization and Accounting (AAA) servers and Home Agents (HAs) in use, the Home AAA server may not have sufficient information to process the re-authentication correctly (i.e., to ensure that the same HA continues to be used). This document defines a Mobile IP extension that carries identities for the Home AAA and HA servers in the form of Network Access Identifiers (NAIs). The extension allows a Home Agent to pass its identity (and that of the Home AAA server) to the mobile node, which can then pass it on to the local AAA server when changing its point of attachment. This extension may also be used in other situations requiring communication of a NAI between Mobile IP nodes. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3846
- Published
- June 2004
- Authors
- F. Johansson; T. Johansson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2794Mobile IP Network Access Identifier Extension for IPv4Current
March 2000
- RFC 4282The Network Access IdentifierObsoleted
December 2005
- RFC 3879Deprecating Site Local AddressesCurrent
September 2004
- RFC 3776Using IPsec to Protect Mobile IPv6 Signaling Between Mobile Nodes and Home AgentsUpdated
June 2004
- RFC 3775Mobility Support in IPv6Obsoleted
June 2004
- RFC 3678Socket Interface Extensions for Multicast Source FiltersCurrent
January 2004
- RFC 4064Experimental Message, Extensions, and Error Codes for Mobile IPv4Current
May 2005
- RFC 4076Renumbering Requirements for Stateless Dynamic Host Configuration Protocol for IPv6 (DHCPv6)Current
May 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?