Design Guidelines for Name Resolution Service in ICN
draft-irtf-icnrg-nrs-requirements-03

Document Type Active Internet-Draft (icnrg RG)
Last updated 2019-11-04
Replaces draft-hong-icnrg-nrs-requirements, draft-dong-icnrg-nrs-requirement
Stream IRTF
Intended RFC status Informational
Formats plain text xml pdf htmlized bibtex
Stream IRTF state In RG Last Call
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: May 7, 2020                                                ETRI
                                                                 L. Dong
                                                             C. Westphal
                                             Futurewei Technologies Inc.
                                                               B. Ohlman
                                                                Ericsson
                                                       November 04, 2019

          Design Guidelines for Name Resolution Service in ICN
                  draft-irtf-icnrg-nrs-requirements-03

Abstract

   This document discusses the functionalities and design guidelines 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, another
   name, etc. 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 7, 2020.

Copyright Notice

   Copyright (c) 2019 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

Hong, et al.               Expires May 7, 2020                  [Page 1]
Internet-Draft          Design Guidelines for NRS          November 2019

   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.  Name Resolution Service in ICN  . . . . . . . . . . . . . . .   4
     2.1.  Explicit name resolution approach . . . . . . . . . . . .   4
     2.2.  Name-based routing approach . . . . . . . . . . . . . . .   4
     2.3.  Hybrid approach . . . . . . . . . . . . . . . . . . . . .   5
     2.4.  Comparisons of name resolution approaches . . . . . . . .   5
   3.  Functionalities of NRS in ICN . . . . . . . . . . . . . . . .   6
     3.1.  Support heterogeneous name types  . . . . . . . . . . . .   6
     3.2.  Support producer mobility . . . . . . . . . . . . . . . .   7
     3.3.  Support scalable routing system . . . . . . . . . . . . .   9
     3.4.  Support off-path caching  . . . . . . . . . . . . . . . .   9
     3.5.  Support nameless object . . . . . . . . . . . . . . . . .  10
     3.6.  Support manifest  . . . . . . . . . . . . . . . . . . . .  10
     3.7.  Support metadata  . . . . . . . . . . . . . . . . . . . .  10
   4.  Design guidelines for NRS in ICN  . . . . . . . . . . . . . .  11
     4.1.  Resolution response time  . . . . . . . . . . . . . . . .  11
     4.2.  Response accuracy . . . . . . . . . . . . . . . . . . . .  11
     4.3.  Resolution guarantee  . . . . . . . . . . . . . . . . . .  12
     4.4.  Resolution fairness . . . . . . . . . . . . . . . . . . .  12
     4.5.  Scalability . . . . . . . . . . . . . . . . . . . . . . .  12
     4.6.  Manageability . . . . . . . . . . . . . . . . . . . . . .  13
     4.7.  Deployed system . . . . . . . . . . . . . . . . . . . . .  13
     4.8.  Fault tolerance . . . . . . . . . . . . . . . . . . . . .  13
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
     6.1.  Accessibility . . . . . . . . . . . . . . . . . . . . . .  14
     6.2.  Authentication  . . . . . . . . . . . . . . . . . . . . .  14
     6.3.  Data confidentiality  . . . . . . . . . . . . . . . . . .  14
     6.4.  Privacy protection  . . . . . . . . . . . . . . . . . . .  15
     6.5.  Robustness/resiliency . . . . . . . . . . . . . . . . . .  15
     6.6.  Network privacy . . . . . . . . . . . . . . . . . . . . .  15
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  15
Show full document text