Requested revision
| Standard: | 802.1CB | Clause: | 7.4.3.6 |
| Clause title: | ShiftSequenceHistory | ||
Rationale for revision
The VectorRecoveryAlgorithm calls ShiftSequenceHistory routine when it
processes
a packet with a sequence number that is in the future (but still falls
within the SequenceHistory). The ShiftSequenceHistory routine erroneously
increments the counter frerCpsSeqRcvyLostPackets as it can’t differentiate
the packets that are actually lost from the packets that are not yet seen.
This is due to the fact that SequencyHistory is initialized to all zeros by
the SequenceRecoveryReset routine that initializes the SequenceRecovery
instance.
Proposed text
Discuss. Perhaps need an additional variable that indicates the initial
state.
Size of this variable is same as size of the SequenceHistory array.
Impact on existing networks
No impact given that frerCpsSeqRcvyLostPackets counting is broken with the
current definition.
Originator
| Name: | Venkat Arunarthi | Email: | venkat.arunarthi@broadcom.com |
| Affiliation: | Broadcom | ||
| Submitted: | 2024-10-31 | ||