In current implementation of WSDiscoveryServiceImpl, endpoint is published with hardcoded IPv4 multicast address:
There is no reason to support only IPv4. Also current implementation does not support WS-Discovery in IPv6 network when IPv4 is not available at all.
Programatically determining network environment and switching the profile might not be the best option (network might be temporarily at the moment of trying down etc.), so at least I would suggest something like .. to allow to choose IPv4/IPv6 profile by system property, with IPv4 as default. This would also allow testing IPv6 on dualstack networks.
In WSDiscoveryClient, although address can be altered by setter or constructor, the default one can be still switched by proposed system property.
Multicast IPv4 and IPv6 addreses in WS-Discovery spec, section 3.1.1