<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Yes , when any changes concerning DS records would drag willing
of support by registries, it sounds reasonable that there should
be an RFC for it.<br>
</p>
<p><br>
</p>
<p>Thanks,</p>
<p>Carlos<br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 02/01/2025 13:45, Robert Wagner
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:SN6PR04MB4559B86E68226416D3612AB2BE142@SN6PR04MB4559.namprd04.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<style type="text/css" style="display:none;">P {margin-top:0;margin-bottom:0;}</style>
<div class="elementToProof"
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 14pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof"
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 14pt; color: rgb(0, 0, 0);">
From my poke a few months back - stuff like PQC and NSA's
Commercial Solutions for Classified settings need to go through
the RFC process. Since both the DNS server and DNS client need
to be on the same page as to which cipher suites they agree on.</div>
<div class="elementToProof"
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 14pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof"
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 14pt; color: rgb(0, 0, 0);">
Around 10/16:</div>
<div class="elementToProof"
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 14pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="background-color: rgb(255, 255, 255); margin: 0px;">
<div class="elementToProof"
style="text-align: left; text-indent: 0px; margin: 0px; font-family: "Segoe UI", "Segoe UI Web (West European)", -apple-system, BlinkMacSystemFont, Roboto, "Helvetica Neue", sans-serif; font-size: 15px; color: rgb(36, 36, 36);">
Robert, if you'd like to propose standardizing SHA-512 for use
in DS records please propose this in an Internet Draft — there
is a helpful page here:
<a href="https://authors.ietf.org/en/home" target="_blank"
id="OWAc97cb751-2377-34b6-395e-015d32ad2141"
class="OWAAutoLink moz-txt-link-freetext"
title="https://authors.ietf.org/en/home"
rel="noopener noreferrer" data-linkindex="1"
data-auth="NotApplicable" style="margin: 0px;"
moz-do-not-send="true">
https://authors.ietf.org/en/home</a> . </div>
</div>
<div style="background-color: rgb(255, 255, 255); margin: 0px;">
<div
style="text-align: left; text-indent: 0px; margin: 0px; font-family: "Segoe UI", "Segoe UI Web (West European)", -apple-system, BlinkMacSystemFont, Roboto, "Helvetica Neue", sans-serif; font-size: 15px; color: rgb(36, 36, 36);">
<br>
</div>
<div
style="text-align: left; text-indent: 0px; margin: 0px; font-family: "Segoe UI", "Segoe UI Web (West European)", -apple-system, BlinkMacSystemFont, Roboto, "Helvetica Neue", sans-serif; font-size: 15px; color: rgb(36, 36, 36);">
W</div>
</div>
<div class="elementToProof"
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 14pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof"
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 14pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" id="Signature">
<div
style="font-size:14pt;color:#000000;font-family:Calibri,Helvetica,sans-serif"
dir="ltr" id="divtagdefaultwrapper">
<p style="margin-top: 0px; margin-bottom: 0px;">Robert Wagner<br>
</p>
<p style="margin-top: 0px; margin-bottom: 0px;"><br>
</p>
</div>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif"
style="font-size:11pt" color="#000000"><b>From:</b> bind-users
<a class="moz-txt-link-rfc2396E" href="mailto:bind-users-bounces@lists.isc.org"><bind-users-bounces@lists.isc.org></a> on behalf of Carlos
Horowicz via bind-users <a class="moz-txt-link-rfc2396E" href="mailto:bind-users@lists.isc.org"><bind-users@lists.isc.org></a><br>
<b>Sent:</b> Thursday, January 2, 2025 7:32 AM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:bind-users@lists.isc.org">bind-users@lists.isc.org</a>
<a class="moz-txt-link-rfc2396E" href="mailto:bind-users@lists.isc.org"><bind-users@lists.isc.org></a><br>
<b>Subject:</b> Question about post-quantum X25519Kyber768</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span
style="font-size:11pt;">
<div class="PlainText">This email originated from outside of
TESLA<br>
<br>
Do not click links or open attachments unless you
recognize the sender and know the content is safe.<br>
<br>
Hi there,<br>
<br>
does anyone know of the bind developers thinking of
incorporating<br>
post-quantum cryptography into bind9 , like Cloudflare
with<br>
X25519Kyber768 on BoringSSL ?<br>
<br>
I'm just curious about if there are thoughts or ongoing
work, or if this<br>
is in the near roadmap at all.<br>
<br>
Thank you,<br>
<br>
Carlos Horowicz<br>
Avascloud/Planisys<br>
<br>
--<br>
Visit <a
href="https://lists.isc.org/mailman/listinfo/bind-users"
moz-do-not-send="true" class="moz-txt-link-freetext">https://lists.isc.org/mailman/listinfo/bind-users</a>
to unsubscribe from this list<br>
<br>
ISC funds the development of this software with paid
support subscriptions. Contact us at
<a href="https://www.isc.org/contact/"
moz-do-not-send="true" class="moz-txt-link-freetext">https://www.isc.org/contact/</a>
for more information.<br>
<br>
<br>
bind-users mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:bind-users@lists.isc.org">bind-users@lists.isc.org</a><br>
<a
href="https://lists.isc.org/mailman/listinfo/bind-users"
moz-do-not-send="true" class="moz-txt-link-freetext">https://lists.isc.org/mailman/listinfo/bind-users</a><br>
</div>
</span></font></div>
</blockquote>
</body>
</html>