| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi all, I was reading over the text in 4.2.5.2 in D0.4 today and it struck me that it wasn’t explicit that the seqnum and the incrementing thereof would be flow-specific, even though I believe it is (I missed the work on the current definition
of this text as I missed a couple of meetings late last year so forgive me if I’m off-base). I respectfully submit the following clarifications to the text, if the group feels that it’s an improvement to what we have right now. 4.2.5.2 Sequence number (seqnum) field The sequence number field is generated by the mapper and constitutes of three independently sized fields, whose sizes depend on two variables p and q.
Figure 9 illustrates the composition of different fields that together form the sequence number. The following rules shall apply: 0 <= p < 32 and 0 <= q <= p and (32-p)+(p-q) <= 32 The field from p up to and including 31 is the p-counter field and the field from q to p is the q-counter field. At minimum the p-counter field shall exist. The other two fields may exist based on the p and q values.
<New Text>Each RoE flow that uses sequence numbers shall have its own instance of p-counter and q-counter. </New Text> Each of the fields is initialized to a known value on the first use of the sequence number within a flow. Note
that the seqNumPMax, seqNumPIncProp, seqNumQMax, seqNumQInc, seqNumQIncProp, and seqNumRsvd values shall remain unchanged during the lifetime of the RoE flow
<new_text>but each flow may have different values for these variables</new_text>. (Richard, if you would like my modified file I can e-mail it to you but it’s probably just as easy to cut and paste from the above) Cheers Gareth |