[DNSOP] IETF 102 Hackathon: prototype implementation of draft-wessels-dns-zone-digest-02

Shane Kerr <shane@time-travellers.org> Sun, 15 July 2018 18:37 UTC

Return-Path: <shane@time-travellers.org>
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 7EC74128CF3 for <dnsop@ietfa.amsl.com>; Sun, 15 Jul 2018 11:37:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 frMhOGuVg4fk for <dnsop@ietfa.amsl.com>; Sun, 15 Jul 2018 11:37:54 -0700 (PDT)
Received: from time-travellers.org (c.time-travellers.nl.eu.org [IPv6:2a02:2770::21a:4aff:fea3:eeaa]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD3B1127598 for <dnsop@ietf.org>; Sun, 15 Jul 2018 11:37:53 -0700 (PDT)
Received: from [2001:67c:370:128:72e7:8f03:3ad9:63f1] by time-travellers.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <shane@time-travellers.org>) id 1felw3-0000XI-SN for dnsop@ietf.org; Sun, 15 Jul 2018 18:39:55 +0000
To: dnsop@ietf.org
From: Shane Kerr <shane@time-travellers.org>
Message-ID: <3e5675e4-3ae0-f21c-7e3a-e9214953888e@time-travellers.org>
Date: Sun, 15 Jul 2018 14:37:49 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/-9fhg2sDqq3Cafr58Q2mQyYRv5s>
Subject: [DNSOP] IETF 102 Hackathon: prototype implementation of draft-wessels-dns-zone-digest-02
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.27
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: Sun, 15 Jul 2018 18:37:57 -0000

Bonjour,

I decided to implement draft-wessels-dns-zone-digest-02 at the IETF 102 
Hackathon. As expected, it is fairly straightforward. You can see the 
code on GitHub:

https://github.com/shane-kerr/ZoneDigestHackathon

It seems to work, although since I have no other implementation to 
compare against I can't be sure that the digest values are in any way 
correct.

In proper hackathon style there are no tests. Bugs surely abound. If you 
use it in production please keep a fire extinguisher handy.

I found the draft to be clear and fairly complete, although I have a few 
suggestions:

* It might be worth mentioning that names are expected to be
   uncompressed. It's kind of obvious, but it might trick up some
   implementations.

* The TTL of the ZONEMD record has to come from somewhere. It can either
   come from configuration or pulled from somewhere else (I used the TTL
   of the SOA record). This should be documented.

* It might be worthwhile giving some recommendations or even
   requirements about what to do with failures. For example, something
   like "secondary servers who receive a zone that fails a digest
   validation SHOULD NOT serve the zone".

* Having some example zones and the expected digest values would be very
   useful for implementers.

As a final note, while it is awesome to have dnspython available to do 
such projects, dnspython is not a joy to work with. I had a brief 
discussion with some other hackathon attendees and it seems to be a 
shared experience. I was encouraged to look at the getdns Python API, 
which has apparently had quite some thought in making it Pythonic. I may 
look at that or making a pure Python version of it at some point in the 
future. If you have other suggestions for DNS in Python feel free to 
contact me off-list (since this isn't a software development list).

Cheers,

--
Shane