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

MIDDLEWARE SYSTEMSRESEARCH GROUP

MSRG.ORG

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

Collaborators:

Reza Sherafat

Young Yoon

Hans-Arno Jacobsen

IBM F2C2, July 29-30th 2013Kaiwen Zhang

msrg.org/papers/sdnlike

MIDDLEWARE SYSTEMSRESEARCH GROUP

MSRG.ORG

2

Content-Based Publish/Subscribe

brokermatch &

forward

Advertisement pathSubscription path

Publication path

publisher

name = `IBM’

price = $40

subscribername = `IBM’

(topic-based)

subscriber

name = `IBM’ price > $30

(content-based)

name = ‘IBM’

MIDDLEWARE SYSTEMSRESEARCH GROUP

MSRG.ORG

3

Software-Defined Networking

MIDDLEWARE SYSTEMSRESEARCH GROUP

MSRG.ORG

4

Overview

SDN-Like Publish/Subscribe

Content-basedPublish/Subscribe

SDN

Virtualized Publish/SubscribeNetwork-as-a-Service

Cross-layerContent-based

Publish/Subscribe

Data/Control Decouplingin Publish/Subscribe

MIDDLEWARE SYSTEMSRESEARCH GROUP

MSRG.ORG

5

Publish/Subscribe-as-a-Service

Customer base

Customer 1 Customer 2 Customer 3

TelecommunicationCompanies

Virtual P/S network

P P

S

P

S

S

Elastisticity, QoS, Migration...

B0B1

S2

S3

MIDDLEWARE SYSTEMSRESEARCH GROUP

MSRG.ORG

6

SDN-Driven Publish/Subscribe

Advertise:

name = ‘IBM’

Subscribe:

name = ‘IBM’

Publish:

name = ‘IBM’

MIDDLEWARE SYSTEMSRESEARCH GROUP

MSRG.ORGChannelization Forwarding

7

OpenFlow switch

Flow table

Flow pattern Action Statistics

Flow pattern Action Statistics

- Identify publication flows by packet header (eg. IP, MPLS)- Flow created persubscription group

- Forward to next hops ofdestination set- Modify header to match downstream flows

MIDDLEWARE SYSTEMSRESEARCH GROUP

MSRG.ORGPros and ConsGround layers:

brokers and clients

Water layers:switches and routers

SDN-driven over broker-based:Can achieve line-speed rate,

offload computation from hosts

Space limitation?- |Flow entries|- |Address range|

Incremental deployment?- How to handle IP multicastin non-SDN routers?

MIDDLEWARE SYSTEMSRESEARCH GROUP

MSRG.ORGAmphibious Publish/Subscribe [Sherafat et al.]

B0B1

S2

S3

Cost model considers:- Broker VM deployment, bandwidth- Switch entry, bandwidth

Ingress datacenter selection for broker VM deployment Frequent and large

subscription groups (FLSGs): maximize gain of flow entries

No home assets:Direct forwarding

Multitenancy? - QoS in cost model

- Customer pricing- Flow isolation- Client churn

General topology?- Multi-switches path

- Virtual switches

MIDDLEWARE SYSTEMSRESEARCH GROUP

MSRG.ORGPublish/SubscribeDecoupling Properties

P Publish/SubscribeService

S1

S2

S3???

???

Space decoupling

Time decoupling

Synchronization decoupling

MIDDLEWARE SYSTEMSRESEARCH GROUP

MSRG.ORGData/Control Decoupling

P Publish/SubscribeService

S1

S2

S3

Production decoupling

DataPlane

ControlPlane

Consumption decoupling

Pr

Producer

Ad

Advertiser

Consumer

C1

C2

C3

IM

Interest Manager

Policy-based:- Metadata- Current state- Application

- Advertisement control- Publication control

MIDDLEWARE SYSTEMSRESEARCH GROUP

MSRG.ORGExample Use Cases

Functionality Use case Application Scenario

Advertisement control Spam filter Social news digest

Publication control Translation Service interoperability

Subscription control Parametric subscriptions Intrusion detection

MIDDLEWARE SYSTEMSRESEARCH GROUP

MSRG.ORG

13

Conclusions

SDN-Like Publish/Subscribe

Content-basedPublish/Subscribe

SDN

Virtualized Publish/SubscribeNetwork-as-a-Service

Cross-layerContent-based

Publish/Subscribe

Data/Control Decouplingin Publish/Subscribe

MIDDLEWARE SYSTEMSRESEARCH GROUP

MSRG.ORG

14

Thank you! Questions?

padres.msrg.orgmsrg.org/papers/sdnlike

MIDDLEWARE SYSTEMSRESEARCH GROUP

MSRG.ORG

S1

15

Channelization Forwarding OpenFlow switch

Flow table

Flow pattern Action Statistics

Flow pattern Action Statistics

S2

S3 S

4

F1

S1

S2

F1

S1

S2

F2

S3

S4

- Identify publication flows by packet header- Flow created persubscription group

- Forward to next hops ofdestination set- Modify header to match downstream flows

MIDDLEWARE SYSTEMSRESEARCH GROUP

MSRG.ORGIP Multicast Flow Matching [Koldehofe et al.]IPfix ∘ Bitstring

Limit to multicast range:IPv4 – 224.0.0.0/8IPv6 – ff0e::/8

1 10 1011

P R0

R1

R2

S0

S1

S2

S3

0*

010*

011*

0101*

0101*

011*

0110*p = “0110”

- Craft publication IP address- IP flow corresponds tosubscription destination set

- Encode pubs and subs using spatial indexing- Establish paths to covered subscribers

MIDDLEWARE SYSTEMSRESEARCH GROUP

MSRG.ORGMPLS-Based Flow Matching

dstip : IPsw

ip-header

pktp =

ip-payload

p

mpls-payload

label1 : SGi

label2 : SGj

mpls-header

IP ofdispatch switch

Unwrap MPLS header:- Compute destination IPs- Replicate and forward

Limit replication factor:Multi-switches MPLS

MIDDLEWARE SYSTEMSRESEARCH GROUP

MSRG.ORGFrequent and Large Subscription Groups

S1

S2

S3

S4

SG1 : {S

1, S

2, S

4}AllSGs

p = {SG

1}, residualSet = {S

3}

Support for false positive groups:Broker-assisted filtering

Topology-aware group management