Processing numeric addresses in a network router

• US 7,779,087 B2
• Filed: 01/18/2007
• Issued: 08/17/2010
• Est. Priority Date: 09/25/2001
• Status: Expired due to Fees

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: Enns, Robert P., Wilson, Reid Evan, Shafer, Philip Austin
• Primary Examiner(s): Chankong; Dohm
• Application Number:
  US11/654,933
• Publication Number:
  US 20070118621A1
• Time in Patent Office: 1,307 Days
• Field of Search: 709/219, 709/217, 709/203, 709/226, 709/245, 709/239, 709/246, 709/227, 709/223, 709/238
• US Class Current: 709/219
• CPC Class Codes: H04L 41/0803 Configuration setting
• CPC Class Codes: H04L 45/60 Router architectures
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]

Abstract

Processing of numeric addresses is facilitated by using a user interface, rather than system modules, to handle name resolution. Processing the addresses at the user interface level avoids delays and packet blocking problems associated with using system modules to perform the task. Relieving the system modules from the responsibility of processing numeric addresses allows them to process other requests, improving overall system efficiency.

Claims

1. A routing device comprising:

a network interface;

a client interface to receive an operational request from a network router client via the network interface;

a management server module communicatively coupled to the client interface; and

a router system module to receive the operational request from the management server module, process the operational request and to provide output to the client interface in a format including one or more tags that describe a type of the output,

wherein the client interface is configured to query a server based on the output, to receive from the server information associated with the output, and to provide a response from the server to the network router client based on the information.

2. The routing device of claim 1, wherein the output is a numeric address.

3. The routing device of claim 2, wherein the server includes a name server, and the information includes a symbolic name associated with the numeric address.

4. The routing device of claim 2, wherein the server includes an owner database, and the information includes an identification of an owner associated with the numeric address.

5. The routing device of claim 2, wherein the server includes a router policy database, and the information includes an identification of one or more router policies associated with the numeric address.

6. The routing device of claim 1, wherein the router system module provides the output to the client interface in an XML-tagged format.

7. The routing device of claim 1, wherein the client interface is further configured to render the output in a text format different from the format that describes a type of the output before querying the server.

8. The routing device of claim 7, wherein the text format is selected from the group consisting of an ASCII format, a UTF-8 format, and a Unicode format.

9. The routing device of claim 1, wherein the output comprises a listing of network peers identified by numeric addresses.

11. The routing device of claim 1, further comprising at least one of a chassis module, a device configuration module, and a routing protocol module.

10. A routing device comprising:

a network interface;

a client interface to receive an operational request from a network router client via the network interface; and

a router system module to receive the operational request from the management server module, process the operational request and to provide output to the client interface in a format including one or more tags that describe a type of the output,

wherein the router system module is one of a BGP protocol module, an OSPF protocol module or a firewall filter module,

wherein the client interface is configured to query a server based on the output, to receive from the server information associated with the output, and to provide a response from the server to the network router client based on the information.

12. A routing device comprising:

a network interface;

a client interface to receive an operational request from a network router client via the network interface; and

a system module to process the operational request and to provide a tagged IP address to the client interface,

wherein the system module is one of a BGP protocol module, an OSPF module or a firewall filter module,

wherein the client interface is configured to query a domain name server to resolve the IP address to a symbolic name and to provide the symbolic name to the network router client.

13. The routing device of claim 12, further comprising at least one of a chassis module, a device configuration module, and a routing protocol module.

14. A routing device comprising:

a network interface;

a client interface to receive an operational request from a network router client via the network interface; and

a management server module communicatively coupled to the client interface;

a system module to receive the operational request from the management server module, process the operational request and to provide a tagged IP address to the client interface,

wherein the client interface is configured to query a domain name server to resolve the IP address to a symbolic name and to provide the symbolic name to the network router client.

15. A routing device comprising:

a network interface;

a client interface to receive an operational request from a network router client via the network interface;

a management server module communicatively coupled to the client interface; and

a router system module to receive the operational request from the management server module and provide output to the client interface, wherein the output includes a tags that describe a numeric value as a network address,

wherein the client interface is configured to query a server based on the output to receive from the server a symbolic name associated with the network address, and

wherein the client interface is configured to provide a response to the network router client communicating the output from the router system module by replacing the network address identified by the tags in the output with the symbolic name received from the server.