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: 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: First and second egress nodes are each multi-homed to a customer edge (CE) that participates in virtual routing and forwarding (VRF). First forwarding information is configured on the first egress node. The first information includes VRF labels and defines forwarding of traffic based on the VRF labels and a status of a primary path to the CE. The VRF labels include a per-VRF label for the VRF and a per-CE label for the CE. Second forwarding information is configured on the second egress node. The second forwarding information includes the per-VRF label and the per-CE label, and defines traffic forwarding based on the VRF labels. Upon receiving traffic for the CE that carries the per-VRF label, the first egress node determines the status of the primary path, and forwards the traffic to either the CE over the primary path or to the second egress node, depending on the status.

Abstract: First and second egress nodes are each multi-homed to a customer edge (CE) that participates in virtual routing and forwarding (VRF). First forwarding information is configured on the first egress node. The first information includes VRF labels and defines forwarding of traffic based on the VRF labels and a status of a primary path to the CE. The VRF labels include a per-VRF label for the VRF and a per-CE label for the CE. Second forwarding information is configured on the second egress node. The second forwarding information includes the per-VRF label and the per-CE label, and defines traffic forwarding based on the VRF labels. Upon receiving traffic for the CE that carries the per-VRF label, the first egress node determines the status of the primary path, and forwards the traffic to either the CE over the primary path or to the second egress node, depending on the status.

Abstract: In a network environment using a PIM (Protocol Independent Multicast) multicast routing protocol, an Assert mechanism is implemented wherein a provider-edge (PE) device sends an Assert message on the Default MDT (multicast distribution tree) and causes selection of an Assert winner, wherein any ingress PE not selected as the Assert winner stops forwarding the data packets on the Data MDT; and the Assert winner sends periodic PIM control messages on the Default MDT to maintain the Assert state on all ingress PE routers until canceled or timed out. The Assert message is created in response to MDT Mapping from at least one other ingress PE device. The PIM control messages may contain a special bit extension which forces an RPF (reverse path forwarding) neighbor to keep pointing to the Assert winner until a PIM neighborship-down event is detected. This obviates the need for periodic Assert messaging and/or data packet punting.

Abstract: A method, in accordance with particular embodiments, includes receiving an interest solicitation message advertising an availability of data from at least one source of a plurality of sources. The solicitation message comprises a source identifier indentifying the at least one source and a group identifier identifying at least one group. The method also includes sending a null message to a rendezvous node. The null message comprises the source identifier and the group identifier. The method additionally includes receiving, via the rendezvous node, a join message indicating that at least one endpoint has requested to join the at least one group identified by the group identifier. The method further includes sending a start message to the at least one source. The start message indicates that at least one endpoint has requested to join the group. The method also includes, receiving a first portion of the data after sending the start message.