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

The note about AEAD limits is not needed #4578

Merged
merged 1 commit into from Jan 7, 2021
Merged

The note about AEAD limits is not needed #4578

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
9 changes: 0 additions & 9 deletions draft-ietf-quic-tls.md
View file
Open in desktop
Expand Up @@ -1710,15 +1710,6 @@ integrity limits; see {{aead-analysis}} for details.
Future analyses and specifications MAY relax confidentiality or integrity limits
for an AEAD.

Note:

: These limits were originally calculated using assumptions about the
limits on TLS record size. The maximum size of a TLS record is 2^14 bytes.
In comparison, QUIC packets can be up to 2^16 bytes. However, it is
expected that QUIC packets will generally be smaller than TLS records.
Where packets might be larger than 2^14 bytes in length, smaller limits might
be needed.

Any TLS cipher suite that is specified for use with QUIC MUST define limits on
the use of the associated AEAD function that preserves margins for
confidentiality and integrity. That is, limits MUST be specified for the number
Expand Down