IETF Logo Mail Archive

Re: [DNSOP] Working Group Last call for draft-ietf-dnsop-dns-error-reporting

Willem Toorop <willem@nlnetlabs.nl> Tue, 20 June 2023 11:14 UTC

Return-Path: <willem@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 3DEB4C15154C for <dnsop@ietfa.amsl.com>; Tue, 20 Jun 2023 04:14:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R_PhZ86LuPOx for <dnsop@ietfa.amsl.com>; Tue, 20 Jun 2023 04:14:06 -0700 (PDT)
Received: from mail-ej1-x62e.google.com (mail-ej1-x62e.google.com [IPv6:2a00:1450:4864:20::62e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 60AF4C151549 for <dnsop@ietf.org>; Tue, 20 Jun 2023 04:14:05 -0700 (PDT)
Received: by mail-ej1-x62e.google.com with SMTP id a640c23a62f3a-9887ebe16d0so335308266b.2 for <dnsop@ietf.org>; Tue, 20 Jun 2023 04:14:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nlnetlabs.nl; s=google; t=1687259644; x=1689851644; h=content-transfer-encoding:in-reply-to:subject:from:content-language :references:cc:to:user-agent:mime-version:date:message-id:from:to:cc :subject:date:message-id:reply-to; bh=ogAu9s/H3sqweN9wYTMkcnpDY1GhqKoagbNc/Tplmpo=; b=RE3VRu3Ef2DXravP8SdJ9PzbYGwobqin/RPS4yOLrGViyeuVEWB/1jTRVFvtEOG+Ue Eni/JBLCVMndDBPlrSa5plsgqHdzTaLnsiPmlH2XCmRoRMS0tZsVSqiOJtGs9EZ+tLuD 2THDymJ0O6p2Tuvz/xFDdptzyGTWk0svH0glFxAGy3sq2mVwQtkxQctuKZut9Aa9sBB7 SfAgMn7vt5hxQU9IF3txmQneNqMJD2ivSUEtIgcFS6DSYVQNTWYNmyPMaETjjMWygFyx n9OV8Yeskshug8ccu50n+99QOKmMTuGKG4gTNS1pwNs6jrEk17rU8mdUM+xU1sN0ckW+ uNdw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687259644; x=1689851644; h=content-transfer-encoding:in-reply-to:subject:from:content-language :references:cc:to:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=ogAu9s/H3sqweN9wYTMkcnpDY1GhqKoagbNc/Tplmpo=; b=c6YOaJBOSFalqnwEgfTE9dPnyBe3o74GteHeZlAp+A0Zd7C5z9di6QaaWPPeQS4f3R OAEHgfpP2DzDTQiP+w9/qkJBle11JnwTh/CrIBQ4TEPtHJHxTvxZ9sXc1wGdn2Osbzya w1n3NIvHKHf4dqVxgnacOkcd3AlQl8LASmBpkGKIR3KNpDQHO6VkBAJzG1dPPe46ly6l RcCvPCwi24gLQCJVdB/yqsnvSBLVuyMAuUnsIhAZPncz5+Tmz9IvxquQGzUnYxBwXN98 gAWLFbT/Y4VzbIj7TDxB6ZHffrB0srqd3ypIZpefdVrxPpEDU9h+5q+lM5lLzRTrUr4c /uPQ==
X-Gm-Message-State: AC+VfDyDC44lPFXsdzPB7u4KM2UQquQc1c5bUCERPI2MZmAd4XG+mc4r iz1hkBg0EZLRzudrYj1sm7+mv5Pgtl5vOU3XRpo=
X-Google-Smtp-Source: ACHHUZ46AlrY+o7/j7MBhn9Darh3WXSx3LLeyR5ykbmO5XdTz+pmB56XUlu7fFwIfnYcecyHdfHWpQ==
X-Received: by 2002:a17:907:1c10:b0:988:2037:c67c with SMTP id nc16-20020a1709071c1000b009882037c67cmr7729372ejc.48.1687259643873; Tue, 20 Jun 2023 04:14:03 -0700 (PDT)
Received: from ?IPV6:2a10:3781:2851:0:a13c:3aca:31e2:c4cd? ([2a10:3781:2851:0:a13c:3aca:31e2:c4cd]) by smtp.gmail.com with ESMTPSA id b8-20020a170906660800b0096f7500502csm1210977ejp.199.2023.06.20.04.14.02 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 20 Jun 2023 04:14:03 -0700 (PDT)
Message-ID: <49112d32-e0c7-0ee0-9bdb-b1379fc8e7ce@nlnetlabs.nl>
Date: Tue, 20 Jun 2023 13:14:02 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.12.0
To: Benno Overeinder <benno@NLnetLabs.nl>, DNSOP Working Group <dnsop@ietf.org>
Cc: DNSOP Chairs <dnsop-chairs@ietf.org>
References: <fa6ec641-0eab-dec6-2267-3ca818402812@NLnetLabs.nl>
Content-Language: en-US
From: Willem Toorop <willem@nlnetlabs.nl>
In-Reply-To: <fa6ec641-0eab-dec6-2267-3ca818402812@NLnetLabs.nl>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/p3itCaLJi4voZA6jZm3h-KMCzY0>
Subject: Re: [DNSOP] Working Group Last call for draft-ietf-dnsop-dns-error-reporting
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: Tue, 20 Jun 2023 11:14:10 -0000

Op 08-06-2023 om 11:59 schreef Benno Overeinder:
> Dear DNSOP WG,
>
> The authors and the chairs feel this document has reached the stage 
> where it's ready for Working Group Last Call.
>
> This starts a Working Group Last Call for: 
> draft-ietf-dnsop-dns-error-reporting.

Dear all,

I find this is a very valuable addition to the DNS protocol for zone 
owners and authoritative operators. It also opens up potential for 
valuable future extensions, such as for example dy-run DNSSEC example ;).

I have spend a few IETF hackathons on Proof of Concept implementations, 
and I can report that it is very straight-forward to implement. The 
draft PR for Unbound that emerged from those hackathons, is already 
almost the finished feature: 
https://github.com/NLnetLabs/unbound/pull/902 (still pending the EDNS0 
opcode though!)

I have one nit.

In the Example in section 4.2., a request still "includes an empty ENDS0 
report channel". The third paragraph of that same section states 
something similar: "As support for DNS error reporting was indicated by 
a empty EDNS0 report channel option in the request". But Section 6.1. 
Reporting Resolver Specification states: "The EDNS0 report channel 
option MUST NOT be included in queries."

I believe the text in the Example section is a left over from an earlier 
version and should be corrected.


Thanks to Roy, and all the other people who worked on this!

-- Willem

>
> Current versions of the draft is available here: 
> https://datatracker.ietf.org/doc/draft-ietf-dnsop-dns-error-reporting/.
>
> The Current Intended Status of this document is: Standards Track.
>
> Please review the draft and offer relevant comments.
> If this does not seem appropriate please speak out.
> If someone feels the document is *not* ready for publication, please 
> speak out with your reasons.
> Supporting statements that the document is ready are also welcome.
>
> This starts a two week Working Group Last Call process, and ends on: 
> June 22nd, 2023.
>
> Thanks,
>
> -- Benno
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop

v2.23.0 | Report a Bug | By Email