New subject: IPv6 adoption (was: address sale)

21 Jul 2019

...
   - I want to
make a 1:1 mapping of every assigned address in our IPv4
   subnet to a /16 network within that /48 space.
   E.g. when we get 1234:5678:abcd::/48 from our ISP, I would map
   44.137.0.1 to 1234:5678:abcd:0001::/64, up to 44.137.255.255 mapped
   to 1234:5678:abcd:ffff::/64  I'm a bit lost at what you're suggesting,
and the practical way it would
 be implemented.  At first glance, this looks like a recipe for
 suboptimal routing to the outside world. 
The above is an idea how to add IPv6 addresses to the 44.137.0.0/16 
network that
is BGP connected in a datacenter and where users are connected via VPN 
and radio
paths.  The added IPv6 addresses would be from the datacenter space and 
would be
routed along the same paths as the 44.137 traffic.  Of course that is 
suboptimal, but
it works for users that do not have IPv6 themselves.

...
  I have 2 AMPRnet IPv4 allocations - one BGP connected,
one IPIP
 connected.  Both sites have IPv6 available.  Here, where the IPIP mesh
 terminates has a /56.  I currently have a /64 on the VPS, but as there's
 only one host, it wouldn't be difficult to carve that into AMPRnet and
 non AMPRnet parts, because IPs are assigned by hand and are all on the
 same interface. 
In my opinion it is not a good idea to deploy a system based on 
splitting a /64 net
in smaller subnets.  You could do that locally, but you would not want 
to give other
local users an IPv6 network that is smaller than a /64.  This is going 
to cause all kinds
of difficulties.  That is why my intention is to give every user at 
least a /64.

Rob

Re: [44net] IPv6 adoption (was: address sale)