Arrangement for retrieving routing information for establishing a bidirectional tunnel between a mobile router and a correspondent router

• US 7,886,075 B2
• Filed: 05/16/2003
• Issued: 02/08/2011
• Est. Priority Date: 05/16/2003
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Molteni, Marco, Villari, Massimo, Wetterwald, Patrick, Thubert, Pascal, Levy-Abegnoli, Eric M.
• Primary Examiner(s): Najjar; Saleh
• Assistant Examiner(s): Kim; Edward J
• Application Number:
  US10/438,853
• Publication Number:
  US 20040228343A1
• Time in Patent Office: 2,825 Days
• Field of Search: 709/238, 709/239, 709/240, 709/242, 709/225, 709/223, 709/227, 709/228, 709/229
• US Class Current: 709/238
• CPC Class Codes: H04L 12/4625 Single bridge functionality, e.g. connection of two networks over a single bridge
• CPC Class Codes: H04L 45/02 Topology update or discovery
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04W 40/248 Connectivity information update
• CPC Class Codes: H04W 40/28 for reactive routing
• CPC Class Codes: H04W 8/082 for traffic bypassing of mobility servers, e.g. location registers, home PLMNs or home agents
• CPC Class Codes: H04W 80/04 Network layer protocols, e.g. mobile IP [Internet Protocol]
• CPC Class Codes: H04W 84/005 Moving wireless networks
• CPC Class Codes: H04W 88/182 Network node acting on behalf of an other network entity, e.g. proxy

Abstract

A mobile router and a correspondent router, each configured for routing services for nodes within their routing prefixes associated with their respective routing tables, establish a secure, bidirectional tunnel based on a messaging protocol between each other and a route server resource. A reactive (i.e., on-demand) protocol is used that enables the requesting device (e.g, the mobile router, correspondent router), to obtain routing information in a secure manner from the route server. The mobile router sends a query via its home agent to the route server resource to identify the correspondent router serving the correspondent node. The mobile router sends a binding update request, specifying a home address and care-of address for the mobile router, to the correspondent router for establishment of a bidirectional tunnel. The correspondent router establishes the bidirectional tunnel, and updates its routing tables based on information from the route server resource.

Claims

1. A method in an Internet Protocol (IP) based mobile router configured for sending packets to a correspondent node, the method comprising:

receiving by the mobile router a packet destined for an IP address of the correspondent node;

determining by the mobile router a host domain name associated with the IP address by requesting a reverse lookup of the IP address from a name server;

identifying by the mobile router an authoritative name server for the host domain name based on generating and sending a query, specifying the host domain name obtained from the reverse lookup of the IP address, to a root name server for identification of the authoritative name server, and generating and sending a second query, specifying the host domain name obtained from the reverse lookup of the IP address, to the authoritative name server to determine if the authoritative name server sends a second IP address matching the IP address of the correspondent node;

generating and sending by the mobile router to the authoritative name server a request for identifying a correspondent router configured for establishing a tunnel for the host domain name, based on the authoritative name server sending the second IP address matching the IP address of the correspondent node; and

the mobile router initiating establishment of the tunnel, as a bidirectional tunnel that bypasses a home agent of the mobile router, with the correspondent router for sending packets to the correspondent node based on information received by the mobile router from the authoritative name server and responsive to the request sent by the mobile router.

2. The method of claim 1, wherein the sending step includes sending a second request for identifying an address prefix for the correspondent node that is reachable by the correspondent router, the method further including updating a routing table with the address prefix, received from the authoritative name server, for reaching additional nodes via the tunnel and that are within a subnetwork specified by the address prefix.

3. The method of claim 2, wherein the sending step includes:

specifying in the request a first resource record type configured for specifying correspondent routers configured for establishing the tunnel according to a prescribed mobile network protocol; and

specifying in the second request a second resource record type configured for specifying the address prefix for the correspondent node according to the prescribed mobile network protocol.

4. The method of claim 2, wherein the sending step includes:

sending the request to a first prescribed subdomain of the authoritative name server associated with identification of correspondent routers configured for establishing the tunnel according to a prescribed mobile network protocol;

sending the second request to a second prescribed subdomain of the authoritative name server associated with identification of address prefixes for identified nodes.

5. The method of claim 1, wherein the identifying step includes recursively sending the host name, following receiving a reply to the second query that specifies an identified name server, to successively identified name servers for identification of the authoritative name server.

6. The method of claim 1, wherein:

the determining step includes sending a query, specifying the reverse lookup, via a home tunnel terminated by the home agent, and

the initiating step includes;

(1) sending a binding update request to the correspondent router via a unidirectional tunnel to the correspondent router, the binding update request specifying a corresponding home address providing reachability to the mobile router via the home agent, a corresponding care-of address providing reachability to the mobile router via an attachment router, and a mobile router flag specifying that the binding update request was generated by a router that is mobile, and

(2) validating for the correspondent router that the home address is reachable via the care-of address.

7. A method in an Internet Protocol (IP) based router configured for sending and receiving packets for a correspondent node, the method comprising:

establishing by the router a bidirectional tunnel with a mobile router based on receiving a binding update that specifies a home address for the mobile router and a care-of address that specifies a point of attachment for the mobile router;

determining by the router a domain name associated with the home address by requesting a reverse lookup of the home address from a name server;

identifying by the router an authoritative name server for the domain name determined from the reverse lookup based on generating and sending a query, specifying the domain name, to a root name server for identification of the authoritative name server, and generating and sending a second query, specifying the domain name determined from the reverse lookup, to the authoritative name server to verify whether the authoritative name server can be trusted;

generating and sending by the router to the authoritative name server a request for identifying at least one address prefix reachable via the mobile router based on verifying the authoritative name server can be trusted; and

updating by the router an internal routing table to indicate the at least one address prefix is reachable via the bidirectional tunnel based on information received by the router from the authoritative name server and responsive to the request sent by the router.

8. The method of claim 7, wherein the sending step includes specifying within the request the address prefix for a mobile node having sent a packet to the correspondent node and being reachable via the mobile router, the updating step including updating the internal routing table to indicate the address prefix for the mobile node is reachable via the bidirectional tunnel.

9. The method of claim 8, wherein the sending step further includes specifying in the request a first resource record type configured for specifying the prefix for a specified mobile node and assigned to a corresponding mobile router configured for establishing the bidirectional tunnel according to a prescribed mobile network protocol.

10. The method of claim 8, wherein the sending step further includes sending the request to a prescribed subdomain of the authoritative name server associated with identification of an address prefix for a specified mobile node and assigned to a corresponding mobile router configured for establishing the bidirectional tunnel according to a prescribed mobile network protocol.

11. The method of claim 7, wherein the sending step includes specifying within the request all address prefixes reachable via the mobile router, the updating step including updating the internal routing table to indicate said all address prefixes are reachable via the bidirectional tunnel.

12. The method of claim 11, wherein the sending step further includes specifying in the request a first resource record type configured for specifying all prefixes assigned to a corresponding mobile router configured for establishing the bidirectional tunnel according to a prescribed mobile network protocol.

13. The method of claim 11, wherein the sending step further includes sending the request to a prescribed subdomain of the authoritative name server associated with identification of all address prefixes assigned to a corresponding mobile router configured for establishing the bidirectional tunnel according to a prescribed mobile network protocol.

14. An Internet Protocol (IP) based mobile router configured for sending packets to a correspondent node, the mobile router comprising:

means for receiving a packet destined for an IP address of the correspondent node;

means for determining a host domain name associated with the IP address by requesting a reverse lookup of the IP address from a name server;

means for identifying an authoritative name server for the host domain name based on generating and sending a query, specifying the host domain name obtained from the reverse lookup of the IP address, to a root name server for identification of the authoritative name server, and generating and sending a second query, specifying the host domain name obtained from the reverse lookup of the IP address, to the authoritative name server to determine if the authoritative name server sends a second IP address matching the IP address of the correspondent node, the means for identifying configured for generating and sending to the authoritative name server a request for identifying a correspondent router configured for establishing a tunnel for the host domain name, based on the authoritative name server sending the second IP address matching the IP address of the correspondent node; and

means for initiating establishment of the tunnel, as a bidirectional tunnel that bypasses a home agent of the mobile router, with the correspondent router for sending packets to the correspondent node based on information received by the mobile router from the authoritative name server and responsive to the request sent by the mobile router.

15. The mobile router of claim 14, wherein the identifying means is configured for sending a second request for identifying an address prefix for the correspondent node that is reachable by the correspondent router, the mobile router further comprising updating a routing table with the address prefix, received from the authoritative name server, for reaching additional nodes via the tunnel and that are within a subnetwork specified by the address prefix.

16. The mobile router of claim 15, wherein the identifying means is configured for:

specifying in the request a first resource record type configured for specifying correspondent routers configured for establishing the tunnel according to a prescribed mobile network protocol; and

specifying in the second request a second resource record type configured for specifying the address prefix for the correspondent node according to the prescribed mobile network protocol.

17. The mobile router of claim 15, wherein the identifying means is configured for:

sending the request to a first prescribed subdomain of the authoritative name server associated with identification of correspondent routers configured for establishing the tunnel according to a prescribed mobile network protocol; and

sending the second request to a second prescribed subdomain of the authoritative name server associated with identification of address prefixes for identified nodes.

18. The mobile router of claim 14, wherein the identifying means is configured for recursively sending the host name, following receiving a reply to the second query that specifies an identified name server, to successively identified name servers for identification of the authoritative name server.

19. The mobile router of claim 14, wherein:

the determining means is configured for sending a query, specifying the reverse lookup, via a home tunnel terminated by the home agent, and

the initiating means is configured for;

(1) sending a binding update request to the correspondent router via a unidirectional tunnel to the correspondent router, the binding update request specifying a corresponding home address providing reachability to the mobile router via the home agent, a corresponding care-of address providing reachability to the mobile router via an attachment router, and a mobile router flag specifying that the binding update request was generated by a router that is mobile, and

(2) validating for the correspondent router that the home address is reachable via the care-of address.

20. An Internet Protocol (IP) based router configured for sending and receiving packets for a correspondent node, the router comprising:

means for establishing a bidirectional tunnel with a mobile router based on receiving a binding update that specifies a home address for the mobile router and a care-of address that specifies a point of attachment for the mobile router;

means for determining a domain name associated with the home address by requesting a reverse lookup of the home address from a name server;

means for identifying an authoritative name server for the domain name determined from the reverse lookup based on generating and sending a query, specifying the domain name, to a root name server for identification of the authoritative name server, and generating and sending a second query, specifying the domain name determined from the reverse lookup, to the authoritative name server to verify whether the authoritative name server can be trusted, the identifying means configured for generating and sending to the authoritative name server a request for identifying at least one address prefix reachable via the mobile router based on the means for identifying verifying that the authoritative name server can be trusted; and

means for updating an internal routing table to indicate the at least one address prefix is reachable via the bidirectional tunnel based on information received by the router from the authoritative name server and responsive to the request sent by the router.

21. The router of claim 20, wherein the identifying means is configured for specifying within the request the address prefix for a mobile node having sent a packet to the correspondent node and being reachable via the mobile router, the updating means configured for updating the internal routing table to indicate the address prefix for the mobile node is reachable via the bidirectional tunnel.

22. The router of claim 21, wherein the identifying means is configured for specifying in the request a first resource record type configured for specifying the prefix for a specified mobile node and assigned to a corresponding mobile router configured for establishing the bidirectional tunnel according to a prescribed mobile network protocol.

23. The router of claim 21, wherein the identifying means is configured for sending the request to a prescribed subdomain of the authoritative name server associated with identification of an address prefix for a specified mobile node and assigned to a corresponding mobile router configured for establishing the bidirectional tunnel according to a prescribed mobile network protocol.

24. The router of claim 20, wherein the identifying means is configured for specifying within the request all address prefixes reachable via the mobile router, the updating means configured for updating the internal routing table to indicate said all address prefixes are reachable via the bidirectional tunnel.

25. The router of claim 24, wherein the identifying means is configured for specifying in the request a first resource record type configured for specifying all prefixes assigned to a corresponding mobile router configured for establishing the bidirectional tunnel according to a prescribed mobile network protocol.

26. The router of claim 24, wherein the identifying means is configured for sending the request to a prescribed subdomain of the authoritative name server associated with identification of all address prefixes assigned to a corresponding mobile router configured for establishing the bidirectional tunnel according to a prescribed mobile network protocol.

27. An Internet Protocol (IP) based mobile router configured for sending packets to a correspondent node, the mobile router comprising:

a query circuit configured for determining a host domain name associated with an IP address of the correspondent node based on requesting a reverse lookup of the IP address from a name server, the query circuit further configured for identifying an authoritative name server for the host domain name based on generating and sending a query, specifying the host domain name obtained from the reverse lookup of the IP address, to a root name server for identification of the authoritative name server, and generating and sending a second query, specifying the host domain name obtained from the reverse lookup of the IP address, to the authoritative name server to determine if the authoritative name server sends a second IP address matching the IP address of the correspondent node, the query circuit configured for generating and sending to the authoritative name server a request for identifying a correspondent router configured for establishing a tunnel for the host domain name, based on the authoritative name server sending the second IP address matching the IP address of the correspondent node;

the mobile router configured for initiating establishment of the tunnel, as a bidirectional tunnel that bypasses a home agent of the mobile router, with the correspondent router for sending packets to the correspondent node based on information received by the mobile router from the authoritative name server and responsive to the request sent by the mobile router.

28. The mobile router of claim 27, wherein the query circuit is configured for sending a second request for identifying an address prefix for the correspondent node that is reachable by the correspondent router, the mobile router further comprising a routing table for storing the address prefix, received from the authoritative name server, for reaching additional nodes via the tunnel and that are within a subnetwork specified by the address prefix.

29. The mobile router of claim 28, wherein the query circuit is configured for:

specifying in the request a first resource record type configured for specifying correspondent routers configured for establishing the tunnel according to a prescribed mobile network protocol; and

specifying in the second request a second resource record type configured for specifying the address prefix for the correspondent node according to the prescribed mobile network protocol.

30. The mobile router of claim 28, wherein the query circuit is configured for:

sending the request to a first prescribed subdomain of the authoritative name server associated with identification of correspondent routers configured for establishing the tunnel according to a prescribed mobile network protocol; and

sending the second request to a second prescribed subdomain of the authoritative name server associated with identification of address prefixes for identified nodes.

31. The mobile router of claim 27, wherein the query circuit is configured for recursively sending the host name, following receiving a reply to the second query that specifies an identified name server, to successively identified name servers for identification of the authoritative name server.

32. The mobile router of claim 27, wherein the query circuit is configured for sending a query, specifying the reverse lookup, via a home tunnel terminated by the home agent, the mobile router further comprising:

a binding update circuit configured for sending a binding update request to the correspondent router via a unidirectional tunnel to the correspondent router, the binding update request specifying a corresponding home address providing reachability to the mobile router via the home agent, a corresponding care-of address providing reachability to the mobile router via an attachment router, and a mobile router flag specifying that the binding update request was generated by a router that is mobile; and

a validation circuit configured for validating for the correspondent router that the home address is reachable via the care-of address.

33. An Internet Protocol (IP) based router configured for sending and receiving packets for a correspondent node, the router comprising:

a first circuit configured for establishing a bidirectional tunnel with a mobile router based on receiving a binding update that specifies a home address for the mobile router and a care-of address that specifies a point of attachment for the mobile router;

a query circuit configured for determining a domain name associated with the home address based on requesting a reverse lookup of the home address from a name server, the query circuit configured for identifying an authoritative name server for the domain name determined from the reverse lookup based on generating and sending a query, specifying the domain name, to a root name server for identification of the authoritative name server, and generating and sending a second query, specifying the domain name determined from the reverse lookup, to the authoritative name server to verify whether the authoritative name server can be trusted, the query circuit configured for generating and sending to the authoritative name server a request for identifying at least one address prefix reachable via the mobile router based on the query circuit verifying the authoritative name server can be trusted; and

a routing table configured for identifying the at least one address prefix is reachable via the bidirectional tunnel based on information received by the router from the authoritative name server and responsive to the request sent by the router.

34. The router of claim 33, wherein the query circuit is configured for specifying within the request the address prefix for a mobile node having sent a packet to the correspondent node and being reachable via the mobile router, the internal routing table updated to indicate the address prefix for the mobile node is reachable via the bidirectional tunnel.

35. The router of claim 34, wherein the query circuit is configured for specifying in the request a first resource record type configured for specifying the prefix for a specified mobile node and assigned to a corresponding mobile router configured for establishing the bidirectional tunnel according to a prescribed mobile network protocol.

36. The router of claim 34, wherein the query circuit is configured for sending the request to a prescribed subdomain of the authoritative name server associated with identification of an address prefix for a specified mobile node and assigned to a corresponding mobile router configured for establishing the bidirectional tunnel according to a prescribed mobile network protocol.

37. The router of claim 33, wherein the query circuit is configured for specifying within the request all address prefixes reachable via the mobile router, the internal routing table updated to indicate said all address prefixes are reachable via the bidirectional tunnel.

38. The router of claim 37, wherein the query circuit is configured for specifying in the request a first resource record type configured for specifying all prefixes assigned to a corresponding mobile router configured for establishing the bidirectional tunnel according to a prescribed mobile network protocol.

39. The router of claim 37, wherein the query circuit is configured for sending the request to a prescribed subdomain of the authoritative name server associated with identification of all address prefixes assigned to a corresponding mobile router configured for establishing the bidirectional tunnel according to a prescribed mobile network protocol.