Re: [DNSOP] Current status of draft-ietf-dnsop-dnssec-validator-requirements

Andrew McConachie <andrew@depht.com> Mon, 05 June 2023 11:37 UTC

Return-Path: <andrew@depht.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BCA0C151063; Mon, 5 Jun 2023 04:37:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cEuB95MRUH3H; Mon, 5 Jun 2023 04:37:25 -0700 (PDT)
Received: from mout-b-105.mailbox.org (mout-b-105.mailbox.org [195.10.208.50]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 86F77C15155B; Mon, 5 Jun 2023 04:37:22 -0700 (PDT)
Received: from smtp2.mailbox.org (smtp2.mailbox.org [10.196.197.2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-b-105.mailbox.org (Postfix) with ESMTPS id 4QZWmY049pz9v39; Mon, 5 Jun 2023 13:37:17 +0200 (CEST)
From: Andrew McConachie <andrew@depht.com>
To: Tim Wicinski <tjw.ietf@gmail.com>
Cc: dnsop <dnsop@ietf.org>, dnsop-chairs <dnsop-chairs@ietf.org>
Date: Mon, 05 Jun 2023 13:36:59 +0200
Message-ID: <9C2BA6CA-E4B5-4EC0-B3BC-F9B3C5B3E413@depht.com>
In-Reply-To: <CADyWQ+FBu991wu4ZEwKs9w-hGQfUR0oOGXruQv1BwX63NsNhBw@mail.gmail.com>
References: <CADyWQ+FBu991wu4ZEwKs9w-hGQfUR0oOGXruQv1BwX63NsNhBw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/vlZvCEe21dJR6MWM0Nrm9X4OVuQ>
Subject: Re: [DNSOP] Current status of draft-ietf-dnsop-dnssec-validator-requirements
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Jun 2023 11:37:26 -0000

As this document’s shepherd, FWIW I think that if the document does 
proceed in the WG it needs significant love and attention. The document 
in its current state is not well written and it would require 
significant labor to resolve its numerous grammar and linguistic issues. 
It’s also very long and if the authors want to continue with it they 
should consider shortening it or breaking it up into multiple more 
targetted drafts.

My $0.02.

-Andrew

On 30 May 2023, at 0:58, Tim Wicinski wrote:

> All,
>
> The chairs want to thank everyone for the feedback on this document
> recently.  We've been in discussions with Warren and the authors about 
> this
> document, and we have some questions we'd like the working group to 
> help us
> resolve.
>
> While this work was relevant when it was first written and adopted, we 
> feel
> that over time the DNSSEC landscape has changed and this document may 
> not
> be as relevant as it once was.
>
> Questions to consider:
>
> Should this draft be removed from the WG?
> Are there fundamental issues that need to be addressed in this 
> document?
> Are there items in the document that should be moved to another 
> document?
>
> The chairs are currently considering abandoning this document in its
> current state.  We'd like to hear from others on this.
>
> We're going to let comments run for two weeks, and wrap up June 12, 
> 2023.
>
> Thanks
> tim
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop