2009
DOI: 10.1145/1594977.1592592
|View full text |Cite
|
Sign up to set email alerts
|

Lipsin

Abstract: A large fraction of today's Internet applications are internally publish/subscribe in nature; the current architecture makes it cumbersome and inept to support them. In essence, supporting efficient publish/subscribe requires data-oriented naming, efficient multicast, and in-network caching. Deployment of native IP-based multicast has failed, and overlay-based multicast systems are inherently inefficient. We surmise that scalable and efficient publish/subscribe will require substantial architectural changes, s… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

0
10
0

Year Published

2012
2012
2019
2019

Publication Types

Select...
5
3

Relationship

0
8

Authors

Journals

citations
Cited by 126 publications
(10 citation statements)
references
References 33 publications
0
10
0
Order By: Relevance
“…The full decoupling in time, space and synchronization between publishers and subscribers [22,23] makes pub/sub systems especially appropriate for large-scale distributed IoT service deployments. Pub/sub systems are divided into several variations in the light of different subscription mechanisms, such as topic-based [24,25,26], content-based [27,28,29] and type-based [30,31] pub/sub systems. In the topic-based pub/sub scheme, events are classified by topics, the group communication notion is used.…”
Section: Related Workmentioning
confidence: 99%
“…The full decoupling in time, space and synchronization between publishers and subscribers [22,23] makes pub/sub systems especially appropriate for large-scale distributed IoT service deployments. Pub/sub systems are divided into several variations in the light of different subscription mechanisms, such as topic-based [24,25,26], content-based [27,28,29] and type-based [30,31] pub/sub systems. In the topic-based pub/sub scheme, events are classified by topics, the group communication notion is used.…”
Section: Related Workmentioning
confidence: 99%
“…Several existing schemes propose a publish-subscribe architecture [23][24][25]. However, this approach is vulnerable to denial of service attacks, as it allows more than one data packet per content request, not preserving the flow balance provided by NDN approach.…”
Section: Related Workmentioning
confidence: 99%
“…Existing ICN proposals [2,3,4] build ICN architectures upon content abstraction. For example, NDN adopts a distributed name based routing mechanism, and maintains forwarding information base, pending interest table, as well as content store in each network nodes.…”
Section: Related Workmentioning
confidence: 99%
“…Intra-area routing and forwarding is done according to the rules of the local DHT algorithms, while inter-area routing is done by the node in both the local DHT and the next higher level DHT [11]. PURSUIT shifts the current send-receive based Internet toward the new publish-subscribe paradigm, and uses the rendezvous network to perform name resolution and data forwarding [4]. These proposals share some commonalities in the perspectives of basic primitives, name based routing, universe in-networking caching, etc [3].…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation