<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.liu-distributed-mobility" target="https://datatracker.ietf.org/doc/html/draft-liu-distributed-mobility-02">
   <front>
      <title>Distributed mobility management</title>
      <author initials="D." surname="Liu" fullname="Dapeng Liu">
         <organization>China Mobile</organization>
      </author>
      <author initials="Z." surname="Cao" fullname="Zhen Cao">
         <organization>China Mobile</organization>
      </author>
      <author initials="P." surname="Seite" fullname="Pierrick Seite">
         </author>
      <author initials="H. A." surname="Chan" fullname="H Anthony Chan">
         <organization>Huawei Technologies</organization>
      </author>
      <date month="July" day="10" year="2010" />
      <abstract>
	 <t>Current mobility solutions generally introduce an anchor point in the
network, e.g., HA in MIPv6, LMA in PMIPv6, GGSN in 3GPP.  The anchor
point is used to maintain the mapping between the stable IP address
(e.g., Home address in MIPv6) and the current routable IP address
(e.g., CoA in MIPv6).  However, one of the trend in mobile network
evolution is to &quot;flatten&quot; mobility architecture by confining mobility
support in the access network, e.g. at the access routers level,
keeping the rest of the network unaware of the mobility events and
their support.  This document discusses the deployment of current IP
mobility mechanisms in such a flat architecture.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-liu-distributed-mobility-02" />
   
</reference>
