Re: [DNSOP] I-D Action: draft-ietf-dnsop-rfc8109bis-02.txt

Florian Obser <florian+ietf@narrans.de> Sat, 16 March 2024 12:11 UTC

Return-Path: <florian+ietf@narrans.de>
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 C0929C14F609 for <dnsop@ietfa.amsl.com>; Sat, 16 Mar 2024 05:11:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nTvqLdisRcoD for <dnsop@ietfa.amsl.com>; Sat, 16 Mar 2024 05:11:47 -0700 (PDT)
Received: from imap.narrans.de (michelangelo.narrans.de [IPv6:2001:19f0:6c01:821:5400:1ff:fe33:a36d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA512) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0985CC14F5EB for <dnsop@ietf.org>; Sat, 16 Mar 2024 05:11:45 -0700 (PDT)
Received: by michelangelo.narrans.de (OpenSMTPD) with ESMTPSA id c4d47077 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO) for <dnsop@ietf.org>; Sat, 16 Mar 2024 13:11:39 +0100 (CET)
From: Florian Obser <florian+ietf@narrans.de>
To: DNSOP WG <dnsop@ietf.org>
In-Reply-To: <170594904036.14914.16859644706065209630@ietfa.amsl.com> (internet-drafts@ietf.org's message of "Mon, 22 Jan 2024 10:44:00 -0800")
References: <170594904036.14914.16859644706065209630@ietfa.amsl.com>
Date: Sat, 16 Mar 2024 13:11:38 +0100
Message-ID: <m1bk7efkat.fsf@narrans.de>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/rY8TKiIKGVLcIQ6kpDjyQ8S65mI>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-rfc8109bis-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.39
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: Sat, 16 Mar 2024 12:11:49 -0000

Sorry for being very late, I was swamped with other stuff

| 4.2.  Completeness of the Response
|
|   At the time this document is published, there are 13 root server
|   operators operating a total of more than 1500 root server instances.

There are only *12* operators, operating 13 letters. a-root and j-root
are both operated by verisign.

|   Each has one IPv4 address and one IPv6 address.  The combined size of

that's not true for the instances (there are IPv4 only instances in
operation). It's also confusing now, it could be read as "there are more
than 1500 IPv4 and IPv6 addresses in use." Of course these are anycasted
so each instance of a letter has the same IPv4/IPv6 addresses...

On 2024-01-22 10:44 -08, internet-drafts@ietf.org wrote:
> Internet-Draft draft-ietf-dnsop-rfc8109bis-02.txt is now available. It is a
> work item of the Domain Name System Operations (DNSOP) WG of the IETF.
>
>    Title:   Initializing a DNS Resolver with Priming Queries
>    Authors: Peter Koch
>             Matt Larson
>             Paul Hoffman
>    Name:    draft-ietf-dnsop-rfc8109bis-02.txt
>    Pages:   11
>    Dates:   2024-01-22
>
> Abstract:
>
>    This document describes the queries that a DNS resolver should emit
>    to initialize its cache.  The result is that the resolver gets both a
>    current NS Resource Record Set (RRset) for the root zone and the
>    necessary address information for reaching the root servers.
>
>    This document, when published, obsoletes RFC 8109.
>
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dnsop-rfc8109bis/
>
> There is also an HTMLized version available at:
> https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-rfc8109bis-02
>
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-dnsop-rfc8109bis-02
>
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts
>
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop

-- 
In my defence, I have been left unsupervised.