[email protected] writes:
> > The DNSOP WG is also responsible for maintenance, updates, and
> > extensions to the DNS protocol as well as other narrowly-scoped DNS-
> > related documents.
> >
> > What does "narrowly-scoped" mean in this context?
>
> [Med] For both questions, please refer to Andy's ballot in the last
> round:
> https://datatracker.ietf.org/doc/charter-ietf-dnsop/ballot/1072869/#charter-ietf-dnsop_andy-newton.
> Of
> course, if there is a more specific home for such work, the work will
> be done there. This is exactly who the WG used to interact with ADD,
> DPRIVE, DELEG, and so on.
IMHO, the confusing part about the current sentence is that the text
"maintenance, updates, and extensions" is wide open to anything remotely
related to the DNS and seems to directly contradict with "as well as
other narrowly-scoped DNS-related documents." IE, the wide-open first
part is followed, the way I read it, with "and maybe some other stuff
too" not as a restriction the first part. If anything, something like:
The DNSOP WG is also responsible for narrowly-scoped DNS-specific
documents that involve the maintenance, updates, and extensions to the DNS
protocol.
I'm a fan of reducing clutter generally, but it seems to me that this
pendulum has swung completely the opposite direction and the new charter
is no longer a sufficient guard against creeping scope.
Looking quickly at the length of text between this, v6ops, sidrops,
srv6ops, mops, iotops, etc there is a huge huge difference between this
very short text and the normal pattern for ops groups. The IESG should
be very careful when considering whether or not they want this sort of
minimal, fairly unrestricted wording in place or not for an ops group.
--
Wes Hardaker
USC/ISI
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]
