draft-ietf-dnsop-resolver-priming-10.txt   draft-ietf-dnsop-resolver-priming-11.txt 
Network Working Group P. Koch Network Working Group P. Koch
Internet-Draft DENIC eG Internet-Draft DENIC eG
Intended status: Best Current Practice M. Larson Intended status: Best Current Practice M. Larson
Expires: June 26, 2017 P. Hoffman Expires: June 27, 2017 P. Hoffman
ICANN ICANN
December 23, 2016 December 24, 2016
Initializing a DNS Resolver with Priming Queries Initializing a DNS Resolver with Priming Queries
draft-ietf-dnsop-resolver-priming-10 draft-ietf-dnsop-resolver-priming-11
Abstract Abstract
This document describes the queries that a DNS resolver should emit This document describes the queries that a DNS resolver should emit
to initialize its cache. The result is that the resolver gets both a to initialize its cache. The result is that the resolver gets both a
current NS RRSet for the root zone and the necessary address current NS RRSet for the root zone and the necessary address
information for reaching the root servers. information for reaching the root servers.
Status of This Memo Status of This Memo
skipping to change at page 1, line 35 skipping to change at page 1, line 35
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 26, 2017. This Internet-Draft will expire on June 27, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 5, line 15 skipping to change at page 5, line 15
with A and/or AAAA RRSets for the root name servers pointed at by the with A and/or AAAA RRSets for the root name servers pointed at by the
NS RRSet. NS RRSet.
Resolver software SHOULD treat the response to the priming query as a Resolver software SHOULD treat the response to the priming query as a
normal DNS response, just as it would use any other data fed to its normal DNS response, just as it would use any other data fed to its
cache. Resolver software SHOULD NOT expect exactly 13 NS RRs because cache. Resolver software SHOULD NOT expect exactly 13 NS RRs because
historically some root servers have returned fewer. historically some root servers have returned fewer.
4.2. Completeness of the Response 4.2. Completeness of the Response
There are currently 13 root servers. All have one IPv4 address, and There are currently 13 root servers. All have one IPv4 address and
12 of the 13 have an IPv6 address. The combined size of all the A one IPv6 address. Not even counting the NS RRSet, the combined size
and AAAA RRSets is 544 bytes. Not even counting the NS RRSet, this of all the A and AAAA RRSets exceeds the original 512 octet payload
value exceeds the original 512 octet payload limit from [RFC1035]. limit from [RFC1035].
In the event of a response where the Additional section omits certain In the event of a response where the Additional section omits certain
root server address information, re-issuing of the priming query does root server address information, re-issuing of the priming query does
not help with those root name servers that respond with a fixed order not help with those root name servers that respond with a fixed order
of addresses in the Additional section. Instead, the recursive of addresses in the Additional section. Instead, the recursive
resolver needs to issue direct queries for A and AAAA RRSets for the resolver needs to issue direct queries for A and AAAA RRSets for the
remaining names. Currently, these RRSets would be authoritatively remaining names. Currently, these RRSets would be authoritatively
available from the root name servers. available from the root name servers.
5. Security Considerations 5. Security Considerations
 End of changes. 5 change blocks. 
8 lines changed or deleted 8 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/