Re: [DNSOP] Request for Comments on I-D about IoT DNS Name Autoconf

Stuart Cheshire <> Mon, 09 November 2015 20:24 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id C7ADF1B8393 for <>; Mon, 9 Nov 2015 12:24:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -100.963
X-Spam-Status: No, score=-100.963 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, HTML_IMAGE_RATIO_02=0.437, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id AZlRuw6p3k8V for <>; Mon, 9 Nov 2015 12:24:37 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D51051B8394 for <>; Mon, 9 Nov 2015 12:24:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256;; s=mailout2048s; c=relaxed/simple; q=dns/txt;; t=1447100677; x=2311014277; h=From:Sender:Reply-To:Subject:Date:Message-id:To:Cc:MIME-version:Content-type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-reply-to:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=q9YwCCHbcu53IaN3YasbJvEB3sDKxIaFT1ho1npl6lw=; b=N1bM0KIG0yT2BqXWFy9AYQ3f8blskusf8JgSxfkrMjvzZyCQGQlM1Nn2NOIAC2Q8 zQJZXQzV5qD02hJtkV6KnMskAxnFZENyFiGysWfP8CsQ4R+l0ygZ2gWb0v74a43w zkGqOf9l8n17eVLs/YiB7aswtrWnLlaazCM3Jaubgh6msYJr7nVUY2EZPSOUNpm9 +XUG5Daydev5oONHfcxKWFsnzV8gOAyqAjC/NegZsw1ddYgg9uomLKepkAXgrL4j 9OyExD7W+4vnlh58TNKOqeojSZh6cl/D0+CIfmVKy/MjkSTqM3LA5sBFoUkmSx4U gkTD/xbpuV/s7Zf9C1AcLw==;
Received: from ( []) by (Apple Secure Mail Relay) with SMTP id 45.3B.27014.50101465; Mon, 9 Nov 2015 12:24:37 -0800 (PST)
X-AuditID: 11973e16-f793c6d000006986-39-56410105c811
Received: from jimbu ( []) (using TLS with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by (Apple SCV relay) with SMTP id 1D.D8.05180.40101465; Mon, 9 Nov 2015 12:24:37 -0800 (PST)
Received: from ( []) by (Oracle Communications Messaging Server 64bit (built Mar 31 2015)) with ESMTPSA id <>; Mon, 09 Nov 2015 12:24:36 -0800 (PST)
Content-type: multipart/alternative; boundary="Apple-Mail=_BA64EA47-90E5-4483-AFAC-432EFE9286A3"
MIME-version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
From: Stuart Cheshire <>
In-reply-to: <>
Date: Mon, 09 Nov 2015 12:24:35 -0800
Message-id: <>
References: <> <> <>
To: "Mr. Jaehoon Paul Jeong" <>
X-Mailer: Apple Mail (2.3096.5)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprNIsWRmVeSWpSXmKPExsUi2FAYrMvK6Bhm0HKX36J5ioDF3TeXWSxe nn3P5MDssWTJT6YAxigum5TUnMyy1CJ9uwSujM6lv9kKDq/irXj8aiNLA2PHD54uRg4OCQET iat/5LoYOYFMMYkL99azdTFycQgJ7GWUmPRoFiNEwkTi7+vNTBCJbiaJt3Pvs0A405kkeq8/ ZAapEhaQkni18jMzyFRmgSSJOz+iQMK8AgYS/682skOU+Eh86JzEAmKzCWhJvPh8hQ3E5hQI luhYOwNsGYuAqsSMw5PYQeYzCyxnkjh5+wgbxCAbiY1TbzJCLD7DKLFm8mWwqSICphKLO/ax QJwqL/FzZQPYqRICk9klvi26zDiBUXgWwlGzkBwFYjMLaEssW/iaGcLWlNjfvZwFwi6S+NbV yIKpRkOi89tEVghbUWJK90N2iPG2EhvO+0OEfSR+7vjABBG2keg7rL+AkXsVo1BuYmaObmae uV5iQUFOql5yfu4mRlBsTrcT28H4cJXVIUYBDkYlHt4J3xzChFgTy4orcw8xSnOwKInzrn5t HSYkkJ5YkpqdmlqQWhRfVJqTWnyIkYmDU6qBsW5VqIhGtiHvzeUFmla7Dzj+W70kza/o5hEW Vq+PpXKedvZb983avfuYBfPZCUVFFhtsWh+r8aqfbrl0OmP1luMZDTG9a/Yr3cpaF/qx7/2i wlNXN15n+Z/u9XGVxSLG+kWZ3EX+x2Ks3Tr+vhJ84xq7d/rBvft8hYuE1zypv3ymXeNR/r2t l5VYijMSDbWYi4oTATPQdw2uAgAA
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrAKsWRmVeSWpSXmKPExsUiON1OVZeV0THM4Hsfp0XzFAGLu28us1i8 PPueyYHZY8mSn0wBjFFcNimpOZllqUX6dglcGZ1Lf7MVHF7FW/H41UaWBsaOHzxdjJwcEgIm En9fb2aCsMUkLtxbz9bFyMUhJNDNJPF27n0WCGc6k0Tv9YfMIFXCAlISr1Z+BrI5OJgFkiTu /IgCCfMKGEj8v9rIDlHiI/GhcxILiM0moCXx4vMVNhCbUyBYomPtDEYQm0VAVWLG4UnsIPOZ BZYzSZy8fYQNYpCNxMapNxkhFp9hlFgz+TLYVBEBU4nFHftYIE6Vl/i5soFpAqPALIQ7ZiG5 A8RmFtCWWLbwNTOErSmxv3s5C4RdJPGtq5EFU42GROe3iawQtqLElO6H7BDjbSU2nPeHCPtI /NzxgQkibCPRd1h/ASP3KkaBotScxEpjvcSCgpxUveT83E2MoGhqKAzewfhnmdUhRgEORiUe 3hc/HMKEWBPLiitzDzGqAE14tGH1BUYplrz8vFQlEV77F0Bp3pTEyqrUovz4otKc1OJDjPsZ gYE1kVlKNDkfmALySuINTUwMTIyNzYyNzU3MB4+wkjjvu1vWYUIC6YklqdmpqQWpRTAvMHFw SjUwtp84uIz7QN7ph5OXb5xQaDZvq3vE4wAeZv6OsonOZ/eLZHFziW7JPrG47n5va55fz23B M4bRSb89PQovSqmtSNcOPXxRLYtzvch6j4/3JlnuNz61OmyjshHXpa5D53mZ7PgaTri4P5dY uvrqiafTF6fGCDi/OSXB0GzErPBrgjDLinXy1tMilFiKMxINtZiLihMBqEok5VMDAAA=
Archived-At: <>
Cc: Brian Haberman <>, IETF IPv6 Mailing List <>, Hyunjong Jeon <>, Myung-Ki Shin <>,, Jung-Soo Park <>, Kyemyung Jung <>,, Sejun Lee <>
Subject: Re: [DNSOP] Request for Comments on I-D about IoT DNS Name Autoconf
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 09 Nov 2015 20:24:40 -0000

On 4 Nov 2015, at 23:14, Mr. Jaehoon Paul Jeong <> wrote:

> Device model (denoted as device_model) in my proposed DNS
> name format can let an IoT device refer to the specification
> of another device's functions, assuming that such a
> device model's specification is available publicly.
> For example, for a given Samsung's refrigerator model, such
> as RF4287HARS (28 cu. ft. French Door Refrigerator Stainless
> Steel), we can know the functions with the specification.
> See Samsung's refrigerators:

Mr Jeong,

Over the last year you have asked the IETF community for feedback on your document on several occasions. Various people have provided feedback, yet your document never changes. You just argue that all the feedback is wrong, and persist with your original proposal. I’m not sure what will be achieved by repeatedly asking for feedback on the same unwavering idea.

You suggest above that the software running on a constrained IoT device should visit the web page you gave, explore the web site to find some document specifying the network functionality provided by the refrigerator model, and the network protocol(s) used to access that functionality (I, as a human, was unable to find that document myself) and then (presumably via some artificial intelligence algorithms) the constrained IoT device would write itself a protocol implementation (and design itself a corresponding user interface) to control the refrigerator. I don’t believe that IoT devices with such artificial intelligence capabilities currently exist outside of Hollywood movies.

In your slides you focus on the example of interfacing to a smart meter over the network (pictured below). But products that do that have been available for a while. I already have one in my house, provided at no charge to me by my local electricity company. This is not some new experimental thing; it’s a mainstream, widely-used product:


When a type of product is readily available for purchase, with a variety of different models from a variety of different vendors, it’s retail, not research.

I believe you could make a much larger contribution by doing something new which builds on the foundation provided by RFC 6762 and RFC 6763, rather than just doing the same thing a different way.

Stuart Cheshire