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

Dick Franks <rwfranks@gmail.com> Tue, 20 June 2023 22:36 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 11BDEC151074; Tue, 20 Jun 2023 15:36:08 -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_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 eNE8CsW9WLhX; Tue, 20 Jun 2023 15:36:06 -0700 (PDT)
Received: from mail-vs1-xe2d.google.com (mail-vs1-xe2d.google.com [IPv6:2607:f8b0:4864:20::e2d]) (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 3A8E4C15106B; Tue, 20 Jun 2023 15:36:06 -0700 (PDT)
Received: by mail-vs1-xe2d.google.com with SMTP id ada2fe7eead31-440c5960b58so487982137.3; Tue, 20 Jun 2023 15:36:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1687300565; x=1689892565; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=XP0xZxVtfh0fXpc2NK38RNG0nLuiYkhzHJH/ncBzu08=; b=eiQNDvefxR8qlu1Eu2aD2fo6SyQzSoriA1IIr5tqd4xzBr7pf1gYJtqqcgabUWXAf3 bY8Hse8AnoV6CpMhLeQ4gtsISTHhD1e3L42Mmg2dKoT5LSYpLuWIpUiYImrYubEngyvb WxyClGN/ilO37lh/tBhzKiAngu5rW5uXda7yFo219xE/Q7y0IVLFDSHGyrLkFOOs5Lkt LkizLDIJTAFVAO7Gz7ANjV9tCoHTVXG5MYfOvljLM6SbbHfMSJSzplbb4zAGz0EJMSlh PToWD0GJQETIMywoiGODi533UoByWaPwfz4gARVmxt5YPR+q8p/uZaQLhbhw73ZY8hrZ OdEg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687300565; x=1689892565; h=content-transfer-encoding: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=XP0xZxVtfh0fXpc2NK38RNG0nLuiYkhzHJH/ncBzu08=; b=hoiZFDt4QpJoRaMgQiM1yVf4X3Ue5aTOYmmD60uWLg0dGZHkEWwoo0kzA+rLigR+Wu BO8OiUr2TX0lLCHxstAG+JeAybPdU2usWl+wifsh6m0kybUUR3xZJtFKJKIx7j7Oq3AQ 5LC4thO+RoIiIDk4WwGeOuDXimf3A/0giLsDECXRfffrDWJLE0UJRZ15OBPPLtHSCPA7 8M1bJcuY/A1XxuBoyMv3Lh7XDJ5IdnLDwktp4WpemB8DsCilO5UmiJd6cAr6RsfXmQGN u1zcFwaRREy1RimFqmok2y5ZAFAP0t6w+S3qe3iy0XtWQiD4Mz5g/Romw2ZctlGQEKu7 mQTw==
X-Gm-Message-State: AC+VfDyPdNrXeIYwt0gSXcq4lG0qbIbsm3bDrxiIo8sNwbtYf/0XaflJ UsyoglXBlxMUe6ihRGh2fp1Wq9JWwmd3ssl11nc=
X-Google-Smtp-Source: ACHHUZ6n+G+1NXf0x6xIRADL58LAAnngQkGTE//6i8RtLNgszMPmV62A5PoonUlhh3uGBA+LZXuOZRdb4BSiSAVUKPA=
X-Received: by 2002:a05:6102:507:b0:440:a8c8:f34 with SMTP id l7-20020a056102050700b00440a8c80f34mr4223747vsa.3.1687300564821; Tue, 20 Jun 2023 15:36:04 -0700 (PDT)
MIME-Version: 1.0
References: <fa6ec641-0eab-dec6-2267-3ca818402812@NLnetLabs.nl> <49112d32-e0c7-0ee0-9bdb-b1379fc8e7ce@nlnetlabs.nl> <395A2004-803E-43CA-945E-F9C1EDE86F21@dnss.ec> <CAKW6Ri6BnA1xpmQLpwepBDCZa=G0FnD-QtBqqskLc9NaOn3n8w@mail.gmail.com> <62DB4990-C49F-46C6-9A72-EBFACFB835B4@dnss.ec>
In-Reply-To: <62DB4990-C49F-46C6-9A72-EBFACFB835B4@dnss.ec>
From: Dick Franks <rwfranks@gmail.com>
Date: Tue, 20 Jun 2023 23:35:28 +0100
Message-ID: <CAKW6Ri7HBG1KvDtf15vLsn8vqKbHZ6LtzUAU86RLgb4+m1YZpA@mail.gmail.com>
To: Roy Arends <roy@dnss.ec>
Cc: Willem Toorop <willem@nlnetlabs.nl>, Benno Overeinder <benno@nlnetlabs.nl>, DNSOP Working Group <dnsop@ietf.org>, DNSOP Chairs <dnsop-chairs@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/lt9_OWzyS6CTl6zzysrtoLV6HKY>
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 22:36:08 -0000

On Tue, 20 Jun 2023 at 22:20, Roy Arends <roy@dnss.ec> wrote:
>8

>
> The change was from -03 to -04 and discussed in the WG IIRC. The specific sentence your refer to was a lingering oversight in the changes from -03 to -04. I have consulted many developers on this, and so far I had no push back.
>
> > explicitly querying the authoritative server for the appropriate
> > report channel to a dependence on authoritatives attaching an
> > (unsolicited) EDNS0 report channel option to each and every query.
>
> No.
>
> An authoritative server includes the option if configured to do so AND if it has the a non-null domain name configured as the reporting channel. It will then reply to each query. This is IMHO better than having a resolver include the option each and every time. Note that resolvers will ignore options that are unknown to them.

6.2.  Authoritative server specification
Contains not a shred of normative language saying any of that.

The preliminary waffle in the overview could apply to either the
solicited or unsolicited regime.

> > I withdraw my earlier statement that the document is almost ready.
> > Now, clearly it is not.
>
> I hear you. I do not agree though, and I hope you reconsider
Not without further work

--rwf