Paul Hoffman wrote:
On 12 Mar 2018, at 10:21, Vix wrote:
I call them full resolved not recursive resolvers. I thought 1034 also
did.
Not really. Please see the full text of Section 6 to see the state of
"full resolver" and "full-service resolver".
huh.
The term "recursive resolver" is
Yes please. I'd start off by noting that "recursive" (like "resolver") is
used in several different ways and a single clear definition isn't
possible.
"Recursive mode" is currently defined as "receiving a query and then either
answering from a cache or sending a query to other servers" -- which se
On 12 Mar 2018, at 10:21, Vix wrote:
I call them full resolved not recursive resolvers. I thought 1034 also
did.
Not really. Please see the full text of Section 6 to see the state of
"full resolver" and "full-service resolver".
The term "recursive resolver" is used in a zillion other places
No cc. I call them full resolved not recursive resolvers. I thought 1034 also
did.
On March 12, 2018 3:09:27 PM UTC, Paul Hoffman wrote:
>Greetings. The definition of "recursive resolver" has been problematic
>both in RFC 7719 and in draft-ietf-dnsop-terminology-bis. Section 6 of
>draft-ietf-d
On 12 Mar 2018, at 11:09, Paul Hoffman wrote:
> Can these be improved on? This is one of the core ideas in the DNS protocol
> and it seems a bit weird that we don't have a crisp set of definitions. If
> there is more text from RFCs to quote, that would possibly be a big help.
One detail that c
Greetings. The definition of "recursive resolver" has been problematic
both in RFC 7719 and in draft-ietf-dnsop-terminology-bis. Section 6 of
draft-ietf-dnsop-terminology-bis defines a bunch of terms about servers,
including "recursive mode" and "recursive resolver". The current text
gives:
