Multiple Care-of Addresses Registration
RFC 5648

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

• Versions
• 14

Network Working Group                                   R. Wakikawa, Ed.
Request for Comments: 5648                                    Toyota ITC
Category: Standards Track                                 V. Devarapalli
                                                                Wichorus
                                                             G. Tsirtsis
                                                                Qualcomm
                                                                T. Ernst
                                                                   INRIA
                                                               K. Nagami
                                                           INTEC NetCore
                                                            October 2009

                Multiple Care-of Addresses Registration

Abstract

   According to the current Mobile IPv6 specification, a mobile node may
   have several care-of addresses but only one, called the primary
   care-of address, can be registered with its home agent and the
   correspondent nodes.  However, for matters of cost, bandwidth, delay,
   etc, it is useful for the mobile node to get Internet access through
   multiple accesses simultaneously, in which case the mobile node would
   be configured with multiple active IPv6 care-of addresses.  This
   document proposes extensions to the Mobile IPv6 protocol to register
   and use multiple care-of addresses.  The extensions proposed in this
   document can be used by mobile routers using the NEMO (Network
   Mobility) Basic Support protocol as well.

Status of This Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright and License Notice

   Copyright (c) 2009 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

Wakikawa, et al.            Standards Track                     [Page 1]
RFC 5648                          MCoA                      October 2009

   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 BSD License.

Table of Contents

   1. Introduction ....................................................3
   2. Terminology .....................................................3
   3. Protocol Overview ...............................................4
   4. Mobile IPv6 Extensions .........................................10
      4.1. Binding Cache Structure and Binding Update List ...........10
      4.2. Binding Update Message ....................................10
      4.3. Binding Identifier Mobility Option ........................11
      4.4. New Status Values for Binding Acknowledgement .............13
   5. Mobile Node Operation ..........................................14
      5.1. Management of Care-of Address(es) and Binding
           Identifier(s) .............................................14
      5.2. Binding Registration ......................................15
      5.3. Bulk Registration .........................................16
      5.4. Binding De-Registration ...................................16
      5.5. Returning Home with Complete Binding
           De-Registration: Using a Single Interface .................17
           5.5.1. Using Only the Interface Attached to the
                  Home Link ..........................................17
           5.5.2. Using Only the Interface Attached to the
                  Visited Link .......................................17
      5.6. Returning Home: Simultaneous Home and Visited Link
           Operation .................................................18
           5.6.1. Problems of Simultaneous Home and Foreign
                  Attachments ........................................18
           5.6.2. Overview and Approach ..............................18
           5.6.3. Home Binding Support ...............................19
           5.6.4. Sending Packets from the Home Link .................20
           5.6.5. Leaving from the Home Link .........................20
      5.7. Receiving Binding Acknowledgement .........................21
      5.8. Receiving Binding Refresh Request .........................22
      5.9. Bootstrapping .............................................22