One document matched: draft-jaehwoon-dmm-pmipv6-00.txt

DMM Working Group                                           Jaehwoon Lee
Internet-Draft                                        Dongguk University
Intended status: Informational                             March 4, 2012
Expires: September 3, 2012


                 PMIPv6-based Distributed Mobility Management
                     draft-jaehwoon-dmm-pmipv6-00


Abstract

   This draft proposes a PMIPv6-based distributed mobility management
   by distributing the Localized Mobility Anchor (LMA) function to
   Mobile Access Gateway (MAGs). Here, the MAG that an MN firstly 
   connects to the PMIPv6 domain becomes the MN's LMA, and other MAGs 
   can find the address of the LMA of MN by using the address assigned 
   to the MN.


Status of this Memo

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

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

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

   This Internet-Draft will expire on September 3, 2012.


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
   
   
   
 Jaehwoon Lee              Expires Sep. 3, 2012                 [Page 1]

Internet-Draft              PMIPv6-based DMM               Mar. 4, 2012
  
   
   
   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.



Table of Contents


   1.  Introduction.................................................3
   2.  Conventions and Terminology..................................3
     2.1.  Conventions used in this document........................3
     2.2.  Terminology  ............................................3
   3.  Protocol Operation...........................................4
   4.  Security Considerations......................................5
   5.  IANA Considerations..........................................5
   6. References....................................................5
   Author's Address.................................................6






























Jaehwoon Lee              Expires Sep. 3, 2012                 [Page 2]

Internet-Draft              PMIPv6-based DMM               Mar. 4, 2012


1.  Introduction


   The Proxy Mobile IPv6 (PMIPv6) is considered as the network-based 
   mobility management mechanism that the access network within the 
   PMIPv6 domain supports the mobility of the mobile node (MN) on behalf
   of the MN itself [1]. In PMIPv6, the Mobile Access Gateway (MAG) is 
   defined to support the mobility of an MN. The MAG acts as the default
   gateway of the access link to which an MN is connected. Also, the 
   Localized Mobility Anchor (LMA) is defined as the Home Agent within 
   the PMIPv6 domain.

   In PMIPv6, traffic exchanged between all MNs and their corresponding 
   nodes (CNs) goes through the LMA and therefore the PMIPv6 protocol 
   has several potential problems such as a single node failure and 
   congestion due to traffic concentration [2].

   In this draft, we propose the PMIPv6 based distributed mobility 
   management by distributing LMA function to MAGs. Here, the MAG that 
   an MN firstly connects to the PMIPv6 domain becomes the MN's LMA, and 
   other MAGs can find the address of the LMA of MN by using the address 
   assigned to the MN.


2.  Conventions and Terminology


2.1.  Conventions

   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 RFC 2119 [3].

   
2.2 Terminoloby
   
   TBD.














Jaehwoon Lee              Expires Sep. 3, 2012                 [Page 3]

Internet-Draft              PMIPv6-based DMM               Mar. 4, 2012


3.  Protocol Operation


      MN                    MAG1                      MAG2          CN
       |                      |                         |            |
       |--------------------->|                         |            |
       |     L2 attachment    |                         |            |
       |<----- RA(PREF) ------|                         |            |
       |---DHCP request msg-->|                         |            |
       |<--DHCP reponse msg---|                         |            |
       |                      |                         |            |
 (Configure IPv6 address)     |                         |            |
       |<-------------------- exchange IP traffic ------------------>|
       |                      |                         |            |
 (Move from MAG1 to MAG2)     |                         |            |
       |----------------------------------------------->|            |
       |                  L2 attachment                 |            |
       |<------------------ RA(PREF) -------------------|            |
       |------------------- IP packet ----------------->|            |
       |                      |                (packet buffering)    |
       |                      |<----- DPBU message -----|            |
       |          (create BCE and est. tunnel)          |            |
       |                      |------ DPBA message ---->|            |
       |                      |        (create BUL and est. tunnel)  |
       |                      |<==== IP packet =========|            |
       |                      |--------------- IP packet ----------->|

                  Figure 1: Message exchange scenario


   Figure 1 shows the message exchange scenario considered in this 
   draft. It is assumed that a network prefix "PREF" is allocated to the 
   PMIPv6 domain and a different sub-network prefix belonging to "PREF" 
   is allocated to a different MAG. In figure 1, it is assumed that 
   a sub-network prefix "PREF1" is allocated to the MAG1 and another 
   sub-network prefix "PREF2" is allocated to the MAG2. Even though a 
   different sub-network prefix is allocated to a different MAG, all the 
   MAGs advertise the same network prefix "PREF" through their 
   interfaces providing PMIPv6 service.

   When an MN enters an PMIPv6 domain and firstly connects to a MAG 
   (say, MAG1), MAG1 transmits Router Advertisement (RA) message by 
   setting "M" flag in order for the MN to configure the address 
   statefully [4]. The RA message contains the prefix information option 
   with "PREF". MN transmits a DHCP request message to the MAG1 for 
   configuring an address to its interface. MAG1 receiving the DHCP 
   request message considers that the MN firstly connects to the PMIPv6 
   domain, assigns an address belonging to "PREF1" and transmits a DHCP 
   response message to the MN. MN receiving the DHCP response message 
   
   
Jaehwoon Lee              Expires Sep. 3, 2012                 [Page 4]

Internet-Draft              PMIPv6-based DMM               Mar. 4, 2012
   
   
   sets the IPv6 address contained in the DHCP response message to its 
   interface, and from now on, MN can communicate with a node within the 
   Internet.

   If MN moves from MAG1 to MAG2, MAG1 can know that the MN is 
   disconnected to the MAG1 by using the layer-2 information. MAG2 
   transmit the RA message containing "PREF" network prefix information 
   to MN. The MN receiving the RA message considers that it still 
   resides in the same network and continues to use the assigned 
   address. The MAG2 checks the first packet sent by the MN. If the 
   first packet contains DHCP request message, then the MAG2 considers 
   that the MN firstly connects to the PMIPv6 domain. Otherwise, MAG2 
   considers that the MN moves from another MAG domain and transmits a 
   DPBU (Distributed Proxy Binding Update) message. The source address 
   of the DPBU message is set to the address of MAG2 and the destination 
   address is set to the MN's address. MAG2 can know the address of the 
   MN by using source address of the packet transmitted by the MN. 
   The DPBU message is transmitted to the MAG1 by using the normal 
   routing procedure within PMIPv6 infrastructure. MAG2 receiving the 
   DPBU message checks whether the MN is currently conncted to it 
   (say, 1-hop neighbor). If not, MAG1 creates the Binding Cache Entry 
   (BCE) for the MN, establishes the tunnel with the MAG2 and transmits 
   a DPBA (Distributed Proxy Binding Acknowledgement) message. The 
   source address of the DPBA message is set to the address of MAG1 and 
   the destination address is set to the address of MAG2. Moreover, the
   DPBA message contains the address of the MN. MAG2 receiving the DPBA 
   message establishes the tunnel with the MAG1. From now on, MN can 
   continue to exchange the traffic with any host within the Internet.


4.  Security Considerations

   TBD


5.  IANA Considerations

   TBD


6.  References

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

   [2] H. Chan et al., "Requirements fo distributed mobility management"
       draft-chan-dmm-requirements-00 (work in progress), Mar. 2012.



Jaehwoon Lee              Expires Sep. 3, 2012                 [Page 5]

Internet-Draft              PMIPv6-based DMM               Mar. 4, 2012



       
   [3]  Bradner, S., "Key words for use in RFCs to Indicate
        Requirement Levels", BCP 14, RFC 2119, March 1997.
       
   [4] T. Narten, E. Nordmark, W. Simpson and H. Soliman, "Neighbor
       Discovery for IP version 6 (IPv6)", RFC 4861, Sep. 2007.
       


Author's Address

   Jaehwoon Lee 
   Dongguk University
   26, 3-ga Pil-dong, Chung-gu
   Seoul 100-715, KOREA  
   Email: jaehwoon@dongguk.edu


































Jaehwoon Lee              Expires Sep. 3, 2012                 [Page 6]

Internet-Draft              PMIPv6-based DMM               Mar. 4, 2012