Hi Carlos, I have a few clarifying questions to your new draft. The draft proposes the distributed logical interface. I don't really get the advantage of virtualizing the previous LMA on the MN's current LMA if packets are routed through the previous LMA anyway. Why not using the current LMA to serve simply as MAG for forwarded traffic (which remains anchored at previous LMA) and using the new LMA to anchor the new address/prefix?
The draft writes that the idea hides the change of the anchor from the mobile node. The DGW2IF on the new LMA does not pretend to be LMA1, or? I don't see how the anchor change is kept transparent to the MN. I somehow agree also to Pete's opinion that solving the packet routing after anchor relocation above the anchors is a good option. It simply allows more optimal routes. Now I am deviating a bit, but into the direction of an important question: That's directly related to the question of how persistent we need to be about IP address continuity. Now, some proposals consider termination of an IP address prefix, which is anchored at a previously used anchor point, as soon as the IP session, which uses that address, terminates. New sessions can use the address being anchored at the new mobility anchor. My opinion is that we need to find a good choice about the lifetime of such an anchored IP address, as it may also be registered with other services, e.g. IMS, messaging, etc, and would require an updated registration after a change in the registered address. And even if such lifetime is short, we may not accept suboptimal routing paths via the previous anchor after anchor relocation. What do you think? Thanks, marco > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of > Carlos Jesús Bernardos Cano > Sent: Montag, 5. März 2012 18:40 > To: [email protected] > Subject: [DMM] New DMM draft: draft-bernardos-dmm-distributed- > anchoring-00.txt > > Dear all, > > We've just submitted a new I-D on the DMM space. The draft describes a > network-based DMM approach extending PMIPv6, and focusing on the > required extensions to effectively support simultaneously anchoring several > flows at different distributed anchors. > > As usual, comments would be warmly welcomed! > > More info below: > > Title : PMIPv6-based distributed anchoring > Author(s) : Carlos J. Bernardos > Juan Carlos Zuniga > Filename : > draft-bernardos-dmm-distributed-anchoring-00.txt > Pages : 23 > Date : 2012-03-05 > > Distributed Mobility Management solutions allow for setting up > networks so that traffic is distributed in an optimal way and does > not rely on centralized deployed anchors to provide IP mobility > support. > > There are many different approaches to address Distributed Mobility > Management, as for example extending network-based mobility protocols > (like Proxy Mobile IPv6), or client-based mobility protocols (as > Mobile IPv6), among others. This document follows the former > approach, and proposes a solution based on Proxy Mobile IPv6 in which > mobility sessions are anchored at the last IP hop router (called > distributed gateway). The distributed gateway is an enhanced access > router which is also able to operate as local mobility anchor or > mobility access gateway, on a per prefix basis. The draft focuses on > the required extensions to effectively support simultaneously > anchoring several flows at different distributed gateways. > > This draft introduces the concept of distributed logical interface > (at the distributed gateway), which is a software construct that > allows to easily hide the change of anchor from the mobile node. > Additionally, the draft describes how to provide session continuity > in inter-domain scenarios in which dynamic tunneling or signaling > between distributed gateways from different operators is not allowed. > > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-bernardos-dmm-distributed- > anchoring-00.txt > > Thanks, > > Carlos > > -- > Carlos Jesús Bernardos Cano http://www.netcom.it.uc3m.es/ GPG FP: D29B > 0A6A 639A A561 93CA 4D55 35DC BA4D D170 4F67 _______________________________________________ dmm mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmm
