This Internet-Draft will expire on April 20, 2019. This Internet-Draft will expire on September 12, 2019.
is identified by the name of host where the information is stored. is identified by the name of host where the information is stored.
communications [Baccelli] [Amadeo] [Quevedo] [Amadeo2] [ID.Zhang2]. [Baccelli] [Amadeo] [Quevedo] [Amadeo2] [ID.Zhang2].
providers/sources that can provide the content. content producers or sources that can provide the content.
either based on its name or locator. content's location either based on its name or locator.
o Content delivery : transfers the content to the requester. o Content delivery : transfers the content to the requester.
name to manifest, and name to locator.
requirements in designing the NRS for ICN. requirements in designing the NRS for ICN.
a persistent name when the name resolution is needed. host using a persistent name when the name resolution is needed.
based routing approach in this document.
but also properly delivering the data.
the router can go back to the standalone name resolution approach.
can carry out the name based routing of the client's request.
approach may flood the whole network (but mitigating techniques request.
resolution, depending on the flooding scope of the content name for later usage.
resolution approach are the name resolution overlay servers (e.g.
locally maintained name based routing tables (e.g. NDN routers).
back an ACK as a response back to the producer or publisher.
4. Motivation of NRS in ICN o Name resolution: Name resolution is the main process of the NRS.
response message to the NRS resolver.
4.1. Heterogeneous names in ICN This section presents the objectives and use cases of NRS in ICN.
verify the binding of the content and the name.
heterogeneous approaches to designing ICN naming schemes [Bari].
flat, hierarchical, and human readable or non-readable. flat, hierarchical, and human readable or non-readable.
routing. The NRS may combine the good aspects of different schemes.
information with respect to the principal. Name resolution in whether it is flat or hierarchical.
hierarchical Dynamic Hash Table (DHT)[Rajahalme] [Katsaros].
out via a Global Name Resolution Service (GNRS).
either it is flat or hierarchical.
ensures that content reception continues without any disruption in seamless mobility in consumer point of view can be easily supported.
mobility, where NRS can be implemented in different ways such as such as at rendezvous points and overlay mapping systems.
scheme used in CCN and NDN architectures has a structure similar to Routing Information Base (RIB) and Forwarding Information Base (FIB).
system. It is because the hierarchy enables aggregation of the name information bases would be significantly large as well [RFC7927].
information which is routable through NRS.
layer. routing scalability problem regardless of the types of namespaces.
where NRS is performed by the RENE. where NRS is performed by the RENE.
data routing as similar to PURSUIT. data routing as similar to PURSUIT.
ni names to addresses in an underlying routable network layer.
approaches such as chase mobile producer and rendezvous data. approaches such as chase mobile producer and rendezvous data.
as NRS in this draft. as NRS in this draft.
of attachment, which differs from NDN/CCN. of attachment, which differs from NDN/CCN.
is a kind of NRS. is a kind of NRS.
into a name- based routing system or into NRS. into a name- based routing system or into NRS.
access latency for a pleasant user experience. access latency for a pleasant user experience.
matching by using SHA-256 hash. matching by using SHA-256 hash.
be collected by using the manifest. be collected by using the manifest.
terms of service, system and security aspects, respectively. terms of service, system and security aspects.
the resolution incomplete when the timer expires.
the update information. For example, a content can be moved from one responding to this request.
forwarding of the resolution request.
move and require the NRS to be updated.
propagated through the NRS system within reasonable delay.
anchor that is kept at the NRS, instead of the content location.
of cached copies. popularity and number of cached copies existing in the network.
requirements for NRS as a system, which are described below.
of content objects as well as billions of users, who may access the (including human users as well as machine-to-machine communications).
up and name records propagation must be efficient and scalable. scalable.
(or should have impact on only a small subset of the NRS servers).
able to access the NRS system as well as a more powerful node.
where data is being frequently generated and/or frequently requested.
can perform name resolution in a very low latency.
stored in the NRS node. the NRS performance significantly.
or restore the name records stored in the NRS server.
corrupt the name mapping records.
these records would not be shared to unauthorized users.
is authorized to modify this record.
the authentication to ensure who claims to be. For example, the themselves in the NRS system to ensure they are who they claim to be.
NRS system must support the privacy to avoid the information leaking.
Otherwise, unauthorized entity may disclose the privacy.
management protocols that it is supporting.
There are no IANA considerations related to this document. There are no IANA considerations related to this document.