Distribution of traffic flow criteria

• US 7,773,596 B1
• Filed: 02/19/2004
• Issued: 08/10/2010
• Est. Priority Date: 02/19/2004
• Status: Active Grant

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: Marques, Pedro R.
• Primary Examiner(s): Trost, IV; William
• Assistant Examiner(s): Shand; Roberta A
• Application Number:
  US10/782,291
• Time in Patent Office: 2,364 Days
• Field of Search: 370/238, 370/351, 370/352, 370/389, 370/392, 370/400, 370/408, 370/409, 370/463, 709238-242
• US Class Current: 370/392
• CPC Class Codes: H04L 45/04 Interdomain routing, e.g. hierarchical routing
• CPC Class Codes: H04L 45/38 Flow based routing

Abstract

Traffic flow criteria are distributed between routing devices. More specifically, a routing protocol, such as the Border Gateway Protocol (BGP), may be extended in a manner that allows fine-grain criteria to be conveyed for application to network traffic. For example, a flow specification data type may be defined in accordance with BGP to allow a variable number of packet flow attributes to be specified, such as source information, destination information, port information, protocol or other flow criteria. In this manner, traffic flow criteria are specified in a way that cannot be expressed using destination address prefixes only. The flow specification data type may be defined as network layer reachability information (NLRI) that is associated with a route advertised in accordance with BGP.

Claims

1. A method for distributing traffic flow criteria between network devices, the method comprising:

defining a flow specification data type for a routing protocol, wherein the flow specification data type allows a variable number of packet flow attributes to be specified for a packet flow through a network;

generating, with a first routing device, a message that encodes routing topology information, wherein the routing topology information defines at least one route between a first network device and a second network device, and traffic flow criteria specifying the packet flow in accordance with the flow specification data type; and

communicating, with the first routing device, the message to a second routing device to direct the second routing device to control network traffic based on the traffic flow criteria,

wherein the traffic flow criteria comprises source information that identifies a source network device of the packet flow, wherein the traffic flow criteria specifies an appropriate action that is performed on the network packet.

2. The method of claim 1, wherein defining a flow specification data type comprises defining the flow specification data type as information associated with a route advertised by the message.

3. The method of claim 1, wherein defining a flow specification data type comprises defining the flow specification data type as network layer reachability information (NLRI) that is associated with a route advertised by the message.

4. The method of claim 1, wherein defining a flow specification data type comprises defining the flow specification type to include a length field that indicates the number of packet flow attributes specified.

5. The method of claim 1, the flow specification data type including multiple subcomponents, wherein defining a flow specification data type comprises defining each of the subcomponents to include a subcomponent type field and a set of value fields.

6. The method of claim 1, wherein defining a flow specification data type comprises defining a subcomponent for specifying a destination prefix.

7. The method of claim 1, wherein defining a flow specification data type comprises defining subcomponents for specifying a destination prefix, a source prefix, a protocol, a source port, a destination port, an ICMP type, and a packet length.

8. The method of claim 1, wherein the routing protocol is the Border Gateway Protocol (BGP).

9. The method of claim 1, wherein defining a flow specification data type comprises redefining a preexisting data type of the routing protocol to define the flow specification data type.

10. The method of claim 1, wherein defining a flow specification data type comprises defining the flow specification data type as an application-specific data type in accordance with the routing protocol.

11. The method of claim 1, wherein defining a flow specification data type further comprises assigning an application-specific identifier to the flow specification data type to direct the router to install the traffic flow criteria within an independent routing information base (RIB).

12. The method of claim 1, further comprising:

assigning an application-specific identifier to the flow specification data type; and

configuring a policy to selectively enable distribution of the traffic flow criteria based on the application-specific identifier.

13. The method of claim 12, wherein assigning an application-specific identifier comprises assigning an Address Family Identifier (AFI) and Subsequent Address Family Identifier (SAFI) to the flow specification data type.

14. The method of claim 1, wherein the appropriate action includes one of load balancing, rate limiting, and filtering.

70. The method of claim 1, wherein generating a message further comprises encoding routing information in accordance with the routing protocol.

71. The method of claim 70, wherein the routing protocol is the Border Gateway Protocol (BGP).

72. The method of claim 70, wherein communicating the message to a routing device to direct the routing device to control network traffic further comprises communicating the message to a routing device to direct the routing device to control network traffic based on the routing information.

15. A method for distributing traffic flow criteria between network devices, the method comprising:

receiving a routing communication that encodes routing topology information, wherein the routing topology information defines at least one route between a first network device and a second network device, and traffic flow criteria specifying the packet flow in accordance with a flow specification data type for a routing protocol, wherein the flow specification data type allows a variable number of packet flow attributes to be specified for a packet flow through a network; and

controlling network traffic in accordance with the traffic flow criteria,

wherein the traffic flow criteria comprises source information that identifies a source network device of the packet flow, wherein the traffic flow criteria specifies an appropriate action that is performed on the network packet.

16. The method of claim 15, wherein controlling network traffic includes one of load balancing, rate limiting, and filtering the network traffic in accordance with the traffic flow criteria.

17. The method of claim 15, wherein the flow specification data type is defined as information associated with a route advertised by the routing communication.

18. The method of claim 17, wherein the flow specification data type is defined as network layer reachability information (NLRI) that is associated with a route advertised by the message.

19. The method of claim 15, wherein the flow specification data type includes a length field for specifying the number of packet flow attributes specified.

20. The method of claim 15, the flow specification data type including multiple subcomponents, wherein each of the subcomponents includes a subcomponent type field and a set of value fields.

21. The method of claim 15, wherein the appropriate action includes one of load balancing, rate limiting, and filtering.

22. The method of claim 15, wherein the routing communication further specifies a route to a network destination, the method further comprising:

comparing the specified route to a routing information base; and

rejecting the traffic flow criteria based on the comparison when the route does not specify a preferred path to the network destination.

23. The method of claim 15, wherein receiving a routing communication comprises communicating with a router in accordance with the routing protocol.

24. The method of claim 15, wherein the routing protocol is the Border Gateway Protocol (BGP).

25. The method of claim 15, wherein the flow specification data type is encoded by redefining a preexisting data type of the routing protocol to define the flow specification data type.

26. The method of claim 15, wherein the flow specification data type is defined as an application-specific data type in accordance with the routing protocol.

27. The method of claim 15, wherein an application-specific identifier is assigned to the flow specification data type to direct the receiving router to install the traffic flow criteria within an independent routing information base (RIB).

28. The method of claim 15, wherein an application-specific identifier is assigned to the flow specification data type.

29. The method of claim 28, wherein the application-specific identifier includes an Address Family Identifier (AFI) and Subsequent Address Family Identifier (SAFI).

30. The method of claim 15, further comprising updating a log that includes information about the routing communication.

73. The method of claim 15, wherein the routing communication further encodes routing information in accordance with the routing protocol.

74. The method of claim 73, wherein the routing protocol is the Border Gateway Protocol (BGP).

75. The method of claim 73, wherein controlling network traffic further comprises controlling network traffic based on the routing information.

31. A network device comprising:

a control unit to generate a message that encodes routing topology information, wherein the routing topology information defines at least one route between a first network device and a second network device, and traffic flow criteria specifying the packet flow in accordance with a flow specification data type, wherein the flow specification data type allows a variable number of packet flow attributes to be specified for a packet flow through a network; and

an interface card to communicate the message to a routing device in accordance with a routing protocol,

wherein the message directs the control unit to apply an appropriate action to network traffic based on the traffic flow criteria, and

wherein the traffic flow criteria comprises source information that identifies a source network device of the packet flow.

32. The network device of claim 31, wherein the control unit defines the flow specification data type as information associated with a route advertised by the message.

33. The network device of claim 32, wherein the control unit defines the flow specification data type as network layer reachability information (NLRI) that is associated with a route advertised by the message.

34. The network device of claim 31, wherein the control unit defines subcomponents for specifying a destination prefix, a source prefix, a protocol, a source port, a destination port, an ICMP type, and a packet length.

35. The network device of claim 31, wherein the routing protocol is the Border Gateway Protocol (BGP).

36. The network device of claim 31, wherein the control unit redefines a preexisting data type of the routing protocol to define the flow specification data type.

37. The network device of claim 31, wherein the control unit defines the flow specification data type as an application-specific data type in accordance with the routing protocol.

76. The network device of claim 31, wherein the message further encodes routing information in accordance with the routing protocol.

77. The network device of claim 76, wherein the routing protocol is the Border Gateway Protocol (BGP).

78. The network device of claim 76, wherein the message further directs the control unit to apply an appropriate action to network traffic based on the routing information.

38. A network device comprising:

an interface card to receive routing communication that encodes routing topology information, wherein the routing topology information defines at least one route between a first network device and a second network device, and traffic flow criteria specifying the packet flow in accordance with a flow specification data type for a routing protocol, wherein the flow specification data type allows a variable number of packet flow attributes to be specified for a packet flow through a network; and

a control unit to compare network traffic to the traffic flow criteria, and apply an appropriate action to the network traffic,

wherein the traffic flow criteria comprises source information that identifies a source network device of the packet flow.

39. The network device of claim 38, wherein the appropriate action includes one of load balancing, rate limiting, and filtering the network traffic in accordance with the traffic flow criteria.

40. The network device of claim 38, wherein the flow specification data type is defined as information associated with a route advertised by the routing communication.

41. The network device of claim 38, wherein the flow specification data type is defined as network layer reachability information (NLRI) that is associated with a route advertised by the message.

42. The network device of claim 38, wherein the routing protocol is the Border Gateway Protocol (BGP).

43. The network device of claim 38, wherein the flow specification data type is defined as an application-specific data type in accordance with the routing protocol.

44. The network device of claim 38, wherein an application-specific identifier is assigned to the flow specification data type, and the control unit install the traffic flow criteria within an independent routing information base (RIB) in response to the application-specific identifier.

79. The network device of claim 38, wherein the routing communication further encodes routing information in accordance with the routing protocol.

80. The network device of claim 79, wherein the routing protocol is the Border Gateway Protocol (BGP).

81. The network device of claim 79, wherein the control unit further applies an appropriate action to network traffic based on the routing information.

45. A system comprising:

a first network device to generate a message that encodes routing topology information, wherein the routing topology information defines at least one route between a first network device and a second network device, and traffic flow criteria specifying the packet flow in accordance with a flow specification data type, and communicate the message to a second routing device via a routing protocol, wherein the flow specification data type allows a variable number of packet flow attributes to be specified for a packet flow through a network; and

a second network device to receive the message, compare network traffic to the traffic flow criteria, and apply an appropriate action to the network traffic based on the traffic flow criteria,

wherein the traffic flow criteria comprises source information that identifies a source network device of the packet flow.

46. The system of claim 45, wherein the first network device defines the flow specification data type as information associated with a route advertised by the message.

47. The system of claim 45, wherein the first network device defines the flow specification data type as network layer reachability information (NLRI) that is associated with a route advertised by the message.

48. The system of claim 45, wherein the first network device defines subcomponents for specifying a destination prefix, a source prefix, a protocol, a source port, a destination port, an ICMP type, and a packet length.

49. The system of claim 45, wherein the routing protocol is the Border Gateway Protocol (BGP).

50. The system of claim 45, wherein the first network device defines a preexisting data type of the routing protocol to define the flow specification data type.

51. The system of claim 45, wherein the appropriate action includes one of load balancing, rate limiting, and filtering the network traffic in accordance with the traffic flow criteria.

52. The system of claim 45, wherein the flow specification data type is defined as an application-specific data type in accordance with the routing protocol.

53. The system of claim 45, wherein an application-specific identifier is assigned to the flow specification data type.

82. The system of claim 45, wherein generating a message further comprises generating a message that encodes routing information in accordance with the routing protocol.

83. The system of claim 82, wherein the routing protocol is the Border Gateway Protocol (BGP).

84. The system of claim 82, wherein applying an appropriate action to the network traffic further comprises applying an appropriate action to network traffic based on the routing information.

54. A computer-readable medium comprising instructions for causing a programmable processor to:

define a flow specification data type for a routing protocol, wherein the flow specification data type allows a variable number of packet flow attributes to be specified for a packet flow through a network;

generate a message that encodes routing topology information, wherein the routing topology information defines at least one route between a first network device and a second network device, and traffic flow criteria specifying the packet flow in accordance with the flow specification data type; and

communicate the message to a routing device to direct the routing device to control network traffic based on the traffic flow criteria,

wherein the traffic flow criteria comprises source information that identifies a source network device of the packet flow, wherein the traffic flow criteria specifies an appropriate action that is performed on the network packet.

55. The computer-readable medium of claim 54, wherein defining a flow specification data type comprises defining the flow specification data type as information associated with a route advertised by the message.

56. The computer-readable medium of claim 54, wherein defining a flow specification data type comprises defining the flow specification data type as network layer reachability information (NLRI) that is associated with a route advertised by the message.

57. The computer-readable medium of claim 54, wherein defining a flow specification data type comprises defining subcomponents for specifying a destination prefix, a source prefix, a protocol, a source port, a destination port, an ICMP type, and a packet length.

58. The computer-readable medium of claim 54, wherein the routing protocol is the Border Gateway Protocol (BGP).

59. The computer-readable medium of claim 54, wherein defining a flow specification data type comprises redefining a preexisting data type of the routing protocol to define the flow specification data type.

60. The computer-readable medium of claim 54, wherein defining a flow specification data type comprises defining the flow specification data type as an application-specific data type in accordance with the routing protocol.

61. The computer-readable medium of claim 54, wherein defining a flow specification data type further comprises assigning an application-specific identifier to the flow specification data type to direct the router to install the traffic flow criteria within an independent routing information base (RIB).

85. The computer-readable medium of claim 54, wherein generating a message further comprises generating a message that encodes routing information in accordance with the routing protocol.

86. The system of claim 85, wherein the routing protocol is the Border Gateway Protocol (BGP).

87. The system of claim 85, wherein communicating the message to a routing device to direct the routing device to control network traffic further comprises communicating the message to a routing device to direct the routing device to control network traffic based on the routing information.

62. A computer-readable medium comprising instructions for causing a programmable processor to:

receive a routing communication that encodes routing topology information, wherein the routing topology information defines at least one route between a first network device and a second network device, and traffic flow criteria specifying the packet flow in accordance with a flow specification data type for a routing protocol, wherein the flow specification data type allows a variable number of packet flow attributes to be specified for a packet flow through a network; and

control network traffic in accordance with the traffic flow criteria,

wherein the traffic flow criteria comprises source information that identifies a source network device of the packet flow, wherein the traffic flow criteria specifies an appropriate action that is performed on the network packet.

63. The computer-readable medium of claim 62, further comprising instructions to cause the processor to control network traffic by performing one of load balancing, rate limiting, and filtering the network traffic in accordance with the traffic flow criteria.

64. The computer-readable medium of claim 62, wherein the flow specification data type is defined as information associated with a route advertised by the routing communication.

65. The computer-readable medium of claim 62, wherein the flow specification data type is defined as network layer reachability information (NLRI) that is associated with a route advertised by the message.

66. The computer-readable medium of claim 62, wherein the routing protocol is the Border Gateway Protocol (BGP).

67. The computer-readable medium of claim 62, wherein the flow specification data type is encoded by redefining a preexisting data type of the routing protocol to define the flow specification data type.

68. The computer-readable medium of claim 62, wherein the flow specification data type is defined as an application-specific data type in accordance with the routing protocol.

69. The computer-readable medium of claim 62, wherein an application-specific identifier is assigned to the flow specification data type.

88. The computer-readable medium of claim 62, wherein the routing communication further encodes routing information in accordance with a routing protocol.

89. The network device of claim 88, wherein the routing protocol is the Border Gateway Protocol (BGP).

90. The network device of claim 88, wherein controlling network traffic further comprises controlling network traffic based on the routing information.