A Naming System for IOT Objects
draft-pskim-dnsop-namesystem-iotobject-00

Document Type Active Internet-Draft (individual)
Last updated 2019-03-09
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                             P. Kim
Internet-Draft                              Korea Polytechnic University
Intended status: Experimental                                     
Expires: September 7, 2019                                            
                                                           March 9, 2019

                    A Naming System for IOT Objects 
               draft-pskim-dnsop-namesystem-iotobject-00

Abstract

   This draft suggests an object-centric naming system including name 
   space and name resolution system for the IOT environment. A name 
   space is defined to cover diverse IOT objects. To consider 
   scalability and distributed architecture, the format of the name 
   space consists of object category, local name, domain name, and 
   parameters. Then, registries and servers are introduced to manage 
   mapping between identifier and object names with one-to-many 
   relationship. Then, name registration and resolution using these 
   registries and servers are described. 
      
Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on September 7, 2019.

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   
Kim                      Expires September 7, 2019               [Page 1]
Internet-Draft         A Naming System for IOT Objects         March 2019

   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . 2
   2.  A Name Space for Diverse IOT Objects  . . . . . . . . . . . . 3
   3.  A Name Resolution System  . . . . . . . . . . . . . . . . . . 4
     3.1.  Components and Functions  . . . . . . . . . . . . . . . . 4
     3.2.  Name Registration and Resolution . .. . . . . . . . . . . 5
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
   5.  References  . . . . . . . . . . . . . . . . . . . . . . . . . 6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . . 7

1.  Introduction

   With the arriving of Internet of things(IOT) which refers to the 
   connection of billions of physical devices around the world to the 
   Internet, the naming system including name(or identifier) and 
   resolution is considered as one of essential elements to name 
   each IoT device[1]-[5]. 

   Although the IP address is performing a primary role at the data 
   plane as well as the control plane in legacy Internet architecture, 
   it has generally a human-unfriendly. Thus, a human readable name 
   space should be required for binding and resolution. The name space 
   can be classified by "host-centric" as well as "object-centric". The 
   host-centric name space names only host as shown in well-known 
   Domain Name System (DNS)[2]. On the other hand, the object-centric 
   name space can name diverse IOT objects such as user, file, device, 
   service, content, context as well as host, as shown in Future 
   Internet(FI) and Digital Object Architecture(DOA)[3]-[5]. This means 
   that IOT objects would not be limited by the host. Hence, the name 
   space should be designed with consideration of the scalability for 
   tremendous IOT objects.

   In addition, as the registration and resolution between name and 
   identifier(or locator) has been required, a name resolution system 
   should be also required in order to take care of the functions 
   necessary to perform the management of mapping between name and 
   identifier, including ensuring that names are unique, and managing 
   the list of identifiers and names. According to the name resolution 
   manner, the naming system can be classified by "lookup-by-name" and 
   "route-by-name". The lookup-by-name based approach uses an 
Show full document text