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

Design loop tracing for Stingray #5

Closed
michielbdejong opened this issue Mar 8, 2024 · 2 comments
Closed

Design loop tracing for Stingray #5

michielbdejong opened this issue Mar 8, 2024 · 2 comments

Comments

@michielbdejong
Copy link
Contributor

As I'm designing Stingray, having implemented the flood probes and pin probes from #4, there comes a point in the algorithm where a node becomes aware of a proof of loop and starts a loop trace.
This loop trace is linked to the probeId and goes out in both directions.

In all cases a loop trace is started when a pin probe comes back.

       North
        |
West - Alice  - East
        |        |
       South ___/

What if you received a probe from multiple directions?
One easy approach is to send the Loop trace back to the sender of the Probe message that triggered it.
And when forwarding a Loop trace, there will generally only be one from of the Probe...

I'll draw some diagrams with Flood-Pin-Trace in different colours to see if this works.

@michielbdejong
Copy link
Contributor Author

Don't skip the PIN!

FLOOD may find a loop in a P shape, where the origin is not on the loop.
Sending a PIN back, it will spread along both directions of the FLOOD, and ensure that when that loops back, it's a single-direction loop.
Then the TRACE can go into the opposite direction to single out the right branch of the PIN tree.

@michielbdejong
Copy link
Contributor Author

Reusing this design for Butterfly

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