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

Andrew McConachie <andrew@depht.com> Thu, 06 August 2020 11:08 UTC

Return-Path: <andrew@depht.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 00C753A10FE for <dnsop@ietfa.amsl.com>; Thu, 6 Aug 2020 04:08:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=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=depht-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 rtrkU-sYYQTq for <dnsop@ietfa.amsl.com>; Thu, 6 Aug 2020 04:08:10 -0700 (PDT)
Received: from mail-il1-x134.google.com (mail-il1-x134.google.com [IPv6:2607:f8b0:4864:20::134]) (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 512F93A10FD for <dnsop@ietf.org>; Thu, 6 Aug 2020 04:08:10 -0700 (PDT)
Received: by mail-il1-x134.google.com with SMTP id p13so11587629ilh.4 for <dnsop@ietf.org>; Thu, 06 Aug 2020 04:08:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=depht-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version; bh=jMNXC7JbbubTuQrX/ofHMHaXgXkagcPQLc65s5N5wwY=; b=A52YgAUQxyyXqX3nO4F7AlUheKAv/lkML/sbS8iSuyJ4bRJMrLT2iZ+W7UI6W6dZ8O N0XUpfxPNRpwNH3bkSjU3PnMhgytP7TiibTwil4vKHBugH3UKlWmWN0kB8o99aHQSqO6 QhEkPpkrODxrGl/9+zndk6sQeJXmRs/8ujzXViRNxN31X/t8xPRfDRuJPfhQmVXQZ0LU qxqRtRZgt5PFnSaM8GifNdOJ7ad8Xx2QbPIfR2pEE6mEQH8K9stw9nzyu70nhCjmkhg4 N6hWCv3270lViLmhLuJUgG3FIsuuUTtnShxajtXhgbqGPbzgXAOvr6s1JifU3jax9YWu elnQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version; bh=jMNXC7JbbubTuQrX/ofHMHaXgXkagcPQLc65s5N5wwY=; b=bEFTthb0wS/30xL/Rmx7x39v+phSP1hKkfESF+EhJKr0PN/ZXlhjq2ZyQCKLPM1pw9 0lIavna7qDLgLo/ogxtZ6RVch68Z+LDSXOwj12urHoQNac7AJ0zzzUO2O4ED0HjsGsk7 wK2YarnQuEKXcT06PufN3AlCO7xEwYCCvI0wNluFvhJZ23LZwhtzZFOdLVHjULO4i+z8 cgH0/AvaR2kK1s7dimd4ImFxwMDAHu9gHbGKTjsQLncJeon3Zi66pE3vDzXQOSC0L3b6 eV18LVMeo6f7se1W7fY9KjyGrVVTynXvZlx4TNxProYb0b+h760/Rggo1Zz0Pkrw3yjh KMmg==
X-Gm-Message-State: AOAM530zZR2E2YGsddsEsvUk7rMEQ43EwGtqxBGAgHUUU/3EgkTBDtR+ isQqHwojH9OZU4OantE1qV83Q7Mz0Ho=
X-Google-Smtp-Source: ABdhPJyjkbogIdoq31jounmnQps5rCXtUcd9/6iCAximY7B9vlMm0Qgexn9uBPPAOM/SZ1oH1O7gFg==
X-Received: by 2002:a92:d651:: with SMTP id x17mr10271569ilp.23.1596712089537; Thu, 06 Aug 2020 04:08:09 -0700 (PDT)
Received: from [10.47.61.44] ([2a02:a212:9285:29f0:5c40:31e8:ca18:1116]) by smtp.gmail.com with ESMTPSA id h9sm3592943ilc.59.2020.08.06.04.08.07 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 06 Aug 2020 04:08:08 -0700 (PDT)
From: "Andrew McConachie" <andrew@depht.com>
To: "Paul Hoffman" <paul.hoffman@icann.org>
Cc: "dnsop WG" <dnsop@ietf.org>
Date: Thu, 06 Aug 2020 13:08:05 +0200
X-Mailer: MailMate (1.13.1r5671)
Message-ID: <C71A0A92-6AC2-43BC-8D04-AE695C1F6C2C@depht.com>
In-Reply-To: <93EB63F9-458B-4F16-BEDC-5CFF4132D049@icann.org>
References: <93EB63F9-458B-4F16-BEDC-5CFF4132D049@icann.org>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; markup=markdown
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/sy6WTHYljcXSbzTyf--GzqC1C20>
Subject: Re: [DNSOP] 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: Thu, 06 Aug 2020 11:08:12 -0000

Dear Peter, Matt and Paul,

What does it mean for a resolver to be primed, or for a resolver to not 
be primed? For example, is a resolver considered primed only if it has 
all root server names and IP addresses? 50%? At least 1?


    Priming is the act of finding the list of root servers from a
    configuration that lists some or all of the purported IP addresses 
of
    some or all of those root servers.  A recursive resolver starts with
    no information about the root servers, and ends up with a list of
    their names and their addresses.

If that were true it would be impossible for the resolver to find 
anything. It definitely starts with some information about the root 
servers. Maybe change "no information" to "this information".

Thanks,
Andrew

On 1 Jul 2020, at 1:39, Paul Hoffman wrote:

> Greetings again. Since RFC 8109 has been published, there has been 
> more discussion of what DNS priming means. This has caused the 
> document authors to see a few places where RFC 8109 could be clarified 
> and improved. Please see:
>    https://datatracker.ietf.org/doc/draft-klh-dnsop-rfc8109bis/
>
> Comments are welcome. If the WG wants to adopt this work, that would 
> be grand as well.
>
> --Paul Hoffman_______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop