English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Plus monthly

Global: Zendy Tools annual

Global: Zendy Tools monthly

Global: Zendy Free Plan

To answer traffic engineering goals, current backbone networks use expensiveand sophisticated equipments, that run distributed algorithms to imple- mentdynamic multi-path routing (e.g., MPLS tunnels and dynamic trunk rerout- ing).We think that the same goals can be fulfilled using a simpler approach, wherethe core of the backbone only implements many a priori computed paths, and mostadaptation to traffic engineering goals only takes place at the edge of thenetwork. In the vein of Software Defined Networking, edge adaptation should bedriven by a logically centralized controller that leverages the available pathsto adapt traffic load balancing to the current demands and network status. Inthis article we present two algorithms to help building this vision. The firstone selects sets of paths able to support future load balancing needs andadaptation to network faults. As the total number of required paths is veryimportant, and their continuous availability requires many FIB entries in corerouters, we also present a second algorithm that aggregates these paths in areduced number of trees. This second algorithm achieves better results thanpreviously proposed algorithms for path aggregation. To conclude, we show thatoff-the-shelf equipment supporting simple protocols may be used to implementrouting with these trees, what shows that simplicity in the core can beachieved by using only trivially available proto- cols and their most commonand unsophisticated implementation

Relieving Core Routers from Dynamic Routing with off-the-shelf Equipment and Protocols