Hi Bill, On 26.06.24 15:45, Carroll, William wrote:
Not sure if normative language with MUST NOT is allowed in BCP, but adding MUST NOT or SHOULD NOT will give for sure a clear valuable guidance that I would expect from this BCP.Hi Pawel,Thank you for your close reading of the doc! We felt that adding a "practices to avoid" to each observed/not-observed section was unnecessary with the best practices already specified. Would you prefer the addition of a "This practice MUST NOT be used" sentence for the worst practices? I think those would include "5.1.3.1. Renaming to External, Presumed Non-Existent Hosts", "5.1.3.3. Renaming to Non-Authoritative Hosts", and "5.1.4.1. Renaming to Pseudo-TLD".
As to the explicit delete, I think the previous "observed in use" was an incorrect reading of a
list email from Gavin Brown about observed practices. For explicit delete, we had in mind that a client would
provide an explicit flag specifying that the client wants to delete any host objects belonging to another
client ("They would be required to explicitly request deletion of these objects."). As far as we
know, no one is currently operating with that practice. I will edit to try to make that clearer, which may
make "5.2.2.1.3.1. Explicit Deletion Request" redundant.
Kind Regards, Pawel
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org
