Re: Implementation of EPP AuthInfo
Francisco Obispo <[email protected]>
| Newsgroups | gmane.ietf.provreg |
|---|---|
| Message-ID | <[email protected]> |
Hi Vlad, What are the problems you're trying to address with these measures? Some thoughts below: On May 6, 2013, at 11:23 PM, Vlad Dinculescu <[email protected]> wrote: > All, > > Please share your thoughts regarding the implementation of the Contact AuthInfo for the approval of initiated contact updates. > > Our current process looks to have the registrant provide the code as an indication of approval regarding the update of their information, completing the update instantly. Updates that are not provided with the code will not execute. > Do you want to accept an update from a non-sponsoring registrar? If that's not the case, the AuthInfo will be available to the sponsoring registrar anyway. > Further to this, we are looking to implement the Domain AuthInfo code as a definite measure for approving registrant changes to a linked domain. In this instance the current registrant must provide the Domain AuthInfo code as approval of the registrant change. > Same as above, but in addition, a contact object can be independently updated regardless if its used in a domain name or not, so the restriction will only have effect if you 'replace' the registrant with other ID, but not if you change the contact underlying data. > Regards, > Vlad Dinculescu > -------------------------------- > Domain Name Services > _______________________________________________ > provreg mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/provreg Francisco Obispo Director of Applications and Services - ISC email: [email protected] Phone: +1 650 423 1374 || INOC-DBA *3557* NOC PGP KeyID = B38DB1BE _______________________________________________ provreg mailing list [email protected] https://www.ietf.org/mailman/listinfo/provreg