LIGHTWEIGHT STORING MODE FOR CONSTRAINED COMPUTER NETWORKS

• US 20120307652A1
• Filed: 06/01/2011
• Published: 12/06/2012
• Est. Priority Date: 06/01/2011
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Vasseur, Jean-Philippe, Hui, Jonathan W.
• Granted Patent: US 8,593,986 B2
• Time in Patent Office: Days
• US Class Current: 370/252
• CPC Class Codes: H04L 45/34 Source routing
• CPC Class Codes: H04L 45/74 Address processing for routing

Abstract

In one embodiment, a management device, such as a root node, monitors Internet Protocol (IP) overhead (e.g., IP header sizes during source-routing or route table sizes) within a directed acyclic graph (DAG) in a computer network. If it is determined that the IP overhead is above a configured threshold, then in response, a trigger is initiated to have devices within the DAG label-switch downward traffic directed away from the root node within the DAG. In another embodiment, a device communicating within a DAG stores IP routes corresponding to upward traffic from the device directed toward a root of the DAG, and IP-routes upward traffic based on the IP routes. Conversely, the device also stores labels corresponding to downward traffic from the device directed away from the root of the DAG, and label-switches downward traffic based on the labels, accordingly.

Claims

1. A method, comprising:

communicating as a device within a directed acyclic graph (DAG) in a computer network;

storing Internet Protocol (IP) routes at the device corresponding to upward traffic from the device directed toward a root of the DAG;

IP-routing upward traffic based on the IP routes;

storing labels at the device corresponding to downward traffic from the device directed away from the root of the DAG; and

label-switching downward traffic based on the labels.

2. The method as in claim 1, further comprising:

source-routing downward traffic at the device based on source-routed packet headers; and

receiving a trigger to label-switch downward traffic instead of source-routing the downward traffic, wherein the storing labels and label-switching are in response to the received label.

3. The method as in claim 1, further comprising:

IP-routing downward traffic at the device based on stored IP routes; and

receiving a trigger to label-switch downward traffic instead of IP-routing the downward traffic, wherein the storing labels and label-switching are in response to the received label.

4. The method as in claim 3, further comprising:

determining that a number routing table entries stored at the device is above a configured threshold; and

in response, internally generating the received trigger.

5. The method as in claim 1, further comprising:

receiving a trigger at the device to initiate label distribution for downward traffic to the device; and

in response to the trigger, initiating label distribution for downward traffic to the device.

6. The method as in claim 1, further comprising:

determining that a number of labels stored at the device is above a configured threshold; and

in response, triggering establishment of a hierarchical label-switched path (H-LSP).

7. The method as in claim 6, wherein a tail-end node of the H-LSP is the device.

8. The method as in claim 6, wherein a tail-end node of the H-LSP is a second device further from the root of the DAG than the triggering device, the method further comprising:

triggering the second device into becoming the H-LSP tail-end node.

9. The method as in claim 1, further comprising:

receiving a label distributed with an indication that the label is to be removed;

removing the corresponding label from being stored at the device;

receiving a hierarchical label associated with a hierarchical label-switched path (H-LSP) in place of the removed label; and

storing the hierarchical label.

10. An apparatus, comprising:

one or more network interfaces to communicate within a directed acyclic graph (DAG) in a computer network;

a processor coupled to the network interfaces and adapted to execute one or more processes; and

a memory configured to store a process executable by the processor, the process when executed operable to;

store Internet Protocol (IP) routes corresponding to upward traffic from the apparatus directed toward a root of the DAG;

IP-route upward traffic based on the IP routes;

store labels corresponding to downward traffic from the apparatus directed away from the root of the DAG; and

label-switch downward traffic based on the labels.

11. The apparatus as in claim 10, wherein the process when executed is further operable to:

source-route downward traffic based on source-routed packet headers;

receive a trigger to label-switch downward traffic instead of source-routing the downward traffic, wherein the storing labels and label-switching are in response to the received label.

12. The apparatus as in claim 10, wherein the process when executed is further operable to:

IP-route downward traffic based on stored IP routes; and

receive a trigger to label-switch downward traffic instead of IP-routing the downward traffic, wherein the storing labels and label-switching are in response to the received label.

13. The apparatus as in claim 10, wherein the process when executed is further operable to:

receive a trigger to initiate label distribution for downward traffic to the apparatus; and

in response to the trigger, initiate label distribution for downward traffic to the apparatus.

14. The apparatus as in claim 10, wherein the process when executed is further operable to:

determine that a number of labels stored is above a configured threshold; and

in response, trigger establishment of a hierarchical label-switched path (H-LSP).

15. A method, comprising:

monitoring Internet Protocol (IP) overhead within a directed acyclic graph (DAG) in a computer network;

determining whether the IP overhead is above a configured threshold; and

in response to the IP overhead being above the configured threshold, initiating a trigger to label-switch downward traffic directed away from a root node within the DAG.

16. The method as in claim 15, wherein determining whether the IP overhead is above the configured threshold is based on one of either an average size or a maximum size of IP header sizes of source-routed packets being above the configured threshold.

17. The method as in claim 15, wherein determining whether the IP overhead is above the configured threshold is based on whether a size of IP routing tables for IP-routing of downward traffic in the DAG is above the configured threshold.

18. The method as in claim 15, further comprising:

selecting one or more devices within the DAG to act as tail-end nodes of label-switched paths, wherein the initiated trigger is specific to the one or more devices.

19. The method as in claim 15, wherein the monitoring, determining, and initiating are performed by the root node.

20. The method as in claim 19, further comprising:

receiving a hierarchical label-switched path (H-LSP) label at the root node;

operating as a head-end of the H-LSP to push a sub-label and the H-LSP label onto traffic destined through the H-LSP.

21. The method as in claim 15, further comprising:

receiving a second trigger requesting a hierarchical label-switched path (H-LSP);

selecting, in response to the second trigger, a set of one or more tail-end nodes for one or more corresponding hierarchical label-switched paths from devices within the DAG; and

signaling to the selected tail-end nodes to initiate H-LSP label distribution for downward traffic to the respective selected tail-end node.

22. An apparatus, comprising:

one or more network interfaces to communicate with a directed acyclic graph (DAG) in a computer network;

a processor coupled to the network interfaces and adapted to execute one or more processes; and

a memory configured to store a process executable by the processor, the process when executed operable to;

monitor Internet Protocol (IP) overhead within the DAG;

determine whether the IP overhead is above a configured threshold; and

in response to the IP overhead being above the configured threshold, initiate a trigger to label-switch downward traffic directed away from a root node within the DAG.

23. The apparatus as in claim 22, wherein the process when executed to determine whether the IP overhead is above the configured threshold is operable to determine whether the IP overhead is above the configured threshold based on one of either an average size or a maximum size of IP header sizes of source-routed packets being above the configured threshold.

24. The apparatus as in claim 22, wherein the process when executed to determine whether the IP overhead is above the configured threshold is operable to determine whether the IP overhead is above the configured threshold based on whether a size of IP routing tables for IP-routing of downward traffic in the DAG is above the configured threshold.