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.

Sign up for GitHub

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

Jump to bottom

Clarify dynamically changing length and sequence number #162

Closed
hannestschofenig opened this issue Nov 20, 2020 · 0 comments · Fixed by #195
Closed

Clarify dynamically changing length and sequence number #162

hannestschofenig opened this issue Nov 20, 2020 · 0 comments · Fixed by #195
Labels
pr-exists

Comments

@hannestschofenig
Copy link
Collaborator

Andy Cunningham wrote

The spec is very specific on the content type fields for C(CID) and EE(Epoch bits). What about S and L? Can the sequence number encoding dynamically change while using the DTLS connection? Same question for length field? Can the connection send packets with and without the length fields (i.e. single datagrams vs multiple datagrams)?

Text would not hurt in the draft to explain this.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
pr-exists
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Clarify mixing sequence and length settings on the same connection ekr/dtls13-spec
2 participants
@hannestschofenig @ekr