Reviewer: Jim Reid
Review result: Ready with Nits

The I-D is a no brainer. It requests a code point for a new crypto algorithm
for Secure DNS and deprecates one for an algorithm that has been obsoleted.

Some language nits.

1) The text in 4.1 "algorithm number 23 is used here as an example..." should
be moved to earlier in the document, before any of the examples are shown.

2) In 2.2 "in the private key file, it must be in one line" should be deleted.

3) The text at the start of 3.1 does not scan well and is confusing. The
private key shown in the ID does not consist of an MX record.

*Additional Comment*
I wanted to mention a meta-issue unrelated to the text in the ID. The doc is to be an Informational RFC that updates a Proposed Standard. Which isn’t allowed IIUC. This issue needs to be fixed (independently of the ID), perhaps with something similar to the RFC6895 DNS RRTYPE Allocation Policy.