IETF Logo Mail Archive

Re: [dnssd] Setting device friendly names

Dave Thaler <dthaler@microsoft.com> Wed, 20 July 2016 16:45 UTC

Return-Path: <dthaler@microsoft.com>
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 9CE9B12D8B8 for <dnssd@ietfa.amsl.com>; Wed, 20 Jul 2016 09:45:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.021
X-Spam-Level:
X-Spam-Status: No, score=-102.021 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.com
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 UN5usUqNqDWS for <dnssd@ietfa.amsl.com>; Wed, 20 Jul 2016 09:45:10 -0700 (PDT)
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-bl2nam02on0090.outbound.protection.outlook.com [104.47.38.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D32B12D7AF for <dnssd@ietf.org>; Wed, 20 Jul 2016 09:44:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=5VXYYaP/67UlDwk0weA4R16bWaKgDzMAkg/h/OhIwDk=; b=oenV1/RQj2TyN7IQQYqESZLzSgeMNzYF7OB+DBpUr105fdqK+ZrLal5FngBmtjN7rMueq3A0FWX3f4Qsb+zQVr84fE2znmyddnrStPlJHsuQV9bCrhDEKm5Qfdt2QyTAXzed4Eb5deg7YPC6+u9VD8uLpitBu+HBMg+Exv7FQig=
Received: from DM2PR0301MB0717.namprd03.prod.outlook.com (10.160.97.13) by DM2PR0301MB0718.namprd03.prod.outlook.com (10.160.97.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.544.10; Wed, 20 Jul 2016 16:44:32 +0000
Received: from DM2PR0301MB0717.namprd03.prod.outlook.com ([10.160.97.13]) by DM2PR0301MB0717.namprd03.prod.outlook.com ([10.160.97.13]) with mapi id 15.01.0534.025; Wed, 20 Jul 2016 16:44:32 +0000
From: Dave Thaler <dthaler@microsoft.com>
To: Ted Lemon <mellon@fugue.com>, "STARK, BARBARA H" <bs7652@att.com>
Thread-Topic: [dnssd] Setting device friendly names
Thread-Index: AdHiibYrxB4vZWkMQdmCvDMGAtoHugAAU4SAAAad77A=
Date: Wed, 20 Jul 2016 16:44:32 +0000
Message-ID: <DM2PR0301MB0717F6F5E5F74852E625C1B7A3080@DM2PR0301MB0717.namprd03.prod.outlook.com>
References: <2040EE15-81F8-47EB-BF8D-DA544564C304@att.com> <CAPt1N1mxx=gPY_RtXaDVBXiT750Aq=YiyiOD4mj+CEh0MCT5qw@mail.gmail.com>
In-Reply-To: <CAPt1N1mxx=gPY_RtXaDVBXiT750Aq=YiyiOD4mj+CEh0MCT5qw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=dthaler@microsoft.com;
x-originating-ip: [2001:67c:370:160:ddbf:b2ce:c0f4:e325]
x-ms-office365-filtering-correlation-id: 3a77df7a-8496-4fcc-9e46-08d3b0bd201c
x-microsoft-exchange-diagnostics: 1; DM2PR0301MB0718; 6:JWwUFjlG3YM38X654th1HVtpqJSDP/UfZV6wQDkSWj2cjQAyK6SYMpw+UpYaNYOKGXxOqWHHA5OIPeTQPA0Kgh2910R+vcCMad4gYsiazVsVXCxta8P318a7QkkSxUVyjIOjGt/TbjwKDu3X9xtITA+7i8Cz1wJO2ZftfrzJkj3J+QlmXsKv9Oa0aMdh6O/xqFPsiYqa7/JG9zOjiek43UO0cZXxbwXBizhenZAOQxwCIQeneSTUQCGWcx9Md05qrQVZB+BvvE2GriehC0AsP6rcjXQqubUah31cf9jYcpzDCThkN6t7l2U2CxYPyTgPOn2j5VthxIxMOfCLYzQdMw==; 5:VLlFKK+r48XiExH8Fuz1Ef0v0CU8Z0ceoS/UM2SRJFX7QaRYXqbq5skIrHZuOIHJPJY23Y7PI2u2NYbOKbe7jMavR6vHIu/4QKP7j7ivVU5IVS2EXNjziryA5h08V6+1cgTEtD9aeY2BcMOjCI5a/g==; 24:pHjdculwAv811hi43ojIi3kYO41SM+QMgf8HAPzyeIt6Z+h5JLvr7pe2Fo7GYW7on3YCBPR3gXKVftbEROIf7ZFezKv3NWC6SXk6y/6T9hE=; 7:ycgkRzVZ5hpAsNRFzic3wNGFVJGcKq59yk1M13pGo2Eo0zZvPqjNVcYTVJqqK8LceX37pDnSngEWB+sMfMH9xRO30hWQ2oIHxtF8SyOVBx7K6gpf2se/t4rwTHr8BtEU6TKjhzHLSSP98+6qoao5N+cZTA/anXyo+9/9GHwZQ3fgQeiCO+ELERrc4egttQYzzIiwI4m/rKOj0OgXkRI1AvnBDRlbN1GSJNv7EqWIMCn1MawdF5hNwdwk/S03HL3O
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR0301MB0718;
x-microsoft-antispam-prvs: <DM2PR0301MB0718A57EAFED515580D1C2A4A3080@DM2PR0301MB0718.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(97927398514766)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6055026)(61426038)(61427038); SRVR:DM2PR0301MB0718; BCL:0; PCL:0; RULEID:; SRVR:DM2PR0301MB0718;
x-forefront-prvs: 000947967F
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(7916002)(189002)(24454002)(199003)(377454003)(81166006)(74316002)(81156014)(5002640100001)(8676002)(10290500002)(10400500002)(5005710100001)(8990500004)(189998001)(2906002)(101416001)(3660700001)(19625215002)(102836003)(19300405004)(68736007)(586003)(97736004)(33656002)(790700001)(86612001)(7846002)(4326007)(2900100001)(8936002)(7696003)(2950100001)(5003600100003)(7736002)(10090500001)(7906003)(87936001)(6116002)(15975445007)(99286002)(86362001)(122556002)(19580395003)(105586002)(3280700002)(19609705001)(76576001)(92566002)(19580405001)(106356001)(19617315012)(76176999)(50986999)(16236675004)(77096005)(11100500001)(5001770100001)(9686002)(54356999)(3826002); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR0301MB0718; H:DM2PR0301MB0717.namprd03.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DM2PR0301MB0717F6F5E5F74852E625C1B7A3080DM2PR0301MB0717_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Jul 2016 16:44:32.1594 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR0301MB0718
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/tK0S9XfWSTBThv-ZPcHRhUvobvQ>
Cc: "dnssd@ietf.org" <dnssd@ietf.org>
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: Wed, 20 Jul 2016 16:45:17 -0000

I wasn’t aware of this before either so I just did a web search…

http://www.upnp.org/download/upnp_vendor_implementation_guide_jan2001.htm
is what I found, which discusses it in somewhat easy to read terms.

https://openconnectivity.org/upnp/specifications says UPnP is a standard, and
I found what I think is the friendlyname referred to, in the “Basic Device:1” spec.

Dave

From: dnssd [mailto:dnssd-bounces@ietf.org] On Behalf Of Ted Lemon
Sent: Wednesday, July 20, 2016 3:31 PM
To: STARK, BARBARA H <bs7652@att.com>
Cc: dnssd@ietf.org
Subject: Re: [dnssd] Setting device friendly names

Can you talk more about this UPnP thing?   Bear in mind that UPnP is not a standard, AFAIK, although its follow-on, PCP, is.   I don't know that PCP has this feature.

The fact that some devices have UIs that users may or may not be able to find does not mean that there needn't be a standard way to do it.   Maybe we don't need it, but if we don't, that's not the reason.

On Wed, Jul 20, 2016 at 3:22 PM, STARK, BARBARA H <bs7652@att.com<mailto: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<mailto:dnssd@ietf.org>
https://www.ietf.org/mailman/listinfo/dnssd

v2.23.0 | Report a Bug | By Email