{"title":"一种基于dns的以信息为中心的网络体系结构,对多种协议开放,用于传输数据对象","authors":"A. Eriksson, A. Malik","doi":"10.1109/ICIN.2018.8401595","DOIUrl":null,"url":null,"abstract":"In this paper, we present the information-centric NEO (Networked Object) architecture. To enable reuse of existing network protocols and naming formats, NEO uses DNS domain names as data object names, as well as DNS proxies and servers that are enhanced for information-centric operation. A key feature of NEO is its openness to a variety of legacy protocols for transfer of data objects, such as HTTP, CoAP or IP multicast. NEO allows for selection of transfer protocol per data object, so that the most optimal protocol can be selected for the data object and use case at hand. Also, NEO can employ clean slate protocols such as CCN or NDN for transfer of data objects. We validate the NEO architecture in a testbed using DNS for resolution of data object names and HTTP, CoAP, IP multicast, and CCN for object transfer. We also describe several features implemented in the NEO testbed, such as policy routing, publisher mobility, publish-subscribe and service chaining for IoT use cases.","PeriodicalId":103076,"journal":{"name":"2018 21st Conference on Innovation in Clouds, Internet and Networks and Workshops (ICIN)","volume":"114 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2018-02-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"4","resultStr":"{\"title\":\"A DNS-based information-centric network architecture open to multiple protocols for transfer of data objects\",\"authors\":\"A. Eriksson, A. Malik\",\"doi\":\"10.1109/ICIN.2018.8401595\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"In this paper, we present the information-centric NEO (Networked Object) architecture. To enable reuse of existing network protocols and naming formats, NEO uses DNS domain names as data object names, as well as DNS proxies and servers that are enhanced for information-centric operation. A key feature of NEO is its openness to a variety of legacy protocols for transfer of data objects, such as HTTP, CoAP or IP multicast. NEO allows for selection of transfer protocol per data object, so that the most optimal protocol can be selected for the data object and use case at hand. Also, NEO can employ clean slate protocols such as CCN or NDN for transfer of data objects. We validate the NEO architecture in a testbed using DNS for resolution of data object names and HTTP, CoAP, IP multicast, and CCN for object transfer. We also describe several features implemented in the NEO testbed, such as policy routing, publisher mobility, publish-subscribe and service chaining for IoT use cases.\",\"PeriodicalId\":103076,\"journal\":{\"name\":\"2018 21st Conference on Innovation in Clouds, Internet and Networks and Workshops (ICIN)\",\"volume\":\"114 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2018-02-01\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"4\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2018 21st Conference on Innovation in Clouds, Internet and Networks and Workshops (ICIN)\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/ICIN.2018.8401595\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"2018 21st Conference on Innovation in Clouds, Internet and Networks and Workshops (ICIN)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ICIN.2018.8401595","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
A DNS-based information-centric network architecture open to multiple protocols for transfer of data objects
In this paper, we present the information-centric NEO (Networked Object) architecture. To enable reuse of existing network protocols and naming formats, NEO uses DNS domain names as data object names, as well as DNS proxies and servers that are enhanced for information-centric operation. A key feature of NEO is its openness to a variety of legacy protocols for transfer of data objects, such as HTTP, CoAP or IP multicast. NEO allows for selection of transfer protocol per data object, so that the most optimal protocol can be selected for the data object and use case at hand. Also, NEO can employ clean slate protocols such as CCN or NDN for transfer of data objects. We validate the NEO architecture in a testbed using DNS for resolution of data object names and HTTP, CoAP, IP multicast, and CCN for object transfer. We also describe several features implemented in the NEO testbed, such as policy routing, publisher mobility, publish-subscribe and service chaining for IoT use cases.