<!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=US-ASCII" http-equiv="Content-Type">

<title>

GitLab

</title>

<style>img {

max-width: 100%; height: auto;

}

</style>

</head>

<body>

<div class="content">

<p style="color: #777777;">

<a href="https://gitlab.com/nmav">Nikos Mavrogiannopoulos</a>

commented:

</p>

<div style="">

<p dir="auto">Given that the RFC brings many changes, including TLS1.3 packets into TLS1.2, I think it makes sense to introduce that in a minimalistic way to avoid changes that make little sense (such as TLS1.3 packet format for AES-CBC ciphersuites). A proposal is with a new <code>gnutls_init</code> flag that will enable this extension but it will prevent advertising or negotiating any non-AEAD ciphersuites. That way the new format can be implemented only for the AEAD ciphersuites under TLS1.2, which is sufficient for the main use case linked, as well as any DTLS1.2 implementation.</p>

</div>

</div>

<div class="footer" style="margin-top: 10px;">

<p style="font-size: small; color: #777;">

—

<br>

Reply to this email directly or <a href="https://gitlab.com/gnutls/gnutls/issues/801#note_296452341">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/2e7330505819b2fb060580e1b6472094/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/801#note_296452341"}}</script>

</p>

</div>

</body>

</html>