Keith Moore wrote:
so it seems like what we need is a bit in the IP header to indicate that
L2 integrity checks are optional, and to specify for various kinds of
IP-over-FOO how to implement that bit in FOO.
How would an app know to set this bit? The problem is that different L2s
will have different likelihoods of corruption; you may decide that it's
safe to set the bit on Ethernet, but not on 802.11*. And, in general,
the app doesn't know all of the L2s that may be involved when it sends a
packet.
--
/==========================================\
|John Stracke |jstracke(_at_)centive(_dot_)com |
|Principal Engineer|http://www.centive.com |
|Centive |My opinions are my own.|
|==========================================|
|Linux: the Unix defragmentation tool. |
\==========================================/