the backbone is the POP ardc are proposing to build.
________________________________________ De : 44Net 44net-bounces+petem001=hotmail.com@mailman.ampr.org de la part de Rob PE1CHL via 44Net 44net@mailman.ampr.org Envoyé : 11 août 2021 04:50 À : 44net@mailman.ampr.org Cc : Rob PE1CHL Objet : Re: [44net] A new era of IPv4 Allocations : Agree
On 8/11/21 10:20 AM, Toussaint OTTAVI via 44Net wrote:
Dual addressing may be complicated now because some 44.x subnets are annouced on BGP while some others are not, because some people are not aware about the fact they must route 44.190 differently, etc...
The purpose of the TAC proposal is to simplify things by splitting / grouping networks into two big subnets, with just two "parent" routing policies.
Yes, but it is a solution that cannot cover every case and it causes a lot of work for lots of people who are not involved in this artificial problem at all.
For a user, it should not matter if a subnet is announced on BGP. They just connect to a next hop in the network which knows about that.
There should be a backbone network which, just like the current IPIP mesh, knows how to route everything. But, it should be easier to access than the IPIP mesh. So everyone can use it, not only those with a fixed internet IP and router that can pass IPIP, and a lot of technical knowledge to debug issues. Therefore tunneling technologies that work over typical ISP NAT routers should be used.
Then these users can send all 44-net traffic which they cannot route locally into that backbone network, and that backbone will know if it is a destination that it can route via a tunnel (similar to IPIP) or if it has to route it to internet. There even could be some option for users to register on the backbone net whether they want their traffic to be only routed to tunnels or if they also want to route to internet. If not, the traffic would be dropped. That would be for the "intranet" advocates.
For a long time now, everything has worked perfectly for those users who announce on internet BGP and do ALSO register on the IPIP mesh. They know how to route to other IPIP mesh members via a tunnel and route the remainder to internet. They are reachable for everyone that has sane routing.
The "problems" that are sketched here do only occur in networks who choose not to do that. That is a design issue. It can be easily solved especially when the new backbone network is present that can do BGP annouces itself, so it is completely transparent to the users if each subnet is on the tunneled network, or on a 44-net subnet only announced on internet. It will always be routed correctly without the operator needing to set separate routes.
Rob _________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net