draft-ietf-mip6-mn-ident-option-02.txt   draft-ietf-mip6-mn-ident-option-03.txt 
Network Working Group A. Patel Network Working Group A. Patel
Internet-Draft K. Leung Internet-Draft K. Leung
Expires: August 11, 2005 Cisco Systems Expires: March 6, 2006 Cisco Systems
M. Khalil M. Khalil
H. Akhtar H. Akhtar
Nortel Networks Nortel Networks
K. Chowdhury K. Chowdhury
Starent Networks Starent Networks
February 10, 2005 September 2, 2005
Mobile Node Identifier Option for Mobile IPv6 Mobile Node Identifier Option for MIPv6
draft-ietf-mip6-mn-ident-option-02.txt draft-ietf-mip6-mn-ident-option-03
Status of this Memo Status of this Memo
By submitting this Internet-Draft, I certify that any applicable By submitting this Internet-Draft, each author represents that any
patent or other IPR claims of which I am aware have been disclosed, applicable patent or other IPR claims of which he or she is aware
and any of which I become aware will be disclosed, in accordance with have been or will be disclosed, and any of which he or she becomes
RFC 3668. aware will be disclosed, in accordance with Section 6 of BCP 79.
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 groups may also distribute working documents as other groups may also distribute working documents as Internet-
Internet-Drafts. 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 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 August 11, 2005. This Internet-Draft will expire on March 6, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). All Rights Reserved. Copyright (C) The Internet Society (2005).
Abstract Abstract
Mobile IPv6 defines a new Mobility header which is used by mobile Mobile IPv6 defines a new Mobility header which is used by mobile
nodes, correspondent nodes, and home agents in all messaging related nodes, correspondent nodes, and home agents in all messaging related
to the creation and management of bindings. Mobile IPv6 nodes need to the creation and management of bindings. Mobile IPv6 nodes need
the capability to identify themselves using an identity other than the capability to identify themselves using an identity other than
February 2005
the default home IP address. Some examples of identifiers include the default home IP address. Some examples of identifiers include
NAI, FQDN, IMSI, MSISDN, etc. This document defines a new mobility NAI, FQDN, IMSI, MSISDN, etc. This document defines a new mobility
option that can be used by Mobile IP6 entities to identify themselves option that can be used by Mobile IPv6 entities to identify
in messages containing a mobility header. 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 . . . . . . . . . . . . . . . . . . 6 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
4.1. General Considerations . . . . . . . . . . . . . . . . . . 7
4.2. MN NAI consideration . . . . . . . . . . . . . . . . . . . 7
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9 6. IPR Disclosure Acknowledgement . . . . . . . . . . . . . . . . 9
7. Normative References . . . . . . . . . . . . . . . . . . . . . 9 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 9 8. Normative References . . . . . . . . . . . . . . . . . . . . . 10
Intellectual Property and Copyright Statements . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11
Intellectual Property and Copyright Statements . . . . . . . . . . 13
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. It is essential to have a mechanism entities using an IPv6 address. It is essential to have a mechanism
wherein mobility entities can be identified using other identifiers wherein mobility entities can be identified using other identifiers
(for 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). deployment specific opaque identifier etc).
skipping to change at page 4, line 5 skipping to change at page 3, line 31
o dynamic allocation of a mobility anchor point, o dynamic allocation of a mobility anchor point,
o dynamic allocation of a home address etc. o dynamic allocation of a home address etc.
This document defines an option with subtype number which denotes a 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 anticipated that other identifiers defined in Section 3.1. It is anticipated that other identifiers
will be defined for use in the mobility header in the future. will be defined for use in the mobility header in the future.
February 2005 This option SHOULD be used when IKE/IPsec is not used for protecting
binding update or binding acknowledgements as specified in [RFC3775].
It is typically used with authentication option [auth_id]. But this
option may be used independently. For example, the identifier can
provide accounting and billing services.
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
this document are to be interpreted as described in RFC 2119. document are to be interpreted as described in RFC 2119.
February 2005
3. Mobile Node Identifier option 3. Mobile Node Identifier option
The Mobile node identifier option is a new optional data field that The Mobile node identifier option is a new optional data field that
is carried in the Mobile IPv6 defined messages which includes the is carried in the Mobile IPv6 defined messages which includes the
mobility header. Various forms of identifiers can be used to mobility header. Various forms of identifiers can be used to
identify a MN. Some examples include a Network Access Identifier identify a MN. Some examples include a Network Access Identifier
(NAI) [RFC_2486bis], an opaque identifier applicable to a particular (NAI) [RFC_2486bis], an opaque identifier applicable to a particular
application, etc. The subtype field in the option defines the application, etc. The subtype field in the option defines the
specific type of identifier. specific type of identifier.
skipping to change at page 6, line 5 skipping to change at page 6, line 12
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 MN-NAI mobility option uses the general format of the Mobile Node
This option uses the subtype value of 1. The MN-NAI mobility option Identifier option as defined in Section 3. This option uses the
is used to identify the mobile node. subtype value of 1. The MN-NAI mobility option 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]. This option MUST be implemented by the entities
implementing this specification.
3.2 Processing Considerations 3.2. Processing Considerations
The location of the MN identifier option is as follows: When present, The location of the MN identifier option is as follows: When present,
this option MUST appear before any authentication related option in a this option MUST appear before any authentication related option in a
message containing a mobility header. message containing a mobility header.
February 2005
4. Security Considerations 4. Security Considerations
4.1. General 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.
In addition, since an NAI reveals the home affiliation of a user, it 4.2. MN NAI consideration
may assist an attacker in determining the identity of the user, help
the attacker in targeting specific victims, or assist in further Since a Mobile Node Identifier option Section 3 reveals the home
probing of the username space. affiliation of a user, it may assist an attacker in determining the
identity of the user, help the attacker in targeting specific
victims, or assist in further probing of the username space.
These vulnerabilities can be addressed through various mechanisms, These vulnerabilities can be addressed through various mechanisms,
such as those discussed below: such as those discussed below:
o Encrypting traffic at link layer such that other users on the same o Encrypting traffic at link layer such that other users on the same
link do not see the identifiers. This mechanism does not help link do not see the identifiers. This mechanism does not help
against attackers on the rest of the path between the mobile node against attackers on the rest of the path between the mobile node
and its home agent. and its home agent.
o Encrypting the whole packet, such as when using IPsec to protect o Encrypting the whole packet, such as when using IPsec to protect
the communications with the home agent [RFC 3776]. the communications with the home agent [RFC 3776].
o Using an authentication mechanism that enables the use of privacy o Using an authentication mechanism that enables the use of privacy
NAIs [RFC_2486bis] or temporary, changing "pseudonyms" as NAIs [RFC_2486bis] or temporary, changing "pseudonyms" as
identifiers. identifiers.
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
3775. In addition, this document is a part of a solution to allow [RFC3775]. In addition, this document is a part of a solution to
dynamic home addresses to be used. This is an improvement to privacy allow dynamic home addresses to be used. This is an improvement to
as well, and affects both communications with the home agent and the privacy as well, and affects both communications with the home agent
correspondent nodes, both of which have to be told the home address. and the correspondent nodes, both of which have to be told the home
address.
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-
MN-ID-OPTION-TYPE. 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, 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
[RFC2434]. [RFC2434].
February 2005 6. IPR Disclosure Acknowledgement
6. Acknowledgements By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
7. 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 8. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 2434, IANA Considerations Section in RFCs", BCP 26, RFC 2434,
October 1998. 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.
[RFC3776] Arkko, J., Devarapalli, V., and F. Dupont, "Using IPsec to
Protect Mobile IPv6 Signaling Between Mobile Nodes and
Home Agents", RFC 3776, 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.
[auth_id] Patel et. al., A., "Authentication Protocol for Mobile
IPv6", draft-ietf-mip6-mn-ident-option-04.txt (work in
progress), February 2005.
Authors' Addresses Authors' Addresses
Alpesh Patel Alpesh Patel
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-853-9580 Phone: +1 408-853-9580
EMail: alpesh@cisco.com Email: alpesh@cisco.com
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@nortel.com
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@nortel.com
Kuntal Chowdhury Kuntal Chowdhury
Starent Networks Starent Networks
2540 Coolwater Dr. 30 International Place
Plano, TX 75025 Tewksbury, MA 01876
US US
Phone: +1 214 550 1416 Phone: +1 214 550 1416
EMail: kchowdury@starentnetworks.com Email: kchowdury@starentnetworks.com
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
 End of changes. 

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