IETF Logo Mail Archive

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

Dick Franks <rwfranks@gmail.com> Tue, 20 June 2023 13:28 UTC

Return-Path: <rwfranks@gmail.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 0AEF5C15155E; Tue, 20 Jun 2023 06:28:42 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 IXraAAQba4v5; Tue, 20 Jun 2023 06:28:37 -0700 (PDT)
Received: from mail-vk1-xa34.google.com (mail-vk1-xa34.google.com [IPv6:2607:f8b0:4864:20::a34]) (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 8559EC151554; Tue, 20 Jun 2023 06:28:37 -0700 (PDT)
Received: by mail-vk1-xa34.google.com with SMTP id 71dfb90a1353d-464f8a20c05so1433042e0c.1; Tue, 20 Jun 2023 06:28:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1687267716; x=1689859716; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ve2XCKwNOL4yp/If+vI+BtudNtbzsvm3SUQe7uAlVYY=; b=VZw8wow/DlfMukGeGmFETdKeGoyoQSz9Ecybw41ZuXCVMZBmEDrYFCrM2XL4e9IRSx OTHEKHzeEHoMMUYJvIPC6DktaUFo35rYIizYFssH32Qzr5IPp5wRNlQ057UpH950sGhE rQQIx4fKqXnWIZ1TeZa7c9BKRiLm9vTXjbo/aCYGkNqVSdmtEFt+U3DI2etj1mLWIEUS 4oMf7AOLr4/lnV3HM1HoNJlZdSzF6mt9ps8K3rAVrqVcRG358xBLSw1jO2k6zZ23vuPB zPLu71d4kPYtM2qqS0IbCQ26c0xZNJs01QvNAmHGi5677ESihXyk2ncn4knHsZX3Ot8y 72Gw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687267716; x=1689859716; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=ve2XCKwNOL4yp/If+vI+BtudNtbzsvm3SUQe7uAlVYY=; b=jBVVsRpVcuvgnOaDPFBHBDTdhSrQ/TVDtFXAvucDZMq04FELX8PlHAJUqLF6pWx2jI NdSWCUcq0bDFXJv5fVXuhNrs7Yjyq8t25PWOaRbcj7u51MfpeXi7/C1lw1pYi1dZ4SS8 TZs2kBoC2jpHjh1mI3HLcawPfrMcXvWTobGFttL/E7MfnQ758jHn9LE1VEwsfHsNiLO6 9Nv3iQ5ym7P/Ywik1PMZVwQ2ex4t69sAjX8ex8nIfd89vL0gYAOIWs1pkXDmBhkrtpsw WLea3x5tJmCgYaSfwO6MrHP4SE0P6PIwiuHeRIUTIfsPbYoj8oEIkmXIlEr4/fEAM76Q AJpw==
X-Gm-Message-State: AC+VfDzBx4AUccnNv2Lw+4y4NQAq6nfee57N45f+ttJPsOkzMbjHgqYv iyTJU7c0uFaPBPP64aD4BdbxdBsDu74vHfSjm+fcIJL1wAQ=
X-Google-Smtp-Source: ACHHUZ4w4j6mWtuw3Idp7Jyztjf3uRggy5HXl0imofK8HrTerbEJBDXiLcYpHg72oxWvRRf8HvxmK2s+XiOBHacmANM=
X-Received: by 2002:a1f:60cf:0:b0:471:6e65:576 with SMTP id u198-20020a1f60cf000000b004716e650576mr2454931vkb.3.1687267716214; Tue, 20 Jun 2023 06:28:36 -0700 (PDT)
MIME-Version: 1.0
References: <fa6ec641-0eab-dec6-2267-3ca818402812@NLnetLabs.nl> <49112d32-e0c7-0ee0-9bdb-b1379fc8e7ce@nlnetlabs.nl>
In-Reply-To: <49112d32-e0c7-0ee0-9bdb-b1379fc8e7ce@nlnetlabs.nl>
From: Dick Franks <rwfranks@gmail.com>
Date: Tue, 20 Jun 2023 14:27:59 +0100
Message-ID: <CAKW6Ri5da0Gnb=840U1h-E_1amt8HrJbGh9Tid-DQSsTpTqAvg@mail.gmail.com>
To: Willem Toorop <willem@nlnetlabs.nl>, Roy Arends <roy@dnss.ec>
Cc: DNSOP Working Group <dnsop@ietf.org>, DNSOP Chairs <dnsop-chairs@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/EyL-79OOaXTvpKOYDu4b4DQ84V8>
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 13:28:42 -0000

On Tue, 20 Jun 2023 at 12:14, Willem Toorop <willem@nlnetlabs.nl> wrote:
>8

> 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".

The only way to discover the destination for the error report is to
repeat the original failed query adding the empty EDNS0 report channel
option.  The subsequent error report relates to the original failed
query and in no way depends upon the failure or otherwise of the
second attempt.

> ... But Section 6.1.
> Reporting Resolver Specification states: "The EDNS0 report channel
> option MUST NOT be included in queries."

-   The EDNS0 report channel option MUST NOT be included in queries.
+   The EDNS0 report channel option MUST NOT be included in report queries.


--rwf

v2.23.0 | Report a Bug | By Email