Re: RE: AD request / L2 Triggers Chapter Statement

Lloyd Wood wrote:
>>>and not as a MIB. My question is: why are endhost implementations so
>>>STUPID compared to routers in this respect, in not even knowing what
>>>they're immediately connected to and whether it's there or not?
>>
>>Hosts that run routing software aren't.
> 
> They are, because the routing software doesn't talk to the endhost
> applications. No real integration or communication between the two.

OK - so build a framework for that; that's an API, not a protocol, and 
not necessarily in scope for the IETF (it's not even socket level).

>>If you have a multihomed host,
>>run routing on that host. Embed the functionality of a router in the
>>endpoint, and call it a day - we did 5 years ago:
>>
>>  "Dynamic Host Routing for Production Use of Developmental Networks"
>>J. Touch and T. Faber, Proc. ICNP '97, Atlanta, Oct. 1997, pp. 285-292.
>>(www.isi.edu/touch/pubs/)
> 
> As for calling it a day - I see you couldn't maintain a TCP connection
> with it since you didn't have control of the source address the SunOS
> stack set

Yup. That's been fixed in some OS's for a while, and won't go away with 
any other solution either.

> - p5 - and you end with a plea for static loopback
> addresses, as found in all good router software for years, to fix
> this. 

Yup - they're available now. It has been 5 years.

>>>1) MIBs aren't realtime. Not so sure they're desirable, either.
>>
>>IP isn't realtime either. 
> 
> Why not?

OK - so if you're on that tack too, please send comments to the IAB. 
This is definitely outside the scope of a single WG.

>>>2) local implementations don't use MIBs to talk to themselves.
>>>   An endhost using a MIB to tell itself about its own link
>>>   interfaces? I don't think so.
>>
>>How do routers do it?
> 
> A simple function call to find out would suffice.

Fine. Implement one. Why standardize it?

Joe



_______________________________________________
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/