IETF Logo Mail Archive

Re: [dnssd] Setting device friendly names

"Christian Huitema" <huitema@huitema.net> Sun, 24 July 2016 09:05 UTC

Return-Path: <huitema@huitema.net>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8550D12D115 for <dnssd@ietfa.amsl.com>; Sun, 24 Jul 2016 02:05:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level:
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yW2iX-GWKocq for <dnssd@ietfa.amsl.com>; Sun, 24 Jul 2016 02:05:31 -0700 (PDT)
Received: from xsmtp01.mail2web.com (xsmtp01.mail2web.com [168.144.250.230]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C85B12B01B for <dnssd@ietf.org>; Sun, 24 Jul 2016 02:05:31 -0700 (PDT)
Received: from [10.5.2.12] (helo=xmail02.myhosting.com) by xsmtp01.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1bRFIr-0004cv-Au for dnssd@ietf.org; Sun, 24 Jul 2016 05:05:30 -0400
Received: (qmail 13533 invoked from network); 24 Jul 2016 09:02:28 -0000
Received: from unknown (HELO huitema1) (Authenticated-user:_huitema@huitema.net@[90.54.87.84]) (envelope-sender <huitema@huitema.net>) by xmail02.myhosting.com (qmail-ldap-1.03) with ESMTPA for <bs7652@att.com>; 24 Jul 2016 09:02:27 -0000
From: Christian Huitema <huitema@huitema.net>
To: 'Ted Lemon' <mellon@fugue.com>, 'Stuart Cheshire' <cheshire@apple.com>
References: <2040EE15-81F8-47EB-BF8D-DA544564C304@att.com> <CAPt1N1mxx=gPY_RtXaDVBXiT750Aq=YiyiOD4mj+CEh0MCT5qw@mail.gmail.com> <AD1ED147-37F0-4276-BC3B-E70072F97EBD@att.com> <B18D9771-8828-42D6-8F89-AC000531C85F@apple.com> <CAPt1N1nPkM2XBi5EapzP7RQmOYNwTWmRuSuD1Y3=JWXmTQcu7w@mail.gmail.com> <8F6598B8-BBE0-4496-B850-51686E63A527@att.com> <CBF3CF2D-DB80-4792-B50A-4C0FFAAAC9F1@apple.com> <CAPt1N1mHfoawS=0xRXVuuZYqmVdKLGdZkR3qqVdz_eNrNs6uSw@mail.gmail.com> <A0740754-0042-4EB1-8FFC-BF85555DD7CB@apple.com> <CAPt1N1=F9vUAbJEg04AQw=SSVKN1oxtOkiffyF7csn6zhzxGKQ@mail.gmail.com>
In-Reply-To: <CAPt1N1=F9vUAbJEg04AQw=SSVKN1oxtOkiffyF7csn6zhzxGKQ@mail.gmail.com>
Date: Sun, 24 Jul 2016 11:02:26 +0200
Message-ID: <009d01d1e58a$1cdd7ca0$569875e0$@huitema.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQKfnuZIyEEmc88/z8GE+crHEvfQPwGQVMAYAiJJWUYB3nkQBwHA3mAnAsoukakBZtKyvAJc+ds/Apy89lgCLrmw6p32eMHQ
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/4uQw7sEYwpBgdmfVOdeesHE8aXc>
Cc: dnssd@ietf.org, "'STARK, BARBARA H'" <bs7652@att.com>
Subject: Re: [dnssd] Setting device friendly names
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jul 2016 09:05:32 -0000

On Thursday, July 21, 2016 7:24 PM, Ted Lemon wrote:

> Right, the issue would be if we changed it in the database operated by 
> the homenet, and didn't tell the host.
>
> On Thu, Jul 21, 2016 at 7:07 PM, Stuart Cheshire <mailto:cheshire@apple.com> wrote:
>> On 21 Jul 2016, at 09:06, Ted Lemon <mailto:mellon@fugue.com> wrote:
>>
>>> Hm.   That's not what I'm saying.  The point Barbara made that I agree with and restated was that the device should report the same name no matter who asks or how.
>>
>> For the most part, this is universally true today. Of all the devices I’ve seen that support both UPnP and Bonjour DNS-SD/mDNS, virtually have a single place in the web UI to set the name, which is then used for both discovery protocols.

Please let's not forget the privacy issues for mobile devices. There is an intarea draft about that, "hostname practices considered harmful." In short, volunteering a name to the network allows tracking; volunteering a user friendly name like "Ted Lemon's laptop" allows for even better tracking.

For DHCP, the "privacy" recommendation is to not volunteer a name at all to the DHCP server, or to use a one-time random name. 

Now, I can understand that these one-time random names should be more user friendly than "F78AC123", maybe using something like "correct-horse-battery-staple" in the tradition of https://www.xkcd.com/936/. 

-- Christian Huitema

v2.23.0 | Report a Bug | By Email