[Search] [txt|pdf|bibtex] [Tracker] [Email] [Nits]

Versions: 00                                                            
Network Working Group                                          Seil Jeon
Internet-Draft                                              Younghan Kim
Intended status: Standards Track                              Jiwon Jang
Expires: April 18, 2011                       Soongsil University, Korea
                                                            October 2010




        Network Mobility Support in the Proxy Mobile IPv6 Domain
                  draft-sijeon-mext-nemo-pmip6-00.txt

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time. It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on February 8, 2011.

Copyright Notice

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



Jeon, et al.             Expires April 18, 2011                 [Page 1]


Internet-Draft      NEMO Support in the PMIPv6 Domain       October 2010


   (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.  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.




































Jeon, et al.             Expires April 18, 2011                 [Page 2]


Internet-Draft      NEMO Support in the PMIPv6 Domain       October 2010


Abstract

   Network mobility (NEMO) enables all the nodes within a mobile network
   to provide session continuity without requiring their involvement
   when the mobile network moves. To provide NEMO support, the NEMO
   basic support protocol (NEMO-BSP) is specified in [RFC 3963].

   With the advances of the network-based mobility management protocol
   referred to as Proxy Mobile IPv6 (PMIPv6), interest in applicable
   NEMO support in the PMIPv6 domain is increasing however, the standard
   PMIPv6, defined in [RFC 5213], handles only a single mobile node.

   This document presents a NEMO-enabled PMIPv6 using a Proxy Router
   (PR) rather than the MR defined in [RFC 3963] and describes detailed
   operations for network/node mobility support in the PMIPv6 domain.


Table of Contents

   1. Introduction.....................................................4
   2. Terminology and Functional Components............................5
   3. Protocol Operation...............................................6
     3.1. PR's Attachment..............................................6
     3.2. MNN's Attachment.............................................7
     3.3. PR's Handoff from P-MAG to N-MAG.............................9
     3.4. MNN's Handoff from the PR to the outer PMIPv6 domain........10
   4. Binding Entry Information.......................................12
     4.1. Extended Proxy Binding Update List in MAG...................12
     4.2. Extended Binding Cache Entry in LMA.........................12
   5. IANA Considerations.............................................13
   6. Security Considerations.........................................13
   7. References......................................................13
     7.1. Normative References........................................13
     7.2. Informative References......................................14
   Author's Address...................................................15










Jeon, et al.             Expires April 18, 2011                 [Page 3]


Internet-Draft      NEMO Support in the PMIPv6 Domain       October 2010


1. Introduction

   Network mobility (NEMO) is a novel concept for handling a group of
   nodes within a moving vehicular area. The recent rapid propagation of
   Wi-Fi handheld devices and increasing demand for Internet access
   everywhere have made NEMO technology much noticeable. To enable
   support for NEMO, the NEMO basic support protocol (NEMO-BSP) is
   specified in [RFC 3963].

   The NEMO-BSP employs the Mobile Router (MR), which connects a mobile
   network node (MNN) and access router (AR) and has the functionality
   of host-based Mobile IPv6 (MIPv6) [RFC 3775] client protocol. Due to
   the host-based features, the MIPv6 has essential performance issues
   (e.g., handover latency, inefficient packet delivery, multiple
   tunneling overhead). To resolve the performance issues found in
   MIPv6, the network-based Proxy Mobile IPv6 (PMIPv6) has been proposed
   [RFC 5213]. The PMIPv6 provides improved performance to mobile nodes
   (MNs), but current specification handles only a single MN.

   In order to deploy the NEMO in the PMIPv6 domain, [PROB-STAT]
   presents a problem statement and applicability of NEMO-BSP. [NEMO-BS-
   PMIPv6] describes PMIPv6-NEMO scenarios and operations when MR is
   based on Mobile IPv6 protocol. [NESTED-NEMO] presents a nested NEMO
   case, and [NEMO-BSP-PMIPv6] presents several scenarios for applying
   NEMO-BSP to the PMIPv6 domain.

   We present a NEMO-enabled PMIPv6 using a Proxy Router (PR) than the
   MR defined in [RFC 3963]. Within the context of this document, the
   PR, which is located between the MNN and mobile access gateway (MAG),
   has no mobility function. It detects the MNN's movement and delivers
   corresponding information to a MAG on behalf of MNNs within its
   coverage.

   The PR and MNNs within a specified mobile network are managed with
   the same group ID by the local mobility anchor (LMA). When a PR moves
   to another MAG, the LMA then changes the binding cache entries for
   the PR and MNNs at the same time. This feature enables all the nodes
   within mobile network to provide session continuity without the MNNs'
   involvement.

   All the information in the MNNs is managed by the MAG as well as the
   LMA. As a result, when an LMA delivers packets to an MNN, no



Jeon, et al.             Expires April 18, 2011                 [Page 4]


Internet-Draft      NEMO Support in the PMIPv6 Domain       October 2010


   additional tunnel is used except for the PMIPv6 tunnel between the
   MAG and the LMA.

   The remainder of this document describes detailed operations for
   network/node mobility in the PMIPv6 domain.


2. Terminology and Functional Components

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119]

   o  Mobile Network Node (MNN) - The node that has an address
      containing the MNP, as defined in [RFC 3963].

   o  Mobile Router (MR) - It is extended from Mobile IPv6 client
      protocol and in charge of mobility management on behalf of MNN
      within a mobile network, as defined in [RFC 3963].

   o  Proxy Router (PR) - It detects the MNN's movement and delivers the
      information to the MAG behalf of MNNs within its coverage. It also
      emulates the MNN's home network on the access link.

   o  PR Group ID (PR-GID) - A unique ID that is assigned from LMA and
      used for efficient NEMO.



















Jeon, et al.             Expires April 18, 2011                 [Page 5]


Internet-Draft      NEMO Support in the PMIPv6 Domain       October 2010


3. Protocol Operation

3.1. PR's Attachment

           PR                MAG               AAA               LMA
            |                 |                 |                 |
            |------ L2 ------>|                 |                 |
            |     Attach      |                 |                 |
            |                 |                 |                 |
            |------ RS ------>|                 |                 |
            |     (PR-ID)     |                 |                 |
            |                 |                 |                 |
            |                 |<- AAA Req/Res ->|                 |
            |                 |                 |                 |
            |                 |--------------- PBU -------------->|
            |                 |          (PR-ID,'B','N')          |
            |                 |                 |                 |
            |                 |                 |      Create the group
            |                 |                 |      (PR-GID) for PR
            |                 |                 |                 |
            |                 |<-------------- PBA ---------------|
            |                 |   (PR-ID,'B','N',PR-HNP,PR-GID)   |
            |                 |                 |                 |
            |           Store the group         |                 |
            |           info. (PR-GID)          |                 |
            |                 |                 |                 |
            |<----- RA -------|                 |                 |
            |    (PR-HNP)     |                 |                 |
            |                 |                 |                 |

                 Figure 1. PR Attachment to the PMIPv6 Domain

   When a PR approaches the PMIPv6 domain, this event is detected by the
   MAG. The MAG then sends a proxy binding update (PBU) message
   containing 'B' and 'N' flags set to 1 toward the LMA. The 'B' flag,
   which is derived from the bulk re-registration mechanism [BULK-REG],
   requests the allocation of a group ID (GID) and reduces the excessive
   signaling cost required to extend the binding lifetime of individual
   mobile hosts. To the 'B' flag, we add an 'N' flag, which is defined
   in this document, to denote that this node is not an ordinary mobile
   host but a proxy router. This information can be obtained from the
   security association between the MAG and the AAA.



Jeon, et al.             Expires April 18, 2011                 [Page 6]


Internet-Draft      NEMO Support in the PMIPv6 Domain       October 2010


3.2. MNN's Attachment

      MNN           PR                MAG           AAA           LMA
       |             |                 |             |             |
       |---- L2 ---->|                 |             |             |
       |   Attach    |                 |             |             |
       |             |                 |             |             |
       |---- RS ---->|                 |             |             |
       |  (MNN-ID)   |                 |             |             |
       |             |------ RS ------>|             |             |
       |             |  ('P', MNN-ID)  |             |             |
       |             |                 |             |             |
       |             |                 |<--- AAA --->|             |
       |             |                 |   Req/Res   |             |
       |             |                 |             |             |
       |             |                 |----------- PBU ---------->|
       |             |                 |    (MNN-ID,'B',PR-ID)     |
       |             |                 |             |             |
       |             |                 |             |    MNN is joined
       |             |                 |             |    to the PR-GID
       |             |                 |             |             |
       |             |                 |<---------- PBA -----------|
       |             |                 | (MNN-ID,'B',MN-HNP,PR-GID)|
       |             |                 |             |             |
       |             |           Store MNN's info    |             |
       |             |                 |             |             |
       |             |<----- RA -------|             |             |
       |             |  ('P',MNN-HNP)  |             |             |
       |<--- RA -----|                 |             |             |
       |  (MNN-HNP)  |                 |             |             |

          Figure 2. MNN Attachment to the PR in the Mobile Network

   When an MNN approaches the PR, it sends its MNN-ID to the PR by means
   of a router solicitation (RS) message. The PR delivers the RS message
   with a 'P' flag denoting proxy, which is defined in this document,
   set to 1. After receiving the RS message, the MAG learns that the
   attached MNN belongs to the PR by examining the 'P' flag of the
   received RS message and link-layer address of the PR. To manage the
   attached node under the PR, a PBU message sent by the MAG includes
   the MNN-ID, the PR-ID of the attached PR, and a 'B' flag set to 1.
   The LMA allocates the home network prefix (HNP) for the MNN and



Jeon, et al.             Expires April 18, 2011                 [Page 7]


Internet-Draft      NEMO Support in the PMIPv6 Domain       October 2010


   groups the MNN around the group ID of the PR (PR-GID). After
   receiving the PBA message, the MAG also adds the MNN to the PR-GID.
   The allocated HNP is delivered to the PR through a router
   advertisement (RA) message with a 'P' flag set to 1. Then, the RA
   message with a 'P' flag set to 0 is finally delivered to the MNN.

   When LMA receives the packets that are destined for the MNN from a
   CN, it looks up the corresponding MAG IP address to which the MNN
   belongs in BCE. Next, the packets, combined with only the PMIPv6
   tunnel header, are sent to the MAG. When the MAG sends packets to the
   MNN via the PR, no tunnel is used because MAG knows the next hop
   address to deliver packets toward the MNN.

































Jeon, et al.             Expires April 18, 2011                 [Page 8]


Internet-Draft      NEMO Support in the PMIPv6 Domain       October 2010


3.3. PR's Handoff from P-MAG to N-MAG

      MNN         PR         P-MAG       N-MAG        AAA         LMA
       |           |           |           |           |           |
       |           |     Detection of      |           |           |
       |           |     PR's movement     |           |           |
       |           |           |           |           |           |
       |           |           |----- PBU (PR-ID, Lifetime=0) ---->|
       |           |           |           |           |           |
       |           |           |<---- PBA (PR-ID, Lifetime=0) -----|
       |           |           |           |           |           |
       |        Handoff        |           |           |           |
       |           |           |           |           |           |
       |           |------ L2 Attach ----->|           |           |
       |           |           |           |           |           |
       |           |------ RS (PR-ID) ---->|           |           |
       |           |           |           |           |           |
       |           |           |           |<--- AAA Req/Res ----->|
       |           |           |           |           |           |
       |           |           |           |--------- PBU -------->|
       |           |           |           |   (PR-ID, 'B', 'N')   |
       |           |           |           |           |           |
       |           |           |           |<-------- PBA ---------|
       |           |           |           | (PR-ID,'B','N',PR-HNP,|
       |           |           |           |PR-GID,MNN-IDs,MNN-HNPs)
       |           |           |           |           |           |
       |           |<-------- RA ----------|           |           |
       |           |  (PR-HNP, MNN-HNPs)   |           |           |
       |           |           |           |           |           |

          Figure 3. PR's Handover operation from MAG_A to MAG_B

   When the PR moves to the next MAG (N-MAG) from the previous MAG (P-
   MAG), the P-MAG detects the PR's movement from a layer-2 event and
   then initiates a de-registration process for the PR. The N-MAG, which
   detects a PR's attachment, sends a PBU message for registration. The
   LMA receives the PBU message, finds that this node is the proxy
   router from the 'N' flag, and verifies that there exists the PR-GID
   for the corresponding PR in BCE. If the LMA has the PR-GID, it sends
   the PBA message, including the MNN-IDs and MNN-HNPs as well as PR-HNP
   and PR-GID, because the N-MAG has no information about the MNNs that
   belong to the PR.



Jeon, et al.             Expires April 18, 2011                 [Page 9]


Internet-Draft      NEMO Support in the PMIPv6 Domain       October 2010


3.4. MNN's Handoff from the PR to the outer PMIPv6 Domain

      MNN           PR               MAG             AAA         LMA
       |             |                |               |           |
       |       Detection of           |               |           |
       |       MNN's movement         |               |           |
       |             |                |               |           |
       |             |------ RS ----->|               |           |
       |             |('P','D',MNN-ID)|               |           |
       |             |                |               |           |
       |             |                |----------- PBU ---------->|
       |             |                |    (MNN-ID, Lifetime=0)   |
       |             |                |               |           |
       |             |                |               |  Remove the MNN
       |             |                |               |  from the group
       |             |                |               |  to which the PR
       |             |                |               |  belongs  |
       |             |                |               |           |
       |             |                |<---------- PBA -----------|
       |             |                |    (MNN-ID, Lifetime=0)   |
       |             |                |               |           |
       |             |          Remove the MNN        |           |
       |             |     from the group to which    |           |
       |             |         the PR belongs         |           |
       |             |                |               |           |
       |---------- L2 Attach -------->|               |           |
       |             |                |               |           |
       |             |                |<-AAA Req/Res->|           |
       |             |                |               |           |
       |             |                |------ PBU (MNN-ID) ------>|
       |             |                |               |           |
       |             |                |<-- PBA (MNN-ID,MNN-HNP) --|
       |             |                |               |           |
       |<-- ------- RA ---------------|               |           |
       |         (MNN-HNP)            |               |           |

   When an MNN moves out from a mobile network, the PR detects the MNN's
   detachment from a layer-2 signal and then sends an RS message to the
   current MAG. This RS message includes 'P' and 'D' flags set to 1 and
   MNN-ID. The 'D' flag, which is defined in this document, to announce
   MNN's movement to the MAG. When the MAG receives the RS message with
   'P' and 'D' flags set to 1, it determines that the corresponding MNN-



Jeon, et al.             Expires April 18, 2011                [Page 10]


Internet-Draft      NEMO Support in the PMIPv6 Domain       October 2010


   ID in received RS message moved out from the PR, and it sends a PBU
   message for de-registration to the LMA defined in [RFC 5213]. The LMA
   performs de-registration and removes the MNN from the group to which
   the PR belongs; then, it sends a PBA message to the MAG. When the MAG
   receives the PBA message from the LMA, it also removes the MNN from
   the group to which the PR belongs and MNN-related entry information
   in the proxy binding update list (PBUL). When the MNN approaches the
   MAG, the MAG detects the node's movement and performs the node
   attachment procedure defined in [RFC 5213].




































Jeon, et al.             Expires April 18, 2011                [Page 11]


Internet-Draft      NEMO Support in the PMIPv6 Domain       October 2010


4. Binding Entry Information

4.1. Extended Proxy Binding Update List in MAG

        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        |   ID   |    HNP     |      PR       |    GID    |   LMA   |
        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        |   PR   | Pref1::/64 |               |  PR-GID1  |  LMA A  |
        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        |  MNN   | Pref2::/64 |  Pref1::/64   |  PR-GID1  |  LMA A  |
        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        |   MN   | Pref3::/64 |               |           |  LMA A  |
        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

4.2. Extended Binding Cache Entry in LMA

        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        |   ID   |    HNP     |      PR       |    GID    |   MAG   |
        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        |   PR   | Pref1::/64 |               |  PR-GID1  |  MAG_A  |
        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        |  MNN   | Pref2::/64 |  Pref1::/64   |  PR-GID1  |  MAG_A  |
        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        |   MN   | Pref3::/64 |               |           |  MAG_A  |
        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+




















Jeon, et al.             Expires April 18, 2011                [Page 12]


Internet-Draft      NEMO Support in the PMIPv6 Domain       October 2010


5. IANA Considerations

   TBD.


6. Security Considerations

   TBD.


7. References

7.1. Normative References

   [RFC 3963]
              V. Devarapalli, R.Wakikawa, A. Petrescu, and P. Thubert,
              "Network Mobility (NEMO) Basic Support Protocol," IETF RFC
              3963, January, 2005.

   [RFC 3775]
              D. Johnson, C. Perkins, and J. Arkko, "Mobility support in
              IPv6," IETF RFC 3775, June 2004.

   [RFC 5213]
              S. Gundavelli, K. Leung, V. Devarapalli, K. Chowdhury, and
              B. Patil, "Proxy Mobile IPv6," IETF RFC 5213, August 2008.

   [PROB-STAT]
              CJ. Bernardos, M. Calderon, and I. Soto, "PMIPv6 and
              Network Mobility Problem Statement," draft-bernardos-
              netext-pmipv6-nemo-ps-01.txt, October 2009.














Jeon, et al.             Expires April 18, 2011                [Page 13]


Internet-Draft      NEMO Support in the PMIPv6 Domain       October 2010


7.2. Informative References

   [NESTED-NEMO]
              H. Zhang et al., "Consideration of Network Mobility in
              PMIPv6," draft-zhang-netlmm-nemo-01.txt, (work in
              progress), March 2010.

   [NEMO-BSP-PMIPv6]
              J. -H. Lee et al., "Network Mobility Basic Support within
              Proxy Mobile IPv6: scenarios and analysis," draft-jhlee-
              netlmm-nemo-scenarios-01.txt, (work in progress),
              September 2008.

   [BULK-REG]
              F. Abinader et al., "Bulk Re-registration for Proxy Mobile
              IPv6," draft-ietf-netext-bulk-re-registration-01.txt,
              (work in progress), July 2010.




























Jeon, et al.             Expires April 18, 2011                [Page 14]


Internet-Draft      NEMO Support in the PMIPv6 Domain       October 2010


Author's Addresses

   Seil Jeon
   Soongsil University
   4F Hyungnam Engineering Bldg. 424,
   (156-743) 511 Sangdo-Dong, Dongjak-Gu, Seoul, Korea
   Phone: +82-2-820-0841
   E-mail: sijeon@dcn.ssu.ac.kr

   Younghan Kim
   Soongsil University
   11F Hyungnam Engineering Bldg. 1107,
   (156-743) 511 Sangdo-Dong, Donajak-Gu, Seoul, Korea
   Phone: +82-2-820-0904
   E-mail: younghak@ssu.ac.kr

   Jiwon Jang
   Soongsil University
   4F Hyungnam Engineering Bldg. 424,
   (156-743) 511 Sangdo-Dong, Dongjak-Gu, Seoul, Korea
   Phone: +82-2-820-0841
   E-mail: jwjang84@dcn.ssu.ac.kr























Jeon, et al.             Expires April 18, 2011                [Page 15]