You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MSL is defined at the section 2.4.2 referring to the clock of fig. 43. In the discussion about data transfer it is used mentioning its role in avoiding duplicates (end of the paragraph after the two figures without number) and saying that sequence numbers should not wrap up before MSL.
Then in the example referring to figure 50 it seems the sequence number wraps up before MSL, and in the text commenting that example, MSL is defined again.
Besides the repetition, the relationship between fig. 43 and 44 is not really clear. The key point is that the timer makes it so that seq. number is not reset after a reboot, or it could conflict with a previously used one, but this is not explicitly mentioned. Only the second bullet mentions reboot but it is not straightforward to relate.
Finally, I would add a note that says that using predictable initial sequence numbers has security consequences and that randomness must be introduced, referencing to sect. 3.12.
The text was updated successfully, but these errors were encountered:
MSL is defined at the section 2.4.2 referring to the clock of fig. 43. In the discussion about data transfer it is used mentioning its role in avoiding duplicates (end of the paragraph after the two figures without number) and saying that sequence numbers should not wrap up before MSL.
Then in the example referring to figure 50 it seems the sequence number wraps up before MSL, and in the text commenting that example, MSL is defined again.
Besides the repetition, the relationship between fig. 43 and 44 is not really clear. The key point is that the timer makes it so that seq. number is not reset after a reboot, or it could conflict with a previously used one, but this is not explicitly mentioned. Only the second bullet mentions reboot but it is not straightforward to relate.
Finally, I would add a note that says that using predictable initial sequence numbers has security consequences and that randomness must be introduced, referencing to sect. 3.12.
The text was updated successfully, but these errors were encountered: