Thanks for the review and feedback, tale! We will fold all these suggestions into our next round of updates.
Much appreciated, Andrew On 2/13/26, 9:16 PM, "David Lawrence via Datatracker" <[email protected] <mailto:[email protected]>> wrote: Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Document: draft-ietf-dnsop-integration Title: Integration of DNS Domain Names into Application Environments: Motivations and Considerations Reviewer: David Lawrence Review result: Almost Ready Hi all. A good start on the things that people should be considering when planning to use DNS names in their applications. Nit: I found "security, stability, and resiliency of the global DNS" to be a bit long to be so repetitive with occuring four times in just two pages. I think I'd modify the second and third occurrences to just remove them, both because the other two occurrences make the context clear and becaue "risks to the global DNS" and "could negatively impact the application and the global DNS" read perfectly well without the extra text. Nit: "Failure to account for the domain name lifecycle [...] allowing users other than the current registrant of the domain name to control the domain name [...] which could lead to confusion." Not just confusion, but this goes pretty directly to the "security" part of the phrase from the introduction. The next section, 3.2, mentions the security risk, but it'd be good to put it right up front the first time that confusion comes up. Nit: One thing I kept thinking as I was reading was that I'd really like to see some sort of case study that illustrated the points being made throughout section 3. That exists in an appendix, but I (who almost never reads the table of contents, perhaps a personal failing) didn't anticipate that an appendix was even coming and first thought I was at the end when I hit the Informative References. It's fine as an appendix, but it might help to indicate in the prose that it's coming. Like maybe as a second paragraph to to section 3[.0], something like "In Appendix A, we'll look at how the considerations listed here relate to two different protocols' approaches to DNS Integration," or of course whatever wording you prefer. Substance: To that end, it'd help if the examples in the appendices more directly referenced each of the considerations described through section 3. The ENS one seems particularly light on useful reflection. _______________________________________________ DNSOP mailing list -- [email protected] <mailto:[email protected]> To unsubscribe send an email to [email protected] <mailto:[email protected]>
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
