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: 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: A first network node maintains separate routing policy information to forward network traffic depending on a direction of the network traffic. Upstream routing policy information at the first node identifies a second node to forward upstream traffic received from at least a first client communicating through the first node. Downstream routing policy information at the first node identifies how to forward downstream network traffic received from another node to the first client. By preventing use of the downstream policy routing information by the first client to route upstream network traffic, the first node is able to forward traffic along a path that the network traffic otherwise would have not traveled. For example, network traffic communicated through the first node can be forced to travel through another network node through which it would have not otherwise have passed if the downstream policy information was available to route the network traffic.