Re: [DNSOP] Please review the definitions around "recursive" in terminology-bis

Paul Vixie <paul@redbarn.org> Mon, 12 March 2018 21:14 UTC

Return-Path: <paul@redbarn.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 58E71126CF9 for <dnsop@ietfa.amsl.com>; Mon, 12 Mar 2018 14:14:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 vMm3fX0__GaB for <dnsop@ietfa.amsl.com>; Mon, 12 Mar 2018 14:14:02 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [24.104.150.213]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D62101200C1 for <dnsop@ietf.org>; Mon, 12 Mar 2018 14:14:02 -0700 (PDT)
Received: from [192.168.2.41] (p4FE4E7A0.dip0.t-ipconnect.de [79.228.231.160]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id B8B667594B; Mon, 12 Mar 2018 21:14:00 +0000 (UTC)
Message-ID: <5AA6ED97.1060604@redbarn.org>
Date: Mon, 12 Mar 2018 14:13:59 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 5.0.24 (Windows/20180302)
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
CC: dnsop@ietf.org
References: <5495D079-93C8-4A61-9329-DBB3AD3D2B67@vpnc.org> <0BCEBFC2-D933-4539-9604-2479E3FB16CD@redbarn.org> <4C7FAA4B-88DC-4A20-95CA-479FF27B3516@vpnc.org>
In-Reply-To: <4C7FAA4B-88DC-4A20-95CA-479FF27B3516@vpnc.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/X4izzfIoYHNAc1HoBLc9qiX37tQ>
Subject: Re: [DNSOP] Please review the definitions around "recursive" in terminology-bis
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, 12 Mar 2018 21:14:04 -0000


Paul Hoffman wrote:
> On 12 Mar 2018, at 10:21, Vix wrote:
>
>> I call them full resolved not recursive resolvers. I thought 1034 also
>> did.
>
> Not really. Please see the full text of Section 6 to see the state of
> "full resolver" and "full-service resolver".

huh.

>
> The term "recursive resolver" is used in a zillion other places, so
> defining it here will help readers understand the DNS.

as long as you don't try to call it a recursor, we'll have no trouble 
between us.

-- 
P Vixie