2017
DOI: 10.1109/mcom.2017.1600177
|View full text |Cite
|
Sign up to set email alerts
|

Resilient Integration of Distributed High-Performance Zones into the BelWue Network Using OpenFlow

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
4
0

Year Published

2017
2017
2021
2021

Publication Types

Select...
2
2
1

Relationship

0
5

Authors

Journals

citations
Cited by 5 publications
(4 citation statements)
references
References 3 publications
0
4
0
Order By: Relevance
“…Novel methods are proposed for "east-west" inter-controller exchange and domain virtualization. Meanwhile, [12] proposes a resilient SDN architecture for connecting highperformance zones in a higher-education network. The authors also use OpenFlow devices to perform failover switching for isolated link outages.…”
Section: Existing Workmentioning
confidence: 99%
See 1 more Smart Citation
“…Novel methods are proposed for "east-west" inter-controller exchange and domain virtualization. Meanwhile, [12] proposes a resilient SDN architecture for connecting highperformance zones in a higher-education network. The authors also use OpenFlow devices to perform failover switching for isolated link outages.…”
Section: Existing Workmentioning
confidence: 99%
“…Still, SDN only provides a control framework and relegates detailed service provisioning and recovery algorithm design to operators themselves. Despite some notable testbed studies [11]- [12] [13], there are no known works on SDN-based disaster recovery. Hence, this effort focuses on translating advanced counter-EMP service recovery schemes (only studied in research literature) into real-world settings by developing a resilient SDN-based management and orchestration (MANO) framework.…”
Section: Introductionmentioning
confidence: 99%
“…is not acceptable for SDN, because unprotected flows remain disconnected or FRR-caused loops persist until the controller comes to rescue. Several solutions based on OpenFlow have been proposed in the literature so far, e.g., based on ideas from LFA [192], [264] or MPLS [254], by encoding primary and backup paths in the packet header [255], or by extending to OpenFlow's fast failover action based on additional state in the OpenFlow pipeline: for example, SPIDER [260] leverages packet labels to carry reroute and connectivity information. An alternative OpenFlow switch design which relies on logical group ports and which aims to support connectivity monitoring, has been proposed by Kempf et al [254] in the context of MPLS networks.…”
mentioning
confidence: 99%
“…The second is not acceptable for SDN, because unprotected flows remain disconnected or FRR-caused loops persist until the controller comes to rescue. Several solutions based on OpenFlow have been proposed in the literature so far, e.g., based on ideas from LFA [184], [255] or MPLS [245], by encoding primary and backup paths in the packet header [246], or by extending to OpenFlow's fast failover action based on additional state in the OpenFlow pipeline: for example, SPIDER [251] leverages packet labels to carry reroute and connectivity information.…”
mentioning
confidence: 99%