Architectural Considerations of ICN using Name Resolution Service
draft-irtf-icnrg-nrsarch-considerations-05

Document Type Active Internet-Draft (icnrg RG)
Authors Jungha Hong  , Taewan You  , Ved Kafle 
Last updated 2020-10-12 (latest revision 2020-09-09)
Replaces draft-hong-icnrg-nrs-requirements
Stream IRTF
Intended RFC status Informational
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Stream IRTF state Awaiting IRSG Reviews
Consensus Boilerplate Yes
Document shepherd David Oran
Shepherd write-up Show (last changed 2020-09-16)
IESG IESG state I-D Exists
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: March 13, 2021                                         V. Kafle
                                                                    NICT
                                                       September 9, 2020

   Architectural Considerations of ICN using Name Resolution Service
               draft-irtf-icnrg-nrsarch-considerations-05

Abstract

   This document describes architectural considerations and implications
   related to the use of a Name Resolution Service (NRS) in Information-
   Centric Networking (ICN).  It explains how the ICN architecture can
   change when an NRS is utilized and how its use influences the ICN
   routing system.  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 March 13, 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
   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

Hong, et al.             Expires March 13, 2021                 [Page 1]
Internet-Draft    Arch Considerations of ICN using NRS    September 2020

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Background  . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Implications of NRS in ICN  . . . . . . . . . . . . . . . . .   5
   5.  ICN Architectural Considerations for NRS  . . . . . . . . . .   6
     5.1.  Name mapping records registration, resolution, and update   6
     5.2.  Protocols and Semantics . . . . . . . . . . . . . . . . .   8
     5.3.  Routing System  . . . . . . . . . . . . . . . . . . . . .   8
   6.  Conclusion  . . . . . . . . . . . . . . . . . . . . . . . . .   9
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  10
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   Information-Centric Networking (ICN) is an approach to evolving the
   Internet infrastructure to provide direct access to Named Data
   Objects (NDOs) by name.  In two common ICN architectures, NDN [NDN]
   and CCNx [CCNx], the name of an NDO is used directly to route a
   request to retrieve the data object.  Such direct name-based routing
   has inherent challenges in enabling a globally scalable routing
   system, accommodating producer mobility, and supporting off-path
   caching.  These specific issues are discussed in detail in Section 3.
   In order to address these challenges, a Name Resolution Service (NRS)
   has been utilized in literature as well as the proposals of several
   ICN projects [Afanasyev] [Zhang2] [Ravindran] [SAIL] [MF] [Bayhan].

   This document describes the potential changes in the ICN architecture
   caused by the introduction of NRS and the corresponding implication
   to the ICN routing system.  It also describes ICN architectural
   considerations for the integration of an NRS.  The scope of this
   document includes considerations from the perspective of ICN
   architecture and routing system when using an NRS in ICN.  A
   description of the NRS itself is provided in the companion NRS design
Show full document text