<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Warren,</p>
<p>I had a student (Ilyas Rahimi) doing a research project: "local
root serving by default: quantifying the traffic trade-off between
root queries and root zone distribution" [1], in which he has
measured the impact on traffic with BIND, Unbound and Knot
Resolver configured following example configurations from RFC 8806
Appendix B [2]. I think it raises interesting questions and showed
show fun results. For example the different perspective w.r.t.
timing values. Should resolvers primarily follow the TTL of the
records in the root (2 days for the non-authoritative and 1 day
for the authoritative delegation information) as those are meant
for resolvers anyway and fetch the root once a day (what Knot
Resolver does by default), or actually try to act as a real
secondary?, which (fun fact) for Unbound currently means it will
fetch the full root zone every 30 minutes (refresh timer in the
SOA) when it is configured to fetch the root over http(s) only
(because it cannot do the SOA query over http(s)).</p>
<p>Besides what is already in his report, we've also created a
incrementally signed "shadow" of all the root zones since 21st of
December 2025 here:
<a class="moz-txt-link-freetext" href="https://github.com/willem-ietf125/incremental-root">https://github.com/willem-ietf125/incremental-root</a> This repo also
includes the IXFRs from version to version (with the size) when
incrementally signed properly (i.e. no signature will be older
than 6 days, so that in the worst case the SOA expire timer goes
off before signatures start to expire)</p>
<p>Would this be interesting to have in the IEPG session? and if so,
do you still have a spot?</p>
<p>Cheers,</p>
<p>-- Willem</p>
<p>[1]
<a class="moz-txt-link-freetext" href="https://nlnetlabs.nl/downloads/publications/DNS_Local_ROOT_ResearchProject2.pdf">https://nlnetlabs.nl/downloads/publications/DNS_Local_ROOT_ResearchProject2.pdf</a></p>
<p>[2]
<a class="moz-txt-link-freetext" href="https://www.rfc-editor.org/rfc/rfc8806#name-example-configurations-of-c">https://www.rfc-editor.org/rfc/rfc8806#name-example-configurations-of-c</a></p>
<div class="moz-cite-prefix">On 2/20/26 17:21, Warren Kumari wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAHw9_iJWq_RZqWFm=DbtVQSYpw7RH3+GEe4uZRF+kvgU=A5h-A@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div>
<div>
<div
style="font-weight:400;text-decoration-style:initial;text-decoration-color:initial"
class="">Hi all,<br>
</div>
<div
style="font-weight:400;text-decoration-style:initial;text-decoration-color:initial"
class=""><br>
</div>
<div
style="font-weight:400;text-decoration-style:initial;text-decoration-color:initial"
class="">The IEPG is an informal gathering that meets on the<span
class=""> <span class=""><span class=""><span class=""><span
class="sh-date">Sunday</span></span></span></span> </span>prior
to IETF meetings. The intended theme of these meetings is
essentially one of operational relevance in some form or
fashion.<br>
</div>
<div
style="font-weight:400;text-decoration-style:initial;text-decoration-color:initial"
class=""><br>
</div>
<div
style="font-weight:400;text-decoration-style:initial;text-decoration-color:initial"
class="">We still have some open agenda time for the IEPG
session at IETF 125…</div>
<div
style="font-weight:400;text-decoration-style:initial;text-decoration-color:initial"
class=""><br>
</div>
<div
style="font-weight:400;text-decoration-style:initial;text-decoration-color:initial"
class="">These presentations / discussions are generally
around things like problems discovered when deploying
various protocols, interesting operational issues or
deployments, interesting measurement results, fun things
discovered while building networks, etc. It is much more
operationally focused than an IETF Working Group meeting,
and is not a place to just present your shiny new Internet
Draft (that's HotRFC and / or the relevant WG).<br>
</div>
<div
style="font-weight:400;text-decoration-style:initial;text-decoration-color:initial"
class=""><br>
</div>
<div
style="text-decoration-color:initial;text-decoration-style:initial;font-weight:400"
class="">
<div
style="text-decoration-color:initial;text-decoration-style:initial;font-weight:400"
class="">So, things like: "If you have a chain of CNAME
records, and one of them is at the apex of a DNS zone, the
3 largest resolver implementations all do
different things. This allows you to fingerprint resolvers
- here are some results….", or "We implemented
BGP Flowspec to allow fast response to DDoS events… and
then we pushed out a rule which blocked access to the
controller. This is what happened after that…" are all
great IEPG presentations.<br>
</div>
<div
style="text-decoration-color:initial;text-decoration-style:initial;font-weight:400"
class="">
<div class="">But "Here is my draft. It adds the Foo
extension to the Bar protocol. The format of the Foo
extension looks like this…. If a router using Bar sees
this extension, it should increment the Baz counter. The
YANG model for Foo looks like this… " is not — that
should be discussed in the Bar WG, or HotRFC, or
Dispatch, or similar…<br>
</div>
<div class=""><br>
</div>
</div>
</div>
<div
style="font-weight:400;text-decoration-style:initial;text-decoration-color:initial"
class=""><br>
</div>
<div
style="font-weight:400;text-decoration-style:initial;text-decoration-color:initial"
class="">Previous presentations are here:<span class=""> </span><a
rel="noopener noreferrer" href="http://www.iepg.org/"
style="color:rgb(84,172,220);text-decoration-line:none;text-decoration-style:initial;text-decoration-color:initial"
target="_blank" class="moz-txt-link-freetext"
moz-do-not-send="true">http://www.iepg.org/</a><br>
</div>
<div
style="font-weight:400;text-decoration-style:initial;text-decoration-color:initial"
class=""><br>
</div>
<div
style="font-weight:400;text-decoration-style:initial;text-decoration-color:initial"
class="">More info on the IEPG: RFC 1690 -<span class=""> </span><a
rel="noopener noreferrer"
href="https://tools.ietf.org/html/rfc1690"
style="color:rgb(84,172,220);text-decoration-line:none;text-decoration-style:initial;text-decoration-color:initial"
target="_blank" class="moz-txt-link-freetext"
moz-do-not-send="true">https://tools.ietf.org/html/rfc1690</a><br>
</div>
<div
style="font-weight:400;text-decoration-style:initial;text-decoration-color:initial"
class="">We will have remote participation through MeetEcho.<br>
</div>
<div
style="font-weight:400;text-decoration-style:initial;text-decoration-color:initial"
class=""><br>
</div>
<div
style="font-weight:400;text-decoration-style:initial;text-decoration-color:initial"
class="">If you have some sort of operationally relevant
topic which you'd be willing to present, please let Jen
Linkova <<a href="mailto:furry13@gmail.com"
rel="noopener noreferrer" target="_blank"
class="moz-txt-link-freetext" moz-do-not-send="true">furry13@gmail.com</a>>
or me know.<br>
</div>
<div
style="font-weight:400;text-decoration-style:initial;text-decoration-color:initial"
class=""><br>
</div>
<div
style="font-weight:400;text-decoration-style:initial;text-decoration-color:initial"
class="">Thanks, <br>
</div>
<div
style="font-weight:400;text-decoration-style:initial;text-decoration-color:initial"
class="">W<br>
</div>
</div>
<br>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre wrap="" class="moz-quote-pre">_______________________________________________
Iepg mailing list
<a class="moz-txt-link-abbreviated moz-txt-link-freetext"
href="mailto:Iepg@lists.isc.org">Iepg@lists.isc.org</a>
<a class="moz-txt-link-freetext"
href="https://lists.isc.org/mailman/listinfo/iepg">https://lists.isc.org/mailman/listinfo/iepg</a>
</pre>
</blockquote>
</body>
</html>