Re: New issue 16: No packets from other end?

   > 
> for example, lets assume my mobile device has a low bandwidth
> GPRS link (address IP1 on that link) and a high bandwidth WLAN
> link (address IP2 on that link). I have set it up so that my
> email is downloaded only when I connect to my Enterprise
> through a VPN connection when I have the WLAN link. if the
> WLAN link is not available, I dont want the email client to
> download email. lets assume I am in the middle of downloading
> email. I lose WLAN coverage. with your proposal, the MOBIKE
> protocol switches to using IP1. I dont want that.
> 
> > We don't need to specify exactly how this works, and as Francis
> > pointed out, there are many complex issues in e.g. handoff 
> > decisions that we don't want to put in MOBIKE specs.
> > 
> > What we IMHO do need to specify are the parts required for 
> > interoperability, like what is sent/received to/from the other 
> > node, and some parts of how those messages are processed. 
> > I think this should be specified in the MOBIKE spec; that is, we
> > should not assume that there is some other unspecified protocol 
> > (in addition to IKEv2 and ESP/AH) running between the parties.
> 
> IMHO, I prefer "something in the Mobile Node" telling MOBIKE,
> "switch to using this address with this VPN GW". then a MOBIKE
> update should be sent. this is the model I had in my mind.
> 
But we don't want to restrict MOBIKE to do it this way. This means we
should keep MOBIKE flexible enough to use any external trigger it wants. 

> for "something in the Mobile Node" I had assumed DNA, MIP6,
> Multi6, new address configuration, default router change, etc...
> 
Agreed.

-mohan

> Vijay
> _______________________________________________
> Mobike mailing list
> [email protected]
> https://www.machshav.com/mailman/listinfo.cgi/mobike