IETF Logo Mail Archive

Re: [DNSOP] [Ext] Starting a -bis document for RFC 8109: Initializing a DNS Resolver with Priming Queries

Paul Hoffman <paul.hoffman@icann.org> Wed, 23 September 2020 00:38 UTC

Return-Path: <paul.hoffman@icann.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 4AB7E3A09E3 for <dnsop@ietfa.amsl.com>; Tue, 22 Sep 2020 17:38:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 PbrWrE6huadM for <dnsop@ietfa.amsl.com>; Tue, 22 Sep 2020 17:38:14 -0700 (PDT)
Received: from ppa2.lax.icann.org (ppa2.lax.icann.org [192.0.33.77]) (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 B17E73A0906 for <dnsop@ietf.org>; Tue, 22 Sep 2020 17:38:11 -0700 (PDT)
Received: from MBX112-E2-CO-1.pexch112.icann.org (out.mail.icann.org [64.78.33.7]) by ppa2.lax.icann.org (8.16.0.42/8.16.0.42) with ESMTPS id 08N0c8dQ008851 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 23 Sep 2020 00:38:09 GMT
Received: from MBX112-W2-CO-1.pexch112.icann.org (10.226.41.128) by MBX112-W2-CO-2.pexch112.icann.org (10.226.41.130) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.659.4; Tue, 22 Sep 2020 17:38:08 -0700
Received: from MBX112-W2-CO-1.pexch112.icann.org ([10.226.41.128]) by MBX112-W2-CO-1.pexch112.icann.org ([10.226.41.128]) with mapi id 15.02.0659.006; Tue, 22 Sep 2020 17:38:08 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: Andrew McConachie <andrew@depht.com>
CC: dnsop WG <dnsop@ietf.org>
Thread-Topic: [DNSOP] [Ext] Starting a -bis document for RFC 8109: Initializing a DNS Resolver with Priming Queries
Thread-Index: AQHWbMX2zfbTqOapkka/9JB83XQ2Yal2H2iA
Date: Wed, 23 Sep 2020 00:38:08 +0000
Message-ID: <0A17B2D1-2011-4010-8054-4DA6D43B3C92@icann.org>
References: <93EB63F9-458B-4F16-BEDC-5CFF4132D049@icann.org> <C71A0A92-6AC2-43BC-8D04-AE695C1F6C2C@depht.com> <AAB62D09-6395-4AFB-B446-7D58C21E82F5@icann.org> <D3FEA286-FBDC-419B-A96D-38EB9A6AAD5F@depht.com>
In-Reply-To: <D3FEA286-FBDC-419B-A96D-38EB9A6AAD5F@depht.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [192.0.32.234]
x-source-routing-agent: Processed
Content-Type: multipart/signed; boundary="Apple-Mail=_33B47D2C-2758-471D-B084-B35B76EDE755"; protocol="application/pkcs7-signature"; micalg="sha-256"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235, 18.0.687 definitions=2020-09-22_21:2020-09-21, 2020-09-22 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/PVGcYKFxKU69Kl0P07Gz81GLxbg>
Subject: Re: [DNSOP] [Ext] Starting a -bis document for RFC 8109: Initializing a DNS Resolver with Priming Queries
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 23 Sep 2020 00:38:22 -0000

Sorry for the delay in getting back to you.


On Aug 7, 2020, at 7:20 AM, Andrew McConachie <andrew@depht.com> wrote:
> How about this for the last sentence, “A recursive resolver starts with no cached information about the root servers, and finishes with a full list of their names and their addresses in its cache.”

Yes, I like this. I have proposed it in our repo. Thanks!

--Paul Hoffman

v2.23.0 | Report a Bug | By Email