On 06/08/2012 04:28, Evan Hunt wrote:
>> i wasn't able to participate in this discussion because I had other
>> business during homenet, but I'm a bit frustrated by this conclusion.
> 
> I was speaking for myself and I believe the issue is in flux; please
> don't take it as a "conclusion". :)
> 
>> IMHO, we shouldn't promote bad solutions, and .local is a bad solution.
> 
> IMHO .<hexidecimal-gibberish> is also a bad solution.  It's, at least
> potentially, a worse one: you buy a new router, and suddenly your devices
> all have new names and your bookmarks don't work.  To make them work again,
> you have to remember the hexidecimal-gibberish that was assigned by your
> previous router and configure it to use the same one.  Ugly.


I do agree that expecting ordinary users to keep track of a pseudorandom
string is unreasonable. Maybe we can take a hint from mailman. When
you install a new CPE router, and it's unable to discover the current
unique string, you could be asked to enter your existing unique string,
but also be offered the option of the router creating a new one.

So the requirements seem to be

1. A discovery mechanism so that new devices on a homenet can find the
local unique string.

2. The string and the discovery mechanism need to survive a cold start
and the replacement of the CPE router (in all scenarios except a "factory
reset"). That means a distributed solution.

3. If there really is no unique string, the CPE router generates one,
unless the user prefers to type it in.

Undoubtedly .sitelocal is simpler.

    Brian

> 
> I'm not really happy with either of these choices, but I'm less unhappy
> with .sitelocal.
> 
>> Whether we come up with some way to leverage a ULA to present things
>> sensibly in some UI is another question, but if we are trying to come up
>> with a solution for geeks, why not come up with a _real_ solution,
>> instead of the .local hack?
> 
> I'd love to hear the plan.
> 
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet

Reply via email to