2016 13th Annual IEEE International Conference on Sensing, Communication, and Networking (SECON) 2016
DOI: 10.1109/sahcn.2016.7733012
|View full text |Cite
|
Sign up to set email alerts
|

RedFixHop: Efficient Ultra-Low-Latency Network Flooding

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
7
0

Year Published

2019
2019
2024
2024

Publication Types

Select...
3
3

Relationship

0
6

Authors

Journals

citations
Cited by 6 publications
(7 citation statements)
references
References 1 publication
0
7
0
Order By: Relevance
“…The Spine Constructive Interference-based Flooding (SCIF) protocol [136,137] extends Glossy with a topology-control mechanism that makes it scale to high-density or large-scale networks, where the authors report that the performance of synchronous transmissions degrades. RedFixHop [37] uses the same transmission technique as Glossy, but encodes the payload in the Medium Access Control (MAC) packet sequence number. Upon the reception of a packet, a node forwards it using hardware-generated acknowledgments.…”
Section: Communication Patternmentioning
confidence: 99%
See 1 more Smart Citation
“…The Spine Constructive Interference-based Flooding (SCIF) protocol [136,137] extends Glossy with a topology-control mechanism that makes it scale to high-density or large-scale networks, where the authors report that the performance of synchronous transmissions degrades. RedFixHop [37] uses the same transmission technique as Glossy, but encodes the payload in the Medium Access Control (MAC) packet sequence number. Upon the reception of a packet, a node forwards it using hardware-generated acknowledgments.…”
Section: Communication Patternmentioning
confidence: 99%
“…A number of protocols use the same flavor of end-to-end retransmissions, including Crystal [52,53], Choco [129], and WTSP [128]. These protocols and many others based on synchronous transmissions also benefit from local (i.e., one-hop) retransmissions; for example, in Glossy [41], RedFixHop [37], or Zippy [123] every node in the network opportunistically retransmits a packet up to a certain number of times. Local retransmissions may also be triggered by an explicit request as used in Codecast [94], Mixer [47,90], or Splash [27] to collect a few packets that some nodes still miss toward the end of a many-to-many or one-to-all communication phase.…”
Section: Reliability Mechanismsmentioning
confidence: 99%
“…The Spine Constructive Interference-based Flooding (SCIF) protocol [123,124] extends Glossy with a topology-control mechanism that makes it scale to high-density or large-scale networks, where the authors report that the performance of synchronous transmissions degrades. RedFixHop [32] uses the same transmission technique as Glossy, but encodes the payload in the Medium Access Control (MAC) packet sequence number. Upon the reception of a packet, a node forwards it using hardware-generated acknowledgments.…”
Section: Communication Patternmentioning
confidence: 99%
“…A number of protocols use the same flavor of end-to-end retransmissions, including Crystal [47,48], Choco [116], and WTSP [115]. These protocols and many others based on synchronous transmissions also benefit from local (i.e., one-hop) retransmissions; for example, in Glossy [36], RedFixHop [32], or Zippy [110] every node in the network opportunistically retransmits a packet up to a certain number of times. Local retransmissions may also be triggered by an explicit request as used in Codecast [84], Mixer [42,80], or Splash [22] to collect a few packets that some nodes still miss toward the end of a many-to-many or one-to-all communication phase.…”
Section: Retransmissions Despite Very Few Exceptions All Communicatio...mentioning
confidence: 99%
See 1 more Smart Citation