Re: [DNSOP] Terminology: validating resolver

"Paul Hoffman" <paul.hoffman@vpnc.org> Tue, 03 April 2018 00:13 UTC

Return-Path: <paul.hoffman@vpnc.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 195D112D889 for <dnsop@ietfa.amsl.com>; Mon, 2 Apr 2018 17:13:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 gyFDQ8tlrWcZ for <dnsop@ietfa.amsl.com>; Mon, 2 Apr 2018 17:13:33 -0700 (PDT)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (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 10B3C127076 for <dnsop@ietf.org>; Mon, 2 Apr 2018 17:13:33 -0700 (PDT)
Received: from [10.32.60.128] (50-1-51-141.dsl.dynamic.fusionbroadband.com [50.1.51.141]) (authenticated bits=0) by mail.proper.com (8.15.2/8.15.2) with ESMTPSA id w330CrFQ095571 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 2 Apr 2018 17:12:53 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 50-1-51-141.dsl.dynamic.fusionbroadband.com [50.1.51.141] claimed to be [10.32.60.128]
From: Paul Hoffman <paul.hoffman@vpnc.org>
To: George Michaelson <ggm@algebras.org>
Cc: dnsop WG <dnsop@ietf.org>
Date: Mon, 02 Apr 2018 17:13:29 -0700
X-Mailer: MailMate (1.11r5462)
Message-ID: <7E0BA54D-00F6-43F2-95F4-CCD6C8831E45@vpnc.org>
In-Reply-To: <CAKr6gn1VVUf_o51B9ZEB0nmazAawrUdObYC5_pRn2hmxy2SaGg@mail.gmail.com>
References: <BE8B724E-016E-4AAB-BA6F-751A193C97DB@vpnc.org> <CAKr6gn1VVUf_o51B9ZEB0nmazAawrUdObYC5_pRn2hmxy2SaGg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/S1x65_bSuDfyF4W3wIOFCWy0RiA>
Subject: Re: [DNSOP] Terminology: validating resolver
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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, 03 Apr 2018 00:13:34 -0000

On 2 Apr 2018, at 17:05, George Michaelson wrote:

> RFC4035 section 3.2 looks like it has usable words surely?

Maybe I'm an idiot, but I see no definition of "validating resolver" 
there.

> not from those words, but in my personal opinion, Any resolver which
> is able to understand and apply the semantic context of DNSSEC
> signatures over RR should be considered a validating resolver.
> However, a validating resolver may also be seen NOT to perform
> validation because it receives queries with the CD bit set. Therefore,
> you cannot say that all queries through a validating resolver
> necessarily demonstrate it is capable of validating. Its not entirely
> subject to external views of its behaviour without the full context of
> what was in the query received.

Errr, could you give that specific words that you would want to replace 
the current definition?

--Paul Hoffman