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

This uses a lot of codepoints #11

Closed
martinthomson opened this issue Jul 10, 2018 · 2 comments
Closed

This uses a lot of codepoints #11

martinthomson opened this issue Jul 10, 2018 · 2 comments

Comments

@martinthomson
Copy link
Contributor

@martinthomson martinthomson commented Jul 10, 2018

If you subscribe to the theory that DTLS has to mux with the realtime protocols, this takes a good slice of the remaining codepoints space. Though TLS has between 20 and 63, DTLS 1.3 takes 32-63 and the registration of 4 more would leave just 3: 29, 30, and 31.

I submit that we might be better considering the TLS 1.3 record construction with a single codepoint. That would get us content type encryption and arbitrary padding as a secondary benefit. All for the modest cost of one octet.

@thomas-fossati
Copy link
Collaborator

@thomas-fossati thomas-fossati commented Aug 24, 2018

If DTLS 1.3 used a demux prefix scheme like the one proposed here, this should be no longer an issue.

@ekr
Copy link
Contributor

@ekr ekr commented Oct 21, 2018

Addressed in #13

@ekr ekr closed this Nov 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants