From 09b075e1823e3358deaad6a6fc7c62c239fbab0b Mon Sep 17 00:00:00 2001 From: garciadeblas Date: Tue, 8 Nov 2016 19:14:55 +0100 Subject: [PATCH] euag_service_chaining_use_case.md Change-Id: I8f47a033139e2056e2c98779c54fe1b5db789dee --- Release5/euag_service_chaining_use_case.md | 31 ++++++++++++++++++++++ 1 file changed, 31 insertions(+) create mode 100644 Release5/euag_service_chaining_use_case.md diff --git a/Release5/euag_service_chaining_use_case.md b/Release5/euag_service_chaining_use_case.md new file mode 100644 index 0000000..4261c29 --- /dev/null +++ b/Release5/euag_service_chaining_use_case.md @@ -0,0 +1,31 @@ +# Service chaining use case # + +## Proposer ## +**EUAG** + +## Type ## +**Feature** + +## Target MDG/TF ## +LCM, RO + +## Description ## +A SP wants to offer a service to corporations consisting of a VPN service with +access to different types of endpoints (other corporate sites, Internet or +public cloud) where each corporation can insert a custom chain of VNFs in the +middle. + +Selected traffic from corporates can reach an NFV datacenter. Once in the +datacenter, the corporation can select which chains to be used for each traffic +flow (i.e. classified) depending on e.g. the source and destination of the +traffic. For instance: + +* FROM Corporate site TO Amazon: chain A +* FROM Corporate site TO Internet: chain B +* FROM Corporate site TO Corporate site: chain C +* FROM a VPN connection from an employee TO Internet: chain D +* FROM a VPN connection from an employee TO Corporate Site: chain C + +## Demo or definition of done ## +N/A + -- 2.17.1