Apply for public IPv4 and IPv6 address ranges
At some point, I would like us to be a functional cloud provider (properly this time). One of the major features we lack in order to do this is a public subnet we control.
Pay the fees and apply for address ranges, become an autonomous system and pray to whatever gods exist that we actually get some v4 subnets, then convince the LKW01 facillity to do peering with us so we can BGP our problems
into the sun outside of sol.
from what i remember, requesting an ASN or ipv6 alloc requires intent to multihome. does LKW01 facility give us the option to peer with more than just one other AS? if not, we may want to consider a direct ipv6 delegation from LKW01. if yes...
would we be requesting an ISP or end-user allocation? do KCRL users count as "employees" or "customers"? standard ISP alloc is ipv6/32, standard user alloc is ipv6/48...
or, would we be requesting a community network allocation? relevant ARIN policy: §6.5.9, §2.11. kcrl might stretch the definition a bit but i'd argue we do provide low-cost access to a form of connectivity.
ASN definitely doesn't require intent to multihome. We'd just be a class 2 AS, which is fine? Currently we would only peer with Speed Bird, though they don't actually have peering negotiated with their ISPs at the moment.
End users would count as customers, I believe. We'd also have to actually like, incorporate I guess, which begs the question of how we'd classify you, @barrow, but that's a question we can figure out by the time we cross that bridge.
We can solidify this plan as we get closer to like, doing this stuff. Its gonna be probably a bit though, especially given we are all under financial constraints at this moment (setup donations page when?)
Anyway, if we do this we need to have KCRL making enough money to sustain itself. If we never get to that point, then this can be marked as "wontfix" and we'll move on. 😄
Deleting a branch is permanent. It CANNOT be undone. Continue?