Requirements for Name Resolution Service in ICN
draft-hong-icnrg-nrs-requirements-00

Document Type Active Internet-Draft (individual)
Last updated 2016-09-29
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)
ICN Research Group                                               J. Hong
Internet-Draft                                                    T. You
Intended status: Informational                                 Y-G. Hong
Expires: April 2, 2017                                              ETRI
                                                      September 29, 2016

            Requirements for Name Resolution Service in ICN
                  draft-hong-icnrg-nrs-requirements-00

Abstract

   This document discusses the motivation and requirements for Name
   Resolution Service (NRS) in ICN.  The NRS in ICN is to translate
   object names into routing hints such as locators, where names are
   location-independent and locators are network addresses.

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 April 2, 2017.

Copyright Notice

   Copyright (c) 2016 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 April 2, 2017                 [Page 1]
Internet-Draft            Requirements for NRS            September 2016

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions and Terminology . . . . . . . . . . . . . . . . .   3
   3.  Motivation  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Requirements for NRS in ICN . . . . . . . . . . . . . . . . .   4
     4.1.  Requirements on Operability . . . . . . . . . . . . . . .   4
       4.1.1.  Scalability . . . . . . . . . . . . . . . . . . . . .   4
       4.1.2.  Low latency . . . . . . . . . . . . . . . . . . . . .   4
       4.1.3.  Fast Update . . . . . . . . . . . . . . . . . . . . .   5
       4.1.4.  Locality  . . . . . . . . . . . . . . . . . . . . . .   5
       4.1.5.  Resilience  . . . . . . . . . . . . . . . . . . . . .   5
       4.1.6.  Fault tolerance / Isolation . . . . . . . . . . . . .   5
     4.2.  Requirements on Manageability . . . . . . . . . . . . . .   5
       4.2.1.  Manageabiliyt . . . . . . . . . . . . . . . . . . . .   5
       4.2.2.  Deployability . . . . . . . . . . . . . . . . . . . .   5
       4.2.3.  Interoperability  . . . . . . . . . . . . . . . . . .   6
     4.3.  Requirements on Security  . . . . . . . . . . . . . . . .   6
       4.3.1.  Access control  . . . . . . . . . . . . . . . . . . .   6
       4.3.2.  Authentication  . . . . . . . . . . . . . . . . . . .   6
       4.3.3.  Data confidentiality  . . . . . . . . . . . . . . . .   6
       4.3.4.  Data integrity  . . . . . . . . . . . . . . . . . . .   6
       4.3.5.  Privacy . . . . . . . . . . . . . . . . . . . . . . .   6
   5.  Use case of NRS . . . . . . . . . . . . . . . . . . . . . . .   6
     5.1.  Lookup by Name Routing (LBNR) . . . . . . . . . . . . . .   6
     5.2.  Route by Name Routing (RBNR)  . . . . . . . . . . . . . .   7
     5.3.  Hybrid Routing (HR) . . . . . . . . . . . . . . . . . . .   7
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   The current Internet is a host-centric networkAhlgrening, where hosts
   are uniquely identified with IP addresses and communication is
Show full document text