Re: [DNSOP] I-D Action: draft-ietf-dnsop-svcb-https-04.txt

Pieter Lexis <pieter.lexis@powerdns.com> Mon, 22 March 2021 17:03 UTC

Return-Path: <pieter.lexis@powerdns.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 1BD553A0D5D for <dnsop@ietfa.amsl.com>; Mon, 22 Mar 2021 10:03:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.401
X-Spam-Level:
X-Spam-Status: No, score=0.401 tagged_above=-999 required=5 tests=[KHOP_HELO_FCRDNS=0.399, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no 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 b5mz0CzX_BAW for <dnsop@ietfa.amsl.com>; Mon, 22 Mar 2021 10:02:56 -0700 (PDT)
Received: from mx4.open-xchange.com (alcatraz.open-xchange.com [87.191.39.187]) (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 B08023A0D5A for <dnsop@ietf.org>; Mon, 22 Mar 2021 10:02:56 -0700 (PDT)
Received: from imap.open-xchange.com (imap.open-xchange.com [82.161.33.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx4.open-xchange.com (Postfix) with ESMTPSA id 0429F6A28B; Mon, 22 Mar 2021 18:02:53 +0100 (CET)
Received: from ananas.home.plexis.eu ([82.161.33.1]) by imap.open-xchange.com with ESMTPSA id 96KhOr3NWGDKcwAA3c6Kzw (envelope-from <pieter.lexis@powerdns.com>); Mon, 22 Mar 2021 18:02:53 +0100
To: Willem Toorop <willem@nlnetlabs.nl>, Ben Schwartz <bemasc=40google.com@dmarc.ietf.org>
Cc: dnsop <dnsop@ietf.org>
References: <161600103837.12472.4123883592260330100@ietfa.amsl.com> <CAHbrMsA3NzpY9RFNhWsvYgQ0hqcqEDuMUrw7HmGBJZ1+uaLtNA@mail.gmail.com> <600ED9AF-2C6F-429F-AF39-445E29E686EF@apple.com> <4DFDEFA6-4132-42CA-8DA7-D0537C5FC29A@isc.org> <99cdd98b-ac59-c96c-a73f-a58729c2ca52@nic.cz> <fbeb99ad-9ccc-1050-a0d2-3b6e5287ed7a@nlnetlabs.nl> <214c21bc-2d05-0c58-ba0f-4891bae0e343@powerdns.com> <b6b65c08-55c1-9f2c-a33b-29ab8e806d45@nlnetlabs.nl> <adad7e8a-280f-3ad6-4dac-eec954fe01bf@powerdns.com> <047911f1-87b8-e798-d361-9927bef7e10c@nlnetlabs.nl> <CAHbrMsCr=+Gdco9pgSeNL82Uz8162JnTDNc+LMMMkUOXsRi-RA@mail.gmail.com> <8872b377-69a1-d9dd-609e-f0258aef46aa@nlnetlabs.nl>
From: Pieter Lexis <pieter.lexis@powerdns.com>
Message-ID: <c936b4be-6771-012e-fd17-f6bf67cd34a5@powerdns.com>
Date: Mon, 22 Mar 2021 18:02:53 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1
MIME-Version: 1.0
In-Reply-To: <8872b377-69a1-d9dd-609e-f0258aef46aa@nlnetlabs.nl>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/UdqpqVJBWP4dIq1g40chXWXnopE>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-svcb-https-04.txt
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: Mon, 22 Mar 2021 17:03:01 -0000

Hi folks,

On 3/22/21 5:29 PM, Willem Toorop wrote:
> [...]
> Would be good to have that in a test vector ;).

Hence the inclusion of the unsorted keys vector :).

> Excellent! How SHOULD it enforce? By failing to load or by fixing.

This is all implementation specific of course :). For PowerDNS we don't
pre-parse the zones when serving (being a database driven server) so we
have a tool (`pdnsutil check-zone`) that will warn/error if things are
wrong with records, where we're covering most of these cases. We'll have
some sanity checking in-line (when serving), but there's no way we will
validate all constraints at runtime (we will probably when you use the
API to manipulate records, but that is not yet implemented)

> Most here tilt to *failing to load*, so these should fail to load:
> [...]
> 
> I think it would be good to have this added to the test-vectors appendix.

I'll try to update the vectors this week, changing the format and adding
some missed cases as well.

Cheers,

Pieter

-- 
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com