Hi Charlie, > -----Original Message----- > From: Charlie Perkins [mailto:[email protected]] > Sent: Tuesday, October 07, 2014 11:16 AM > To: Templin, Fred L; [email protected] > Subject: Re: [DMM] AERO and Mobile IP comparison > > > Hello Fred, > > One comment: > > On 10/7/2014 11:08 AM, Templin, Fred L wrote: > > - the mobility archetype for AERO is that of a mobile router that stays > > connected to its > > home link even if it changes between access link technologies > > This implies local-only mobility, right?
Not just local, but global also. Take for example an AERO mobile router that is connecting over an access link provided by some ISP other than its home network. In that case, the node typically remains connected to its home link by setting up a VPN connection via a security gateway connected to its home network. In that case, the AERO link is said to be extended *through* the security gateway. So, the AERO mobile router remains tethered to its home link via the VPN, but it can set up route optimization with Internet correspondents in a manner similar to MIPv6. In that case, communications with the Internet correspondent can bypass the home network. > If so, then I guess from your other description that "local" is > engineered to be huge. AERO has been evolving for the better part of a decade really, but in recent years it has been specifically focused on enterprise network mobility where the enterprise network that services my employer has been used as the reference model. In such cases, the AERO virtual link is indeed huge. > But more to the point it puts AERO > pretty much in direct competition with PMIP -- or, perhaps > PMIP with LMAs stitched together by way of BGP. I have to admit that PMIP comparison was an after-thought that only went into the AERO spec very recently. Yes, AERO can be applied in the same use cases as for PMIP, but in the enterprise mobility case the AERO Client itself is the mobile router and runs a small piece of application layer code to do the tunneling and control messaging. In our enterprise, for example, mobile nodes can start out attached to a wired LAN connection, then change over to WiFi, then change over to 4G, etc. See my "day in the life" message from several weeks ago: http://www.ietf.org/mail-archive/web/dmm/current/msg01464.html In fact, I see PMIP as a very specialized solution for cellular operator networks. There are vastly many other use cases where having the mobile node do the tunneling on its own behalf is necessary. AERO supports either model. Thanks - Fred [email protected] > Regards, > Charlie P. _______________________________________________ dmm mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmm
