You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 14, 2021. It is now read-only.
I'm opening this issue to start discussing the way a TTN router will discover TTN brokers.
Current situation
Upon reception of a packet, a router either
Broadcasts a packet to all known brokers
Forwards the packet to brokers that previously accepted the devAddr (routing tables)
If rejected, then broadcast.
This system obviously isn't very scalable, because:
Routing tables will grow and become useless
Broadcasting to a couple 100s brokers is just insane
There are security issues (many possibilities of DoS)
Long term
For a long-term solution, we're working with a group of experts that will help us define a perfect solution.
Short term
For the short term, we need something that is better than the current situation.
Initial option to start the discussion:
Registry Service: Brokers register address range (prefix) with a TTN registry service, so routers only have to broadcast to a smaller number of brokers.
The text was updated successfully, but these errors were encountered:
I'm opening this issue to start discussing the way a TTN router will discover TTN brokers.
Current situation
Upon reception of a packet, a router either
devAddr
(routing tables)This system obviously isn't very scalable, because:
Long term
For a long-term solution, we're working with a group of experts that will help us define a perfect solution.
Short term
For the short term, we need something that is better than the current situation.
Initial option to start the discussion:
The text was updated successfully, but these errors were encountered: