Re: RE: AD request / L2 Triggers Chapter Statement

I am sorry about that "sand" comment.  It seems the arguments quickly get circuitous.  What we
are suggesting is something really subtle.  

A).  IP needs to create a standard interface method on its unspecified bottom half.
B).  It already has one on the top, namely sockets.

This is quite different than saying, all L2s must do this or that.  What we want is a mechanism to 
pass L2 information in a standard way up to and through the IP stack.  In order for this to
happen in the correct way, the IETF needs to specify it.

What is so complicated about this?   Just because we proposing something new, i.e. it
does not exist in ppp, arp, or other similar mechanisms why is it immediately assumed
that it is an L2 issue?

The IETF has already made their recommendations to L2 providers.  Now its time for
the IETF to be a bit more introspective.  If there are some skeletons here, let's pull them
out and take a peek.


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