Re: [dnssd] DNS Name Autoconfiguration for Home Network Devices

"Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com> Tue, 18 November 2014 01:29 UTC

Return-Path: <jaehoon.paul@gmail.com>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 172A91AD03B for <dnssd@ietfa.amsl.com>; Mon, 17 Nov 2014 17:29:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 4z4WYvwmZwM5 for <dnssd@ietfa.amsl.com>; Mon, 17 Nov 2014 17:29:48 -0800 (PST)
Received: from mail-ie0-x22b.google.com (mail-ie0-x22b.google.com [IPv6:2607:f8b0:4001:c03::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 751F11AD02F for <dnssd@ietf.org>; Mon, 17 Nov 2014 17:29:48 -0800 (PST)
Received: by mail-ie0-f171.google.com with SMTP id rl12so2626954iec.2 for <dnssd@ietf.org>; Mon, 17 Nov 2014 17:29:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=d3ugc9zDkaZSXgD/mIee/rPkHznIt8J3Bl/Q2gL7EB0=; b=jSzizr07DO5qdfUGub9gb50cNUT5vJzCeacSkxSPVDu2Gp+T2TtmzIRnJ36c1MVf3m OFF5zU1dJsGahjebnbUBnDYYIDuzaXRXRCr5vin+Yq/4+TWfXjelXxpBnu4xIxQSgMtd 6M4EkQYgwDImWjyjKJRSPo37LDcmTSjpYmBSnE87+R3JDAzDb2TmUKHE64IDuUZsJc1N gojW5FNy4LT9FGZZOo0RAb1gCHipJCtmdICiUZuZ4F/dgvWj8Qmd3vpymsHfigUZo7T1 6z6kg0o534V9QUSvTHmFvkrTxF1o+0VpBUijYeNjeyAeXm3fktIrOoy2nmiwHxKH6G5r pAFg==
MIME-Version: 1.0
X-Received: by 10.50.62.4 with SMTP id u4mr509957igr.46.1416274187525; Mon, 17 Nov 2014 17:29:47 -0800 (PST)
Received: by 10.64.62.18 with HTTP; Mon, 17 Nov 2014 17:29:47 -0800 (PST)
In-Reply-To: <D08FC56A.3C9AF%Robby.Simpson@GE.com>
References: <CAPK2DeyuABqSbH5dtdtScYWnE-vkmGO642xFb6FZehu-5MTaAA@mail.gmail.com> <436692B4-978D-4E62-868E-78FA8AF3F26F@nominum.com> <CAPK2Deys6VU83R0hfv_8svNKuaSBEfu_dGqnGkoN_pQ9zE_6HQ@mail.gmail.com> <cc9f90afaa7a48bdaf7a8906546571b5@BY2PR03MB412.namprd03.prod.outlook.com> <CAPK2Dex=hR5HE-BFtvbMzgadfcu-4CPgP8zd1sziNPCQNJ+aCw@mail.gmail.com> <D08FC56A.3C9AF%Robby.Simpson@GE.com>
Date: Tue, 18 Nov 2014 10:29:47 +0900
Message-ID: <CAPK2DezTzh7qz-FEm8yJ2hqxcq5UDn6oppn4Wid3syGQZ8NSYw@mail.gmail.com>
From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
To: "Simpson, Robby (GE Energy Management)" <robby.simpson@ge.com>
Content-Type: multipart/alternative; boundary=047d7bdca6e0da30b80508180734
Archived-At: http://mailarchive.ietf.org/arch/msg/dnssd/amgJynITXz_NmWhoo4xHk9MyeqA
Cc: Brian Haberman <brian@innovationslab.net>, Myung-Ki Shin <mkshin@etri.re.kr>, "dnssd@ietf.org" <dnssd@ietf.org>, Dave Thaler <dthaler@microsoft.com>, Jung-Soo Park <pjs@etri.re.kr>, Ted Lemon <Ted.Lemon@nominum.com>, Sejun Lee <prosejun14@gmail.com>
Subject: Re: [dnssd] DNS Name Autoconfiguration for Home Network Devices
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion of extensions to Bonjour \(mDNS and DNS-SD\) for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 18 Nov 2014 01:29:52 -0000

Hi Robby,
Yes, my intent is to to include semantics (e.g., device category, device
vendor, and device model)
in a standardized fashion into the DNS names of low-capacity IoT devices.

I intend to place machine-interpretable semantics into the actual DNS names
themselves
so that machines can use the DNS name for the identification of other
machines
without additional service discovery through mDNS.

The localization of devices is also possible with the DNS name
because the DNS name can include the location of the device,
as describe in Section 6 (Location-Aware DNS Name Configuration) in my
draft:
http://datatracker.ietf.org/doc/draft-jeong-homenet-device-name-autoconf/

Thanks for your good opinion.

Paul

===========================
Mr. Jaehoon (Paul) Jeong, Ph.D.
Assistant Professor
Department of Software /
Department of Computer Engineering
Sungkyunkwan University
Office: +82-31-299-4957
Mobile: +82-10-4758-1765
Fax: +82-31-290-5119
Email: pauljeong@skku.edu, jaehoon.paul@gmail.com
CPS Lab Website: http://cpslab.skku.edu
Personal Homepage: http://cpslab.skku.edu/people-jaehoon-jeong.php

On Tue, Nov 18, 2014 at 6:15 AM, Simpson, Robby (GE Energy Management) <
robby.simpson@ge.com> wrote:

> It seems to me that part of your intent is to include semantics (e.g.,
> device category, device vendor, device model) in a standardized fashion
> into the DNS name.
>
> On the other hand, while we often apply semantics to DNS names currently
> for human readers, these semantics typically are not standardized for
> machines.  For that, we have DNS-SD.
>
> As an example from the IoT space, we use both mDNS and DNS-SD for SEP 2.0
> (IEEE 2030.5).  While the DNS names often reflect aspects such as device
> manufacturer and category, these are not meant to be machine interpretable
> in SEP 2.0.  Rather, we use DNS-SD to advertise various functionality that
> is machine interpretable.
>
> Perhaps I am misinterpreting, but is your intent to place
> machine-interpretable semantics into the actual DNS names themselves?
>
> Thanks,
> Robby
>
>
> Robby Simpson, PhD
>
> System Architect
>
> GE
>
> Digital Energy
>
> M: +1 404 219 1851
>
> Robby.Simpson@GE.com
>
>
> From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com<mailtomailto:
> jaehoon.paul@gmail.com>>
> Date: Saturday, November 15, 2014 at 1:22 AM
> To: Dave Thaler <dthaler@microsoft.com<mailto:dthaler@microsoft.com>>
> Cc: Brian Haberman <brian@innovationslab.net<mailtomailto:
> brian@innovationslab.net>>t;>, Myung-Ki Shin <mkshin@etri.re.kr<mailtomailto:
> mkshin@etri.re.kr>>t;>, "dnssd@ietf.org<mailto:dnssd@ietf.org>" <
> dnssd@ietf.org<mailto:dnssd@ietf.org>>, Jung-Soo Park <pjs@etri.re.kr
> <mailto:pjs@etri.re.kr>>, Ted Lemon <Ted.Lemon@nominum.com<mailtomailto:
> Ted.Lemon@nominum.com>>t;>, Sejun Lee <prosejun14@gmail.com<mailtomailto:
> prosejun14@gmail.com>>
> Subject: Re: [dnssd] DNS Name Autoconfiguration for Home Network Devices
>
> Dave,
> Thanks for your clarification.
>
> In Page 32 in RFC 6762, there is the recommended course of action after
> probing and failing, but
> there is no text about a random ID selection.
> Anyway, we can perform a random ID selection for the uniqueness of a DNS
> name, but
> the readability for such a DNS name is not good for the users.
>
> My original intention for DNS name generation is to include device
> category (e.g., refrigerator),
> device vendor (e.g., Samsung), device model (e.g., RH269LP).
> This name itself delivers much information to users and mobile  smart
> devices (e.g., smartphone or smart TV)
> to represent the device icon visually.
>
> I am not sure this is enough answer for your last question.
> If you have more comments, please let me know.
>
> Paul
>
> ===========================
> Mr. Jaehoon (Paul) Jeong, Ph.D.
> Assistant Professor
> Department of Software /
> Department of Computer Engineering
> Sungkyunkwan University
> Office: +82-31-299-4957
> Mobile: +82-10-4758-1765
> Fax: +82-31-290-5119
> Email: pauljeong@skku.edu<mailto:pauljeong@skku.edu>,
> jaehoon.paul@gmail.com<mailto:jaehoon.paul@gmail.com>
> CPS Lab Website: http://cpslab.skku.edu
> Personal Homepage: http://cpslab.skku.edu/people-jaehoon-jeong.php
>
> On Fri, Nov 14, 2014 at 11:59 AM, Dave Thaler <dthaler@microsoft.com
> <mailto:dthaler@microsoft.com>> wrote:
> Paul wrote:
> > For the regeneration and verification of a unique DNS name under DNS
> name conflict,
> > the solution in RFC 6762 recommends to use an incremental digit (such as
> 2, 3, 4, etc.)
> > by trial and error. In an IoT scenario where there will be many IoT
> devices of the same
> > type, such as light bulb in home or hotel here, this incremental
> numbering approach
> > will be costly and slow to let each IoT device have a unique DNS name,
> ...
>
> My reading is that RFC 6762 does not _require_ an incremental digit.  You
> can put in
> a random ID or MAC-derived ID or something else highly unlikely to collide.
> As such, it should not be "costly and slow".  Indeed RFC 6762 does not
> specify what
> you have to do.   Would it be possible to recast your draft as
> "how to choose a unique ID and use RFC 6762" ?
>
> -Dave
>
>