Subject: Re: CVS commit: src/sys/netinet
To: Steven M. Bellovin <email@example.com>
From: David Laight <firstname.lastname@example.org>
Date: 09/08/2003 19:47:51
> The spec permits one IPid sequence per <src,dst,protocol> triple,
> since those parameters are used in matching fragments. The downside
> is implementation complexity; it won't break anything anywhere on
> the net. You also don't need to consume IPid space -- or at least,
> you don't need to worry about preventing duplicates -- on packets
> that have set.
^ dont fragment ???
Actually there is is little point separating on the src address 
I also suspect that very few IP packets are fragmented anywhere other
than the source system (pppoe is one place where it could be done...) .
So you don't really need to worry too much about the IPid on unfragmented
 Only relevant if the system has a large number of source addresses,
but only talks to a small number of remote addresses.
 fddi - ethernet and token-ring ethernet gateways could have to split
long frames, but I actually suspect there is little (ie only a few %)
benefit in using 17k frames on 16M token ring. Do many systems restrict
the size to the ethernet limit anyway? (we didn't....)
David Laight: email@example.com