Why does it all start with "2"? e.g. 2000 -> 2f00? Where are the other prefix segments?
As yet unissued, according to the page.
Posters of the IPv4 and IPv6 internet as of Jan 1, 2023
71–80 of 104 posts
Re: Posters of the IPv4 and IPv6 internet as of Jan 1, 2023
#72The ghostly amount of v6 space is so exciting to see. One day we’ll need to physically route a whole block to another planet — there’s no point using BGP when the ping from Earth to Mercury is 230,000ms at best. I love IPv6 and it’s so exciting to see it used widely at last. My mobile device is v6 although it’s still dual stack. Home networks are doomed to by v4 forever so your 1990s eToaster can display Yahoo! News!…
> Home networks are doomed to by v4 forever
Why? I've had dual-stack at home for many years, and I can hit sites via IPv6-only: way back when, I blocked Facebook connectivity for privacy reasons, but at some point I noticed I started getting those little FB icons again that came directly from their servers. Turns out that I was hitting them via IPv6 and had to update my (DNS filtering) rules to block AAAA records as well.
Even my not-very-new Brother HL-L2360 (running firmware from (AFAICT) 2015) supports IPv6, and has both a fe80 link-local address, and a 'proper' address that it got via a prefix advertisement from my Asus router.
Most IoT devices run Linux under the hood and get IPv6 support 'for free'.
Re: Posters of the IPv4 and IPv6 internet as of Jan 1, 2023
#73Earlier quoted context omitted.
They don't need to buy as expensive cgnat hardware if a greater proportion of traffic is ipv6. That's the rationale given by an up-and-coming ISP in Australia.
Still need CGNAT for Dual Stack - Lite. Or, a NAT for 464Xlat.
Video is by far the largest bandwidth hog that most people use, and both Google/Youtube and Netflix support IPv6 for streaming last time I checked. The more traffic that supports IPv6, both from the client- and server-end of things, the less horsepower that the CG-NAT boxes need for network processing (and for things like logging of connection mappings for mandated law enforcement purposes).
There is certainly an upfront cost of getting IPv6 going for a 'legacy' ISP, but once the infrastructure is there it can reduce the ongoing costs of CG-NAT (because IPv6 will just be part of the fixed costs that you need/have anyway to be an ISP).
Re: Posters of the IPv4 and IPv6 internet as of Jan 1, 2023
#74Why does it all start with "2"? e.g. 2000 -> 2f00? Where are the other prefix segments?
> Where are the other prefix segments?
Currently not needed.
The IETF/IANA folks were a bit cautious, so only 2000::/3 is officially designated to be assigned. If, a few years down the road, they find out that a mistake was someone made in address allocations, they can then 'start over' from the lessons learned, and start assigning things from 4000::/3.
If they made a mistake again, they can start over again with 6000::/3. And then 8000::/3, a000::/3, and c000::/3.
* https://www.iana.org/assignments/ipv6-address-space/ipv6-add...
So that's why all global unicast addresses start with 2: they're to be 'conservative' in what is usable so that if there are problems there is room for corrections in the coming years/decades/centuries.
We don't want to have to go through another IP protocol transition.
Re: Posters of the IPv4 and IPv6 internet as of Jan 1, 2023
#75Earlier quoted context omitted.
> get static IPv6 addresses instead of a dynamic one behind an ISP NAT. Some UK ISPs give out /48s (cough Sky) but with dynamic allocation. So you reboot your router and every single IPv6 device on your network needs to re-address. Makes routing/port forwarding a PITA and nearly impossible using IPv6.
Even if it was static changing the ISP will result in a new public range, meaning an internal re number, unless you use NAT, in which case you may as well use ipv4 and nat. If you have two ISPs (say a backup 5G) then you have to renumber every time the main goes down. If you want to load balance you’re screwed, unless of course you use nat. Residential ISPs won’t allow you to bgp peer your own /48
> Even if it was static changing the ISP will result in a new public range, meaning an internal re number, unless you use NAT, in which case you may as well use ipv4 and nat.
Kind of: if you use IPv6's ULA (fc00/7 [1]), then you can have a NAT-like translation layer using NPTv6 [2]. The advantage of NTPv6 over NAT44 is that you get an entire prefix to play with instead of a single IP on your router's WAN interface.
If you wish to have multiple services (web, SSH, Minecraft), then with IPv4 hole punching you can only have one server on the default port and the second system with the same service needs to be on a different port. With IPv6/NPTv6 you can have each service on a different IPv6 address and live on its default port.
You also have the flexibility of either only allowing one particular port in for that service/IPv6 address, or just allowing all traffic in without any firewalling/filtering.
So NPTv6 is no worse than NAT44 in the simple cases, but also has extra functionality over it.
[1] https://en.wikipedia.org/wiki/Unique_local_address
[2] https://en.wikipedia.org/wiki/IPv6-to-IPv6_Network_Prefix_Tr...
Re: Posters of the IPv4 and IPv6 internet as of Jan 1, 2023
#76IPv6 is handed out using sparse allocation inside /12 from IANA ensuring two goals: minimal recall on IANA and maximum utilisation inside each /12 preserving second call headroom for the original delegates announcing the space in BGP. They can take a /32 to a 31 or 30 or 26 or whatever and not have to announce disaggregated blocks in BGP. (They can disaggregate, but it's not forced by being given discontinuous blocks…
As an example of how big ipv6 is, we got a /29 from ripe at a not very big at all ISP, which even if we had handed out a /48 to each and every DIA customer physical location/cpe, would have lasted us at our projected growth rate for the next several hundred years. And that was in addition to the ARIN /32 we already had.
I've got my own homelab /44 prefix for only 15€/yr. /48 would have been fine too, but /44 was the smallest they had.
Re: Posters of the IPv4 and IPv6 internet as of Jan 1, 2023
#77The ghostly amount of v6 space is so exciting to see. One day we’ll need to physically route a whole block to another planet — there’s no point using BGP when the ping from Earth to Mercury is 230,000ms at best. I love IPv6 and it’s so exciting to see it used widely at last. My mobile device is v6 although it’s still dual stack. Home networks are doomed to by v4 forever so your 1990s eToaster can display Yahoo! News!…
My ISP to this day still doesn't have dual-stack. It makes a 6rd tunnel available to their users as a "beta" (for years). I find it mystifying to be honest. I know for a fact they have a nice modern facility and an expert head sysadmin. They even have a local fiber optic network. It makes no sense to me that they're clinging so tightly to IPv4.
I too am waiting for Sonic Fiber to finally get native IPv6. Luckily, they finally started rolling it out in some cities.
Re: Posters of the IPv4 and IPv6 internet as of Jan 1, 2023
#78Earlier quoted context omitted.
Rollout isn’t a problem for anyone it’s when services start to become unaccessible to IPv4 but accessible on IPv6 end users can get marginalized. We’re still many years from that though which greatly amplifies how much an issue it’ll actually still be when that time comes.
Rollout is still pretty slow: https://www.google.com/intl/en/ipv6/statistics.html#tab=ipv6... But services supporting it is the other side of the problem. Both need to be addressed.
Wow. Sweden is disappointing.
Re: Posters of the IPv4 and IPv6 internet as of Jan 1, 2023
#79In considering the rollout of IPv6, end users often get marginalized. This is frustrating to me. When we try to highlight ISPs who refuse to deploy IPv6, mobile services get highlighted - as if homes and businesses could just use them instead of wireline. If that doesn't end the discussion then IPv6 acolytes will go on about transit traffic or anything else until IPv4-only users go away and stop ruining their optimis…
It even happens to ISPs themselves to get marginalized in this way. I work in a small local ISP, and we're fully IPv6-ready, but the publicly funded optical networks we use to reach our clients are not IPv6 ready. It should just be a simple VLAN, transported how they please, that connects us to our client, but no, the infrastructure operator built a mess just to connect us to our clients, I suppose just transporting a VLAN was too simple for them (we do get a VLAN, but they do some weird DHCP interception on it, and dynamically route IPs in their iBGP based on that, and didn't set it up for DHCPv6, so no IPv6 for our clients).
This is one of the biggest FTTH networks in France, where IPv6 is deployed a lot.
Of course, the bigger operators can collect their traffic straight at the OLT, so they don't have to go through this mess, and get better quality of service (the DHCP interceptors fail often) as well as native IPv6.
We small operators need to set up tunnels to provide IPv6 to our clients. Even for additional IPv4s or just anything bigger than /32 we need a custom tunnel. And these tunnels are a mess to manage when the customers have their own CPE. It's so sad, and that's all done with public money.
And yes, of course, this infrastructure operator, Covage/XPFibre is owned by Altice, who also owns SFR, one of the big four operators. How surprising.
Re: Posters of the IPv4 and IPv6 internet as of Jan 1, 2023
#80Serious question: why would I want to purchase this as a poster? Asking as a nerd, but maybe not a very specific data oriented nerd.
For decorative purposes. Just like having a globe or a map.