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

Document Type Active Internet-Draft (icnrg RG)
Last updated 2020-05-25 (latest revision 2020-03-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 Waiting for Document Shepherd
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: September 10, 2020                                     V. Kafle
                                                                    NICT
                                                          March 09, 2020

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

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 architectures
   may change and what implications are introduced within the ICN
   routing system when NRS is integrated into an ICN architecture.

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 September 10, 2020.

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
   include Simplified BSD License text as described in Section 4.e of

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

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Background  . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Implications of NRS in ICN  . . . . . . . . . . . . . . . . .   5
   5.  ICN Architectural Considerations for NRS  . . . . . . . . . .   5
     5.1.  Name mapping records registration, resolution, and update   5
     5.2.  Protocols and Semantics . . . . . . . . . . . . . . . . .   7
     5.3.  Routing System  . . . . . . . . . . . . . . . . . . . . .   8
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

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 has
   inherent challenges in supporting globally scalable routing system,
   producer mobility, and off-path caching.  In order to address these
   challenges, the Name Resolution Service (NRS) has been integrated
   into several ICN project's proposals and literature [Afanasyev]
   [Zhang2] [Ravindran] [SAIL] [MF] [Bayhan].

   This document describes how ICN architectures may change and what
   implications are introduced within the ICN routing system when NRS is
   integrated into an ICN architecture.  It also discusses ICN
   architectural considerations for an NRS.  In other words, the scope
   of this document includes considerations in the view of the ICN
   architecture and routing system when NRS is integrated into ICN.  The
   discussion of NRS itself is provided in the NRS design guidelines
   [NRSguidelines] document.

2.  Terminology

   o  Name Resolution Service (NRS): NRS in ICN is defined as the
      service that provides the name resolution function for translating
      an object name into some other information such as a locator, a
      off-path-cache pointer, or an alias name for forwarding the object

Hong, et al.           Expires September 10, 2020               [Page 2]
Show full document text