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

Document Type Active Internet-Draft (individual)
Last updated 2017-07-03
Stream (None)
Intended RFC status (None)
Formats plain text 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)
ICNRG                                                                        J. Hong
Internet-Draft                                                                   ETRI
Intended status: Informational                                    Lijun Dong
Expires: January 4, 2018                                                Huawei
                                                                                   T. You
                                                                                      ETRI
                                                                      Cedric Westphal
                                                                                  Huawei
                                                                             Y-G. Hong
                                                                                      ETRI
                                                                               GQ Wang
                                                                                  Huawei
                                                                        Jianping Wang
                                                        City University Hong Kong
                                                                           July 3, 2017
 

              Requirements for Name Resolution Service in ICN
                draft-jhong-icnrg-nrs-requirements-01.txt

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 http://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 January 4, 2018.

Hong, et al.           Expires January 4, 2018                [Page 1]
Internet-Draft            NRS Requirements                   July 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
   (http://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.

Hong, et al.           Expires January 4, 2018                [Page 2]
Internet-Draft            NRS Requirements                   July 2017

Table of Contents

   1. Introduction .............................................................. 3
   2. Conventions and terminology ...................................... 5
   3. Name Resolution Service in ICN  .................................. 5
   4. Motivation of NRS in ICN  ............................................ 8
      4.1. Handling Heterogeneous Names in ICN ................... 8
      4.2. Handling Dynamism in ICN ..................................... 9
      4.3. Use cases of NRS ................................................ 9
         4.3.1. Flat Name routing support ................................ 9
         4.3.2. Publisher Mobility support ............................... 10
         4.3.3. Scalable Routing support ................................ 11
         4.3.4. Nameless object support  ............................... 12
   5. Requirements for NRS in ICN ...................................... 12
      5.1. Service aspect .................................................... 12
         5.1.1. Delay sensitivity ............................................. 12
         5.1.2. Time transiency ............................................. 13
         5.1.3. Resolution guarantee ...................................... 13
         5.1.4. Accuracy ...................................................... 13
      5.2. System aspects ................................................... 13
Show full document text