Greetings,

We wanted to clarify three points about MTL we saw after the interim around 
potential protocol changes, implementation complexity, and suitability for 
operators.

Re: protocol changes – since the -01 version of the base draft, MTL no longer 
uses EDNS(0) to request full versus condensed signatures [1]. Every RRSIG in 
the base draft is now a full signature containing both the signed ladder 
(ML-DSA-44 signature) and Merkle proof. Beyond what any new DNSSEC algorithm 
requires (code points, validator support), no DNS protocol changes are needed. 
This simplifies the base implementation with the trade-off of moving potential 
bandwidth savings to an optional extension draft [2] while still giving 
operators benefits for space and compute.

Re: implementation complexity — MTL does add some complexity compared to 
ML-DSA-44, but the latest base draft is meant to ease that. For validators, MTL 
is deployed like any existing DNSSEC algorithm where each RRSIG can be 
evaluated against a DNSKEY. This change has removed the complexity of needing 
to keep track of other signature state as a validator has access to the full 
signature in each RRSIG. Validators may still want to add logic to store the 
same signed ladder only once to avoid re-verifying a previously seen signed 
ladder in a full signature, but this is not required. Another small bit of 
complexity is the need to implement Merkle proof validation logic, but that 
would only add a few fast hash operations.

For an authoritative server, there is more complexity as there is a need to 
keep track of Merkle tree(s) and MTL specific state. In exchange, MTL offers 
potential for considerable space and computation savings. Importantly, assuming 
multiple PQ DNSSEC algorithms are standardized and deployed, authoritative 
operators can opt into the algorithm that works best for them, so this added 
complexity falls primarily on those who choose it. For large TLD zones, MTL can 
be more economical compared to ML-DSA-44, so we view this complexity as 
acceptable. Other operators may come to different conclusions for their own 
zones.

Re: suitability for operators – MTL works for various types of operational 
profiles and was designed to accommodate various zone sizes, including large 
TLD zones. As an example, MTL can produce new full and condensed signatures 
during every zone update, after a batched update, and in support of dynamic 
signing. The exact benefits one achieves vary depending on how an operator 
implements MTL, e.g., a dynamic signer that batches multiple RRSIGs into one 
signed MTL would be faster than one that creates multiple separate MTLs for 
each RRSIG because MTL reduces the number of PQ signatures needed. Our 
experience is with COM and NET zones, so feedback on other operational profiles 
would help us improve guidance in the draft!

A final point we want to emphasize is we as a DNS community should approach the 
PQ challenges as a both-and. We recognize that ML-DSA-44 may be acceptable for 
many operators, but MTL has considerable benefits for larger zone operators and 
enables economical deployment of PQ DNSSEC. More broadly, MTL can also promote 
cryptographic agility. The general approach is suited for both larger 
parameters of ML-DSA (e.g., ML-DSA-87) and other algorithms like SLH-DSA, so 
work on MTL now hardens DNSSEC against future cryptographic surprises while 
also enabling the mentioned benefits for operators in the near term.

Looking forward to continuing this discussion on the list, at OARC, and at IETF 
127.

[1] https://datatracker.ietf.org/doc/draft-kaizer-dnsop-ml-dsa-mtl-dnssec/
[2] 
https://datatracker.ietf.org/doc/draft-hdong-dnsop-ml-dsa-mtl-dnssec-sigtag-ext/

Thanks!
Swapneel Sheth


On 10/20/26, 4:33 AM, "Peter Thomassen" <[email protected] 
<mailto:[email protected]> <mailto:[email protected] 
<mailto:[email protected]>>> wrote:




Caution: This email originated from outside the organization. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe. 




All,




The Meetecho recording, slides and minutes of the DNSOP interim-2026-dnsop-02 
meeting on PQ DNSSEC are available via datatracker:




https://secure-web.cisco.com/1N24ST3STVL25Dyf0474aGbDvvHB6eNRDQp7RDNnFF_pT9odxt7FTD9oQYEFq89r78g4dFmGUu3bbMwaVMQ5lSqfphZOCQvrAc82Zs11ON2FDLWtPGMmaYTJCJGswPHGcAr6qG6xK8iZ-n1yigYkBK3BNCP7tofF9OJ364gL-_U9m_WrLiZe2sWOtIYrnP8d_NDIYBdSwHeKm3uOOTPD-TYp-luQ6Lw8gKhi9Lw_eRmfdebKPSRGVZXmnFuWODNkmVJNmxaAkWKIgnwxIDmjU3vVIvDqcLDO1-hutWOjuyPQ/https%3A%2F%2Fdatatracker.ietf.org%2Fmeeting%2Finterim-2026-dnsop-02%2Fsession%2Fdnsop
 
<https://secure-web.cisco.com/1N24ST3STVL25Dyf0474aGbDvvHB6eNRDQp7RDNnFF_pT9odxt7FTD9oQYEFq89r78g4dFmGUu3bbMwaVMQ5lSqfphZOCQvrAc82Zs11ON2FDLWtPGMmaYTJCJGswPHGcAr6qG6xK8iZ-n1yigYkBK3BNCP7tofF9OJ364gL-_U9m_WrLiZe2sWOtIYrnP8d_NDIYBdSwHeKm3uOOTPD-TYp-luQ6Lw8gKhi9Lw_eRmfdebKPSRGVZXmnFuWODNkmVJNmxaAkWKIgnwxIDmjU3vVIvDqcLDO1-hutWOjuyPQ/https%3A%2F%2Fdatatracker.ietf.org%2Fmeeting%2Finterim-2026-dnsop-02%2Fsession%2Fdnsop>
 
<https://secure-web.cisco.com/1N24ST3STVL25Dyf0474aGbDvvHB6eNRDQp7RDNnFF_pT9odxt7FTD9oQYEFq89r78g4dFmGUu3bbMwaVMQ5lSqfphZOCQvrAc82Zs11ON2FDLWtPGMmaYTJCJGswPHGcAr6qG6xK8iZ-n1yigYkBK3BNCP7tofF9OJ364gL-_U9m_WrLiZe2sWOtIYrnP8d_NDIYBdSwHeKm3uOOTPD-TYp-luQ6Lw8gKhi9Lw_eRmfdebKPSRGVZXmnFuWODNkmVJNmxaAkWKIgnwxIDmjU3vVIvDqcLDO1-hutWOjuyPQ/https%3A%2F%2Fdatatracker.ietf.org%2Fmeeting%2Finterim-2026-dnsop-02%2Fsession%2Fdnsop>
 
<https://secure-web.cisco.com/1N24ST3STVL25Dyf0474aGbDvvHB6eNRDQp7RDNnFF_pT9odxt7FTD9oQYEFq89r78g4dFmGUu3bbMwaVMQ5lSqfphZOCQvrAc82Zs11ON2FDLWtPGMmaYTJCJGswPHGcAr6qG6xK8iZ-n1yigYkBK3BNCP7tofF9OJ364gL-_U9m_WrLiZe2sWOtIYrnP8d_NDIYBdSwHeKm3uOOTPD-TYp-luQ6Lw8gKhi9Lw_eRmfdebKPSRGVZXmnFuWODNkmVJNmxaAkWKIgnwxIDmjU3vVIvDqcLDO1-hutWOjuyPQ/https%3A%2F%2Fdatatracker.ietf.org%2Fmeeting%2Finterim-2026-dnsop-02%2Fsession%2Fdnsop&gt;>




The chairs and PQ DNSSEC side meeting organizers think that while actual 
protocol or other standardization work can occur in DNSOP (or the new 
post-split WG once it is formed), the side meetings may still remain useful for 
implementation reports, measurements, non-IETF-draft studies, and the like.




For convenience, I have added the minutes to this email below.




Best,
Peter




---------




DNSOP WG
Interim meeting interim-2026-dnsop-02
Date: Friday October 2, 2026
Time: 1300 UTC
Chair: Benno Overeinder




Only discussion during the mic line is covered here, not the slides
You should definitely read the slides:
Minutes by Paul Hoffman




Meeting info: 
https://secure-web.cisco.com/1N24ST3STVL25Dyf0474aGbDvvHB6eNRDQp7RDNnFF_pT9odxt7FTD9oQYEFq89r78g4dFmGUu3bbMwaVMQ5lSqfphZOCQvrAc82Zs11ON2FDLWtPGMmaYTJCJGswPHGcAr6qG6xK8iZ-n1yigYkBK3BNCP7tofF9OJ364gL-_U9m_WrLiZe2sWOtIYrnP8d_NDIYBdSwHeKm3uOOTPD-TYp-luQ6Lw8gKhi9Lw_eRmfdebKPSRGVZXmnFuWODNkmVJNmxaAkWKIgnwxIDmjU3vVIvDqcLDO1-hutWOjuyPQ/https%3A%2F%2Fdatatracker.ietf.org%2Fmeeting%2Finterim-2026-dnsop-02%2Fsession%2Fdnsop
 
<https://secure-web.cisco.com/1N24ST3STVL25Dyf0474aGbDvvHB6eNRDQp7RDNnFF_pT9odxt7FTD9oQYEFq89r78g4dFmGUu3bbMwaVMQ5lSqfphZOCQvrAc82Zs11ON2FDLWtPGMmaYTJCJGswPHGcAr6qG6xK8iZ-n1yigYkBK3BNCP7tofF9OJ364gL-_U9m_WrLiZe2sWOtIYrnP8d_NDIYBdSwHeKm3uOOTPD-TYp-luQ6Lw8gKhi9Lw_eRmfdebKPSRGVZXmnFuWODNkmVJNmxaAkWKIgnwxIDmjU3vVIvDqcLDO1-hutWOjuyPQ/https%3A%2F%2Fdatatracker.ietf.org%2Fmeeting%2Finterim-2026-dnsop-02%2Fsession%2Fdnsop>
 
<https://secure-web.cisco.com/1N24ST3STVL25Dyf0474aGbDvvHB6eNRDQp7RDNnFF_pT9odxt7FTD9oQYEFq89r78g4dFmGUu3bbMwaVMQ5lSqfphZOCQvrAc82Zs11ON2FDLWtPGMmaYTJCJGswPHGcAr6qG6xK8iZ-n1yigYkBK3BNCP7tofF9OJ364gL-_U9m_WrLiZe2sWOtIYrnP8d_NDIYBdSwHeKm3uOOTPD-TYp-luQ6Lw8gKhi9Lw_eRmfdebKPSRGVZXmnFuWODNkmVJNmxaAkWKIgnwxIDmjU3vVIvDqcLDO1-hutWOjuyPQ/https%3A%2F%2Fdatatracker.ietf.org%2Fmeeting%2Finterim-2026-dnsop-02%2Fsession%2Fdnsop>
 
<https://secure-web.cisco.com/1N24ST3STVL25Dyf0474aGbDvvHB6eNRDQp7RDNnFF_pT9odxt7FTD9oQYEFq89r78g4dFmGUu3bbMwaVMQ5lSqfphZOCQvrAc82Zs11ON2FDLWtPGMmaYTJCJGswPHGcAr6qG6xK8iZ-n1yigYkBK3BNCP7tofF9OJ364gL-_U9m_WrLiZe2sWOtIYrnP8d_NDIYBdSwHeKm3uOOTPD-TYp-luQ6Lw8gKhi9Lw_eRmfdebKPSRGVZXmnFuWODNkmVJNmxaAkWKIgnwxIDmjU3vVIvDqcLDO1-hutWOjuyPQ/https%3A%2F%2Fdatatracker.ietf.org%2Fmeeting%2Finterim-2026-dnsop-02%2Fsession%2Fdnsop&gt;>
Full recording: 
https://secure-web.cisco.com/190hWsMV7Hj9rkVjydcl221LkH985nPbCuge2-TkD-YiyJxJhSxD1Za5kU3HhInTMsSy_vsIe2jYTslZVD3LVNxWvt9NCaQInfEaPA5iRzhMND250LZUpUJE-JCHfL8aGYv9Z8qtXlFtH71EiFsQkYwYX8LgSNtt923ALGZo8gb8Y0KuizKiXR3-B-KTrShizpJkDR-cCmtl_1ekG17AnPwOkZ_qJAliWYdhhyjuXjyGPmRGv6Esg8rcue-9N_T5M636oR0sOykqxO1W4kIVN1fwVD_dQaJApGaaOxO7MSw8/https%3A%2F%2Fmeetecho-player.ietf.org%2Fplayout%2F%3Fsession%3DIETF-DNSOP-20261002-1300
 
<https://secure-web.cisco.com/190hWsMV7Hj9rkVjydcl221LkH985nPbCuge2-TkD-YiyJxJhSxD1Za5kU3HhInTMsSy_vsIe2jYTslZVD3LVNxWvt9NCaQInfEaPA5iRzhMND250LZUpUJE-JCHfL8aGYv9Z8qtXlFtH71EiFsQkYwYX8LgSNtt923ALGZo8gb8Y0KuizKiXR3-B-KTrShizpJkDR-cCmtl_1ekG17AnPwOkZ_qJAliWYdhhyjuXjyGPmRGv6Esg8rcue-9N_T5M636oR0sOykqxO1W4kIVN1fwVD_dQaJApGaaOxO7MSw8/https%3A%2F%2Fmeetecho-player.ietf.org%2Fplayout%2F%3Fsession%3DIETF-DNSOP-20261002-1300>
 
<https://secure-web.cisco.com/190hWsMV7Hj9rkVjydcl221LkH985nPbCuge2-TkD-YiyJxJhSxD1Za5kU3HhInTMsSy_vsIe2jYTslZVD3LVNxWvt9NCaQInfEaPA5iRzhMND250LZUpUJE-JCHfL8aGYv9Z8qtXlFtH71EiFsQkYwYX8LgSNtt923ALGZo8gb8Y0KuizKiXR3-B-KTrShizpJkDR-cCmtl_1ekG17AnPwOkZ_qJAliWYdhhyjuXjyGPmRGv6Esg8rcue-9N_T5M636oR0sOykqxO1W4kIVN1fwVD_dQaJApGaaOxO7MSw8/https%3A%2F%2Fmeetecho-player.ietf.org%2Fplayout%2F%3Fsession%3DIETF-DNSOP-20261002-1300>
 
<https://secure-web.cisco.com/190hWsMV7Hj9rkVjydcl221LkH985nPbCuge2-TkD-YiyJxJhSxD1Za5kU3HhInTMsSy_vsIe2jYTslZVD3LVNxWvt9NCaQInfEaPA5iRzhMND250LZUpUJE-JCHfL8aGYv9Z8qtXlFtH71EiFsQkYwYX8LgSNtt923ALGZo8gb8Y0KuizKiXR3-B-KTrShizpJkDR-cCmtl_1ekG17AnPwOkZ_qJAliWYdhhyjuXjyGPmRGv6Esg8rcue-9N_T5M636oR0sOykqxO1W4kIVN1fwVD_dQaJApGaaOxO7MSw8/https%3A%2F%2Fmeetecho-player.ietf.org%2Fplayout%2F%3Fsession%3DIETF-DNSOP-20261002-1300&gt;>




Administrivia, Chairs
Opening, Note Well, Review of current WG documents 




Mic line at the end of the presentations
Peter Thomassen: Paul metioned non-NIST algorithms
Would like an overview
How to proceed: go to ML-DSA and work on TCP operations
Start with ML-DSA now and maybe switch to something better later
We can always add other algorithms later
Has concerns how MTL affects online signing
Push towards TCP might help make secure transports happen sooner
Paul: Follow the NIST mailing list to see breaks in signing from the Chinese 
competition
Stephen Farrell: Agrees with Peter
Doesn't think optimizing for TCP will help increase number of zones that are 
signed
Ben Schwartz: Finds MTL interesting
We will push ahead in all directions at once
DELEG will change the way we think about DNS over QUIC
We have ML-DSA in production
Wants to hear from validators about MTL mode
MTL and online signing: it might still come out better than current
Karl Dyson: Interested in understanding on very dynamic zones (one per second)
Would MTL cause a full redesign of the zone?
Mukund Sivaraman: Adopt ML-DSA
Good support in libraries
We would have a solution today
Likes dropping any current algorithms
We should measure resolver to authoritative traffic
Simplicity and elegance might be better in the long term than complicated
Paul: No need to adopt Bas' draft because it already has a codepoint in the 
IANA registry
Benno: Should the work be done in DNSOP or in the Security Area?
Can decide later
Ben: When sizing authoritative server, size is not as important as DoS 
protection
Authoritative fleet sizing is not that important
Running over TLS was not as big of a cost as being ready for DoS protection
Bas observation of single valid path is important
Maybe need changes to validation rules or protocol
Mohamed Boucadair: This work belongs in DNSOP
Deb Cooley: As long as you are choosing algorithms that are well-vetted, you 
can do it in DNSOP
If you are looking at new operations, you need more security review
Maybe call in CFRG if you are using non-NIST algorithms
Benno: More on the mailing list, and will be brought up again in San Francisco
PQ-DNSSEC side-meeting chairs organize helpful side-meetings and helped 
organize this meeting.
_______________________________________________
DNSOP mailing list -- [email protected] <mailto:[email protected]> 
<mailto:[email protected] <mailto:[email protected]>>
To unsubscribe send an email to [email protected] 
<mailto:[email protected]> <mailto:[email protected] 
<mailto:[email protected]>>











_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to