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

"Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com> Tue, 25 November 2014 00:44 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 0A5971A6FF6 for <dnssd@ietfa.amsl.com>; Mon, 24 Nov 2014 16:44:29 -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 mwF8g6nZEt_0 for <dnssd@ietfa.amsl.com>; Mon, 24 Nov 2014 16:44:26 -0800 (PST)
Received: from mail-ie0-x22f.google.com (mail-ie0-x22f.google.com [IPv6:2607:f8b0:4001:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5C8F1A6F5A for <dnssd@ietf.org>; Mon, 24 Nov 2014 16:44:25 -0800 (PST)
Received: by mail-ie0-f175.google.com with SMTP id at20so10071603iec.20 for <dnssd@ietf.org>; Mon, 24 Nov 2014 16:44:24 -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=SIEPAwpdJWbDGMJgD3FoOZZjxvP2V6e4BHRZXJhzpqM=; b=igzJT8xOl1p2cHYpeGZHxPgxRQAVqpXACAqG+ziTbbXXAEGy2zDYtSCUJcEBXnmcgV HaJd1JE+OPCD/vUSpStb0rLqvs8tmrMeRnhfBHlhzoI6WfxvgoERtkuaoH3w1q6iY0qr vwLU3etucqWoEhvAVzs31lGHaViDt9fyiSD2TVFE4gmQO5NXg5tZ1sM5tYVePUiyW4lt U+w5kCWcFkiE38GLQPzcLl0mWmlYChM1+rwgpCMzk4VCzDp2vsiYRQRglXSXcRgIOIKs xjnT0Axa9TCCrT86euqFmxtIgjRp+nQc17pCVvjdXq+2qhUJHi6NDr17MgJRzpyJWH9t YGrA==
MIME-Version: 1.0
X-Received: by 10.43.74.3 with SMTP id yu3mr27243693icb.15.1416876264807; Mon, 24 Nov 2014 16:44:24 -0800 (PST)
Received: by 10.64.57.14 with HTTP; Mon, 24 Nov 2014 16:44:24 -0800 (PST)
In-Reply-To: <D098C799.3CFD6%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> <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> <D098C799.3CFD6%Robby.Simpson@GE.com>
Date: Tue, 25 Nov 2014 09:44:24 +0900
Message-ID: <CAPK2Dez2gxDSLOwY9MHH0_b287owzetSK7PLw1ndCxUOO25a1Q@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=001a11c20c087464cf0508a43632
Archived-At: http://mailarchive.ietf.org/arch/msg/dnssd/fV53zQU9By7nsdCUvzrfmQYEUKg
Cc: "dnssd@ietf.org" <dnssd@ietf.org>, Guangqing Deng <dengguangqing@cnnic.cn>
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:44:29 -0000

Robby,
This is a good reference for constrained node, such as IoT.
I will include the definitions of constrained node and IoT in the next
version of my draft.

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:32 AM, Simpson, Robby (GE Energy Management) <
robby.simpson@ge.com> wrote:

> When discussing constrained devices (which I think is the intent here), I
> find the definitions from RFC 7228 (
> https://datatracker.ietf.org/doc/rfc7228/) convenient.
>
> - Robby
>
> From: Guangqing Deng <dengguangqing@cnnic.cn<mailto:dengguangqing@cnnic.cn
> >>
> Date: Monday, November 24, 2014 at 11:26 AM
> To: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com<mailtomailto:
> jaehoon.paul@gmail.com>>
> Cc: "dnssd@ietf.org<mailto:dnssd@ietf.org>" <dnssd@ietf.org<mailtomailto:
> dnssd@ietf.org>>
> Subject: Re: [dnssd] DNS Name Autoconfiguration for Home Network Devices
>
> 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<mailto:jaehoon.paul@gmail.com>
> Date: 2014-11-19 12:00
> To: Stuart Cheshire<mailto:cheshire@apple.com>
> CC: dnssd@ietf.org<mailto:dnssd@ietf.org>; Myung-Ki Shin<mailto:
> mkshin@etri.re.kr>gt;; Brian Haberman<mailto:brian@innovationslab.net>;
> Jung-Soo Park<mailto: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<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 Wed, Nov 19, 2014 at 7:46 AM, Stuart Cheshire <cheshire@apple.com
> <mailto:cheshire@apple.com>> wrote:
> On 17 Nov, 2014, at 17:33, Mr. Jaehoon Paul Jeong <jaehoon.paul@gmail.com
> <mailto: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<mailto:dnssd@ietf.org>
> https://www.ietf.org/mailman/listinfo/dnssd
>
>