[DNSOP] some editorial comments on RFC9499
Michael Richardson <[email protected]> Sun, 19 Jul 2026 11:26:42 +0200
| Newsgroups | gmane.ietf.dnsop |
|---|---|
| Message-ID | <791330.1784453202@dyas> |
0) Should RFC9499 get revised again, may I suggest that the $-anchors that
RFC4949 did be used? (I wish it had been named Terminology, rather than Glossary)
{What interesting numerology about 9499 vs 4949...}
1) I'm more of a DNS RFC user than producer, and I'm kinda still annoyed that
there is no term in 9499 for public resolver. I think I said this before,
and was told that nobody could agree on a term.
Even more so that the "open resolver" entry refers to "public resolver" in
quotes, but never actually defines it.
It is unclear to me from the entry if I'm intended to call them open
resolvers, or if that term is intended to refer to resolvers which are
merely misconfigured. The RFC5358 reference pushes me to not want to
use the term open resolver.
--
Michael Richardson <[email protected]>, Sandelman Software Works
-= IPv6 IoT consulting =- *I*LIKE*TRAINS*
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]
signature.asc
(application/pgp-signature, 487 B)
-----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEERK+9HEcJHTJ9UqTMlUzhVv38QpAFAmpcmFIACgkQlUzhVv38 QpAhCAgAiISxcDI3P8W60nEJMB6cjmkLNNTsCMNNXBIUsy654PtZHo6sV1l2OW0C Qm61hiWwByTveCCmAtmQJRNKzvGtScLOur8u2sq0MblO0fcTjGEtfC8JIIE+87be y49dx6IsFZBL885WDr3KG9a+BVrrXmnGHh+9aaxeWLr2vfWCuQN+/XLKGOsCB8UR aoEKpq4qu0ZwCx8wRRUGcWRoYl4sGls6iqbE3ICe6ImegbaGtAdLxp/BfLYy6OBB GvLo1gIYaUS+yxqaNUSHwfXtRt4j0IV+BaWw9IV5ugOGnvJpIifEG0kkAmul84iD byRiwLMsNIzkBPf1zRpJiW46SqcG6A== =TgIR -----END PGP SIGNATURE-----