Exemplified systems and methods facilitate multicasting latency optimization operations for router, switches, and other network devices, for routed Layer-3 multicast packets to provide even distribution latency and/or selective prioritized distribution of latency among multicast destinations. A list of network destinations for serially-replicated packets is traversed in different sequences from one packet to the next, to provide delay fairness among the listed destinations. The list of network destinations are mapped to physical network ports, virtual ports, or logical ports of the router, switches, or other network devices and, thus, the different sequences are also traversed from these physical network ports, virtual ports, or logical ports. The exemplified systems and methods facilitates the management of traffic that is particularly beneficial in in a data center.

Exemplified systems and methods facilitate multicasting latency optimization operations for router, switches, and other network devices, for routed Layer-3 multicast packets to provide even distribution latency and/or selective prioritized distribution of latency among multicast destinations. A list of network destinations for serially-replicated packets is traversed in different sequences from one packet to the next, to provide delay fairness among the listed destinations. The list of network destinations are mapped to physical network ports, virtual ports, or logical ports of the router, switches, or other network devices and, thus, the different sequences are also traversed from these physical network ports, virtual ports, or logical ports. The exemplified systems and methods facilitates the management of traffic that is particularly beneficial in in a data center.

Examples described herein relate to apparatuses and methods for managing communications within a supercluster or across superclusters, including a first supercluster having a plurality of first machines and a publish-subscribe (Pub-Sub) channel to which each of the plurality of first machines is subscribed. A second supercluster has a plurality of second machines and a bridge between the first supercluster and the second supercluster. A first machine is configured to receive, via the bridge, an availability status and resource allocation information of each second machine and publish, on the Pub-Sub channel of the first supercluster, the availability status and the resource allocation information.

Examples described herein relate to apparatuses and methods for managing communications within a supercluster or across superclusters, including a first supercluster having a plurality of first machines and a publish-subscribe (Pub-Sub) channel to which each of the plurality of first machines is subscribed. A second supercluster has a plurality of second machines and a bridge between the first supercluster and the second supercluster. A first machine is configured to receive, via the bridge, an availability status and resource allocation information of each second machine and publish, on the Pub-Sub channel of the first supercluster, the availability status and the resource allocation information.

Disclosed herein are embodiments of systems, methods, and products comprising a computing device, which provides Efficient Data-In-Transit Protection Techniques for Handheld Devices (EDITH) to protect data-in-transit. An end user device (EUD) may generate a multicast data packet. The EDITH module of the EUD encapsulates the data packet in a GRE packet and directs the GRE packet to a unicast destination address of an EDITH Multicast Router included in an infrastructure. The EDITH module on the EUD double compresses and double encrypts the GRE packet. The EDITH module on the infrastructure decrypts and decompresses the double compressed and double encrypted GRE packet to recreate the GRE packet. The EDITH module on the infrastructure decapsulates the GRE packet to derive the original multicast data packet, and distributes the original multicast data packet to the multiple group member based on the multicast destination address included in the original multicast data packet.

Disclosed herein are embodiments of systems, methods, and products comprising a computing device, which provides Efficient Data-In-Transit Protection Techniques for Handheld Devices (EDITH) to protect data-in-transit. An end user device (EUD) may generate a multicast data packet. The EDITH module of the EUD encapsulates the data packet in a GRE packet and directs the GRE packet to a unicast destination address of an EDITH Multicast Router included in an infrastructure. The EDITH module on the EUD double compresses and double encrypts the GRE packet. The EDITH module on the infrastructure decrypts and decompresses the double compressed and double encrypted GRE packet to recreate the GRE packet. The EDITH module on the infrastructure decapsulates the GRE packet to derive the original multicast data packet, and distributes the original multicast data packet to the multiple group member based on the multicast destination address included in the original multicast data packet.

Various example embodiments for supporting stateless multicast communications in a communication system are presented. Various example embodiments for supporting stateless multicast communications may be configured to support stateless multicast communications in a label switching network (e.g., a Multiprotocol Label Switching (MPLS) network, an MPLS—Traffic Engineered (TE) network, or the like) based on use of local label spaces of nodes of the label switching network for encoding of an explicit path tree for the multicast communications within the multicast communications. Various example embodiments for supporting stateless multicast communications in a label switching network based on use of local label spaces of nodes of the label switching network may be configured to support use of local label spaces of nodes of the label switching network by using network-wide unique node identifiers to uniquely identify nodes with which the node and adjacency labels of the explicit path tree are associated.

Various example embodiments for supporting stateless multicast communications in a communication system are presented. Various example embodiments for supporting stateless multicast communications may be configured to support stateless multicast communications in a label switching network (e.g., a Multiprotocol Label Switching (MPLS) network, an MPLS—Traffic Engineered (TE) network, or the like) based on use of local label spaces of nodes of the label switching network for encoding of an explicit path tree for the multicast communications within the multicast communications. Various example embodiments for supporting stateless multicast communications in a label switching network based on use of local label spaces of nodes of the label switching network may be configured to support use of local label spaces of nodes of the label switching network by using network-wide unique node identifiers to uniquely identify nodes with which the node and adjacency labels of the explicit path tree are associated.

A disclosed method is performed at a first boundary node bordering a BIER domain. The method includes receiving a message associated with a source and group for multicast from outside the BIER domain. The method further includes generating an encapsulated message based on the message, a metric, and a first proxy address of the first boundary node. The method also includes forwarding the encapsulated message through the BIER domain to at least one second boundary node bordering the BIER domain and connectable to the first boundary node. The first boundary node additionally triggers the at least one second boundary node to decapsulate the encapsulated message for forwarding out of the first domain and store a record including the source, the group, the metric representing the cost of the first boundary node to the source, and the first proxy address on the at least one second boundary node.

A disclosed method is performed at a first boundary node bordering a BIER domain. The method includes receiving a message associated with a source and group for multicast from outside the BIER domain. The method further includes generating an encapsulated message based on the message, a metric, and a first proxy address of the first boundary node. The method also includes forwarding the encapsulated message through the BIER domain to at least one second boundary node bordering the BIER domain and connectable to the first boundary node. The first boundary node additionally triggers the at least one second boundary node to decapsulate the encapsulated message for forwarding out of the first domain and store a record including the source, the group, the metric representing the cost of the first boundary node to the source, and the first proxy address on the at least one second boundary node.