ROUTING TABLE MAINTENANCE

• US 20140164645A1
• Filed: 12/06/2012
• Published: 06/12/2014
• Est. Priority Date: 12/06/2012
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Palani, Kumara Venkatesh
• Application Number:
  US13/706,667
• Publication Number:
  US 20140164645A1
• Time in Patent Office: Days
• US Class Current: 709/242
• CPC Class Codes: H04L 45/54 Organization of routing tables

Abstract

Among other things, one or more techniques and/or systems are provided for maintain a routing table. The routing table may comprise a routing statement associated with a destination. The routing statement may comprise a domain identifier, such as a URL, for the destination and a gateway identifier, such as an IP address, for a gateway through which communication traffic to the destination may be routed. During routing of a request, an IP address for the destination may be dynamically resolved based upon the domain identifier within the routing statement. The IP address may be cached for a restricted period of time so that subsequent requests may utilize the cached IP address. Because the routing statement is based upon a domain identifier (e.g., as opposed to a hardcoded static IP address), the routing statement may remain valid even though an IP address of the destination may change.

Claims

1. A method for maintaining a routing table, comprising:

maintaining a first routing statement within a routing table, the first routing statement comprising a domain identifier and a gateway identifier; and

responsive to receiving a request to access a destination associated with the domain identifier;

resolving an IP address associated with the domain identifier;

intersecting the IP address with the request to create an updated request; and

routing the updated request to a gateway associated with the gateway identifier.

2. The method of claim 1, the resolving an IP address comprising:

identifying a first entry within a cache, the first entry comprising a mapping of the domain identifier to the IP address.

3. The method of claim 1, the resolving an IP address comprising:

sending a lookup request for the domain identifier to a domain name system (DNS) server; and

receiving a response comprising the IP address from the DNS server.

4. The method of claim 3, comprising:

storing a first entry within a cache, the first entry comprising a mapping of the domain identifier to the IP address.

5. The method of claim 4, the response comprising a time to live (TTL) value, and the storing comprising specifying a cache expiration for the first entry based upon the TTL value.

6. The method of claim 4, comprising:

specifying a cache expiration for the first entry based upon at least one of;

cache configuration data;

or

traffic flow associated with the domain identifier.

7. The method of claim 4, the response from the DNS server comprising a second IP address, and the method comprising:

storing a second entry within the cache, the second entry comprising a second mapping of the domain identifier to the second IP address.

8. The method of claim 1, the intersecting comprising:

dynamically binding the IP address to the request en route during routing of the request.

9. The method of claim 1, comprising:

maintaining the routing table within a virtual server of a datacenter.

10. The method of claim 9, the gateway comprising a virtual switch hosted by the datacenter.

11. The method of claim 1, the intersecting comprising:

encapsulating the updated request with encapsulation data based upon the request corresponding to a hypervswitch.

12. The method of claim 11, the encapsulating comprising:

dynamically resolving the gateway based upon the gateway identifier and the encapsulation data.

13. The method of claim 1, comprising:

maintaining a second routing statement within the routing table, the second routing statement comprising a second domain identifier and a second gateway identifier, the second domain identifier different than the domain identifier and the second gateway identifier different than the gateway identifier.

14. A system for maintaining a routing table, comprising:

a routing table component configured to;

maintain a first routing statement within a routing table, the first routing statement comprising a domain identifier and a gateway identifier; and

a routing component configured to;

responsive to receiving a request to access a destination associated with the domain identifier;

resolve an IP address associated with the domain identifier;

intersect the IP address with the request to create an updated request; and

route the updated request to a gateway associated with the gateway identifier.

15. The system of claim 14, the routing component configured to:

identify a first entry within a cache, the first entry comprising a mapping of the domain identifier to the IP address.

16. The system of claim 14, the routing component configured to:

send a lookup request for the domain identifier to a domain name system (DNS) server; and

receive a response comprising the IP address from the DNS server.

17. The system of claim 16, the routing table component configured to:

store a first entry within a cache, the first entry comprising a mapping of the domain identifier to the IP address.

18. The system of claim 15, the routing table component configured to:

specify a cache expiration for the first entry based upon at least one of;

a time to live (TTL) value specified by a domain name server;

cache configuration data;

or

traffic flow associated with the domain identifier.

19. The system of claim 18, the routing table component configured to:

remove the first entry from the cache based upon expiration of the cache expiration.

20. A computer readable medium comprising instructions which when executed at least in part via a processing unit perform a method for maintaining a routing table, comprising:

maintaining a routing statement within a routing table, the routing statement comprising a domain identifier and a gateway identifier; and

responsive to receiving a request to access a destination associated with the domain identifier;

responsive to determining that a cache comprises an entry comprising a mapping of the domain identifier to an IP address, resolving the IP address for the request based upon the entry;

responsive to determining that the cache does not comprise the entry, resolving the IP address for the request based upon a domain name system (DNS) server lookup;

intersecting the IP address with the request to create an updated request; and

routing the updated request to a gateway associated with the gateway identifier.