NAI Resolution for Wireless Networks
draft-ietf-mobileip-nai-wn-00

Document Type Expired Internet-Draft (mobileip WG)
Last updated 1999-03-03
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-mobileip-nai-wn-00.txt

Abstract

RFC 2468 [1] defines the need of a standardized format for identifying ISP subscribers for dial-up roaming operations. It introduced the Network Access Identifier (NAI) to fulfill this need. The NAI is provided by the mobile node to the dialed ISP during PPP authentication. The ability to resolve an NAI for second and third generation cellular mobile nodes allow traditional cellular service providers to evolve their home cellular networks to provide cellular services, IP packet data services and so on with a single subscription using NAIs. Additionally, this allows cellular provider to evolve their networks to be IP based. Second and third generation cellular mobile nodes must perform a registration and authentication process with their wireless service provider before the mobile node user may initiate other operations (See [1] for examples). These mobile nodes do not support the programming of an NAI nor does the cellular registration message support the transfer of an NAI to the wireless access network. For example, North American cellular networks (e.g. AMPS, TDMA, CDMA) service mobile nodes that register with a Mobile Identification Number (MIN). The MIN is then associated with a cellular subscriber. For the same reasons stated in [1], it would be convenient if an option was available to provide the wireless subscriber identification in the form of an NAI during the wireless registration and authentication process. This draft proposes a solution to resolve NAIs from traditional mobile node identifiers.

Authors

Lachu Aravamudhan (lachu@nortelnetworks.com)
Mark O'Brien (markob@nortelnetworks.com)
Basavaraj Patil (basavaraj.patil@nokia.com)

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