Requirements for Name Resolution Service in ICN
draft-irtf-icnrg-nrs-requirements-00

Document Type Active Internet-Draft (icnrg RG)
Last updated 2018-10-22 (latest revision 2018-10-17)
Replaces draft-hong-icnrg-nrs-requirements, draft-dong-icnrg-nrs-requirement
Stream IRTF
Intended RFC status Informational
Formats plain text xml pdf html bibtex
Stream IRTF state Active RG Document
Consensus Boilerplate Unknown
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
ICN Research Group                                               J. Hong
Internet-Draft                                                    T. You
Intended status: Informational                                 Y-G. Hong
Expires: April 20, 2019                                             ETRI
                                                             C. Westphal
                                                                  Huawei
                                                                V. Kafle
                                                                    NICT
                                                        October 17, 2018

            Requirements for Name Resolution Service in ICN
                  draft-irtf-icnrg-nrs-requirements-00

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 April 20, 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

Hong, et al.             Expires April 20, 2019                 [Page 1]
Internet-Draft            Requirements for NRS              October 2018

   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 . . . . . . . . . . . . . . . . .   3
   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 . . . . . . . . . . . . . . . . . . . . .   4
     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 . . . . . . . . . . . . . . . . . .   7
     4.4.  Use cases of NRS  . . . . . . . . . . . . . . . . . . . .   8
       4.4.1.  Flat name based routing support . . . . . . . . . . .   8
       4.4.2.  Producer mobility support . . . . . . . . . . . . . .   8
       4.4.3.  Scalable routing support  . . . . . . . . . . . . . .   9
       4.4.4.  Off-Path cache support  . . . . . . . . . . . . . . .   9
       4.4.5.  Nameless object support . . . . . . . . . . . . . . .  10
       4.4.6.  Menifest support  . . . . . . . . . . . . . . . . . .  10
   5.  Requirements for NRS in ICN . . . . . . . . . . . . . . . . .  11
     5.1.  Requirements as a service . . . . . . . . . . . . . . . .  11
       5.1.1.  Delay sensitivity . . . . . . . . . . . . . . . . . .  11
       5.1.2.  Accuracy  . . . . . . . . . . . . . . . . . . . . . .  11
       5.1.3.  Resolution guarantee  . . . . . . . . . . . . . . . .  11
     5.2.  Requirements as a system  . . . . . . . . . . . . . . . .  11
       5.2.1.  Scalability . . . . . . . . . . . . . . . . . . . . .  11
       5.2.2.  Manageability . . . . . . . . . . . . . . . . . . . .  12
       5.2.3.  Deployability . . . . . . . . . . . . . . . . . . . .  12
       5.2.4.  Fault tolerance . . . . . . . . . . . . . . . . . . .  12
     5.3.  Requirements on Security aspect . . . . . . . . . . . . .  12
       5.3.1.  Accessibility . . . . . . . . . . . . . . . . . . . .  12
       5.3.2.  Authentication  . . . . . . . . . . . . . . . . . . .  12
       5.3.3.  Data confidentiality  . . . . . . . . . . . . . . . .  12
       5.3.4.  Data privacy  . . . . . . . . . . . . . . . . . . . .  13
Show full document text