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
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
