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

"Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com> Tue, 25 November 2014 00:50 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 2BE761A7018 for <dnssd@ietfa.amsl.com>; Mon, 24 Nov 2014 16:50:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.018
X-Spam-Level:
X-Spam-Status: No, score=-1.018 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_FONT_FACE_BAD=0.981, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 oTJwZFpnhGTo for <dnssd@ietfa.amsl.com>; Mon, 24 Nov 2014 16:50:15 -0800 (PST)
Received: from mail-ig0-x22b.google.com (mail-ig0-x22b.google.com [IPv6:2607:f8b0:4001:c05::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF2B11A700C for <dnssd@ietf.org>; Mon, 24 Nov 2014 16:50:14 -0800 (PST)
Received: by mail-ig0-f171.google.com with SMTP id z20so102742igj.16 for <dnssd@ietf.org>; Mon, 24 Nov 2014 16:50:14 -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=kckmwZvPjd7LRgs4/x+7ylwoetFoeec7zfdWSgDEEy8=; b=Sx9r86Vi4Gmkk+OaVaBYvK3aINZNlWVaGjt28QcGRrD3UiVznTOqUDfKS/ibM/W0DF L86qT3sKtrk8Cnr3LOn14goTVj5oz9h6nP8FfIKtQyNe70kyaUGvol+YsRBGrrCgjK22 ORw/vu7J4IWO4jh0yGf+Y8J7p5KeZ2GaiuOrvYrUjkthQoq62Cunm/a8RRlNYB4932tq z5X7rx7z7V58RdQi92hM6Uisiem6YGzdBxNGGDHJFx2tNA1KVeISnNf8S02ZwDFiDZ+c 5WJgq0z5Dvwa347tGnfX3/JKzFUmgNkqg6EC+O8v4o9DXmmGngoBtd2AL11TS5gIHAXh f66w==
MIME-Version: 1.0
X-Received: by 10.107.156.131 with SMTP id f125mr21466267ioe.15.1416876613894; Mon, 24 Nov 2014 16:50:13 -0800 (PST)
Received: by 10.64.57.14 with HTTP; Mon, 24 Nov 2014 16:50:13 -0800 (PST)
In-Reply-To: <201411250026365350479@cnnic.cn>
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> <42C3C87F-0D99-47CB-B50A-9107BD10A2E6@bangj.com> <CAPK2Dew8BOUOG-bZ-_EcTtxuz6m_NeAUj70i8jzXc4RC-zTFFA@mail.gmail.com> <26B22159-3630-493B-AAA0-BC2DEA9DBA7F@apple.com> <CAPK2DewGvnZG5eMUYsq4bT7pEuJsAt2DSPs30_chycE21CTHqA@mail.gmail.com> <201411250026365350479@cnnic.cn>
Date: Tue, 25 Nov 2014 09:50:13 +0900
Message-ID: <CAPK2DexePs2Sm-K+XDaTUqvEzvq6ECxJdjb=nwMB6nxEfz2qVQ@mail.gmail.com>
From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
To: Guangqing Deng <dengguangqing@cnnic.cn>
Content-Type: multipart/alternative; boundary=001a1140c8d84308870508a44bbf
Archived-At: http://mailarchive.ietf.org/arch/msg/dnssd/eswpk9GbuTtHtIczPYaciac2xUU
Cc: "dnssd@ietf.org" <dnssd@ietf.org>
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, 25 Nov 2014 00:50:17 -0000

Guangqing,
Domain name has the meaning of both logical space and physical space.
For example, ".home" means the domain of logical space for home network and
also
the physical place of my home.

In my draft, the location as part of domain name puts more weight on
physical space and
the device category as part of domain name puts more weight on local space
as a device cluster in a home network.

Thanks.

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 25, 2014 at 1:26 AM, Guangqing Deng <dengguangqing@cnnic.cn>
wrote:

>  The term of "IoT device" is mentioned many times here and in the
> draft, and it seems necessary to give a relatively formal defination to it
> instead of only presenting some instances of so called "IoT device". The
> domain name is usually used to uniquely and consistently identify objects
> and thus it is better to keep the domain name unchangeable. If many kinds
> of information of "IoT devices" (such as their locations and categories)
> are inserted into the domain name in some way, whether we should change the
> domain name or not if some kinds of information (like the location) changes?
>
> ------------------------------
>  Guangqing Deng
> cnnic
>
>  *From:* Mr. Jaehoon Paul Jeong <jaehoon.paul@gmail.com>
> *Date:* 2014-11-19 12:00
> *To:* Stuart Cheshire <cheshire@apple.com>
> *CC:* dnssd@ietf.org; Myung-Ki Shin <mkshin@etri.re.kr>kr>; Brian Haberman
> <brian@innovationslab.net>et>; Jung-Soo Park <pjs@etri.re.kr>
> *Subject:* Re: [dnssd] DNS Name Autoconfiguration for Home Network Devices
>  Stuart,
> Thanks for your constructive comments.
>
> As I answered Alf's email message just before,
> I would like to allow IoT vendors to have an alternative way for DNS naming
> with more compact implementation based on IPv6 stateless autoconfiguration.
>
> For the question about how users find out the host names and which
> protocols are used
> were presented with the following slides 4 and 5 during the last dnssd WG
> session in Hawaii:
> http://www.ietf.org/proceedings/91/slides/slides-91-dnssd-6.pdf
>
> To figure out what those devices do, we can use device category and device
> model
> in the DNS name format.
>
> 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 Wed, Nov 19, 2014 at 7:46 AM, Stuart Cheshire <cheshire@apple.com>
> wrote:
>
>> On 17 Nov, 2014, at 17:33, Mr. Jaehoon Paul Jeong <jaehoon.paul@gmail.com>
>> wrote:
>>
>> > Hi Tom,
>> >
>> > You are right for appliances with enough capacity to run mDNS.
>> >
>> > However, for low capacity IoT devices without mDNS, my proposal will be
>> able to support an alternative way for DNS naming.
>>
>> You assert that there are devices with insufficient resources to run
>> DNS-SD/mDNS.
>>
>> You assert that these devices would have sufficient resources to run your
>> alternative.
>>
>> I think you need data to substantiate these claims. Note that devices
>> like the SitePlayer Telnet implement DNS-SD/mDNS in under one kilobyte
>> (about 850 bytes of code, if I remember correctly): <
>> http://netmedia.com/siteplayer/telnet/>
>>
>> So you need to demonstrate that:
>>
>> 1. That there are devices where 850 bytes of code is too much.
>>
>> 2. That these devices can implement your thing in under 850 bytes.
>>
>> 3. That your thing is useful. I’m still unclear on what your thing is
>> useful for. Your proposal says how devices pick host names, but not how
>> users find out what those host names are, or find out what those devices
>> do, or what protocol to use to communicate with them, and how clients
>> resolve those host names to addresses.
>>
>> Stuart Cheshire
>>
>> _______________________________________________
>> dnssd mailing list
>> dnssd@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnssd
>>
>
>