Browse Prior Art Database

Mobile IP Network Access Identifier Extension for IPv4 (RFC2794)

IP.com Disclosure Number: IPCOM000003393D
Original Publication Date: 2000-Mar-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 7 page(s) / 16K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

P. Calhoun: AUTHOR [+2]

Abstract

Since the NAI is typically used to uniquely identify the mobile node, the mobile node's home address is not always necessary to provide that function. Thus, it is possible for a mobile node to authenticate itself, and be authorized for connection to the foreign domain, without even having a home address. A message containing the Mobile Node NAI extension MAY set the Home Address field to zero (0) in the Registration Request, to request that a home address be assigned.

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 19% of the total text.

Network Working Group P. Calhoun

Request for Comments: 2794 Sun Microsystems Laboratories

Updates: 2290 C. Perkins

Category: Standards Track Nokia Research Center

March 2000

Mobile IP Network Access Identifier Extension for IPv4

Status of this Memo

This document specifies an Internet standards track protocol for the

Internet community, and requests discussion and suggestions for

improvements. Please refer to the current edition of the "Internet

Official Protocol Standards" (STD 1) for the standardization state

and status of this protocol. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (2000). All Rights Reserved.

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.

1. Introduction

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) [1]. This document

specifies the Mobile Node NAI extension to the Mobile IP Registration

Request [7] message from the mobile node.

Since the NAI is typically used to uniquely identify the mobile node,

the mobile node's home address is not always necessary to provide

that function. Thus, it is possible for a mobile node to

authenticate itself, and be authorized for connection to the foreign

domain, without even having a home address. A message containing the

Mobile Node NAI extension MAY set the Home Address field to zero (0)

in the Registration Request, to request that a home address be

assigned.

The "Mobile-IPv4 Configuration" option to IPCP has been specified in

RFC 2290 [8] for proper interaction between a mobile node and a peer,

through which the mobile node connects to the network using PPP.

According to that specification the Mobile Node's Home Address field

of the option MUST not be zero. However, in the context of this memo

which allows a mobile node to be identified ...