[DNSOP] draft-ietf-dnsop-terminology-bis and "recursive resolver"

Ted Lemon <mellon@fugue.com> Thu, 19 January 2017 18:51 UTC

Return-Path: <mellon@fugue.com>
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 1F36212952D for <dnsop@ietfa.amsl.com>; Thu, 19 Jan 2017 10:51:45 -0800 (PST)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 jbRl75f-RoF6 for <dnsop@ietfa.amsl.com>; Thu, 19 Jan 2017 10:51:36 -0800 (PST)
Received: from mail-ua0-x22b.google.com (mail-ua0-x22b.google.com [IPv6:2607:f8b0:400c:c08::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5BFF312951F for <dnsop@ietf.org>; Thu, 19 Jan 2017 10:51:36 -0800 (PST)
Received: by mail-ua0-x22b.google.com with SMTP id i68so43231578uad.0 for <dnsop@ietf.org>; Thu, 19 Jan 2017 10:51:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:mime-version:subject:message-id:date:to; bh=QdnIXdk8S/klKMrBlALHQDhhDvpQDRmz/yWaHKc+VNE=; b=ua1XH0YppkSemRKNIcbZniT0eSw54FXuQuJhmzhRoRy9nPkdZlN0h7NNDtyf6+7q/J r1uM7jWYT3Nn6tsu1VdqjoWn7Jr0CtZcVrJFRxUrxJVpJFil41cQY5i9gPKqxtQvHfb2 AxswKFrQ6uev7kbko6aaDrM+fZiCTBx9XIq/lW2FfYvGaDH5kEl7PvucBdyiwvkTa2GV JyFlI9WFRev5xv5tPGHImPF1IrelfV1WkMIAZyDtyNV4UePqTBa20pIwZOe2M1NI6s3G htBmbYcvolQq9dmtFk04X4PlUIqNMd/ZxXwM2FCnv1J7SJ9+Dqv4sPtdf3paVLvWQxk4 DO/w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:message-id:date:to; bh=QdnIXdk8S/klKMrBlALHQDhhDvpQDRmz/yWaHKc+VNE=; b=Pgt2YYfzhFUm0s9o7bTVhfM/jHcz1Bavq59EzPEWV1VmHX4goPn4+YaEJU8Av72q37 nQP7w++k3e5Wk/c5+nZWpS2C3bjld6jXGhB/3VcDz4WXkdr5+DbX1ZAIvXAFk/rkkg6o EIjzwk5lbJvmj5b3exTkkstcJx64iRhVf+WXRRgi5IIXO3nwkSshPW1t3bWTs5Ip1+Dt CW5+zB/R7VypiGZLFvLpqAMSanCNOvRZML6/9EcW2nwTs5nwNTjHJCdIxAFhEhfPgip8 QsSjZgr5wO7ZeNcw0Hv3gbfWpoyb8bIH49K02Cr34QZr/gGh+e93hZXSOuRWl0XTLgbG trGQ==
X-Gm-Message-State: AIkVDXIefwBXTQXa4qhAdxpRFPXmHXSHIFpmXhc9GkKRtXwY43XsYVB63Tf/rWaxlOzl9w==
X-Received: by 10.200.54.86 with SMTP id n22mr9695321qtb.254.1484851895038; Thu, 19 Jan 2017 10:51:35 -0800 (PST)
Received: from [192.168.1.228] (c-73-167-64-188.hsd1.ma.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id 127sm3028744qkd.3.2017.01.19.10.51.33 for <dnsop@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 19 Jan 2017 10:51:34 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_E43416B8-AF12-4886-AD20-9C3F17A538E8"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Message-Id: <02D05E11-F351-405F-8E25-8DC529425FF2@fugue.com>
Date: Thu, 19 Jan 2017 13:51:33 -0500
To: dnsop <dnsop@ietf.org>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/jKlvsFMWRtblShzGvKPqCo0L49E>
Subject: [DNSOP] draft-ietf-dnsop-terminology-bis and "recursive resolver"
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 19 Jan 2017 18:51:45 -0000

I'm updating a document for another working group, and Ralph Droms in his last call comments on that document asked me to use "recursive resolver" instead of "caching name server", referencing draft-ietf-dnsop-terminology-bis.   That document doesn't actually define "recursive resolver," but instead "full service resolver," which means almost, but not quite, the same thing.   The document does use the term "recursive resolver" fairly liberally despite there not being a definition for it.   Given that "recursive resolver" is in such common use, including in this document, I think the document should include a definition for "recursive resolver".

To me, it would make sense to say that a recursive resolver is a resolver that acts in recursive mode.   We would expect it to do caching, which would make it a full-service resolver, but it might not.