Re: Request for Comments on Internet Draft about IoT DNS Name Autoconf

manning <bmanning@karoshi.com> Fri, 17 July 2015 04:26 UTC

Return-Path: <bmanning@karoshi.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B813E1ACD7B for <ipv6@ietfa.amsl.com>; Thu, 16 Jul 2015 21:26:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.41
X-Spam-Level:
X-Spam-Status: No, score=-2.41 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_22=0.6, J_CHICKENPOX_24=0.6, J_CHICKENPOX_28=0.6, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] 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 qn8XAycuTO2U for <ipv6@ietfa.amsl.com>; Thu, 16 Jul 2015 21:26:38 -0700 (PDT)
Received: from vacation.karoshi.com (vacation.karoshi.com [198.32.6.68]) by ietfa.amsl.com (Postfix) with ESMTP id A880E1ACD8B for <ipv6@ietf.org>; Thu, 16 Jul 2015 21:26:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by vacation.karoshi.com (Postfix) with ESMTP id 29C78A6A5C9; Thu, 16 Jul 2015 21:26:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at karoshi.com
Received: from vacation.karoshi.com ([127.0.0.1]) by localhost (vacation.karoshi.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gEK8zdvH7BNj; Thu, 16 Jul 2015 21:26:27 -0700 (PDT)
Received: from [198.32.4.206] (unknown [198.32.4.206]) by vacation.karoshi.com (Postfix) with ESMTPSA id 844B3A6A5BA; Thu, 16 Jul 2015 21:26:27 -0700 (PDT)
Subject: Re: Request for Comments on Internet Draft about IoT DNS Name Autoconf
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: text/plain; charset="us-ascii"
From: manning <bmanning@karoshi.com>
In-Reply-To: <CAPK2DextYY=pJ_4D8wGn2Fb9fUBOkuFR93ksx0ZYCd88K76h_A@mail.gmail.com>
Date: Thu, 16 Jul 2015 21:26:34 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <66EFA3EF-8BA5-4040-99F5-E68EC346E625@karoshi.com>
References: <CAPK2DexcdtrfdA6dKNF6OcjjPzSAt6DnN0poJ86x-evYRVdiHA@mail.gmail.com> <CA+9kkMAd5_fufdVUru6ZordE+ro5NwhySLeb9XnR=qSjhhvmdg@mail.gmail.com> <C521D18C-2A60-4F7F-A848-CB612F45E411@karoshi.com> <CAPK2DextYY=pJ_4D8wGn2Fb9fUBOkuFR93ksx0ZYCd88K76h_A@mail.gmail.com>
To: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/3X-RbReiNGMsIHWTfCqm1Wb7YWM>
Cc: 6MAN WG <ipv6@ietf.org>, Hyunjong Jeon <hjjeon@jubix.co.kr>, Myung-Ki Shin <mkshin@etri.re.kr>, Brian Haberman <brian@innovationslab.net>, Jung-Soo Park <pjs@etri.re.kr>, Kyemyung Jung <jubix@jubix.co.kr>, Sejun Lee <prosejun14@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jul 2015 04:26:44 -0000

The reason I ask is that the title is about DNS name autoconfig.  It might be reasonable to run a parallel stream in DNSOPs, in the unlikely event of problems.
manning
bmanning@karoshi.com
PO Box 12317
Marina del Rey, CA 90295
310.322.8102



On 16July2015Thursday, at 12:19, Mr. Jaehoon Paul Jeong <jaehoon.paul@gmail.com> wrote:

> Hi Manning,
> Sure, my proposal can be discussed in DNSOPS WG.
> Since my proposal uses IPv6 ND(neighbor discovery) and NI(node information) query,
> 6MAN WG will be a good place to discuss it first.
> After that, if needed, I will be able to introduce it to DNSOPS WG.
> 
> Thanks.
> 
> Paul
> 
> On Fri, Jul 17, 2015 at 2:29 AM, manning <bmanning@karoshi.com> wrote:
> Ted et.al.   Is there a good reason this is not being discussed in the DNSOPS WG?
> 
> 
> manning
> bmanning@karoshi.com
> PO Box 12317
> Marina del Rey, CA 90295
> 310.322.8102
> 
> 
> 
> On 14July2015Tuesday, at 11:16, Ted Hardie <ted.ietf@gmail.com> wrote:
> 
> > Dear Professor Jeong,
> >
> > Thank you for sharing the update to your draft.  I note that in the security section of your draft that you make the following proposal:
> >   to prevent the disclosure of location information for privacy
> >   concern, the subdomains related to location can be encrypted by a
> >   shared key or public-and-private keys.  For example, a DNS name of
> >   smartphone1.living_room.home can be represented as
> >   smartphone1.xxx.home where xxx is a string of the encrypted
> >   representation of the subdomain living_room.
> >
> > First, I believe that there are more privacy concerns here than location privacy.  The base format:
> >
> >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >    | unique_id.device_model.device_category.mic_loc.mac_loc.domain_name|
> >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >
> >
> > proposes to include both the device model and a unique identifier.
> > A naive implementation could easily select its serial number, which
> > would clearly be problematic; even the device model may be an issue for certain cases (e.g. a medical device).
> >
> > Second, the delegation model here seems to require a consistent view  of both device categories and location names.  How do you see that being produced?
> >
> > Lastly, the privacy mitigation given is not yet clear to me.  How would a user of the DNS determine how to decrypt the encrypted strings?  If the point of the effort is autoconfiguration, relying on out-of-band configuration for this  seems contrary to the goal.  If you distribute the decryption keys within the DNS, however, you are likely to lose whatever privacy protection is provided.  Can you explain this further?
> > regards,
> >
> > Ted Hardie
> >
> >
> > On Tue, Jul 14, 2015 at 6:31 AM, Mr. Jaehoon Paul Jeong <jaehoon.paul@gmail.com> wrote:
> > Hi 6MAN WG,
> > This is Paul.
> >
> > I would like to let you know a draft for IoT Device DNS Name Autoconfiguration:
> >
> > ----------------------------------------------------------------------------
> > DNS Name Autoconfiguration for Internet of Things Devices
> > (draft-jeong-homenet-device-name-autoconf-03)
> >
> > https://tools.ietf.org/html/draft-jeong-homenet-device-name-autoconf-03
> >
> > Abstract
> >    This document specifies an autoconfiguration scheme for DNS names of
> >    Internet of Things (IoT) devices, such as appliances and sensors.  By
> >    this scheme, the DNS name of an IoT device can be autoconfigured with
> >    the device's category and model in wired and wireless networks (e.g.,
> >    home, office, shopping mall, smart grid, and road network).  This DNS
> >    name lets IoT users (e.g., home residents and customers) easily
> >    identify each device for monitoring and remote-controlling it in a
> >    target network.
> > ----------------------------------------------------------------------------
> >
> > This draft is a follow-up IETF draft of RFC6106-bis for IPv6 RA RDNSS and
> > DNSSL options for IPv6 Host DNS Configuration:
> >
> > https://tools.ietf.org/html/draft-jeong-6man-rdnss-rfc6106-bis-00
> >
> > For this draft, three organizations (i.e., SKKU, ETRI, and Jubix)
> > are developing a prototype of our proposed IoT DNS name autoconfiguration
> > on top of a smart grid platform to collect the usage of electonic meters over
> > IPv6/6lo/SUN (Smart Utility Network, IEEE 802.15.4g) in a smart grid in
> > Korea Electric Power Corporation (KEPCO).
> >
> > We believe that the proposed scheme will be useful in a variety of
> > environments using IPv6, such as smart grid, smart home, smart mall, smart factory,
> > and smart Intelligent Transportation Systems (ITS).
> >
> > I think that this IoT DNS name autoconfiguration will be an enabler such that
> > IPv6 will be a key network layer of such IoT environments.
> >
> > In this IETF meeting, I will briefly introduce this scheme along with our prototype.
> > Please read our draft and give us your comments by email before the 6MAN WG
> > meeting in Prague:
> >
> > https://tools.ietf.org/html/draft-jeong-homenet-device-name-autoconf-03
> >
> > Thanks.
> >
> > Paul
> > ===========================
> > Jaehoon (Paul) Jeong
> > Assistant Professor
> > Department of Software
> > Sungkyunkwan University
> > Mobile: +82-10-4758-1765
> > Email: pauljeong@skku.edu, jaehoon.paul@gmail.com
> > URI: http://cpslab.skku.edu/people-jaehoon-jeong.php
> >
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
> >
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
> 
> 
> 
> 
> -- 
> ===========================
> Mr. Jaehoon (Paul) Jeong, Ph.D.
> Assistant Professor
> Department of Software
> Sungkyunkwan University
> Office: +82-31-299-4957
> Email: jaehoon.paul@gmail.com, pauljeong@skku.edu
> Personal Homepage: http://cpslab.skku.edu/people-jaehoon-jeong.php