Hello folks,

   REQ1:  Distributed processing

          IP mobility, network access and routing solutions provided by
          DMM MUST enable distributed processing for mobility management
          so that traffic does not need to traverse centrally deployed
          mobility anchors and thereby avoid non-optimal routes.

The real issue is not the "central location of the anchor", but "off-path 
location of the anchor".

The triangular route is caused by forcing the packets to traverse an anchor 
node that is not on the direct IP path between the MN and the CN.

See the CNet-Homing proposal. 
http://www.ietf.org/id/draft-yegin-dmm-cnet-homing-01.txt. We place the anchor 
in corresponding network, or the ISP serving that network. Therefore, the path 
going via that anchor does not cause triangulation. Some people may perceive 
that as locating the anchor in a central location (though this time it's not an 
"absolute/unchanging" center as implied in the current text).

Therefore I recommend the following revision:

   REQ1:  Distributed processing

          IP mobility, network access and routing solutions provided by
          DMM MUST enable distributed processing for mobility management
          so that traffic is not forced to traverse off-path
          mobility anchors and thereby avoid non-optimal routes.

Alper




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

Reply via email to