IP Library › Granted Patent US 12,418,505
Granted Patent B2
US 12,418,505 · App. 17/956,633 · Granted Sep 16, 2025

Multiple provisioning object operation

Inventors: James F. Gould (Leesburg, VA); Srikanth Veeramachaneni (South Riding, VA); Nagesh Chigurupati (Aldie, VA)
Assignee: VeriSign, Inc.
H04L61/4511H04L63/102H04L61/302H04L63/20
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,418,505
App. No.
17/956,633
Granted
Sep 16, 2025
Kind
B2
Abstract

A computer-implemented method, computer-readable medium, and an apparatus operable to perform the method is provided for managing multiple provisioned domain name system (“DNS”) registry objects. The method can include receiving, at a DNS registry, a multiple domain extensible provisioning protocol (“EPP”) command from a registrar on behalf of a registrant to perform an action for each provisioned DNS registry object of the multiple provisioned DNS registry objects; comparing the action with one or more allowable actions in a policy maintained by the registry; determining, by a processor, that the action is allowable based on the comparing; and performing, based on the determining, the action on each of the provisioned DNS registry objects in one transaction.

Claims (50)

1. A computer-implemented method for updating domain name system (“DNS”) registry objects, the method comprising:

receiving, at a DNS registry, a first command indicating a relationship between a first provisioned DNS registry object and a second provisioned DNS registry object;

receiving, at a DNS registry, a second command to perform an action on the first provisioned DNS registry object;

comparing the action with a policy maintained by the DNS registry, wherein the policy comprises at least one allowable action;

determining that the action is allowable based on the policy; and

after determining that the action is allowable, performing the action for each of the first provisioned DNS registry object and the second provisioned DNS registry object, wherein the first provisioned DNS registry object is related to the second provisioned DNS registry object.

2. The method of claim 1 , wherein the first provisioned DNS registry object and the second provisioned DNS registry object share one or more common attributes.

3. The method of claim 2 , wherein the action comprises updating the one or more common attributes.

4. The method of claim 1 , wherein the second provisioned DNS registry object comprises an internationalized version of the first provisioned DNS registry object.

5. The method of claim 1 , wherein receiving the second command comprises:

receiving an extensible provisioning protocol (“EPP”) command from a DNS registrar.

6. The method of claim 5 , wherein the EPP command groups the first provisioned DNS registry object and the second provisioned DNS registry object to be managed together.

7. The method of claim 5 , wherein the EPP command is a command to transfer the first provisioned DNS registry object,

wherein performing the action comprises transferring the first provisioned DNS registry object and the second provisioned DNS registry object.

8. The method of claim 1 , wherein the first provisioned DNS registry object comprises a first top-level domain and the second provisioned DNS registry object comprises a second top-level domain, and wherein the first top-level domain and the second top-level domain are different top-level domains.

9. A system for updating domain name system (“DNS”) registry objects, the system comprising:

a processor; and

a memory communicatively coupled to the processor, the memory storing instructions which, when executed on the processor, perform operations comprising:

receiving, at a DNS registry, a first command indicating a relationship between a first provisioned DNS registry object and a second provisioned DNS registry object;

receiving, at a DNS registry, a second command to perform an action on the first provisioned DNS registry object;

comparing the action with a policy maintained by the DNS registry, wherein the policy comprises at least one allowable action;

determining that the action is allowable based on the policy; and

after determining that the action is allowable, performing the action for each of the first provisioned DNS registry object and the second provisioned DNS registry object, wherein the first provisioned DNS registry object is related to the second provisioned DNS registry object.

10. The system of claim 9 , wherein the first provisioned DNS registry object and the second provisioned DNS registry object share one or more common attributes.

11. The system of claim 9 , wherein the action comprises updating the one or more common attributes.

12. The system of claim 9 , wherein receiving the second command comprises:

receiving an extensible provisioning protocol (“EPP”) command from a DNS registrar,

wherein the EPP command groups the first provisioned DNS registry object and the second provisioned DNS registry object to be managed together.

13. The system of claim 9 , wherein receiving the second command comprises:

receiving an extensible provisioning protocol (“EPP”) command from a DNS registrar,

wherein the EPP command is a command to transfer the first provisioned DNS registry object, and

wherein performing the action comprises transferring the first provisioned DNS registry object and the second provisioned DNS registry object.

14. The system of claim 9 , wherein the first provisioned DNS registry object comprises a first top-level domain and the second provisioned DNS registry object comprises a second top-level domain, and wherein the first top-level domain and the second top-level domain are different top-level domains.

15. A non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to:

receive, at a DNS registry, a first command indicating a relationship between a first provisioned DNS registry object and a second provisioned DNS registry object;

receive, at a DNS registry, a second command to perform an action on the first provisioned DNS registry object;

compare the action with a policy maintained by the DNS registry, wherein the policy comprises at least one allowable action;

determine that the action is allowable based on the policy; and

after determining that the action is allowable, perform the action for each of the first provisioned DNS registry object and the second provisioned DNS registry object, wherein the first provisioned DNS registry object is related to the second provisioned DNS registry object.

16. The non-transitory computer-readable medium of claim 15 , wherein the first provisioned DNS registry object and the second provisioned DNS registry object share one or more common attributes.

17. The non-transitory computer-readable medium of claim 15 , wherein the action comprises updating the one or more common attributes.

18. The non-transitory computer-readable medium of claim 15 , wherein receiving the second command comprises:

receiving an extensible provisioning protocol (“EPP”) command from a DNS registrar,

wherein the EPP command groups the first provisioned DNS registry object and the second provisioned DNS registry object to be managed together.

19. The non-transitory computer-readable medium of claim 15 , wherein receiving the second command comprises:

receiving an extensible provisioning protocol (“EPP”) command from a DNS registrar,

wherein the EPP command is a command to transfer the first provisioned DNS registry object, and

wherein performing the action comprises transferring the first provisioned DNS registry object and the second provisioned DNS registry object.

20. The non-transitory computer-readable medium of claim 15 , wherein the first provisioned DNS registry object comprises a first top-level domain and the second provisioned DNS registry object comprises a second top-level domain, and wherein the first top-level domain and the second top-level domain are different top-level domains.

21. The method of claim 1 , wherein the policy comprises at least one of a domain name system security extensions (“DNSSEC”)-related policy, a top level domain (TLD) launch policy, a redemption grace period policy, or a domain lifecycle policy.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 29, 2022
From: GOULD, JAMES F; VEERAMACHANENI, SRIKANTH; CHIGURUPATI, NAGESH
To: VERISIGN, INC.
Reel/Frame 061261/0122 →
Continuity (5)
Continuation 17233118 · Apr 16, 2021
Continuation 16261625 · Jan 30, 2019
Continuation 14537597 · Nov 10, 2014
Provisional Application 61903219 · Nov 12, 2013
Related Publication 20230082749A1 · Mar 16, 2023
References Cited (77)
US 6446133B1 · Tan et al. · 2002 [cited by applicant]
US 6880007B1 · Gardos et al. · 2005 [cited by applicant]
US 6895430B1 · Schneider · 2005 [cited by applicant]
US 6901436B1 · Schneider · 2005 [cited by applicant]
US 6973505B1 · Schneider · 2005 [cited by applicant]
US 6980990B2 · Fellman · 2005 [cited by applicant]
US 7188138B1 · Schneider · 2007 [cited by applicant]
US 7194552B1 · Schneider · 2007 [cited by applicant]
US 7299299B2 · Hollenbeck et al. · 2007 [cited by applicant]
US 7565402B2 · Schneider · 2009 [cited by applicant]
US 7797413B2 · Adelman et al. · 2010 [cited by applicant]
US 7861286B2 · M'Raihi et al. · 2010 [cited by applicant]
US 7904898B2 · King · 2011 [cited by examiner]
US 8037168B2 · Schneider · 2011 [cited by applicant]
US 8224994B1 · Schneider · 2012 [cited by applicant]
US RE43690E · Schneider et al. · 2012 [cited by applicant]
US 8370217B1 · Parsons et al. · 2013 [cited by applicant]
US RE44207E · Schneider · 2013 [cited by applicant]
US 8458161B2 · Schneider · 2013 [cited by applicant]
US 8612565B2 · Schneider · 2013 [cited by applicant]
US 8635340B1 · Schneider · 2014 [cited by applicant]
US 8719900B2 · Maccarthaigh · 2014 [cited by applicant]
US 8819795B2 · Hitchcock et al. · 2014 [cited by applicant]
US 8904519B2 · Essawi · 2014 [cited by examiner]
US 10237231B2 · Gould et al. · 2019 [cited by applicant]
US 20020091703A1 · Bayles · 2002 [cited by applicant]
US 20040172463A1 · King et al. · 2004 [cited by applicant]
US 20040199493A1 · Ruiz et al. · 2004 [cited by applicant]
US 20050102354A1 · Hollenbeck et al. · 2005 [cited by applicant]
US 20060253456A1 · Pacholec et al. · 2006 [cited by applicant]
US 20070271393A1 · Wong · 2007 [cited by applicant]
US 20080016233A1 · Schneider · 2008 [cited by applicant]
US 20080059607A1 · Schneider · 2008 [cited by applicant]
US 20090327098A1 · Ronen et al. · 2009 [cited by applicant]
US 20100036725A1 · Turakhia · 2010 [cited by applicant]
US 20100325723A1 · Essawai et al. · 2010 [cited by applicant]
US 20120017259A1 · Maccarthaaigh · 2012 [cited by applicant]
US 20120117095A1 · Chavvakula et al. · 2012 [cited by applicant]
US 20120173685A1 · Shorter et al. · 2012 [cited by applicant]
US 20130080341A1 · Veeramachaneni · 2013 [cited by examiner]
US 20130290269A1 · Griffiths et al. · 2013 [cited by applicant]
US 20140189489A1 · Bushlack et al. · 2014 [cited by applicant]
US 20150134832A1 · Gould et al. · 2015 [cited by applicant]
US 20200160468A1 · Veeramachaneni et al. · 2020 [cited by applicant]
CN 101444072A · 2009 [cited by applicant]
EP 2658218A1 · 2013 [cited by applicant]
WO 2001011443A2 · 2001 [cited by applicant]
WO 2004015547A2 · 2004 [cited by applicant]
Martinelli et al. ‘The EPP server of the .it Registry: main features and functionalities’, Istituto di Informatica e Telematica, Apr. 2010 [retrieved on Mar. 5, 2018]. Retrieved from the Internet: <URL:https://core.ac.u… [cited by examiner]
“Registry/Registrar Documentation for the .barcelona TLD”, Core Internet Council of Registrars, Aug. 28, 2013 [retrieved on Dec. 29, 2023]. Retrieved from the Internet: <URL: https://web.archive.org/web/20140611082330/h… [cited by examiner]
Registry/Registrar Documentation for the .barcelona TLD, Core Internet Council of Registrars, Aug. 28, 2013 [retrieved on Feb. 15, 2017]. Retrieved from the Internet: URL:http://corenic.org/files/CORERSDocumentationBARC… [cited by applicant]
Manley, D. “Helpful How to for EPP registrars”, Sourceforge.net, Sep. 28, 2001 [retrieved on Jan. 30, 2017]. Retrieved from the Internet: URL:http://epp-rtk.sourceforge.net/epp-howto.html , pp. 1-20. [cited by applicant]
Tacacs and Vty, The Cisco Learning Network, Nov. 20, 2011 [retreieved on Feb. 14, 2017]. Retrieved from the Internet: URL:https://learningnetwork.cisco.com/thread/36861 ,pp. 1-9. [cited by applicant]
Hollenbeck, S. “RFC 5732—Extensible Provisioning Protocol (EPP) Host Mapping,” Aug. 2009 [Retrieved on Feb. 14, 2017]. Retrieved from the Internet: URL:https://tools.ietf.org/html/rfc5732 , pp. 1-29. [cited by applicant]
Mitchell, J. et al. “Domain Name Variant Extension Mapping for the Extensible Provisioning Protocol (EPP)”, AusRegistry, Dec. 2012 [retrieved on Feb. 14, 2017]. Retrieved from the Internet: URL:http://ausregistry.github… [cited by applicant]
Gould, J. “IDN Language Tag for the Extensible Provisioning Protocol (EPP)”, Verisign Inc., Dec. 10, 2013 [retrieved on Feb. 15, 2017]. Retrieved from the Internet: URL:http://www.verisign.com/assets/epp-sdk/verisign_ep… [cited by applicant]
Martinelli et al. ‘The EPP server of the .it Registry: main features and functionalities’, Istituto di Informatica e Telematica, Apr. 2010 [retrieved on Mar. 5, 2018]. Retrieved from the Internet: URL:https://core.ac.uk… [cited by applicant]
Author Unknown, “Medium Enterprise Design Profile (MEDP)—Network Security Design”, Medium Enterprise Design Profile Reference Guide, http://www.3c3cc.com/c/en/us/td/docs/solutions/Enterprise/Medium_Enterprise_Design_Pro… [cited by applicant]
Hollenbeck, S., “ConsoliDate Mapping for the Extensible Provisioning Protocol”, VerisignNaming and Directory Services, Mar. 22, 2005, 10 pages. [cited by applicant]
Notice of Allowance issued in U.S. Appl. No. 13/626,455 on Sep. 25, 2019, pp. 1-10. [cited by applicant]
Notice of Allowance issued in U.S. Appl. No. 16/261,625 on Apr. 30, 2020, pp. 1-21. [cited by applicant]
Office Action issued in U.S. Appl. No. 16/261,625 on Sep. 11, 2020, 18 pages. [cited by applicant]
Notice of Allowance issued in U.S. Appl. No. 16/261,625 on Jan. 6, 2021, pp. 1-7. [cited by applicant]
Notice of Allowance issued in U.S. Appl. No. 16/261,625 on May 28, 2021, 13 pages. [cited by applicant]
SSL Shopper, SSL Certificate: Why Verify Domain Ownership, https://www.sslshopper.com/article-ssl-certificate-why-verify-domain-ownership.html, dated Dec. 16, 2007, pp. 1-3 (Year: 2007). [cited by applicant]
New EPP regulations now in effect http://www.moniker.com/news/vol6/v6art5.jsp 2 pages, Jan. 10, 2007, retrieved from Internet ARchive Wayback Machine https://web.archive.org/web/2007011 0222202/http://www.moniker.com/ne… [cited by applicant]
Author Unknown, “EPP Extensions for the .coop TLD Registrant Verification”, Internet Article, Oct. 5, 2010, http://www.nic.coop/media/1517/EppExtensionsForDotCoop.pdf, accessed Sep. 11, 2013, pp. 1-16. [cited by applicant]
Wikipedia, “Extensible Provisioning Protocol”, Internet Article, Jul. 15, 2011, http://en.wikipedia.org/w/index.phptitle=Extensible_Provisioning_Protocol oldid=439639435, accessed Sep. 11, 2013, pp. 1-2. [cited by applicant]
Wikipedia, “Transfer secret”, Internet Article, Aug. 29, 2011, http://en.wikipedia.org/w/index.phptitle=Transfer_secret oldid=447393192, accessed Sep. 11, 2013, pp. 1-2. [cited by applicant]
Office Action issued in U.S. Appl. No. 16/261,625 on Oct. 30, 2019, pp. 1-19. [cited by applicant]
Hollenbeck, “RFC 5731, Extensible Provisioning Protocol (EPP) Domain Name Mapping,” Internet Engineering Task Force (IETF), Aug. 31, 2009, retreived from the internet: <URL: https;/www/rfc-editor.org/rfc/pdfrfc/rfc5731.… [cited by applicant]
Hollenbeck, “RFC 5733, Extensible Provisioning Protocol (EPP) Contact Mapping,” Interenet Engineering Task Force (IETF), Aug. 31, 2009, Retrieved from the interent: <URL: https://www.rfc-editor.org/rfc/pdfrfc/rfc5733.tx… [cited by applicant]
“EPP Protocol create multiple domains in one command,” Serverfault website, Nov. 3, 2013 [retreved on Dec. 18, 2021]. Retrieved from the intern: <URL: https://serverfault.com/questions/549648/epp.-protocol-create-multip… [cited by applicant]
Gould, J. et al. “Related Domain Extension for the Extensible Provisioning Protocol (EPP)”, Verisign Inc., Jan. 2, 2014 [retrieved on Feb. 15, 2017]. Retrieved from the Internet: URL:http://www.verisign.com/assets/epp-s… [cited by applicant]
Chinese Office Action issued in Chinese Patent Application No. 201410848610.7 on Aug. 30, 2018. [cited by applicant]
Extended European Search Report dated Mar. 10, 2015, European Application No. 14192697.2 filed Nov. 11, 2014, pp. 1-6. [cited by applicant]
Extended European Search Report dated Sep. 19, 2013, European Application No. 12186193.4, filed Sep. 26, 2012, pp. 1-7. [cited by applicant]