Re: [homenet] alternatives to .home

Michael, the reason to have a consistent name is that the name _will_ show
up in UI elements, and therefore _should_ behave in a comprehensible
manner.   The IETF tends to be understandably dismissive of the end-user's
capacity to correctly model the functioning of the network, but we should
not use techniques that deliberately subvert the user's ability to make
models.

The problem with presenting something that is not the actual token that is
being used to address the device to the user is that the user cannot then
tell the difference between that device and some other device with the same
presentation name, but a different identifying name.   This then becomes an
attack surface for malware that wants to trick the user.

Even if the user doesn't understand the structure of the name, there is no
harm in revealing that name in the UI.   It can appear next to the
descriptive name.

On Fri, Jun 17, 2016 at 9:23 AM, Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> Edmon Chung <edmon@registry.asia> wrote:
>     > e.g. 2 character non-countrycodes: QM QN QO QP QQ QR QS QT QU QV QW
> QX
>     > QY QZ XA XB XC XD XE XF XG XH XI XJ XK XL XM XN XO XP XQ XR XS XT XU
> XV
>     > XW XX XY XZ
>
> .xh
> .xn
>
> seem like the best.
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>
>