Design Considerations for Name Resolution Service in ICN
draft-irtf-icnrg-nrs-requirements-04

Document Type Active Internet-Draft (icnrg RG)
Authors Jungha Hong  , Taewan You  , Lijun Dong  , Cedric Westphal  , Börje Ohlman 
Last updated 2020-10-27 (latest revision 2020-10-09)
Replaces draft-hong-icnrg-nrs-requirements, draft-dong-icnrg-nrs-requirement
Stream IRTF
Intended RFC status Informational
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Stream IRTF state IRSG Review
Revised I-D Needed
Consensus Boilerplate Unknown
Document shepherd David Oran
Shepherd write-up Show (last changed 2020-03-19)
IESG IESG state I-D Exists::Revised I-D Needed
Telechat date
Responsible AD (None)
Send notices to David Oran <daveoran@orandom.net>
ICN Research Group                                               J. Hong
Internet-Draft                                                    T. You
Intended status: Informational                                      ETRI
Expires: April 12, 2021                                          L. Dong
                                                             C. Westphal
                                             Futurewei Technologies Inc.
                                                               B. Ohlman
                                                                Ericsson
                                                         October 9, 2020

        Design Considerations for Name Resolution Service in ICN
                  draft-irtf-icnrg-nrs-requirements-04

Abstract

   This document provides the functionalities and design considerations
   for a Name Resolution Service (NRS) in ICN.  An 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.  This
   document is a product of the Information-Centric Networking Research
   Group (ICNRG).

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

Copyright Notice

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

Hong, et al.             Expires April 12, 2021                 [Page 1]
Internet-Draft        Design Considerations for NRS         October 2020

   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.  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 considerations 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.  Conclusion  . . . . . . . . . . . . . . . . . . . . . . . . .  14
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
     7.1.  Accessibility . . . . . . . . . . . . . . . . . . . . . .  14
     7.2.  Authentication  . . . . . . . . . . . . . . . . . . . . .  15
     7.3.  Confidentiality . . . . . . . . . . . . . . . . . . . . .  15
     7.4.  Resiliency  . . . . . . . . . . . . . . . . . . . . . . .  15
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  15
Show full document text