Inter- domain, SDN, SDX, and NDN (Named Data Networking) CANS 2014 September 15, 2014 John Hicks, Internet2

Transcription

1 Inter- domain, SDN, SDX, and NDN (Named Data Networking) CANS 2014 September 15, 2014 John Hicks, Internet2

2 Overview Inter- domain SDN SDX & Network izaoon NDN (Named Data Networking)

3 OSCARS OSCARS (On- demand Secure Circuits and Advance ReservaOon System) Developed by the Department of Energy s high- performance science network Esnet Features Guaranteed bandwidth scheduling and provisioning of network resources Network technology agnosoc Works on a next- hop peering relaoonship

4 OSCARS

5 NSI NSI (Network s Interface) NSI is designed to allow Grid, Cloud and other applicaoons to mange network connecovity The OGF NSI standards work has generated two documents so far: The NSI Framework document describes the high level abstracted nooons of the NSI environment The NSI Connec0on Protocol describes the funcoonal primioves that control point to point connecoons through their lifecycle. h\p://forge.gridforum.org/sf/go/doc16014?nav=1

6 What is NSI? NSI is an architecture for inter- domain, automated, network connecoon provisioning. It defines an abstract model of a network Connec&on It specifies a very simple and generic mulo- domain Topology model over which ConnecOons are established It defines an automated Network Agent (NSA) that represent each service domain in the topology It defines a simple high level protocol between NSAs that manages a connecoon over its lifeome. Ingress A Access Transport SecOon Egress Z Access NSI Protocol Network Agents NSA NSA NSA ConnecOons STP A.1 STP A.2 STP B.1 STP B.2 STP C.1 STP C.2

7 Overview Inter- domain SDN SDX & Network izaoon NDN (Named Data Networking)

8 Seattle Internet2 Network Advanced Layer2 s Topology Map June 2014 Portland Minneapolis Albany Boston Equinix Starlight Sunnyvale Salt Lake City Denver Chicago Cleveland Pittsburgh New York Philadelphia Kansas City Ashburn Washington D.C. Columbia Raleigh Los Angeles Phoenix Tulsa Charlotte Tucson Atlanta El Paso Dallas Jackson Baton Rouge Jacksonville Advanced Layer2 PoP Houston

9 PacWave SEAT PWNGP TR-CPS Internet2 Network Advanced Layer2 s Connector Map June 2014 Starlight NEREN PORT CIC XSEDE XSEDE 6 MINN ESnet SUNN LOSA CENIC XSEDE SALT PacWave PHOE TUCS TR-CPS Sun Corridor UNM UEN XSEDE NOAA DENV Internet2 ELPA LEARN MREN UIUC ESnet TR-CPS KANS COLU4 GPN TULS DALL TR-CPS HOUH EQCH Indiana Gigapop JCSN BATO CHIC STAR OARnet CLEV PITT PSC TR-CPS MARIA NIH Smithsonian 6 CHAR ATLA JACK RALE NEWY PHIL ASHB WASH ALBA BOST NOX MAGPI MANLAN TR-CPS UPENN MAX Gigapop CAAREN WIX NOAA RENCI SoX Clemson FLR DALL AL2S Juniper MX960 FLR HOUH AL2S Brocade MLXe-16 Exchange Points Connector 10G 100G

10 : Open Exchange Sofware Suite Layer2 Circuit Features Sub second intra- domain provisioning Point to point and point to mulopoint End user controlled provisioning portal Workgroup system for shared access control nooficaoons License Apache Online DocumentaOon Videos and presentaoons h\ps://globalnoc.iu.edu/sdn/oess.html DocumentaOon h\ps://globalnoc.iu.edu/sdn/oess/using- oess.html

11 WG: Network Status

12 Workgroup Examples Connector Indiana Gigapop OneNet Overlay XSEDE GENI

13 KEY OpenFlow Internet2 Software Stack UI FOAM EXP APP EXP APP EXP APP Experimenter Code API Sofware Architecture API API API OSCARS API NSI NSI API NSI FOAM NOX OSCARS IDCP OpenFlow OpenFlow OpenFlow OpenFlow OpenFlow OpenFlow

14 Overview Inter- domain SDN SDX & Network izaoon NDN (Named Data Networking)

15 FlowSpace Firewall OpenFlow 1.0 today Simple VLAN Tag based flowspace firewall / proxy (non- overlapping ranges) Per slice total rule limits Per slice per flow modificaoon rate limits Built upon FloodLight Designed for producoon use. Developed by Internet2 with GlobalNOC Sofware Engineering

16 Network izaoon: Working DefiniOon From a customer perspecove, what does the service offer and how it is uolized? The Network izaoon service/enhancement offers the ability to write a controller and control a slice of the naoonal Layer 2 infrastructure. The customer uolizes the service by operaong their own service across the Internet2 service. From an internal operator perspecove, how is the service implemented? An instance of Flowspace Firewall sits between the Layer 2 es and other controllers (including those used in producoon services like AL2S) Who is the target audience? Advanced Networking Community Network Researchers OrganizaOons InnovaOve ApplicaOon Developers What are the goals for the service? SupporOng network researchers Deployment of private networks Prototyping of new services

17 I2 Production User I2 Prototype Internet2 Taxonomy Implemented Using LHCONE NET+ External Provider s Dependencies XSEDE GENI? Layer 3 R&E IP and TR-CPS s I2-Run Specific Hardware Connectors GENI Learning ONOS? General Purpose VLAN - AL2S SDN Controller ESNET NOAA NVS (Network ization ) ized Ethernet ing Hypervisor Ethernet es Circuits and Wavelengths - AL1S Fiber & Optical Transport

18 KEY OpenFlow Internet2 Software Stack UI FOAM EXP APP EXP APP EXP APP Experimenter Code API Sofware Architecture API API API OSCARS API NSI NSI API NSI FOAM NOX OSCARS IDCP OpenFlow OpenFlow OpenFlow OpenFlow OpenFlow OpenFlow

19 KEY OpenFlow Internet2 Software Stack Experimenter Code Exp OF App Exp OF App UI FOAM EXP APP EXP APP EXP APP API OpenFlow API API API OSCARS API NSI API NSI NSI FOAM FlowVisor NOX OSCARS IDCP OpenFlow OpenFlow OpenFlow OpenFlow OpenFlow OpenFlow OpenFlow OpenFlow OpenFlow

20 Use Case Examples ProducOon Staging GENI wants to move to SOtching v3.0, but SOtching 2.0 is in wide use Set up a slice, deploy a second, deploy new version of FOAM SOtching Aggregator When it s tested and ready, move to the producoon stack Network Research Network researcher has a be\er idea how to do networking Set up a slice, deploy new network controller, write paper Prototyping Look at alternaoves to AL3S Implement a route server that speaks OpenFlow on southbound interface with no routers Deploy in a slice, begin peering with other domains Over Ome transioon to new services Private Networks Want something akin to AtlanOc Wave, original vision for LHCONE, or GENI Network Set up a distributed SDX across mulople domains

21 SDX SDX1

22 SDX SDX1 SDX2 SDX3

23 SDX NSI NSI NSI SDX1 SDX2 SDX3

24 Multi-Domain SDX SDX1 SDX2 SDX3

25 Multi-Domain SDX SDX2 SDX3

26 Multi-Domain SDX GENI Controller SDX2 SDX3

27 Multi-Domain SDX FlowSpace Firewall SDX2 SDX3

28 Multi-Domain SDX SDX2 SDX3

29 NORDUnet Multi-Domain SDX Internet2 SDX2 SDX3

30 Overview Inter- domain SDN SDX & Network izaoon NDN (Named Data Networking)

31 What is Named Data Networking (NDN) NDN is one of five projects funded by the NaOonal Science FoundaOon under the Future Internet Architecture program NDN uses data instead of locaoon for route decisions and content delivery All data object are named The user asks the network for data instead of going to a locaoon to get data AutomaOc cashing to opomize bandwidth NDN secures the content instead of the container

32 NDN ConsorOum UCLA, Washington University St. Louis, Univ. of Memphis, were some the leaders to help to establish a Named Data Networking consoroum of UniversiOes and Technology leaders. The NDN team is developing a new fundamental architecture to replace the Transmission Control Protocol/Internet Protocol (TCP/IP) suite, the underlying approach to all communicaoon over the Internet. h\p://named- data.net/project/

33 NDN testbed h\p://ndnmap.arl.wustl.edu/

34 NDN testbed (cont.) Deployable now as a overlay (TCP/IP) network or layer2 transport Testbed of 15 routers on Internet2/GENI To parocipate in the NDN testbed Sofware router and C library implementaoon available for download Client code available in C++, Python, Java, and Javascipt h\p://named- data.net/codebase/plaporm/

35 Thank You CANS 2014 September 15, 2014 John Hicks, Internet2