Abstract: A first network device may generate a first protocol data unit (PDU) identifying a request to transition from a power on state to a power sleep state, and may provide the first PDU to a second network device. The first network device may receive a second PDU identifying a link of the second network device to transition from the power on state to the power sleep state, and may generate a third PDU identifying a link of the first network device to transition from the power on state to the power sleep state. The first network device may provide the third PDU to the second network device, and may transition the link of the first network device and the link of the second network device from the power on state to the power sleep state based on the second PDU and the third PDU.

Abstract: A first network device may provide a link discovery message to a second network device, and may identify a link based on the link discovery message. The first network device may provide, to the second network device, a first control channel message that identifies the link at the first network device, a current state of the link as a power on state, and a desired state of the link as a power sleep state, and may receive, from the second network device, a second control channel message that identifies the link at the second network device, the current state of the link as the power on state, and the desired state of the link as the power sleep state. The first network device may place the link in the power sleep state based on the first control channel message and the second control channel message.

Abstract: An ingress network device may calculate entry paths from across an entry network of a network, wherein the network includes a transit network with a plurality of transit network devices and a destination network with a plurality of destination network devices. The ingress network device may store the entry paths locally in the ingress network device, and may receive traffic destined for a destination. The ingress network device may retrieve, from a distributed data structure, transit paths associated with the transit network and destination paths associated with the destination network, and may determine a path for the traffic based on the entry paths, the transit paths, and the destination paths. The ingress network device may provide the traffic to the destination via the path.

Abstract: A first network device may create a port group for a plurality of links directly connected to a second network device, and may select the first network device as a controller network device and the second network device as a worker network device. The first network device may rank the plurality of links of the port group to generate a list of ranked links, and may select, from the list of ranked links, a highest ranked link as a control channel. The first network device may power off one or more of the plurality of links, except the control channel, based on one of a configuration, a policy, or a traffic prediction, and may identify a termination of a time period associated with powering off the one or more of the plurality of links. The first network device may power on the one or more of the plurality of links based on the termination of the time period.

Abstract: A network device may receive an MPLS packet destined for a destination via a label-switched path (LSP), and may determine whether to apply a first special purpose label (SPL) option or a second SPL option for a label stack of the MPLS packet. The network device may apply, when the first SPL option is determined to be applied, one of a first type of the first SPL option for the label stack via a policy data indicator (PDI) and policy data (PD), or a second type of the first SPL option for the label stack via the PDI and the PD. The network device may forward the MPLS packet to a hop of the LSP based on the first type of the first SPL option or the second type of the first SPL option applied to the MPLS packet.

Abstract: A first network device may create a port group for a plurality of links directly connected to a second network device, and may select the first network device as a controller network device and the second network device as a worker network device. The first network device may rank the plurality of links of the port group to generate a list of ranked links, and may select, from the list of ranked links, a highest ranked link as a control channel. The first network device may power off one or more of the plurality of links, except the control channel, based on one of a configuration, a policy, or a traffic prediction, and may identify a termination of a time period associated with powering off the one or more of the plurality of links. The first network device may power on the one or more of the plurality of links based on the termination of the time period.

Abstract: In some implementations, a network device may receive one or more indications of one or more power usage ratings associated with a plurality of network devices. The network device may perform path placement on one or more network devices of the plurality of network devices using the one or more power usage ratings.

Abstract: A disclosed computing device may include (1) a storage device configured to store a database that identifies states of nodes included in a network and (2) circuitry configured to (A) receive one or more packet fragments that account for at least one change made to a state of one of the nodes in a transaction, (B) identify, among the packet fragments, a transaction identifier corresponding to the transaction and an indication of a total number of packet fragments representing the transaction, and (C) update the database to account for the change upon ensuring receipt of all the packet fragments representing the transaction based at least in part on the transaction identifier and the indication. Various other devices, systems, and methods are also disclosed.

Abstract: The techniques describe network slicing in computer networks. For example, a node receives a slice policy definition. The slice policy definition comprising a slice selector to identify packets belonging to one or more network slices, referred to as a “slice aggregate,” and one or more network resource requirements for the slice aggregate to meet one or more Service Level Objectives (SLOs). The node configures, based on the slice policy definition, a path for the slice aggregate that complies with the one or more network resource requirements. In response to receiving a packet, the node determines whether the packet is associated with the slice aggregate and, in response to determining that the packet is associated with the slice aggregate, forwards the packet along the path for the slice aggregate.

Abstract: A first network device may create a port group for a plurality of links directly connected to a second network device, and may select the first network device as a controller network device and the second network device as a worker network device. The first network device may rank the plurality of links of the port group to generate a list of ranked links, and may select, from the list of ranked links, a highest ranked link as a control channel. The first network device may power off one or more of the plurality of links, except the control channel, based on one of a configuration, a policy, or a traffic prediction, and may identify a termination of a time period associated with powering off the one or more of the plurality of links. The first network device may power on the one or more of the plurality of links based on the termination of the time period.

Abstract: A device may utilize a data modeling language to generate a request to identify components of a network device and operational dependencies of the components, and may provide the request to the network device. The device may receive, based on the request, data identifying the components and the operational dependencies of the components, and may receive power consumptions by the components and power off capabilities of the components. The device may generate a model of power consumptions by the components based on the power consumptions by the components and the power off capabilities of the components, and may identify, from the components, a component capable of powering off based on the model. The device may instruct the network device to place the component in a power save state.

Abstract: A first network device may identify one or more components to transition to a sleep state, and may power down the one or more components to cause a link with a second network device to be in a sleep state. The first network device may provide, to the second network device, a link sleep state message identifying the link, and may provide updated link sleep state messages to the second network device while the sleep state of the link is maintained.

Abstract: A first network device may provide a link discovery message to a second network device, and may identify a link based on the link discovery message. The first network device may provide, to the second network device, a first control channel message that identifies the link at the first network device, a current state of the link as a power on state, and a desired state of the link as a power sleep state, and may receive, from the second network device, a second control channel message that identifies the link at the second network device, the current state of the link as the power on state, and the desired state of the link as the power sleep state. The first network device may place the link in the power sleep state based on the first control channel message and the second control channel message.

Abstract: A first network device may determine a power group associating a plurality of ports of the first network device with a processing component of the first network device, and may advertise the power group to a second network device. The first network device may utilize the power group with a path placement strategy to compute a path to the second network device, and may determine a traffic load associated with the first network device. The first network device may disable the plurality of ports and the processing component based on the path and the traffic load.

Abstract: A first network device may generate a first protocol data unit (PDU) identifying a request to transition from a power on state to a power sleep state, and may provide the first PDU to a second network device. The first network device may receive a second PDU identifying a link of the second network device to transition from the power on state to the power sleep state, and may generate a third PDU identifying a link of the first network device to transition from the power on state to the power sleep state. The first network device may provide the third PDU to the second network device, and may transition the link of the first network device and the link of the second network device from the power on state to the power sleep state based on the second PDU and the third PDU.

Abstract: A network device may receive a border gateway protocol (BGP) flow specification route associated with creation of an overlay network slice in a network, and may create a new routing instance based on the BGP flow specification route. The network device may associate interfaces defined by the BGP flow specification route with virtual private network (VPN) members, and may determine VPN parameters based on the BGP flow specification route. The network device may advertise the VPN parameters within the network to cause the network to generate the overlay network slice.

Abstract: A disclosed computing device may include (1) a storage device configured to store a database that identifies states of nodes included in a network and (2) circuitry configured to (A) receive one or more packet fragments that account for at least one change made to a state of one of the nodes in a transaction, (B) identify, among the packet fragments, a transaction identifier corresponding to the transaction and an indication of a total number of packet fragments representing the transaction, and (C) update the database to account for the change upon ensuring receipt of all the packet fragments representing the transaction based at least in part on the transaction identifier and the indication. Various other devices, systems, and methods are also disclosed.

Abstract: A network device may receive a border gateway protocol (BGP) flow specification route associated with creation of an overlay network slice in a network, and may create a new routing instance based on the BGP flow specification route. The network device may associate interfaces defined by the BGP flow specification route with virtual private network (VPN) members, and may determine VPN parameters based on the BGP flow specification route. The network device may advertise the VPN parameters within the network to cause the network to generate the overlay network slice.

Abstract: An ingress network device may receive a core domain network segment identifier associated with a core domain network of the multi-domain network. The ingress network device may receive location data of an egress network device associated with a second leaf domain network of the multi-domain network, wherein the location data may include data identifying the core domain network segment identifier, a second leaf domain network segment identifier associated with the second leaf domain network, and an egress network device segment identifier associated with the egress network device. The ingress network device may store the core domain network segment identifier and the location data, and may utilize the core domain segment identifier and the location data to route traffic to the egress network device.

Abstract: A network device may receive a border gateway protocol (BGP) flow specification route associated with creation of an overlay network slice in a network, and may create a new routing instance based on the BGP flow specification route. The network device may associate interfaces defined by the BGP flow specification route with virtual private network (VPN) members, and may determine VPN parameters based on the BGP flow specification route. The network device may advertise the VPN parameters within the network to cause the network to generate the overlay network slice.