Re: [DNSOP] Please review the definitions around "recursive" in terminology-bis
P Vix <paul@redbarn.org> Mon, 12 March 2018 17:21 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 9657E126B72 for <dnsop@ietfa.amsl.com>; Mon, 12 Mar 2018 10:21:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 4njtkTY779XJ for <dnsop@ietfa.amsl.com>; Mon, 12 Mar 2018 10:21:55 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 37140126579 for <dnsop@ietf.org>; Mon, 12 Mar 2018 10:21:55 -0700 (PDT)
Received: from [10.0.6.89] (p2E5A559B.dip0.t-ipconnect.de [46.90.85.155]) (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 486777594B for <dnsop@ietf.org>; Mon, 12 Mar 2018 17:21:54 +0000 (UTC)
Date: Mon, 12 Mar 2018 17:21:48 +0000
User-Agent: K-9 Mail for Android
In-Reply-To: <5495D079-93C8-4A61-9329-DBB3AD3D2B67@vpnc.org>
References: <5495D079-93C8-4A61-9329-DBB3AD3D2B67@vpnc.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----XYLGJWR309HFOS6L75RR7ALOU8G63G"
Content-Transfer-Encoding: 7bit
To: dnsop@ietf.org
From: P Vix <paul@redbarn.org>
Message-ID: <0BCEBFC2-D933-4539-9604-2479E3FB16CD@redbarn.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/vkOafRBQFuXKk0tDpjxz8tiN5PM>
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 17:21:57 -0000
No cc. I call them full resolved not recursive resolvers. I thought 1034 also did. On March 12, 2018 3:09:27 PM UTC, Paul Hoffman <paul.hoffman@vpnc.org> wrote: >Greetings. The definition of "recursive resolver" has been problematic >both in RFC 7719 and in draft-ietf-dnsop-terminology-bis. Section 6 of >draft-ietf-dnsop-terminology-bis defines a bunch of terms about >servers, >including "recursive mode" and "recursive resolver". The current text >gives: > > Recursive mode: A resolution mode of a server that receives DNS > queries and either responds to those queries from a local cache >or > sends queries to other servers in order to get the final answers > to the original queries. Section 2.3 of [RFC1034] describes this > as "The first server pursues the query for the client at another > server". A server operating in recursive mode may be thought of > as having a name server side (which is what answers the query) >and > a resolver side (which performs the resolution function). >Systems > operating in this mode are commonly called "recursive servers". > Sometimes they are called "recursive resolvers". While strictly > the difference between these is that one of them sends queries to > another recursive server and the other does not, in practice it >is > not possible to know in advance whether the server that one is > querying will also perform recursion; both terms can be observed > in use interchangeably. > > Recursive resolver: A resolver that acts in recursive mode. In > general, a recursive resolver is expected to cache the answers it > receives (which would make it a full-service resolver), but some > recursive resolvers might not cache. > >That is, "recursive mode" is only barely defined in RFC 1034, and >"recursive resolver" is defined almost trivially. > >Can these be improved on? This is one of the core ideas in the DNS >protocol and it seems a bit weird that we don't have a crisp set of >definitions. If there is more text from RFCs to quote, that would >possibly be a big help. > >--Paul Hoffman > >_______________________________________________ >DNSOP mailing list >DNSOP@ietf.org >https://www.ietf.org/mailman/listinfo/dnsop -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
- [DNSOP] Please review the definitions around "rec… Paul Hoffman
- Re: [DNSOP] Please review the definitions around … Joe Abley
- Re: [DNSOP] Please review the definitions around … P Vix
- Re: [DNSOP] Please review the definitions around … Paul Hoffman
- Re: [DNSOP] Please review the definitions around … Evan Hunt
- Re: [DNSOP] Please review the definitions around … Paul Vixie