Of course you can sit and wait until IPv6 becomes critical to your business. But is it a good idea?
What makes good, or bad, configurables, how do I tell them apart and why should I actually bother to look?
Devices that are “user configurable”, “field/user upgradeable” and “microcontroller driven” may score with buzzword bingo, but that doesn’t necessarily mean that you may want to use them.
While sales people talk about the “Internet of Things”, “Home Automation” and “Industry 4.0” with growing desparation, people are widely reluctant to actually spend mony on them—and they actually have reasons to be wary. To make these ideas actually work, a number of things still need to be taken care of.
If you think that IPv6 had enough addresses to let you have some static ones for your home, then think again. After all, for the ISPs IPv6 is not about giving proper Internet access to people again, but about making money fast.
A sometimes rather emotionally discussed topic related to IPv6 address plans is wether to use Unique-Local addresses (ULAs) or not. As usual, the only “one size fits all” answer to that question is “it depends”; here are some of the criteria I found relevant.
With the subnet prefix part taken care of, this second part of the address concept “mini series” deals with the IPv6 interface IDs.
Devising an IPv6 address concept is fairly straightforward—if you know how to start and which pitfalls to avoid.
Running out of IPv6 addresses is simple: Encode whatever isn’t routing related in your IPv6 addresses and you will soon realize that 16 bytes of space don’t get you all that far.
If you think that the IPv6 address space is infinite for all practical purposes, then think again.