Skip to main content

Mobile IPv4 NAI-based Home Address Assignment
draft-paulkandasamy-mobileip-nai-based-home-addres-02

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Naveen PaulKandasamy , Kent Leung
Last updated 2007-03-08
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

AAA servers are in use within the Internet today to provide authentication and authorization services for dial-up computers. Such services are likely to be equally valuable for mobile nodes using Mobile IP when the nodes are attempting to connect to foreign domains with AAA servers. AAA servers today identify clients by using the Network Access Identifier (NAI). Our proposal defines a way for the mobile node to identify itself, by including the NAI along with the Mobile IP Registration Request. This memo also updates RFC 2290 which specifies the Mobile-IPv4 Configuration option for IPCP, by allowing the Mobile Node's Home Address field of this option to be zero and specifying a comprehensive procedure for achieving a NAI-based home address assignment and more particularly, the Home Agent and Mobile Node behaviors including the error recovery mechanisms for various scenarios related to NAI-based home address assignment.

Authors

Naveen PaulKandasamy
Kent Leung

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)