Earlier quoted context omitted.
How do you do that? I'd like to buy one.
You need to buy a minimum of /24
[deleted]
AWS IPv4 Estate Now Worth $4.5B
281–290 of 480 posts
Re: AWS IPv4 Estate Now Worth $4.5B
#282Earlier quoted context omitted.
These arguments always boil down to these two: "Please just try to fit more than 4 billion numbers into 4 bytes" -- this is mathematically impossible. "Just extend the address size" -- this is an entirely new protocol by the definition of IPv4, which uses fixed-size addresses. The reason for the slow IPv6 adoption is that there was no financial or business pressure. While IPv4 is ubiquitous, nobody individually feels…
There was a third option: make the existing IPv4 space a hierarchically routed island of the new IPv4.1 space, with backwards compatible packet format, then upgrade just the endpoints in the first phase. So every owner of a ipv4 would get, say, an entire 32 bit space that routes over existing IPv4 infrastructure . So, if the endpoints are upgraded, you have guaranteed end-to-end deliverability without silly hacks suc…
This is exactly how NAT64 works, and still doesn't solve the problem of IPv4 clients trying to connect to servers with only IPv6 addresses.
The backwards incompatibility is irreducible, inherent to the special place of Layer 3 in the networking stack.
Re: AWS IPv4 Estate Now Worth $4.5B
#283Can we go back in time and hit the designers of IPv6 upside the head? The decision not to make IPv6 backwards compatible, the belief that a beautiful new standard could magically replace something already so widespread... "Naive" is an inadequate word. We are still futzing with the transition 3 decades later, with no end in sight. Grrr, grumble...
IPV6 adoption reminds of the whole Python 2=>3 fiasco except it is much much worse.
Re: AWS IPv4 Estate Now Worth $4.5B
#284IPv4 is the new Bitcoin.
Re: AWS IPv4 Estate Now Worth $4.5B
#285Earlier quoted context omitted.
Yeah, one example is Cloudflare and 1.1.1.1; though the story behind that is less about money and far more interesting. Apparently, APNIC had owned 1.1.1.1 for, basically, forever, but were never able to actually use it for anything because it caught so much garbage traffic. Cloudflare is one of only a handful of service providers that could announce the IP and handle the traffic; so in exchange for helping APNIC's r…
So, what happened to everything that expected 1.1.1.1 to error out and now is getting something? (not worried about them, just curious)
Yeah it broke my use case. I used to run `curl --retry 9999 http://1.1.1.1` and since it didn't exit, the heat generated by the running curl process kept me warm in the winter. But now http://1.1.1.1 returns immediately, so I'm freezing!
Re: AWS IPv4 Estate Now Worth $4.5B
#286Earlier quoted context omitted.
> The problem isn't ipv6 (even with the tons of extra features that ipv6 forces upon you) The year is 2023, The chromium engine is full blown operating system, it has notifications, background task management, GPU acceleration for general compute, it's larger than Windows XP, and can in fact run windows XP in the browser. Teams consumes 500 mb of ram to do the same job ICQ did in 2002 with 5 mb of ram. Cars have 4G,…
> But Ipv6 features take a few extra bytes and are a problem. Some people pay for each extra byte they have to send through a network, and design whole systems around the goal of minimizing the amount of data they ship around. No one pays for the extra free gigabyte that Chrome takes over.
This concern about an extra few bytes is substantial in approximately zero organizations' IPv6 adoption decisions.
Re: AWS IPv4 Estate Now Worth $4.5B
#287Earlier quoted context omitted.
Everyone is always quick to complain that we're going through N number of NAT gateways or N number of proxies, but this is virtually never a problem for most of the Internet. Even despite this rats maze of proxies and NAT gateways we're still supporting virtually all the applications that consumers use and love such as VoIP, WebRTC, HTTP(S), DNS, Gaming, Streaming Video, Mobile Apps, etc. NAT seems to always get a ba…
>Even despite this rats maze of proxies and NAT gateways we're still supporting virtually all the applications that consumers use That's a tautology: "Despite the limitations of IPv4, we're still supporting all the applications that can work within the limitations of IPv4". Lots of potential P2P applications (that might solve a lot of problems with have with the current centralised model of the internet) either don't…
> I think there would be many more that wanted this if it were trivially easy to do
I've seen figures from proponents of Future Internet Architectures such as Named Data Networking claim that consumption is about 80% of Internet traffic. The truth is not everyone needs a Internet addressable host, mobile phones for example don't. And well, we're living in this situation today with CGNAT and you don't hear complaints from customers about not having Internet addressable IPs.
> What's the sacrifice in using IPv6?
Support. Enabling IPv6 on broadband consumer networks, small medium businesses, etc. means that you have to support the various devices v6 stacks and applications and ensure they continue to work just as well as they did with IPv4. IPv6 can still cause damage and the ability to support and fix these issues throw out virtually all incumbent knowledge.
If it were really just a "flip of a switch", everyone would've done it by now.
Re: AWS IPv4 Estate Now Worth $4.5B
#288Earlier quoted context omitted.
This is even better: game.latticeanimal.net. 3600 IN A 1.2.3.4
I don't know a single gamer who rented a domain for private use. In fact, I would argue than the hassle of setting one up is the reason why Hamachi got popular back then. You don't have to bother with knowing any technical stuff, just download a software, share a code and play.
People used to use https://www.noip.com/ and similar services for this.
Re: AWS IPv4 Estate Now Worth $4.5B
#289Earlier quoted context omitted.
Fitting more than 4B numbers into 4 bytes is mathematically impossible, but building a backwards compatible and easier to integrate standard may not be. Take USB for example. The capabilities of USB 3.1, 3.0, 2.0 is impossible to achieve for USB 1.0. So is high-speed charging. However, the end-user experience is generally pleasant, nitpicks around some of USB-IF's specific choices aside.
IPv6 is backwards compatible. In multiple ways: Option 1: "6to4" https://en.wikipedia.org/wiki/6to4 Option 2: "nat64" https://en.wikipedia.org/wiki/NAT64 + DNS64 Option 2b: "nat46" (which makes a few ipv6 hosts available over ipv4 if yo ulike) Option 3: "Teredo" (also known as "6in4" "tunnel broker" "6over4" "tunneling" ...) https://en.wikipedia.org/wiki/Teredo_tunneling Option 4: 6rd https://en.wikipedia.org/wiki/IP…
RFC1726 Technical Criteria for Choosing IP The Next Generation (IPng)
Section 5.5:
CRITERION
The protocol must have a straightforward transition plan from the current IPv4.Re: AWS IPv4 Estate Now Worth $4.5B
#290GitHub.com still doesn't support IPv6. I know that there is some work going on to support it, but this shows that it is far from trivial.
Hacker news also does not support IPv6