Skip to main content

Requirements of Name Resolution Service in ICN

Document Type Replaced Internet-Draft (individual)
Authors Lijun Dong , Cedric Westphal , Guoqiang Wang , Jianping Wang
Last updated 2017-01-22 (Latest revision 2016-07-21)
Replaced by RFC 9138
Stream (None)
Intended RFC status (None)
Expired & archived
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-irtf-icnrg-nrs-requirements
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


This document summarizes the existing approaches for name resolution in various ICN architectures, and categorizes them into two groups: (1) standalone name resolution; (2) name based routing. It compares the two types of approaches from the aspects of update message overhead, resolution capability, node failure impact, and maintained database. And hybrid approaches also exist with a subnet of routers carrying out name based routing. Despite the coexistence of different name resolution approaches, the Name Resolution Service (NRS) is most essential service that shall be provided by the ICN infrastructure. The document gives the definition of NRS in ICN and proposes some requirements of NRS, i.e. resolution guarantee, delay sensitivity, minimum inter-domain traffic, failure resilience, accuracy, security and accessibility, scalability, and time transiency, support for manifest, interoperability, resolution result selection, heterogeneity, unspecified Content Name.


Lijun Dong
Cedric Westphal
Guoqiang Wang
Jianping Wang

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)