Re: RE: AD request / L2 Triggers Chapter Statement

> 
> The whole of L2 Triggers assumes that:
> 
> 1) events occur at the link on the timescale of milliseconds
> 2) these events must be communicated to L3
> 3) L3 can do something useful with these triggers
> 
> #1 is granteed, but #2 assumes that #3 ever occurs. There is little in 
> IP as a whole that supports such "realtime" requirements of millisecond 
> responses. In fact, that's in opposition to most of the rest of the 
> Internet architecture.

Yes.  That IS the point.  There needs to be.  If IP were to create a nice
home for L2s, life would be much simpler for wireless system providers.
Wireless links stink.  They come and they go.  IP was build for 10E0-06 
or better BER links.  This needs to change.  It needs to change in IP not
in the L2s.  The L2s do what they can.  I would beg to differ that this
is NOT realtime.  Many routers handle millions of packets per second
over optical links.  THIS IS VERY REALTIME.  The underbelly of
IP is underspecified and must provide a robust well documented 
interface for L2 attachement.  This includes notifications from L2s.
Just think of it is another sockets layer but on the bottom side of IP.
Also, many of these events will need to be relayed to the various
transport protocols that have registered interest in the events for the
particular link.  Applications include but are not limited to:

o      Fault tolerant failover of links
o      L2 signal quality indications
o      L2 congestion control
o      L2 fragmentation control

Thanks,

Phil





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