Requirements for Name Resolution Service in ICN
draft-jhong-icnrg-nrs-requirements-02

Document Type Active Internet-Draft (individual)
Last updated 2017-10-30
Stream (None)
Intended RFC status (None)
Formats plain text xml 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)
ICN Research Group                                               J. Hong
Internet-Draft                                                      ETRI
Intended status: Informational                                   L. Dong
Expires: May 3, 2018                                              Huawei
                                                                  T. You
                                                                    ETRI
                                                             C. Westphal
                                                                  Huawei
                                                               Y-G. Hong
                                                                    ETRI
                                                                GQ. Wang
                                                                  Huawei
                                                                 J. Wang
                                               City University Hong Kong
                                                        October 30, 2017

            Requirements for Name Resolution Service in ICN
                 draft-jhong-icnrg-nrs-requirements-02

Abstract

   This document discusses the motivation and requirements for Name
   Resolution Service (NRS) in ICN.  The NRS in ICN is to translate an
   object name into some other information such as locator and another
   name which is used for forwarding the object request.

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 May 3, 2018.

Hong, et al.               Expires May 3, 2018                  [Page 1]
Internet-Draft            Requirements for NRS              October 2017

Copyright Notice

   Copyright (c) 2017 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
   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Conventions and Terminology . . . . . . . . . . . . . . . . .   4
   3.  Name Resolution Service in ICN  . . . . . . . . . . . . . . .   4
     3.1.  Standalone name resolution approach . . . . . . . . . . .   4
     3.2.  Name based routing approach . . . . . . . . . . . . . . .   4
     3.3.  Hybrid approach . . . . . . . . . . . . . . . . . . . . .   5
     3.4.  Comparisons of name resolution approaches . . . . . . . .   5
   4.  Motivation of NRS in ICN  . . . . . . . . . . . . . . . . . .   6
     4.1.  Heterogeneous names in ICN  . . . . . . . . . . . . . . .   6
     4.2.  Dynamism in ICN . . . . . . . . . . . . . . . . . . . . .   7
     4.3.  Routing system in ICN . . . . . . . . . . . . . . . . . .   8
     4.4.  Use cases of NRS  . . . . . . . . . . . . . . . . . . . .   8
       4.4.1.  Flat name based routing support . . . . . . . . . . .   8
       4.4.2.  Publisher mobility support  . . . . . . . . . . . . .   9
       4.4.3.  Scalable routing support  . . . . . . . . . . . . . .   9
       4.4.4.  Nameless object support . . . . . . . . . . . . . . .  10
   5.  Requirements for NRS in ICN . . . . . . . . . . . . . . . . .  10
     5.1.  Requirements as a service . . . . . . . . . . . . . . . .  10
       5.1.1.  Delay sensitivity . . . . . . . . . . . . . . . . . .  10
       5.1.2.  Accuracy  . . . . . . . . . . . . . . . . . . . . . .  10
       5.1.3.  Resolution guarantee  . . . . . . . . . . . . . . . .  10
     5.2.  Requirements as a system  . . . . . . . . . . . . . . . .  11
       5.2.1.  Scalability . . . . . . . . . . . . . . . . . . . . .  11
       5.2.2.  Manageability . . . . . . . . . . . . . . . . . . . .  11
       5.2.3.  Deployability . . . . . . . . . . . . . . . . . . . .  11
Show full document text