{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2025,9,29]],"date-time":"2025-09-29T08:11:30Z","timestamp":1759133490278,"version":"3.41.0"},"reference-count":16,"publisher":"Association for Computing Machinery (ACM)","issue":"3","license":[{"start":{"date-parts":[[2018,9,7]],"date-time":"2018-09-07T00:00:00Z","timestamp":1536278400000},"content-version":"vor","delay-in-days":0,"URL":"https:\/\/www.acm.org\/publications\/policies\/copyright_policy#Background"}],"content-domain":{"domain":["dl.acm.org"],"crossmark-restriction":true},"short-container-title":["SIGCOMM Comput. Commun. Rev."],"published-print":{"date-parts":[[2018,9,7]]},"abstract":"<jats:p>As a proposed Internet architecture, Named Data Networking (NDN) changes the network communication model from delivering packets to destinations identified by IP addresses to fetching data packets by names. This architectural change leads to changes of host functions and initial configurations. In this paper we present an overview of the basic functions of a host in an NDN network, together with necessary operations to configure an NDN host. We also compare and contrast the functionality and configuration between an NDN host and an IP host, to show the differences resulted from the different architecture designs.<\/jats:p>","DOI":"10.1145\/3276799.3276804","type":"journal-article","created":{"date-parts":[[2018,9,10]],"date-time":"2018-09-10T12:11:14Z","timestamp":1536581474000},"page":"35-41","update-policy":"https:\/\/doi.org\/10.1145\/crossmark-policy","source":"Crossref","is-referenced-by-count":20,"title":["NDN host model"],"prefix":"10.1145","volume":"48","author":[{"given":"Haitao","family":"Zhang","sequence":"first","affiliation":[{"name":"University of California"}],"role":[{"role":"author","vocabulary":"crossref"}]},{"given":"Yanbiao","family":"Li","sequence":"additional","affiliation":[{"name":"University of California"}],"role":[{"role":"author","vocabulary":"crossref"}]},{"given":"Zhiyi","family":"Zhang","sequence":"additional","affiliation":[{"name":"University of California"}],"role":[{"role":"author","vocabulary":"crossref"}]},{"given":"Alexander","family":"Afanasyev","sequence":"additional","affiliation":[{"name":"Florida International University"}],"role":[{"role":"author","vocabulary":"crossref"}]},{"given":"Lixia","family":"Zhang","sequence":"additional","affiliation":[{"name":"University of California"}],"role":[{"role":"author","vocabulary":"crossref"}]}],"member":"320","published-online":{"date-parts":[[2018,9,7]]},"reference":[{"volume-title":"The protocols. addison-Wesley","year":"2011","author":"Fall Kevin R","key":"e_1_2_1_1_1"},{"key":"e_1_2_1_2_1","doi-asserted-by":"publisher","DOI":"10.1145\/1658939.1658941"},{"key":"e_1_2_1_4_1","doi-asserted-by":"publisher","DOI":"10.1145\/2656877.2656887"},{"key":"e_1_2_1_5_1","first-page":"2131","article-title":"Dynamic host configuration protocol","author":"Droms Ralph","year":"1997","journal-title":"RFC"},{"key":"e_1_2_1_6_1","doi-asserted-by":"publisher","DOI":"10.17487\/RFC3315"},{"key":"e_1_2_1_7_1","first-page":"4862","article-title":"stateless address autoconfiguration","author":"Thomson Susan","year":"2007","journal-title":"RFC"},{"key":"e_1_2_1_10_1","doi-asserted-by":"publisher","DOI":"10.1145\/2810156.2810170"},{"volume-title":"https:\/\/named-data.net\/doc\/ndn-cxx\/current\/specs\/signed-interest.html","year":"2018","author":"Project Team NDN","key":"e_1_2_1_11_1"},{"volume-title":"NDN","year":"2018","author":"Afanasyev Alexander","key":"e_1_2_1_12_1"},{"key":"e_1_2_1_13_1","doi-asserted-by":"publisher","DOI":"10.1016\/j.comcom.2013.01.005"},{"key":"e_1_2_1_16_1","doi-asserted-by":"publisher","DOI":"10.23919\/IFIPNetworking.2017.8264832"},{"key":"e_1_2_1_18_1","doi-asserted-by":"publisher","DOI":"10.1109\/INFCOMW.2015.7179398"},{"key":"e_1_2_1_19_1","doi-asserted-by":"publisher","DOI":"10.17487\/RFC2411"},{"volume-title":"RFC Editor","year":"2008","author":"Dierks T.","key":"e_1_2_1_20_1"},{"key":"e_1_2_1_22_1","first-page":"6182","article-title":"Architectural guidelines for multipath TCP development","author":"Ford Alan","year":"2011","journal-title":"RFC"},{"key":"e_1_2_1_23_1","doi-asserted-by":"publisher","DOI":"10.1145\/3098822.3098842"}],"container-title":["ACM SIGCOMM Computer Communication Review"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/3276799.3276804","content-type":"unspecified","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/dl.acm.org\/doi\/pdf\/10.1145\/3276799.3276804","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2025,6,18]],"date-time":"2025-06-18T00:57:41Z","timestamp":1750208261000},"score":1,"resource":{"primary":{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/3276799.3276804"}},"subtitle":[],"short-title":[],"issued":{"date-parts":[[2018,9,7]]},"references-count":16,"journal-issue":{"issue":"3","published-print":{"date-parts":[[2018,9,7]]}},"alternative-id":["10.1145\/3276799.3276804"],"URL":"https:\/\/doi.org\/10.1145\/3276799.3276804","relation":{},"ISSN":["0146-4833"],"issn-type":[{"type":"print","value":"0146-4833"}],"subject":[],"published":{"date-parts":[[2018,9,7]]},"assertion":[{"value":"2018-09-07","order":2,"name":"published","label":"Published","group":{"name":"publication_history","label":"Publication History"}}]}}