draft-ietf-mip6-bootstrapping-integrated-dhc-02.txt   draft-ietf-mip6-bootstrapping-integrated-dhc-03.txt 
Network Working Group K. Chowdhury, Editor Network Working Group K. Chowdhury, Editor
Internet-Draft Starent Networks Internet-Draft Starent Networks
Intended status: Standards Track A. Yegin Intended status: Standards Track A. Yegin
Expires: August 11, 2007 Samsung AIT Expires: October 21, 2007 Samsung AIT
February 7, 2007 April 19, 2007
MIP6-bootstrapping for the Integrated Scenario MIP6-bootstrapping for the Integrated Scenario
draft-ietf-mip6-bootstrapping-integrated-02.txt draft-ietf-mip6-bootstrapping-integrated-03.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware 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 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. 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
skipping to change at page 1, line 35 skipping to change at page 1, line 35
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, 2007. This Internet-Draft will expire on October 21, 2007.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
The Mobile IPv6 bootstrapping problem statement describes two main The Mobile IPv6 bootstrapping problem statement describes two main
scenarios. In the first scenario (i.e. the split scenario), the scenarios. In the first scenario (i.e. the split scenario), the
mobile node's mobility service is authorized by a different service mobile node's mobility service is authorized by a different service
authorizer than the basic network access authorizer. In the second authorizer than the basic network access authorizer. In the second
scenario (i.e. the integrated scenario), the mobile node's mobility scenario (i.e. the integrated scenario), the mobile node's mobility
service is authorized by the same service authorizer as the basic service is authorized by the same service authorizer as the basic
network access service authorizer. This document defines a method network access service authorizer. This document defines a method
for home agent information discovery for the integrated scenario. for home agent information discovery for the integrated scenario.
Table of Contents Table of Contents
1. Introduction and Scope . . . . . . . . . . . . . . . . . . . . 3 1. Introduction and Scope . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Solution Overview . . . . . . . . . . . . . . . . . . . . . . 5 3. List of Assumptions . . . . . . . . . . . . . . . . . . . . . 5
3.1. Logical Diagram of the Integrated Scenario . . . . . . . . 5 4. Solution Overview . . . . . . . . . . . . . . . . . . . . . . 6
3.2. Bootstrapping Message Sequence, Success Case . . . . . . . 6 4.1. Logical Diagram of the Integrated Scenario . . . . . . . . 6
3.2.1. Home Agent allocation in the MSP . . . . . . . . . . . 6 4.2. Bootstrapping Message Sequence, Success Case . . . . . . . 7
3.2.2. Home Agent allocation in the ASP . . . . . . . . . . . 8 4.2.1. Home Agent allocation in the MSP . . . . . . . . . . . 7
3.3. Bootstrapping Message Sequence: Fallback case . . . . . . 10 4.2.2. Home Agent allocation in the ASP . . . . . . . . . . . 9
3.4. HoA and IKEv2 SA Bootstrapping in the Integrated 4.3. Bootstrapping Message Sequence: Fallback case . . . . . . 11
Scenario . . . . . . . . . . . . . . . . . . . . . . . . . 10 4.4. HoA and IKEv2 SA Bootstrapping in the Integrated
4. Security Considerations . . . . . . . . . . . . . . . . . . . 11 Scenario . . . . . . . . . . . . . . . . . . . . . . . . . 11
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 5. Security Considerations . . . . . . . . . . . . . . . . . . . 12
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 15 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 15
8.1. Normative References . . . . . . . . . . . . . . . . . . . 16 9. Normative References . . . . . . . . . . . . . . . . . . . . . 16
8.2. Informative References . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18
Intellectual Property and Copyright Statements . . . . . . . . . . 19 Intellectual Property and Copyright Statements . . . . . . . . . . 19
1. Introduction and Scope 1. Introduction and Scope
The Mobile IPv6 protocol [RFC3775] requires the mobile node to have The Mobile IPv6 protocol [RFC3775] requires the mobile node to have
knowledge of its Home Address, the home agent address and the knowledge of its Home Address, the home agent address and the
cryptographic materials for establishing an IPsec security cryptographic materials for establishing an IPsec security
association with the home agent prior to performing home association with the home agent prior to performing home
registration. The mechanism via which the mobile node obtains these registration. The mechanism via which the mobile node obtains these
skipping to change at page 3, line 39 skipping to change at page 3, line 39
[BOOT-SPLIT] identifies four different components of the [BOOT-SPLIT] identifies four different components of the
bootstrapping problem: home agent address discovery, HoA assignment, bootstrapping problem: home agent address discovery, HoA assignment,
IPsec Security Association setup and Authentication and Authorization IPsec Security Association setup and Authentication and Authorization
with the MSA. This document defines a mechanism for home agent with the MSA. This document defines a mechanism for home agent
address discovery. For the rest of components, please refer to address discovery. For the rest of components, please refer to
[BOOT-SPLIT]. [BOOT-SPLIT].
In the integrated scenario, the bootstrapping of the home agent In the integrated scenario, the bootstrapping of the home agent
information can be performed via DHCPv6. DHCPv6 is designed for information can be performed via DHCPv6. DHCPv6 is designed for
configuration management and it is being deployed by operators to configuration management and it is being deployed by operators to
handle their configuration management needs in their networks. handle their configuration management needs in their networks. This
document defines the mip6 bootstrapping procedures for the integrated
scenario. This draft enables Home Agent assignment in the integrated
scenario by utilizing DHCP and AAA protocols. The specification
utilizes DHCP and AAA options and AVPs that are defined in [HIOPT],
[MIP6-Dime], and [MIP6-RADIUS]. This document specifies the
interworking among MN, NAS, DHCP, and AAA entities for bootstrapping
procedure in the integrated scenario.
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 this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
General mobility terminology can be found in [RFC3753]. The General mobility terminology can be found in [RFC3753]. The
following additional terms, as defined in [RFC4640], are used in this following additional terms, as defined in [RFC4640], are used in this
document: document:
skipping to change at page 4, line 26 skipping to change at page 4, line 26
authenticates a mobile node and establishes the mobile node's authenticates a mobile node and establishes the mobile node's
authorization to receive Internet service. authorization to receive Internet service.
Access Service Provider (ASP): A network operator that provides Access Service Provider (ASP): A network operator that provides
direct IP packet forwarding to and from the mobile node. direct IP packet forwarding to and from the mobile node.
Mobility Service Authorizer (MSA): A service provider that authorizes Mobility Service Authorizer (MSA): A service provider that authorizes
Mobile IPv6 service. Mobile IPv6 service.
Mobility Service Provider (MSP): A service provider that provides Mobility Service Provider (MSP): A service provider that provides
Mobile IPv6 service. In order to obtain such service, the mobile Mobile IPv6 service. A MSP is called home MSP when MSP == MSA. In
node must be authenticated and authorized to obtain the Mobile IPv6 this document the term MSP means a Mobility Service Provider that has
service. roaming relationship with the MSA but it is not the MSA.
Split scenario: A scenario where the mobility service and the network Split scenario: A scenario where the mobility service and the network
access service are authorized by different entities. access service are authorized by different entities.
Integrated Scenario: A scenario where the mobility service and the Integrated Scenario: A scenario where the mobility service and the
network access service are authorized by the same entity. network access service are authorized by the same entity.
3. Solution Overview 3. List of Assumptions
3.1. Logical Diagram of the Integrated Scenario The following assumptions are made in this document:
a. MSA == ASA.
b. MSA and MSP roaming relationship is assumed but not required.
c. DHCP relay and NAS are collocated or there is a way to pass
received AAA information from the NAS to the DHCP relay.
d. the NAS shall support MIPv6 specific AAA attributes as specified
in [MIP6-RADIUS] and [MIP6-Dime].
e. MSP == MSA scenario is termed as home MSP.
4. Solution Overview
4.1. Logical Diagram of the Integrated Scenario
In the integrated scenario the mobile node utilizes network access In the integrated scenario the mobile node utilizes network access
authentication process to bootstrap Mobile IPv6. It is assumed that authentication process to bootstrap Mobile IPv6. It is assumed that
the access service authorizer is mobility service aware. This allows the access service authorizer is mobility service aware. This allows
for Mobile IPv6 bootstrapping at the time of access authentication for Mobile IPv6 bootstrapping at the time of access authentication
and authorization. Also, the mechanism defined in this document and authorization. Also, the mechanism defined in this document
requires the NAS to support Mobile IPv6 specific AAA attributes and a requires the NAS to support Mobile IPv6 specific AAA attributes and a
collocated DHCP relay agent. collocated DHCP relay agent.
The following diagram shows the network elements and layout in the The following diagram shows the network elements and layout in the
skipping to change at page 6, line 4 skipping to change at page 7, line 4
+----+ | | |DHCP | | +----+ | | |DHCP | |
| MN |------| NAS/|----|Server| | | MN |------| NAS/|----|Server| |
+----+ |Relay| | | | +----+ |Relay| | | |
+-----+ +------+ | +-----+ +------+ |
| |
| |
+--------+ | +--------+ +--------+ | +--------+
| HA | | | HA | | HA | | | HA |
| in ASP | | |in MSP | | in ASP | | |in MSP |
+--------+ | +--------+ +--------+ | +--------+
Integrated Scenario, Network Diagram with DHCP Integrated Scenario, Network Diagram with DHCP Server
Figure 1. Integrated Scenario, Network Diagram with DHCP Figure 1. Integrated Scenario, Network Diagram with DHCP
Figure 1 shows the AAA infrastructure with a AAA client (NAS), a AAA Figure 1 shows the AAA infrastructure with a AAA client (NAS), a AAA
proxy in the visited network and a AAA server in the home network. proxy in the visited network and a AAA server in the home network.
The user's home network authorizes the mobile node for network access The user's home network authorizes the mobile node for network access
and also for mobility services. Note that a home agent for usage and also for mobility services. Note that a home agent for usage
with the mobile node might be selected in the access service with the mobile node might be selected in the access service
provider's network or alternatively in the mobility service provider's network or alternatively in the mobility service
provider's network. provider's network.
The mobile node interacts with the DHCP Server via the Relay Agent The mobile node interacts with the DHCP Server via the Relay Agent
after the network access authentication as part of the mobile node after the network access authentication as part of the mobile node
configuration procedure. configuration procedure.
3.2. Bootstrapping Message Sequence, Success Case 4.2. Bootstrapping Message Sequence, Success Case
In the success case, the mobile node is able to acquire the home In the success case, the mobile node is able to acquire the home
agent address via a DHCPv6 query. The message flows for home agent agent address via a DHCPv6 query. The message flows for home agent
allocation in the ASP and the MSP are illustrated below. Since, in allocation in the ASP and the MSP are illustrated below. Since, in
the integrated scenario, the ASA and the MSA are the same, it can be the integrated scenario, the ASA and the MSA are the same, it can be
safely assumed that the AAAH used for network access authentication safely assumed that the AAAH used for network access authentication
(ASA) has access to the same database as the AAAH used for the (ASA) has access to the same database as the AAAH used for the
mobility service authentication (MSA). Hence, the same AAAH can mobility service authentication (MSA). Hence, the same AAAH can
authorize the mobile node for network access and mobility service at authorize the mobile node for network access and mobility service at
the same time. the same time. When the MN performs Mobile IPv6 registration (IKEv2
exchanges), the AAAH ensures that the MN is accessing the assigned
Home Agent for that MSP.
3.2.1. Home Agent allocation in the MSP 4.2.1. Home Agent allocation in the MSP
This section describes a scenario where the home agent is allocated This section describes a scenario where the home agent is allocated
in the mobile node's home MSP network. in order to provide the mobile in the mobile node's MSP network(s). in order to provide the mobile
node with information about the assigned home agent the AAAH conveys node with information about the assigned home agent the AAAH conveys
the assigned home agent's information to the NAS via AAA protocol the assigned home agent's information to the NAS via AAA protocol
[MIP6-RADIUS] or [MIP6-Dime]. [MIP6-RADIUS] or [MIP6-Dime].
| |
--------------ASP------>|<--ASA+MSA-- --------------ASP------>|<--ASA+MSA--
| |
+----+ +------+ +-------+ +-----+ +----+ +------+ +-------+ +-----+
| | | | | | | | | | | | | | | |
| MN/| |NAS/ | | DHCP | |AAAH | | MN/| |NAS/ | | DHCP | |AAAH |
skipping to change at page 7, line 34 skipping to change at page 8, line 34
| | | | | | | |
| | 4 | | | | 4 | |
| |<------------| | | |<------------| |
| | | | | | | |
| 5 | | | | 5 | | |
|<--------------| | | |<--------------| | |
| | | | | | | |
Home Agent in the MSP Home Agent in the MSP
Figure 2. The home agent allocation in the home MSP Figure 2. The home agent allocation in the MSP
Figure 2 shows the message sequence for home agent allocation in the Figure 2 shows the message sequence for home agent allocation in the
home MSP. MSP.
(1) The mobile node executes the network access authentication (1) The mobile node executes the network access authentication
procedure (e.g., IEEE 802.11i/802.1X) and thereby interacts with the procedure (e.g., IEEE 802.11i/802.1X) and thereby interacts with the
NAS. The NAS is in the ASP and it interacts with the AAAH, which is NAS. The NAS is in the ASP and it interacts with the AAAH, which is
in the ASA/MSA, to authenticate the mobile node. In the process of in the ASA/MSA, to authenticate the mobile node. In the process of
authorizing the mobile node the AAAH verifies in the AAA profile that authorizing the mobile node the AAAH verifies in the AAA profile that
the mobile node is allowed to use Mobile IPv6 service. The AAAH the mobile node is allowed to use Mobile IPv6 service. The AAAH
assigns a home agent in the home MSP and returns this information to assigns home agent in the home MSP and other authorized MSPs and
the NAS. returns this information to the NAS. The NAS may keep the received
information for a configurable duration or it may keep the
information for as long as the MN is connected to the NAS.
(2) The mobile node sends a DHCPv6 Information Request message (2) The mobile node sends a DHCPv6 Information Request message
[RFC3315] to the All_DHCP_Relay_Agents_and_Servers multicast address. [RFC3315] to the All_DHCP_Relay_Agents_and_Servers multicast address.
In this message the mobile node (DHCP client) SHALL include the In this message the mobile node (DHCP client) SHALL include the
Option Code for Home Network Identifier Option [HIOPT] in the Option Code for Home Network Identifier Option [HIOPT] in the
OPTION_ORO, Home Network Identifier Option with id-type set to 1 and OPTION_ORO, Home Network Identifier Option with id-type set to 1 and
the Home Network Identifier field set to the network realm of the the Home Network Identifier field set to the network realm of the
home MSP [HIOPT]. The mobile node SHALL also include the home MSP [HIOPT]. The mobile node SHALL also include the
OPTION_CLIENTID to identify itself to the DHCP server. OPTION_CLIENTID to identify itself to the DHCP server.
(3) The Relay Agent intercepts the Information Request from the (3) The Relay Agent intercepts the Information Request from the
mobile node and forwards it to the DHCP server. The Relay Agent also mobile node and forwards it to the DHCP server. The Relay Agent also
includes the received home agent information from the AAAH in the includes the received home agent information from the AAAH in the
skipping to change at page 8, line 12 skipping to change at page 9, line 15
In this message the mobile node (DHCP client) SHALL include the In this message the mobile node (DHCP client) SHALL include the
Option Code for Home Network Identifier Option [HIOPT] in the Option Code for Home Network Identifier Option [HIOPT] in the
OPTION_ORO, Home Network Identifier Option with id-type set to 1 and OPTION_ORO, Home Network Identifier Option with id-type set to 1 and
the Home Network Identifier field set to the network realm of the the Home Network Identifier field set to the network realm of the
home MSP [HIOPT]. The mobile node SHALL also include the home MSP [HIOPT]. The mobile node SHALL also include the
OPTION_CLIENTID to identify itself to the DHCP server. OPTION_CLIENTID to identify itself to the DHCP server.
(3) The Relay Agent intercepts the Information Request from the (3) The Relay Agent intercepts the Information Request from the
mobile node and forwards it to the DHCP server. The Relay Agent also mobile node and forwards it to the DHCP server. The Relay Agent also
includes the received home agent information from the AAAH in the includes the received home agent information from the AAAH in the
OPTION_MIP6-RELAY-Option [HIOPT]. OPTION_MIP6-RELAY-Option [HIOPT]. If a NAS implementation does not
store the received information as long as the MN's session remains in
the ASP, and if the MN delays sending DHCP request, the NAS/DHCP
relay does not include the OPTION_MIP6-RELAY-Option in the Relay
Forward message.
(4) The DHCP server identifies the client by looking at the DUID for (4) The DHCP server identifies the client by looking at the DUID for
the client in the OPTION_CLIENTID. The DHCP server also determines the client in the OPTION_CLIENTID. The DHCP server also determines
that the mobile node is requesting home agent information in the MSP that the mobile node is requesting home agent information in the MSP
by looking at the Home Network Identifier Option (id-type 1). The by looking at the Home Network Identifier Option (id-type 1). The
DHCP server determines that the home agent is allocated by the AAAH DHCP server determines that the home agent is allocated by the AAAH
by looking at the MIP6 home agent sub-option in the OPTION_MIP6- by looking at the MIP6 home agent sub-option in the OPTION_MIP6-
RELAY-Option. The DHCP server extracts the allocated home agent RELAY-Option. The DHCP server extracts the allocated home agent
information from the OPTION_MIP6-RELAY-Option and includes it in the information from the OPTION_MIP6-RELAY-Option and includes it in the
Home Network Information Option [HIOPT] in the Reply Message. Home Network Information Option [HIOPT] in the Reply Message. If the
requested information is not available in the DHCP server, it follows
the behavior described in [HIOPT].
(5) The Relay Agent relays the Reply Message from the DHCP server to (5) The Relay Agent relays the Reply Message from the DHCP server to
the mobile node. At this point, the mobile node has the home agent the mobile node. At this point, the mobile node has the home agent
information that it requested. information that it requested.
3.2.2. Home Agent allocation in the ASP 4.2.2. Home Agent allocation in the ASP
This section describes a scenario where the mobile node requests for This section describes a scenario where the mobile node requests for
home agent allocation in the ASP by setting the id-type field to zero home agent allocation in the ASP by setting the id-type field to zero
in the Home Network Identifier Option in the DHCPv6 request message. in the Home Network Identifier Option in the DHCPv6 request message.
In this scenario, the ASP becomes the MSP for the duration of the In this scenario, the ASP becomes the MSP for the duration of the
network access authentication session. network access authentication session.
| |
--------------ASP-------->|<--ASA+MSA-- --------------ASP-------->|<--ASA+MSA--
| |
skipping to change at page 10, line 32 skipping to change at page 11, line 32
configured to do so, the DHCP server allocates an home agent from its configured to do so, the DHCP server allocates an home agent from its
configured list of home agents and includes it in the Home Network configured list of home agents and includes it in the Home Network
Information Option [HIOPT] in the Reply Message. Note that in this Information Option [HIOPT] in the Reply Message. Note that in this
case, the DHCP server does not use the received information in the case, the DHCP server does not use the received information in the
OPTION_MIP6-RELAY-Option. OPTION_MIP6-RELAY-Option.
(5) The Relay Agent relays the Reply Message from the DHCP server to (5) The Relay Agent relays the Reply Message from the DHCP server to
the mobile node. At this point, the mobile node has the home agent the mobile node. At this point, the mobile node has the home agent
information that it requested. information that it requested.
3.3. Bootstrapping Message Sequence: Fallback case 4.3. Bootstrapping Message Sequence: Fallback case
In the fallback case, the mobile node is not able to acquire the home In the fallback case, the mobile node is not able to acquire the home
agent information via DHCPv6. The mobile node MAY perform DNS agent information via DHCPv6. The mobile node MAY perform DNS
queries to discover the home agent address as defined in queries to discover the home agent address as defined in
[BOOT-SPLIT]. To perform DNS based home agent discovery, the mobile [BOOT-SPLIT]. To perform DNS based home agent discovery, the mobile
node needs to know the DNS server address. How the mobile node knows node needs to know the DNS server address. How the mobile node knows
the DNS server address is outside the scope of this document. the DNS server address is outside the scope of this document.
3.4. HoA and IKEv2 SA Bootstrapping in the Integrated Scenario 4.4. HoA and IKEv2 SA Bootstrapping in the Integrated Scenario
In the integrated scenario, the HoA, IPsec Security Associations In the integrated scenario, the HoA, IPsec Security Associations
setup, and Authentication and Authorization with the MSA are setup, and Authentication and Authorization with the MSA are
bootstrapped via the same mechanism as described in the bootstrapping bootstrapped via the same mechanism as described in the bootstrapping
solution for split scenario [BOOT-SPLIT]. solution for split scenario [BOOT-SPLIT].
4. Security Considerations 5. Security Considerations
The transport of the assigned home agent information via the AAA The transport of the assigned home agent information via the AAA
infrastructure (i.e., from the AAA server to the AAA client) to the infrastructure (i.e., from the AAA server to the AAA client) to the
NAS is subject to the standard RADIUS and Diameter security NAS may only be integrity protected as per standard RADIUS and
considerations. No new security considerations are imposed by the Diameter security mechanisms. No additional security considerations
usage of this document. The security mechanisms provided by are imposed by the usage of this document. The security mechanisms
[RFC2865] and [RFC3588] are applicable and provide adequate security provided by [RFC2865] and [RFC3588] are applicable for this purpose.
for this purpose.
The communication between the NAS/DHCP relay agent to the DHCP server
must be authenticated, integrity and replay protected. Deployments
MAY either rely on lower-layer security, (i.e., physical or link
layer security), or rely on security mechanisms specifically defined
for DHCPv6, such as [RFC4030].
The communication between the DHCP client and the DHCP server for the
exchange of home agent information is security sensitive and requires
authentication, integrity and replay protection. Either lower-layer
security (such as link layer security established as part of the
network access authentication protocol run) or DHCP security
[RFC3118] can be used. The latter approach is only applicable in
non-roaming environments due to the limited applicability of the DHCP
security mechanisms. An adversary that is able to modify home agent
information can force the mobile node to use a different home agent
than intended by the MSA. However, this type of attack can be
detected by the security mechanism between the mobile node and the
home agent.
Overall, the home agent information carried by the AAA protocols and
DHCP does not impose any new security concerns for the transport
protocols.
If the home agent selected by the mobile node is local or nearby, (as
in section 3.2.2), disclosing the mobile node's home address (e.g.,
by updating the mobile node's FQDN in the DNS) has the potential to
expose some information about the mobile node's location.
Just by knowing the mobile node's home address, an attacker cannot
determine whether the mobile node's home address belongs to a home
agent that is local, nearby or remote for the mobile node and, hence,
cannot determine where the mobile node is actually located. However,
if additional information such as the mobile node's home agent
selection policy and the home agent allocation policy of ASPs is
known by an attacker, this may be different. For instance, if an
attacker knows that the mobile node's home agent selection policy is
to bootstrap with a new local home agent whenever entering a new
network (e.g., because the mobile node wants to improve routing
efficiency in Bi-directional Tunneling mode), the attacker can track
the mobile node's movement if it is aware of the mobile node's
current home addresses. The accuracy of the revealed location
information depends on the deployment style of home agents and the
frequency of bootstrapping.
Consequently, if a high level of location privacy is desired, a
mobile node should not switch to local home agents in an eager manner
or should not reveal its home address to untrusted nodes.
Furthermore, the disclosure of policy information that can help
locating the mobile node should be carefully considered.
5. IANA Considerations 6. IANA Considerations
None None
6. Acknowledgements 7. Acknowledgements
The authors would like to thank Kilian Weniger for his valuable The authors would like to thank Kilian Weniger, Vidya Narayanan, and
comment related to location privacy. George Tsirtsis for their review and comments.
7. Contributors 8. Contributors
This contribution is a joint effort of the bootstrapping solution This contribution is a joint effort of the bootstrapping solution
design team of the MIP6 WG. The contributors include Gerardo design team of the MIP6 WG. The contributors include Gerardo
Giaretta, Basavaraj Patil, Alpesh Patel, Jari Arkko, James Kempf, Giaretta, Basavaraj Patil, Alpesh Patel, Jari Arkko, James Kempf,
Gopal Dommety, Alper Yegin, Junghoon Jee, Vijay Devarapalli, Kuntal Gopal Dommety, Alper Yegin, Junghoon Jee, Vijay Devarapalli, Kuntal
Chowdhury, Julien Bournelle, and Hannes Tschofenig. Chowdhury, Julien Bournelle, and Hannes Tschofenig.
The design team members can be reached at: The design team members can be reached at:
Gerardo Giaretta gerardo.giaretta@tilab.com Gerardo Giaretta gerardo.giaretta@tilab.com
skipping to change at page 16, line 5 skipping to change at page 16, line 5
Junghoon Jee jhjee@etri.re.kr Junghoon Jee jhjee@etri.re.kr
Vijay Devarapalli vijayd@iprg.nokia.com Vijay Devarapalli vijayd@iprg.nokia.com
Kuntal Chowdhury kchowdhury@starentnetworks.com Kuntal Chowdhury kchowdhury@starentnetworks.com
Julien Bournelle julien.bournelle@int-evry.fr Julien Bournelle julien.bournelle@int-evry.fr
Hannes Tschofenig hannes.tschofenig@siemens.com Hannes Tschofenig hannes.tschofenig@siemens.com
8. References 9. Normative References
8.1. Normative References [BOOT-SPLIT]
Giaretta et. al., A., "Mobile IPv6 bootstrapping in split
scenario.", draft-ietf-mip6-bootstrapping-split-04.txt
(work in progress), December 2006.
[HIOPT] Hee Jang et. al., A., "DHCP Option for Home Agent [HIOPT] Hee Jang et. al., A., "DHCP Option for Home Agent
Discovery in MIPv6.", draft-ietf-mip6-hiopt-01.txt (work Discovery in MIPv6.", draft-ietf-mip6-hiopt-02.txt (work
in progress), December 2006. in progress), February 2007.
[MIP6-Dime] [MIP6-Dime]
Korhonen et. al., J., "Diameter Mobile IPv6: NAS - HAAA Korhonen et. al., J., "Diameter Mobile IPv6: NAS - HAAA
Support.", draft-ietf-dime-mip6-integrated-02.txt (work in Support.", draft-ietf-dime-mip6-integrated-03.txt (work in
progress), January 2007. progress), February 2007.
[MIP6-RADIUS] [MIP6-RADIUS]
Chowdhury et. al., K., "RADIUS Mobile IPv6 Support.", Chowdhury et. al., K., "RADIUS Mobile IPv6 Support.",
draft-ietf-mip6-radius-01.txt (work in progress), draft-ietf-mip6-radius-02.txt (work in progress),
October 2006. March 2007.
[RFC1035] Mockapetris, P., "Domain names - implementation and [RFC1035] Mockapetris, P., "Domain names - implementation and
specification", STD 13, RFC 1035, November 1987. specification", STD 13, RFC 1035, November 1987.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson,
"Remote Authentication Dial In User Service (RADIUS)", "Remote Authentication Dial In User Service (RADIUS)",
RFC 2865, June 2000. RFC 2865, June 2000.
skipping to change at page 17, line 13 skipping to change at page 18, line 5
August 2005. August 2005.
[RFC4030] Stapp, M. and T. Lemon, "The Authentication Suboption for [RFC4030] Stapp, M. and T. Lemon, "The Authentication Suboption for
the Dynamic Host Configuration Protocol (DHCP) Relay Agent the Dynamic Host Configuration Protocol (DHCP) Relay Agent
Option", RFC 4030, March 2005. Option", RFC 4030, March 2005.
[RFC4640] Patel, A. and G. Giaretta, "Problem Statement for [RFC4640] Patel, A. and G. Giaretta, "Problem Statement for
bootstrapping Mobile IPv6 (MIPv6)", RFC 4640, bootstrapping Mobile IPv6 (MIPv6)", RFC 4640,
September 2006. September 2006.
8.2. Informative References
[BOOT-SPLIT]
Giaretta et. al., A., "Mobile IPv6 bootstrapping in split
scenario.", draft-ietf-mip6-bootstrapping-split-04.txt
(work in progress), December 2006.
Authors' Addresses Authors' Addresses
Kuntal Chowdhury Kuntal Chowdhury
Starent Networks Starent Networks
30 International Place 30 International Place
Tewksbury, MA 01876 Tewksbury, MA 01876
US US
Phone: +1 214-550-1416 Phone: +1 214-550-1416
Email: kchowdhury@starentnetworks.com Email: kchowdhury@starentnetworks.com
 End of changes. 34 change blocks. 
115 lines changed or deleted 93 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/