Re: [homenet] alternatives to .home

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.

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.

Regards

- Pierre

> Le 17 juin 2016 à 03:10, Andrew Sullivan <ajs@anvilwalrusden.com> a écrit :
> 
> On Thu, Jun 16, 2016 at 07:53:42PM -0400, Ted Lemon wrote:
> 
>> .local has worked
> 
> But mostly because ordinary humans never see it.  That's what's not
> clear to me.
> 
> Is this a name that will mostly be hidden by user-interface sugar
> (which is mostly how it works with mDNS -- please don't tell me about
> ssh.  That's not our audience, I maintain)?  If so, then any domain
> will do, and putting it under arpa would be fine.
> 
> Is it a name that we expect people often to use in you-type-it-in
> contexts?  If so, then the story is very different.
> 
> In any case, I'd really like "translation" to be off the table.  We
> are not competent to do that, and anyway we're specifying a permanent
> part of infrastructure that will not be able to evolve as (say)
> language evolves.
> 
> Best regards,
> 
> A
> 
> -- 
> Andrew Sullivan
> ajs@anvilwalrusden.com
> 
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet