TFI2014 Session II - Requirements for SDN - Brian Field

1. A
perspec(ve
on
“SDN”
Brian
Field
Ph.D.
Comcast
Fellow
BField
-­‐-­‐
Comcast
/
COISC
SDN
August
2014
1

2. Is
this
SDN?
Applications Applications
Controller
HTTP
OpenFlow
Router Router
BField
-­‐-­‐
Comcast
/
COISC
SDN
August
2014
2

3. Is
this
SDN?
(with
focus)
Controller
OpenFlow
BGP, ISIS,
etc
OF
Proprietary CLI
Proprietry OS/
chassis
Proprietary ASICs
Router Vendor Y
BGP, ISIS,
etc
OF
Proprietary CLI
Proprietry OS/
chassis
Proprietary ASICs
Router Vendor X
BField
-­‐-­‐
Comcast
/
COISC
SDN
August
2014
3

4. Is
this
SDN?
Really?
Controller
OpenFlow
BGP, ISIS,
etc
OF
Proprietary CLI
Proprietry OS/
chassis
Proprietary ASICs
BGP, ISIS,
etc
OF
Proprietary CLI
Proprietry OS/
chassis
Proprietary ASICs
Router Vendor X
Controller Vendors
A B
ONF
IETF
X Y Z
To get a
new feature
means...
Router Vendor Y Router Vendors
BField
-­‐-­‐
Comcast
/
COISC
SDN
August
2014
4

5. Why
does
Openflow
exist?
• The
Stanford
folks
wanted
to:
– Experiment
with
new
protocols
directly
on
their
produc(on
rou(ng
infrastructure
network.
– And
there
was
no
way
to
do
this
(mid
late
2000s).
• They
concluded:
– If
one
can
separate
control
plane
from
forwarding
and
– Define
an
“open”
API
between
the
two
(and
get
the
vendors
to
support),
one
can
test
new
concepts
“marioneYe
style”
on
the
network
infrastructure.
BField
-­‐-­‐
Comcast
/
COISC
SDN
August
2014
5

6. There
is
at
least
one
open
pla[orm
Legacy
open
protocols
Vendor
Proprietary
code
Insert ideas
here
Insert code
here
Linux
Proprietary ASICs
Hybrid platform
• Pla[orm
on
which
one
can
run
both
vendor
and
SP
defined
code.
• We
call
this
a
“hybrid
open”
architecture
(“HOpen”)
BField
-­‐-­‐
Comcast
/
COISC
SDN
August
2014
6

7. Comcast
changes
to
HOpen
pla[orm
Legacy
open
protocols
Vendor
Proprietary
code
Insert ideas
here
Insert code
here
Linux
Proprietary ASICs
Hybrid platform
• Added
Segment
Rou(ng
capability.
– Demo’d
Comcast
SR
running
on
HOpen
pla[orm
and
inter-­‐
op’ing
with
cisco
and
UCL
instances
at
IETF
July
2014
• Added
new
feature/TLV
to
ISIS
Quagga
and
ran
that
on
pla[orm
(turning
off
vendor’s
ISIS)
BField
-­‐-­‐
Comcast
/
COISC
SDN
August
2014
7

8. We
think
this
is
SDN…
(innova(ng
within
the
pla[orm)
Vendor Open
Linux
Proprietary
ASICs
HOpen
platform
(today)
Vendor Open
Linux
Proprietary
ASICs
HOpen
platform
(tomorrow)
Vendor Open
Linux
Proprietary
ASICs
HOpen
platform
(tomorrow++)
BField
-­‐-­‐
Comcast
/
COISC
SDN
August
2014
8

9. What
does
this
mean?
• HOpen
enables
Agility:
– If
a
SP
needs
a
feature
quickly,
we
can
develop
it
ourselves
without
pla[orm
vendor
or
standards
bodies
being
involved.
• HOpen
is
an
alterna(ve
SDN
paradigm:
– Leverage
the
control
plane
work
the
vendor
has
done
– Supplement
with
Operator
code
or
/
Open
Source
for
new
features
• HOpen
-­‐-­‐
Best
of
both
worlds:
– Vendor
support
for
“legacy”
features
– Operator
can
develop
new
features
as
needed,
prove
value,
vendor
rolls
into
their
code
base.
• Maybe
in
an
Open
Source
kind
of
way
BField
-­‐-­‐
Comcast
/
COISC
SDN
August
2014
9

10. Rough
consensus
and
working
code…
• This
paradigm
enables
[unaffiliated]
individuals
to
create,
develop
and
deploy
new
control
plane
protocols
on
produc(on
rou(ng
pla[orms
• Does
this
change
how
things
work
in
IETF?
• Might
this
be
good?
BField
-­‐-­‐
Comcast
/
COISC
SDN
August
2014
10

11. Quote
(me
“…With
great
power
comes
great
responsibility…”
-­‐-­‐
Voltaire
(and
later
FDR,
Ben
Parker–
Spiderman’s
uncle)
BField
-­‐-­‐
Comcast
/
COISC
SDN
August
2014
11

12. Thanks!
Feel
free
to
contact
me
at:
brian_field@cable.comcast.com
Further
details
on
the
HOpen
architecture
can
be
found
at
the
June
2014
NANOG
web
site
BField
-­‐-­‐
Comcast
/
COISC
SDN
August
2014
12