<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
<html lang="en">
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
<title>
GitLab
</title>
<style>img {
max-width: 100%; height: auto;
}
</style>
</head>
<body>
<div class="content">
<div style="">
<p dir="auto">I have filed <a href="https://gitlab.com/gnutls/gnutls/merge_requests/879" data-original="!879" data-link="false" data-link-reference="false" data-project="179611" data-merge-request="22570305" data-reference-type="merge_request" data-container="body" data-placement="bottom" title="WIP: Fix issues in record_size_limit extension handling" class="gfm gfm-merge_request has-tooltip">!879</a> that should fix some of the issues.</p>
<p dir="auto">For 2, GnuTLS uses 2<strong>14 as the upper limit, regardless of the version. If we want 2</strong>14+1 for TLS 1.3, it would require delaying the initialization after version negotiation. I'm not sure if such complexity is worth it just for 1 byte.</p>
<p dir="auto">Similarly for 8, the lower limit is 512 and adding support for [64, 511) doesn't look straightforward.</p>
<p dir="auto">For 5, does the 1/n-1 splitting in TLS 1.0 actually work without the extension?</p>
</div>
</div>
<div class="footer" style="margin-top: 10px;">
<p style="font-size: small; color: #777777;">
—
<br>
Reply to this email directly or <a href="https://gitlab.com/gnutls/gnutls/issues/676#note_132471795">view it on GitLab</a>.
<br>
You're receiving this email because of your account on gitlab.com.
If you'd like to receive fewer emails, you can
<a href="https://gitlab.com/sent_notifications/c8674a6b48accc2311030b989d801bbe/unsubscribe">unsubscribe</a>
from this thread or
adjust your notification settings.
<script type="application/ld+json">{"@context":"http://schema.org","@type":"EmailMessage","action":{"@type":"ViewAction","name":"View Issue","url":"https://gitlab.com/gnutls/gnutls/issues/676#note_132471795"}}</script>
</p>
</div>
</body>
</html>