Presented By:

22 August 2014In the Denver Technology Center

6400 S Fiddlers Green Cir

Greenwood Village, CO 80111

TFI2014 - COISOC 2

The Future of the Internet 2014:

Defining Software Defined Networks

Gold Sponsors

Bronze Sponsors

Event Host

22 August 2014

TFI2014 - COISOC 3

The Colorado Internet Society (CO ISOC) is hosting our first annual "The Future of the Internet" event

on August 22nd, 2014 with a theme of "Defining Software Defined Networks".

While this is the first in what we plan to be an annual meeting series, it is building on the successes of

events we have previously held. Our two most notable events so far have been:

2013 - INET Denver: IPv4 Exhaustion and the Path to IPv6

http://www.internetsociety.org/events/inet-denver

2012 - IPv6: What is it, why do I need it, and how do I get it?

https://www.eventbrite.com/e/ipv6-what-is-it-why-do-i-need-it-and-how-do-i-get-it-tickets-4103501684

In order to keep our eye to the horizon, we are shifting away from IPv6 in 2014 and looking into the

newer areas surrounding SDN. At this year's event, CO ISOC is bringing together experts and

professionals from across the globe to discuss SDN, NfV, open networking, and all things related to

network programability; the ability for networked applications to more directly interact with network

elements such as routers, switches, and firewalls. Whether you call it Software Defined Networking,

Software Driven Networks, Open Networking, Cloud Routing, Network Virtualization, or something

else; the exciting part is extrapolating this "SDN" trend into the future as we make these programs

and languages more fully featured and more standardized. SDN is no magic pill, but it does have the

potential to drastically simplify network operations while simultaneously increasing network

efficiency. This first annual CO ISOC Future of the Internet event will focus on the real problems and

on finding the best solutions, so that attendees can leave informed, ready to tackle the newest

networking trends while avoiding the pitfalls of the newest buzzword.

We expect networking professionals to attend, ranging from technology leaders, systems architects,

technical engineers, and researchers from around the country and the world. The entire event will be

live streamed and recorded.

The webcast for the event will be available at https://new.livestream.com/internetsociety/SDN2014

All presentations will be recorded and posted for all 70k Internet Society members to access. The

event will also be highly publicized through social media, both before and after.

The event will also feature an onsite SDN Lab, where top sponsors can demonstrate their newest

gear and services to attendees throughout the day and during the 2 hour Beer-N-Gear event. The

Beer-N-Gear will take place in the SDN Lab immediately following the plenary session.

On behalf of the Colorado Internet Society, it’s a pleasure to welcome you!

22 August 2014

Welcome to the Future

of the Internet!

TFI2014 - COISOC 4

Table of ContentsAgenda at a Glance 5

Getting Around (maps) 6

Message from the Colorado Internet Society Board 7

Keynote Speaker 8-9• Russ White, Ericsson

Speakers 10-42• John Giacomoni, F5

• Recep Ozdag, Cyan

• Sam K. Aldrin, Huawei

• Karen “Shelly” Cadora, Cisco

• Scott Sneddon, Nuage

• Joseph Marsella, Ciena

• Gary Hemminger, vArmour

• Brian Field, Comcast

• Eric Osborne, Level3

• Jeff Doyle, Fishnet

• Geoff Mulligan, Presidential Innovation Fellow

• Matthew Wallace, ViaWest

• Doug Marschke, SDN Essentials

• Mike Thompson, A10

• Douglas Gourlay, Arista

About the Colorado Internet Society 44

22 August 2014

TFI2014 - COISOC 5

Agenda at a Glance9:00 - 9:15 am Conference Opening

9:15 - 10:00 am Keynote

10:00 - 10:30 am Break in the SDN Lab

10:30 - 12:00 pm Plenary Session I – “State of SDN" - A look at

the current ecosystem and landscape (what's

available and what's going on today) • John Giacomoni, F5

• Recep Ozdag, Cyan

• Sam K. Aldrin, Huawei

• Karen “Shelly” Cadora, Cisco

• Scott Sneddon, Nuage

• Joseph Marsella, Ciena

• Gary Hemminger, vArmour

12:00 - 1:30 pm Lunch Front Hall / Outside - SDN Lab Open

1:30 - 3:00 pm Plenary Session II - Requirements for SDN -

What are operators (ISP/DC/Enterprise/etc.)

looking for from SDN (what's missing today,

what do you need tomorrow)?• Brian Field, Comcast

• Eric Osborne, Level3

• Jeff Doyle, Fishnet

• Geoff Mulligan, Presidential Innovation Fellow

• Matthew Wallace, ViaWest

3:00 - 3:30 pm Break in the SDN Lab

3:30 - 5:00 pm Plenary Session III - Conclusions and next

steps - Convergent themes from the day's

discussions and a look to the future (where do

we go from here?)• Jeff Doyle, Fishnet

• Geoff Mulligan, Presidential Innovation Fellow

• Doug Marschke, SDN Essentials

• Mike Thompson, A10

• John Giacomoni, F5

• Douglas Gourlay, Arista

5:00 - 7:00 pm Beer-N-Gear in the SDN Lab

22 August 2014

TFI2014 - COISOC 6

Building Map and Parking DirectionsLocation: 6400 S Fiddlers Green Cir, Greenwood Village, CO 80111

Directions: From I-25 take exit #197/CO-88/Arapahoe Rd (CR-42 W) onto E Arapahoe Rd towards

Yosemite St South/Yosemite St North 0.4 mil

Turn right onto S Yosemite St 0.3 mil

Turn left onto E Peakview Ave 0.1 mil

Turn right onto S Fiddlers Green Cir 446ft

The conference building and parking are on the right

Enter the garage

Parking is free, you will be given a voucher at the event registration

desk

Conference Rooms Building

RTD Light Rail, E and F lines

Arapahoe at Village Center station

22 August 2014

Wireless Network

SSID: TFI2014-VIAWEST

WPA key: coisoc-viawest

TFI2014 - COISOC 7

Message from the Colorado

Internet Society Board

The Colorado Internet Society Board is very pleased to organize the Future of

the Internet 2014: Defining Software Defined Networks Summit!

We’ve worked hard to put together an event that will help you keep up with

the tools and know-how you need.

Our hope is that this event helps you and your organization understand SDN,

NfV, open networking, and things related to network programability.

Welcome to you all.

22 August 2014

Ogi Mitev

Chairman

Chris Grundemann

Founding Chairman

Jeff Doyle

Executive Vice President

Joshua Sahala

Administrative Vice

President

Karen Mulberry

Secretary/Treasurer

Mike Schoenecker

Chairman, Program

Committee

Paul Ebersman

Chairman, Membership

Committee

TFI2014 - COISOC 8

Keynote SpeakerRuss White

Russ White has over 25 years of experience in network engineering from operating systems

to network architecture. Russ is a Principal Engineer at Ericsson in the IPOS Team, where he

works on large scale design, control planes, Internet governance, network complexity

puzzles, and anything else that comes along. He currently serves as a member of the IETF's

Routing Area Directorate and as a Cochair of the Internet Society's Advisory Council.

While working on meteorological and airfield navigation equipment in the US Air Force, Russ

became involved in the installation of a fiber backbone at McGuire AFB, and developed an

interest in all things networking. After moving to the Raleigh, NC, area, with his wife, he

became a member of the Cisco TAC's Routing Protocols backline TRT. Moving to Cisco's

Global Escalation Team led to a quick rampup in network design skills by working on failed

network designs in some of the world's largest networks. This led to the publication of

Advanced IP Network Design, which kicked off a series of nine books in the network

engineering field, covering routing protocols to router architecture to The Art of Network

Architecture.

Russ holds both a BSIT and MSIT in network technologies from Capella University, and a

MACM in Biblical Literature from Shepherds Theological Seminary. He currently posts

regularly at Packet Pushers, and speaks worldwide. His current research interests include

network complexity, particularly in the areas of network design and understanding the

tradeoffs between centralized and decentralized control planes. He is working on a new book

on Addison-Wesley in the area of network complexity.

22 August 2014

TFI2014 - COISOC 9

Keynote SpeakerRuss WhiteWe got a chance to ask Russ; how does the network of the future differ from today’s?

Here’s what he had to say:

The computer networking world is facing an existential event — the very paradigm

through which we view what began as a motley collection of a few mainframes, and is now a

huge multinational business, is being challenged by a simple idea: let’s centralize the control

plane. But before we declare the end of the world as we know it, and before we declare the

paradigm shift complete, let’s take stock of a little history. The truth is, we’ve seen this all

happen before. The computer world is one of pendulums and perpetual motion machines;

it’s been estimated that the half life of any skill set in the networking world is around two

and a half years. Every five years, any particular skill is probably about one quarter as useful

as when you learned it; in ten years the skill has become almost too embarrassing to put on

your resume. There is a clarity in the moment when the pendulum starts to swing, however,

that we cannot find when the pendulum is at its ultimate reach. This current moment, when

centralized control planes seem to be gathering steam for a complete takeover of the entire

networking world through this thing we call the software defined network, should be one of

those moments of clarity.

But what is it we should learn? Maybe I can answer that question by offering a vision of

what computer networks could be.

The computer network of the future should be ubiquitous — that seems to be a given. But

it should not be forgotten. The computer network of the future should be able to disperse

policy easily, but it should not be centralized to the point of fragility. The computer network

of the future should add convenience and value to our lives, but it should not contribute to a

loss of privacy and human freedom. For anyone familiar with the stock arguments of the last

several years, these might seem like contradictory goals.

Perhaps, if we use this moment of clarity, and think seriously about what the software

defined network really can be, we can find a way to move past the stock discussions and

realize all of these goals.

Taking the challenge and promise of software defined networking seriously can help us

bring clarity to questions about when it makes sense to centralize, and when it makes sense

to distribute — and what the best way to centralize should be, once we’ve decided what to

centralize. Taking this challenge seriously can help to think about our processes as network

engineers, possibly moving us from flying by the seat of our pants to fly-by-wire. Taking this

challenge seriously can help us to think through security and profit, and bring the ethical

dimension into our work.

SDNs, defined in their broadest sense, are an important part of that conversation, and an

important part of the future of computer networking.

22 August 2014

TFI2014 - COISOC 10

SpeakersJohn Giacomoni

John Giacomoni is a Senior Architect at F5 Networks focussing on SDN as well as both the

kernel architecture and go to market strategy for the LineRate product. John has focussed his

15+ year career on bringing deep systems technologies to market in new and interest ways

as an entrepreneur, researcher, and OS/networking architect/programmer. Most recently F5

Networks acquired LineRate Systems, an SDN company, where John raised initial capital as

the founding CEO and later CTO. LineRate Systems’ SDN technology was based on John’s

research and dissertation work dating back to 2003. Additional notable projects that John

has worked on include NCSA Mosaic, Argus Systems Groups’ Pitbull Trusted Operating

System (certified), and a performance visualization system for Google.

Take it away John!

tl;dr SDN excites me because we can finally see a path towards being able to treat the

network, and the rest of the computing infrastructure via SDDC, as a programmatically

controlled utility where the infrastructure immediately responds to the needs of services and

applications. However, the morass of SDN definitions (OpenFlow, Overlay Networking,

Service Chaining, Vendor Neutral, etc.) has only served to confuse and paralyze most

customers. In conversations with customers I define SDN as follows:

“SDN is a family of architectures (not technologies) for operationalizing networks with

improved time to market, reduced risks, and reduced operating expenses by centralizing

control into a control plane that programmatically controls and extends all network data path

elements and services via open APIs.”

22 August 2014

TFI2014 - COISOC 11

SpeakersJohn GiacomoniSDN and the Network of the Future:

The past few years have rekindled my excitement in networking for the first time since I

discovered the NSFNET in the late 80s and realized the potential of a globally interconnected

set of networks. As a computer scientist, software engineer, and entrepreneur I believe our

focus has been on satisfying consumer needs by refining techniques grounded by static

topologies.

SDN and SDDC (SDN’s infrastructure wide version) finally offer us a solid path towards

achieving the promise of a true utility computing model where the utility can span the globe

and be programmatically reconfigured “instantaneously” based on the needs of the

consumer via services and applications.

Defining SDN:

Having followed SDN since 2011 and earlier, I find it endlessly fascinating and frustrating that

we get a new definition of SDN every 1-2 years in spite of the general sense of agreement

that SDN is the future of networking. In my opinion, the trouble stems from trying to scale

the description of useful but point technologies into something all encompassing.

Instead we should be focusing on a holistic definition that encompasses most of the

problems suffered by participants in the SDN discussion. In doing so we can actually have a

open discourse about problems and solutions without having to argue whether OpenFlow or

Overlay Networking is the best expression of SDN – both are useful but neither is sufficient.

The result of these arguments, outlined in more detail below, is that we’ve created a tower

of babel type situation with most of the customers that I have spoken with being paralyzed

by confusion.

Instead I offer the following definition that helps them understand the types of problems

that can be addressed by SDN and how they can move forward today without choosing

poorly.

“SDN is a family of architectures (not technologies) for operationalizing networks with

improved time to market, reduced risks, and reduced operating expenses by centralizing

control into a control plane that programmatically controls and extends all network data path

elements and services via open APIs.”

22 August 2014

TFI2014 - COISOC 12

SpeakersJohn GiacomoniProblems with Existing SDN Definitions:

In very broad strokes I’ve seen a rough correspondence of definitions to the 4 major eras of

“media defined” SDN with each successive era convinced they’d cracked the nut and

achieved SDN nirvana:

History-2011: Abstraction and network protocols at the packet level

2011-2012: OpenFlow

2012-2013: Overlay and Virtual Networking

2013-2014: Service Chaining

Confusingly, each of these eras has its own set of technologies and a definition that explains

how these technologies are the apex of SDN to the exclusion of other technologies. This is

not surprising as primarily customers and vendors with a agendas have defined each of these

eras. What we are seeing are solutions in search of a problem that get lots of hype and then

slowly fade. This is sad as each of these eras can contribute to customer problems when

viewed viewed as a tool to solve the operational problems that network operators are

suffering today.

Adding additional complexity to the situation is the desire for a universal set of APIs that can

describe the totality of networking devices in use today and those that may yet be invented.

This idea began as early as the ONFs initial definition of SDN that included a requirement for

a ‘vendor neutral API’ to allow data plane devices to be swapped out at will. This desire

makes sense in the context of OpenFlow being used to implement stateless packet

forwarding rules with minimal logic built on switching fabrics.

However, customers are pushing that this concept be taken to extremes such that it applies

to all 7 layers of the OSI stack including stateless layer 4 firewalls, stateful layer 4 firewalls,

layer 7 traffic managers, and even application layer firewalls. While I am certainly not all

knowing, I can see only two realistic paths forward. Either we as an industry define a

simplistic set of APIs equivalent to Amazon’s ELB or OpenStack’s LBaaS (the production

equivalent of writing a book in notepad) or we define APIs with sufficient complexity that

one might as well write one’s networking policy definitions with a C++ compiler. In my

opinion a productive compromise is to acknowledge that there is a reason why services are

complex and that there will be some amount of work when switching vendors but that at the

same time vendors need to focus on delivering elegant (not obfuscated) APIs.

In closing SDN presents us with an exciting path to a new era in computing provided we can

provide a useful definition that we can all move forward and solve real problems.

22 August 2014

TFI2014 - COISOC 13

SpeakersRecep Ozdag

Recep Ozdag is Director of Solutions Marketing for SDN and NFV at Cyan Inc. Before joining

Cyan, Recep was in product marketing for the Communications and Storage Infrastructure

Group (CSIG) at Intel. He lead Intel’s SDN switch and router marketing efforts as well as

launched Intel’s SDN and NFV initiative; the Open Network Platform.

Prior to this role he was a design manager at Fulcrum Microsystems and has been involved

in all of the commercial products that came out of the fabless semiconductor startup. Recep

was one of the influential designers of the world’s lowest latency, highest bandwidth and

SDN optimized switch silicon – the FM6000 Alta, which led to the Intel acquisition in 2011.

Recep is also part of the faculty within the engineering department at USC, where he

occasionally teaches graduate level courses. He co-authored the book titled “A Designer’s

Guide to Asynchronous VLSI”.

Recep Ozdag has received his PhD in Electrical Engineering from the University of Southern

California and his MBA from the University of California Los Angeles.

What is SDN?

In short, disaggregation of software from networking devices and improved multi-vendor

interoperability captures the essence of what SDN represents.

Software-defined networking had its birth in the data-center and now extends into the WAN.

SDN controllers for WANs have emerged, enabling network virtualization across multiple-

vendors, multi-layer management and visualization, constraint-based path computation – or,

in the simplest of terms, transformed the WAN into a programmable resource that enables

on-demand connectivity between users and their applications.

The reality is, true service delivery relies on configuring and managing multiple domains that

consist of a diverse set of physical and virtual resources, networks and small and large

distributed data centers that may belong to service providers or users such as enterprises.

With SDN, we are able to decouple the control and intelligence from proprietary devices and

able to use white box hardware with modular and interoperable, intelligent software,

thereby giving control and visibility back to the users.22 August 2014

TFI2014 - COISOC 14

SpeakersRecep OzdagWhy are you excited about SDN?

Today network operators provision services piece-meal across their networks, one hop or

node at a time, without end-to-end visibility or coordination. Adding yet another dimension

of complexity is that often times different network layers are operationally siloed. This makes

it impossible for an operator to make path computation decisions across a multi-layer service

offering.

Yet, service providers and network operators around the world need to transform their

operational models to drive faster growth, lower costs, and to offer services that meet end-

customer requirements for dynamic network control

So how do network operators solve this? Especially in an environment where most large

network operators are challenged by issues such as network size, the number of vendors in

the network, and incomplete inventory systems.

SDN promises to make networks easier to use, turn them into a resource pool, and make

them programmable. This in turn takes knowledge; knowledge about the network topology,

knowledge about the inventory and state, and knowledge about the network layers and their

relationships. When equipped with this meta-data about a network, a controller can help

reap the promise of SDN.

The benefits include the ability to visualize, monitor and troubleshoot services from end-to-

end over across multiple network domains, over multiple layers of network technologies,

and through multiple vendors’ equipment. These service automation efforts enable the

acceleration of service management, delivery, and provisioning and are a strategic step

toward a software-defined network.

The result is services that are provisioned in minutes or hours instead of months. Errors are

reduced. Time to market and revenue is greatly accelerated. These are all benefits the

industry can all understand.

22 August 2014

TFI2014 - COISOC 15

SpeakersRecep OzdagHow does the network of the future differ from today’s?

In the near future, services will increasingly become cloud-centric workloads. Starting in data

centers (DC) and at the network edges – networking services, capabilities, and business

policies will be instantiated as needed over this common infrastructure. Such an approach

will be embodied by orchestrating software instances that can be composed to perform

similar tasks at various scale and reliability using techniques typical of cloud software

architecture.

Network Function Virtualization (NFV) will be common place and services will be delivered as

virtual machines running on COTS servers spread over CEs, PoPs, COs and at central

locations. Beyond reducing dependency on dedicated hardware-based appliances,

virtualizing network functions also greatly reduces the complexity associated with

introducing new services across the entire network.

Any network function that has not been virtualized will be implemented in a white box

fashion from optical switches to core routers all the way to top-of-the-rack switches.

22 August 2014

TFI2014 - COISOC 16

SpeakersSam K. Aldrin

Working as Principal Engineer in IP Labs of Network Product Line R&D division at

Huawei Technologies, based at Santa Clara, USA. More than 20 years of experience

in the area IP, MPLS and Datacenter technologies. Driving various initiatives in new

technology development and research areas of IP packet, Mobile Backhaul,

Datacenter and Transport networks. Architected, designed and deployed IP/MPLS

and MPLS TP within various network products based on IETF and ITU standards. An

active participant at standard body groups and authored several RFC’s and drafts.

Prior to Huawei Technologies worked at Cisco Systems for more than a decade.

What is SDN?

SDN = ‘Self Defined Networks’ :D

SDN means different to different folks. Traditionally, control plane technologies are

closely tied to data plane. Network elements, distributed across the network, works

in harmony with control plane being the glue in providing signaling and establishing

data paths depending on the connectivity and polices configured. SDN definition

coined by Open Networking Foundation is the separation of Control Plane and Data

Plane. In my perspective, separation of control plane and data plane was in

existence since long, with protocols like MPLS, etc.

A true SDN in my definition is “Programmable network, without the need for Data

plane dependency on the Control plane, and enablement of the network topology,

data and configuration models abstracted, controlled and programmed through

standard API definition”. This will enable the networks to be dynamic, adaptable

and hardware independent, thus enabling the service delivery and new technology

adoption roll out at a faster rate. Although there is a benefit in terms of lowering of

CAPEX, but over all TCO may vary compared to traditional network model, at least

in the near term.

22 August 2014

TFI2014 - COISOC 17

SpeakersSam K. AldrinWhy are you excited about SDN?

SDN provides multiple benefits, which were not available in the traditional network

devices and deployments. Some of the key and exciting factors, which I personally

believe, are

Ability to program networks using software and make the networks, to be

application specific.

Ability to centralize intelligence and empowering service providers rollout

new services with minimal impact

Availability of API, not just CLI and SNMP only, to be able to program using

application and drive new applications to cater to the needs of services

Exciting opportunity to make networks move away from vendor lock-in’s and

giving the power to make networks to be multivendor capable and less of

hardware dependent.

Move from ‘what services network could support?’ ->To-> ‘Create network

on demand to support services, programmatically’

How does the network of the future differ from today?

Today, Networks are viewed as static physical infrastructure over which services

could be delivered, depending on the capability and resource availability. In order to

roll out new services and technologies, not only it is complicated but also very rigid

due to the lack of interface to program the network.

With SDN, it opens a world of possibilities to move the intelligence from hardware

dependent to software based applications. Rather than making the hardware a

dumb device, which many proponents of SDN used to say, it empowers the Operator

and applications to leverage the power of software, which used to be vendor

dependent, and make it open and with common interface, within the networks and

its devices. SDN leverages both declarative and imperative models to serve the

needs of various services based network designs.

Some of the initiatives which I am driving with SDN in conjunction with NFV

@Huawei, could potentially change the way networks and services are being rolled

out today

Seamless Virtual Area Networks – Provides end to end virtual networks

considering various attributes like QoS, Bandwidth elasticity, Protection services

End to end virtual services orchestration – Dynamic allocation, creation and chaining of

network function like policy controller, traffic optimizer, etc for a given service/tenant/DC

OAM for virtual networks – Ability to manage and administer services running over virtual

networks.

22 August 2014

TFI2014 - COISOC 18

SpeakersKaren "Shelly" Cadora

A 16 year Cisco veteran and CiscoLive Hall of Fame Distinguished Speaker, I am currently a

Technical Marketing Engineer for One Platform Kit (onePK) and other device-level APIs. I

have worked in development and marketing for a variety of products and solutions, from

security to voice to programmability. I have a PhD from Stanford University and a CCIE in

Routing and Switching.

How does the network of the future differ from today’s?

The networks of the future will not be completely unrecognizable to those of us who’ve

spent a good bit of our careers building and troubleshooting the networks of today. Some

fundamental characteristics of networks are determined by inescapable physical realities –

geography, distance, the diversity of transport media. But networks of the future will differ

in important ways.

In the future, automation will become a central part of network management. Device APIs

will enable new platforms (as well as existing toolchains) to automatically provision, monitor

and audit the network.

To enable automation, new kinds of abstractions will be required. Forget customized screen-

scraping for every vendor and software release. No more crafting network-wide policies

device by device. With simpler, higher-level interfaces into the network, fewer people will

need to know the obscure CLIs that we memorize today.

22 August 2014

TFI2014 - COISOC 19

SpeakersKaren "Shelly" CadoraHow does the network of the future differ from today’s? (continue)

For all the excitement about separating and centralizing the network control plane, scale and

resilience will mandate distributed intelligence in the network for a long time to come. But

that doesn’t mean that there won’t be pockets of deep innovation, particularly in greenfield

and/or highly homogenous environments. In these new landscapes for networks, parts of

the control plane will shift to a centralized model and some applications will achieve tighter

integration into the network.

The future is bringing software paradigms deep into networking.

Modularization, virtualization, programming interfaces – these are well-developed ideas in

software development that will change how we define, deploy, interact with and monetize

networks. Networks won’t just be discrete boxes communicating over IETF-standardized

protocols, but will expand to include modular pieces of software communicating over

APIs, with monetizable services at every interface, and specialized hardware for particular

use cases.

In short, network of the future will be a cyborg of sorts: embodied in the physical world but

spanning virtual space, deeply indebted to hardware and deeply infiltrated by software,

simultaneously distributed and centralized, sometimes customized and sometimes

monolithic, loosely coupled in some places and tightly integrated in others. The fundamental

tension between “easy” and “programmable” will not be resolved any time soon, but there is

material for innovation in the drive to achieve both.

22 August 2014

TFI2014 - COISOC 20

SpeakersScott Sneddon

Scott Sneddon is a Principle Solutions Architect and leads Business Development in APAC for

Nuage Networks, where he spends most of his time evangelizing the benefits of Network

Virtualization and Software Defined Networking. Previous experience includes Chief

Solutions Architect at Vyatta Inc, an innovator in Network Virtualization; Consulting

Engineering positions at Juniper Networks where he contributed to Cloud designs at IBM,

AT&T, France Telecom, and Telstra; Consulting Engineering positions at Alcatel-Lucent where

he contributed to MPLS network designs at AT&T (uVerse), Telus, and Verizon; and as

Director of Architecture at Exodus Communications where he led the global network

architecture team. His background is in architecting carrier scale Cloud environments and

service provider MPLS networks. He was talking about network virtualization before network

virtualization was cool.

Scott shared some thoughts on SDN:

I’ve been involved in SDN and networking for Cloud environments since 2008. What has

always excited me about this technology space is the opportunity to provide networking as

an easily consumable service in lock step with the Cloud platforms through automation and

programmability. We’re seeing an emerging trend in a “Policy Approach to Software Defined

Networking”, in which network services are defined in policy templates that are easily

consumed by DevOps teams in an automated fashion. In my talk I’ll discuss this trend, some

new concepts in defining network topologies, and some of the activities driving this trend

within OpenStack and OpenDaylight.

22 August 2014

TFI2014 - COISOC 21

SpeakersJoseph Marsella

Joseph Marsella currently serves as Senior Director of Strategic Solutions & SDN at Ciena

Corporation. In this role, he is responsible for overseeing the companies market focused

solutions including it’s SDN strategy and product offerings. Mr. Marsella has been at Ciena for

16 years, holding a variety of roles in product research and development, engineering, and

management of the Packet-Optical Transport and Packet-Optical Switching product lines.

Prior to joining Ciena in 1997, Mr. Marsella worked as a software engineer for Nokia Siemens

Networks. Mr. Marsella holds a B.S. from Clemson University, a M.S. from Johns Hopkins

University, and a MBA from Purdue University and ESCP/EAP Paris.

Joe was kind enough to elucidate on “What is SDN” for us, enjoy:

SDN began as an idea, an idea that we should truly separate the data plane from the control

plane thus unleashing greater programmability, innovation and agility out of the network.

That we could in essence separate the hardware from the software through standards based

flow table provisioning and open APIs. The implementation of such an architecture would

break the historical model of vendor specific ASICs, with vendor specific platforms and

control planes, with proprietary southbound protocols to vendor specific NMS/EMSs and

finally opening up through semi-standardized northbound interfaces to integrate into

customer’s BSS/OSS and back-office systems. This new approach would hold the promise of

greater innovation opportunities through enhanced network access, lower costs through

hardware and architectural simplification, and operational savings through commonality of

control, creating what promised to be an undeniably powerful business case for network

operators around the world.

22 August 2014

TFI2014 - COISOC 22

SpeakersJoseph MarsellaJoe was kind enough to elucidate on “What is SDN” for us, enjoy: (continue)

Today however the definition of SDN is not so straightforward. The term “SDN” has now

expanded from its original definition as an idea, to become almost an ideology, that when

taken to its extreme can be defined as: “anything software can do to improve the value of a

network”. It has become a rallying call for change in networking that stretches from access to

core, from user to datacenter, from mobile to fixed networks and through virtually all layers

of the traditional OSI model. It is no longer possible to generically speak about SDN and be

assured that the reciprocating party’s reference definition is the same. But with this said, this

lack of definition uniformity is not as troublesome as it may sound.

If we were to look at general themes and then attempt to categorize these seemingly

disparate ideals into factions they would tend to fall into one of three 1) the Purists – those

that remain true to the original definition of SDN, 2) the Pragmatists – those that resonate

with the benefits of SDN but aren’t prescriptive on the method utilized to achieve them, and

3) the Operators – those that are looking to finally solve the age old operational and multi-

vendor management challenges we’ve faced as an industry for years. There are clearly other

factions, beliefs and those that fit into multiple categories but these high level classifications

typically capture the majority of existing opinions out in the market today. But to truly

answer the question of “What is SDN?” we need to look a little deeper at these suggested

classifications.

The purist camp adheres to the true definition of SDN as originated out of Stanford and now

formally documented in the ONF. They generally believe in the strict separation of the data

plane from the control plane and the implementation of OpenFlow as an open southbound

protocol to achieve this. When implemented properly and completely the purist definition

represents the true revolution in networking that stands to be a defining moment in

networking history. But is the industry ready both from a mindset perspective as well as a

technological perspective to realize such a significant architectural transformation? Proof

points indeed exist and momentum is clearly in this direction but skepticism also remains,

which leads some in the market to more of a pragmatic view.

22 August 2014

TFI2014 - COISOC 23

SpeakersJoseph MarsellaJoe was kind enough to elucidate on “What is SDN” for us, enjoy: (continue)

The Pragmatists also realize that things have to change. They realize that for networks to

scale and to enable rapid innovation in a fast moving market that divisions need to be broken

and programmability needs to be improved. They also realize that software is the key to

enabling such a network transformation and believe SDN represents a unique inflection point

on the road to achieving this. But this desire for change is not focused solely on OpenFlow,

rather on a more varied set of APIs both at the network element and at the higher layers in

the controller. This improved programmability enables the opportunity for innovative

applications to be developed that are capable of maximizing existing revenue streams while

minimizing cost through greater network knowledge and real-time intelligence. In addition

they do not necessarily believe that foundational architectural change is required, that

control planes need to be separated from data planes. In short they believe that existing, or

in some cases new, interfaces communicating with existing distributed control planes still

have a place in the network and that with the proper abstraction and northbound interface

modifications a flourishing ecosystem of value-add software applications could be created.

The final more operational focused classification looks at the network operator’s side and

seeks to solve the traditional problem of multi-vendor management and service assurance.

They tend to recognize the growing trend towards “openness” and view it as an opportunity

to break the single vendor equipment to NMS/EMS based solution coupling that has existed

for years. To the “Operators” the ability to provide a single interface to provision multi-

vendor end-to-end services, the ability to simply view all networking alarms and faults from a

single screen, and the ability to see a combined multi-domain and multi-layer topology

represent examples of the promise that SDN can deliver. This definition even begins to blur

the lines between SDN controllers and traditional EMS/NMSs, making it difficult in some

cases to define where SDN beings and traditional management ends. In summary the

“Operators” view SDN as holding the promise of

multi-vendor management with enhanced service assurance.

The truth is SDN means all of these things and more. One’s exact definition of SDN is not as

important as having a clear understanding of the problems one is looking to address and the

risk vs. reward factors one is willing to accept. Ultimately a comprehensively defined SDN

solution addresses all these challenges and enables the user to migrate from one to another

as their business needs dictate. In conclusion what truly is SDN? – it is both an idea and an

ideology both representing a significant inflection point in the networking industry – unlike

any we have witnessed before……

22 August 2014

TFI2014 - COISOC 24

SpeakersGary Hemminger

Gary Hemminger is currently Head of Product Management for vArmour Networks. Prior to

vArmour, Gary ran product management for LogLogic, a Big Data, Security Analytics

company. Gary also ran product management and marketing for the Application Delivery

Controller, Network Management, and Enterprise Switching Business Unit. Gary ran

Marketing for IP Infusion, a maker of OEM routing, switching, and MPLS software for the

telecommunication and security industry. Gary has had marketing, product management,

and product marketing roles in network, security, and performance management products.

Gary received his BA in computer science from UC Berkeley and a master's degree in

computer science from Stanford.

Excited about SDN?

Traffic patterns in the data center have changed radically over the last few years. Whereas

in the past, much of the traffic was north-south (Internet to web-app-db server) today the

traffic is mainly east-west (ie server-to-server, app-to-app) in the data center. Recent studies

show that as much as 80% of the traffic in the data center is east-west. This shift is due to a

number of factors, including the steady move towards virtualized and software defined data

centers, SOA designs, mashups, and the general decomposition of applications.

Since east-west traffic goes from server-to-server, it is unlikely that in today’s data center

design, that the traffic will ever encounter a security device, such as a firewall or threat

management system. In addition, it is unlikely that organizations will have any visibility into

this traffic for troubleshooting, analytics, security, or even compliance purposes. Most of the

security solutions that are available today are designed to be placed at the perimeter. The

east-west traffic does not cross the perimeter, so there is no visibility or control of this traffic.

22 August 2014

TFI2014 - COISOC 25

SpeakersGary HemmingerExcited about SDN? (continue)

In the past, organizations trusted that the perimeter security devices would protect the data

center from attacks, but with the number of breaches occurring today, this assumption is no

longer valid. The trusted data center model is broken and many organizations are now

trying to put security and threat solutions into the data center. The problem is that with

traditional network designs, this can be a very tricky proposition. Trying to isolate and

control traffic between virtual machines can be very difficult. If an organization wants to

provide visibility and control for east-west traffic at L4 or L7, this means that security devices

like firewalls need to see all of the flows. For a heavily virtualized environment this means

the L4-7 firewall needs to see the flows between virtual machines on the same virtual

switch.

Since most organizations configure their virtual and physical switches at the top of rack in

Layer 2 mode, how do you insert a firewall between the physical servers or between virtual

machines on each hypervisor? This requires creating what could be a large number of port

groups and VLANs to isolate either individual virtual machines or groups of virtual machines.

Or at minimum, changing the underlying L2 network configuration.

As an example, assume a data center server rack has 20 servers each running a hypervisor

with 25 VM’s per hypervisor. Providing micro-segmentation and isolation for each VM would

require 20*25=500 port groups and VLANs per server rack. We could certainly group the

VM’s into zones (ie Web, App, DB) to reduce the number of port groups required, but still,

insertion of a L4-7 device in an L2 environment in the data center is somewhat complicated.

This is where SDN comes in and what makes vArmour (and I suspect other security

organizations) so excited. With SDN, the underlying L2 configuration requires no changes for

an L4-7 security solution to be inserted. Even at the virtual switch level, VM to VM traffic can

be redirected to the port where a firewall is connected without any change in the existing L2

configuration. This allows easy insertion and data chaining for security and other L4-7

solutions within the data center, and especially in heavily virtualized environments.

The excitement for vArmour and organizations is that with SDN, it is now easier and more

cost-effective to insert L4-7 devices in the data center to provide visibility, control, security,

threat management, and compliance solutions. We feel that security is one of the key use

cases for the advent of SDN, and in our experience using SDN opens the way for

organizations to cost-effectively design, build, and operate highly agile and secure next

generation data centers.

22 August 2014

TFI2014 - COISOC 26

SpeakersBrian Field

Brian Field is a Fellow with Comcast. He is currently working on developing technologies and

solutions that enable innovation within the network and router platform areas. Previously,

Brian was involved in a number of CDN, network and video initiatives within Comcast.

Previous to Comcast, Brian worked at ATT Broadband, MediaOne and USWest. Brian has a

PhD in Computer Science.

A Perspective on the Network of the Future.

22 August 2014

TFI2014 - COISOC 27

SpeakersBrian FieldA Perspective on the Network of the Future. (continue)

22 August 2014

TFI2014 - COISOC 28

SpeakersBrian FieldA Perspective on the Network of the Future. (continue)

Continue at http://www.coisoc.org

22 August 2014

TFI2014 - COISOC 29

SpeakersEric Osborne

Eric has been involved in the Internet industry for almost twenty years. His career took him

from a small startup ISP later acquired by Verio (now NTT-America) to Cisco, where he spent

the bulk of his career doing GSR, CRS, IP and MPLS work, and just recently to Level3 where

he is a principal architect. His current responsibilities include figuring out what use, if any,

SDN and NFV have to his current employer. He is a co-author, along with Ajay Simha, of

“Traffic Engineering with MPLS” (Cisco Press, 2003) and an active IETF participant. He lives

outside of Boston, MA with a kid, a wife and a dog, at least two of which are usually happy

with him at any time.

What is SDN?

SDN is either the narrowly defined, Stanford-birthed programmable 10-tuple or the more

nebulous, “definition of networks using software” that the industry seems to have turned it

into. I look at it as the narrow one. If you put the label ‘SDN’ on *everything*, as people

seem to be doing, you might as well put the label on nothing at all. The narrow definition of

SDN basically makes it look like policy routing, which we’ve had in routers for twenty years.

So what’s different this time? SDN is not just policy routing, it’s centrally managed,

ubiquitous, performant policy routing. This changes the conversation from “what can I do

with these vendor knobs in this code rev” to “what could I do if I had really good policy

routing everywhere in my network”, or maybe “what could I do if the dominant forwarding

paradigm wasn’t destination-based”?

22 August 2014

TFI2014 - COISOC 30

SpeakersEric OsborneWhy are you excited about SDN?

I draw parallels between SDN and MPLS.

I just told you that SDN is just high quality policy routing. But MPLS is nothing more than

frame relay with an IP control plane. Just because it’s easy to describe doesn’t mean it’s a

good idea to dismiss.

I was around for a lot of the early days of MPLS, and I saw people go through the same

mania that they’re doing now with SDN. I had people say “You need to help me get MPLS”.

I’d say “OK, why do you want MPLS?” And more often than not, the answer was “Because I

don’t have it!” And if the best business case you have is a tautology, you might want to go

work on that a bit.

But after the dust settled, MPLS changed the world. If we can get past the hype, I think SDN

might do the same.

How does the network of the future differ from today’s?

Yesterday’s epiphany is often today’s baseline. Again, look at MPLS. There are precious few

people that don’t do at least some MPLS, and half of those people are opposed to it on

“nobody my permission to do it first so I hate it” grounds.

SDN will be the same. Networks will get bigger and faster; that’s how the world works. Just

being big or fast isn’t enough. Networks also now need to be flexible, more so than they’ve

ever been. This is where the broader SDN umbrella comes in. SDN is a building block for a

more responsive network. It’s not the only thing (NFV is big here, along with orchestration

and service chaining). But it’s a big thing. And in a year, in three, in five, in ten, it’ll be the

New Normal. The iPhone is seven years old, and today a phone that only makes phone calls

is a museum piece. In seven years, if your network doesn’t take advantage of SDN and the

other stuff coming with it, will you be a network operator? Or a museum curator?

22 August 2014

TFI2014 - COISOC 31

SpeakersMatthew Wallace

Matthew Wallace is a veteran technologist with 19 years of experience in Internet services.

He is currently working on bringing next-generation cloud services to life at ViaWest as

Director of Product Development. He is the co-author of Securing the Virtual Environment:

How to Defend the Enterprise Against Attack, published in May, 2012 by Wiley and Sons, and

a frequent speaker on topics of cloud services and security.

He previously worked in Cloud Services Engineering at VMware as a Cloud Solutions

Architect, where he worked on service provider adoption, cloud reference architecture,

partner integration, and software development.

Matthew was the founding engineer of Exodus Communications’ Managed Security Services

team, now part of SAVVIS, Inc.

22 August 2014

TFI2014 - COISOC 32

SpeakersMatthew WallaceWhat is SDN?

SDN is programmable networking. Marc Andreessen wrote “Software is eating the world” in

2011, and this trend continues to extend to infrastructure, as widespread adoption of cloud

technologies and devops methodologies has led to an increasing expectation that all aspects

of the datacenter will be controlled by programming and policy, not hand crafted and

managed. SDN accomplishes this through things like overlay networking and network

function virutalization.

Why are you excited about SDN?

We see a lot of customers where the need for physical one-per-customer connections (even

within the datacenter) and hardware network functions, such as firewalls and load balancers,

add expense to a final solution. SDN, to me, has the potential to deliver faster, more

precisely controlled and “guaranteed correct” networking and network functions, at a lower

cost.

How does the network of the future differ from today’s?

The future of networking is application-centric rather. In the past, we’ve seen a focus on

wires, devices, netblocks, etc. The future is about delivering networking services – whether

that’s basic connectivity, private connectivity, or network functions like firewalling and load

balancing, intelligently to the application, controlled by software, with policies that migrate

with and adapt to the application, rather than the other way around.

22 August 2014

TFI2014 - COISOC 33

SpeakersJeff Doyle

Jeff Doyle, Principal Architect at FishNet Security

Specializing in routing and MPLS, data center architectures, SDN, and IPv6, Jeff Doyle has

designed or assisted in the design of large-scale IP service provider networks in 26 countries

over 6 continents. He worked with early IPv6 adopters in Japan, China, and South Korea, and

now advises service providers, government agencies, military contractors, equipment

manufacturers, and large enterprises on network design best practices.

Jeff is the author of CCIE Professional Development: Routing TCP/IP, Volumes I and II; OSPF

and IS-IS: Choosing an IGP for Large-Scale Networks; and is an editor and contributing author

of Juniper Networks Routers: The Complete Reference. He also writes blogs for both

Network World and for Network Computing. Jeff is one of the founders of the Rocky

Mountain IPv6 Task Force and is an IPv6 Forum Fellow.

22 August 2014

TFI2014 - COISOC 34

SpeakersJeff DoyleHow Does the Network of the Future Differ from Today’s Networks?

You don’t really need to look into a crystal ball to see what tomorrow’s networks will look

like. You really only have to look at today’s networking pain points. There are plenty of

interesting new technologies arising every day, but the ones that will succeed are the ones

that relive some of the “owies”:

Human Error. A person touching individual network elements remains the primary cause of

network problems. The more a complex system can be automated, without humans inserted

between elements or between layers, the more predictable and reliable the system

becomes. And speaking of reliability…

Unreliability. This is where vendors start talking about five-nines and MTBF. But reliability

has to apply to a system as whole, not just individual components. A network exists to

support applications, so we have to take an application-centric approach to building

networks.

Unavailability. Rather than looking at how quickly a network can recover from a failure, we

have to look at available our applications are over the network. Another way of looking at

this is application continuity.

Inflexibility. Yes, agility is a popular marketing buzzword. But it matters. Businesses cannot

wait months, weeks, or even days for a network to be adapted to new applications. The

network of the future must adapt almost instantaneously to changing application demands.

IPv6

It’s surprising that anyone is still arguing about this one. IPv4 is done. It’s depleted. And

trying to keep our networks limping along on this exhausted resource is increasingly like

squeezing blood from a turnip.

It’s time to give up our NATs and our highly segmented networks. The network of the future

will not be a dual stacked IPv4/IPv6 network. It will be an IPv6 only network. Complex

address design and management, “security through obscurity,” address dependencies in

applications, private addressing, address overlap, and VLSM will be as obsolete as IPv4.

Tomorrow’s networks will use one-size-fits-all subnets. They will have true end-to-end

security practices. They will be easier to troubleshoot from an address perspective (yes, IPv6

is easier to work with than IPv4). They will have better mobility. They will have better

multicast. Routing tables will be more manageable.

IPv6 makes all this possible. We move from the constraints of a highly depleted resource to a

practically unlimited resource.

22 August 2014

TFI2014 - COISOC 35

SpeakersJeff DoyleAutomation

We are already seeing the benefits of automation in the data center, where the compute and

storage elements are abstracted and controlled by an orchestration layer. Virtual machines

and virtual storage are agile, mobile, and adaptable.

But the network is currently a roadblock. Operators still have to manually reconfigure the

network to fit the changing needs of the compute and storage elements in a data center. This

means high operational expenses, high rates of configuration errors, inconsistent

configurations, and heavy delays.

SDN and NFV move us closer to an automated network, and while early efforts are mostly

centered on data center environments we can expect the lessons learned to quickly move

into enterprise and service provider networks. Networks will become abstractions,

controlled by the same orchestration that controls storage and compute. Network elements

can be deployed or withdrawn on demand as can stateful services such firewalls, load

balancers, and cache engines.

Programmability

Integrating the virtualized network into the same orchestration layer as compute and storage

gives rise to network programmability. This is more than the scripting we often use to

manage todays networks. The individual elements of the networks of the future – switches,

routers, firewalls, load balancers, and so on – will not be individually configured using diverse

operating systems and vendor-defined configuration statements. Instead, the network will be

holistically configured with a programmatic “If… Then… Else” syntax.

Programmability puts a layer of abstraction between the humans defining network behavior

and the network elements themselves. Configuration error is reduced, as are operational and

training costs.

Application Defined Networks?

All of these trends help bring the network more readily in service of applications. Looking a

bit further into the future, one can see a time when the orchestration layer controlling the

network becomes an arbitration layer between the network and the applications. The

orchestration layer knows, moment by moment, what network resources are available and

what immediate demands the applications have. The network then adapts dynamically, and

in real time, to changing application requirements: Application defined networks.

Humans then are removed entirely from the vertical stack. Our role becomes one of defining

policies to the network, rather than acting as intermediaries between the applications and

the network.

These trends are well underway, so the network of the future is not all that hard to predict. It

will be more deterministic, more reliable, more available, and far more agile than the

networks of today.

22 August 2014

TFI2014 - COISOC 36

SpeakersGeoff Mulligan

Geoff Mulligan is currently serving as a Presidential Innovation Fellow working on Cyber

Physical Systems (CPS) for the Office of Science and Technology Policy of the White House

and the U. S. National Institute for Standards and Technology. In this role, Geoff is working to

advance the development and promote the use and deployment of CPS technologies that

will improve the efficiencies of Healthcare, Energy, Manufacturing and Safety across America.

The SmartAmerica Challenge White House project is bringing together CPS and Internet of

Things (IoT) systems of systems overlaid on the backdrop of Smart Cities. The goal is to 1)

show the huge and direct benefits that will come from this type of technology deployment;

2) to identify common architectures, protocols, design patterns as well as gaps and 3)

advance the thinking surrounding the privacy and security issues related to the build-out of

these Smart Cities. Previously, Geoff helped create and deploy the Arpanet working on the

Arpanet architecture including the design of IPv6. He wrote the first version of IPv6 for the

PC, hosted the first IPv6 “Plugfest” and wrote the first embedded IPv6 implementation.

Geoff created and lead the standardization of 6lowpan (chairing the working group for 6+

years). He helped with the formation and founding of the Zigbee Alliance and the IPSO

Alliance – serving on the Board of Directors of both organizations and as Chairman of IPSO.

He worked with IEEE 1451 and wrote the IP section of IEEE 1451.5 and led the Networking

and Communications Task Group of ISA100. He has participated in a number of IEEE, ANSI

and TIA standardization efforts and in the initialization of the Smart Grid Interoperability

Panel (SGIP). After graduating from the Air Force Academy, he served in the Air Force and

worked for a few different companies including Digital Equipment, Sun Microsystems, and

Invensys. He helped found start-ups working on email security, next generation Internet

technologies and protocol design and technology development. He holds over 15 patents,

wrote a book on combating SPAM and testified before the U. S. Congress on computer

security.

22 August 2014

TFI2014 - COISOC 37

SpeakersGeoff MulliganGeoff offers the following thoughts on SDN:

SDN, if you strip away all the hype, offers some really cool opportunities for the future of the

Internet of Things and more importantly Cyber-Physical Systems (CPS). First for background,

CPS differs from the IoT in that the latter is today about sensing thing and the environment

and sending the data to the cloud and applying big-data analytics. The former extends this

using control-theory to interacting with the environment via machine controls, usually

without humans in the loop. In order for CPS to be deployed the underlying network fabric

needs to provide a higher level of service currently offered by today’s internet. The CPS fabric

requires a “high confidence network (HCN)” which will very likely rely on SDN to help

provide. This HCN needs to provide higher speed, improved determinism, bounded latencies

and resilience to network failure. With the deployment of SDN the benefits of CPS across

numerous industry sectors such as healthcare, energy, transportation, and manufacturing

may be realized. This next phase of the Internet, supported by SDN, can be to the Internet

what the Industrial Revolution was to manufacturing.

22 August 2014

TFI2014 - COISOC 38

SpeakersDoug Marschke

Doug is currently the founder of a SDN services company called SDN Essentials. Specializing

in Education and Professional services for various SDN architectures. Over the last two years,

Marschke has been immersing himself into SDN, presenting at colleges and with partners,

taking interviews on webcasts, authoring books, and joining leadership forums like Open

Networking Foundation, OpenDaylight and the European Telecommunications Standards

Institute. Prior to his transition as the SDN Evangelist, and CTO/Founder of SDN Essentials,

Marschke founded, built and sold Proteus Networks, a network services company that was

the premier stop for routing and switching education and professional services. He created

many of the Juniper Networks certification exams, including the JNCIE Enterprise Exam and

wrote and published JUNOS Enterprise Routing and Junos Enterprise Switching. Marschke

has been the leader of true “engineering rockstars” and the largest group of Ingenious

Champions at Juniper’s top VAR and Partner of the Year. He is certified as JNCIE-ENT #3 and

JNCIE-SP #41. Since he graduated from the University of Michigan, Marschke has been on a

mission with his ventures to help service providers and enterprises optimize their networks

for better performance, cost and reliability. He’s worked with national and international

students, customers, partners, associations and peers, so he’s prepared to take on and drive

SDN education and solutions with SDN Essentials. In his free time he runs and independent

film company (www.funnyhowfilms.com) and two san Francisco restaurants

(www.tacoshopsf.com) and (www.tacko.co).

22 August 2014

TFI2014 - COISOC 39

SpeakersDoug MarschkeWhat is SDN?

The classic definition of SDN is really the separation of control and forwarding with a central

(OS) environments. Two other confusing definitions have also arrived as well, one is overlay

architectures from companies like VMware, Plumgrid and Juniper. Lastly, adding an API onto

a current platform has been the solution for many of the incumbent vendors.

Why are you excited about SDN?

It really changes the way that we “network” networks. The modern problems we have to

solve need to be looked at differently as some of the older protocols and techniques are not

going to hold true.

How does the network of the future differ from today’s?

I would offer 3 predictions:

Less “big iron” solutions

Less reliance of proprietary single box solutions

More basic connectivity solved in software

22 August 2014

TFI2014 - COISOC 40

SpeakersMike Thompson

Mike Thompson is in the Office of the CTO and is the Director of Architecture and

Engineering for Application Delivery, Cloud and Security for A10 Networks. His career starting

in 1996 has been primarily focused on automation, application delivery and security. As the

lead developer for 3rd party integration and OpenStack for A10 Networks, he has

contributed to the service VM, service chaining and service insertion blueprints and working

groups. Mike was part of the A10′s team that assisted Microsoft as part of the Citadel and

Zero Access botnet takedown. Mike’s passion for DevOps grew in 2003 as the Sr. Architect for

a large web hosting company. His team was responsible for the development, security and

automation of the mass virtual hosting and datacenter environments that hosted 500,000

websites. The power of automation allowed his team to remain small… 3 people.

22 August 2014

TFI2014 - COISOC 41

SpeakersMike ThompsonWhat is SDN?

Software Defined Networking is the consumption of network resources and topology in an

automated fashion as to abstract the consumer from the physical infrastructure. This is done

through various techniques including API’s, Encapsulation, Network Function Virtualization

and Security/Policy inheritance.

Why are you excited about SDN?

Most endusers do not have an understanding of networking so why should they be held up

by it? The essence of SDN is to remove networking out the equation when provisioning

applications and services. SDN is not a new concept as many companies have been

automating network configuration and architecture for a long time. What is new and

interesting is the new methods of encapsulation, layer 2 scalability and the commoditization

of automation associated with the network, and standardization of API’s.

How does the network of the future differ from today’s?

This depends on the vantage point of the consumer or provider.

From the consumers perspective allocation of network resources changes dramatically for

one primary reason, the consume does not need to rely on another department or

organization for connectivity. One massive leap ahead is the data and information located in

the network that can be leveraged by the application. The future will enable new integration

patterns and collaboration techniques within the application deliver network. This can lead

to further enhancements associated with right scaling the infrastructure.

From the perspective of the provider the sky is the limits when the offerings become API

driven. The provider can extend a portfolio offering in ways that were not possible before.

The provider will be able to reduce or reassign resources the allow the companies primary

mission or business logic to be executed because of the improved efficiencies.

22 August 2014

TFI2014 - COISOC 42

SpeakersDouglas Gourlay

Vice President, Systems Engineering and Technology Marketing

As Vice President of Systems Engineering, Douglas Gourlay is responsible for bringing

modern products and solutions to our customers at Arista Networks. Doug is a key

technology and marketing evangelist for Arista's Software Driven Cloud Networking. Prior to

joining Arista, Doug was the Vice President of Data Center Marketing at Cisco Systems where

he held key roles in sales, systems engineering, and product marketing. Doug has filed or

holds more than twenty patents in networking technologies.

Prior to his work in the technology sector Doug served as a US Army Infantry Officer.

22 August 2014

TFI2014 - COISOC 4322 August 2014

A10 Networks, Inc. is an acknowledged leader in providing application delivery controllers (ADCs), carrier grade NAT (CGNAT), and Distributed Denial of Service (DDoS) protection with an array of deliver models from harward to cloud services.A10 Networks aCloud Services Architecture is a portfolio of products and features that enable integration with cloud orchestration platforms and SDN network fabrics, which is critically important to the automation and orchestration of L4-7 services in a cloud data center. The aCloud Service Architecture delivers improvements in provisioning speed, business agility and total cost of ownership. This allows new initiatives to be realized, whether for software defined data centers (SDDC), SDN or for network function virtualization (NFV) goals. Plug-in service modules for leading SDN vendors, including Cisco ACI, IBM SDN VE, Microsoft System Center Virtual Machine Manager (SCVMM), OpenStack, VMware vCloud Director as well as VMware NSX, eliminate the manual configuration of L4-7, security, and networking services.

TFI2014 - COISOC 44

The Internet Society is focused on the intersection of Technology, Policy and Education. As

ISOCers, we stand where those three circles overlap and are part of the sole global

organization to do so.

CO ISOC is the local epicenter of this focus.

Our purpose is to bring together local Internet experts, enthusiasts and amateurs in order to

increase our individual effectiveness. Collectively we can support each other, our region and

the Internet community at large by bringing our joint knowledge, experience and enthusiasm

for technology, policy and education together to advance all three.

The Internet Society, Colorado Chapter also serves as an environment for social and

professional networking in order to build a more cohesive culture for Internet professionals

and amateurs in this region.

The Colorado Internet Society is also an At-Large organization of ICANN part of NARALO.

More information at http://www.coisoc.org

22 August 2014

About the Colorado

Internet Society