Re: IPv6 native percentage (end user perspective)

["Forrest Christian (List Account) via NANOG" <nanog () lists nanog org>]

Essentially labor (support) costs:

Training support staff on IPv6, including helping customers provision/use
IPv6.
Adding IPv6 to internally developed databases and provisioning tools.
Adding support to IPAM and our address-allocation and tracking tools to
support IPv6 (we are largely statically addressed to the customer for
historical reasons).
Configuring IPv6 across the network.
Troubleshooting/supporting two protocols that can break instead of one.

Many of these have become less expensive than before.  For example, 10
years ago, I would have added "upgrade all the gear that doesn't support
IPv6," but I think we're mostly beyond that.


On Fri, Jun 20, 2025 at 8:04 AM Tom Mitchell <tmitchell () netelastic com>
wrote:

> "Why bother adding the cost of supporting a dual-stack network when there
> is precisely zero cost for me to stick with IPv4? "
>
> What is the incremental cost?
>
> - Tom

-- 
- Forrest
_______________________________________________
NANOG mailing list 
https://lists.nanog.org/archives/list/nanog () lists nanog org/message/RXEIS3SQQ7Z5N3FUL5AFCEX22ZZN6NLE/