Hi Kim,

On 17 Nov 2026, at 17:57, Kim Davies <[email protected]> wrote:

> We would appreciate your feedback and would like to see if this document can 
> be adopted by the working group.
> 
>       https://datatracker.ietf.org/doc/draft-davies-internal-tld/

I just read -08 and I think it's fine. I have only editorial suggestions for 
improvement, and I think it's probably a good idea (a) to have the namespace 
documented in the RFC series and (b) to have internal included in the special 
names registry. On the latter, I was persuaded by Stuart's comments yesterday 
that it would be weird if someone wanted to find out why the "internal" domain 
was special and they couldn't find a link from there. It certainly does no harm 
to include it.

On the editorial comments, I think the phrase "Entities choosing to do so 
should be cognizant of the implications of this decision" might reasonably be 
replaced by "Using the 'internal' top-level domain has risks" -- this is just a 
flavour of suggestions I might erupt in if given half a chance, so I'll stop 
now since this is mainly a matter of stylistic choice.

I think the document might consider citing RFC 9499 in section 2 and using 
terms from that document where possible. For example, RFC 9499 defines 
"Resolver" and "Recursive resolver" but not the phrase "Caching DNS servers" 
which is used repeatedly in section 5. I imagine there are other phrases that 
could be normalised in that way, because there usually are.


Joe
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to