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

Flows Reduction Scheme Using Two MPLS Tags in Software-Defined Network

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

0
9
0

Year Published

2018
2018
2021
2021

Publication Types

Select...
4
1
1

Relationship

0
6

Authors

Journals

citations
Cited by 12 publications
(11 citation statements)
references
References 12 publications
0
9
0
Order By: Relevance
“…In our opinion, use of a single node as an entrance to each region increases probability of a congestion. We cannot qualitatively compare this mechanism with our solution because paper [28] does not introduce any multipath transmission method. The next advantage of our mechanism present contrary to [28] is a lack of communication between switches and a controller for every new flow installation (excluding the extension presented is Subsection III-C).…”
Section: Discussionmentioning
confidence: 98%
See 3 more Smart Citations
“…In our opinion, use of a single node as an entrance to each region increases probability of a congestion. We cannot qualitatively compare this mechanism with our solution because paper [28] does not introduce any multipath transmission method. The next advantage of our mechanism present contrary to [28] is a lack of communication between switches and a controller for every new flow installation (excluding the extension presented is Subsection III-C).…”
Section: Discussionmentioning
confidence: 98%
“…To be consistent with our terminology, we use the 'edge' notion for the nodes where host networks are connected. When a network posessing 100 edge nodes is divided into 10 regions, each with 10 edge nodes, the maximum number of flow entries in a core node is 20 for mechanism proposed in [28]. Such the number is valid when only one node is a communication point for other regions.…”
Section: Discussionmentioning
confidence: 99%
See 2 more Smart Citations
“…Due to the passivity of current IP networks, a novel routing protocol can take five to ten years to be completely produced, estimated, and used. Furthermore, a clean-slate plan to change the Internet architecture 20 (e.g., replacing IP) is viewed as a daunting mission not possible in practice [3,4].…”
Section: Introductionmentioning
confidence: 99%