Re: [homenet] alternatives to .home

[Markus Stenberg <[e-mail]>]

On 17.6.2016, at 10.37, Pierre Pfister <[e-mail]> wrote:
> I think this is a key point indeed.
> 
> mDNS works really hard to *not* show any name to the user.
> I would like it to be the same for homenet, but I am not sure we have a complete solution for no-name multi-link service discovery for homenet yet.

Agreed; dealing with naming collisions is mainly the painful part on implementation front.

> So either we seriously address the service discovery problem. And we make the assumption that non-geeky users shall not see names, never. In which case the name we pick does not matter.
> Or we assume users will see names, in which case allocating a user-friendly name is utterly important.

For home use case, I suspect there is no need for multiple zones _at all_, at least visible to the user, and users do not typically care about the domain unless they want remote access (and I am not sure many really do, and in that case it would be something sourced from ISP anyway).

e.g. even if we (for implementation purposes) use hybrid proxy underneath, the published data would be just ‘legacy browse’ (flat, no domain at all) names and not ‘browse’ (full domain _including_ whatever .hn.asdf.arpa we wind up with). To make names unique we might want to garbage-fy them if we want to use mdns as source of information, but that’s it.

Cheers,

-Markus