70 likes | 140 Views
Achieving the Programmable WAN: Introduction. Marshall Brinn, GPO March 18, 2014 1600-1730. What do we mean by the “Programmable WAN * ”. GENI wants to provide the impression of having your own private network [“WAN”]
E N D
Achieving the Programmable WAN:Introduction Marshall Brinn, GPO March 18, 2014 1600-1730
What do we mean by the “Programmable WAN*” • GENI wants to provide the impression of having your own private network [“WAN”] • Creating connectivity across range of allocated resources (e.g. Stitching) • Traffic is isolated (your net from others) • Traffic flows along interfaces within your slice as configured (P2P, M-Cast, B-Cast) • But that’s really just where GENI begins. • To complete the picture, we must enable control over how traffic flows through this network: what paths, what protocols [“Programmable”] *This may be a misnomer: perhaps we mean “Distributed LAN”
Example Slice Topology: WAN MAC/IFace Switch
Example Slice Topology: Programmable WAN Network Controller MAC/IFace Switch Programmable Switch
Example Slice Topology: Programmable WAN • Architecturally, GENI doesn’t specify how this is done: • Switches (generally, forwarding elements) could be S/W or H/W • Traffic could be stacked, tunneled, encapsulated • Different possible isolation mechanisms (VLAN, subnet, …) Network Controller MAC/IFace Switch Programmable Switch
Programmability: Past, Present, near-Future • We already have a number of possibilities for network programmability in GENI • GENI OpenFlow Network • Mesoscale Infrastructure provides shared VLANs connected with OF switches • FOAM/FlowVisorSliced OF switches (by subnet, VLAN) • Experimenters can allocate/configure their own OVS switches, Click routers • Each of these has its strengths and limitations (particular wrt. to ease-of-use for experimenter)
Agenda We’re looking, in this session, to step back and look at what is possible and desirable in offering a “Programmable WAN” capability to experimenters, both in new directions and extending existing directions • Nick Bastin, Barnstormer Softworks: VTS • Eric Boyd, Internet2: AL2S / Flowspace Firewall • Rick McGeer, US Ignite: GEE • Joe Mambretti, ICAIR: SDX, FOAM/Starlight • Jerry Sobieski, NORDUnet: GEANT • Open / Panel Discussion