I would still keep this as "Hold for document" update. I don't see any value in adding "e.g.," to the document via errata, the updated wording could be added in the next catalog zone update together with current secure transports.
Ondrej -- Ondřej Surý (He/Him) [email protected] A gentle nudge is always appreciated if I take a little longer to reply. > On 23. 9. 2026, at 11:43, [email protected] wrote: > > Re-, > > The proposal is to separate the main guidance vs. one why to achieve it. If > we have that worded as example we don't have to handle future errata that > suggest to also list their favorite encrypted transport as Normative > reference. > > Having RFC9103 as normative is questionable. > > Cheers, > Med > >> -----Message d'origine----- >> De : Ondřej Surý <[email protected]> >> Envoyé : mercredi 23 septembre 2026 11:15 >> À : BOUCADAIR Mohamed INNOV/NET <[email protected]> >> Cc : [email protected]; [email protected]; >> [email protected]; [email protected]; [email protected]; >> [email protected]; [email protected]; >> [email protected]; [email protected]; [email protected]; >> [email protected]; [email protected] >> Objet : Re: [Technical Errata Reported] RFC9432 (9180) >> >> Hi Med, >> >>> On 23. 9. 2026, at 10:47, [email protected] wrote: >>> >>> So, if we have to make a change, the following minimal one (but >> still technical) would be more accurate IMO: >>> >>> NEW: >>> Catalog zones reveal the zones served by their consumers, >> including >>> their properties. To prevent unintentional exposure of >> catalog zone >>> contents, it is RECOMMENDED to limit the systems able to query >> them >>> and to conduct catalog zone transfers confidentially (e.g., >> [RFC9103]). >> >> I am unsure that this actually helps the implementors to do the >> right thing. >> If anyone implementing the catalog zones does not know about all >> the secure transports in DNS then they would not know about DoH or >> DoQ, so the added 'e.g.' does not provide much guidance to them >> and if they already know they will do the right thing. >> >> This feels like a change for a sake of change... >> >> Ondrej >> -- >> Ondřej Surý (He/Him) >> [email protected] >> >> A gentle nudge is always appreciated if I take a little longer to >> reply. > > ____________________________________________________________________________________________________________ > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu > ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages > electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou > falsifie. Merci. > > This message and its attachments may contain confidential or privileged > information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete > this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been > modified, changed or falsified. > Thank you. _______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
