# US 11,444,929 B2 · Safemode management of domain transitioning > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,444,929 B2 - Document ID: US11444929B2 - Status: Granted - Kind: B2 - Application number: 17/126,103 - Filed: 2020-12-18 - Published: 2022-06-23 - Granted: 2022-09-13 - Earliest claimed: 2020-12-18 - Assignees: Afilias Limited - Applicants: Jimmy Lam; Howard Eland; Cedarampattu Mohan - Inventors: Jimmy Lam; Howard Eland; Cedarampattu Mohan - Web page: https://patentgrep.com/patent/US11444929B2 ## CPC - H04L 61/302: {Administrative registration, e.g. for domain names at internet corporation for assigned names and numbers [ICANN]} - H04L 63/062: {for key distribution, e.g. centrally by trusted party (cryptographic mechanisms or cryptographic arrangements for key distribution involving a central third party H04L9/0819)} - H04L 9/0891: {Revocation or update of secret information, e.g. encryption key update or rekeying} - H04L 9/0894: {Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage} - H04L 9/14: using a plurality of keys or algorithms - H04L 61/4511: using domain name system [DNS] - H04L 63/164: {at the network layer} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Methods for transitioning an existing TLD from an existing registry operator to a new TLD of a new registry operator, the new TLD subsequently accessible over a communications network, the existing TLD having a non-operational zone or an operational zone. The method includes: collecting existing registry data for the existing TLD from a plurality of registrars associated with one or more domain names of the existing TLD, such that each of the plurality of registrars provides a respective portion of the existing registry data; aggregating the respective portions of the existing registry data to generate new registry data for the new TLD; generating new zone data for the new TLD; publishing in a first mode the new zone data to nodes of a DNS (Domain Name System), the first mode disabling write functionality of the new zone data while facilitating querying of the new zone data; and publishing in a second mode the new zone data to the nodes of the DNS, the second mode facilitating the write functionality of the new zone data, including the querying and updating of the new zone data, the new zone data of the second mode considered as an operational zone; wherein the new zone data and the new registry data in the first mode as well as in the second mode are accessible by the plurality of registrars over the communications network. ## Claims ### Claim 1 A method for transitioning an existing TLD (Top Level Domain) from an existing registry operator to a new TLD of a new registry operator, the new TLD subsequently accessible over a communications network, the existing TLD having a non-operational zone, which method comprises: collecting existing registry data for the existing TLD from a plurality of registrars associated with one or more domain names of the existing TLD, such that each of the plurality of registrars provides a respective portion of the existing registry data; aggregating the respective portions of the existing registry data to generate new registry data for the new TLD; using the new registry data to generate new zone data for the new TLD, the new registry data containing at least some data representative of existing zone data for the existing TLD; publishing in a first mode the new zone data to nodes of a DNS (Domain Name system), the first mode disabling write functionality of the new zone data while facilitating querying of the new zone data; and publishing in a second mode the new zone data to the nodes of the DNS, the second mode facilitating the write functionality of the new zone data, including said querying and updating of the new zone data, the new zone data of the second mode considered as an operational zone; wherein the new zone data and the new registry data in the first mode as well as in the second mode are accessible by the plurality of registrars over the communications network. ### Claim 2 (depends on 1) The method of claim 1, wherein while in the first mode a status of the new TLD is non operational by inhibiting updates to the new zone data. ### Claim 3 (depends on 1) The method of claim 1, further comprising the step of receiving updates to the new zone data from one or more of the plurality of registrars and republishing the new zone data including said updates. ### Claim 4 (depends on 1) The method of claim 1 further comprising the step of receiving updates to the new registry data from one or more of the plurality of registrars and storing the new registry data including said updates. ### Claim 5 (depends on 1) The method of claim 1, wherein said querying and said updating utilizes respective Extensive Provisioning Protocol (EPP) commands. ### Claim 6 (depends on 1) The method of claim 1, wherein said generating the new zone data includes provisioning DNSSEC (Domain Name System Security Extensions) signing key settings on a DNSSEC signing system and generating one or more signatures for the new zone data in order to provide the new zone data as a signed zone. ### Claim 7 (depends on 1) The method of claim 1, wherein the existing registry data includes at least one of contact data and domain status data. ### Claim 8 (depends on 1) The method of claim 1, wherein the existing zone data is collected from another data source other than the plurality of registrars. ### Claim 9 (depends on 1) The method of claim 1, wherein the step of generating one or more signatures includes generating one or more new public keys, such that the existing zone data contains one or more existing public keys, such that the one or more signatures includes the one or more new public keys. ### Claim 10 (depends on 8) The method of claim 8, wherein the new zone data includes new root zone data. ### Claim 11 (depends on 1) The method of claim 1, wherein the existing registry data includes administration data for a plurality of registrants for domain names of the existing TLD; and the new registry data is stored in a new registry database for the new TLD. ### Claim 12 (depends on 1) The method of claim 1, further comprising the step of: cross checking the existing registry data with the existing zone data in order to identify one or more conflicts. ### Claim 13 (depends on 1) The method of claim 1, further comprising the step of: supplementing the existing registry data collected from the plurality of registrars with additional registry data obtained from at least one of an existing registry database of the TLD and a current operator of the TLD. ### Claim 14 (depends on 13) The method of claim 13, further comprising the step of reconciling the additional registry data with the existing registry data. ### Claim 15 (depends on 13) The method of claim 13, wherein the existing registry data is stored as offline backup data. ### Claim 16 (depends on 15) The method of claim 15, wherein the offline backup data is escrow data and the existing TLD is a gTLD (generic Top Level Domain). ### Claim 17 (depends on 1) The method of claim 1, further comprising the step of: supplementing the existing zone data with additional zone data obtained from at least one of an existing registry database of the TLD and a current operator of the TLD. ### Claim 18 (depends on 17) The method of claim 17, further comprising the step of reconciling the additional zone data with the existing zone data. ### Claim 19 (depends on 17) The method of claim 17, wherein the existing zone data is stored as offline backup data. ### Claim 20 (depends on 19) The method of claim 19, wherein the offline backup data is escrow data and the existing TLD is a gTLD. ### Claim 21 A method for transitioning an existing TLD from an existing registry operator to a new TLD of a new registry operator, the new TLD subsequently accessible over a communications network, the existing TLD having an operational zone, which method comprises: collecting existing registry data for the existing TLD from a plurality of registrars associated with one or more domain names of the existing TLD, such that each of the plurality of registrars provides a respective portion of the existing registry data; aggregating the respective portions of the existing registry data to generate new registry data for the new TLD; using the new registry data to generate new zone data for the new TLD, the new registry data containing at least some data representative of existing zone data of the operational zone for the existing TLD; publishing in a first mode the new zone data to nodes of a DNS (Domain Name System) as an unsecured zone, the first mode disabling write functionality of the new zone data while facilitating querying of the new zone data; waiting for a hold down period to expire; generating one or more signatures for the new zone data in order to provide the new zone data as a secured zone; and publishing in a second mode the new zone data to the nodes of the DNS, the second mode facilitating the write functionality of the new zone data, including said querying and updating of the new zone data, the new zone data of the second mode considered as a new operational zone for the new TLD and including the one or more signatures; wherein the new zone data and the new registry data in the first mode as well as in the second mode are accessible by the plurality of registrars over the communications network. ### Claim 22 (depends on 21) The method of claim 21, wherein while in the first mode a status of the TLD is non operational by inhibiting updates to the new zone data. ### Claim 23 (depends on 21) The method of claim 21, further comprising the step of receiving updates to the new zone data from one or more of the plurality of registrars and republishing the new zone data including said updates. ### Claim 24 (depends on 21) The method of claim 21, further comprising the step of receiving updates to the new registry data from one or more of the plurality of registrars and storing the new registry data including said updates. ### Claim 25 (depends on 21) The method of claim 21, wherein said querying and said updating utilizes respective Extensive Provisioning Protocol (EPP) commands. ### Claim 26 (depends on 21) The method of claim 21, wherein said generating the new zone data includes provisioning DNSSEC signing key settings on a DNSSEC signing system and generating the one or more signatures for the new zone data in order to provide the new zone data as a signed zone. ### Claim 27 (depends on 21) The method of claim 21, wherein the existing registry data includes at least one of contact data and domain status data. ### Claim 28 (depends on 1) The method of claim 1, wherein the existing zone data is collected from another data source other than the plurality of registrars. ### Claim 29 (depends on 1) The method of claim 1, wherein the step of generating one or more signatures includes generating one or more new public keys, such that the existing zone data contains one or more existing public keys, such that the one or more signatures includes the one or more new public keys. ### Claim 30 (depends on 28) The method of claim 28, wherein the new zone data includes new root zone data. ### Claim 31 (depends on 21) The method of claim 21, further comprising the step of: accessing one or more existing public keys of the existing zone data by implementing corresponding one or more DNS queries; wherein the one or more existing public keys are utilized in said step of generating the one or more signatures, the one or more signatures including new delegation signer records. ### Claim 32 (depends on 31) The method of claim 31, further comprising the step of replacing existing delegation signer records of the new zone data with new delegation signer records. ### Claim 33 (depends on 32) The method of claim 32, further comprising the step of delaying publication of new delegation signer records with the new zone data for a specified period of time. ### Claim 34 (depends on 21) The method of claim 21, further comprising the step of: accessing one or more new public keys of the new zone data by implementing corresponding one or more DNS queries; wherein the one or more new public keys are utilized in said step of generating the one or more signatures, the one or more signatures including new delegation signer records. ### Claim 35 (depends on 34) The method of claim 34, further comprising the step of replacing existing delegation signer records of the new zone data with new delegation signer records. ### Claim 36 (depends on 35) The method of claim 35, further comprising the step of delaying publication of new delegation signer records with the new zone data for a specified period of time. ### Claim 37 A method for transitioning an existing TLD from an existing registry operator to a new TLD of a new registry operator, the new TLD subsequently accessible over a communications network, the existing TLD having an operational zone, which method comprises: collecting existing registry data for the existing TLD from a plurality of registrars associated with one or more domain names of the existing TLD, such that each of the plurality of registrars provides a respective portion of the existing registry data; aggregating the respective portions of the existing registry data to generate new registry data for the new TLD; accessing the existing zone data in order to generate new zone data for the new TLD, the existing zone data containing at least some data facilitating the operational zone for the existing TLD; publishing in a first mode the new zone data to nodes of a DNS (Domain Name System), the first mode disabling write functionality of the new zone data while facilitating querying of the new zone data; and publishing in a second mode the new zone data to the nodes of the DNS, the second mode facilitating the write functionality of the new zone data, including said querying and updating of the new zone data, the new zone data of the second mode considered as a new operational zone for the new TLD; wherein the new zone data and the new registry data in the first mode as well as in the second mode are accessible by the plurality of registrars over the communications network. ### Claim 38 (depends on 37) The method of claim 37, wherein said publishing in the first mode is as a secured zone, the first mode disabling write functionality of the new zone data while facilitating querying of the new zone data, the new zone data containing one or more signatures. ### Claim 39 (depends on 37) The method of claim 37, wherein said publishing in the first mode is as an unsecured zone, the first mode disabling write functionality of the new zone data while facilitating querying of the new zone data. ### Claim 40 (depends on 39) The method of claim 39, wherein the new zone data contains one or more signatures in order to provide the new zone data as a secured zone.