Dear Fujiwara san, It was nice talking with you on Monday.
One thought I had is that since version -04, this document has shifted toward collecting new limit values. This is slightly different from what I expected from the title "upper limit values." I was thinking not just about limits we already have, but also those we might need in the future. People are already finding ways to overwhelm DNS by taking advantage of values with no upper limits or inappropriate limits. Therefore, I was wondering if it would make sense to add a "considerations" section to discuss potential issues before they arise? The benefit is that operators can refer to a single document to understand the current default values and what else might need limits in the future. I think that would make this document both prescriptive and informative. Bashan Zuo CNNIC On Thu, Nov 12, 2026 at 10:39 PM Kazunori Fujiwara <[email protected]> wrote: > Hi DNSOP, > > We have submitted draft-fujiwara-dnsop-upper-limit-values-06. > > Title: Upper limit values for DNS > Authors: Kazunori Fujiwara > Yorgos Thessalonikefs > Name: draft-fujiwara-dnsop-dns-upper-limit-values-06.txt > Pages: 10 > Dates: 2026-11-01 > > https://datatracker.ietf.org/doc/draft-fujiwara-dnsop-dns-upper-limit-values/ > > The authors would like to ask the working group for advice on how to move > this document forward. > > Initially, we considered targeting Best Current Practice (BCP) to > recommend common upper-limit values, but it seems unlikely that we could > reach consensus on specific numbers. We then shifted our focus toward an > Informational document that surveys and compiles the upper limits across > various implementations. > > However, due to the recent wave of vulnerabilities, implementations are > continuously adding and adjusting new limits. As a result, the landscape is > shifting too rapidly for this document to stabilize anytime soon. > > We would appreciate your feedback on the following questions: > > 1. Future direction: Is there value in continuing to periodically collect > and update these implementation limits as an Informational document, or > would another approach (e.g., an IANA registry or a living wiki/repository) > be more appropriate? > 2. Minimum required limits: Rather than upper limits, we find that the > minimum baseline values (lower bounds) that implementations should support > are also undefined. Would a discussion on establishing such minimum > requirements be useful for the WG? > > Any thoughts or suggestions would be greatly appreciated. > > Best regards, > > Kazunori Fujiwara (on behalf of the authors) > _______________________________________________ > DNSOP mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
