Dynamic Service Chaining with Dysco

Zave, Pamela; Ferreira, Ronaldo A.; Zou, Xuan Kelvin; Morimoto, M.; Rexford, Jennifer

doi:10.1145/3098822.3098827

“…It is based on a source routing model to steer traffic segment to segment. Recent work has also made the case for session protocol to build service overlay [34]. Even if the approach allows dynamic chaining, it relies on extending/modifying TCP, which, in an ossified Internet, is a hard task [19].…”

Section: Related Workmentioning

confidence: 99%

Distributed Function Chaining with Anycast Routing

Wion

¹

,

Bouet

²

,

Iannone

³

et al. 2019

Proceedings of the 2019 ACM Symposium on SDN Research

View full text Add to dashboard Cite

Current networks more and more rely on virtualized middleboxes to flexibly provide security, protocol optimization, and policy compliance functionalities. As such, delivering these services requires that the traffic be steered through the desired sequence of virtual appliances. Current solutions introduce a new logically centralized entity, often called orchestrator, needing to build its own holistic view of the whole network so to decide where to direct the traffic.We advocate that such a centralized orchestration is not necessary and that, on the contrary, the same objectives can be achieved by augmenting the network layer routing so to include the notion of service and its chaining.In this paper, we support our claim by designing such a system. We also present an implementation and an early evaluation, showing that we can easily steer traffic through available resources. This approach also offers promising features such as incremental deployability, multi-domain service chaining, failure resiliency, and easy maintenance.

show abstract

“…Second, they grow in complexity when a vSF make a hard to handle change in network headers (e.g., Network Address Translation service) [7], [8], [10]. Recent works, instead, propose to (i) encode service chains as a set of waypoints in the packet header, and (ii) rely on the network routing layer for waypoint connectivity [9], [11], [12]. This approach is not only interoperable with regular IP networks but also reduce forwarding state.…”

Section: Related Workmentioning

confidence: 99%

“…This approach is not only interoperable with regular IP networks but also reduce forwarding state. Indeed, flow path is either fully described in packet headers [9], [11] or stored on waypoints at flow initialization [12]. Several techniques have been proposed to encode the path of service function chains [11]- [13].…”

Section: Related Workmentioning

confidence: 99%

“…Several techniques have been proposed to encode the path of service function chains [11]- [13]. In Segment Routing v6 [11] and Dysco [12], an ingress node is in charge of setting a list of locations to reach before being delivered using IPv6 and TCP extensions respectively. Recent work at the Internet Engineering Task Force (IETF) proposes Network Service Header (NSH) as a dedicated encapsulation header for service chaining [13].…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Let there be chaining: how to augment your IGP to chain your services

Wion

¹

,

Bouet

²

,

Iannone

³

et al. 2019

2019 IFIP Networking Conference (IFIP Networking)

0

View full text Add to dashboard Cite

Ever since Network Functions Virtualization has replaced dedicated appliances, ISPs have been able to add a degree of flexibility in their traffic engineering. However, it also has increased the complexity of the optimization problem, because it is now necessary to place virtual functions and route traffic jointly. Insofar, a logically centralized approach has been taken, where a so-called orchestrator, having full knowledge of the network, the virtual functions, and the traffic, run complex algorithms to find a suitable solution to the problem. The outcome of the algorithms are then translated to network configurations to be pushed to all of the appliances. We argue that there is no need to fully centralize every decision, rather we can leverage existing network intelligence to achieve the same goal. In particular we propose to augment the routing layer with the notion of services, so to rely on the robustness and scalability of Interior Gateway Protocols (IGP). Our solution leverages on existing distributed routing protocols where, in addition, autonomous nodes announce information about the virtual services they provide. Our design is modular and incrementally deployable and has been implemented in what we call a NFV Router. In our evaluation, we show that (i) NFV Routers distributed chaining decisions are close to optimal centrally-computed paths, (ii) on a large scale testbed deployment, NFV Routers efficiently steer traffic through chains and only add a small overhead to control traffic and (iii) our distributed system, because of its local control loop, has a faster reaction to network events than centralized solutions.

show abstract

“…Second, they grow in complexity when a vSF make a hard to handle change in network headers (e.g., Network Address Translation service) [7], [8], [10]. Recent works, instead, propose to (i) encode service chains as a set of waypoints in the packet header, and (ii) rely on the network routing layer for waypoint connectivity [9], [11], [12]. This approach is not only interoperable with regular IP networks but also reduce forwarding state.…”

Section: Related Workmentioning

confidence: 99%

Let there be Chaining: How to Augment your IGP to Chain your Services

Wion¹,

Bouet²,

Iannone³

et al. 2019

2019 IFIP Networking Conference (IFIP Networking)

1

0

View full text Add to dashboard Cite

Ever since Network Functions Virtualization has replaced dedicated appliances, ISPs have been able to add a degree of flexibility in their traffic engineering. However, it also has increased the complexity of the optimization problem, because it is now necessary to place virtual functions and route traffic jointly. Insofar, a logically centralized approach has been taken, where a so-called orchestrator, having full knowledge of the network, the virtual functions, and the traffic, run complex algorithms to find a suitable solution to the problem. The outcome of the algorithms are then translated to network configurations to be pushed to all of the appliances. We argue that there is no need to fully centralize every decision, rather we can leverage existing network intelligence to achieve the same goal. In particular we propose to augment the routing layer with the notion of services, so to rely on the robustness and scalability of Interior Gateway Protocols (IGP). Our solution leverages on existing distributed routing protocols where, in addition, autonomous nodes announce information about the virtual services they provide. Our design is modular and incrementally deployable and has been implemented in what we call a NFV Router. In our evaluation, we show that (i) NFV Routers distributed chaining decisions are close to optimal centrally-computed paths, (ii) on a large scale testbed deployment, NFV Routers efficiently steer traffic through chains and only add a small overhead to control traffic and (iii) our distributed system, because of its local control loop, has a faster reaction to network events than centralized solutions.

show abstract

Dynamic Service Chaining with Dysco

Cited by 47 publications

References 21 publications

Distributed Function Chaining with Anycast Routing

Distributed Function Chaining with Anycast Routing

Let there be chaining: how to augment your IGP to chain your services

Let there be Chaining: How to Augment your IGP to Chain your Services

Contact Info

Product

Resources

About