Re: [DNSOP] DNSOP Working Group Update and IETF94 Agenda Requests

"Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com> Sat, 10 October 2015 18:24 UTC

Return-Path: <jaehoon.paul@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB00F1ACD85 for <dnsop@ietfa.amsl.com>; Sat, 10 Oct 2015 11:24:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level:
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, 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 zN3yD36YIk4Z for <dnsop@ietfa.amsl.com>; Sat, 10 Oct 2015 11:24:05 -0700 (PDT)
Received: from mail-yk0-x234.google.com (mail-yk0-x234.google.com [IPv6:2607:f8b0:4002:c07::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76D5E1ACD3A for <dnsop@ietf.org>; Sat, 10 Oct 2015 11:24:05 -0700 (PDT)
Received: by ykdg206 with SMTP id g206so105478950ykd.1 for <dnsop@ietf.org>; Sat, 10 Oct 2015 11:24:04 -0700 (PDT)
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=EnnLimVDf6YptxCvjJuaRMK7Nqs6M0a5llx9l5b7tHI=; b=dvxad8jPxYhfASFEdIIAQ/RH7Jdoww9KwY9bS4iF6md6dyN16h2pasirVllfgx32QU wIg8iRZ9Or6o2mXWUgQBMGqs4cDmPimW5Z6OiOasA3kaMyUUgp2kU/s6DMfZ2Vtr+36h VTcYa+sxFFMoxgZ5qdjm1ssM99EI39di2bldAVvXlFxfWHhG6Z4hwIRTgPdDa+qPCztR lsvVBTAgWjsjOH2gFq/FTKGDbeFSsepoYgmGE6IkfQsW+xpnwEjNZcjuZfGDu7Kq3eLA C6bRIS7Q59nus3Ik0YLyGiUdKRNYm2WlRxTy2r22YcSZpZ1UJtsA14oDoRUdK8qH4nov vExw==
MIME-Version: 1.0
X-Received: by 10.129.107.84 with SMTP id g81mr13994628ywc.288.1444501444548; Sat, 10 Oct 2015 11:24:04 -0700 (PDT)
Received: by 10.129.109.142 with HTTP; Sat, 10 Oct 2015 11:24:04 -0700 (PDT)
In-Reply-To: <56102BF4.1090206@gmail.com>
References: <56102BF4.1090206@gmail.com>
Date: Sun, 11 Oct 2015 03:24:04 +0900
Message-ID: <CAPK2Deyv5iJ9Q9k-qHEmRc7+6A5TVzgGsBciqK+uNH=YOrdx2w@mail.gmail.com>
From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
To: Tim WIcinski <tjw.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="001a1141c10c7ae1bc0521c43313"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/gxb-VAowWuYXBs3NHhXK9J4MDDo>
Cc: dnsop@ietf.org, Myung-Ki Shin <mkshin@etri.re.kr>, Sejun Lee <prosejun14@gmail.com>, suzworldwide@gmail.com, Jung-Soo Park <pjs@etri.re.kr>
Subject: Re: [DNSOP] DNSOP Working Group Update and IETF94 Agenda Requests
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Oct 2015 18:24:07 -0000

Hi Tim,
Could I present the following draft on IoT device DNS name
autoconfiguration in 5 minutes
in DNSOP WG in IETF94?

Title: DNS Name Autoconfiguration for Internet of Things Devices
(https://tools.ietf.org/html/draft-jeong-homenet-device-name-autoconf-04)

Abstract:
This document specifies an autoconfiguration scheme for the global
(or local) 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 target networks (e.g., home, office, shopping
mall, smart grid, and road network).  This DNS name lets IoT users
(e.g., home residents and customers) in the Internet (or local
network) easily identify each device for monitoring and remote-
controlling it in the target network.

This draft proposes the autoconfiguration of IoT devices' global DNS names
with device information (such as device category and device model).
As you know, Multicast DNS (mDNS) in RFC 6762 is designed for networked
devices
in a local link with local DNS names (e.g., .local) rather than in the
Internet with global DNS names.

I believe that the proposed scheme will facilitate the DNS naming service
of lots of IoT devices in terms of configuration and management cost.

We have implemented the prototype of the proposed scheme and tested it
with electricity meters for a smart grid.

Thanks.

Paul




On Sun, Oct 4, 2015 at 4:26 AM, Tim WIcinski <tjw.ietf@gmail.com> wrote:

> Hi
>
>
> Since we (the chairs) took the summer recovering from the .onion IETF Last
> Call,   I wanted to update the working group on what has been accomplished
> and what is currently outstanding.
>
>         The Negative-Trust-Anchor draft is now RFC7646.
>
>         The root-loopback draft is getting ready to be published.
>
>         The dns-terminology draft is in the RFC Editor Queue.
>
> Along with the key-timing and .onion drafts, the Working Group will have
> published 9 drafts this year.  We want to thank you for all your work.
> However, we are not done:
>
> We have *two* Working Group Last Calls on documents that have been through
> a major discussion process, but received *no* mention during the process:
>
>      draft-ietf-dnsop-qname-minimisation-05
>      https://datatracker.ietf.org/doc/draft-ietf-dnsop-qname-minimisation/
>
>
>      draft-ietf-dnsop-cookies-05
>      https://datatracker.ietf.org/doc/draft-ietf-dnsop-cookies/
>
>
> The chairs feel these documents are done and ready to move forward. But it
> does seem bad form to just act unilaterally.
>
> We have one document in Call for Adoption.
>
>      draft-howard-isp-ip6rdns
>      https://datatracker.ietf.org/doc/draft-howard-isp-ip6rdns/
>
> The author has addressed many comments and concerns raised since IETF91
> (Honolulu), and the chairs feel that all concerns have been addressed and
> should be adopted.  Again, there has been no comments since starting call
> for adoption.
>
> —
>
> We have several drafts which have been steadily being worked on and are
> ready for Working Group Last Call:
>
>      draft-ietf-dnsop-alt-tld
>      https://datatracker.ietf.org/doc/draft-ietf-dnsop-alt-tld/
>
>      draft-dnsop-edns-tcp-keepalive
>      https://datatracker.ietf.org/doc/draft-ietf-dnsop-edns-tcp-keepalive/
>
>      draft-dnsop-ietf-dnsop-5966bis
>      https://datatracker.ietf.org/doc/draft-ietf-dnsop-5966bis/
>
> alt-tld may be waiting for keeping RFC6761 discussions, but the other
> tcp-keepalive is more than ready, and 5966bis is ready once I give it
> another editorial read.
>
> —
>
> Saying all of this, we’re putting out  a call for agenda items for
> Yokohama.   Please send your request to dnsop-chairs@ietf.org
>
> We plan on spending the next month(s) moving the levers of the process
> forward.
>
> thanks
>
> tim
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>



-- 
===========================
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