Re: RE: AD request / L2 Triggers Chapter Statement

Phil Neumiller wrote:
> 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.

Given that IP is stateless and connectionless, what would IP do with any 
particular information it gets?

There is no way to push information through a stateless system into a 
stateful one (e.g., TCP, or to application layers, e.g., routing 
protocols or user applications that are carried as data inside transport 
protocols).

The exceptions would be MPLS (as a stateful layer below IP, which could 
do something with such info). The state of mobile IP is essentially 
application layer, for all intents, to the IP layer.

> What is so complicated about this?

See above.

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/