[Add] AD review of draft-ietf-add-resolver-info-09 and the associated shepherd write-up

["Eric Vyncke (evyncke)" <[e-mail]>]

Tiru, Med, and ADD WG,

First of all, thank you for all the work done on this draft.

Please find below my AD review of draft-ietf-add-resolver-info-09.

Before proceeding with the publication process, i.e., the IETF Last Call, I am requesting a reply to all the points below, either by a simple reply or by a text change.

Tommy,

Thank you for the detailed shepherd write-up (barring the absence of intended status justification) and I smiled when reading that your own employer does not intend to implement this feature (this part was written with sensitivity -- thanks).

# COMMENTS

## Section 1

Just to be clear s/ upstream resolvers/ upstream recursive resolvers/

## Section 3

Please qualify "the resolver" in `If the resolver understands the RESINFO RR`, i.e., is it the stub or recursive ? Also in a couple of other places.

Adding an example would be appreciated by the readers.

## Section 4

`The motivation for using the same format as TXT records is to convey a small amount of useful information about a DNS resolver`

Unsure whether the above text brings any value.

## Section 5

Which "server" it is in `The server MUST support the content-type 'text/html'.`

s/ if and only if the encrypted resolver has sufficient reputation, according to some local policy/ if and only if according to some local policy/ ? Using the term "reputation" is rather vague.

The infourl example is rather weird as it seems to indicate that the host server must be collocated with the DNS recursive resolver...

## Section 6

s/ the attributes received from the resolver, which will be used for resolver selection or display / the attributes received from the resolver *that* will be used for resolver selection or *displayed* /

This section also uses the term "reputation" that is rather vague and does not add any value, why not simply using "according to local policy" ?

# NITS

## Abstract

s/ the scope of the document/ the scope of this document/

## Section 1

s/ that may impact delivered DNS services, means to help stub resolvers/ that may impact delivered DNS service; means to help stub resolvers/ or another to make easier the parsing of the sentence.

## Section 4

s/ The resolver information uses/ The resolver information record uses/

## Section 5

s/ possibily/ possibly/

## Section 6

s/ DNS clients communicating with DNS resolvers discovered MUST employ / DNS clients communicating with *discovered* DNS resolvers MUST *use* / (2 changes)

## Section 7

s/ occurences/ occurrences/