Abstract:
BIER architecture currently does not support anycast, in that each BIER Forwarding Router (BFR) has its own unique BFR-prefix and BFR-ID. BIER signaling protocols also check if there are duplicate BFR-IDs advertised. Anycast support with BIER is described. The description updates (e.g., relaxes and/or removes some requirements of) RFC 8279, RFC 8401, and RFC 8444.
Abstract:
A router on a multicast tree, may: (a) receive a control plane message (including a label and a tree identifier identifying the multicast tree) from a downstream router on the multicast tree; (b) construct an SRv6 SID in a LOC:FUNCT:ARG form, wherein the LOC part is a locator of the downstream router and the FUNCT part is the label included in the control plane message received; and (c) create an entry in its forwarding table so that the router replicates received traffic of this multicast tree to the downstream node using the SRv6 SID. A router on a multicast tree may construct an SRv6 SID in a LOC:FUNCT:ARG form for the multicast tree, wherein the LOC is a locator of the router and the FUNCT is to be signaled to an upstream router as a label.
Abstract:
In an example, a method comprises executing, by an access network user plane function (ANUP) for a mobile network, an access network protocol to implement a connection with a user equipment (UE); implementing, by the ANUP, based on session data received from a control plane function of a mobile core network for the mobile network, an interface with a data network; and routing or switching, by the ANUP, packets between the connection with the UE and the interface with the data network.
Abstract:
Techniques are described for signaling a resource reservation point-to-multipoint (P2MP) label switched path (LSP) in a ring network. For example, the techniques include sending a single resource reservation request message without the ingress needing to send multiple resource reservation request messages, one for each leaf network device of the P2MP ring LSP. The resource reservation request message includes a leaf identification object from which network devices of a P2MP ring LSP may explicitly or implicitly identify themselves as prospective leaf network devices of the P2MP ring LSP. A network device determined to be a leaf network device may send a resource reservation response message back to the ingress network device of the P2MP ring LSP and send a modified resource reservation request message (if explicit) and/or the same resource reservation request message (if implicit) to a next hop network device along the P2MP ring LSP.
Abstract:
Techniques are described for signaling a resource reservation point-to-multipoint (P2MP) label switched path (LSP) in a ring network. For example, the techniques include sending a single resource reservation request message without the ingress needing to send multiple resource reservation request messages, one for each leaf network device of the P2MP ring LSP. The resource reservation request message includes a leaf identification object from which network devices of a P2MP ring LSP may explicitly or implicitly identify themselves as prospective leaf network devices of the P2MP ring LSP. A network device determined to be a leaf network device may send a resource reservation response message back to the ingress network device of the P2MP ring LSP and send a modified resource reservation request message (if explicit) and/or the same resource reservation request message (if implicit) to a next hop network device along the P2MP ring LSP.
Abstract:
A network device receives multicast packets that include information identifying destinations in the network, identifies next hops associated with the destinations, and populates a cache with the destinations and addresses of the identified next hops. The network device receives a particular multicast packet that includes information identifying particular destinations included in the cache, identifies one or more next hops for the particular destinations from the cache, and forwards the particular multicast packet to the identified one or more next hops to permit the identified one or more next hops to forward the multicast packet toward the particular destinations.
Abstract:
The disclosed computer-implemented method may include (1) receiving, at an upstream router of a multicast distribution tree, a packet that is destined for a receiver within an MPLS network, (2) identifying within the packet (A) a context label that specifies a controller and (B) a tree label that is assigned by the controller, (3) identifying a forwarding table that corresponds to the context label identified within the packet, (4) searching the forwarding table that corresponds to the context label for the tree label that specifies the multicast distribution tree, (5) identifying, based at least in part on the search, a downstream router of the multicast distribution tree that is to receive the packet on the way to the receiver, and then (6) forwarding the packet to the downstream router of the multicast distribution tree on the way to the receiver. Various other methods, systems, and apparatuses are also disclosed.
Abstract:
Techniques are described for utilizing Protocol Independent Multicast Sparse Mode (PIM-SM) to transport BUM (broadcast, unknown unicast, and multicast) traffic in a Virtual Extensible LAN (VXLAN) underlay of a data center, where the BUM traffic is received on active-active, multi-homed Ethernet virtual private network (EVPN) interconnects between multiple physical data centers. For example, the techniques may readily be applied to support usage of PIM-SM where provider edge (PE) routers of the EVPN operate as gateways between the EVPN and the VXLAN spanning the data center interconnect.
Abstract:
Techniques are described for utilizing Protocol Independent Multicast Sparse Mode (PIM-SM) to transport BUM (broadcast, unknown unicast, and multicast) traffic in a Virtual Extensible LAN (VXLAN) underlay of a data center, where the BUM traffic is received on active-active, multi-homed Ethernet virtual private network (EVPN) interconnects between multiple physical data centers. For example, the techniques may readily be applied to support usage of PIM-SM where provider edge (PE) routers of the EVPN operate as gateways between the EVPN and the VXLAN spanning the data center interconnect.