[DNSOP] Last Call: <draft-ietf-dnsop-resolver-priming-09.txt> (Initializing a DNS Resolver with Priming Queries) to Best Current Practice

The IESG <iesg-secretary@ietf.org> Thu, 27 October 2016 14:57 UTC

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
Message-ID: <147758022943.24671.1643494998130945117.idtracker@ietfa.amsl.com>
Date: Thu, 27 Oct 2016 07:57:09 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/0rgOKFrD8zd05UCYnlCIiUg3xPw>
Cc: Tim Wicinski <tjw.ietf@gmail.com>, joelja@gmail.com, dnsop-chairs@ietf.org, dnsop@ietf.org, draft-ietf-dnsop-resolver-priming@ietf.org
Subject: [DNSOP] Last Call: <draft-ietf-dnsop-resolver-priming-09.txt> (Initializing a DNS Resolver with Priming Queries) to Best Current Practice
Reply-To: ietf@ietf.org

The IESG has received a request from the Domain Name System Operations WG
(dnsop) to consider the following document:
- 'Initializing a DNS Resolver with Priming Queries'
<draft-ietf-dnsop-resolver-priming-09.txt> as Best Current Practice

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2016-11-10. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

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 RRSet for the root zone and the necessary address
information for reaching the root servers.

The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-dnsop-resolver-priming/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-dnsop-resolver-priming/ballot/

No IPR declarations have been submitted directly on this I-D.

The document contains these normative downward references.
See RFC 3967 for additional information:
rfc5452: Measures for Making DNS More Resilient against Forged Answers (Proposed Standard - IETF stream)
rfc4033: DNS Security Introduction and Requirements (Proposed Standard - IETF stream)
rfc3226: DNSSEC and IPv6 A6 aware server/resolver message size requirements (Proposed Standard - IETF stream)
Note that some of these references may already be listed in the acceptable Downref Registry.

[DNSOP] Last Call: <draft-ietf-dnsop-resolver-pri… The IESG