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

embedded-tls does not understand message fragmenting #110

Open
bugadani opened this issue Apr 21, 2023 · 2 comments
Open

embedded-tls does not understand message fragmenting #110

bugadani opened this issue Apr 21, 2023 · 2 comments

Comments

@bugadani
Copy link
Collaborator

bugadani commented Apr 21, 2023

This was mentioned in #75 (comment) but that issue has since been closed.

@bugadani bugadani changed the title embedded-tls does not understand message fragmentation embedded-tls does not understand message fragmenting Apr 21, 2023
@lulf
Copy link
Member

lulf commented Apr 21, 2023

Does it need to for 99% of embedded use cases?

@bugadani
Copy link
Collaborator Author

bugadani commented Apr 21, 2023

No idea, but on one hand, it might help with MaxFragmentLength extension to tune things, and on the other, I just want this fact visible.

Edit: my guess here is that it's probably not necessary, but also that we might implement something for it under the alloc flag. There's no reason not to be compliant if there is a way to do so :) Definitely not something I'll spend time on any time soon, though.

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

2 participants