IETF Logo Mail Archive

Re: [DNSOP] I-D Action: draft-ietf-dnsop-extended-error-04.txt

Stephane Bortzmeyer <bortzmeyer@nic.fr> Thu, 14 February 2019 19:28 UTC

Return-Path: <stephane@sources.org>
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 62A2F12EB11 for <dnsop@ietfa.amsl.com>; Thu, 14 Feb 2019 11:28:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 S7QVPa1E8lgv for <dnsop@ietfa.amsl.com>; Thu, 14 Feb 2019 11:28:09 -0800 (PST)
Received: from ayla.bortzmeyer.org (ayla.bortzmeyer.org [92.243.4.211]) (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 656201289FA for <dnsop@ietf.org>; Thu, 14 Feb 2019 11:28:09 -0800 (PST)
Received: by ayla.bortzmeyer.org (Postfix, from userid 10) id 453D0A07C9; Thu, 14 Feb 2019 20:28:06 +0100 (CET)
Received: by mail.sources.org (Postfix, from userid 1000) id D5051190673; Thu, 14 Feb 2019 20:25:37 +0100 (CET)
Date: Thu, 14 Feb 2019 20:25:37 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Petr Špaček <petr.spacek@nic.cz>
Cc: dnsop@ietf.org
Message-ID: <20190214192537.ti7oaylw63y36cw7@sources.org>
References: <154689301066.32204.17312124670782800354@ietfa.amsl.com> <ybl1s5nxgau.fsf@w7.hardakers.net> <3c2ef704-148f-ed03-26a9-8ea29256acc2@nic.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <3c2ef704-148f-ed03-26a9-8ea29256acc2@nic.cz>
X-Transport: UUCP rules
X-Operating-System: Debian GNU/Linux 9.6
X-Charlie: Je suis Charlie
User-Agent: NeoMutt/20170113 (1.7.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/pg2yZ-_aPEP7SlIBae8lHFluvdg>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-extended-error-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: Thu, 14 Feb 2019 19:28:13 -0000

On Thu, Feb 07, 2019 at 04:47:01PM +0100,
 Petr Špaček <petr.spacek@nic.cz> wrote 
 a message of 129 lines which said:

> > 4.1.1.  NOERROR Extended DNS Error Code 1 - Unsupported DNSKEY Algorithm
> > 
> >    The resolver attempted to perform DNSSEC validation, but a DNSKEY
> >    RRSET contained only unknown algorithms.  The R flag should be set.
> > 
> > 4.1.2.  NOERROR Extended DNS Error Code 2 - Unsupported DS Algorithm
> > 
> >    The resolver attempted to perform DNSSEC validation, but a DS RRSET
> >    contained only unknown algorithms.  The R flag should be set.
> 
> Why R flag? This is not an error, resolution suceeded,

But without the AD flag.

> and there is nothing to retry. I propose change both cases to "The R
> flag should not be set."

In both cases, because another resolver may know other, different
algorithms and therefore succeed to validate.

v2.14.0 | Report a Bug | By Email