Reviewer: Dirk Von Hugo
Review result: Ready with Nits
Dear all,
I am an assigned INT directorate reviewer for draft-ietf-dnsop-rfc8109bis.
These comments were written primarily for the benefit of the Internet Area
Directors. Document editors and shepherd(s) should treat these comments just
like t
Thanks for the review! Those nits are the kind of thing the RFC Editor picks
up, so unless we have to revise the document for the IESG, we'll let them catch
them during the editorial process.
--Paul Hoffman
On Aug 19, 2024, at 06:23, Dirk Von Hugo via Datatracker
wrote:
>
> Reviewer: Dirk Vo
Orie Steele has entered the following ballot position for
draft-ietf-dnsop-rfc8109bis-06: No Objection
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please refer to
Reviewer: Patrick Mevzek
Review result: Ready with Nits
I reviewed draft-ietf-dnsop-rfc8109bis-06 which was current version at time of
review.
The document, updating RFC 8109, does not introduce changes in the DNS protocol
or specifications, but gives guidance on best operational behavior for a
r
I know this is late in the process but why is DNS COOKIE not suggested
as it is much better than source port randomisation for eliminating spoofed
responses? It even works when NATs that de-randomise source ports are in
the path.
Additionally I don’t know why all the root servers are not implemen
Mahesh Jethanandani has entered the following ballot position for
draft-ietf-dnsop-rfc8109bis-06: No Objection
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please re
