[dns-at-ietf] Re: managing workload within and across DNS WGs

[Ondřej Surý <[e-mail]>]

Hi Wes,

this is something I've been thinking about and is related to the questions below.

With groups large in content and people like dnsop, one of the problem
that I have as a chair are the following indicators:

- Is there enough interest in the draft?
- Has there been enough reviews?
- Has the consensus been reached?

There are currently 1159 subscribers to the list, but only handful active participants
(and most of them are on this list here too).

With a broad-scope group, the active participant groups might or might not
overlap on the individual topics - there are drafts related to operators, RRRs,
developers, etc...

I think this could be one of the advantages of a split to more focused groups.
It might be easier to understand the feeling of the room because there will be
fewer clusters of people interested in the topic.

Ondrej
--
Ondřej Surý (He/Him)
[e-mail]

> On 7. 11. 2025, at 7:13, Wes Hardaker <[e-mail]> wrote:
> 
> 
> In a large number of conversations this week, and at the OPSAREA meeting
> yesterday, the topic of work overload has come up frequently.  It's not
> a problem that can be easily overcome by WG restructuring alone (as many
> have pointed out).
> 
> - What techniques can ADs and chairs use to manage WG workloads?
> 
> - What techniques can ADs and chairs use to manage IETF-wide workloads?
> 
> - How will ADs and chairs detect when too much work has been taken on?
> 
> - How will ADs and chairs detect when more work can be taken on?
> 
> - How do we prioritize work so critical ones or maybe short ones get
>  prioritized?
> 
> - How can ADs and chairs properly communicate to ensure a proper balance
>  between them has been found?  [note: assume load balancing only, not
>  moving work between groups with different charters]
> 
> - When the same volunteers exist in multiple WGs with different
>  charters, how do we ask the WGs to prioritize between their charters?
>  (or do we need to?)
> 
> I expect the results of this discussion will not necessarily affect the
> results of any potential structural changes, but rather will simply
> serve as useful input to the ADs and chairs when balancing longer term
> loads regardless of the structures in place.
> 
> -- 
> Wes Hardaker
> Google
> 
> _______________________________________________
> dns-at-ietf mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]