draft-ietf-mip4-aaa-nai-00.txt   draft-ietf-mip4-aaa-nai-01.txt 
Mobile IP Working Group F. Johansson Mobile IP Working Group F. Johansson
Internet-Draft ipUnplugged Internet-Draft ipUnplugged
Expires: March 19, 2004 T. Johansson Expires: May 31, 2004 T. Johansson
Bytemobile Bytemobile
September 19, 2003 December 1, 2003
Mobile IPv4 Extension for AAA Network Access Identifiers Mobile IPv4 Extension for carrying Network Access Identifiers
draft-ietf-mip4-aaa-nai-00.txt <draft-ietf-mip4-aaa-nai-01.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that other
other groups may also distribute working documents as groups may also distribute working documents as Internet-Drafts.
Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress".
The list of current Internet-Drafts can be accessed at http:// The list of current Internet-Drafts can be accessed at http://
www.ietf.org/ietf/1id-abstracts.txt. www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html
This Internet-Draft will expire on March 19, 2004. This Internet-Draft will expire on May 31, 2004.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract Abstract
When a mobile node moves between two foreign networks it has to be When a mobile node moves between two foreign networks it has to be
reauthenticated. If the home network has multiple Authentication re-authenticated. If for instance the home network has multiple
Authorization and Accounting (AAA) servers the reauthentication Authentication Authorization and Accounting (AAA) servers the
request may not be received by the same Home AAA server as previous re-authentication request may not be received by the same Home AAA
authentication requests. In order for the new Home AAA server to be server as previous authentication requests. In order for the new
able to forward the request to the correct Home Agent it has to know Home AAA server to be able to forward the request to the correct Home
the identity of the Home Agent. This document defines a Mobile IP Agent it has to know the identity of the Home Agent. This document
extension that enables the HA to pass its identity to the mobile node defines a Mobile IP extension that carries identities in the form of
which can then pass it on to the new AAA server when changing point Network Access Identifiers (NAIs), which may be used by an HA to pass
of attachment. its identity to the mobile node which can then pass it on to the new
AAA server when changing point of attachment. This extension may also
be used in other situations requiring communication of a NAI between
Mobile IP nodes.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements terminology . . . . . . . . . . . . . . . . . . . 3 2. Requirements terminology . . . . . . . . . . . . . . . . . . . 3
3. AAA NAI Extension . . . . . . . . . . . . . . . . . . . . . . 4 3. NAI Carrying Extension . . . . . . . . . . . . . . . . . . . . 4
3.1 Processing of the AAA NAI Extension . . . . . . . . . . 5 3.1 Processing of the NAI Carrying Extension . . . . . . . . 5
4. HA Identity subtype . . . . . . . . . . . . . . . . . . . . . 5 4. HA Identity subtype . . . . . . . . . . . . . . . . . . . . . 5
5. AAAH Identity subtype . . . . . . . . . . . . . . . . . . . . 6 5. AAAH Identity subtype . . . . . . . . . . . . . . . . . . . . 6
6. Security Considerations . . . . . . . . . . . . . . . . . . . 6 6. Security Considerations . . . . . . . . . . . . . . . . . . . 6
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7
skipping to change at page 3, line 20 skipping to change at page 3, line 20
authentication will be handled by one of the AAA servers in the home authentication will be handled by one of the AAA servers in the home
domain. At a later point, when the mobile node moves to another domain. At a later point, when the mobile node moves to another
visited domain it again has to be authenticated. However, due to the visited domain it again has to be authenticated. However, due to the
redundancy offered by the AAA protocol, it can not be guaranteed that redundancy offered by the AAA protocol, it can not be guaranteed that
the authentication will be handled by the same AAAH server as the the authentication will be handled by the same AAAH server as the
previous one which can result in the new AAAH not knowing which HA previous one which can result in the new AAAH not knowing which HA
the session was assigned to. This document defines a Mobile IP the session was assigned to. This document defines a Mobile IP
extension which can be used to distribute the information needed to extension which can be used to distribute the information needed to
resolve this. resolve this.
To solve this the home agent MUST include the NAI of the AAAH server
in the registration reply message, which the mobile node then MUST
include in every subsequent registration request sent to a foreign
agent when changing point of attachment.
Furthermore, the only information that is normally available about Furthermore, the only information that is normally available about
the home agent in the registration request is the IP address as the home agent in the registration request is the IP address as
defined in RFC 3344 [1]. This is unfortunately not enough, since the defined in RFC 3344 [1]. This is unfortunately not enough, since the
AAA infrastructure needs to know the FQDN identity of the home agent AAA infrastructure needs to know the FQDN identity of the home agent
to be able to correctly handle the assignment of home agent. A to be able to correctly handle the assignment of home agent. A
reverse DNS lookup would only disclose the identity of the Mobile IP reverse DNS lookup would only disclose the identity of the Mobile IP
interface for that HA IP address, which may or may not have a interface for that HA IP address, which may or may not have a
one-to-one correspondence with the home agent FQDN identity. This is one-to-one correspondence with the home agent FQDN identity. This is
the reason why the HA also includes its own identity in the the reason why the HA also includes its own identity in the
registration reply. It can then be included by the mobile node in registration reply. It can then be included by the mobile node in the
the coming registration requests when changing point of attachment. coming registration requests when changing point of attachment.
2. Requirements terminology 2. Requirements terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [4]. document are to be interpreted as described in RFC 2119 [4].
The Mobile IP related terminology described in RFC 3344 [1] is used The Mobile IP related terminology described in RFC 3344 [1] is used
in this document. In addition, the following terms are used: in this document. In addition, the following terms are used:
skipping to change at page 4, line 11 skipping to change at page 4, line 5
FQDN FQDN
Fully Qualified Domain Name. Fully Qualified Domain Name.
Identity Identity
The identity of a node is equal to its FQDN. The identity of a node is equal to its FQDN.
NAI NAI
Network Access Identifier [2]. Network Access Identifier [2].
3. AAA NAI Extension 3. NAI Carrying Extension
This section defines the AAA NAI Extension which may be carried in This section defines the NAI Carrying Extension which may be used in
Mobile IP Registration Request and Reply messages [1]. The extension Mobile IP Registration Request and Reply messages, and also in Mobile
may be used by any node that wants to send identity information in IP Agent Advertisements [1]. The extension may be used by any node
the form of a NAI [3]. This document defines subtype numbers which that wants to send identity information in the form of a NAI [3].
identify the NAI as a HA identity and a Home AAA identity, This document also defines some subtype numbers which identify the
respectively. specific type of NAI carried, in Section 4 and Section 5. It is
expected that other types of NAI will be defined by other documents
in the future.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Sub-Type | NAI ... | Type | Length | Sub-Type | NAI ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type Type
(Type to be assigned by IANA) (skippable) [1] (Type to be assigned by IANA) (skippable) [1]
Length 8-bit unsigned integer. Length of the extension, in octets, Length 8-bit unsigned integer. Length of the extension, in octets,
excluding the extension Type and the extension Length excluding the extension Type and the extension Length
fields. This field MUST be set to 1 plus the total length fields. This field MUST be set to 1 plus the total length
of the NAI field. of the NAI field.
Sub-Type This field describes the type of the entity which owns the Sub-Type This field describes the particular type NAI which is
NAI. The following subtypes are defined: carried in the NAI field.
1 HA Identity NAI (Section 4)
2 AAAH Identity NAI (Section 5)
NAI Contains the NAI [2] in a string format. NAI Contains the NAI [2] in a string format.
3.1 Processing of the AAA NAI Extension 3.1 Processing of the NAI Carrying Extension
When a mobile node or home agent adds a AAA NAI extension to a When a mobile node or home agent adds a NAI Carrying Extension to a
registration message, the extension MUST appear prior to any registration message, the extension MUST appear prior to any
authentication extensions. authentication extensions.
In the event the foreign agent adds an AAA NAI extension to a In the event the foreign agent adds a NAI Carrying Extension to a
registration message, the extension MUST appear prior to any registration message, the extension MUST appear prior to any
authentication extensions added by the FA. authentication extensions added by the FA.
If an HA has appended an AAA NAI extension to a Registration Reply to If an HA has appended a NAI Carrying Extension to a Registration
an MN, and does not receive the NAI extension in subsequent Reply to an MN, and does not receive the NAI extension in subsequent
Registration Request messages from the MN, the HA can assume that the Registration Request messages from the MN, the HA can assume that the
MN does not understand this NAI extension. In this case, the HA MN does not understand this NAI extension. In this case, the HA
SHOULD NOT append this NAI extension to further Registration Reply SHOULD NOT append this NAI extension to further Registration Reply
messages to the MN. messages to the MN.
4. HA Identity subtype 4. HA Identity subtype
The HA identity uses subtype 1 of the AAA NAI Extension. It contains The HA identity uses subtype 1 of the NAI Carrying Extension. It
the NAI of the HA in the form hostname@realm. Together the hostname contains the NAI of the HA in the form hostname@realm. Together the
and realm forms the complete FQDN (hostname.realm) of the HA. hostname and realm forms the complete FQDN (hostname.realm) of the
HA.
The Home Agent MUST provide this in the first Registration Reply sent A Home Agent using this extension MUST provide it in the first
to the Mobile Node destined through the AAA infrastructure. The Registration Reply sent to a Mobile Node which is not currently
extension only need to be included in subsequent Registration Replies registered. The extension only need to be included in subsequent
if the same extension is included in Registration Requests received Registration Replies if the same extension is included in
from the same Mobile Node. Registration Requests received from the same Mobile Node.
A mobile node that recieves this extension in a registration reply A mobile node using this extension MUST, if it receives in a
message MUST provide it in every registration request when registration reply message, provide it in every subsequent
re-authentication is needed. If the mobile node requests a specific registration request when re-authentication is needed. If the mobile
home agent and it has the information available it MUST provide this node requests a specific home agent and it has the information
extension in its initial registration request. available it MUST provide this extension in its initial registration
request.
A foreign agent which receives the Home Agent NAI by this extension A foreign agent which receives the Home Agent NAI by this extension
in a registration request SHOULD include the Home Agent NAI when in a registration request SHOULD include the Home Agent NAI when
requesting Mobile Node authentication through the AAA infrastructure requesting Mobile Node authentication through the AAA infrastructure
if the AAA protocol used can carry the information. if the AAA protocol used can carry the information.
5. AAAH Identity subtype 5. AAAH Identity subtype
The AAAH identity uses subtype 2 of the AAA NAI Extension. It The AAAH identity uses subtype 2 of the NAI Carrying Extension. It
contains the NAI of the home AAA server in the form hostname@realm. contains the NAI of the home AAA server in the form hostname@realm.
Together the hostname and realm forms the complete FQDN Together the hostname and realm forms the complete FQDN
(hostname.realm) of the home AAA server. (hostname.realm) of the home AAA server.
If there exists several AAA servers in the Home Network, the Home If there exists several AAA servers in the Home Network, a Home Agent
Agent MUST provide this in the first Registration Reply sent to the providing AAAH selection support according to this document MUST
provide the AAAH identity in the first Registration Reply sent to the
Mobile Node. The extension only need to be included in subsequent Mobile Node. The extension only need to be included in subsequent
Registration Replies if the same extension is included in Registration Replies if the same extension is included in
Registration Requests received from the same Mobile Node. Registration Requests received from the same Mobile Node.
A mobile node MUST always save the latest AAAH Identity received in a A mobile node MUST always save the latest AAAH Identity received in a
registration reply message and MUST provide the AAAH Identity in registration reply message and MUST provide the AAAH Identity in
every registration request sent when re-authenticating. every registration request sent when re-authenticating.
A foreign agent which receives the AAAH NAI by this extension in a A foreign agent which receives the AAAH NAI by this extension in a
registration request SHOULD include the AAAH NAI provided when registration request SHOULD include the AAAH NAI provided when
requesting Mobile Node authentication through the AAA infrastructure requesting Mobile Node authentication through the AAA infrastructure
if the AAA protocol used can carry the information. if the AAA protocol used can carry the information.
6. Security Considerations 6. Security Considerations
This specification introduces new Mobile IP extensions that are used This specification introduces new Mobile IP extensions that are used
to carry mobility agent and AAA server identities, in the form of to carry mobility agent and AAA server identities, in the form of
Network Access Identifiers. It is assumed that the Mobile IP Network Access Identifiers. The Mobile IP messages that carry this
messages that would carry these extensions would be authenticated in extension MUST be authenticated as described in [3], unless other
the manner that is described in [4], or any follow-on authentication authentication methods have been agreed upon. Therefore, this
mechanisms. Therefore, this specification does not lessen the specification does not lessen the security of Mobile IP messages.
security of Mobile IP messages.
It should be noted that the identities sent in the extensions It should be noted that the identities sent in the extensions
specified herein MAY be sent in the clear over the network. However, specified herein MAY be sent in the clear over the network. However,
the authors do not envision that this information would create any the authors do not envision that this information would create any
security issues. security issues.
7. IANA Considerations 7. IANA Considerations
This document defines one new mobile IP extension, and one new Mobile This document defines one new mobile IP extension, and one new Mobile
IP extension sub-type numbering space to be managed by IANA. IP extension sub-type numbering space to be managed by IANA.
Section 3 defines a new Mobile IP extension, the Mobile IP AAA NAI Section 3 defines a new Mobile IP extension, the Mobile IP NAI
Extension. The type number for this extension is [TBD, assigned by Carrying Extension. The type number for this extension is [TBD,
IANA]. This extension introduces a new sub-type numbering space assigned by IANA]. This extension introduces a new sub-type
where the values 1 and 2 has been assigned values in this document. numbering space where the values 1 and 2 has been assigned values in
Approval of new Mobile IP AAA NAI Extension sub-type numbers is this document. Approval of new Mobile IP NAI Carrying Extension
subject to Expert Review, and a specification is required [5]. sub-type numbers is subject to Expert Review, and a specification is
required [5].
The value assigned to the AAA NAI Extension should be taken from the The content and format for this extension is not specific to AAA
IANA number space for Mobile IPv4 skippable extensions. NAIs, so if in the future new NAIs are defined which does not
strictly fall within the category of AAA NAIs, they may nevertheless
be accommodated within the subtype numbering space defined for the
NAI Carrying Extension defined in this document.
The value assigned to the NAI Carrying Extension should be taken from
the IANA number space for Mobile IPv4 skippable extensions.
8. Acknowledgements 8. Acknowledgements
Thanks to the original authors of the GNAIE draft, Mohamed M Khalil, Thanks to the original authors of the GNAIE draft, Mohamed M Khalil,
Emad Qaddoura, Haseeb Akhtar, Pat R. Calhoun. The original draft Emad Qaddoura, Haseeb Akhtar, Pat R. Calhoun. The original draft was
was removed from the MIP WG charter when no use was seen for the removed from the MIP WG charter when no use was seen for the
extension. The original ideas has been reused in this draft. extension. The original ideas has been reused in this draft.
Also thanks to Henrik Levkowetz and Kevin Purser for valuable Also thanks to Henrik Levkowetz and Kevin Purser for valuable
feedback and help when writing this draft. feedback and help when writing this draft.
Normative References Normative References
[1] Perkins, C., "IP Mobility Support for IPv4", RFC 3344, August [1] Perkins, C., "IP Mobility Support for IPv4", RFC 3344, August
2002. 2002.
skipping to change at page 10, line 7 skipping to change at page 10, line 7
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assignees. revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/