Re: [RFC/PATCH] "strict" ipv4 reassembly

[Rick Jones <rick.jones2@xxxxxx>]

> Actually, the problem is much worse now - we have virtual
> partitions in the Xen environment for instance where some
> packets are headed for local consumption (virtual network,
> no actual network latency to speak of) and some going
> out to the network. Having a global IP id generator just
> won't be able to keep up - we could wrap in submilliseconds...
and the classic TCP sequence number isn't _really_ all that far behind :)

> > The larger NFS UDP mount sizes mean more fragments, but intriguingly, 
> > they also mean slower wrap of the IP ID space :)
>
> True, but in a 32 NIC environment, see how they wrap ;)...
Yep - I'd thought that just about everyone had gone to per-dest or per-route IP 
ID's by now, but even then
rick