Public Comment is a vital part of our multistakeholder model. It provides a mechanism for stakeholders to have their opinions and recommendations formally and publicly documented. It is an opportunity for the ICANN community to effect change and improve policies and operations.
Ce contenu est uniquement disponible en
It was a huge mistake to use 127.0.53.53 for this without following the appropriate procedure by means of an IETF I-D. It MUST be corrected now that we know it for the proper registration of the prefix that IETF decides is best for this. So please, also submit an I-D for the correct IPv4 address to be chosen by the IETF consensus process.
Consequently, doing it again for IPv6 will be an even bigger mistake. Please, use the procedures, by means of an I-D that can reach consensus thru the IETF process.
Those parameters belong to IETF as part of IETF protocols, and that's the right place for the discussion, not any public comment. ICANN/IANA can't unilaterally consult on those matters. I'm sure it was not done in bad faith, but should be avoided, when we have at IETF and in our relation with ICANN/IANA, very well defined procedures for that.