Architectural Considerations of ICN using Name Resolution Service
draft-hong-icnrg-icnnrs-01

Document Type Active Internet-Draft (individual)
Last updated 2018-07-02
Stream (None)
Intended RFC status (None)
Formats plain text xml 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)
ICN Research Group                                               J. Hong
Internet-Draft                                                    T. You
Intended status: Informational                                 Y-G. Hong
Expires: January 3, 2019                                            ETRI
                                                            July 2, 2018

   Architectural Considerations of ICN using Name Resolution Service
                       draft-hong-icnrg-icnnrs-01

Abstract

   This document discusses architectural considerations and implications
   of Information-Centric Networking (ICN) related to the usage of the
   Name Resolution Service (NRS).  It describes how ICN architecture
   changes and what implications are in the routing system when NRS is
   utilized in ICN.

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 January 3, 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
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of

Hong, et al.             Expires January 3, 2019                [Page 1]
Internet-Draft    Arch Considerations of ICN using NRS         July 2018

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions and Terminology . . . . . . . . . . . . . . . . .   3
   3.  Background  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Implications of NRS in ICN  . . . . . . . . . . . . . . . . .   4
   5.  ICN Architectural Considerations for NRS  . . . . . . . . . .   4
     5.1.  Resolution  . . . . . . . . . . . . . . . . . . . . . . .   4
     5.2.  Protocols and Semantics . . . . . . . . . . . . . . . . .   5
     5.3.  Routing System  . . . . . . . . . . . . . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
     6.1.  Name Space Separation . . . . . . . . . . . . . . . . . .   6
     6.2.  NRS System  . . . . . . . . . . . . . . . . . . . . . . .   6
     6.3.  NRS Protocols and Messages  . . . . . . . . . . . . . . .   6
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   Information-Centric Networking (ICN) is an approach to evolve the
   Internet infrastructure to directly access Named Data Objects (NDOs)
   by its name, i.e., the name of NDO is directly used to route the
   request to the data object.  Such name based routing in ICN poses a
   number of issues, which are not solved yet in ICN.  These issues
   includes global scalability of routing, producer mobility, off-path
   cache, etc.  In order to address these issues, the name resolution
   function has been applied to several ICN projects and literature
   [Afanasyev][Zhang2][Ravindran][MF][Bayhan].

   The requirements of Name Resolution Service (NRS) has been discussed
   in [NRS] which focus on designing NRS itself in terms of service,
   system and security aspects.  As implementation of NRS, few NRS
   systems has been introduced in ICNRG.  [BNRS] is an NRS system
   utilizing bloom filter to support a flat name based routing and
   [NRS_CCNx] is another NRS implemented on CCNx to support a scalable
   routing system for CCN.  [NRS] has been well discussed on the
   considerations and requirements of NRS.  However, it is necessary to
   discuss the ICN architectural issues considered when NRS system is
   implemented in ICN.

   Thus, this document describes how ICN architecture changes and what
   implications are in the routing system when Name Resolution Sevice
Show full document text