Re: [DNSOP] Implementation status for ZONEMD?

Benno Overeinder <benno@NLnetLabs.nl> Wed, 23 December 2020 14:25 UTC

Return-Path: <benno@NLnetLabs.nl>
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 7C7833A0FFB for <dnsop@ietfa.amsl.com>; Wed, 23 Dec 2020 06:25:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nlnetlabs.nl
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 CSlBTH8t1J8v for <dnsop@ietfa.amsl.com>; Wed, 23 Dec 2020 06:25:51 -0800 (PST)
Received: from outbound.soverin.net (outbound.soverin.net [116.202.65.218]) (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 83D613A0FF7 for <dnsop@ietf.org>; Wed, 23 Dec 2020 06:25:51 -0800 (PST)
Received: from smtp.soverin.net (unknown [10.10.3.28]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) by outbound.soverin.net (Postfix) with ESMTPS id C325A60157 for <dnsop@ietf.org>; Wed, 23 Dec 2020 14:25:48 +0000 (UTC)
Received: from smtp.soverin.net (smtp.soverin.net [159.69.232.142]) by soverin.net
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nlnetlabs.nl; s=soverin; t=1608733548; bh=onJHaWO8ZlvxUx5yAlwjlOiblOjH8mOpc6TeDrwBl6k=; h=To:References:From:Subject:Date:In-Reply-To:From; b=SDhLBw892ohar9KlVifRVxMnBzuPoIUq9WF0OKen0hmVIbsxv0uOGBonMloB2+75M hIStnZ8JWl2S2buNhkXlqMRzVUgEFpTOvcW6KwjwAGE21Frolt6fONgR93qPX0SJkh buj33mEjkQR6W9vZPMCSYHbkpRzXVlWtja6q6cnUCa9me3opHu7vQNzdDr4y61p6IU Oh4muBtIDnrD3+AG+16jhTa87iR56L/oZ1qkCVcRNyuoJ/K58IVQSbM4gHm3eSRbAl Sgef7s0nNu6DvTRXcoLEvrZNXQEX+svZjVN+y95Lbhm4HAihSLV8Ie7vdM5vPNmp6/ EvQPehpvq0YJA==
To: dnsop@ietf.org
References: <ED068CDB-A808-457D-8A99-A834B4E5FA19@icann.org> <8327f72a-295a-44f4-4f50-84485f47df4a@NLnetLabs.nl> <dfad87c7-c96e-9ecb-8341-b979e294f9e5@nlnetlabs.nl>
From: Benno Overeinder <benno@NLnetLabs.nl>
Message-ID: <6d2a5141-b8c5-777e-4650-343772ed3521@NLnetLabs.nl>
Date: Wed, 23 Dec 2020 15:25:43 +0100
MIME-Version: 1.0
In-Reply-To: <dfad87c7-c96e-9ecb-8341-b979e294f9e5@nlnetlabs.nl>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Mlr5OiE8NB6ENokbZ6OxKpMlGTI>
Subject: Re: [DNSOP] Implementation status for ZONEMD?
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: Wed, 23 Dec 2020 14:25:54 -0000

On 22/12/2020 10:27, Willem Toorop wrote:
> Recently, also the ldns library has been extended with zone-digest
> functionality. ZONEMD RRs can now be calculated and added with
> ldns-signzone , and verified with ldns-verify-zone .
> This is available on the develop branch on
> 
> 	https://github.com/NLnetLabs/ldns
> 
> this will also be released early next year.

With ZONEMD verification in ldns-verify-zone, and CreDNS zone 
verification mechanism in NSD, there is also support for ZONEMD 
verification in NSD (not signing!).  With a zone transfer (inbound), 
NSD/CreDNS verifies the zone integrity using ldns-verify-zone.  Only if 
the zone is correct will the zone be transferred (outbound) to (public) 
secondary name servers.

See also the IETF 109 DNSOP WG presentation of Willem: 
https://datatracker.ietf.org/meeting/109/materials/slides-109-dnsop-sessb-dns-hackathon-results-00.

Best,

-- Benno

-- 
Benno J. Overeinder
NLnet Labs
https://www.nlnetlabs.nl/