SDN-Like: A Network-as-a-Service Publish/Subscribe Model

1. SDN-Like:A Network-as-a-Service Publish/Subscribe Model IBM F2C2, July 29-30th 2013 Kaiwen Zhang Collaborators: Reza Sherafat Young Yoon Hans-Arno Jacobsen msrg.org/papers/sdnlike

2. subscriber publisher name = `IBM’ (topic-based) name = `IBM’ price = $40 subscriber name = `IBM’ price > $30 (content-based) Advertisement path Subscription path Publication path Content-Based Publish/Subscribe broker match & forward name = ‘IBM’ 2

3. Software-Defined Networking 3

4. Overview Virtualized Publish/Subscribe Network-as-a-Service SDN-Like Publish/Subscribe Content-based Publish/Subscribe SDN Cross-layer Content-based Publish/Subscribe Data/Control Decoupling in Publish/Subscribe 4

5. Customer base Customer 1 Customer 2 Customer 3 Virtual P/S network S P P P S S Publish/Subscribe-as-a-Service Elastisticity, QoS, Migration... B1 S3 Telecommunication Companies B0 S2 5

6. SDN-Driven Publish/Subscribe Advertise: name = ‘IBM’ Publish: name = ‘IBM’ Subscribe: name = ‘IBM’ 6

7. Flow table Flow pattern Action Statistics Flow pattern Action Statistics Channelization Forwarding OpenFlow switch - Identify publication flows by packet header (eg. IP, MPLS) - Flow created per subscription group - Forward to next hops of destination set - Modify header to match downstream flows 7

8. Pros and Cons SDN-drivenover broker-based: Can achieve line-speed rate, offload computation from hosts Ground layers: brokers and clients Space limitation? - |Flow entries| - |Address range| Incremental deployment? - How to handle IP multicast in non-SDN routers? Water layers: switches and routers

9. Amphibious Publish/Subscribe [Sherafat et al.] B1 S3 B0 Ingress datacenter selection for broker VM deployment Frequent and large subscription groups (FLSGs): maximize gain of flow entries S2 Multitenancy? - QoS in cost model - Customer pricing - Flow isolation - Client churn Cost model considers: - Broker VM deployment, bandwidth - Switch entry, bandwidth No home assets: Direct forwarding General topology? - Multi-switches path - Virtual switches

10. Publish/Subscribe Decoupling Properties S1 Publish/Subscribe Service P S2 ??? S3 ??? Space decoupling Time decoupling Synchronization decoupling

11. Data/Control Decoupling Policy-based: - Metadata - Current state - Application - Advertisement control - Publication control Control Plane Ad IM Interest Manager Advertiser C1 S1 Publish/Subscribe Service Data Plane P Pr C2 S2 C3 S3 Production decoupling Producer Consumer Consumption decoupling

12. Example Use Cases

13. Conclusions Virtualized Publish/Subscribe Network-as-a-Service SDN-Like Publish/Subscribe Content-based Publish/Subscribe SDN Cross-layer Content-based Publish/Subscribe Data/Control Decoupling in Publish/Subscribe 13

14. Thank you! Questions? padres.msrg.org msrg.org/papers/sdnlike 14

15. Flow table Flow pattern Action Statistics Flow pattern Action Statistics F1 F1 F2 S1 S1 S3 S2 S2 S4 Channelization Forwarding S2 OpenFlow switch S1 S3 S4 - Identify publication flows by packet header - Flow created per subscription group - Forward to next hops of destination set - Modify header to match downstream flows 15

16. 1 10 1011 0101* S0 010* R1 S1 0101* P R0 0* 011* S2 R2 011* S3 0110* IP Multicast Flow Matching [Koldehofe et al.] IPfix∘ Bitstring Limit to multicast range: IPv4 – 224.0.0.0/8 IPv6 – ff0e::/8 - Craft publication IP address - IP flow corresponds to subscription destination set - Encode pubs and subs using spatial indexing - Establish paths to covered subscribers p = “0110”

17. ip-payload dstip : IPsw pktp = ip-header mpls-header label1 : SGi label2 : SGj p mpls-payload MPLS-Based Flow Matching Limit replication factor: Multi-switches MPLS Unwrap MPLS header: - Compute destination IPs - Replicate and forward IP of dispatch switch

18. Frequent and Large Subscription Groups S2 SG1 : {S1, S2, S4} AllSGsp = {SG1}, residualSet = {S3} S1 S4 S3 Support for false positive groups: Broker-assisted filtering Topology-aware group management