Hi all,

FWIW, a slot to present the consensus conclusions by Wes/Joe is reserved in the 
OPSAREA session (2026-03-16 14:00-16:00 CST). More logistic details are 
provided below:

# Agenda: 
https://datatracker.ietf.org/meeting/125/materials/agenda-125-opsarea-00
# Calendar: https://datatracker.ietf.org/meeting/125/session/35065.ics

I expect the team to publish an updated version of the report before IETF#125. 
Pending issues (if any) will be discussed in the meeting.

Cheers,
Med

> -----Message d'origine-----
> De : Wes Hardaker <[email protected]>
> Envoyé : mardi 10 février 2026 22:26
> À : [email protected]; [email protected]
> Objet : [OPSAWG]Community consensus report on DNS WG structures at
> IETF
> 
> Greetings DNS enthusiasts,
> 
> You likely recall that last October-ish the DNS@IETF community had
> a discussion around the best way to structure work within the
> IETF.  There were many discussions on mailing lists, in meeting
> rooms, in hallways, etc.  I gathered all that feedback and met
> with Joe Abley and Lars-Johan Liman multiple times to discuss it.
> We have since distilled the feedback into a set of findings and
> *suggested* paths forward based on the findings.  We have put
> these resulting findings and suggestions into draft-hardaker-dns-
> wgs-at-ietf.
> 
> We will continue to gather responses to this draft for the rest of
> the month, after which we'll make any last changes deemed
> necessary based on any comments received and will turn it over to
> the IESG for their information.  What they choose to do with the
> information, of course, is up to them.
> 
> As a reminder, our job, as a three-person small team, was merely
> to distill the collected information and extract consensus, all
> the while leaving our personal opinions out of it as much as
> possible.  I would personally like to thank Joe and Liman for
> their willingness to help me out in this effort -- their insights
> into the evaluation and suggested paths forward proved invaluable.
> Do feel free to disagree with us and our conclusions, but we did
> try to be "just the messengers".
> 
> A link to the draft for everyone to consider is below.
> 
> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> datatracker.ietf.org%2Fdoc%2Fdraft-hardaker-dns-wgs-at-
> ietf%2F&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C6929450716
> e84c2981a708de68eb0c94%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%
> 7C639063555931559323%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRyd
> WUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%
> 3D%3D%7C0%7C%7C%7C&sdata=CZEKyXs6i8KE0FFzJmH6OhGUel5FogaDKOY9XKyYu
> kM%3D&reserved=0
> 
> When responding, please do keep the [email protected] list in
> To/CC as that is where much of the discussion has been held. 

____________________________________________________________________________________________________________
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]

Reply via email to