1. Welcome to Technology Exchange 2016
Elias G. Eldayrie
Vice President and Chief Information Officer

2. The one constant – Change
Universities both large and small face an ever changing list of demands on IT services.
Large Universities such as UF are:
Providers of Education.
Institutions of Research and Academic Development.
Providers of Healthcare.
Businesses.
A residential community.
A meeting place for a large number of guests.
A small town with a physical plant and police force.
And more…
We must serve these constituencies across a large distributed campus environment, but at the same time meet our security, privacy and regulatory obligations.
We must also be able to handle fundamentally new requirements without having to redesign.
Each constituency has a different requirement for security/privacy/data rate/ etc.

3. Strategic Directions “Friction Free” network for research
CRN
2013 – 100G to AL2S, Upgrade CRN to 200G capacity.
2016 – Connect to FLR Regional ScienceDMZ
Each constituency has a different requirement for security/privacy/data rate/ etc.
Our deployment of the CRN had all the ingredients of a science DMZ before the term was coined.
Our approach to API development is to create a common API model for all of our services. This API is a layer of abstraction to what is below it (switch/firewall/etc). This set of APIs will track usage/state/etc and do resource and security checking, so we are not compromising the stability of our underlying network.
Invest heavily in providing a high capacity “friction free” network for research
Plan and Deploy Campus Research Network (ScienceDMZ).
2013 – 100G to AL2S. First to complete all three requirements for Internet2 Innovation Campus site.
2013 – Upgrade CRN to 200G capacity.
2016 – Connect to FLR Regional ScienceDMZ
Virtualize the Campus Network.
Plan and deploy MPLS based Network Environments (NE) along with security at touch-points.
Data centric approach to networking. Allow research innovation and academic freedom while protecting sensitive data.
Implement an SDN approach for all major functions of the campus network.
2016+ Build/Expose APIs to authorized groups
Border, Edge, Data center, NE Security.
Data center and edge network provisioning.
Device registration.
Location Services.
All of our major services will be “programmable” with resource and security constraint checking baked in. Starting with campus border and datacenter.
The network becomes an agile platform.

4. UF ScienceDMZ

5. Connect to FLR Regional DMZ

6. Strategic Directions (cont)
Virtualize the Campus Network.
MPLS Based Network Environments
Data centric approach to networking.
SDN approach for all major functions of the campus network.
2016+ Build/Expose APIs to authorized groups
Border, Edge, Data center, NE Security and provisioning.
Device registration and location services.
All of our major services will be “programmable,” The network becomes an agile platform.

7. UFNet2: Virtualized Network Environments
Note that ScienceDMZ is also an environment. Gives access to SDMZ for 1-10Gbps hosts anywhere on campus. Traditional physical ScienceDMZ is now reserved for G and beyond, but they both have the same posture.
Most of the beige circles are also controlled by our API to automate the provisioning process. Exception is UF Health Firewall.
NE Definition:
Create “rough grained” collections of things that need approximately the same security posture.
Take the physical network and virtualize/slice it (VRF). This creates what we call “Network Environments”.
Move systems, data, devices, and/or users to the most appropriate environment.
Allows for rough posture to be assigned anywhere on campus.
Environments can only talk to each other at well defined points in the network.

8. Thank you and enjoy the conference!