[DNSOP] Terminology: forwarding and forwarder

Paul Hoffman <paul.hoffman@vpnc.org> Sat, 25 April 2015 00:55 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6CC91B3212 for <dnsop@ietfa.amsl.com>; Fri, 24 Apr 2015 17:55:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.053
X-Spam-Level:
X-Spam-Status: No, score=0.053 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HELO_MISMATCH_COM=0.553] autolearn=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 jBkpohS2LFko for <dnsop@ietfa.amsl.com>; Fri, 24 Apr 2015 17:55:11 -0700 (PDT)
Received: from 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 6D0EC1B3210 for <dnsop@ietf.org>; Fri, 24 Apr 2015 17:55:11 -0700 (PDT)
Received: from [10.20.30.101] (50-1-98-218.dsl.dynamic.fusionbroadband.com [50.1.98.218]) (authenticated bits=0) by proper.com (8.15.1/8.14.9) with ESMTPSA id t3P0tAPd055742 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <dnsop@ietf.org>; Fri, 24 Apr 2015 17:55:10 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: proper.com: Host 50-1-98-218.dsl.dynamic.fusionbroadband.com [50.1.98.218] claimed to be [10.20.30.101]
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-Id: <D57A2F26-2756-4F05-B52B-9ECBDB0F125A@vpnc.org>
Date: Fri, 24 Apr 2015 17:55:09 -0700
To: "dnsop@ietf.org WG" <dnsop@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
X-Mailer: Apple Mail (2.2098)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/1GPG7Eez0kvWdhBk0A-D8ot5xck>
Subject: [DNSOP] Terminology: forwarding and forwarder
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sat, 25 Apr 2015 00:55:12 -0000

Greetings again. After the active discussion on these terms, we propose the following, which tries to hew closely to both RFCs. Comments are certainly welcome.

--Paul Hoffman

   Forwarding -- The process of one server sending a DNS query with the
   RD bit set to 1 to another server to resolve that query.  Forwarding
   is a function of a DNS resolver; it is different than simply blindly
   relaying queries.

   [RFC5625] does not give a specific definition for forwarding, but
   describes in detail what features a system that forwards need to
   support.  Systems that forward are sometimes called "DNS proxies",
   but that term has not yet been defined (even in [RFC5625]).

   Forwarder -- Section 1 of [RFC2308] describes a forwarder as "a
   nameserver used to resolve queries instead of directly using the
   authoritative nameserver chain".  [RFC2308] further says "The
   forwarder typically either has better access to the internet, or
   maintains a bigger cache which may be shared amongst many resolvers."
   That definition appears to suggest that forwarders normally only
   query authoritative servers.  In current use, however, forwarders
   often stand between stub resolvers and recursive servers.  [RFC2308]
   is silent on whether a forwarder is iterative-only or can be a full
   resolver.