Tony,
On 30.12.20 at 22:28 wrote Tony Langdon via 44Net:
...
Still have to find the /32 somehow. And I still see a
lot of suboptimal
routing happening here, unless there's some other protocol in the core
doing clever routing.
I absolutely agree! What I wanted to point out is that there might be
basically two expectations about 44 addresses. Topological routing as
you have pointed out is one of it.
Let me elaborate on the second idea: lots of isolated /32 hosts or /28
subnets: Sure, if I need to load the entire routing table to every node,
this will not scale. But a single node will not need the full routing
table typically. Only a few entries are interesting at a single time.
So if you have a dynamic lookup facility of the gateway address, you
could populate your routing tables on demand. This facility could be
realized by means of a distributed hash table, so there is no single
point of failure. And yes the optimal routing is done by the core
internet in such a use case.
But again this clearly is a different use than topological routing, and
it possibly would be a good idea to separate the IP address space
between such uses at a coarse level.
73 de Roland oe1rsa
--
__________________________________________
_ _ | Roland Schwarz
|_)(_ |
| \__) | mailto:roland.schwarz@blackspace.at
________|
http://www.blackspace.at