My parents have Planet Networks service in Vernon, NJ. I recently installed a Unifi Dream Router 7 on their network (so I can remotely manage it). The router says IPv6 is available. I turned on DHCPv6 on the WAN side but nothing is happening. The router is seeing an IPv6 router advertisement (says it's a /64 but the prefix given looks like a /48). Do we need to contact Planet Networks to enable IPv6? Does Planet Networks use SLAAC or another method for IPv6? Is Planet Networks working towards IPv6 but not there yet?
Do you all actually follow BCOP-690 and give /48 persistent ia_pd to eyeballs? I'm impressed if that's true. I have some ISPs in the USA under my management where we do the same; everybody gets a /48 persistent ia_pd, take it or leave it.
Although RIPE-690 says to not assign anything longer than a /56 to customers, we assign a /62 to each customer. That's 72 quintillion addresses - a massive number and natively gives each customer four /64 blocks for any internal subnetting they would like. I've been around long enough to remember when people handed out /24s and /20s like candy and we always said we would never run out. We did. We have two /32s and a /36, but I've been traumatized by running out of IPv4 so many times so I try to not "waste" IPs. :)
A /32 will only provide /48s to 65,535 customers so when everyone adopts IPv6 universally, we would burn through our allocation right away. We can serve 1.048 million customers from a /32 before we run out of /62s.
All of our customer Kontron and eero routers support IPv6 natively and everyone we provide equipment for is automatically setup as dual stack. Over time, this will only increase.
We do minimum /28s per ORG ID at RIR level and give /48s to every customer. IPv6 isn't about number of addresses (that's IPv4), it's about number of /64s segment available for use. Customers are adopting RFC9663 in the home (based on software support on their CPEs) for /64 per endpoint especially with namespaces on Linux/Android.
We additionally do /60 per endpoint in 802.11 campuses/MDUs in the USA.
We already see tens of thousands of endpoints pulling a /64 (or /60) at scale in the USA alone. That number is far larger if I include other networks across 5 continents under my management.
The basic mathematics of IPv6 when it was created was/is /48 per human alive. Meaning it's insanely large and by the time it runs out we'd have a new technology replacing it. Because IP just sucks for scaling (see how they do GPU networking at insane performance constraints).
Finally a /62 isn't even nibble bit boundary aligned. Very strange decision.
Feel free to DM me, if you'd like professional assessment. You can look me up, I'm involved with IPv6 from ISP to DC to AI fabrics to IETF mailing lists to ARIN PPML and APNIC.
It's actually kind of hard to change a brownfield IPv6 network if we want to maintain hierarchical aggregation of routes in the FIB in your internal network devices. But it can be done via phased migration.
We do not want to kill your BNGs and Spine/Leaf fabric TCAMs with IPv6 at scale in the future when you have tens of thousands of routes in the internal network.
We have a holddown aggregate route for the larger block per POP so a /32 or /36 would be assigned per POP. We can ask ARIN for a larger IPv6 assignment so we can have a /32 assigned per POP. /36 would work for now, but some of the larger ones are approaching 8,192 customers and having to use two /36s or later renumbering into a /32 and disrupting 8K customers isn't a good idea. I appreciate you reaching out and making me dedicate some brain cycles to this issue.
I wouldn't do /36 "holddown" like that; get a /28 and subnet into /32s per SUPER parent functionality; the backbone is diff. from the customer PtP and customer-routed prefixes (/48) are entirely different blocks as well.
The "holddown" will vary based on purpose essentially, and for Americans, I usually do USA-Wide subnet plan from day one. I do the aggregation in a way that allows the network operator to inject SR-TE/EPE policies easily as and when they need it.
A portion of our existing /32 is for internal PTP links and hosts. Definitely warrants a bigger conversation. I requested a larger block from ARIN. Let's see what they say. That will determine what we can do.
As a follow up to everyone, working with Planet Networks to figure this out. The UniFi router is sending out DHCPv6 Solicit messages but not seeing the Advertise message back although PN seems to be sending it. Still troubleshooting but something going on between their DHCP relay and the router.
1
u/jimjim975 17d ago
Call planet and ask them.