Architectural Considerations of ICN using Name Resolution Service
draft-hong-icnrg-icnnrs-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2019-01-03 (latest revision 2018-07-02) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-hong-icnrg-icnnrs-01.txt
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 architecture changes and what implications are in the routing system when NRS is utilized in ICN.
Authors
Jungha Hong
(jhong@etri.re.kr)
Taewan You
(twyou@etri.re.kr)
Yong-Geun Hong
(YGHONG@ETRI.RE.KR)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)