A hypothetical solution would be to stick with the DNS SD / avahi concept and use domains ending in .local. That would have the benefit to be able to create a

A hypothetical solution would be to stick with the DNS SD / avahi concept and use domains ending in .local. That would have the benefit to be able to create a CA for that domain that can cross-sign your certificates in order to prevent the snakeoil workflow, which must stick to local IPv4 ranges and the fe80:: IPv6 prefix. I've been digging through the DNS SD specifications lately (and how airplay, airprint, airscan and others work)...and I'm mindblown on how simple all things IoT could be if everything would support the DNS service discovery RFC. In a parallel world nobody has IP problems, and nobody has problems connecting to their printers. The way it's currently going though, I don't see any legacy firmware working in the near future due to CORS. I mean, most of the admin interfaces will break, probably, because of how they use forms to submit configs and settings.