docs: add dev docs on handshake and io#5596
Conversation
|
Sorry, Click on the wrong button. I didn't mean to approve this revision. |
docs/development/APPLICATION_DATA.md
Outdated
|
|
||
| ## Fragmentation | ||
|
|
||
| TLS records may only contain a limited amount of data. If an application wants to send a large amount of data, that data will be broken into "fragments" and each fragment will be sent in a separate record. |
There was a problem hiding this comment.
I feel like this is a very confusing way of introducing fragments. Like, why do both TLS records and TLS fragments have a max length of 2^14? It's because they're literally the same thing. Fragmentation is just what happens when a message is > 2^14 and you have to split it up across multiple records, or you've artificially set your "max record length" to be smaller than the spec for optimization reasons.
"The record layer fragments information blocks into TLSPlaintext
records carrying data in chunks of 2^14 bytes or less."
There was a problem hiding this comment.
I don't want to say words like TLSPlaintext here. But "record" refers to a fragment + header.
Co-authored-by: Boquan Fang <boquanfang3@gmail.com> Co-authored-by: maddeleine <59030281+maddeleine@users.noreply.github.com>
Release Summary:
Resolved issues:
Description of changes:
New s2n-tls developers tend to struggle the most with the handshake and send/receive logic. Those sections are extremely important to how s2n-tls operates, but also somewhat complex. This PR adds some documentation aimed at s2n-tls developers trying to understand those sections.
Testing:
Just documentation.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.