IETF Logo Mail Archive

Re: [Add] Designated Resolver Terminology

Tommy Pauly <tpauly@apple.com> Fri, 05 March 2021 17:53 UTC

Return-Path: <tpauly@apple.com>
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 12CF23A2916 for <add@ietfa.amsl.com>; Fri, 5 Mar 2021 09:53:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.366
X-Spam-Level:
X-Spam-Status: No, score=-2.366 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.248, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.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 8jlQIJncAc4J for <add@ietfa.amsl.com>; Fri, 5 Mar 2021 09:53:57 -0800 (PST)
Received: from ma1-aaemail-dr-lapp03.apple.com (ma1-aaemail-dr-lapp03.apple.com [17.171.2.72]) (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 4B3E53A2915 for <add@ietf.org>; Fri, 5 Mar 2021 09:53:57 -0800 (PST)
Received: from pps.filterd (ma1-aaemail-dr-lapp03.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp03.apple.com (8.16.0.42/8.16.0.42) with SMTP id 125HqYPY053834; Fri, 5 Mar 2021 09:53:56 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=from : message-id : content-type : mime-version : subject : date : in-reply-to : cc : to : references; s=20180706; bh=pLS7BIzcOzBqvRjcYa6FNL2dgHUd3y52yqao2cCzHnI=; b=krCfuuPgQP/EU2vJIiPwNhzT85IeT6sFdpNTSVNNOLXQAgD9JQzaFijKvSEX9VKq7HTa +S1JwYrDYbi8a87Yw+/lWHvk8HyTItcdtjaGr3MigWcEmXJTdUoABP6vpvaBVISro5fT awW8+m2aR0e77r0GYtPl2EdB/USocEQqe176ou/qilmefP4Ub6X5enKVEtrYh8E06Isd ZMZvJBsOAQqGa3Zvphmsin+WOHvDjHvVKXe8sD2oXhmB+2+CFSdaGrEfgJDtsh5AKFLQ XK/gj39evDG87E8e+vWX6Y1USxWBtF3ho7ZVkr3hP/PpZk5pn7t8m7J4innflyL9Ce+Y zA==
Received: from rn-mailsvcp-mta-lapp04.rno.apple.com (rn-mailsvcp-mta-lapp04.rno.apple.com [10.225.203.152]) by ma1-aaemail-dr-lapp03.apple.com with ESMTP id 36yny1j9k5-4 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 05 Mar 2021 09:53:56 -0800
Received: from rn-mailsvcp-mmp-lapp04.rno.apple.com (rn-mailsvcp-mmp-lapp04.rno.apple.com [17.179.253.17]) by rn-mailsvcp-mta-lapp04.rno.apple.com (Oracle Communications Messaging Server 8.1.0.7.20201203 64bit (built Dec 3 2020)) with ESMTPS id <0QPI00XJECDVHA00@rn-mailsvcp-mta-lapp04.rno.apple.com>; Fri, 05 Mar 2021 09:53:55 -0800 (PST)
Received: from process_milters-daemon.rn-mailsvcp-mmp-lapp04.rno.apple.com by rn-mailsvcp-mmp-lapp04.rno.apple.com (Oracle Communications Messaging Server 8.1.0.7.20201203 64bit (built Dec 3 2020)) id <0QPI00N00C6DXY00@rn-mailsvcp-mmp-lapp04.rno.apple.com>; Fri, 05 Mar 2021 09:53:55 -0800 (PST)
X-Va-A:
X-Va-T-CD: 853e6b44f09d35456c14a531d0e3b2cf
X-Va-E-CD: cb05be34af746a3bc8d3d432504d8ef2
X-Va-R-CD: ea8a835c4e9abcc7bff0f3ce208e4996
X-Va-CD: 0
X-Va-ID: 69f87a7f-a8dd-485b-9634-10d77cd4f15f
X-V-A:
X-V-T-CD: 853e6b44f09d35456c14a531d0e3b2cf
X-V-E-CD: cb05be34af746a3bc8d3d432504d8ef2
X-V-R-CD: ea8a835c4e9abcc7bff0f3ce208e4996
X-V-CD: 0
X-V-ID: 1ab8f339-2a9d-411d-9896-fb511ce0b386
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369, 18.0.761 definitions=2021-03-05_13:2021-03-03, 2021-03-05 signatures=0
Received: from smtpclient.apple (unknown [17.11.110.245]) by rn-mailsvcp-mmp-lapp04.rno.apple.com (Oracle Communications Messaging Server 8.1.0.7.20201203 64bit (built Dec 3 2020)) with ESMTPSA id <0QPI00IFBCDUDK00@rn-mailsvcp-mmp-lapp04.rno.apple.com>; Fri, 05 Mar 2021 09:53:55 -0800 (PST)
From: Tommy Pauly <tpauly@apple.com>
Message-id: <2C5D1986-C1E4-42AF-AA8D-7703335F6183@apple.com>
Content-type: multipart/alternative; boundary="Apple-Mail=_3785853D-788D-4CA9-9F65-2EBB427E1465"
MIME-version: 1.0 (Mac OS X Mail 14.0 \(3654.80.0.2.6\))
Date: Fri, 05 Mar 2021 09:53:54 -0800
In-reply-to: <SN6PR07MB54560A1E0490F01353D15B94C0969@SN6PR07MB5456.namprd07.prod.outlook.com>
Cc: "add@ietf.org" <add@ietf.org>
To: Jim Mozley <jmozley@INFOBLOX.COM>
References: <SN6PR07MB54560A1E0490F01353D15B94C0969@SN6PR07MB5456.namprd07.prod.outlook.com>
X-Mailer: Apple Mail (2.3654.80.0.2.6)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369, 18.0.761 definitions=2021-03-05_13:2021-03-03, 2021-03-05 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/-OD9bQ1keBMwfw2Er3-VQN3f-fw>
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: Fri, 05 Mar 2021 17:53:59 -0000

Hi Jim,

Yes, there is a different use of the term between the documents. The adopted draft is trying to have the right terminology to describe the intent of the mechanism for discovering capabilities via SVCB records as described.

Fundamentally, the mechanism in draft-pauly-add-resolver-discovery is also discovering resolvers based off of SVCB records. The difference lies in which party is designating: a resolver designating another resolver, and a domain owner designating a resolver. I think we could start calling the latter case (in the document not adopted) "Domain-Designated Resolver” or something similar. We can update that some time.

Best,
Tommy

> On Mar 5, 2021, at 5:35 AM, Jim Mozley <jmozley@INFOBLOX.COM> wrote:
> 
> Hi ADD,
>  
> A question on Designated Resolver terminology.
>  
> The draft Adaptive DNS Resolver Discovery https://tools.ietf.org/html/draft-pauly-add-resolver-discovery-01#section-2 <https://tools.ietf.org/html/draft-pauly-add-resolver-discovery-01#section-2> has the following definition:
>  
> “Designated Resolver:  A DNS resolver that is designated as a responsible resolver for a given domain or zone.  Designated resolvers use encrypted transports.”
>  
> I do realise that this draft has expired on 14th January.
>  
> Whereas https://www.ietf.org/archive/id/draft-ietf-add-ddr-00.txt <https://www.ietf.org/archive/id/draft-ietf-add-ddr-00.txt> terminology has this definition:
>  
> “Designated Resolver:  A resolver, presumably an Encrypted Resolver, designated by another resolver for use in its own place. This designation can be authenticated with TLS certificates.”
>  
>  
> Does this mean that the earlier definition is no longer in use, perhaps because the draft has expired? Hence does the term Designated Resolver now only apply to a Recursive Resolver?
>  
> I believe Apple is using some of the concepts detailed in https://tools.ietf.org/html/draft-pauly-add-resolver-discovery-01 <https://tools.ietf.org/html/draft-pauly-add-resolver-discovery-01>. If there is an implementation of the earlier (expired) draft will this be updated to reflect the change in usage of the term Designated Resolver?
>  
> Jim
> --
> Jim Mozley, Threat Researcher, Infoblox
> jmozley@infoblox.com <mailto:jmozley@infoblox.com>-- 
> Add mailing list
> Add@ietf.org <mailto:Add@ietf.org>
> https://www.ietf.org/mailman/listinfo/add <https://www.ietf.org/mailman/listinfo/add>

v2.23.0 | Report a Bug | By Email