Re: [DNSOP] Obsoleting DLV

Paul Wouters <paul@nohats.ca> Tue, 02 July 2019 18:41 UTC

Return-Path: <paul@nohats.ca>
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 48AE41206D9 for <dnsop@ietfa.amsl.com>; Tue, 2 Jul 2019 11:41:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CYtSMxWdbufT for <dnsop@ietfa.amsl.com>; Tue, 2 Jul 2019 11:41:54 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39C651200D5 for <dnsop@ietf.org>; Tue, 2 Jul 2019 11:41:54 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 45dY4H62kpzCty; Tue, 2 Jul 2019 20:41:51 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1562092911; bh=LoUdfePMows4qR0zETxMmc1jvQzq7NLEkrLa4Vkc698=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=NF/29xVffWA5XVcWXmwFVZBWHrTUEQKWMGu8w9iZxVEtqzlKttdNVD2XYtjkwqk/h dkirIXun4KEgIDXdLGV35wtN5TXiIczN/hAjVLUL2MjPnb6ub9E7vKl3j/XPkSN7u4 palCcw2wBVzmOcF9eaYQ76eAQP00d6JPhya3TJlY=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id tOOzSdfhU6MF; Tue, 2 Jul 2019 20:41:50 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Tue, 2 Jul 2019 20:41:49 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 29B724392C5; Tue, 2 Jul 2019 14:41:48 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca 29B724392C5
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 21DF1410A925; Tue, 2 Jul 2019 14:41:48 -0400 (EDT)
Date: Tue, 02 Jul 2019 14:41:48 -0400
From: Paul Wouters <paul@nohats.ca>
To: Matthijs Mekking <matthijs@pletterpet.nl>
cc: "dnsop@ietf.org" <dnsop@ietf.org>
In-Reply-To: <56a4b9a1-6e80-be24-0852-fe3b91869f1e@pletterpet.nl>
Message-ID: <alpine.LRH.2.21.1907021433491.19483@bofh.nohats.ca>
References: <56a4b9a1-6e80-be24-0852-fe3b91869f1e@pletterpet.nl>
User-Agent: Alpine 2.21 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/i5lAHU0v1fREDltK2GUc1-NeoxY>
Subject: Re: [DNSOP] Obsoleting DLV
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Jul 2019 18:41:56 -0000

On Tue, 2 Jul 2019, Matthijs Mekking wrote:

> So ISC plans to deprecate the feature in BIND 9.  But also I think it is
> time to move the protocol to Historic status as a clear signal to
> everyone that it should no longer be implemented or deployed.

I agree with moving DLV to historic. It is no longer needed at large,
and while it can serve a few corner cases, the only public DLV registry
has been deactivated years ago, and DLV is not universally implemented
to begin with, so one could not depend on a new to be launched DLV registry
anyways.

The draft seems to explain it well.

> Title:	  Moving DNSSEC Lookaside Validation (DLV) to Historic Status

>  https://datatracker.ietf.org/doc/draft-mekking-dnsop-obsolete-dlv/

 	"As of May 2019, the root zone is signed"

While it is correct that in May 2019, the root zone is signed, I don't
think that's the information you are trying to relay :) :) :)


3.1.1.2.  I-D.lhotka-dnsop-iana-class-type-yang

    The draft "YANG Types for DNS Classes and Resource Record Types"
    [I-D.lhotka-dnsop-iana-class-type-yang] refers to RFC 4431 to
    describe the DLV entry in the YANG module iana-dns-class-rr-type.
    This reference should be removed.

I think this does not need to be in this document, but the authors
should be requested to remove it in an update to their document.
In general, yang documents should not populate IANA registries, which
is something I raised afew months ago and the yang community is looking
at that. (and reference IANA registries instead)

And I think Ond&#345;ej  should fix up his name :)

Paul