Re: [DNSOP] IETF meeting prep and what

Warren Kumari <> Thu, 17 June 2021 14:59 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 246363A2350 for <>; Thu, 17 Jun 2021 07:59:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.887
X-Spam-Status: No, score=-1.887 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id IBerXtwdr_jy for <>; Thu, 17 Jun 2021 07:59:34 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::12d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 3F3763A234E for <>; Thu, 17 Jun 2021 07:59:33 -0700 (PDT)
Received: by with SMTP id h4so11029133lfu.8 for <>; Thu, 17 Jun 2021 07:59:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ygK63Ak3mr0V9krDYyEKc09tusNzDKYvBAE2x7CA3do=; b=vQHt5yIEdKJQfFpEgvFZW4pOIH8RAC400DZf1ekVxfKmTaoHlfBuzVVK2lVHnkB3HZ MKR0KU9T9upJ4khldamOgBZzVq3xP3h3O4RC5lalqVfhqXbbUDfGYGv2EOGRTRKYVgxs iGdu1bgtQNe/0JLgioEOlY4wNUQvcmCZRbASOmn0B9VXhlXDQwlX8gWp42w3yPKUb6xj MOdzBX3x5qlDnK23ey1GfNVxGc5KD6eNJBboVEjBi83zZ2WfBQb4Phyxzh+Q0Dbj/CdI qzherJ3gI1YIyu9DK3YdhigvHsluY8yOa2Qy4tGvkzyJgtmEBLbUynPX0+iL6422LNm7 icXQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ygK63Ak3mr0V9krDYyEKc09tusNzDKYvBAE2x7CA3do=; b=VUNMyk4zEhVWdkgNIKSLVAwoZIC3KQqoNEQHgUMg6GDE8war2G2nvMMHStlNPBf/1c t17sEXtl+4WIyP49YQK8Bz/KyG/av7uBqH9rZK+p+5MdDFoOZCyQLb1i/WeA05NpcnKm 0SlMG0S1p8R8yhNNR/2Yc8yv8FSxv35hUz1lIIDoXRmeCAz2GZPi2Kx1toWiAek/p1bC wyGqa744MCDRHJX+CAV7t1MSrqODn8d4cy6U7DrsVS28a7uLmZZPWLnrfCBK9WEZLsGx d8/SRNwhKS+J9eN/32gdst8K5w0FJutx8tY08FTSeGZmwX4ZJjRSzwgXlt/AcxVI3adf RPtg==
X-Gm-Message-State: AOAM532T89ntK+dMYhRyNfiXU5sUe5fxzljZKPkvDwZNYO0KuGFX3OJ5 40zoHYSPM58TGbtW1yCJ3AzC64MINglLT9Nje2nozw==
X-Google-Smtp-Source: ABdhPJyfNC1BUOCliQhrpfggwgZXqn4c4GbZAJbxX1Go+7xATe83Oar3ygDfPBqBlrSa7YPY4MtApMD8ckLmu3uODak=
X-Received: by 2002:ac2:5def:: with SMTP id z15mr2758484lfq.562.1623941970283; Thu, 17 Jun 2021 07:59:30 -0700 (PDT)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Warren Kumari <>
Date: Thu, 17 Jun 2021 10:58:54 -0400
Message-ID: <>
To: Tim Wicinski <>
Cc: dnsop <>, dnsop-chairs <>
Content-Type: multipart/alternative; boundary="00000000000046617005c4f774eb"
Archived-At: <>
Subject: Re: [DNSOP] IETF meeting prep and what
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 17 Jun 2021 14:59:37 -0000

On Wed, Jun 16, 2021 at 7:39 PM Tim Wicinski <> 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
> 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.


Poorly organized data here:

> Thanks
> Benno/Suzanne/Tim
> _______________________________________________
> DNSOP mailing list

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