Root zone management --- Root zone management is a day-to-day operation: root zone file gets edited quite very often, due to various technical updates by top level domain registries, among other.

Technically, it is a role assigned on basis of a commercial contract by ICANN to a third party - it used to be VeriSign, the US company, and I think it still is (the contract was renewed in 2016). Thus, the contract obliges the manager to follow the rules set by ICANN through a multistakeholder process.

Could it happen that VeriSign unilaterally decide to remove a country? I am not aware of all the details of the control of day-to-day process, but I believe there are safeguards in place. But even if this would happen, the file could instantly be revoked by all the other root-zone servers which are taking copying the altered root zone file: they would revert to the 'last known good configuration', minimising the effects of the change.

Should a company be in charge of such a delicate work? Whenever we need high quality performance, a company is better fit for the job than any administration (and it used to be the US administration, btw). As long as the rules are clear, and they are obliged through the contract - plus various safeguards are in place - this shouldn't be an issue. History confirms this - so far.

(info: https://dig.watch/updates/icann-and-verisgn-complete-negotiations-root-zone-maintainer-services-agreement)

Source author: Vladimir Radunovic vladar@diplomacy.edu