A logical routing element (LRE) having multiple designated instances for routing packets from physical hosts (PH) to a logical network is provided. A PH in a network segment with multiple designated instances can choose among the multiple designated instances for sending network traffic to other network nodes in the logical network according to a load balancing algorithm. Each logical interface (LIF) of an LRE is defined to be addressable by multiple identifiers or addresses, and each LIF identifier or address is assigned to a different designated instance.

A network access point (NAP) of a second type of network is configured to receive a first type of packet from a device configured to operate in only a first type of network. The NAP is configured to determine an appropriate namespace for the first type of packet based on an address of an intended destination of the first type of packet. The NAP is configured to encapsulate the first type of packet into a second type of packet for use in the second type of network. The NAP is configured to route the second type of packet to a plurality of devices subscribed to the namespace in the second type of network.

A control device is connected to a plurality of networks, dispatches a packet received from a user terminal to a network among the plurality of networks, and includes a memory and a processor configured to execute receiving a DNS query packet transmitted from the user terminal, and based on a query target of the DNS query packet, dispatching the DNS query packet to a network among the plurality of networks; and receiving a packet, determining a destination of the packet based on a destination address of the packet, and transmitting the packet to the determined destination.

A method is provided in one example embodiment and may include determining at a parent content node that a plurality of recipient content nodes are to receive a same content; generating, based on a determination that the same content is available at the parent content node, a multi-delivery header comprising a plurality of identifiers, wherein each identifier of the plurality of identifiers indicates each recipient content node that is to receive the same content; appending the multi-delivery header to one or more packets of an Internet Protocol (IP) flow associated with the same content; and transmitting packets for the IP flow to each of the plurality of the recipient content nodes.

A network device may receive a message. The network device may determine that the message includes return information indicating a path to an initial device that generated the message. The network device may modify the message by adding an upstream device identifier, wherein the upstream device identifier identifies a device from which the message is received. The network device may modify the message by adding an indication of whether the initial device is reachable by the network device using a segment identifier. The network device may provide the modified message to a downstream device.

A network device may receive, from a first network, a network packet of a first network packet type that encapsulates a fragment of a second network packet of a second network packet type, where the network packet is part of a flow of a plurality of network packets of the first network packet type that encapsulates fragments of the second network packet, and where the network packet includes a flow label that indicates a source port for the second network packet. The network device may perform an anti-spoof check on the fragment of the second network packet based at least in part on the source port for the second network packet that is indicated by the flow label of the network packet. The network device may, based on the fragment passing the anti-spoof check, forward the fragment of the second network packet to a second network.

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.

A method is disclosed, comprising: receiving a first and a second Internet Protocol (IP) packet at a mesh network node; tagging the first and the second IP packet at the mesh network node based on a type of traffic by adding an IP options header to each of the first and the second IP packet; forwarding the first and the second IP packet toward a mesh gateway node; filtering the first and the second IP packet at the mesh gateway node based on the added IP options header by assigning each of the first and the second IP packet to one of a plurality of message queues, each of the plurality of message queues having a limited forwarding throughput; and forwarding the first and the second IP packet from the mesh gateway node toward a mobile operator core network, thereby providing packet flow filtering based on IP header and traffic type.

A USB-to-coaxial network bridging system and method includes receiving data frames from a USB or FireWire device via a corresponding USB or FireWire communication interface, wherein the received data frames are intended for transmittal to a predetermined remote device on a coaxial network; combining the received data frames into an aggregated frame and addressing the aggregated frame to allow the aggregated frame to be routed to the predetermined remote device on the coaxial network; and sending the aggregated frame to the remote device over the coaxial network.

A method of delivering content in one or more packets over a network is described. A content request packet comprising a request for content based on a first IPv6 address is received, the first IPv6 address identifying the content. The first IPv6 address is mapped to a second IPv6 address, the second IPv6 address being associated with the content at a physical location. The content requested in the content request packet is then received from the physical location associated with the second IPv6 address for delivery to a user. A further method includes routing a packet for requesting the content from a client to a content server storing an instant of the content, based on an IPv6 address of content being requested by the client. A communication session is then set up between the client and the content server; and the requested content is transmitted from the content server.