I was hoping with IPv6, getting an address space as an individual would go back to how it was in the early IPv4 days, but alas you need to be a multihomed individual with tons of usage instead of just a sophisticated netzien that wants to own their block.

▲

dogcow 6 hours ago | parent | next [-]

Yes, same here. Very frustrating. It is almost as if the powers that be don't want lowly netizens controlling their own destiny.

▲

direwolf20 6 hours ago | parent [-]

Actually, they don't want to pollute the internet routing table with routes that are fully subsumed into other routes. The effect on address ownership is a side effect.

▲

zhouzhao 5 hours ago | parent [-]

Actually, they just want to milk the money out of you. It's a matter of how much your willing to pay, as a business customer, it's all possible.

Most ISP do not have such pure goals, as to protect the global routing tables ;)

	▲	direwolf20 5 hours ago \| parent [-]
		RIRs, not ISPs, allocate addresses at the top level, they make money on each address allocation, and they still won't allocate addresses to you if you don't multihome because they have a duty to conserve resources. When you get PI addresses your LIR/ISP just passes your data on to the RIR.

▲

dietr1ch 4 hours ago | parent | prev | next [-]

I don't want an address, they should be cheap, meaningless (sans routing, the longer the common prefix, the closer geographically you should be) and not conflated with identifiers.

I just want a way to do public-key based discovery. I'm not sure if wireguard + DHT would do though as it'd also mean that it's easy to track your PK (and maybe you through your devices/services announced with PKs).

Maybe you can announce your IP in a neat encryption scheme that adds some privacy without increasing costs too much?

	▲	direwolf20 4 hours ago \| parent [-]
		Basically Yggdrasil?

▲

nine_k 5 hours ago | parent | prev | next [-]

What is the point of owning public address space?

Anything in your private network (even if it goes over public internet) should be encrypted and locked up anyway. Something like Wireguard or Nebula only needs a few (maybe just one) publicly accessible address. Inside the overlay network, it's easy to keep IP addresses stable.

Anything public-facing likely needs a DNS record, updatable quickly when the IP of a publicly accessible interface changes (infrequently).

What am I missing?

▲

direwolf20 4 hours ago | parent | next [-]

The realistic point is to have your own abuse email contact, to evade the banhappy policies that most server hosts have even when you did nothing wrong. Usually they suspend your account if you don't reply within 24 hours, even if the complaint is obvious nonsense.

▲

cyberax 3 hours ago | parent | prev | next [-]

It's the only real way of running reliable IPv6 networks with multiple uplinks. Unless you want NATv6.

▲

kortilla 3 hours ago | parent | prev [-]

DNS updates are slow. BGP can react to a downed link in <1 sec.

	▲	zamadatix 9 minutes ago \| parent [-]
		I have both my own multihomed ASN and operate my own nameservers. The latter has usually been about as fast for failover overall in practice. BGP may look to converge near instantly from your 2-3 peer outbound perspective but the inbound convergence from the 100k networks on the rest of the internet is much slower and has a long tail very akin to trying to set your DNS TTL to 0 and having the rest of the internet decide to do it slower for cache/churn reasons anyways.

▲

seszett 4 hours ago | parent | prev | next [-]

Honestly it's not free but it's really not that expensive. With RIPE it's about 75€ per year for the ASN and being multihomed is not really a problem, there are multiple services that will let you announce through them for free or very cheap. You don't have volume minimums.

I do agree it should be simpler, but it is accessible to individuals today.

▲

zhouzhao 6 hours ago | parent | prev | next [-]

I feel you. Us nerds have been ignored by modern day home user contracts.

▲

7 hours ago | parent | prev [-]

[deleted]