Mobile IPv6 (MIPv6) Bootstrapping for the Integrated Scenario
RFC 6611

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 06

Internet Engineering Task Force (IETF)                 K. Chowdhury, Ed.
Request for Comments: 6611                     Radio Mobile Access, Inc.
Category: Standards Track                                       A. Yegin
ISSN: 2070-1721                                                  Samsung
                                                                May 2012

     Mobile IPv6 (MIPv6) Bootstrapping for the Integrated Scenario

Abstract

   Mobile IPv6 bootstrapping can be categorized into two primary
   scenarios: the split scenario and the integrated scenario.  In the
   split scenario, the mobile node's mobility service is authorized by a
   different service authorizer than the network access authorizer.  In
   the integrated scenario, the mobile node's mobility service is
   authorized by the same service authorizer as the network access
   service authorizer.  This document defines a method for home agent
   information discovery for the integrated scenario.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc6611.

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Chowdhury & Yegin            Standards Track                    [Page 1]
RFC 6611         MIPv6 Bootstrapping Integrated Scenario        May 2012

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1. Introduction and Scope ..........................................2
   2. Terminology .....................................................3
   3. Assumptions and Conformance .....................................4
   4. Solution Overview ...............................................5
      4.1. Logical View of the Integrated Scenario ....................5
      4.2. Bootstrapping Message Sequence .............................6
           4.2.1. Home Agent Allocation in the MSP ....................7
           4.2.2. Home Agent Allocation in the ASP ....................9
      4.3. Bootstrapping Message Sequence: Fallback Case .............10
      4.4. HoA and IKEv2 SA Bootstrapping in the Integrated
           Scenario ..................................................10
   5. Security Considerations ........................................10
   6. Acknowledgements ...............................................11
   7. Contributors ...................................................11
   8. References .....................................................11
      8.1. Normative References ......................................11
      8.2. Informative References ....................................12

1.  Introduction and Scope

   The Mobile IPv6 protocol [RFC6275] requires the mobile node to have
   the following information:

   o  the Home Address (HoA),

   o  the home agent address, and

   o  the cryptographic materials for establishing an IPsec security
      association with the home agent.

Chowdhury & Yegin            Standards Track                    [Page 2]
RFC 6611         MIPv6 Bootstrapping Integrated Scenario        May 2012

   The cryptographic materials need to be established prior to
   initiating the registration process.  The mechanism via which the
   mobile node obtains this information is called "Mobile IPv6