Abstract: A network node adapted to forward incoming data packets, the network node including a tag identifying unit, adapted to identify a tag of an incoming data packet as a replicate tag; a tag look-up module, adapted to retrieve from a tag table a number of replications and destinations for the replicate tag; a replicating engine, configured to replicate the incoming data packet according to the number of replications, thereby generating replicated data packets; and a forwarding unit, adapted to forward the replicated data packets to the destinations.

Abstract: A first network device adapted for communication with one or more other network devices is configured to determine a number of receivers of a multicast, and to control switching of traffic between selective and inclusive routes for the multicast based at least in part on the determined number of receivers. For example, in some embodiments the first network device is configured to control switching of traffic between the selective and inclusive routes for the multicast by utilizing a selective route for the multicast responsive to a determination that traffic for the multicast is at or above a bandwidth threshold and the number of receivers is below an add threshold, and utilizing an inclusive route for the multicast responsive to a determination that traffic for the multicast is below the bandwidth threshold or the number of receivers is above a delete threshold.

Abstract: A first network device adapted for communication with one or more other network devices is configured to originate a first route identifying a tunnel for carrying traffic for a multicast, to originate a second route specifying a leaf information requirement for the multicast but not identifying a tunnel for carrying traffic for the multicast, and to track a plurality of receivers of the multicast based at least in part on leaf information received from the multicast receivers responsive to the specified leaf information requirement of the second route. The first route may comprise an inclusive route having a tunnel attribute that identifies an inclusive tunnel for the multicast and the second route may comprise a selective route having a tunnel attribute configured to indicate that it carries no tunnel information. Multicast traffic can be switched between an inclusive tunnel and a selective tunnel responsive to the multicast receiver tracking.

Abstract: A network node adapted to forward incoming data packets, the network node including a tag identifying unit, adapted to identify a tag of an incoming data packet as a replicate tag; a tag look-up module, adapted to retrieve from a tag table a number of replications and destinations for the replicate tag; a replicating engine, configured to replicate the incoming data packet according to the number of replications, thereby generating replicated data packets; and a forwarding unit, adapted to forward the replicated data packets to the destinations.

Abstract: A first network device adapted for communication with one or more other network devices is configured to originate a first route identifying a tunnel for carrying traffic for a multicast, to originate a second route specifying a leaf information requirement for the multicast but not identifying a tunnel for carrying traffic for the multicast, and to track a plurality of receivers of the multicast based at least in part on leaf information received from the multicast receivers responsive to the specified leaf information requirement of the second route. The first route may comprise an inclusive route having a tunnel attribute that identifies an inclusive tunnel for the multicast and the second route may comprise a selective route having a tunnel attribute configured to indicate that it carries no tunnel information. Multicast traffic can be switched between an inclusive tunnel and a selective tunnel responsive to the multicast receiver tracking.

Abstract: A first network device adapted for communication with one or more other network devices is configured to originate a first route identifying a tunnel for carrying traffic for a multicast, to originate a second route specifying a leaf information requirement for the multicast but not identifying a tunnel for carrying traffic for the multicast, and to track a plurality of receivers of the multicast based at least in part on leaf information received from the multicast receivers responsive to the specified leaf information requirement of the second route. The first route may comprise an inclusive route having a tunnel attribute that identifies an inclusive tunnel for the multicast and the second route may comprise a selective route having a tunnel attribute configured to indicate that it carries no tunnel information. Multicast traffic can be switched between an inclusive tunnel and a selective tunnel responsive to the multicast receiver tracking.

Abstract: A method for using OpenFlow protocol to configure an OpenFlow-enabled switch is disclosed. In the embodiment, the method involves decoding an OpenFlow flow entry from a flow mod message, the flow entry including two or more actions, searching a Service Access Point (SAP) match table for an outgoing interface having attributes that match the two or more actions, and updating a flow table on the OpenFlow-enabled switch to include the decoded flow entry when an outgoing interface having attributes that match the two or more actions is found.

Abstract: A method for using the OpenFlow protocol to configure an OpenFlow-enabled switch is disclosed. In the embodiment, the method involves decoding an OpenFlow flow entry from a flow mod message, the flow entry including two or more components comprising at least one of a match field and an experimenter field, searching a service access point (SAP) match table for an incoming interface having attributes that match the two or more components, and updating a flow table on the OpenFlow-enabled switch to include the decoded flow entry when an incoming interface having attributes that match the two or more components is found.

Abstract: A method for inserting an OpenFlow flow entry into a flow table is disclosed. In the embodiment, the method involves receiving a flow mod message at an OpenFlow-enabled switch, the flow mod message including a cookie field, decoding an OpenFlow flow entry from the flow mod message, identifying a flow table from the cookie field, and inserting the decoded flow entry into the flow table.

Abstract: A method for inserting an OpenFlow flow entry into a flow table is disclosed. In the embodiment, the method involves receiving a flow mod message at an OpenFlow-enabled switch, the flow mod message including a cookie field, decoding an OpenFlow flow entry from the flow mod message, identifying a flow table from the cookie field, and inserting the decoded flow entry into the flow table.

Abstract: A first network device adapted for communication with one or more other network devices is configured to originate a first route identifying a tunnel for carrying traffic for a multicast, to originate a second route specifying a leaf information requirement for the multicast but not identifying a tunnel for carrying traffic for the multicast, and to track a plurality of receivers of the multicast based at least in part on leaf information received from the multicast receivers responsive to the specified leaf information requirement of the second route. The first route may comprise an inclusive route having a tunnel attribute that identifies an inclusive tunnel for the multicast and the second route may comprise a selective route having a tunnel attribute configured to indicate that it carries no tunnel information. Multicast traffic can be switched between an inclusive tunnel and a selective tunnel responsive to the multicast receiver tracking.

Abstract: A first network device adapted for communication with one or more other network devices is configured to originate a first route identifying a tunnel for carrying traffic for a multicast, to originate a second route specifying a leaf information requirement for the multicast but not identifying a tunnel for carrying traffic for the multicast, and to track a plurality of receivers of the multicast based at least in part on leaf information received from the multicast receivers responsive to the specified leaf information requirement of the second route. The first route may comprise an inclusive route having a tunnel attribute that identifies an inclusive tunnel for the multicast and the second route may comprise a selective route having a tunnel attribute configured to indicate that it carries no tunnel information. Multicast traffic can be switched between an inclusive tunnel and a selective tunnel responsive to the multicast receiver tracking.

Abstract: A method for inserting an OpenFlow flow entry into a flow table is disclosed. In the embodiment, the method involves receiving a flow mod message at an OpenFlow-enabled switch, the flow mod message including a cookie field, decoding an OpenFlow flow entry from the flow mod message, identifying a flow table from the cookie field, and inserting the decoded flow entry into the flow table.

Abstract: A method for using OpenFlow protocol to configure an OpenFlow-enabled switch is disclosed. In the embodiment, the method involves decoding an OpenFlow flow entry from a flow mod message, the flow entry including two or more actions, searching a Service Access Point (SAP) match table for an outgoing interface having attributes that match the two or more actions, and updating a flow table on the OpenFlow-enabled switch to include the decoded flow entry when an outgoing interface having attributes that match the two or more actions is found.

Abstract: A method for using the OpenFlow protocol to configure an OpenFlow-enabled switch is disclosed. In the embodiment, the method involves decoding an OpenFlow flow entry from a flow mod message, the flow entry including two or more components comprising at least one of a match field and an experimenter field, searching a service access point (SAP) match table for an incoming interface having attributes that match the two or more components, and updating a flow table on the OpenFlow-enabled switch to include the decoded flow entry when an incoming interface having attributes that match the two or more components is found.

Abstract: A method for inserting an OpenFlow flow entry into a flow table is disclosed. In the embodiment, the method involves receiving a flow mod message at an OpenFlow-enabled switch, the flow mod message including a cookie field, decoding an OpenFlow flow entry from the flow mod message, identifying a flow table from the cookie field, and inserting the decoded flow entry into the flow table.

Abstract: Various exemplary embodiments relate to a method and related network element including one or more of the following: receiving, in a network element in the telecommunications network, a first plurality of packets transmitted from a P2P client to a P2P central entity, the first plurality of packets relating to a request for peer location information; performing deep packet inspection (DPI) to extract a key from the request for peer location information, the key identifying a P2P content item; querying a key storage module using the key to determine whether the key corresponds to a P2P content item for which transfers are to be prevented; and preventing subsequent transfers of the P2P content item between the P2P client and one or more peers that maintain the P2P content item.

Abstract: Virtual connection route selection apparatus and techniques are disclosed. At a communication traffic routing apparatus, metric information associated with multiple different routes for a virtual connection, such as a PseudoWire, toward a destination is collected. The metric information may be collected from one or more remote route computation elements capable of computing routes for virtual connections between the routing apparatus and other routing apparatus over an underlying communication system, or during actual establishment of the virtual connections, for example. An initial or re-optimized route for a virtual connection can then be selected at the routing apparatus based on the collected metric information. In some embodiments, although the virtual connection routes are paths computed by Path Computation Elements (PCEs), actual path selection decisions are distributed to routers.

Abstract: A first network device adapted for communication with one or more other network devices is configured to determine a number of receivers of a multicast, and to control switching of traffic between selective and inclusive routes for the multicast based at least in part on the determined number of receivers. For example, in some embodiments the first network device is configured to control switching of traffic between the selective and inclusive routes for the multicast by utilizing a selective route for the multicast responsive to a determination that traffic for the multicast is at or above a bandwidth threshold and the number of receivers is below an add threshold, and utilizing an inclusive route for the multicast responsive to a determination that traffic for the multicast is below the bandwidth threshold or the number of receivers is above a delete threshold.

Abstract: A first network device adapted for communication with one or more other network devices is configured to originate a first route identifying a tunnel for carrying traffic for a multicast, to originate a second route specifying a leaf information requirement for the multicast but not identifying a tunnel for carrying traffic for the multicast, and to track a plurality of receivers of the multicast based at least in part on leaf information received from the multicast receivers responsive to the specified leaf information requirement of the second route. The first route may comprise an inclusive route having a tunnel attribute that identifies an inclusive tunnel for the multicast and the second route may comprise a selective route having a tunnel attribute configured to indicate that it carries no tunnel information. Multicast traffic can be switched between an inclusive tunnel and a selective tunnel responsive to the multicast receiver tracking.