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

 
> 
> Triggering something known locally (interface down etc)
> needs an external trigger. Lack of packets could be triggered
> either by external triggers or MOBIKE/IKEv2 itself. I
> personally prefer the latter, because there would be
> less reliance on APIs and other protocol layers.
> 
There are already other working groups like DNA, multi6 etc. that would
come up with mechanisms to detect link changes, path changes etc. MOBIKE
could just use that. But your concern is how will MOBIKE interface with other
modules to learn the information ? i.e., if there is no mechanism to learn about
link up/link down in the system or MIP4/MIP6 is not implemented in the node,
what should MOBIKE do ? Also, what does it mean if there are other mechanisms,
should MOBIKE use that or invent something new or take into consideration both ?

It would  be simpler if we just document what sort of triggers ( a few examples)
are needed for MOBIKE to work. Whether it is implemented as part of MOBIKE or
outside of MOBIKE is an implementation detail.  I guess this is what Francis is getting
at. If so, i agree.

-mohan

> --Jari
> 
> Mohan Parthasarathy wrote:
> > Are we assuming that triggers for these are going to come from outside of mobike or
> > mobike itself will detect such things ?
> > 
> > -mohan
> > 
> > ----- Original Message ----- 
> > From: <[email protected]>
> > To: <[email protected]>
> > Sent: Thursday, August 12, 2004 6:01 AM
> > Subject: [Mobike] New issue 16: No packets from other end?
> > 
> > 
> > I've created a new issue in the issue list:
> > 
> >    "Can the protocol recover from situations where the only 
> >    sign of problems is lack of packets from the other end?"
> > 
> >    (http://www.vpnc.org/ietf-mobike/issues.html)
> > 
> > Many people at the WG meeting expressed opinions that this 
> > should be handled somehow (in addition to handling e.g. 
> > link-down triggers from layer 2, or something similar).
> > 
> > So far, I do not remember anyone saying that the protocol
> > does not need to handle this situation. But comments
> > are welcome.
> > 
> > Best regards,
> > Pasi
> > _______________________________________________
> > Mobike mailing list
> > [email protected]
> > https://www.machshav.com/mailman/listinfo.cgi/mobike
> > _______________________________________________
> > Mobike mailing list
> > [email protected]
> > https://www.machshav.com/mailman/listinfo.cgi/mobike
> > 
> > 
>