Re: [DNSOP] IETF meeting prep and what

On Wed, Jun 16, 2021 at 7:39 PM Tim Wicinski <tjw.ietf@gmail.com> wrote:

> All
>
> The chairs have been doing prep work for the upcoming IETF meeting; one
> issue that we are working on is reaching out to authors whose working group
> documents have recently expired. While doing this, Benno did some
> datatracker stuff and ended up with this list
>
>
> https://datatracker.ietf.org/doc/search?name=draft-ietf-dnsop&sort=&olddrafts=on&by=group&group=DNSOP
>
> Which goes back to 1999 and has lots of old cruft.
>
> We chatted with our IESG Overlord Warren, and we're looking at gracefully
> removing drafts we’re unlikely to work on or advance from the datatracker’s
> view of the WG. The intent is that they won’t clutter a list that’s
> supposed to help WG chairs and contributors track what we’re actively
> working on.
>
> Our plan is to release from the WG all drafts that were last updated prior
> to 1 January 2016. This action may create some emails to the mailing list
> or the authors, and we want to make you aware of this before we start.
>
> All documents from 1 January 2016 onward are open for discussion.   For
> the older documents that are left - if someone wishes to take them on,
> please reach out.
>
Thank you very much, chairs!

While having a discussion with the IESG, I had a look at the number of
Active Drafts that we have, and compared it to other workinggroups -- DNSOP
currently has 14 listed, with 3 in some form of publication requested
(draft-ietf-dnsop-iana-class-type-yang, draft-ietf-dnsop-nsec-ttl,
draft-ietf-dnsop-rfc7816bis), leaving 11 "active" ones. Only 6 WGs have
more than this, and some of these are in states like "Implementation
needed", etc.

I think it would be good if we could try and clear some of the active queue
(and any expired WG documents that we still want to work on) before
adopting many new documents. This isn't "no new work!", but rather "let's
try to prioritize existing work first". The intent here is to allow us to
focus more on each individual document, and not have our attention
scattered between so many.

W

Poorly organized data here:
https://docs.google.com/spreadsheets/d/1AbOEkwVEIhIEPJ1TLUB92D-va7zszRlozZDkDBcYPw8/edit?usp=sharing

>
>
> Thanks
>
> Benno/Suzanne/Tim
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>

-- 
The computing scientist’s main challenge is not to get confused by the
complexities of his own making.
  -- E. W. Dijkstra