Abstract: A method comprises, at a first router configured to perform Bit Index Explicit Replication (BIER) for forwarding of multicast packets in a network, storing configuration information that indicates that the first router belongs to multiple subdomains of a BIER domain, and is able to forward the multicast packets for a virtual private network on the multiple subdomains. The method further comprises, during an auto-discovery procedure, generating an auto-discovery message to include an auto-discovery route and route attributes that indicate the multiple subdomains, and sending the auto-discovery message to a second router of the virtual private network the network.

Abstract: In an example method for redundant multicast trees with fast recovery, a protocol independent multicast (PIM) backup designated router (BDR) can receive a request from a host to join a multicast group associated with a source; send to a next hop a PIM join message identifying an address of the PIM BDR and identifying the PIM join message as a backup PIM join; receive, from a PIM router along a path to/from the source, a unicast message sent to the address which identifies a second address associated with the PIM router; store the second address and a route associated with the unicast message; in response to a designated router migration trigger, set to blocking a backup multicast tree state associated with the source and multicast group; and send, to the PIM router, a unicast message including instructions to set to blocking a backup multicast tree state at the PIM router.

Abstract: In one illustrative example, a multicast traceroute facility for a plurality of interconnected router nodes which are configured to communicate IP multicast traffic amongst hosts is described. The multicast traceroute facility may be for use in processing a multicast traceroute batch query packet which indicates a batch of multicast traceroute queries of a batch query, for identifying a plurality of traced paths for a batch of IP multicast traffic flows. Each identified traced path may be associated with one or more links, each of which has a link metric that satisfies a requested link metric (e.g. a link bandwidth). Resources for satisfying the requested link metric may be reserved for a predetermined or specified time period. The batch of IP multicast traffic flows may be established via at least some of the interconnected router nodes according to the plurality of traced paths identified from the query packet processing.

Abstract: A method is performed by a network controller. The method includes receiving information that defines a topology of a network having Ethernet Segments configured with virtual local area networks (VLANs) and including provider edges that are multi-homed to customer edges. The method further comprises, based on the topology, determining for the VLANs particular provider edges among the provider edges that are to operate as designated forwarders of traffic for the VLANs, such that the VLANs are load balanced across the particular provider edges. The method also includes programming the particular provider edges as the designated forwarders of traffic for the VLANs.

Abstract: In one embodiment, resource availability reallocation is used in establishing one or more new designated multicast flow paths with guaranteed availability of resources currently allocated and/or used by one or more designated existing multicast flow path to allocate/use for the new designated flow path(s). These resources typically include allocated guaranteed bandwidth of a network path between two adjacent or non-adjacent nodes of the network, and possibly forwarding/processing/memory resources of a network node. One embodiment communicates multicast control messages between nodes identifying to establish a new multicast flow path with resource availability reallocation from a designated multicast flow path.

Abstract: In one embodiment, a first computer networking device executes an election algorithm to determine whether at least the first computer networking device or a second computer networking device is responsible for forwarding, to at least one receiving device, communications addressed to a specified group of computing devices. The first computer networking device may further store first data indicating that the first computer networking device is responsible for forwarding the communications. However, in response to the first computer networking device determining that it is no longer receiving the communications, it may store second data indicating that the first computer networking device is no longer responsible for forwarding the communications and may send, to the second computer networking device, third data indicating that the first computer networking device is not receiving the communications.

Abstract: In one embodiment, a device deploys a first machine learning model to an inference location in a network. The first machine learning model is used at the inference location to make inferences about the network. The device receives, from the inference location, an indication that the first machine learning model is exhibiting poor performance. The device identifies a corrective measure for the poor performance that minimizes resource consumption by a model training pipeline of the device. The device deploys, based on the corrective measure, a second machine learning model to the inference location. The second machine learning model is used in lieu of the first machine learning model to make the inferences about the network.

Abstract: A networking environment includes a first node and a second node configured as Ethernet Virtual Private Networking (EVPN) peers on an EVPN subnet that is coupled to a Layer 3 VPN over a core network. The first node receives a first multicast join request from a third node in the core network, the first multicast join request including a source address and multicast group address of a source of a multicast stream. The first node determines that the source address and the multicast group address for the source are behind the EVPN subnet at the second node. The first node sends to the second node, a control plane join request message that includes a receiver identifier that identifies the third node as a receiver of the multicast stream, the receiver identifier enabling the second node to forward the multicast stream directly into the core network to the third node.

Abstract: A networking environment includes a first node and a second node configured as Ethernet Virtual Private Networking (EVPN) peers on an EVPN subnet that is coupled to a Layer 3 VPN over a core network. The first node receives a first multicast join request from a third node in the core network, the first multicast join request including a source address and multicast group address of a source of a multicast stream. The first node determines that the source address and the multicast group address for the source are behind the EVPN subnet at the second node. The first node sends to the second node, a control plane join request message that includes a receiver identifier that identifies the third node as a receiver of the multicast stream, the receiver identifier enabling the second node to forward the multicast stream directly into the core network to the third node.

Abstract: In one embodiment, method includes receiving, by a first network apparatus, a first multicast message from a second network apparatus. The first multicast message includes attestation-capability information associated with the second network apparatus and an attestation token. The attestation token is for proving that the second network apparatus is in a known safe state. The method also includes determining, by the first network apparatus, that the attestation-capability information satisfies a pre-determined attestation capability requirement and determining, by the first network apparatus, that the attestation token is valid for the second network apparatus at a current time. The method further includes establishing, by the first network apparatus, an adjacency to the second network apparatus.

Abstract: This disclosure describes a method usable in a network that has a combination of mLDP-capable and BIER-capable devices. The disclosed method includes advertising, by an mLDP-capable multicast source, an indication of a BIER edge router that it has determined is usable as a path between the BIER devices and the mLDP-capable multicast source. A provider edge router can include in a multicast join message both an indication of the mLDP-capable multicast source as well as the indication of the BIER router advertised as being usable as the path to the mLDP-capable multicast source. The BIER devices can communicate with each other to pass a multicast join message to the BIER edge router that is indicated as being usable as the path to the mLDP-capable multicast source.

Abstract: A method comprises, at a first router configured to perform Bit Index Explicit Replication (BIER) for forwarding of multicast packets in a network, storing configuration information that indicates that the first router belongs to multiple subdomains of a BIER domain, and is able to forward the multicast packets for a virtual private network on the multiple subdomains. The method further comprises, during an auto-discovery procedure, generating an auto-discovery message to include an auto-discovery route and route attributes that indicate the multiple subdomains, and sending the auto-discovery message to a second router of the virtual private network the network.

Abstract: A router node may be configured for communication of multicast traffic in a network fabric which may include a plurality of spine nodes interconnected to a plurality of leaf nodes. The router node may be configured as one of the leaf nodes and serve as a first hop router for multicast traffic. At the router node, a message for flooding the network fabric may be sent based on an indication of communication of multicast traffic for a multicast group from a source device. The message may include at least one spine node identifier of at least one preferred spine node joined to the multicast group at the router node. The message may be for indicating, to at least one of the leaf nodes, to prioritize joining to the multicast group at the at least one preferred spine node according to at least one spine node identifier.

Abstract: A router node may be configured for communication of multicast traffic in a network fabric which may include a plurality of spine nodes interconnected to a plurality of leaf nodes. The router node may be configured as one of the leaf nodes and serve as a first hop router for multicast traffic. At the router node, a message for flooding the network fabric may be sent based on an indication of communication of multicast traffic for a multicast group from a source device. The message may include at least one spine node identifier of at least one preferred spine node joined to the multicast group at the router node. The message may be for indicating, to at least one of the leaf nodes, to prioritize joining to the multicast group at the at least one preferred spine node according to at least one spine node identifier.

Abstract: In one embodiment, a first computer networking device executes an election algorithm to determine whether at least the first computer networking device or a second computer networking device is responsible for forwarding, to at least one receiving device, communications addressed to a specified group of computing devices. The first computer networking device may further store first data indicating that the first computer networking device is responsible for forwarding the communications. However, in response to the first computer networking device determining that it is no longer receiving the communications, it may store second data indicating that the first computer networking device is no longer responsible for forwarding the communications and may send, to the second computer networking device, third data indicating that the first computer networking device is not receiving the communications.

Abstract: In one embodiment, a first label-distribution-protocol (LDP) session is established between a first interface of a first computing device and a second computing device, while a second LDP session is established between a second interface and the second computing device. The method may further comprise receiving a request from a third computing device to subscribe to a multicast group, storing an association between a first label, the multicast group, and the first interface, and sending, to the second computing device via the first LDP session, an indication that the first label is associated with the multicast group. Further, the method may include receiving a request from a fourth computing device to subscribe to the multicast group, storing an association between a second label, the multicast group and, the second interface, and sending, via the second LDP session, an indication that the second label is associated with the multicast group.

Abstract: A first network device joins a redundancy group of a multihomed network element that is connected to a computing device. The first network device detects an active link between the first network device and the computing device, and receives from the computing device, a subscription to a multicast flow. The first network device adds the subscription to a first list of active multicast subscriptions stored on the first network device. The first network device sends a unicast notification to a second network device of the multihomed network element. The unicast notification causes the subscription to be added to a second list of active multicast subscriptions stored on the second network device.

Abstract: Seamless multipoint label distribution protocol (mLDP) transport over a bit index explicit replication (BIER) core may be provided. First, it may be determined that a first plurality of network devices comprise BIER edge routers. Then, in response to determining that the first plurality of network devices comprise BIER edge routers, a Targeted Label Distribution Protocol (T-LDP) session may be created between a first one of the first plurality of network devices and a second one of the first plurality of network devices. Next, an address of a peer device connected to the second one of the first plurality of network devices may be advertised by the second one of the first plurality of network devices over the T-LDP session.

Abstract: In one illustrative example, a network node connected in a network fabric may identify that it is established as part of a multicast distribution tree for forwarding multicast traffic from a source node to one or more host receiver devices of a multicast group. In response, the network node may propagate in the network fabric a message for advertising the network node as a candidate local source node at which to join the multicast group. The message for advertising may include data such as a reachability metric. The propagation of the message may be part of a flooding of such messages in the network fabric. The network node serving as the candidate local source node may thereafter “locally” join a host receiver device in the multicast group at the network node so that the device may receive the multicast traffic from the source node via the network node.

Abstract: A router node may be configured for communication of multicast traffic in a network fabric which may include a plurality of spine nodes interconnected to a plurality of leaf nodes. The router node may be configured as one of the leaf nodes and serve as a first hop router for multicast traffic. At the router node, a message for flooding the network fabric may be sent based on an indication of communication of multicast traffic for a multicast group from a source device. The message may include at least one spine node identifier of at least one preferred spine node joined to the multicast group at the router node. The message may be for indicating, to at least one of the leaf nodes, to prioritize joining to the multicast group at the at least one preferred spine node according to at least one spine node identifier.