Re: [dnssd] Setting device friendly names

i've been in this neighborhood before.  Not sure there exists a clearly
defined meaning for "friendly".  That said, there exists a canonical name.
Others (governments, DNS admins, DHCP, UPnP, et.al.) are external, third
parties and often set their own rules as to the "name" of an entity in
their own context.  Thirdly, a name often consists of several facets or
attributes.  The construct that was used for the Client Based Naming system
was tripart;  a) a string of unicode labels,  b) a cryptographic
certificate for the string of unicode labels,  and  c) a locality reference
where the string and the certificate were first bound.
All non-canonical names were derived from one or more facets or fragments
of facets of the canonical name.  A shorter name most of the time,

On Wed, Jul 20, 2016 at 6:22 AM, STARK, BARBARA H <bs7652@att.com> wrote:

> In my experience, many devices already support mechanisms for friendly
> name acquisition. Many devices, including PCs, ask for names during setup.
> Others support UPnP friendly name service. Others have UIs to allow naming.
> What I really want (as a user) is for the device to have the same name in
> all contexts. So if it's been named, through whatever means, use that name.
> Which to me says we don't need a new standard for remote naming that all
> devices must support.
> Barbara
> _______________________________________________
> dnssd mailing list
> dnssd@ietf.org
> https://www.ietf.org/mailman/listinfo/dnssd
>