IETF Logo Mail Archive

[DNSOP] Terminology: validating resolver

"Paul Hoffman" <paul.hoffman@vpnc.org> Mon, 02 April 2018 23:45 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 5246B127076 for <dnsop@ietfa.amsl.com>; Mon, 2 Apr 2018 16:45:46 -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 Ls_vLSZiNFpl for <dnsop@ietfa.amsl.com>; Mon, 2 Apr 2018 16:45:45 -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 06D70120721 for <dnsop@ietf.org>; Mon, 2 Apr 2018 16:45:45 -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 w32Nj53W094196 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <dnsop@ietf.org>; Mon, 2 Apr 2018 16:45:06 -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: dnsop WG <dnsop@ietf.org>
Date: Mon, 02 Apr 2018 16:45:42 -0700
X-Mailer: MailMate (1.11r5462)
Message-ID: <BE8B724E-016E-4AAB-BA6F-751A193C97DB@vpnc.org>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ubIAr2PGUlF2ETF4QFc2G26Vwbw>
Subject: [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: Mon, 02 Apr 2018 23:45:46 -0000

Some folks didn't feel all that great about this because it's not 
defined in an RFC. Specific suggestions welcome.

Validating resolver:
   A security-aware recursive name server, security-aware resolver, or
   security-aware stub resolver that is applying at least one of the
   definitions of validation (above), as appropriate to the resolution
   context.  For the same reason that the generic term "resolver" is
   sometimes ambiguous and needs to be evaluated in context,
   "validating resolver" is a context-sensitive term.

v2.23.0 | Report a Bug | By Email