Robert Elz <[EMAIL PROTECTED]> writes:
> With a 20 bit field, and a PRNG value in the field, then there's
> room for a million different flows, all passing through a router,
> and all being uniquely matched by just the flow label (with address
> verification later).
I'm not sure what do you mean by your parenthetical comment.
If you are to match on source and destination later, you could as well
include them in the key. They are either part of the key or not,
"order" of matching bits in the key isn't the issue (you probably want
to hash the whole key anyway).
With 20 bits PRN as flow label, collisions will start occuring after
roughly 1000 flows. That's obviously way too low a number. If you
want to be able to identify flows by their labels you'd need many more
bits for the label.
What's the point, though? Why is matching on some bits (flow label)
preferable to matching on other bits (addresses)? Is your concern to
have a contiguous block of bits? (That shouldn't matter in ASICs, I
suppose.)
--
Stanislav Shalunov http://www.internet2.edu/~shalunov/
"Nuclear war can ruin your whole compile." -- Karl Lehenbauer
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
