draft-ietf-mip6-bootstrapping-integrated-dhc-04.txt   draft-ietf-mip6-bootstrapping-integrated-dhc-05.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: December 3, 2007 Samsung AIT Expires: December 22, 2007 Samsung AIT
June 1, 2007 June 20, 2007
MIP6-bootstrapping for the Integrated Scenario MIP6-bootstrapping for the Integrated Scenario
draft-ietf-mip6-bootstrapping-integrated-04.txt draft-ietf-mip6-bootstrapping-integrated-05.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 December 3, 2007. This Internet-Draft will expire on December 22, 2007.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
Mobile IPv6 bootstrapping can be categorized into two primary Mobile IPv6 bootstrapping can be categorized into two primary
scenarios, the split scenario and the integrated scenario. In the scenarios, the split scenario and the integrated scenario. In the
split scenario, the mobile node's mobility service is authorized by a split scenario, the mobile node's mobility service is authorized by a
different service authorizer than the network access authorizer. In different service authorizer than the network access authorizer. In
the the integrated scenario, the mobile node's mobility service is the the integrated scenario, the mobile node's mobility service is
authorized by the same service authorizer as the network access authorized by the same service authorizer as the network access
service authorizer. This document defines a method for home agent service authorizer. This document defines a method 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. Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Assumptions & Conformance . . . . . . . . . . . . . . . . . . 5
4. Solution Overview . . . . . . . . . . . . . . . . . . . . . . 6 4. Solution Overview . . . . . . . . . . . . . . . . . . . . . . 6
4.1. Logical View of the Integrated Scenario . . . . . . . . . 6 4.1. Logical View of the Integrated Scenario . . . . . . . . . 6
4.2. Bootstrapping Message Sequence . . . . . . . . . . . . . . 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
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. Assumptions 3. Assumptions & Conformance
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 mechanism to pass c. DHCP relay and NAS are collocated or there is a mechanism to
received AAA information from the NAS to the DHCP relay. transfer received AAA information from the NAS to the DHCP relay.
Note: if assignment of home agent in the home MSP is not required by
a deployment, collocation of the NAS and the DHCP relay functions or
a mechanism to transfer received AAA information from the NAS to the
DHCP relay won't be necessary. In such a case, only the
implementation of the options and procedures defined in [HIOPT]
should suffice.
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. The AAAH used for network access authentication (ASA) has access e. The AAAH used for network access authentication (ASA) has access
to the same database as the AAAH used for the mobility service to the same database as the AAAH used for the mobility service
authentication (MSA). authentication (MSA).
If home agent assignment only in the ASP is required by the
deployment, a minimal implementation of this specification MAY only
support the delivery of information from the DHCP server to the DHCP
client through [HIOPT]. However, if home agent assignment in the MSP
is required by the deployment, the implementation conforming to this
specification SHALL be able to transfer received information (from
the AAA server) from the NAS to the DHCP relay function. This can be
achieved either by collocating the NAS and the DHCP relay functions
or via an interface between these functions. The detail of this
interface is out of scope of this specification.
4. Solution Overview 4. Solution Overview
4.1. Logical View 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
skipping to change at page 17, line 12 skipping to change at page 17, line 12
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
Phone:
Email: a.yegin@partner.samsung.com Email: a.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.
 End of changes. 9 change blocks. 
8 lines changed or deleted 30 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/