Yes, it is. It seems like NI is not interested in keeping LabVIEW up to date with respect to networking. You would think they would be all over this given IoT, which is directly in their market space. Maybe they think all those remote sensors should just transmit everything in the clear. Very displeased with NI's lack of action in this area.
Mark Yedinak Certified LabVIEW Architect LabVIEW Champion
"Does anyone know where the love of God goes when the waves turn the minutes to hours?" Wreck of the Edmund Fitzgerald - Gordon Lightfoot
Earlier this year I talked to Pedro Vargas, Field Engineer from National Instruments in my area, regarding our concern about the lack of support with things like you guys have mentioned in this thread.
His response was that maybe our company was better with something like Python for our "small" projects.
Quite frustrating for us to hear that, but maybe he was right. After more than 10 years renovating our LabVIEW licence every year, being a certified developer for some time myself, investing resources developing the missing libraries we needed (like COAP, MQTT and others), getting excited about LabVIEW NGX, out of frustration, we finally decided to move our software assets to a Python based framework.
It may take us the rest of the year completing a comparable library, but we are starting to feel again that we have a tool that help us to deliver solutions. The reason I had two decades ago when I decided to learn LabVIEW.
During webinar about what's new in LabVIEW 2020 and NXG 5.0 I asked a question about future support for IPV6 in LabVIEW/NXG. This is the answer I received afterwords:
"As far as IPv6 support in LabVIEW, it’s currently in our backlog but not prioritized. So it’s a possibility that it will get introduced in a future version of LabVIEW. At the moment for LabVIEW NXG we do not have IPv6 on the roadmap. That can always change if we get enough feedback that the support is needed."
So, I guess there is no reason to expect NI support for IPV6 for the next years to come.