Shared registration system for registering domain names

• US 7,299,299 B2
• Filed: 12/20/2004
• Issued: 11/20/2007
• Est. Priority Date: 04/22/1999
• Status: Expired due to Term

• Current Assignee: VeriSign, Inc.
• Original Assignee: Network Solutions Incorporated (Pivotal Group Incorporated)
• Inventors: Holtzman, David, Hollenbeck, Scott, Srivastava, Manoj, Saraf, Neeran
• Primary Examiner(s): Cardone; Jason
• Assistant Examiner(s): Nguyen; Minh Chau
• Application Number:
  US11/014,709
• Publication Number:
  US 20050102354A1
• Time in Patent Office: 1,065 Days
• Field of Search: 709/203, 709217-219, 709/223, 709/245
• US Class Current: 709/245
• CPC Class Codes: G06Q 10/02 Reservations, e.g. for tickets, services or events
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions

Abstract

An apparatus and method for processing a domain name registration operation in a shared registration system is provided. A registry receives a request for performing a domain name registration operation from a registrar. The registry performs an authentication of the registrar that sent the request. If the registrar is determined to be authenticated, the registry then determines whether the registrar is authorized to perform an action necessitated by the operation. Subsequently, the registry executes the operation based on a determination that the registrar is authorized and stores changes necessitated by the operation in a database. A response indicating success or failure of the operation is sent to the registrar.

Claims

1. A method for processing a domain name registration operation in a shared registration system comprising the steps of:

receiving a registry-registrar protocol (RRP) request for performing a domain name registration operation from a registrar;

parsing the request;

determining whether the registrar that sent the request is authorized to perform an action necessitated by the operation;

if the registrar is authorized, performing the operation;

storing changes necessitated by the operation in a domain name registry; and

sending a RRP response to the registrar, the response indicating success or failure of the operation.

2. The method of claim 1, wherein the request includes a command name and an entity block.

3. The method of claim 2, wherein the entity block includes an indication as to whether the operation pertains to a domain name or a name server.

4. The method of claim 1, further comprising:

determining whether the request is valid before the determining step.

5. The method of claim 1, wherein the operation enables a registrar to register a domain name or a name server.

6. The method of claim 1, wherein the operation enables a registrar to determine whether a domain name or name server has previously been registered.

7. The method of claim 1, wherein the operation enables a registrar to delete the registration of a domain name or delete a name server.

8. The method of claim 1, wherein the operation enables a registrar to update a registered domain name or name server.

9. The method of claim 1, wherein the operation enables a registrar to close a connection with the registry.

10. The method of claim 1, wherein the operation enables a registrar to re-register a domain name.

11. The method of claim 1, wherein the operation enables a registrar to authenticate a connection with the registry.

12. The method of claim 1, wherein the operation allows a registrar to determine the current status of a domain name or name server.

13. The method of claim 1, wherein the operation allows a registrar to request transfer of domain name sponsorship from a second registrar and to approve or reject transfer requests initiated by other registrars.

14. The method of claim 1, wherein the operation allows a registrar to request transfer of domain name sponsorship from a second registrar and to approve or reject transfer requests initiated by other registrars.

15. A computer-readable storage medium storing instructions which, when executed by a processor, cause the processor to perform a method comprising:

receiving a registry-registrar protocol (RRP) request for performing a domain name registration operation from a registrar;

parsing the request;

determining whether the registrar that sent the request is authorized to perform an action necessitated by the operation;

if the registrar is authorized, performing the operation;

storing changes necessitated by the operation in a domain name registry; and

sending a RRP response to the registrar, the response indicating success or failure of the operation.