draft-ietf-mip6-mn-ident-option-01.txt   draft-ietf-mip6-mn-ident-option-02.txt 
Network Working Group A. Patel Network Working Group A. Patel
Internet-Draft K. Leung Internet-Draft K. Leung
Expires: June 21, 2005 Cisco Systems Expires: August 11, 2005 Cisco Systems
M. Khalil M. Khalil
H. Akhtar H. Akhtar
Nortel Networks Nortel Networks
K. Chowdhury K. Chowdhury
Starent Networks Starent Networks
December 21, 2004 February 10, 2005
Mobile Node Identifier Option for Mobile IPv6 Mobile Node Identifier Option for Mobile IPv6
draft-ietf-mip6-mn-ident-option-01.txt draft-ietf-mip6-mn-ident-option-02.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, I certify that any applicable By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed, patent or other IPR claims of which I am aware have been disclosed,
and any of which I become aware will be disclosed, in accordance with and any of which I become aware will be disclosed, in accordance with
RFC 3668. RFC 3668.
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
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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 The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://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 June 21, 2005. This Internet-Draft will expire on August 11, 2005.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2005). All Rights Reserved.
Abstract Abstract
This document defines new mobility option to identify mobility Mobile IPv6 defines a new Mobility header which is used by mobile
entities using identifiers other than the home IP address. This nodes, correspondent nodes, and home agents in all messaging related
option can be used in messages containing a mobility header. to the creation and management of bindings. Mobile IPv6 nodes need
the capability to identify themselves using an identity other than
December 2004 February 2005
the default home IP address. Some examples of identifiers include
NAI, FQDN, IMSI, MSISDN, etc. This document defines a new mobility
option that can be used by Mobile IP6 entities to identify themselves
in messages containing a mobility header.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Mobile Node Identifier option . . . . . . . . . . . . . . . . 5 3. Mobile Node Identifier option . . . . . . . . . . . . . . . . 5
3.1 MN-NAI mobility option . . . . . . . . . . . . . . . . . . 5 3.1 MN-NAI mobility option . . . . . . . . . . . . . . . . . . 6
3.2 Processing Considerations . . . . . . . . . . . . . . . . 6 3.2 Processing Considerations . . . . . . . . . . . . . . . . 6
4. Security Considerations . . . . . . . . . . . . . . . . . . . 7 4. Security Considerations . . . . . . . . . . . . . . . . . . . 7
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9
7. Normative References . . . . . . . . . . . . . . . . . . . . . 9 7. Normative References . . . . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 9 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 9
Intellectual Property and Copyright Statements . . . . . . . . 11 Intellectual Property and Copyright Statements . . . . . . . . 11
December 2004 February 2005
1. Introduction 1. Introduction
The base specification of Mobile IPv6 [RFC3775] identifies mobility The base specification of Mobile IPv6 [RFC3775] identifies mobility
entities using an IPv6 address. A mechanism is needed where in entities using an IPv6 address. It is essential to have a mechanism
mobility entities can be identified using other identifiers (for wherein mobility entities can be identified using other identifiers
example, a network access identifier (NAI) [RFC_2486bis], (for example, a network access identifier (NAI) [RFC_2486bis],
International Mobile Station Identifier (IMSI), an application/ International Mobile Station Identifier (IMSI), an application/
deployment specific opaque identifier etc). Using other identities deployment specific opaque identifier etc).
for a mobile node (MN) permits various applicabilities, e.g.
authentication using existing infrastructure (AAA (Authentication,
Authorization and Accounting), HLR/AuC (Home Location Register/
Authentication Center)), dynamic allocation of a mobility anchor
point, dynamic allocation of an address etc.
This document defines an option with subtype number which identify a The capability to identify a mobility entity via identifiers other
than the IPv6 address can be leveraged for performing various
functions, eg.
o authentication and authorization using an existing AAA
(Authentication, Authorization and Accounting) infrastructure or
via an HLR/AuC (Home Location Register/Authentication Center),
o dynamic allocation of a mobility anchor point,
o dynamic allocation of a home address etc.
This document defines an option with subtype number which denotes a
specific type of identifier. One instance of subtype, the NAI is specific type of identifier. One instance of subtype, the NAI is
defined in Section 3.1. It is expected that other types of defined in Section 3.1. It is anticipated that other identifiers
identifiers will be defined by other documents in the future. will be defined for use in the mobility header in the future.
December 2004 February 2005
2. Terminology 2. Terminology
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
this document are to be interpreted as described in RFC 2119. this document are to be interpreted as described in RFC 2119.
December 2004 February 2005
3. Mobile Node Identifier option 3. Mobile Node Identifier option
This section defines the Mobile Node Identifier option. Various The Mobile node identifier option is a new optional data field that
forms of identifiers can be used to identify a MN. Some examples is carried in the Mobile IPv6 defined messages which includes the
include a Network Access Identifier (NAI) [RFC_2486bis], an opaque mobility header. Various forms of identifiers can be used to
identifier applicable to a particular application, etc. The sub-type identify a MN. Some examples include a Network Access Identifier
field in the option defines the specific type of identifier. (NAI) [RFC_2486bis], an opaque identifier applicable to a particular
application, etc. The subtype field in the option defines the
specific type of identifier.
This option can be used in mobility messages containing a mobility This option can be used in mobility messages containing a mobility
header. The subtype field in the option is used to interpret the header. The subtype field in the option is used to interpret the
specific type of identifier. specific type of identifier.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Option Type | Option Length | | Option Type | Option Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 5, line 49 skipping to change at page 6, line 5
Subtype field defines the specific type of identifier included Subtype field defines the specific type of identifier included
in the identifier field. in the identifier field.
Identifier: Identifier:
A variable length identifier of type as specified by the A variable length identifier of type as specified by the
subtype field of this option. subtype field of this option.
This option does not have any alignment requirements. This option does not have any alignment requirements.
February 2005
3.1 MN-NAI mobility option 3.1 MN-NAI mobility option
The format of the MN-NAI mobility option is as defined in Section 3. The format of the MN-NAI mobility option is as defined in Section 3.
This option uses the subtype value of 1. The MN-NAI mobility option This option uses the subtype value of 1. The MN-NAI mobility option
December 2004
is used to identify the mobile node. is used to identify the mobile node.
The MN-NAI mobility option uses an identifier of the form user@realm The MN-NAI mobility option uses an identifier of the form user@realm
[RFC_2486bis]. [RFC_2486bis].
3.2 Processing Considerations 3.2 Processing Considerations
When present, this option MUST appear before any authentication The location of the MN identifier option is as follows: When present,
related option in a message containing a mobility header. this option MUST appear before any authentication related option in a
message containing a mobility header.
December 2004 February 2005
4. Security Considerations 4. Security Considerations
Mobile IPv6 already contains one mechanism for identifying mobile Mobile IPv6 already contains one mechanism for identifying mobile
nodes, the Home Address Option [RFC 3775]. As a result, the nodes, the Home Address Option [RFC 3775]. As a result, the
vulnerabilities of the new option defined in this document are vulnerabilities of the new option defined in this document are
similar to those that already exist for Mobile IPv6. In particular, similar to those that already exist for Mobile IPv6. In particular,
the use of a permanent, stable identifier may compromise the privacy the use of a permanent, stable identifier may compromise the privacy
of the user, making it possible to track a particular device or user of the user, making it possible to track a particular device or user
as it moves through different locations. as it moves through different locations.
skipping to change at page 8, line 5 skipping to change at page 8, line 5
In any case, it should be noted that as the identifier option is only In any case, it should be noted that as the identifier option is only
needed on the first registration at the home agent and subsequent needed on the first registration at the home agent and subsequent
registrations can use the home address, the window of privacy registrations can use the home address, the window of privacy
vulnerability in this document is reduced as compared to the RFC vulnerability in this document is reduced as compared to the RFC
3775. In addition, this document is a part of a solution to allow 3775. In addition, this document is a part of a solution to allow
dynamic home addresses to be used. This is an improvement to privacy dynamic home addresses to be used. This is an improvement to privacy
as well, and affects both communications with the home agent and the as well, and affects both communications with the home agent and the
correspondent nodes, both of which have to be told the home address. correspondent nodes, both of which have to be told the home address.
December 2004 February 2005
5. IANA Considerations 5. IANA Considerations
IANA services are required for this document. The values for new IANA services are required for this document. The values for new
mobility options must be assigned from the Mobile IPv6 [RFC3775] mobility options must be assigned from the Mobile IPv6 [RFC3775]
numbering space. numbering space.
The values for Mobility Option types MN-ID-OPTION-TYPE as defined in The values for Mobility Option types MN-ID-OPTION-TYPE as defined in
Section 3 need to be assigned. The suggested value is 7 for the Section 3 need to be assigned. The suggested value is 7 for the
MN-ID-OPTION-TYPE. MN-ID-OPTION-TYPE.
IANA should record a value for this new mobility option. IANA should record a value for this new mobility option.
In addition, the IANA needs to create a new namespace for the subtype In addition, IANA needs to create a new namespace for the subtype
field of the Mobile Node Identifier Option. The currently allocated field of the Mobile Node Identifier Option. The currently allocated
values are as follows: values are as follows:
NAI (defined in this document) [1] NAI (defined in this document) [1]
New values for this namespace can be allocated using Standards Action New values for this namespace can be allocated using Standards Action
[RFC 2434]. [RFC 2434].
December 2004 February 2005
6. Acknowledgements 6. Acknowledgements
The authors would like to thank Basavaraj Patil for his review and The authors would like to thank Basavaraj Patil for his review and
suggestions on this draft. Thanks to Jari Arkko for review and suggestions on this draft. Thanks to Jari Arkko for review and
suggestions regarding security considerations and various other suggestions regarding security considerations and various other
aspects of the document. aspects of the document.
7 Normative References 7 Normative References
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 2434,
October 1998.
[RFC3775] Johnson, D., Perkins, C. and J. Arkko, "Mobility Support [RFC3775] Johnson, D., Perkins, C. and J. Arkko, "Mobility Support
in IPv6", RFC 3775, June 2004. in IPv6", RFC 3775, June 2004.
[RFC_2486bis] [RFC_2486bis]
Aboba, et. al., B., "The Network Access Identifier", Aboba, et. al., B., "The Network Access Identifier",
draft-ietf-radext-rfc2486bis-03.txt (work in progress), draft-ietf-radext-rfc2486bis-03.txt (work in progress),
November 2004. November 2004.
Authors' Addresses Authors' Addresses
skipping to change at page 9, line 44 skipping to change at page 10, line 5
Kent Leung Kent Leung
Cisco Systems Cisco Systems
170 W. Tasman Drive 170 W. Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
US US
Phone: +1 408-526-5030 Phone: +1 408-526-5030
EMail: kleung@cisco.com EMail: kleung@cisco.com
February 2005
Mohamed Khalil Mohamed Khalil
Nortel Networks Nortel Networks
2221 Lakeside Blvd. 2221 Lakeside Blvd.
Richardson, TX 75082 Richardson, TX 75082
US US
Phone: +1 972-685-0574 Phone: +1 972-685-0574
EMail: mkhalil@nortelnetworks.com EMail: mkhalil@nortelnetworks.com
December 2004
Haseeb Akhtar Haseeb Akhtar
Nortel Networks Nortel Networks
2221 Lakeside Blvd. 2221 Lakeside Blvd.
Richardson, TX 75082 Richardson, TX 75082
US US
Phone: +1 972-684-4732 Phone: +1 972-684-4732
EMail: haseebak@nortelnetworks.com EMail: haseebak@nortelnetworks.com
Kuntal Chowdhury Kuntal Chowdhury
Starent Networks Starent Networks
2540 Coolwater Dr. 2540 Coolwater Dr.
Plano, TX 75025 Plano, TX 75025
US US
Phone: +1 214 550 1416 Phone: +1 214 550 1416
EMail: kchowdury@starentnetworks.com EMail: kchowdury@starentnetworks.com
December 2004 February 2005
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
skipping to change at page 11, line 43 skipping to change at page 11, line 43
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject Copyright (C) The Internet Society (2005). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
Acknowledgment 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/