draft-ietf-mip6-bootstrapping-integrated-dhc-03.txt   draft-ietf-mip6-bootstrapping-integrated-dhc-04.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: October 21, 2007 Samsung AIT Expires: December 3, 2007 Samsung AIT
April 19, 2007 June 1, 2007
MIP6-bootstrapping for the Integrated Scenario MIP6-bootstrapping for the Integrated Scenario
draft-ietf-mip6-bootstrapping-integrated-03.txt draft-ietf-mip6-bootstrapping-integrated-04.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 October 21, 2007. This Internet-Draft will expire on December 3, 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 Mobile IPv6 bootstrapping can be categorized into two primary
scenarios. In the first scenario (i.e. the split scenario), the scenarios, the split scenario and the integrated scenario. In the
mobile node's mobility service is authorized by a different service split scenario, the mobile node's mobility service is authorized by a
authorizer than the basic network access authorizer. In the second different service authorizer than the network access authorizer. In
scenario (i.e. the integrated scenario), the mobile node's mobility the the integrated scenario, the mobile node's mobility service is
service is authorized by the same service authorizer as the basic authorized by the same service authorizer as the network access
network access service authorizer. This document defines a method service authorizer. This document defines a method for home agent
for home agent information discovery for the integrated scenario. 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. List of Assumptions . . . . . . . . . . . . . . . . . . . . . 5 3. Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Solution Overview . . . . . . . . . . . . . . . . . . . . . . 6 4. Solution Overview . . . . . . . . . . . . . . . . . . . . . . 6
4.1. Logical Diagram of the Integrated Scenario . . . . . . . . 6 4.1. Logical View of the Integrated Scenario . . . . . . . . . 6
4.2. Bootstrapping Message Sequence, Success Case . . . . . . . 7 4.2. Bootstrapping Message Sequence . . . . . . . . . . . . . . 7
4.2.1. Home Agent allocation in the MSP . . . . . . . . . . . 7 4.2.1. Home Agent allocation in the MSP . . . . . . . . . . . 7
4.2.2. Home Agent allocation in the ASP . . . . . . . . . . . 9 4.2.2. Home Agent allocation in the ASP . . . . . . . . . . . 9
4.3. Bootstrapping Message Sequence: Fallback case . . . . . . 11 4.3. Bootstrapping Message Sequence: Fallback case . . . . . . 11
4.4. HoA and IKEv2 SA Bootstrapping in the Integrated 4.4. HoA and IKEv2 SA Bootstrapping in the Integrated
Scenario . . . . . . . . . . . . . . . . . . . . . . . . . 11 Scenario . . . . . . . . . . . . . . . . . . . . . . . . . 11
5. Security Considerations . . . . . . . . . . . . . . . . . . . 12 5. Security Considerations . . . . . . . . . . . . . . . . . . . 12
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 15 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 15
9. Normative References . . . . . . . . . . . . . . . . . . . . . 16 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18 9.1. Normative References . . . . . . . . . . . . . . . . . . . 16
Intellectual Property and Copyright Statements . . . . . . . . . . 19 9.2. Informative References . . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17
Intellectual Property and Copyright Statements . . . . . . . . . . 18
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 information 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 initiating the registration
registration. The mechanism via which the mobile node obtains these process. The mechanism via which the mobile node obtains these
information is called Mobile IPv6 bootstrapping. In order to allow a information is called Mobile IPv6 bootstrapping. In order to allow a
flexible deployment model for Mobile IPv6, it is desirable to define flexible deployment model for Mobile IPv6, it is desirable to define
a bootstrapping mechanism for the mobile node to acquire these a bootstrapping mechanism for the mobile node to acquire these
parameters dynamically. The [RFC4640] describes the problem parameters dynamically. [RFC4640] describes the problem statement
statement for Mobile IPv6 bootstrapping. It also defines two for Mobile IPv6 bootstrapping. It also defines two bootstrapping
bootstrapping scenarios based on the relationship between the entity scenarios based on the relationship between the entity that
that authenticates and authorizes the mobile node for network access authenticates and authorizes the mobile node for network access
(i.e., the Access Service Authorizer) and the entity that (i.e., the Access Service Authorizer) and the entity that
authenticates and authorizes the mobile node for mobility service authenticates and authorizes the mobile node for mobility service
(i.e., the Mobility Service Authorizer). The scenario in which the (i.e., the Mobility Service Authorizer). The scenario in which the
Access Service Authorizer is not the Mobility Service Authorizer is Access Service Authorizer is not the Mobility Service Authorizer is
called the "Split" scenario. The bootstrapping solution for split called the "Split" scenario. The bootstrapping solution for split
scenario is defined in [BOOT-SPLIT]. The scenario in which the scenario is defined in [BOOT-SPLIT]. The scenario in which the
Access Service Authorizer is also the Mobility Service Authorizer is Access Service Authorizer is also the Mobility Service Authorizer is
called the "Integrated" scenario. This document defines a called the "Integrated" scenario. This document defines a
bootstrapping solution for the Integrated scenario. bootstrapping solution for the Integrated scenario.
[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. The other components of bootstrapping are as per
[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 achieved via DHCPv6. This document defines the
configuration management and it is being deployed by operators to mip6 bootstrapping procedures for the integrated scenario. It
handle their configuration management needs in their networks. This enables Home Agent assignment in the integrated scenario by utilizing
document defines the mip6 bootstrapping procedures for the integrated DHCP and AAA protocols. The specification utilizes DHCP and AAA
scenario. This draft enables Home Agent assignment in the integrated options and AVPs that are defined in [HIOPT], [MIP6-Dime], and
scenario by utilizing DHCP and AAA protocols. The specification [MIP6-RADIUS]. This document specifies the interworking among MN,
utilizes DHCP and AAA options and AVPs that are defined in [HIOPT], NAS, DHCP, and AAA entities for bootstrapping procedure in the
[MIP6-Dime], and [MIP6-RADIUS]. This document specifies the integrated scenario.
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 RFC 2119.
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:
Access Service Authorizer (ASA): A network operator that Access Service Authorizer (ASA): A network operator that
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
skipping to change at page 5, line 5 skipping to change at page 5, line 5
Mobile IPv6 service. A MSP is called home MSP when MSP == MSA. In Mobile IPv6 service. A MSP is called home MSP when MSP == MSA. In
this document the term MSP means a Mobility Service Provider that has this document the term MSP means a Mobility Service Provider that has
roaming relationship with the MSA but it is not the MSA. 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. List of Assumptions 3. Assumptions
The following assumptions are made in this document: The following assumptions are made in this document:
a. MSA == ASA. a. MSA == ASA.
b. MSA and MSP roaming relationship is assumed but not required. 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 c. DHCP relay and NAS are collocated or there is a mechanism to pass
received AAA information from the NAS to the DHCP relay. received AAA information from the NAS to the DHCP relay.
d. the NAS shall support MIPv6 specific AAA attributes as specified d. the NAS shall support MIPv6 specific AAA attributes as specified
in [MIP6-RADIUS] and [MIP6-Dime]. in [MIP6-RADIUS] and [MIP6-Dime].
e. MSP == MSA scenario is termed as home MSP. e. The AAAH used for network access authentication (ASA) has access
to the same database as the AAAH used for the mobility service
authentication (MSA).
4. Solution Overview 4. Solution Overview
4.1. Logical Diagram of the Integrated Scenario 4.1. Logical View 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 7, line 20 skipping to change at page 7, line 20
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.
4.2. Bootstrapping Message Sequence, Success Case 4.2. Bootstrapping Message Sequence
In the success case, the mobile node is able to acquire the home In this case, the mobile node is able to acquire the home agent
agent address via a DHCPv6 query. The message flows for home 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. In the
the integrated scenario, the ASA and the MSA are the same, it can be 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. When the MN performs Mobile IPv6 registration (IKEv2 the same time. When the MN performs Mobile IPv6 registration, the
exchanges), the AAAH ensures that the MN is accessing the assigned AAAH ensures that the MN is accessing the assigned Home Agent for
Home Agent for that MSP. that MSP.
4.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 MSP network(s). 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].
| |
skipping to change at page 8, line 40 skipping to change at page 8, line 40
| | | | | | | |
Home Agent in the MSP Home Agent in the MSP
Figure 2. The home agent allocation in the 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
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 it interacts with the NAS.
NAS. The NAS is in the ASP and it interacts with the AAAH, which is The NAS is in the ASP and it interacts with the AAAH, which is in the
in the ASA/MSA, to authenticate the mobile node. In the process of 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 home agent in the home MSP and other authorized MSPs and assigns home agent in the home MSP and other authorized MSPs and
returns this information to the NAS. The NAS may keep the received returns this information to the NAS. The NAS may keep the received
information for a configurable duration or it may keep the information for a configurable duration or it may keep the
information for as long as the MN is connected to the NAS. 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.
skipping to change at page 9, line 41 skipping to change at page 9, line 41
the behavior described in [HIOPT]. 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.
4.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 [HIOPT] in the DHCPv6 request
In this scenario, the ASP becomes the MSP for the duration of the message. In this scenario, the ASP becomes the MSP for the duration
network access authentication session. of the network access authentication session.
| |
--------------ASP-------->|<--ASA+MSA-- --------------ASP-------->|<--ASA+MSA--
| |
+----+ +-------+ +-------+ +------+ +----+ +-------+ +-------+ +------+
| | | | | | | | | | | | | | | |
| MN/| | NAS/ | | DHCP | |AAAH | | MN/| | NAS/ | | DHCP | |AAAH |
|User| | DHCP | | Server| | | |User| | DHCP | | Server| | |
| | | relay | | Server| | | | | | relay | | Server| | |
+----+ +-------+ +-------+ +------+ +----+ +-------+ +-------+ +------+
skipping to change at page 10, line 40 skipping to change at page 10, line 40
| | | | | | | |
Home Agent in the ASP Home Agent in the ASP
Figure 3. The home agent allocation in the ASP Figure 3. The home agent allocation in the ASP
Figure 3 shows the message sequence for home agent allocation in the Figure 3 shows the message sequence for home agent allocation in the
ASP. ASP.
(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 it interacts with the NAS.
NAS. The NAS is in the ASP and it interacts with the AAAH, which is The NAS is in the ASP and it interacts with the AAAH, which is in the
in the ASA/MSA, to authenticate the mobile node. In the process of 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 services. The AAAH the mobile node is allowed to use Mobile IPv6 services. The AAAH
assigns a home agent in the home MSP and returns this information to assigns a home agent in the home MSP and returns this information to
the NAS. Note that the AAAH is not aware of the fact that the mobile the NAS. Note that the AAAH is not aware of the fact that the mobile
node will rather request for a home agent allocation in the ASP. node prefers a home agent allocation in the ASP. Therefore the
Therefore the assigned home agent may not be used by the mobile node. assigned home agent may not be used by the mobile node. This leaves
This leaves the location of the mobility anchor point decision to the the location of the mobility anchor point decision to the mobile
mobile node. node.
(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 0. OPTION_ORO, Home Network Identifier Option with id-type set to 0.
The mobile node SHALL also include the OPTION_CLIENTID to identify The mobile node SHALL also include the OPTION_CLIENTID to identify
itself to the DHCP server. 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
skipping to change at page 11, line 38 skipping to change at page 11, line 38
(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.
4.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. The details of how the MN
the DNS server address is outside the scope of this document. is configured with the DNS server address is outside the scope of
this document.
4.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].
5. 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 may only be integrity protected as per standard RADIUS and NAS may only be integrity protected as per standard RADIUS and
Diameter security mechanisms. No additional security considerations Diameter security mechanisms. No additional security considerations
are imposed by the usage of this document. The security mechanisms are imposed by the usage of this document. The security mechanisms
provided by [RFC2865] and [RFC3588] are applicable for this purpose. provided by [RFC2865] and [RFC3588] are applicable for this purpose.
This document does not introduce any new security issues to Mobile
IPv6.
6. IANA Considerations 6. IANA Considerations
None None
7. Acknowledgements 7. Acknowledgements
The authors would like to thank Kilian Weniger, Vidya Narayanan, and The authors would like to thank Kilian Weniger, Vidya Narayanan, and
George Tsirtsis for their review and comments. George Tsirtsis for their review and comments.
8. 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 gerardog@qualcomm.com
Basavaraj Patil basavaraj.patil@nokia.com Basavaraj Patil basavaraj.patil@nsn.com
Alpesh Patel alpesh@cisco.com Alpesh Patel alpesh@cisco.com
Jari Arkko jari.arkko@kolumbus.fi Jari Arkko jari.arkko@kolumbus.fi
James Kempf kempf@docomolabs-usa.com James Kempf kempf@docomolabs-usa.com
Gopal Dommety gdommety@cisco.com Gopal Dommety gdommety@cisco.com
Alper Yegin alper.yegin@samsung.com Alper Yegin a.yegin@partner.samsung.com
Junghoon Jee jhjee@etri.re.kr Junghoon Jee jhjee@etri.re.kr
Vijay Devarapalli vijayd@iprg.nokia.com Vijay Devarapalli Vijay.Devarapalli@AzaireNet.com
Kuntal Chowdhury kchowdhury@starentnetworks.com Kuntal Chowdhury kchowdhury@starentnetworks.com
Julien Bournelle julien.bournelle@int-evry.fr Julien Bournelle julien.bournelle@orange-ftgroup.com
Hannes Tschofenig hannes.tschofenig@siemens.com Hannes Tschofenig hannes.tschofenig@nsn.com
9. Normative References 9. References
9.1. Normative References
[BOOT-SPLIT] [BOOT-SPLIT]
Giaretta et. al., A., "Mobile IPv6 bootstrapping in split Giaretta et. al., A., "Mobile IPv6 bootstrapping in split
scenario.", draft-ietf-mip6-bootstrapping-split-04.txt scenario.", draft-ietf-mip6-bootstrapping-split-05.txt
(work in progress), December 2006. (work in progress), May 2007.
[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-02.txt (work Discovery in MIPv6.", draft-ietf-mip6-hiopt-03.txt (work
in progress), February 2007. in progress), May 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-03.txt (work in Support.", draft-ietf-dime-mip6-integrated-04.txt (work in
progress), February 2007. progress), May 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-02.txt (work in progress), draft-ietf-mip6-radius-02.txt (work in progress),
March 2007. March 2007.
[RFC1035] Mockapetris, P., "Domain names - implementation and
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.
[RFC3118] Droms, R. and W. Arbaugh, "Authentication for DHCP
Messages", RFC 3118, June 2001.
[RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C.,
and M. Carney, "Dynamic Host Configuration Protocol for and M. Carney, "Dynamic Host Configuration Protocol for
IPv6 (DHCPv6)", RFC 3315, July 2003. IPv6 (DHCPv6)", RFC 3315, July 2003.
[RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. [RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J.
Arkko, "Diameter Base Protocol", RFC 3588, September 2003. Arkko, "Diameter Base Protocol", RFC 3588, September 2003.
[RFC3753] Manner, J. and M. Kojo, "Mobility Related Terminology",
RFC 3753, June 2004.
[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.
[RFC4005] Calhoun, P., Zorn, G., Spence, D., and D. Mitton, 9.2. Informative References
"Diameter Network Access Server Application", RFC 4005,
August 2005.
[RFC4030] Stapp, M. and T. Lemon, "The Authentication Suboption for [RFC3753] Manner, J. and M. Kojo, "Mobility Related Terminology",
the Dynamic Host Configuration Protocol (DHCP) Relay Agent RFC 3753, June 2004.
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.
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
Email: kchowdhury@starentnetworks.com Email: kchowdhury@starentnetworks.com
Alper Yegin Alper Yegin
Samsung AIT Samsung AIT
Istanbul, Istanbul,
Turkey Turkey
Email: a.yegin@partner.samsung.com
Phone:
Email: alper01.yegin@partner.samsung.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
 End of changes. 43 change blocks. 
97 lines changed or deleted 88 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/