[DNSOP] BCP 209, RFC 8109 on Initializing a DNS Resolver with Priming Queries

rfc-editor@rfc-editor.org Thu, 16 March 2017 00:08 UTC

Return-Path: <wwwrun@rfc-editor.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 7A5FA130153; Wed, 15 Mar 2017 17:08:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-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 uiCP00hzBUUg; Wed, 15 Mar 2017 17:08:53 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E81CA12FB9A; Wed, 15 Mar 2017 17:08:08 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5E9CCB814DA; Wed, 15 Mar 2017 17:07:58 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, dnsop@ietf.org
Message-Id: <20170316000758.5E9CCB814DA@rfc-editor.org>
Date: Wed, 15 Mar 2017 17:07:58 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/XEwtPSKSJe5MLPBUeC4FqJZL9K8>
Subject: [DNSOP] BCP 209, RFC 8109 on Initializing a DNS Resolver with Priming Queries
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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, 16 Mar 2017 00:08:54 -0000

A new Request for Comments is now available in online RFC libraries.

        BCP 209        
        RFC 8109

        Title:      Initializing a DNS Resolver with 
                    Priming Queries 
        Author:     P. Koch, M. Larson,
                    P. Hoffman
        Status:     Best Current Practice
        Stream:     IETF
        Date:       March 2017
        Mailbox:    pk@DENIC.DE, 
                    matt.larson@icann.org, 
                    paul.hoffman@icann.org
        Pages:      7
        Characters: 15645
        See Also:   BCP 209

        I-D Tag:    draft-ietf-dnsop-resolver-priming-11.txt

        URL:        https://www.rfc-editor.org/info/rfc8109

        DOI:        10.17487/RFC8109

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 is a product of the Domain Name System Operations Working Group of the IETF.


BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC