Hi Roman, Please see inline.
Cheers, Med > -----Message d'origine----- > De : Roman Danyliw via Datatracker <[email protected]> > Envoyé : mercredi 9 juillet 2025 19:37 > À : The IESG <[email protected]> > Cc : [email protected]; [email protected] > Objet : Roman Danyliw's Block on charter-ietf-dnsop-04-01: (with > BLOCK and COMMENT) > > > Roman Danyliw has entered the following ballot position for > charter-ietf-dnsop-04-01: Block > > When responding, please keep the subject line intact and reply to > all email addresses included in the To and CC lines. (Feel free to > cut this introductory paragraph, however.) > > -------------------------------------------------------------------- > BLOCK: > -------------------------------------------------------------------- > > I am in agreement with Orie about the vague nature of the charter. > > I previously balloted on the -04-00 with the following feedback: > > ==[ snip ]== > ** What DNS topics are out of scope in the WG? As framed, it > appears that nearly everything related to the "DNS protocol" would > be in scope - BCPs for "DNS protocols (Sentence 1), documents from > DNS operators (Sentence 2), and "maintenance, updates, and > extensions to the DNS protocol" (Sentence 3). > > In what way is this scope different than DPRIVE, DELEG, or DNSSD > that are also defining elements of the "DNS protocol"? ==[ snip ]== > > I don't see any meaningful changes to provide restrictions to the > charter. In the discussion on my earlier comment feedback during > initial review, this WG was framed as one of last resort. I don't > see that reflected here. > > Additionally, it isn't clear under what circumstance a new DNS- > focused group would be established. Is there a consolidation > opportunity? Do we need other DNS-focused WGs (e.g., DPRIVE, DELEG, > and DNSSD)? I suspect that consolidation is not the answer, so this > suggests additions scope to capture in this charter text. [Med] OK. Updated the charter text to include: "DNS topics which are being developed in other IETF WGs are out of scope for the DNSOP WG." Also, added this text (thanks, Jim): NEW: DNS-related I-Ds that don't have an obvious WG which could adopt them can be submitted to the DNSOP WG for consideration. The DNSOP WG will advise on the appropriate way to progress these I-Ds, for instance by suggesting the most suitable WG or recommending the chartering of a new WG. > > I appreciate that the addition of the phrase "as well as other > narrowly-scoped DNS-related documents" was added to provide scope. > For me it did the opposite. > The original text "The DNSOP WG is also responsible for > maintenance, updates, and extensions to the DNS protocol" seemed to > cover nearly everything in DNS by my interpretation. Now, there is > additional scope of work that is "DNS-related" which is less clear. [Med] Removed that part. > What work is "DNS-related"? > > > -------------------------------------------------------------------- > -- > COMMENT: > -------------------------------------------------------------------- > -- > > I previously balloted on the -04-00 with the following feedback: > > ==[ snip ]== > ** Without specificity, isn't this statement of "The WG will engage > with relevant WGs and other appropriate organizations whenever > collaboration is needed" true for any WG. How does this shape the > behavior of the WG? Can it be more specific? ==[ snip ]== > > [Med] Updated to "The WG will engage with relevant WGs and other appropriate organizations whenever collaboration is needed, especially for WG adoption and Last Calls". ____________________________________________________________________________________________________________ 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]
