<!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">rfc6125 doesn't answer this question. The trailing dot is only relevant when extending a name into a FQDN.   If we compare domains, we assume they are absolute, even when they don't have a trailing dot. (Is this a wrong assumption !?). So we have to ignore the trailing dot when comparing two (fully qualified = absolute) domains. The RFC calls it comparing label-by-label (case insensitive), which is IMO effectively the same.</p>

<p dir="auto">If we assume that trailing dots are not allowed / not used in certificates nor in the TLS protocol, the best would be to to strip it from user input in the CLI tools and change nothing else.</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/merge_requests/709#note_89289232">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/0d4d97ff156b25204f1c8292821efb5b/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/709#note_89289232"}}</script>

</p>

</div>

</body>

</html>