Described herein are methods and devices (e.g., routers) that add in-network services to a multiprotocol label switching (MPLS) network. A method can include a router of the MPLS network receiving a packet and modifying the packet by adding one or more MPLS extension headers, adding a header of the extension header(s), and adding an indication within an MPLS label stack that one or more MPLS extension headers have been added to the packet. The method can also include the router forwarding the packet as modified to another router of the MPLS network. In certain embodiments, an extension header label (EHL) within a label value field of a label stack entry indicates that one or more MPLS extension headers have been added to the packet. In other embodiments, a forward equivalent class (FEC) indicates that one or more MPLS extension headers follow the MPLS label stack.

Described herein are methods and devices (e.g., routers) that add in-network services to a multiprotocol label switching (MPLS) network. A method can include a router of the MPLS network receiving a packet and modifying the packet by adding one or more MPLS extension headers, adding a header of the extension header(s), and adding an indication within an MPLS label stack that one or more MPLS extension headers have been added to the packet. The method can also include the router forwarding the packet as modified to another router of the MPLS network. In certain embodiments, an extension header label (EHL) within a label value field of a label stack entry indicates that one or more MPLS extension headers have been added to the packet. In other embodiments, a forward equivalent class (FEC) indicates that one or more MPLS extension headers follow the MPLS label stack.

A data multicast implementation method, apparatus, and system are provided. In some embodiments, a transmission device receives a standby forwarding path establishment request, where the standby forwarding path establishment request includes a device identifier, has a destination address being an address of a multicast source device, and is used to request to establish a standby forwarding path between a multicast destination device identified by the device identifier and the multicast source device. In those embodiments, when determining, based on the device identifier in the standby forwarding path establishment request, that the transmission device is located on an active forwarding path between the multicast destination device and the multicast source device, the transmission device skips using the transmission device as a device on the standby forwarding path between the multicast destination device and the multicast source device, and skips forwarding the standby forwarding path establishment request.

A data multicast implementation method, apparatus, and system are provided. In some embodiments, a transmission device receives a standby forwarding path establishment request, where the standby forwarding path establishment request includes a device identifier, has a destination address being an address of a multicast source device, and is used to request to establish a standby forwarding path between a multicast destination device identified by the device identifier and the multicast source device. In those embodiments, when determining, based on the device identifier in the standby forwarding path establishment request, that the transmission device is located on an active forwarding path between the multicast destination device and the multicast source device, the transmission device skips using the transmission device as a device on the standby forwarding path between the multicast destination device and the multicast source device, and skips forwarding the standby forwarding path establishment request.

The disclosure describes techniques for enhancements to the Multicast Source Discovery Protocol (MSDP) to reduce Source Active (SA) message loops in one or more multicast domains having overlapping MSDP mesh groups. In some examples, a method includes receiving, by a first MSDP speaker, from a second MSDP speaker, a SA message. The method also includes, when the second MSDP speaker is in a mesh group with the first MSDP speaker, determining whether the first MSDP speaker includes an active SA state corresponding to the SA message. Additionally, the method includes, when the first MSDP speaker does not include the active SA state corresponding to the SA message, accepting the SA message and forwarding the SA message to a third MSDP speaker that is not in the mesh group with the first MSDP speaker and the second MSDP speaker.

A message processing method and device, a storage medium, and an electronic device are provided. The method includes: receiving a message to be processed by means of a Bidirectional Forwarding Detection (BFD) processing engine of a chip, the BFD processing engine storing head Maintenance End Points (MEP); if a head MEP corresponding to the message to be processed is not found in the BFD processing engine of the chip, judging whether to forward the message to be processed to a processor; and if a judgment result is yes, saving the information of the message in a client MEP in the processor. The problem in the related art that an MEP on a Head side in RFC8562 only transmits but does not receive a BFD message, an MEP on a Tail side only receives but does not transmits a BFD message and thus the requirements cannot be satisfied is resolved.

A message processing method and device, a storage medium, and an electronic device are provided. The method includes: receiving a message to be processed by means of a Bidirectional Forwarding Detection (BFD) processing engine of a chip, the BFD processing engine storing head Maintenance End Points (MEP); if a head MEP corresponding to the message to be processed is not found in the BFD processing engine of the chip, judging whether to forward the message to be processed to a processor; and if a judgment result is yes, saving the information of the message in a client MEP in the processor. The problem in the related art that an MEP on a Head side in RFC8562 only transmits but does not receive a BFD message, an MEP on a Tail side only receives but does not transmits a BFD message and thus the requirements cannot be satisfied is resolved.

A method for reverse path forwarding (RPF) selection by a network device connected to a network includes receiving an advertisement message from each of a plurality of neighbor devices within the network, parsing the advertisement message to determine a color identification (ID) of each of the neighbor devices, and selecting, from among the neighbor devices, a RPF device based on the color ID of each of the neighbor devices.

A method for operation of a broadband access network of a telecommunications network includes: in a first step, a first access functionality primarily associated with a first central office point of delivery is also connected to a second central office point of delivery, and a second access functionality primarily associated with the second central office point of delivery is also connected to the first central office point of delivery; and in a second step, the cluster controller and both a first control functionality or control plane of the first central office point of delivery and a second control functionality or control plane of the second central office point of delivery control whether the first and second access functionalities are served by the first central office point of delivery or second central office point of delivery.

A method for operation of a broadband access network of a telecommunications network includes: in a first step, a first access functionality primarily associated with a first central office point of delivery is also connected to a second central office point of delivery, and a second access functionality primarily associated with the second central office point of delivery is also connected to the first central office point of delivery; and in a second step, the cluster controller and both a first control functionality or control plane of the first central office point of delivery and a second control functionality or control plane of the second central office point of delivery control whether the first and second access functionalities are served by the first central office point of delivery or second central office point of delivery.