Abstract:
Techniques are provided for, at an administrative device in a network domain, monitoring a network traffic flow parameter to determine whether a presently applied domain wide policy configured to control a network traffic flow should be removed. In response to determining that the domain wide policy should be removed, a command is generated which causes removal of the domain wide policy at each one of the plurality of network devices, and the command is sent to each one of the plurality of network devices to cause the domain wide policy to be removed at substantially the same time at each network device. Alternatively, the domain wide policy can be automatically removed by the expiry of a timer or in accordance with a timestamp so that the policy is revoked across the network domain without a need for an explicit network wide control message instructing removal of the policy.
Abstract:
System, computer program product, and method to configure an external network based on internal network conditions, by monitoring a load attribute of one or more network flows traversing an ingress port of at least one network element in a software-defined networking (SDN) enabled network, upon determining that the load attribute of a first network element in the SDN enabled network exceeds a predefined threshold, provisioning, by the application, an additional service on the external network, by the application, an additional service on the external network, and extending, by the application, the SDN enabled network to include the additional service on the external network.
Abstract:
Described herein are devices, systems, methods, and processes for optimizing network traffic distribution across multiple paths in a manner that is energy-efficient and environmental sustainability-aware. This may be achieved by leveraging time-series analytics and capacity planning based on seasonalities. Data associated with the Layer 3 topology of the network can be collected. Bandwidth can be pre-reserved on an energy-aware traffic engineering tunnel. The time-series data can be used to build a capacity plan based on the seasonalities. Nodes may be clustered based on usage patterns and network utilization seasonality. The data can be used to make decisions about when and where to combine or shut down paths for energy efficiency, while maintaining optimal network performance. A hysteresis mechanism may be incorporated to avoid oscillation when changing active links. Power savings can be achieved by fully turning off or depowering certain network components when they are not needed.
Abstract:
Described herein are devices, systems, methods, and processes for managing power congestion in multi-path routing systems. Indications may be similar to the ECN, and may be used in network headers, including headers for IPV6, SRv6, NSH, or other tunneling protocols. The indications, namely EOPN, PTE, and ECMP-exclude, can provide a mechanism for managing network power consumption and controlling ECMP routing based on flow priority and characteristics. The power budget can be dynamically adjusted based on the current power source mix, which may help to achieve sustainability goals. Hashing optimizations and signaling can be utilized to manage network power congestion and bandwidth-normalized power efficiency availability. A process may be implemented to ensure there is sufficient capacity to serve the expected traffic for different next-hop paths. Additionally, the ECN can be used to quickly react to congestion, bring capacity back online, and maintain optimal network performance, even in the absence of congestion.
Abstract:
Techniques for varying locations of virtual networks associated with endpoints using Network Address Translation (NAT), Mobile Internet Protocol (MIP), and/or other techniques in conjunction with Domain Name System (DNS). Rather than having DNS provide a client device with an IP address of an endpoint device, such as a server, the DNS instead returns a virtual IP (VIP) address that is mapped to the client device and the endpoint device. The VIP address may be selected based on a number of factors (e.g., power usage, privacy requirements, virtual distances, etc.). In this way, IP addresses of servers are obfuscated by a virtual network of VIP addresses that can be periodically rotated and/or load balanced. The client device may then communicate data packets to the server using the VIP address as the destination address, and a virtual network service that works in conjunction with DNS can convert the VIP address to the actual IP address of the server using NAT and forward the data packet onto the server.
Abstract:
Systems and methods for generating verifiable power line sustainability data are disclosed herein. In many embodiments, a device includes a processor, a memory commutatively coupled to the processor, a communication port coupled with a second device, and a smart meter logic configured to execute within a trusted execution environment. Power source data may be received through the communication port. The power source data may be processed such as attesting to the validity of the data through a trusted execution environment. The received power source data may be communicated to energy-consuming devices and formatted to allow the energy-consuming devices to adjust their energy consumption in response to a metric, such as a sustainability metric, within the power source data. Sustainability metrics can include a power source carbon footprint, greenhouse gas mix values, and/or other indicators. Power use decisions for energy-consuming devices can be made in response to these verified sustainability metrics.
Abstract:
A method is provided in one example and includes allocating a first queue, allocating at least two default queues, where the at least two default queues depend from the first queue, allocating a plurality of local queues that each depend from one of the at least two defaults queues, receiving data in a data stream, determining a quality of service (QoS) associated with the data, and assigning the data to one of the plurality of local queues based on the determined QoS. In an example, the QoS is a differentiated services code point.
Abstract:
An example method for facilitating conflict avoidant traffic routing in a network environment is provided and includes detecting, at a network element, an intent conflict at a peer network element in a network, and changing a forwarding decision at the network element to steer traffic around the conflicted peer network element. The intent conflict refers to an incompatibility between an asserted intent associated with the traffic and an implemented intent associated with the traffic. In specific embodiments, the detecting includes mounting rules from the peer network element into the network element, and analyzing the mounted rules to determine intent conflict. In some embodiments, a central controller in the network deploys one or more intentlets on a plurality of network elements in the network according to corresponding intent deployment parameters.
Abstract:
An example method for facilitating conflict avoidant traffic routing in a network environment is provided and includes detecting, at a network element, an intent conflict at a peer network element in a network, and changing a forwarding decision at the network element to steer traffic around the conflicted peer network element. The intent conflict refers to an incompatibility between an asserted intent associated with the traffic and an implemented intent associated with the traffic. In specific embodiments, the detecting includes mounting rules from the peer network element into the network element, and analyzing the mounted rules to determine intent conflict. In some embodiments, a central controller in the network deploys one or more intentlets on a plurality of network elements in the network according to corresponding intent deployment parameters.
Abstract:
Techniques are provided for, at an administrative device in a network domain, monitoring a network traffic flow parameter to determine whether a presently applied domain wide policy configured to control a network traffic flow should be removed. In response to determining that the domain wide policy should be removed, a command is generated which causes removal of the domain wide policy at each one of the plurality of network devices, and the command is sent to each one of the plurality of network devices to cause the domain wide policy to be removed at substantially the same time at each network device. Alternatively, the domain wide policy can be automatically removed by the expiry of a timer or in accordance with a timestamp so that the policy is revoked across the network domain without a need for an explicit network wide control message instructing removal of the policy.