Re: [Add] Designated Resolver Terminology
Stephen Farrell <stephen.farrell@cs.tcd.ie> Sat, 27 March 2021 18:36 UTC
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: add@ietfa.amsl.com
Delivered-To: add@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2ECC33A0C7E for <add@ietfa.amsl.com>; Sat, 27 Mar 2021 11:36:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level:
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 rXEthQdsObqv for <add@ietfa.amsl.com>; Sat, 27 Mar 2021 11:36:27 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83C103A0C64 for <add@ietf.org>; Sat, 27 Mar 2021 11:36:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 4CE8CBE2F; Sat, 27 Mar 2021 18:36:23 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TBVjm3m8AZRy; Sat, 27 Mar 2021 18:36:17 +0000 (GMT)
Received: from [10.244.2.119] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 6A38EBE1C; Sat, 27 Mar 2021 18:36:17 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1616870177; bh=VsB71b7VkLpq1Jse4OqbwhgStJe0JhQm9dfLLZxJ8B4=; h=Subject:To:References:From:Date:In-Reply-To:From; b=exm8giCFlB0LiCbRBrfIdWJUzC8/4o+s5WxaY2TZTR2eCJXofkKpzqsHxW9InTrUk tQttBMr1dZ3joRNLlCqwhw3EHvee0JhH6Rb5qWPNufMk0qfYwrnO8yHhtUPcppFYUl D0RDhpp8piAl8Mcrgrdv4hgCIVe+B6AGeuOC0R0E=
To: Bill Woodcock <woody@pch.net>, "add@ietf.org" <add@ietf.org>
References: <SN6PR07MB54560A1E0490F01353D15B94C0969@SN6PR07MB5456.namprd07.prod.outlook.com> <2C5D1986-C1E4-42AF-AA8D-7703335F6183@apple.com> <SN6PR07MB545679D87E72047C52C84355C0949@SN6PR07MB5456.namprd07.prod.outlook.com> <SN6PR07MB5456741F967AC14D0F3965CEC0639@SN6PR07MB5456.namprd07.prod.outlook.com> <D5860B50-FC40-48A0-ABC4-B68AB6BC87CE@cisco.com> <6944BB00-ADF8-471E-A7CF-1BCDC3496F7C@pch.net>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Message-ID: <68c1db2d-588a-16a7-38bf-f8ca71c3b4b5@cs.tcd.ie>
Date: Sat, 27 Mar 2021 18:36:16 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1
MIME-Version: 1.0
In-Reply-To: <6944BB00-ADF8-471E-A7CF-1BCDC3496F7C@pch.net>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="uA9eQ19HP5bWn6KwO2HtsYMjiiCSEjMmE"
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/5R5uiST_t-a3-bfW1VR-xva1_3M>
Subject: Re: [Add] Designated Resolver Terminology
X-BeenThere: add@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications Doing DNS <add.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/add>, <mailto:add-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/add/>
List-Post: <mailto:add@ietf.org>
List-Help: <mailto:add-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/add>, <mailto:add-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Mar 2021 18:36:32 -0000
On 27/03/2021 12:49, Bill Woodcock wrote: > > >> On Mar 27, 2021, at 1:25 PM, Eliot Lear >> <lear=40cisco.com@dmarc.ietf.org> wrote: >>> “Designated Authoritative Resolver” – for designated >>> authoritative resolvers >> >> In what sense is a resolver authoritative? >> >>> “Designated Caching Resolver” – for caching resolvers >> >> Which resolvers do not cache? > > Yeah, while I’m fully supportive of the goal of working out > harmonized terminology and using it ubiquitously and uniformly, > Eliot has an excellent point that the way to get there is not to > recombine terms which have specific meanings in novel and unintuitive > ways. +1 And further, I'm not sure terminology is where this WG faces a challenge, nor that new terms will help solve what I think really comes down to a challenge due to a change in who controls what. S > Sometimes a neologism is what’s needed, since it can be defined, and > nobody assumes that they know what it means, because they know what > the words mean, or how it’s used in other contexts. > > -Bill > >
- [Add] Designated Resolver Terminology Jim Mozley
- Re: [Add] Designated Resolver Terminology Tommy Pauly
- Re: [Add] Designated Resolver Terminology Jim Mozley
- Re: [Add] Designated Resolver Terminology Jim Mozley
- Re: [Add] Designated Resolver Terminology Tommy Jensen
- Re: [Add] Designated Resolver Terminology Eliot Lear
- Re: [Add] Designated Resolver Terminology Bill Woodcock
- Re: [Add] Designated Resolver Terminology Jim Mozley
- Re: [Add] Designated Resolver Terminology Jim Mozley
- Re: [Add] Designated Resolver Terminology Stephen Farrell
- Re: [Add] Designated Resolver Terminology Jim Mozley