25 Apr
2014
25 Apr
'14
4:02 a.m.
On Thu, Apr 24, 2014 at 6:51 PM, Don Fanning <don(a)00100100.net> wrote:
No, I mean BGP out to the Internet, not to private peer relationships.
Once a 44.x.x.x subnet is routable to the Internet, it is routable to
all other 44.x.x.x subnets that also have access to the Internet.
There really would only need to be a few BGP (border) nodes and they
would most likely be routers, like CIscos or Mikrotiks (higher end
units). Those routers would provide tunnels whether IPIP or VPN out
to subnets in the 44.x.x.x space and route traffic for those subnets
both to other 44.x.x.x subnets or the Internet in general.
For example this router http://routerboard.com/CCR1009-8G-1S has a
level 6 license, which means it has no license limit on the number of
VPNs/Tunnels it supports. Depending on traffic and ingress/egress
bandwidth it could probably support many /16 vpns. In turn, a local
network would be able to run a modest router, e.g.
http://routerboard.com/RB750GL and in turn route to upto 200 smaller
VPNs/Tunnels. For reliability the border nodes might multi-home their
subnets at 2 or more data centers.
44.x.x.x is part of the Internet's addressable space. If we don't use
it in that way, we may as well turn it back and just use 10.x.x.x
I guess you could if you
wanted to but the 2 protocols have extremely different uses. Use BGP to
connect with one or more network service providers where you then bring
your own address space. Use GRE to build tunnels into those networks.
once BGP peered to the internet cloud, let the cloud do the routing and
delivery between networks for you.
I think John means this would be a private BGP and AS and not something
requiring something from IANA/RIR's. You would still need a tunnel back to
a master hub to get GRE tunnel information via NHRP as that information
isn't obtain by BGP magic.