IETF Logo Mail Archive

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

Roy Arends <roy@dnss.ec> Tue, 20 June 2023 11:21 UTC

Return-Path: <roy@dnss.ec>
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 A4E21C15154C for <dnsop@ietfa.amsl.com>; Tue, 20 Jun 2023 04:21:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 (1024-bit key) header.d=dnss.ec
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 jj9ZTObIvqXS for <dnsop@ietfa.amsl.com>; Tue, 20 Jun 2023 04:21:07 -0700 (PDT)
Received: from mail-qt1-x841.google.com (mail-qt1-x841.google.com [IPv6:2607:f8b0:4864:20::841]) (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 3EA4CC151071 for <dnsop@ietf.org>; Tue, 20 Jun 2023 04:21:05 -0700 (PDT)
Received: by mail-qt1-x841.google.com with SMTP id d75a77b69052e-3fde9739e20so23391211cf.2 for <dnsop@ietf.org>; Tue, 20 Jun 2023 04:21:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dnss.ec; s=google; t=1687260064; x=1689852064; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=fUIg75bfQSfz6bmoUdZsaI7CUZcdImH0np/dWMaw6rE=; b=GRDk1F62GYdXOYLzzFwovkgpsCwvnUnf7qFyQQHwGaHZGn1WUb6EXKoAZToh9N3fGW maz4jLiUAJaBNR52jau2hJDFOc2ETaKNb0Q1aUumXQ9Dg7OTbTxKx+x2PcK1bqULee8u BscpHuawF9M0rD1/8fapLyyEDg4c7V+yu2bO4=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687260064; x=1689852064; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=fUIg75bfQSfz6bmoUdZsaI7CUZcdImH0np/dWMaw6rE=; b=k6G6Wl3K1g80yMWZ9Vl6/Q+bR7Dn3K38g0+/j+e95BBL5CI/EEbgdxc4QnN3L/NTIs LxBEbJ2sv+xqle2GSjpkjfHAjGjiRfE8atdwgpvRZCuOr9JLIF/sGCMBvQv6U9oNf+s+ i1rKMucVlJiXogdhkrigGgVCjHyJUAfBHmuD0Jo3cFmNQPsn3kZUtIEOYQLG8KKpY4JG P6FFCr7p3iMy4jKXd4wZK0ci1tCp2jNE5z/+6dsSpuOdtE/S3dEnk1wWHHoAIpukMC/2 SAqMFX3yoyxcUofnrM6lzrJ8PaFKLv3Dga2DvJ8tixrI/mCoO6SPCyk/7j5Sp3JbBkrU MORg==
X-Gm-Message-State: AC+VfDyem+v7D5Y2BnxS8SX6bmv4VF9Sb7T2RopTM7vvchsvMXycQ6Tj +CqEX8GLh4l5u74THZ6Ms8S+7A==
X-Google-Smtp-Source: ACHHUZ5iUmSDu4I8DzH3JPlq789ziCtTxaTzd5Ai9HwgNVWZ6FnEYlmb6tFGiD6i15iskrFwtqgXyg==
X-Received: by 2002:a05:622a:40b:b0:3f4:f58d:d00d with SMTP id n11-20020a05622a040b00b003f4f58dd00dmr17280003qtx.40.1687260064371; Tue, 20 Jun 2023 04:21:04 -0700 (PDT)
Received: from smtpclient.apple ([89.33.15.144]) by smtp.gmail.com with ESMTPSA id v11-20020a05622a130b00b003f3c9754e1dsm1004772qtk.17.2023.06.20.04.21.03 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 20 Jun 2023 04:21:04 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\))
From: Roy Arends <roy@dnss.ec>
In-Reply-To: <49112d32-e0c7-0ee0-9bdb-b1379fc8e7ce@nlnetlabs.nl>
Date: Tue, 20 Jun 2023 12:20:51 +0100
Cc: Benno Overeinder <benno@NLnetLabs.nl>, DNSOP Working Group <dnsop@ietf.org>, DNSOP Chairs <dnsop-chairs@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <395A2004-803E-43CA-945E-F9C1EDE86F21@dnss.ec>
References: <fa6ec641-0eab-dec6-2267-3ca818402812@NLnetLabs.nl> <49112d32-e0c7-0ee0-9bdb-b1379fc8e7ce@nlnetlabs.nl>
To: Willem Toorop <willem@nlnetlabs.nl>
X-Mailer: Apple Mail (2.3731.600.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/kOrqHNLVFpwop-LjQXNhougvL34>
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:21:11 -0000

Hoi Willem,

> On 20 Jun 2023, at 12:14, Willem Toorop <willem@nlnetlabs.nl> wrote:
> 
> 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.

Ah, yes, I will remove that sentence completely!

Thanks for the review and the work on the implementations.

Roy

> 
> 
> 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
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop

v2.23.0 | Report a Bug | By Email