Abstract: To mitigate attacks utilizing compromised DNS caches, a server gateway provides clients with unique IP addresses to contact the server. Packets sent to a server IP address from a particular client which are not linked to that particular with the server gateway are dropped. Thus, even if a client is compromised, the IP address for the server in the client's DNS cache cannot be used by other machines or virtual machines. With a one to one client to server IP address relationship, malicious actors cannot use numerous machines or virtual machines to overload the server with requests.

Abstract: Various embodiments of the present invention relating to a subscriber fairness solution are disclosed. The subscriber fairness solution contemplates a variety of improved techniques for using a flow-based statistical collection mechanism to monitor subscriber usage across various attributes (e.g., subscriber byte count, flow count, etc.) and maintain subscriber usage information for different time frames. In embodiments, the subscriber fairness solution includes a detection phase and a mitigation phase. In the detection phase, “outliers,” or subscribers who are using more than their fair share of network resources, are identified. In the mitigation phase, appropriate action is taken to resolve the constraints on the network resources, caused by these outliers. The subscriber fairness solution may be embodied in hardware, software, or a composite approach of both hardware and software.

Abstract: Various embodiments of the present invention relating to a subscriber fairness solution are disclosed. The subscriber fairness solution contemplates a variety of improved techniques for using a flow-based statistical collection mechanism to monitor subscriber usage across various attributes (e.g., subscriber byte count, flow count, etc.) and maintain subscriber usage information for different time frames. In embodiments, the subscriber fairness solution includes a detection phase and a mitigation phase. In the detection phase, “outliers,” or subscribers who are using more than their fair share of network resources, are identified. In the mitigation phase, appropriate action is taken to resolve the constraints on the network resources, caused by these outliers. The subscriber fairness solution may be embodied in hardware, software, or a composite approach of both hardware and software.

Abstract: Various embodiments of the present invention relating to a subscriber fairness solution are disclosed. The subscriber fairness solution contemplates a variety of improved techniques for using a flow-based statistical collection mechanism to monitor subscriber usage across various attributes (e.g., subscriber byte count, flow count, etc.) and maintain subscriber usage information for different time frames. In embodiments, the subscriber fairness solution includes a detection phase and a mitigation phase. In the detection phase, “outliers,” or subscribers who are using more than their fair share of network resources, are identified. In the mitigation phase, appropriate action is taken to resolve the constraints on the network resources, caused by these outliers. The subscriber fairness solution may be embodied in hardware, software, or a composite approach of both hardware and software.

Abstract: A mechanism is disclosed for identifying, classifying, and controlling flows in a network. In one implementation, a separate set of behavioral statistics is maintained for each flow. These behavioral statistics are updated as packets belonging to a flow are processed. Whenever a packet belonging to a flow is processed, a set of policies that the flow's behavioral statistics satisfy is determined. For each policy that the flow's behavioral statistics satisfy, actions that are associated with that policy are applied relative to the packet. The actions may be designed to cause a router to handle, in a user-specified manner, packets that are likely to represent a particular kind of traffic. Thus, different flows, such as VOIP, gaming, streaming, and P2P flows, which are associated with different behavioral statistics, may be handled in ways applicable for the specific application traffic type.

Abstract: Various embodiments of the present invention relating to a subscriber fairness solution are disclosed. The subscriber fairness solution contemplates a variety of improved techniques for using a flow-based statistical collection mechanism to monitor subscriber usage across various attributes (e.g., subscriber byte count, flow count, etc.) and maintain subscriber usage information for different time frames. In embodiments, the subscriber fairness solution includes a detection phase and a mitigation phase. In the detection phase, “outliers,” or subscribers who are using more than their fair share of network resources, are identified. In the mitigation phase, appropriate action is taken to resolve the constraints on the network resources, caused by these outliers. The subscriber fairness solution may be embodied in hardware, software, or a composite approach of both hardware and software.

Abstract: A mechanism is disclosed for identifying, classifying, and controlling flows in a network. In one implementation, a separate set of behavioral statistics is maintained for each flow. These behavioral statistics are updated as packets belonging to a flow are processed. Whenever a packet belonging to a flow is processed, a set of policies that the flow's behavioral statistics satisfy is determined. For each policy that the flow's behavioral statistics satisfy, actions that are associated with that policy are applied relative to the packet. The actions may be designed to cause a router to handle, in a user-specified manner, packets that are likely to represent a particular kind of traffic. Thus, different flows, such as VoIP, gaming, streaming, and P2P flows, which are associated with different behavioral statistics, may be handled in ways applicable for the specific application traffic type.

Abstract: A mechanism is disclosed for identifying, classifying, and controlling flows in a network. In one implementation, a separate set of behavioral statistics is maintained for each flow. These behavioral statistics are updated as packets belonging to a flow are processed. Whenever a packet belonging to a flow is processed, a set of policies that the flow's behavioral statistics satisfy is determined. For each policy that the flow's behavioral statistics satisfy, actions that are associated with that policy are applied relative to the packet. The actions may be designed to cause a router to handle, in a user-specified manner, packets that are likely to represent a particular kind of traffic. Thus, different flows, such as VOIP, gaming, streaming, and P2P flows, which are associated with different behavioral statistics, may be handled in ways applicable for the specific application traffic type.