System and method for improving spoke to spoke communication in a computer network

• US 8,625,610 B2
• Filed: 10/12/2007
• Issued: 01/07/2014
• Est. Priority Date: 10/12/2007
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Asati, Rajiv, Khalid, Mohamed, Weis, Brian E., Sethi, Pratima Pramod
• Primary Examiner(s): Ton, Dang
• Assistant Examiner(s): RANDHAWA, MANDISH K
• Application Number:
  US11/871,508
• Publication Number:
  US 20090097417A1
• Time in Patent Office: 2,279 Days
• Field of Search: 709/223, 709/224, 709238-243, 713150-153, 713/162, 713/163, 370/389, 370/255, 370/401, 370/395.31
• US Class Current: 370/401
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00
• CPC Class Codes: H04L 45/02 Topology update or discovery
• CPC Class Codes: H04L 45/17 Shortcut routing, e.g. using next hop resolution protocol [NHRP]
• CPC Class Codes: H04L 63/0272 Virtual private networks
• CPC Class Codes: H04L 63/061 for key exchange, e.g. in peer-to-peer networks cryptographic mechanisms or cryptographic arrangements for key agreement H04L9/0838
• CPC Class Codes: H04L 63/164 at the network layer

Abstract

Various embodiments of the disclosed subject matter provide methods and systems for improved efficiency in spoke-to-spoke network communication. Embodiments provide systems and methods for registering a spoke with a hub, updating at least one database with spoke registration information at the hub, and advertising the spoke registration information to other spokes using a single control plane that includes transport security, peer discovery, and unicast routing information.

Claims

1. A method comprising:

registering a spoke with a hub;

updating at least one database with spoke registration information at the hub;

encoding into the spoke registration information next hop information and prefix reachability information within extensions of a group key management protocol thereby eliminating a need for use of a next hop routing protocol; and

advertising the spoke registration information to other spokes using a single control plane provided by the extensions of the group key management protocol to integrate transport security, peer discovery, and unicast routing information.

2. The method as claimed in claim 1 including sending information corresponding to at least a portion of the at least one database to a plurality of registered spokes via a Group Key Management Protocol (GKMP).

3. The method as claimed in claim 2 wherein the GKMP includes a set of GKMP extensions.

4. The method as claimed in claim 3 wherein the set of GKMP extensions carry information pertaining to the single control plane.

5. The method as claimed in claim 3 wherein the set of GKMP extensions carry information pertaining to the single control plane, the information including next-hop mapping information.

6. The method as claimed in claim 3 wherein the set of GKMP extensions carry information pertaining to the single control plane, the information including prefix reachability information.

7. A method comprising:

registering a spoke with a hub via a Group Key Management Protocol (GKMP);

updating at least one database with spoke registration information;

encoding into the spoke registration information next hop information and prefix reachability information within extensions of the Group Key Management Protocol (GKMP) thereby eliminating a need for use of a next hop routing protocol; and

sending information corresponding to at least a portion of the at least one database to a plurality of registered spokes via a single control plane provided by the extensions of the Group Key Management Protocol (GKMP).

8. The method as claimed in claim 7 wherein the GKMP includes a set of GKMP extensions.

9. The method as claimed in claim 7 wherein registering a spoke with a hub includes providing, in a GKMP message for the hub, spoke registration information including an IP address, and next hop mapping information corresponding to the registering spoke.

10. The method as claimed in claim 7 wherein registering a spoke with a hub includes providing, in a GKMP message for the hub, spoke registration information including an IP address, next hop mapping information, and local prefix reachability information corresponding to the registering spoke.

11. The method as claimed in claim 9 wherein the next hop mapping information corresponds to an association of one or more next-hop IP addresses with one or more IP addresses.

12. The method as claimed in claim 7 including obtaining next hop mapping information and local prefix reachability information from the at least one database.

13. The method as claimed in claim 7 including obtaining next hop mapping information and local prefix reachability information in either an aggregated manner or an individual manner.

14. The method as claimed in claim 7 wherein the hub maintains the at least one database.

15. The method as claimed in claim 7 wherein the spoke maintains a local spoke database which includes information corresponding to at least a portion of the at least one database.

16. The method as claimed in claim 15 wherein the spoke uses the information from the local spoke database to update IP routing or forwarding table entries in the spoke.

17. The method as claimed in claim 7 wherein the hub uses the information from the at least one database to update IP routing or forwarding table entries in the hub.

18. A method comprising:

registering a spoke with a hub using extensions of a Group Key Management Protocol (GKMP) message to provide spoke registration information including an IP address, next hop mapping information, and local prefix reachability information corresponding to the registering spoke thereby eliminating a need for use of a next hop routing protocol;

updating at least one database with the spoke registration information; and

sending information corresponding to at least a portion of the at least one database to a plurality of registered spokes via a single control plane provided by the extensions of the Group Key Management Protocol (GKMP) message, the information having encoded therein next hop information and prefix reachability information within the extensions of the Group Key Management Protocol (GKMP) thereby eliminating a need for use of the next hop routing protocol.

19. The method as claimed in claim 18 wherein the hub maintains the at least one database.

20. The method as claimed in claim 18 wherein the spoke maintains a local spoke data store which includes information corresponding to at least a portion of the at least one database.

21. An apparatus comprising:

means for registering a spoke with a hub via a Group Key Management Protocol (GKMP);

means for updating at least one database with spoke registration information;

encoding into the spoke registration information next hop information and prefix reachability information within extensions of the Group Key Management Protocol (GKMP) thereby eliminating a need for use of a next hop routing protocol; and

means for sending information corresponding to at least a portion of the at least one database to a plurality of registered spokes via a single control plane provided by the extensions of the Group Key Management Protocol (GKMP).

22. The apparatus as claimed in claim 21 wherein the GKMP includes a set of GKMP extensions.

23. A hub apparatus comprising:

a hub/spoke interface to receive a spoke registration message from a spoke via a Group Key Management Protocol (GKMP);

a hub database for storage of spoke registration information from the spoke registration message; and

a hub updater to encode into the spoke registration information next hop information and prefix reachability information within extensions of the Group Key Management Protocol (GKMP) thereby eliminating a need for use of a next hop routing protocol, the hub updater further to send information corresponding to at least a portion of the hub database to a plurality of registered spokes via a single control plane provided by the extensions of the Group Key Management Protocol (GKMP).

24. The hub apparatus as claimed in claim 23 wherein the spoke registration message includes an IP address, next hop mapping information, and local prefix reachability information corresponding to the registering spoke.