diff options
author | Georg Kunz <georg.kunz@ericsson.com> | 2016-07-22 17:38:22 +0200 |
---|---|---|
committer | Georg Kunz <georg.kunz@ericsson.com> | 2016-07-22 17:38:22 +0200 |
commit | e3448d10dcd973e60b6b2819bbc2dba8455b9c11 (patch) | |
tree | f38411d41e4b1740a5090349ada0c8db75f0db9b /docs/requirements/use_cases/l3vpn_hub_and_spoke.rst | |
parent | a973062e984d73b04f71790af4ed1fa05172ec71 (diff) |
Incorporating further review comments
Change-Id: I65fa2036f32c018c3d9cda46a82c6f1e2d4e6323
Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
Diffstat (limited to 'docs/requirements/use_cases/l3vpn_hub_and_spoke.rst')
-rw-r--r-- | docs/requirements/use_cases/l3vpn_hub_and_spoke.rst | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/docs/requirements/use_cases/l3vpn_hub_and_spoke.rst b/docs/requirements/use_cases/l3vpn_hub_and_spoke.rst index 07004ef..17459b6 100644 --- a/docs/requirements/use_cases/l3vpn_hub_and_spoke.rst +++ b/docs/requirements/use_cases/l3vpn_hub_and_spoke.rst @@ -8,12 +8,12 @@ Hub and Spoke Case Description ~~~~~~~~~~~ -A Hub-and-spoke topology comprises two types of network entities: a central hub -and multiple spokes. The corresponding VRFs of the hub and the spokes are -configured to import and export routes such that all traffic is routed through -the hub. As a result, spokes cannot communicate with each other directly, but -only indirectly via the central hub. Hence, the hub typically hosts central network -functions such firewalls. +In a traditional Hub-and-spoke topology there are two types of network entities: +a central hub and multiple spokes. The corresponding VRFs of the hub and the +spokes are configured to import and export routes such that all traffic is +directed through the hub. As a result, spokes cannot communicate with each other +directly, but only indirectly via the central hub. Hence, the hub typically +hosts central network functions such firewalls. Furthermore, there is no layer 2 connectivity between the VNFs. |