2012.**.** Supporting reliability using reverse path in Publish/Subscribe Internet Takashima Daiki ParkLab, Waseda University, Japan 1/11

Outline 2/11 1.What is Information-Centric Networking? 2. Introduction of PURSUIT -Forwarding 3. Background 4. Proposal 5. Conclusion 6. References

What is Information-Centric Networking ? 3/11 Information-Centric Networking (ICN) is one of the significant directions of current networking research. When retrieving content, ICN uses content information itself instead of location information. In the Internet the only way to retrieve content is to establish an end-to-end connection. While the user’s demand has been changed to content-oriented one: YouTube, twitter, facebook ・・・ etc.

Introduction of PURSUIT PURSUIT is one of the ICN architecture which uses publish subscribe model. 4/11 Rendezvous Point Publisher Subscriber Subscription message Publication message Send Fid Matching!! Forward data Get Fid Rendezvous identifier ( Rid ): denotes individual content itself Scope identifier ( Sid ): makes group of Rid, access rights of data sources, categories of data Forwarding identifier ( Fid ): denotes forwarding path from publisher to subscriber Sid (waseda) Rid1 Rid2 Rid3 Sid (music) Rid4 Rid5 Rid6 Topology Management

5/11 Introduction of PURSUIT ~ Forwarding~ Fid consists of Bloom Filter and strict routing is realized. Subscriber Publisher DATA Fid: Data packet IF P-1 InterfaceLink ID IF IF IF Node 1 Node 2 Node 3 InterfaceLink ID IF P IF 1-1 IF 1-2 Match and forward IF 1-3 InterfaceLink ID IF IF IF 3-1 IF 3-2 InterfaceLink ID IF IF IF S-1 IF 2-2 IF 2-1 Match and forward 忘却防止のためヒ ントとなるキーワ ードを入れる

Background How to support reliability is one of the main problems in PURSUIT. We propose reliability communication by making reverse path. 6/11 AdvantagesDisadvantages Not need to know source or destination No way for a subscriber to contact a publisher Easy to realize multicast False positive Table1. Advantages and Disadvantages of Fid (Bloom Filter)

Subscriber Publisher 7 Proposal ~ making reverse path ~ DATA Fid: Data packet IF P-1 InterfaceLink ID IF IF IF Node 1 Node 2 Node 3 InterfaceLink ID IF P IF 1-1 IF 1-2 Match and forward IF 1-3 InterfaceLink ID IF IF IF 3-1 IF 3-2 InterfaceLink ID IF IF IF S-1 IF 2-2 IF 2-1 Match and forward Reverse path can be made by aggregating incoming Link ID in each node. Reverse Fid: /11 InterfaceLink ID IF S

Supporting reliability using reverse path Reverse path realizes ・ sending ACK message, ・ requesting missed data to the publisher or near cache Reliability connection like TCP comes true without knowing who or where the publisher is. 8/11 Rendezvous Point Publisher Subscriber When forwarding data Topology management Each node aggregates incoming Link ID ACK or Request for missed data ( Reverse path’s Fid )

Subscription message for RP Returning specified data directly Reverse path also realizes returning specified cached data directly when subscription message is sent to RP and the data is found at a node on the path. In this case, cache node can decrease the burden of Rendezvous Point. 9/11 Rendezvous Point Publisher Subscriber Matching Forward data Topology management Cache hit!!!

10/11 Reverse path is useful to supporting: ・ sending ACK message ・ requesting missed data to the publisher or near cache ・ returning specified cached data directly when subscription message is sent to Rendezvous Point and the data is found at a node on the path. Conclusion

[1] G Xylomenos, et al., Caching and Mobility Support in a Publish- Subscribe Internet Architecture, IEEE Comm Magazine, July [2] Nikolaos Fotiou, George C.Polyzos,DirkTrossen,”Illustrating a Publish-Subscribe Internet Architecture,” 11/11 Reference

Thank you !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

False positive : ~data is sent undesirable way~ If Link ID of IF 1-2 is Packet will be sent to undesirable way (: Node 3 where no subscriber is) How to set a bit string is a significant problem. Subscriber Publisher DATA Fid: Data packet IF P-1 InterfaceLink ID IF IF IF Node 1 Node 2 Node 3 InterfaceLink ID IF P IF 1-1 IF 1-2 Match and forward IF 1-3 InterfaceLink ID IF IF IF 3-1 IF 3-2 InterfaceLink ID IF IF IF S-1 IF 2-2 IF 2-1 Match and forward

Existing method for subscriber’s mobility 10/13 Rendezvous Point Publisher Subscriber Subscription message Cache node Send Fid Data forwarding [1] G Xylomenos, et al., Caching and Mobility Support in a Publish-Subscribe Internet Architecture, IEEE Comm Magazine, July Problem A moved subscriber always has to resend subscription message to RP. This increases RP’s burden and latency. Traditional support for subscriber’s mobility

Cache node can send data to a moved node according to reverse path’s Fid. 11/13 Rendezvous Point Publisher Subscriber Subscription message Data forwarding Supporting subscriber’s mobility Cache node Using reverse path can support subscriber’s mobility efficiently.