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

"Mr. Jaehoon Paul Jeong" <> Tue, 25 November 2014 03:54 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id D00771A1B8A for <>; Mon, 24 Nov 2014 19:54:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.999
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id RUF0aeAt42-p for <>; Mon, 24 Nov 2014 19:54:15 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4001:c03::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 7E3AC1A1B7D for <>; Mon, 24 Nov 2014 19:54:14 -0800 (PST)
Received: by with SMTP id rl12so10227789iec.33 for <>; Mon, 24 Nov 2014 19:54:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ZjuGmKO5r99Xhx2nxKDEUCMPrf1Wme1FoL7FcX9PebU=; b=SEqtzw8+DyZVovBP0pzG6krnGeziyh0W4Egh9iGZfzTOHGtbSxkih5TDeuTl8bTQSq PukYdUlXTgQyYlqliq/RuwRshgkwK+LS8CfS5h9IvCjyTqypNQxEtrJlG9d1ji9sWaWf AVK96FAaXqNw7CXAOZLiJWXjUHZ2GWN3rl10cuMiwLIVQNiwGqXlOxbzFGFzY+WZBBfq rOqeJC5+PXy2wh84wSlLilJaZZHuYmL6zUn1sq6LKKtmsa02wVeU+2U5tRN2MsJ6vob/ /9r4X9lnZ0g/7egR9GRGFk+N5TrEKo8JqsGO5/kMH818U4EHEwurYP3nA9SD1eIdq/qi hMsw==
MIME-Version: 1.0
X-Received: by with SMTP id g19mr15671142igt.40.1416887653092; Mon, 24 Nov 2014 19:54:13 -0800 (PST)
Received: by with HTTP; Mon, 24 Nov 2014 19:54:12 -0800 (PST)
In-Reply-To: <>
References: <> <> <> <> <> <> <> <> <> <> <> <>
Date: Tue, 25 Nov 2014 12:54:12 +0900
Message-ID: <>
From: "Mr. Jaehoon Paul Jeong" <>
To: Ted Lemon <>
Content-Type: multipart/alternative; boundary=047d7bdc15b23fd81b0508a6dd79
Cc: Brian Haberman <>, Jung-Soo Park <>, Sejun Lee <>, "" <>, Myung-Ki Shin <>
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: Tue, 25 Nov 2014 03:54:17 -0000

I agree that mDNS with 850 bytes in binary does not require so much in
However, every engineer for IoT devices must implement much more source
code than 850 bytes for
a simple DNS name autoconfiguration.
On the other hand, my proposal will require much less source code than
allowing the engineers to make less efforts.
This is my point.


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 Tue, Nov 25, 2014 at 11:42 AM, Ted Lemon <> wrote:

> On Nov 24, 2014, at 8:01 PM, Mr. Jaehoon Paul Jeong <
>> wrote:
> > In order to lead the early deployment of IoT into the reality,
> > a simple light DNS naming approach with only IPv6 stateless
> autoconfiguration
> > will be beneficial for LLN IoT devices while the mDNS approach is used
> for appliances
> > and computers in home networks.
> You have said this numerous times.   However, in order to get IETF
> consensus on some work you want to do, you need to do more than say what
> work you want to do.   You also have to convince some IETF working group to
> adopt the work you want to do.   Stuart Cheshire gave you a pretty good
> summary of what you need to do to convince the working group that this work
> is worth doing.
> Can you please read what Stuart wrote and try to do as he asked?   Please
> understand that if you can't show that your solution is so much smaller
> than an mDNS implementation that it makes sense to do it, there is no
> chance that this working group, or any other working group in the IETF,
> will agree to take on the work you propose to do, as you propose to do it.
> "As you propose to do it" is really important, though.   If there is some
> problem you have that is not addressed by existing mDNS standards or by
> standards currently being contemplated by this working group, then you
> should try to explain how that problem is different from the problems mDNS
> already solves.   In that case, even if the working group doesn't agree to
> work on your specific solution to the problem, we may decide that the
> problem you want to solve is important, and may therefore agree to work on
> a solution to that problem.