draft-ietf-mip6-mn-ident-option-00.txt   draft-ietf-mip6-mn-ident-option-01.txt 
Network Working Group A. Patel Network Working Group A. Patel
Internet-Draft K. Leung Internet-Draft K. Leung
Expires: June 9, 2005 Cisco Systems Expires: June 21, 2005 Cisco Systems
M. Khalil M. Khalil
H. Akhtar H. Akhtar
Nortel Networks Nortel Networks
K. Chowdhury K. Chowdhury
Starent Networks Starent Networks
December 9, 2004 December 21, 2004
MN Identifier Option for Mobile IPv6 Mobile Node Identifier Option for Mobile IPv6
draft-ietf-mip6-mn-ident-option-00.txt draft-ietf-mip6-mn-ident-option-01.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 9, 2005. This Internet-Draft will expire on June 21, 2005.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract Abstract
This document defines new mobility option to identify mobility This document defines new mobility option to identify mobility
entities using identifiers other than the home IP address. This entities using identifiers other than the home IP address. This
option can be used in messages containing a mobility header. option can be used in messages containing a mobility header.
December 2004
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. MN Identifier option . . . . . . . . . . . . . . . . . . . . . 5 3. Mobile Node Identifier option . . . . . . . . . . . . . . . . 5
3.1 MN-NAI mobility option . . . . . . . . . . . . . . . . . . 6 3.1 MN-NAI mobility option . . . . . . . . . . . . . . . . . . 5
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
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. A mechanism is needed where in
mobility entities can be identified using other identifiers (for mobility entities can be identified using other identifiers (for
example, a network access identifier (NAI) [RFC2486], International example, a network access identifier (NAI) [RFC_2486bis],
Mobile Station Identifier (IMSI), an application/deployment specific International Mobile Station Identifier (IMSI), an application/
opaque identifier etc). Using other identities for a mobile node deployment specific opaque identifier etc). Using other identities
(MN) permits various applicabilities, e.g. authentication using for a mobile node (MN) permits various applicabilities, e.g.
existing infrastructure (AAA (Authentication, Authorization and authentication using existing infrastructure (AAA (Authentication,
Accounting), HLR/AuC (Home Location Register/Authentication Center)), Authorization and Accounting), HLR/AuC (Home Location Register/
dynamic allocation of a mobility anchor point, dynamic allocation of Authentication Center)), dynamic allocation of a mobility anchor
an address etc. point, dynamic allocation of an address etc.
This document defines an option with subtype number which identify a This document defines an option with subtype number which identify 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 expected that other types of
identifiers will be defined by other documents in the future. identifiers will be defined by other documents in the future.
December 2004
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.
3. MN Identifier option December 2004
3. Mobile Node Identifier option
This section defines the Mobile Node Identifier option. Various This section defines the Mobile Node Identifier option. Various
forms of identifiers can be used to identify a MN. Some examples forms of identifiers can be used to identify a MN. Some examples
include a Network Access Identifier (NAI) [RFC2486], an opaque include a Network Access Identifier (NAI) [RFC_2486bis], an opaque
identifier applicable to a particular application, etc. The sub-type identifier applicable to a particular application, etc. The sub-type
field in the option defines the specific type of identifier. 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 5, line 45 skipping to change at page 5, line 47
Subtype: Subtype:
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.
Alignment requirements:
This option does not have any alignment requirements. This option does not have any alignment requirements.
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
[RFC2486]. [RFC_2486bis].
3.2 Processing Considerations 3.2 Processing Considerations
When present, this option MUST appear before any authentication When present, this option MUST appear before any authentication
enabling extension in a message containing a mobility header. Also, related option in a message containing a mobility header.
if this option is present in the first Binding Update used to create
a binding cache entry at the Home Agent, it MUST be present in all December 2004
subsequent Binding Updates used to renew the binding cache entry. If
this option is present in the Binding Update, it MUST be included in
the corresponding reply (Binding Acknowledgement).
4. Security Considerations 4. Security Considerations
None. This document defines new identifiers for a mobile node and Mobile IPv6 already contains one mechanism for identifying mobile
does not introduce new security threats. nodes, the Home Address Option [RFC 3775]. As a result, the
vulnerabilities of the new option defined in this document are
similar to those that already exist for Mobile IPv6. In particular,
the use of a permanent, stable identifier may compromise the privacy
of the user, making it possible to track a particular device or user
as it moves through different locations.
In addition, since an NAI reveals the home 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,
such as those discussed below:
o Encrypting traffic at link layer such that other users on the same
link do not see the identifiers. This mechanism does not help
against attackers on the rest of the path between the mobile node
and its home agent.
o Encrypting the whole packet, such as when using IPsec to protect
the communications with the home agent [RFC 3776].
o Using an authentication mechanism that enables the use of privacy
NAIs [RFC_2486bis] or temporary, changing "pseudonyms" as
identifiers.
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
registrations can use the home address, the window of privacy
vulnerability in this document is reduced as compared to the RFC
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
as well, and affects both communications with the home agent and the
correspondent nodes, both of which have to be told the home address.
December 2004
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 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
field of the Mobile Node Identifier Option. The currently allocated
values are as follows:
NAI (defined in this document) [1]
New values for this namespace can be allocated using Standards Action
[RFC 2434].
December 2004
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. suggestions on this draft. Thanks to Jari Arkko for review and
suggestions regarding security considerations and various other
aspects of the document.
7 Normative References 7 Normative References
[RFC2486] Aboba, B. and M. Beadles, "The Network Access Identifier",
RFC 2486, January 1999.
[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]
Aboba, et. al., B., "The Network Access Identifier",
draft-ietf-radext-rfc2486bis-03.txt (work in progress),
November 2004.
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
skipping to change at page 10, line 4 skipping to change at page 10, line 4
EMail: kleung@cisco.com EMail: kleung@cisco.com
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
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
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
 End of changes. 

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