Need method for making available TLDs in handshake when ICANN Applicant Withdraws or Cancels TLD

[dnsguru]

As evidenced in the bootstrap process, there were some friendly amendments made to address the delta between the root zone snapshot and the changes that had occurred after it was taken.

As evidenced in #6, there were some additions that the bootstrap process missed, but in addition to the zones being added to the ICANN root, there are zones also being removed when applicants opt to cancel them.

From time to time, ICANN updates the following file:
https://www.icann.org/resources/registries/gtlds/v2/gtlds.json with adds/changes/removes. The most recent update releases two IDN TLDs from Richemont, and .aigo

The Public Suffix picks up the deltas and auto-PSs them https://github.com/publicsuffix/list/pull/1059

These changes happen from time to time, and this leaves the option of releasing these in the handshake namespace.

[pinheadmz]

If they're reserved names it would require a hard fork to "release" them before the four year reservation-expiration. Any nodes that don't upgrade will reject the auctions as invalid. However if ICANN ever releases those TLDs again they can be claimed by whoever gets them (more explicitly: whoever has a DNSSEC proof signed by ICANN at the root).

ICANN themselves can unilaterally claim these names at any time even if they have no owner in their own root zone just by generating such a proof.

Otherwise it's the four year wait. Consider it more like unclaimed Alexa names or unredeemed airdrops...