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

Document Type Active Internet-Draft (icnrg RG)
Last updated 2019-03-11
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: September 12, 2019                                         ETRI
                                                                 L. Dong
                                                             C. Westphal
                                                                  Huawei
                                                                V. Kafle
                                                                    NICT
                                                               B. Ohlman
                                                                Ericsson
                                                          March 11, 2019

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

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 a locator and another
   name which is used for forwarding the object request towards the
   object location.

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 12, 2019.

Copyright Notice

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

Hong, et al.           Expires September 12, 2019               [Page 1]
Internet-Draft            Requirements for NRS                March 2019

   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
   4.  Objectives of NRS in ICN  . . . . . . . . . . . . . . . . . .   5
     4.1.  To support heterogeneous types of names . . . . . . . . .   5
     4.2.  To support dynamic features . . . . . . . . . . . . . . .   5
     4.3.  To support efficient routing  . . . . . . . . . . . . . .   6
     4.4.  Use cases of NRS  . . . . . . . . . . . . . . . . . . . .   6
       4.4.1.  To support flat name based routing  . . . . . . . . .   6
       4.4.2.  To support producer mobility  . . . . . . . . . . . .   7
       4.4.3.  To support scalable routing system  . . . . . . . . .   7
       4.4.4.  To support off-path caching . . . . . . . . . . . . .   8
       4.4.5.  To support nameless object  . . . . . . . . . . . . .   8
       4.4.6.  To support manifest . . . . . . . . . . . . . . . . .   9
   5.  Requirements for NRS in ICN . . . . . . . . . . . . . . . . .   9
     5.1.  Requirements as a service . . . . . . . . . . . . . . . .   9
       5.1.1.  Resolution response time  . . . . . . . . . . . . . .   9
       5.1.2.  Response accuracy . . . . . . . . . . . . . . . . . .  10
       5.1.3.  Resolution guarantee  . . . . . . . . . . . . . . . .  10
       5.1.4.  Resolution fairness . . . . . . . . . . . . . . . . .  10
     5.2.  Requirements as a system  . . . . . . . . . . . . . . . .  10
       5.2.1.  Scalability . . . . . . . . . . . . . . . . . . . . .  11
       5.2.2.  Manageability . . . . . . . . . . . . . . . . . . . .  11
       5.2.3.  Deployed system . . . . . . . . . . . . . . . . . . .  11
       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  . . . . . . . . . . . . . . . .  13
Show full document text