> -----Original Message----- > From: Carl Wallace via Datatracker <nore...@ietf.org> > Sent: Wednesday, November 27, 2024 4:37 PM > To: sec...@ietf.org > Cc: draft-ietf-regext-epp-delete-bcp....@ietf.org; last-c...@ietf.org; > regext@ietf.org > Subject: [EXTERNAL] Secdir last call review of > draft-ietf-regext-epp-delete-bcp- > 08 > > 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. > > Reviewer: Carl Wallace > Review result: Ready > > This draft describes best current practices and proposes new potential > practices to delete domain and host objects that reduce the risk of DNS > resolution failure and maintain client-server data consistency when using the > Extensible Provisioning Protocol. The draft is well written and references > several helpful documents. One minor issue I had with the draft is that it > becomes a wall of benefits and detriments, most of which are repetitious. This > occurs in Section 5. I think that presentation is OK, but it may benefit from > a > shorter summary presentation in Section 6 of at least the MUST NOT > practices. > At present, only the MUST practices are highlighted in Section 6.
[SAH] Thanks for the review, Carl. Ultimately, the practices not mentioned in Section 6 are NOT RECOMMENDED. We can make that clear by saying so explicitly. Scott _______________________________________________ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org
