Re: RE: AD request / L2 Triggers Chapter Statement

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?

I still don't see how link unavailablity is *reasonably* translated
into TCP connection sniping -- particularly as a default policy.

-- 
James Carlson, Solaris Networking         <[email protected]>
SUN Microsystems / 1 Network Drive         71.234W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.497N   Fax +1 781 442 1677

_______________________________________________
pilc mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/pilc
http://www.ietf.org/html.charters/pilc-charter.html
http://pilc.grc.nasa.gov/