<!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>

<p dir="auto">By the way, I am currently implementing ClientHello recording (RFC 8446 8.2), as anti-replay measure.  That suggests that in some occasions (e.g. a ticket arrived out of time window), the server should reject 0-RTT but can continue with 1-RTT.  In that case, the client may want to resend the early data as a normal application data after handshake.  So rather than having a separate send function (<code>gnutls_record_send_early_data</code>), it might make more sense to reuse <code>gnutls_record_send2</code> and allow it to fallback from 0-RTT to 1-RTT.</p>

<p dir="auto">What do you think?</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/merge_requests/775#note_110331340">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/5ce67c1d51858e8aedb6be0ae31a0746/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 Merge request","url":"https://gitlab.com/gnutls/gnutls/merge_requests/775#note_110331340"}}</script>

</p>

</div>

</body>

</html>