On Nov 12, 2026, at 22:39, Kazunori Fujiwara <[email protected]> wrote: > 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.
This is an interesting question, one that we cannot answer well. In the past year, I have seen some documents that have made it through WG last call and IETF last call get DISCUSS ballots from ADs saying "this is too prescriptive", and some other documents get "this is not prescriptive enough". Saying to a DNS operator "you must make these settings in your DNS system or other DNS systems might reject your traffic" seems like the kind of thing you would hear from the Internet Police. Saying to software developers "you must only allow these settings in your DNS system or other DNS systems might reject your traffic" also feels like the Internet Police. And yet we have decades of experience that shows that some settings are harmful to the DNS as a whole, and telling DNS operators "making these settings is good for the ecosystem and will prevent some other operators from blocking you" seems like valuable advice to give. --Paul Hoffman _______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
