Conflict/Dispute Resolution. In extreme cases, data discrepancies may require some form of (as yet undefined) dispute resolution process to examine the available data and make a determination as to the proper registrant or sponsoring registrar. Such a process might be adapted from the registrar transfer dispute resolution process, but needs to be performed by ICANN or a party ICANN decides to contract. Given that the Transition-In process reconciles differences between a registry’s released escrow deposits and a zone file, and given the nature of the mandatory algorithm, there are at least four critical classes of dispute as described in the table below. There are several ways in which a registrant could be inadvertently changed (e.g., out of date or incomplete SRS).
Appears in 3 contracts
Samples: Emergency Back End Registry Operator Agreement, Emergency Back End Registry Operator Agreement, Emergency Back End Registry Operator Agreement
Conflict/Dispute Resolution. In extreme cases, data discrepancies may require some form of (as yet undefined) dispute resolution process to examine the available data and make a determination as to the proper registrant or sponsoring registrar. Such a process might be adapted from the registrar transfer dispute resolution process, but needs to be performed by ICANN or a party ICANN decides to contract. Given that the Transition-In process reconciles differences between a registry’s released escrow deposits and a zone file, and given the nature of the mandatory algorithm, there are at least four critical classes of dispute as described in the table below. There are several ways in which a registrant could be inadvertently changed (e.g., out of date or incomplete SRS).
Appears in 1 contract
