Routing protocol interface for generalized data distribution

• US 9,137,116 B1
• Filed: 07/12/2012
• Issued: 09/15/2015
• Est. Priority Date: 07/12/2012
• Status: Active Grant

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: Rijsman, Bruno
• Primary Examiner(s): YEUNG, MANG HANG
• Application Number:
  US13/547,978
• Time in Patent Office: 1,160 Days
• Field of Search: 370/392, 370/254, 709238-244
• US Class Current: 1/1
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 45/02 Topology update or discovery
• CPC Class Codes: H04L 45/74 Address processing for routing
• CPC Class Codes: H04L 49/351 for local area network [LAN], e.g. Ethernet switches
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/18 Multiprotocol handlers, e.g. single devices capable of handling multiple protocols

Abstract

In general, techniques are described for defining an interface to a network router software infrastructure that allows developers to dynamically extend a routing protocol executed by the network router to distribute data throughout the routing domain for use with custom applications. In some examples, a routing protocol process executing on a control plane of a network device may expose an interface, such as an Application Programming Interface (API), that defines methods and parameters for extending the operation of a routing protocol executed by the routing protocol process. Third-party developers may then build custom applications that invoke the interface of the routing protocol process to define new routing protocol messages or message payloads, inject application-specific data into the routing protocol process for distribution within the newly defined messages/payloads, and extract application-specific data that is carried by newly defined messages/payloads that are originated by another network device in the routing domain.

Claims

1. A network device comprising:

a control unit comprising one or more processors;

one or more interface cards;

a routing protocol process configured to execute on the control unit to send a first routing protocol advertisement to a peer network device via the interface cards in accordance with a routing protocol, wherein the first routing protocol advertisement specifies a route to a network address and a predefined address family identifier that identifies a network layer protocol associated with the network address,

an application configured to execute on the control unit;

address family configuration data,

wherein the routing protocol process is configured to receive, from the application via an interface of the routing protocol process, a request to dynamically extend the routing protocol process to register a new address family identifier for the routing protocol, wherein the new address family identifier is associated with the application,

wherein the routing protocol process is configured to register, in response to the request, the new address family identifier in the address family configuration data, and

wherein the routing protocol process is configured to send, to the peer network device in response to receiving application data from the application via the interface, a second routing protocol advertisement that specifies the new address family identifier and includes the application data.

2. The network device of claim 1,

wherein the application is configured to send, to the routing protocol process via the interface, a request that the routing protocol process inject the application data into the routing protocol in association with the new address family identifier,

wherein the routing protocol process is configured to generate, in response to the request that the routing protocol process inject the application data, the second routing protocol advertisement.

3. The network device of claim 2, further comprising:

a set of one or more policies that each define a condition and a corresponding action that intermediate operations of the application and the routing protocol process,

wherein the routing protocol process is configured to apply the policies to the request that the routing protocol process inject the application data, and

wherein the routing protocol process is configured to generate the routing protocol advertisement only when the request satisfies the policies.

4. The network device of claim 1,

wherein the routing protocol process is configured to receive a third routing protocol advertisement that specifies the new address family identifier, and

wherein the routing protocol process is configured to store new application data, carried by the third routing protocol advertisement that specifies the new address family identifier, to a database associated with the new address family identifier.

5. The network device of claim 1,

wherein the request to dynamically extend the routing protocol process to register the new address family identifier for the routing protocol comprises a callback for the application,

wherein the routing protocol process is configured to receive a third routing protocol advertisement that specifies the new address family identifier and includes additional application data, and

wherein the routing protocol process is configured to provide the additional application data to the application using the callback.

6. The network device of claim 1, wherein the application comprises a third-party application that is not supplied by a vendor or manufacturer of the network device.

7. The network device of claim 1,

wherein the routing protocol comprises Border Gateway Protocol, and

wherein the new address family identifier comprises a combination of an Address Family Identifier and a Subsequent Address Family Identifier.

8. The network device of claim 7,

wherein the routing protocol process is configured to receive a third routing protocol advertisement that specifies the new address family identifier and includes additional application data,

wherein the routing protocol process is configured to store the additional application data to a routing information base that stores Network Layer Reachability Information for the new address family identifier.

9. The network device of claim 1, further comprising:

a management interface configured to present an interface by which the application dynamically registers an inject function for the new address family identifier by which an administrator invokes the interface of the routing protocol process to inject application data, in association with the new address family identifier, into the routing protocol process,

wherein the routing protocol process is configured to generate a third routing protocol advertisement that specifies the new address family identifier and includes the injected application data, and

wherein the routing protocol process is configured to send, to the peer network device, the third routing protocol advertisement that specifies the new address family identifier and includes the injected application data.

10. The network device of claim 1, further comprising:

a management interface process configured to present an interface by which the application dynamically registers a display function for the new address family identifier,

wherein an administrator invokes the display function, and

wherein the management interface process is configured to format the application data stored in the new database in accordance with the display function and returns the formatted application data to the administrator.

11. The network device of claim 1,

wherein the application comprises a management interface process configured to present a registration interface by which an administrator supplies the new address family identifier.

12. The network device of claim 11,

wherein the registration interface includes an application data formatting information parameter by which an administrator supplies application data formatting information,

wherein the management interface process is configured to format application data stored in the new database and return the formatted application data to the administrator.

13. A method comprising:

sending, by a routing protocol process executing on a network device, a first routing protocol advertisement to a peer network device in accordance with a routing protocol, wherein the first routing protocol advertisement specifies a route to a network address and a predefined address family identifier that identifies a network layer protocol associated with the network address;

receiving, by the routing protocol process from an application executing on the network device and via an interface of the routing protocol process, a request to dynamically extend the routing protocol process to register a new address family identifier for the routing protocol, wherein the new address family identifier is associated with the application;

registering, by the routing protocol process in response to the request, the new address family identifier; and

sending, by the routing protocol process to the peer network device in response to receiving application data from the application via the interface, a second routing protocol advertisement that specifies the new address family identifier and includes the application data.

14. The method of claim 13, further comprising:

sending, by the application to the routing protocol process via the interface of the routing protocol process, a request that the routing protocol process inject the application data into the routing protocol in association with the new address family identifier; and

generating, by the routing protocol process in response to the request that the routing protocol process inject the application data, the second routing protocol advertisement.

15. The method of claim 14, further comprising:

storing a set of one or more policies that each define a condition and a corresponding action that intermediate operations of the application and the routing protocol process;

applying the policies to the request that the routing protocol process inject the application data; and

generating the routing protocol advertisement only when the request satisfies the policies.

16. The method of claim 13, further comprising:

receiving a third routing protocol advertisement that specifies the new address family identifier; and

storing, by the routing protocol process, new application data, carried by the third routing protocol advertisement that specifies the new address family identifier, to a database associated with the new address family identifier.

17. The method of claim 13,

wherein the request to dynamically extend the routing protocol process to register the new address family identifier for the routing protocol comprises a callback for the application;

receiving, by the routing protocol process, a third routing protocol advertisement that specifies the new address family identifier and includes additional application data;

providing, by the routing protocol process to the application using the callback, the additional application data.

18. The method of claim 13, wherein the application comprises a third-party application that is not supplied by a vendor or manufacturer of the network device.

19. The method of claim 13,

wherein the routing protocol comprises Border Gateway Protocol, and

wherein the new address family identifier comprises a combination of an Address Family Identifier and a Subsequent Address Family Identifier.

20. The method of claim 19, further comprising:

receiving, by the routing protocol process, a third routing protocol advertisement that specifies the new address family identifier and includes additional application data;

storing the additional application data to a routing information base that stores Network Layer Reachability Information for the new address family identifier.

21. The method of claim 13, further comprising:

dynamically registering, with the application by an interface of a management interface process of the network device, an inject function for the new address family identifier by which an administrator invokes the interface of the routing protocol process to inject application data, in association with the new address family identifier, into the routing protocol process;

generating, by the routing protocol process, a third routing protocol advertisement that specifies the new address family identifier and includes the injected application data; and

sending, by the routing protocol process to the peer network device, the third routing protocol advertisement that specifies the new address family identifier and includes the injected application data.

22. The method of claim 13, further comprising:

dynamically registering, with the application by an interface of a management interface process, a display function for the new address family identifier;

formatting the application data in accordance with the display function; and

outputting the formatted application data to an administrator.

23. The method of claim 13,

wherein the application comprises a management interface process that presents a registration interface by which an administrator supplies the new address family identifier.

24. The method of claim 23,

wherein the registration interface includes an application data formatting information parameter by which an administrator supplies application data formatting information,

wherein the management interface process formats application data stored in the new database and returns the formatted application data to the administrator.

25. A non-transitory computer-readable medium comprising instructions for causing one or more programmable processors of a network device to:

send, by a routing protocol process, a first routing protocol advertisement to a peer network device in accordance with a routing protocol, wherein the first routing protocol advertisement specifies a route to a network address and a predefined address family identifier that identifies a network layer protocol associated with the network address;

receive, by the routing protocol process from an application executing on the network device and via an interface of the routing protocol process, a request to dynamically extend the routing protocol process to register a new address family identifier for the routing protocol, wherein the new address family identifier is associated with the application;

register, by the routing protocol process in response to the request, the new address family identifier; and

send, by the routing protocol process to the peer network device in response to receiving application data from the application via the interface, a second routing protocol advertisement that specifies the new address family identifier and includes the application data.