Yeah, hobbyist niche sites like these: https://clintonwhitehouse1.archives.gov/ https://clintonwhitehouse2.archives.gov/
Backward compatibility was never really the problem; the problem is that forward compatibility with ANY successor protocol (without modifying IPv4) is a fundamental impossibility. But at least a reasonable facsimile…
Additionally, their fixed-wireless product gives you a physical CPE that does the CLAT (NAT46) side of the 464XLAT. To the local network, it looks like there's native IPv4, but it's translated to IPv6 by the gateway,…
2.7 - 4.0 years, by my math, so I would agree with your assessment. ...but that's based on pre-IANA-runout rates, though, and doesn't account for the pent-up backpressure of demand. So probably a lot less, in reality.…
Anyone who's ever had to delegate DNS authority on anything other than an 8-bit boundary can understand the value of that feature. At face value, yeah, that's replacing "8" with "4," but from a practical perspective,…
This is pretty remarkable, given that RFC 1883 is only 30 years old.
This. "Vibes," vs. data.
It officially started becoming scarce in 2011, when IANA, and then APNIC, depleted their IPv4 "free" pools, FWIW. Things have only gotten worse from there. Cloud computing doesn't mitigate IPv4 issues, it just moves it…
> And if I'm reading the ARIN fees correctly, it only costs $4000 annually for a "/16" allocation: For better or worse, you're not; that's for IPv4 /16. For IPv6 /16, it'd be the X-Large service category, so…
I have been working with IP based networks for over 20 years, and specifically IPv6 networks for over 17 of those. IPv6 is the main reason I got my current job, FWIW. > The use of NAT64 is helping many organisations to…
That's another benefit of https://stats.labs.apnic.net/ipv6/ -- the tables, including down to ASN.
https://labs.apnic.net/?p=479 https://labs.apnic.net/?p=655 From what I've gleaned, the use of Google ads catches the use case of people who don't actively use Google -- based on the delta in metrics between Google's…
Just to warn you, even on T-Mobile, not all hotspot devices support IPv6 (either by default or at all). I forget if inbound connections work, though.
- APNIC ran out in 2011, but has a new-LIR pool remaining - RIPE ran out in 2012, but has a new-LIR pool remaining (part of which is that /8 you mentioned) - LACNIC ran out in 2014, but has a new-LIR pool remaining -…
I'd half agree with this; for those who are actively working on this, yes, the low-hanging fruit are all done, but there's still plenty of low-hanging fruit in organizations where no one's bothered to pick them.
a) It's a translator, not a tunnel. b) You're ultimately still right that it enables connectivity to IPv4-only resources, but depending on the IPv6 client device, you may NEED to use a DNS 'A' record to get the traffic…
> With IPv4 my ISP has to shuffle IPs with every reconnect. With IPv6 you could get one IP for lifetime? In theory, yes; in practice, most ISPs will give you a new prefix via DHCPv6-PD anytime your DUID changes (plus…
As mentioned/hinted by ancarda: a) You missed Belgium. (Common oversight, due to the size on the map.) b) Google's stats have something of a US-centric bias; https://stats.labs.apnic.net/ipv6/ is a little less biased…
As others have said, most major operating systems implemented RFC4941 (IPv6 Privacy Extensions) years ago. Unless you're using unmaintained OSes (in which case you shouldn't be complaining about security), what privacy…
In 2005 or so, sure. Now...not so much? What privacy erosion/easier tracking are you talking about that wasn't remedied by the very wide deployment of RFC4941 (IPv6 Privacy Extensions) in operating systems?
Any word on IPv6 support?
Yeah, hobbyist niche sites like these: https://clintonwhitehouse1.archives.gov/ https://clintonwhitehouse2.archives.gov/
Backward compatibility was never really the problem; the problem is that forward compatibility with ANY successor protocol (without modifying IPv4) is a fundamental impossibility. But at least a reasonable facsimile…
Additionally, their fixed-wireless product gives you a physical CPE that does the CLAT (NAT46) side of the 464XLAT. To the local network, it looks like there's native IPv4, but it's translated to IPv6 by the gateway,…
2.7 - 4.0 years, by my math, so I would agree with your assessment. ...but that's based on pre-IANA-runout rates, though, and doesn't account for the pent-up backpressure of demand. So probably a lot less, in reality.…
Anyone who's ever had to delegate DNS authority on anything other than an 8-bit boundary can understand the value of that feature. At face value, yeah, that's replacing "8" with "4," but from a practical perspective,…
This is pretty remarkable, given that RFC 1883 is only 30 years old.
This. "Vibes," vs. data.
It officially started becoming scarce in 2011, when IANA, and then APNIC, depleted their IPv4 "free" pools, FWIW. Things have only gotten worse from there. Cloud computing doesn't mitigate IPv4 issues, it just moves it…
> And if I'm reading the ARIN fees correctly, it only costs $4000 annually for a "/16" allocation: For better or worse, you're not; that's for IPv4 /16. For IPv6 /16, it'd be the X-Large service category, so…
I have been working with IP based networks for over 20 years, and specifically IPv6 networks for over 17 of those. IPv6 is the main reason I got my current job, FWIW. > The use of NAT64 is helping many organisations to…
That's another benefit of https://stats.labs.apnic.net/ipv6/ -- the tables, including down to ASN.
https://labs.apnic.net/?p=479 https://labs.apnic.net/?p=655 From what I've gleaned, the use of Google ads catches the use case of people who don't actively use Google -- based on the delta in metrics between Google's…
Just to warn you, even on T-Mobile, not all hotspot devices support IPv6 (either by default or at all). I forget if inbound connections work, though.
- APNIC ran out in 2011, but has a new-LIR pool remaining - RIPE ran out in 2012, but has a new-LIR pool remaining (part of which is that /8 you mentioned) - LACNIC ran out in 2014, but has a new-LIR pool remaining -…
I'd half agree with this; for those who are actively working on this, yes, the low-hanging fruit are all done, but there's still plenty of low-hanging fruit in organizations where no one's bothered to pick them.
a) It's a translator, not a tunnel. b) You're ultimately still right that it enables connectivity to IPv4-only resources, but depending on the IPv6 client device, you may NEED to use a DNS 'A' record to get the traffic…
> With IPv4 my ISP has to shuffle IPs with every reconnect. With IPv6 you could get one IP for lifetime? In theory, yes; in practice, most ISPs will give you a new prefix via DHCPv6-PD anytime your DUID changes (plus…
As mentioned/hinted by ancarda: a) You missed Belgium. (Common oversight, due to the size on the map.) b) Google's stats have something of a US-centric bias; https://stats.labs.apnic.net/ipv6/ is a little less biased…
As others have said, most major operating systems implemented RFC4941 (IPv6 Privacy Extensions) years ago. Unless you're using unmaintained OSes (in which case you shouldn't be complaining about security), what privacy…
In 2005 or so, sure. Now...not so much? What privacy erosion/easier tracking are you talking about that wasn't remedied by the very wide deployment of RFC4941 (IPv6 Privacy Extensions) in operating systems?
Any word on IPv6 support?