On Tue, 9 Jul 2002, James Carlson wrote:
> Lloyd Wood writes:
> > > A link on a host going down isn't enough; the host might be multihomed,
> >
> > The host should know whether it's multihomed or not; it should know
> > what it's immediately connected to. If it's not multihomed and e.g.
> > the AAA server at the other end of the PPPoE line goes down and takes
> > your phoneline's TCP dialtone with it - the immediate link is down and
> > your stack is offline. You can inform the apps.
>
> How does the stack determine that the link is down because, for
> instance, the peer router is rebooting, and that it will be back in a
> few seconds? Should my ssh session and all of my redirected X11
> windows be blown out of existence because the router at the other end
> of that DSL link bounces?
That's a decision for ssh or the Xserver to take as applications.
> I still don't see how link unavailablity is *reasonably* translated
> into TCP connection sniping -- particularly as a default policy.
What default policy? Provide the information to be used on a
case-by-case basis, that's all.
L.
<http://www.ee.surrey.ac.uk/Personal/L.Wood/><L.Wood@surrey.ac.uk>
_______________________________________________
pilc mailing list
pilc@ietf.org
https://www1.ietf.org/mailman/listinfo/pilc
http://www.ietf.org/html.charters/pilc-charter.html
http://pilc.grc.nasa.gov/
This archive was generated by hypermail 2b29 : Tue Jul 09 2002 - 08:12:25 EDT