Abstract: Various example embodiments for supporting link-state flooding for a routing protocol based on use of a transport layer protocol are presented. Various example embodiments for supporting link-state flooding for a routing protocol based on use of a transport layer protocol may be configured to support use of routing protocol messages of the routing protocol to support establishment of transport layer connections of a transport layer protocol (e.g., use of adjacency messages of the routing protocol for identifying routers configured to support use of transport layer connections for supporting link-state flooding). Various example embodiments for supporting link-state flooding for a routing protocol based on use of a transport layer protocol may be configured to support use of transport layer connections to support communication of routing protocol messages of the routing protocol (e.g.

Abstract: Various example embodiments for supporting service differentiation in a communication network are presented herein. The service differentiation may be supported in a constrained network topology of the communication network. The service differentiation may be supported in the constrained network topology of the communication network based on use of one or more constrained network topology slices supported for the constrained network topology of the communication network. The constrained network topology of the communication network may be a Flexible Algorithm topology, in which case the constrained network topology slices may be Flexible Algorithm topology slices.

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: Various example embodiments for supporting link-state flooding for routing protocols may be configured to support sparse link-state flooding for routing protocols. Various example embodiments for supporting sparse link-state flooding for routing protocols may be configured to support sparse link-state flooding for routing protocols by supporting distributed establishment of a sparse link-state flooding topology. Various example embodiments for supporting link-state flooding for routing protocols may be configured to support sparse link-state flooding for routing protocols based on processes for enabling routers to identify and clamp onto a sparse link-state flooding topology.

Abstract: Various example embodiments for supporting link-state flooding for routing protocols may be configured to support sparse link-state flooding for routing protocols. Various example embodiments for supporting sparse link-state flooding for routing protocols may be configured to support sparse link-state flooding for routing protocols by supporting distributed establishment of a sparse link-state flooding topology. Various example embodiments for supporting link-state flooding for routing protocols may be configured to support sparse link-state flooding for routing protocols based on processes for enabling routers to identify and clamp onto a sparse link-state flooding topology.

Abstract: Various example embodiments for supporting link-state flooding for a routing protocol based on use of a transport layer protocol are presented. Various example embodiments for supporting link-state flooding for a routing protocol based on use of a transport layer protocol may be configured to support use of routing protocol messages of the routing protocol to support establishment of transport layer connections of a transport layer protocol (e.g., use of adjacency messages of the routing protocol for identifying routers configured to support use of transport layer connections for supporting link-state flooding). Various example embodiments for supporting link-state flooding for a routing protocol based on use of a transport layer protocol may be configured to support use of transport layer connections to support communication of routing protocol messages of the routing protocol (e.g.

Abstract: Various example embodiments for supporting link-state flooding for routing protocols may be configured to support sparse link-state flooding for routing protocols. Various example embodiments for supporting sparse link-state flooding for routing protocols may be configured to support sparse link-state flooding for routing protocols by supporting distributed establishment of a sparse link-state flooding topology. Various example embodiments for supporting link-state flooding for routing protocols may be configured to support sparse link-state flooding for routing protocols based on processes for enabling routers to identify and clamp onto a sparse link-state flooding topology.

Abstract: For securely transferring an authorization of connected objects, a supervision server (SS): receives a report (Rp) on authentication, authorization and accounting of a connected object (CO), said report containing the IP address at which the connected object can be reached a persistent identifier of the connected object, determines a manufacturer of the connected object by means of said persistent identifier, identifies at least one pre-established trust domain associated with said manufacturer, by means of a secure policy associated with said manufacturer, the trust domain defining a set of credentials or certificates and mechanisms for communication between the supervision server (SS) and an application server (AS), producing an authorization state of the connected object by means of the received report (Rp), instructs a network device (ND) to be programmed with rules that are identified in the secure policy associated with the manufacturer and that admit the IP address of the connected object, the network

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: One embodiment includes, inter alia, methods, apparatus, computer-storage media, mechanisms, and/or means associated with automated transitioning between different communication protocols in a network. In one embodiment, automatic transition routers are automatically discovered along with the knowledge of what non-native protocols need to be transported across a network. Communication pathways are automatically established as needed to transport these non-native protocols. One embodiment is particularly useful in transitioning a network from one protocol to another, such as from Internet Protocol version 4 to version 6.

Abstract: In one embodiment, a packet switching device receives a particular directive to throttle a flow of packet traffic. In response, the packet switching device performs an analysis to determine one or more reduced number of flow throttling engines of a plurality of flow throttling engines in the packet switching device configured to be responsive to a received directive to throttle a corresponding flow of packet traffic. The one or more reduced number of flow throttling engines correspond to learned one or more incoming interfaces on which packets of the flow of packet traffic are correct in being received, and the one or more reduced number of flow throttling engines is less than all of the plurality of flow throttling engines. The packet switching device configures to throttle the flow of packet traffic in each of said one or more reduced number of flow throttling engines.

Abstract: One embodiment includes, inter alia, methods, apparatus, computer-storage media, mechanisms, and/or means associated with automated transitioning between different communication protocols in a network. In one embodiment, automatic transition routers are automatically discovered along with the knowledge of what non-native protocols need to be transported across a network. Communication pathways are automatically established as needed to transport these non-native protocols. One embodiment is particularly useful in transitioning a network from one protocol to another, such as from Internet Protocol version 4 to version 6.

Abstract: One embodiment includes, inter alia, methods, apparatus, computer-storage media, mechanisms, and/or means associated with automated transitioning between different communication protocols in a network. In one embodiment, automatic transition routers are automatically discovered along with the knowledge of what non-native protocols need to be transported across a network. Communication pathways are automatically established as needed to transport these non-native protocols. One embodiment is particularly useful in transitioning a network from one protocol to another, such as from Internet Protocol version 4 to version 6.

Abstract: One embodiment includes, inter alia, methods, apparatus, computer-storage media, mechanisms, and/or means associated with automated transitioning between different communication protocols in a network. In one embodiment, automatic transition routers are automatically discovered along with the knowledge of what non-native protocols need to be transported across a network. Communication pathways are automatically established as needed to transport these non-native protocols. One embodiment is particularly useful in transitioning a network from one protocol to another, such as from Internet Protocol version 4 to version 6.