Please check the updated REQ1 in draft-ietf-dmm-requirements-02:

   REQ1:  Distributed deployment

          IP mobility, network access and routing solutions provided by
          DMM MUST enable distributed deployment for mobility management
          of IP sessions so that traffic does not need to traverse
          centrally deployed mobility anchors and thus can be routed in
          an optimal manner.

          Motivation: This requirement is motivated by current trends in
          network evolution: (a) it is cost- and resource-effective to
          cache and distribute content by combining distributed mobility
          anchors with caching systems (e.g., CDN); (b) the
          significantly larger number of mobile nodes and flows call for
          improved scalability; (c) single points of failure are avoided
          in a distributed system; (d) threats against centrally
          deployed anchors, e.g., home agent and local mobility anchor,
          are mitigated in a distributed system.

   This requirement addresses problems PS1, PS2, PS3, and PS4 in the
   following.

   PS1:  Non-optimal routes

         Routing via a centralized anchor often results in a longer
         route.  The problem is especially manifested when accessing a
         local server or servers of a Content Delivery Network (CDN).

   PS2:  Divergence from other evolutionary trends in network
         architecture

         Centralized mobility management can become non-optimal with a
         flat network architecture.

   PS3:  Low scalability of centralized route and mobility context
         maintenance

         Setting up routes through a central anchor and maintaining
         mobility context for each MN therein requires more resources is
         more difficult to scale in a centralized design, thus reducing
         scalability.  Distributing the route maintenance function and
         the mobility context maintenance function among different
         network entities can increase scalability.

   PS4:  Single point of failure and attack

         Centralized anchoring may be more vulnerable to single points
         of failures and attacks than a distributed system.  The impact
         of a successful attack on a system with centralized mobility
         management can be far greater as well.

H Anthony Chan
_______________________________________________
dmm mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmm

Reply via email to