Hi all, We are implementing the changes to address the feedback we received in IETF#116. The candidate changes can be seen at Diff: draft-ietf-dnsop-structured-dns-error-01.txt - draft-ietf-dnsop-structured-dns-error.txt<https://author-tools.ietf.org/api/iddiff?doc_1=draft-ietf-dnsop-structured-dns-error&url_2=https://ietf-wg-dnsop.github.io/draft-ietf-dnsop-structured-dns-error/draft-ietf-dnsop-structured-dns-error.txt>
The current version of the draft indicates that the policy for registering a new suberr is via DE. We added a guard to prevent that DEs modify entries set via IETF review. I know that Ben indicated a preference for requiring IETF review for the registry. This seems to me too restrictive, especially that the policy for the EDE itself is FCFS. The argument that DEs will be pressured is not specific to this registry and would a priori apply for every registry with a DE policy. I think that we need a good balance to allow for useful suberr codes to be registered without requiring much heaviness in the process that is induced by an IETF review. Ben, if your concern is to have some control, what about requiring that new registrations should be sent to the DEs and also to dnsop (or another list), and that DEs should listen to whatever feedback received from the list? Thank you. Cheers, Med _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
