2017
DOI: 10.1016/j.procs.2017.10.051
|View full text |Cite
|
Sign up to set email alerts
|

Efficient Topology Discovery in Software Defined Networks: Revisited

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
10
0

Year Published

2019
2019
2022
2022

Publication Types

Select...
7

Relationship

0
7

Authors

Journals

citations
Cited by 23 publications
(10 citation statements)
references
References 6 publications
0
10
0
Order By: Relevance
“…3b and Fig. 3c represent the usual exchange of HDDP Request and HDDP Reply messages, respectively, as explained in the previous section (steps [1][2][3][4][5][6][7][8]. In the hypothetical situation in which, for example, node E3 moves, this is noticed by the periodic exchange of Hello messages.…”
Section: B Hddp In Wireless Scenariosmentioning
confidence: 98%
See 2 more Smart Citations
“…3b and Fig. 3c represent the usual exchange of HDDP Request and HDDP Reply messages, respectively, as explained in the previous section (steps [1][2][3][4][5][6][7][8]. In the hypothetical situation in which, for example, node E3 moves, this is noticed by the periodic exchange of Hello messages.…”
Section: B Hddp In Wireless Scenariosmentioning
confidence: 98%
“…Nowadays, there is no standalone topology discovery solution that can obtain the full topology of a hybrid SDN domain with SDN and non-SDN devices. The most commonly deployed service for topology discovery in SDN is OFDP [3], based on Link Layer Discovery Protocol (LLDP). However, OFDP requires that all devices support OpenFlow [3].…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…Hasan and Othman [25] revisit the current OpenFlowbased topology discovery protocols, taking into account the effects of retransmitting the discovery packets until the SDN controller identifies the entire map of the network. To that end, the authors re-implemented the OFDPv2 proposed in [22] and [23] and compared it with the standard OFDP protocol.…”
Section: A Openflow-based Approachesmentioning
confidence: 99%
“…In [22], [23], [25]- [27], and [29], the controller needs, as previous knowledge, the IP address and the list of active ports of each SDN switch in the network. This knowledge is obtained through the establishment of an initial handshake between the controller and forwarding devices.…”
Section: A Openflow-based Approachesmentioning
confidence: 99%