Live data from Hacker News

Update: Approaching IPv4 Run-out

ripe.net

121–130 of 140 posts

Re: Update: Approaching IPv4 Run-out

#121

Earlier quoted context omitted.

$ ip -4 addr show | grep eth0 # nothing $ dig news.ycombinator.com AAAA +short 64:ff9b::d1d8:e6f0 $ wget -6 https://news.ycombinator.com -O /dev/null Resolving news.ycombinator.com (news.ycombinator.com)... 64:ff9b::d1d8:e6f0 Connecting to news.ycombinator.com (news.ycombinator.com)|64:ff9b::d1d8:e6f0|:443... connected. HTTP request sent, awaiting response... 200 OK [...] ‘/dev/null’ saved [34663] WFM!

It's a translated with DNS64 ipv4 address into a NAT64 ipv6. They have 64:ff9b prefix.

Indeed it is, and it works fine. v4-only websites aren't a problem for running v6-only.

Re: Update: Approaching IPv4 Run-out

#122
post #30

Earlier quoted context omitted.

Instead of excluding CF, I'd like to see server stats weighted by popularity. I'd bet that the concentration of traffic to just a few mega-sites means most people can now get by just fine with IPv6.

You might be surprised. For reasons I can't begin to fathom, a coffee shop near me used to have its wifi router set up to only permit connections to external sites over IPv6. I was legitimately surprised at how many sites I couldn't access from there, including sites from Fortune 50 companies and big tech firms, who you'd expect to be among those who'd be on top of this sort of thing. (Including, ahem, HN.)

It's on our list. Hoping to get there soon.

Re: Update: Approaching IPv4 Run-out

#123
post #114

Earlier quoted context omitted.

Very few companies would need to decide to not interconnect with IPv4 networks before IPv4 was effectively dead. Typically, though, there's a process that they would go through before making that move. That's what I was asking about. Has anybody floated a date for IPv4 death?

Those very few influential people who make the decisions are incredibly conservative; they won't even kick criminals off the Internet without overwhelming evidence. I don't think they're even interested in discussing IPv4 sunset at this point. Rather than a date I think it would make sense to look at the traffic. When IPv4 hits, say, 1% it might make sense to turn it off. I would estimate that's decades away.

Google is one of those influential companies and I could totally see them declaring that their crawler is going to stop visiting IPv4 after some date.

Re: Update: Approaching IPv4 Run-out

#124
post #3

RIPE, there's this story of The Boy Who Cried Wolf. Would suggest reading it.

When did they cry wolf over this? They've made various announcements at each stage of running out, but this is the first time they've announced that they have more pending LIR applications than blocks to assign to them.

Yes, I remember the "Bring on IPv6" event when IANA ceremonially handed over the last IPv4 /8 to RIPE, at the TfL Museum, London in 2011.

Re: Update: Approaching IPv4 Run-out

#125
post #15

IPv6 worldwide adoption is at just under 30%: https://www.google.com/intl/en/ipv6/statistics.html If the current growth rate continues, it looks like it will reach 100% by about 2035.

Would love to see the time slider on the per-country adoption map.

Re: Update: Approaching IPv4 Run-out

#126
post #57

Earlier quoted context omitted.

I doubt that, but I think we're going to see more and more companies to sell off the unused blocks. Last year MIT sold off 1/2 of 18.0.0.0/8 to Amazon. It looks like the going rate per IP is between $20-$24 currently: https://auctions.ipv4.global/prior-salesw

That's a good point...further scarcity will drive the prices to a point where selling is very attractive.

It's a big gamble on when to sell though. Eventually IPv6 adoption will hit a critical mass threshold and interest in paying for IPv4 IPs will dry up.

Re: Update: Approaching IPv4 Run-out

#127

Earlier quoted context omitted.

It's a translated with DNS64 ipv4 address into a NAT64 ipv6. They have 64:ff9b prefix.

Indeed it is, and it works fine. v4-only websites aren't a problem for running v6-only.

I am now at home and tried your experiment but I have IPv4 as well as IPv6.

The wget forced to v6 does not work here. That's a bug somewhere. My eyes are no longer happy 8( ... 8) ... ahh, all OK now!

Re: Update: Approaching IPv4 Run-out

#128
post #114

Earlier quoted context omitted.

Those very few influential people who make the decisions are incredibly conservative; they won't even kick criminals off the Internet without overwhelming evidence. I don't think they're even interested in discussing IPv4 sunset at this point. Rather than a date I think it would make sense to look at the traffic. When IPv4 hits, say, 1% it might make sense to turn it off. I would estimate that's decades away.

Google is one of those influential companies and I could totally see them declaring that their crawler is going to stop visiting IPv4 after some date.

They would do that only once it costs them more money than they could make with the retrieved data. That's not going to happen anytime soon.

You might as well wonder whether google is actually going to stop crawling IPv6 addresses (are there any significant IPv6-only servers?)

Re: Update: Approaching IPv4 Run-out

#129
post #124

Earlier quoted context omitted.

When did they cry wolf over this? They've made various announcements at each stage of running out, but this is the first time they've announced that they have more pending LIR applications than blocks to assign to them.

Yes, I remember the "Bring on IPv6" event when IANA ceremonially handed over the last IPv4 /8 to RIPE, at the TfL Museum, London in 2011.

For comparison, ARIN went dry in 2015. RIPE had a rationing policy (one /22 per LIR) for that last /8, which is why it's lasted until now.
Post reply on HN