Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarifying the use of message_seq vs. record sequence_number #2

Closed
ekr opened this issue Jun 23, 2017 · 0 comments
Closed

Clarifying the use of message_seq vs. record sequence_number #2

ekr opened this issue Jun 23, 2017 · 0 comments

Comments

@ekr
Copy link
Collaborator

ekr commented Jun 23, 2017

Copied from ekr's repo:
Ben wrote:

On page 20, second paragraph, please be clear that it is the
message_seq vs. the record sequence_number that must match
next_receive_seq.
The text in the document says:

DTLS implementations maintain (at least notionally) a
next_receive_seq counter. This counter is initially set to zero.
When a message is received, if its sequence number matches
next_receive_seq, next_receive_seq is incremented and the message is
processed. If the sequence number is less than next_receive_seq, the
message MUST be discarded. If the sequence number is greater than
next_receive_seq, the implementation SHOULD queue the message but MAY
discard it. (This is a simple space/bandwidth tradeoff).

@ekr ekr closed this as completed in e644762 Jul 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant