In your previous mail you wrote:

   does anyone work on a real ARP implementation? I mean, one which can
   handle multiple protocols for link level and user protocol?
   
=> I am some notes about this idea (because I have already done
Neighbor Discovery (which includes address resolution) for IPv6
and I want to extend it to ATM).

   No, FDDI does not count: it seems to masquerade as Ethernet for ARP
   purposes. 
   
   ARCnet doesn't count either; I didn't implement it yet ;-)

=> I agree: we want generic code for non-IEEE networks,
for instance ATM.

   I guess somebody might be working on IPv6 and implementing a real ARP
   code for that, so I thougt it would be better to ask first.
   
=> good thought! I believe the link-layer part (exactly arpcom-ifnet)
must be made generic with ARP input functions. Most of the code
can be shared then it is not so trivial to write. Another point is
if some protocol specific parts are introduced into the ifnet struct
this should be done in a flexible way and without recompiling
the whole stuff for minor changes (for instance the arpcom stuff
is not good because on SunOS when you add multicast support you
break FDDI drivers: it is obviously bad engineering).

Thanks

Francis.Dupont@inria.fr

PS: I have just seen the need and I am looking for a good way
to solve it.