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

"Guangqing Deng" <> Mon, 24 November 2014 16:26 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 88B511A01D5 for <>; Mon, 24 Nov 2014 08:26:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 1.77
X-Spam-Level: *
X-Spam-Status: No, score=1.77 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_FONT_FACE_BAD=0.981, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Bn-Nk7uED5oB for <>; Mon, 24 Nov 2014 08:26:52 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 450C71A6EEF for <>; Mon, 24 Nov 2014 08:26:50 -0800 (PST)
Received: from dgq-PC (unknown []) by (Coremail) with SMTP id AQAAf0BJUMA9XHNUuZLTAA--.3132S2; Tue, 25 Nov 2014 00:26:38 +0800 (CST)
Date: Tue, 25 Nov 2014 00:26:37 +0800
From: "Guangqing Deng" <>
To: "Mr. Jaehoon Paul Jeong" <>
References: <> <> <> <> <> <> <> <> <>, <>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7, 1, 2, 36[cn]
Mime-Version: 1.0
Message-ID: <>
Content-Type: multipart/alternative; boundary="----=_001_NextPart774738355674_=----"
X-Coremail-Antispam: 1UD129KBjvJXoWxurWDGryrAF13Cr43WF4fGrg_yoW5urykpF Z3tFyvkrn8Kry7G3y7uw1kuFWrZryfAw15Jwn5Jr1UCF98uFyftr1jkr1Fva4DCrsaya47 ZFWa9r1DGwn8ZFJanT9S1TB71UUUUU7qnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUB2b7Iv0xC_Cr1lb4IE77IF4wAFF20E14v26r1j6r4UM7CY07I2 0VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0rw A2F7IY1VAKz4vEj48ve4kI8wA2z4x0Y4vE2Ix0cI8IcVAFwI0_Gr0_Xr1l84ACjcxK6xII jxv20xvEc7CjxVAFwI0_Gr0_Cr1l84ACjcxK6I8E87Iv67AKxVWxJVW8Jr1l84ACjcxK6I 8E87Iv6xkF7I0E14v26r4j6r4UJwAS0I0E0xvYzxvE52x082IY62kv0487Mc02F40E57IF 67AEF4xIwI1l5I8CrVCF0I0E4I0vr24lYx0E2Ix0cI8IcVAFwI0_Jr0_Jr4lYx0Ex4A2js IE14v26r1j6r4UMcvjeVCFs4IE7xkEbVWUJVW8JwACjcxG0xvY0x0EwIxGrwACY4xI67k0 4243AVAKzVAKj4xxM4xvF2IEb7IF0Fy26I8I3I1l42xK82IYc2Ij64vIr41l4I8I3I0E4I kC6x0Yz7v_Jr0_Gr1lx2IqxVAqx4xG67AKxVWUGVWUWwC20s026x8GjcxK67AKxVWUGVWU WwC2zVAF1VAY17CE14v26r1Y6r17MIIYrxkI7VAKI48JMIIF0xvE2Ix0cI8IcVAFwI0_Jr 0_JF4lIxAIcVC0I7IYx2IY6xkF7I0E14v26r1j6r4UMIIF0xvE42xK8VAvwI8IcIk0rVWr Zr1j6s0DMIIF0xvEx4A2jsIE14v26r1j6r4UMIIF0xvEx4A2jsIEc7CjxVAFwI0_Jr0_Gr 1l6VACY4xI67k04243AbIYCTnIWIevJa73UjIFyTuYvjxU2b10UUUUU
X-CM-SenderInfo: 5ghqww5xdqw1xlqjqupqqluhdfq/
Cc: "" <>
Subject: Re: [dnssd] DNS Name Autoconfiguration for Home Network Devices
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion of extensions to Bonjour \(mDNS and DNS-SD\) for routed networks." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 24 Nov 2014 16:26:54 -0000

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

From: Mr. Jaehoon Paul Jeong
Date: 2014-11-19 12:00
To: Stuart Cheshire
CC:; Myung-Ki Shin; Brian Haberman; Jung-Soo Park
Subject: Re: [dnssd] DNS Name Autoconfiguration for Home Network Devices
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:

To figure out what those devices do, we can use device category and device model 
in the DNS name format.


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
CPS Lab Website:
Personal Homepage:

On Wed, Nov 19, 2014 at 7:46 AM, Stuart Cheshire <> wrote:

On 17 Nov, 2014, at 17:33, Mr. Jaehoon Paul Jeong <> 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): <>

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