The present disclosure relates to an optical line terminal device. The optical line terminal device includes a data center point of presence module, one or more access point of presence modules and one or more aggregation point of presence modules. The data center point of presence module includes a first region and a second region. The first region includes a leaf and spine fabric and a top-of-rack architecture. The second region includes compute infrastructure and storage infrastructure. Further, the one or more access point of presence modules include optical line terminal-Gigabit Passive Optical Networks access input/output and Metro Ethernet Access input/output. The one or more aggregation point of presence include access input/output hardware abstraction, limited compute infrastructure and multi-protocol label switching transfer router.

A device may receive, from a provider edge device, a packet to be provided to one or more other provider edge devices. Some of the one or more other provider edge devices may be multi-homed with a same customer edge device as the provider edge device. The device may configure a source IP address of the packet based on a capability of an assisted replicator device after receiving the packet. The capability may relate to whether the assisted replicator device is capable of retaining the source IP address of the packet as received from the provider edge device. The device may provide the packet to at least some provider edge devices, of the one or more other provider edge devices, after configuring the source IP address of the packet.

This application discloses a packet processing method and an LSR. The method includes: receiving, by an Ingress LSR of a first MPLS tunnel, a first notification packet that is based on an IGP, where the first notification packet includes an ELC flag, which is used to indicate that the first Egress LSR has ELC; after learning from the first notification packet that the first Egress LSR has ELC, inserting a label into a first packet, to generate a second packet, where the label forms an MPLS label stack, which includes, from bottom to top, a first EL, a first ELI, and a first TL; and sending the second packet to the first Egress LSR through the first MPLS tunnel.

Systems, methods, and computer-readable media are provided for determining a packet's round trip time (RTT) in a network. A system can receive information of a packet sent by a component of the network and further determine an expected acknowledgement (ACK) sequence number associated with the packet based upon received information of the packet. The system can receive information of a subsequent packet received by the component and determine an ACK sequence number and a receiving time of the subsequent packet. In response to determining that the ACK sequence number of the subsequent TCP packet matches the expected ACK sequence number, the system can determine a round trip time (RTT) of the packet based upon the received information of the packet and the received information of the subsequent packet.

A forwarding table generation method is provided. The method includes: determining, by a forwarding device, a first timeslot set, where the first timeslot set includes multiple timeslots during which the forwarding device sends, to a first device by using a first flexible Ethernet group, multiple encoded data blocks generated by a physical coding sublayer; determining, by the forwarding device, a second timeslot set, where the second timeslot set includes multiple timeslots during which the forwarding device receives, by using a second FlexE group, the multiple encoded data blocks sent by a second device; and generating, by the forwarding device, a forwarding table, where the forwarding table includes a mapping relationship between the second FlexE group and the multiple timeslots included in the second timeslot set, and between the first FlexE group and the multiple timeslots included in the first timeslot set.

A method of streaming media content over a network from a media cache node is described. The method includes receiving a request for a media content item from a client device, the request comprising an address identifying a media content item to be streamed. In response to the request, a streaming engine process is allocated to the media content item for fulfilling the request. Based on the address identifying the media content item, a location comprising a media cache node able to provide the media content item is determined and the media content item is streamed to the client device using the streaming engine process allocated to the media content item. Further methods of streaming a media content item and providing access to media content are also described.

A method provides for receiving network traffic from a host having a host IP address and operating in a data center, and analyzing a malware tracker for IP addresses of hosts having been infected by a malware to yield an analysis. When the analysis indicates that the host IP address has been used to communicate with an external host infected by the malware to yield an indication, the method includes assigning a reputation score, based on the indication, to the host. The method can further include applying a conditional policy associated with using the host based on the reputation score. The reputation score can include a reduced reputation score from a previous reputation score for the host.

Disclosed is a mechanism that provides the extensions of PCEP message and the objects to support PCECC with P2MP capability in downloading the labels for branch node of P2MP TE LSPs. In one implementation, various embodiments provide an apparatus, a system, a node and a method that receives a PCLabelUpd message with all the extensions and the objects to support PCECC with P2MP capability, detects the object and identifies that the label download is for P2MP TE LSP and for this LSP. In those embodiments, the apparatus/the system/the node acts as a branch node, and thereby the apparatus/the system/the node downloads all the labels specified in the object to data plane with respect to any existing branch node download mechanism for a P2MP TE LSP.

Echo or traceroute functionality is supported in a path spanning multiple autonomous systems (ASes) having segment routing (SR) enabled, the path including an ingress node and an egress node, by: (a) obtaining a return label stack to reach the ingress node from either (A) the egress node, or (B) a transit node in the path; (b) obtaining a label stack to reach, from the ingress node, either (A) the egress node, or (B) the transit node; (c) generating a request message including the return label stack; and (d) sending the request message towards either (A) the egress node, or (B) the transit node using the label stack. The example method may further include: (e) receiving, by either (A) the egress node, or (B) the transit node, the request message, wherein the request message includes information for performing a validity check; (f) performing a validity check using the information included in the request message to generate validity information; (g) generating a reply message including the validity information and information from the return label stack; and (h) sending the reply message towards the ingress node using information from the return label stack included in the request message.

Techniques are described in which a centralized controller constructs a service chain between a bare metal server (BMS) and a virtual execution element (e.g., virtual machine or container), or in some instances a remote BMS, across a plurality of networks. In some examples, the controller may construct a service chain between a BMS and a virtual execution element or remote BMS using Ethernet Virtual Private Network (EVPN)-Virtual Extensible Local Area Network (VXLAN) and Internet Protocol Virtual Private Networks (IP VPNs) such as BGP/Multiprotocol Label Switching (BGP/MPLS) IP VPNs.