Reviewer: Scott Rose
Review result: Ready with Nits
Reviewing version -10
Ready with nits
The draft does not include any changes to the DNS or DNS over TLS, it does
restate what the RFC 8310 says about mandatory support for TLS. This is not
changed by this draft.
Nit:
There is a typo in Sec. 5 f
Reviewer: Scott Rose
Review result: Ready
I believe the draft is ready, with a minor typo/nit that don't change the
document:
In Section 5.1 second paragraph has "Signaling Zone" while other instances are
"signaling zone".
Scott
___
DNSOP maili
Reviewer: Scott Rose
Review result: Ready with Nits
There does not appear to be any change to the text that relates how the DNS RRs
are to be provisioned and queried. So the review from the -12 version still
applies. This draft does not impact the DNS protocol and is ready in that
respect.
I wil
Reviewer: Scott Rose
Review result: Ready with Nits
The draft describes a yang model for provisioning NAPTR RRs (and queries) for
ALTO servers in the DNS reverse tree. This draft does not alter the DNS
protocol or defined use of NAPTR RRs for this purpose. That is defined in other
RFCs.
There is
Reviewer: Scott Rose
Review result: Ready with Issues
Review of dnssec-bootstrapping
The draft is likely OK to proceed as there are only a few nits that do not
change the overall contents. I am confused about if it adds to methods in RFC
8078 or replaces methods in RFC 8078.
1. Abstract:
The Abs
Reviewer: Scott Rose
Review result: Ready with Nits
This Internet-Draft assigns a code point to a cryptographic algorithm for use
in DNSSEC and obsoletes a preceding algorithm. The DNS and DNSSEC protocols are
not changed in any way and in that sense of review the I-D is Ready.
The nits listed in
