23 Jul
2019
23 Jul
'19
8:43 a.m.
BGP is a signaling protocol which does not carry any traffic, while
BGP44 is suggesting otherwise. Essentially its just a regular BGP
network. If you are doing this the BGP way, you'll still need to use
ASNs, private or public, and use maybe roa to authenticate the source of
the prefix, i.e., someone with 44.1.1.0/24 may fat fingered to
44.21.1.0/24.
It looks like you are making something like dn42[0] but with public IP
space.
Q.
--
[0]: https://dn42.net/home
On 7/23/2019 8:22 PM, Rob Janssen via 44Net wrote:
That is true,
but only if we are the only ones using private ASNs.
But if happens that some people already uses private ASN for other
purpose, they would be in trouble connecting to 44net... because there
would be collisions.
I see no point of using public IP addresses and route them using private
ASNs. It may be that I do not understand BGP well.
It is important to note that
the routing in this overlay network,
let's call it BGP44 from now, is running as a separate BGP instance
that is not combined with BGP announcement to internet or private use
of BGP. The BGP44 instance will only distribuite the routing info
for AMPRnet subnets, similar to what is now in the IPIP routing table.
Also, even though there could theoretically be collisions, in practice
there is not much risk because there are 94,967,295 available AS numbers
in the space that we use. That is 8 times more than the number of IP
addresses we have left.
Rob
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net