Consumer-producer API for named data networking

Moiseenko, Ilya; Zhang, Lixia

doi:10.1145/2660129.2660158

Cited by 10 publications

(5 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…NDTP is implemented using two main data structures: A producer that publishes content and a consumer that retrieves content. This design is inspired by the NDN API design [72]. Figure 1 shows an overview of the NDTP producer functional structure.…”

Section: Ndtpmentioning

confidence: 99%

Named-Data Transport

Albalawi

Garcia-Luna-Aceves

2020

Proceedings of the 7th ACM Conference on Information-Centric Networking

View full text Add to dashboard Cite

Named-Data Transport (NDT) is introduced to provide efficient content delivery by name over the existing IP Internet. NDT consists of the integration of three end-to-end architectural components: The first connection-free reliable transport protocol, the Named-Data Transport Protocol (NDTP); minor extensions to the Domain Name System (DNS) to include records containing manifests describing content; and transparent caches that track pending requests for content. NDT uses receiver-driven requests (Interests) to request content and NDT proxies that provide transparent caching of content while enforcing privacy. The performance of NDT, the Transmission Control Protocol (TCP), and Named-Data Networking (NDN) is compared using off-the-shelf implementations in the ns-3 simulator. The results demonstrate that NDT outperforms TCP and is as efficient as NDN, but without making any changes to the existing Internet routing infrastructure. CCS CONCEPTS • Networks → Naming and addressing; Network protocol design; Transport protocols.

show abstract

Section: Ndtpmentioning

confidence: 99%

Named-Data Transport

Albalawi

Garcia-Luna-Aceves

2020

Proceedings of the 7th ACM Conference on Information-Centric Networking

View full text Add to dashboard Cite

show abstract

“…Under this model, the consumer can decide how many items into the "future" to poll for simultaneously. This whole process can be abstracted over with a consumer-side library [29,35].…”

Section: Ssb Over Ndnmentioning

confidence: 99%

Secure Scuttlebutt

Tarr¹,

Lavoie

Meyer

et al. 2019

Proceedings of the 6th ACM Conference on Information-Centric Networking

View full text Add to dashboard Cite

Secure Scuttlebutt (SSB) is a novel peer-to-peer event-sharing protocol and architecture for social apps. In this paper we describe SSB's features, its operations as well as the rationale behind the design. We also provide a comparison with Named Data Networking (NDN), an existing information-centric networking architecture, to motivate a larger exploration of the design space for information-centric networking primitives by formulating an identity-centric approach. We finally discuss SSB's limitations and evolution opportunities. CCS CONCEPTS • Networks → Network architectures; • Software and its engineering → Publish-subscribe / event-based architectures; • Computer systems organization → Peer-to-peer architectures; • Information systems → Linked lists.

show abstract

“…For all other uses, contact the owner/author(s sockets with a novel socket domain, and to deploy NDN as an overlay over existing technologies. Differently from [5], we propose a protocol stack composed of two layers, transport and network, which sits between socket API and an underlying technology that provides connectivity between two NDN nodes. NaNET supports Ethernet and IP to provide connectivity between two NDN nodes.…”

Section: Pcc and Nanetmentioning

confidence: 99%

“…Similarly to [5], we identify two key processes involved in the process-to-content communication model (PCC) used by NDN: the publisher and the consumer. The publisher process makes content publicly and permanently available to the network by opening one or more sockets that simply wait for incoming requests.…”

Section: Pcc and Nanetmentioning

confidence: 99%

NaNET

Gallo¹,

Gu²,

Perino³

et al. 2014

Proceedings of the 1st ACM Conference on Information-Centric Networking

View full text Add to dashboard Cite

Inter-process communication (IPC) refers to the set of methods which enable data exchange among processes. When two processes are remote (connected via a network), IPC is realized through the socket and the networking protocol stack implemented at end-hosts. Today, most computer networks rely on the Internet NETtworking socket domains (INET) and the Internet Protocol (IP) suite.Information-centric networking (ICN) is a novel networking paradigm centered around named data rather than named hosts. ICN shifts the communication principle from processto-process towards process-to-content (PCC) by mean of a novel name-based protocol suite. We propose Named NETworking, a new socket domain and protocol stack that realize PCCà la NDN [1] while remaining compatible with current protocols and standards. Finally we implement NaNET in the Unix operating system as a set of kernel modules.

show abstract

Consumer-producer API for named data networking

Cited by 10 publications

References 3 publications

Named-Data Transport

Named-Data Transport

Secure Scuttlebutt

NaNET

Contact Info

Product

Resources

About