Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

We need a strategy to setup the maximum hello interval #4

Open
italovalcy opened this issue Sep 8, 2020 · 0 comments
Open

We need a strategy to setup the maximum hello interval #4

italovalcy opened this issue Sep 8, 2020 · 0 comments

Comments

@italovalcy
Copy link
Owner

Our proposal uses the adaptative hello interval to dynamically adjust the time between hello interests: between 1s and 60s. When a node stays some time without learning new neighbors, we consider the network is quite stable and increment the hello interval. Thus, the hello interval becomes a relation between being too short and rapidly detect changes with the price of increasing the overhead.

So far so good. However, when we have a highly dynamic environment and the node stays for a quite long time without adjacency nodes (e.g., moving away from anyone else), the hello increases, and maybe when someone comes to its neighborhood, we lose the adjacency detection window.

A way to solve this would be to take advantage of information from the underlayer protocols. In 802.11, for example, the beacon exchange gives us the "association list" that could help to set up the proper hello interval.

For now, we reduced the maximum hello interface to the average association time of the scenario (e.g., 5s - it depends on the scenario).

italovalcy added a commit that referenced this issue Sep 8, 2020
 - Change the syncData parameter from boolean to integer (number of
   rounds to generate data);
 - using a random interval (uniform dist 10ms - 15ms) to request
   data upon learning a new prefix;
 - changing the max hello interval from 60s to 5s (Issue #4);
 - Setting up a retransmission of data when the interest returns
   timeout (the producer node may had moved away);
 - many adjustments on the scenario/ndncomm2020-exp1.cpp
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant