►
From YouTube: CNCF Network Service Mesh 2020-05-19
Description
CNCF Network Service Mesh 2020-05-19
A
A
Yeah
we
were
just
having
just
before
this
call.
We
have
the
issue
PR
call
and
we
sort
of
got
to
about
57
minutes
there,
three
minutes
till
the
top
of
the
hour.
Oh
no,
we
have
to
go
to
the
community
call
because
after
we
had
some
problems
with
zoom
bombing,
we
had
to
sort
of
put
various
security
things
in
place,
one
of
which
is
that
you
have
to
login
as
the
host
to
start
the
meeting,
and
we
haven't
figured
out
how
to
very
clean.
A
So
security
is
hard,
yes
cool,
so
we
usually
take
a
few
minutes
to
get
going
usually
about
5:00.
But
in
the
meantime
let
me
go
ahead
and
put
in
the
chat
window.
The
link
to
the
meeting
minutes
feel
free
to
add
anything
to
the
agenda
if
you've
got
anything.
Also,
please
add
yourselves
to
the
meeting
minutes
as
an
attendee.
A
And
we'll
probably
get
going
here
in
about
five.
Oh
one,
other
thing
to
be
aware
of
these
communities
are
all
recorded.
The
recordings
are
all
being
posted
semi-automatically
to
YouTube
by
stemming
automatically,
unfortunately,
they
they're
still
working
out
actual
automation
and
so
there's
a
lovely
human
who
is
kind
enough
to
do
this
for
us
every
week,
but
I
do
hope
they
manage
to
automate
it
soon.
C
C
C
C
Yeah
and
and
if
you
get
update
the
name
because
I
just
like
the
word
presentation
that
you've
been
accurately
reflect
the
and
the
name
of
it,
and
so
all
of
this,
we
we
keep
a
running
tab
since
the
beginning
of
time
on
everything,
we've
spoken
about
at
a
macro
level,
and
so
this
will
help
people.
So
if
someone
said
six
months
ago,
know
that
Jonathan
beri
presented
a
really
fantastic
thing,
easily
often
find
it
and
work
out
what
day
it
is
and
then
correlated
to
the
right.
That
would
serve
a
special
meeting
on
YouTube.
C
And
the
second
thing
that
we
have
you're
gonna
talk
about
vo3
today
after
the
presentation
but
don't
feel
pressured.
We
can
always
wrap
the
conversation
tomorrow
at
two
next
week
or
we
could
push
vol
3
back
to
tomorrow
or
next
week,
worst
case
scenario,
and
so
don't
feel
pressure
like
you
have
to
rush
or
anything
to
get
your
point
across
and
simultaneously.
C
C
A
A
Yes,
I
mean
I
think
effectively.
One
of
the
conversations
that
we've
had
things
we
had
come
in
is
NSM
convert.
Really
you
and
we've
been
saying
for
a
while
now
that
we're
going
to
follow
cute
khan's
lead
for
the
17th
to
the
20th,
because
we
already
have
the
speaker's
lined
up
and
everything
else,
but
it
might
be
a
good
idea
to
try
and
informal
eyes
that
a
little
bit
more
see
if
there's
someone
who's
interested
in
going-
and
you
know
chatting
with
VLF
about
what
the
CN
CF
about.
A
What's
involved
mechanically
that
kind
of
thing,
and
then
we
also
had
a
question
about
when
we're
going
to
open
up
our
CFP
for
NSM
con
north
america,
2020
embossed,
hopefully
in
boston.
You
know.
Hopefully,
things
have
settled
down
by
then
and
sort
of
see
see
about
that.
So
those
are
two
questions
that
have
come
in
on
the
mailing
list
and
but
I've
been.
C
Okay,
so
let's
get
started
so
welcome
to
the
next
network
service
met
remaining.
We
hold
this
particular
meeting
every
Tuesday
at
8
a.m.
Pacific
time.
We
are
also
involved
in
the
CNC
up
telecom
user
group,
which
occurs
every
first
Monday
at
8
a.m.
Pacific
and
every
third
Monday
at
3
a.m.
Pacific.
We
also
participate
in
the
CNC
f
ckin'
network
call,
which
occurs
every
first
and
third
Thursday
of
every
month
at
11:00
and
the
we
have
links
to
each
of
these
in
the
agenda.
C
We
also
so
in
terms
of
major
events.
I
had
a
new
event
come
up,
I,
don't
have
the
exact
leak.
Yet
that
event
is
it's
going
to
be
sometime
next
week,
I'm
going
to
be
giving
a
talk,
I've
made
it
zero
trust
for
openshift
Commons.
They
host
a
webinar
a
few
times
a
week,
usually
at
9:00
a.m.
Pacific,
so
I'm
aiming
I've
asked
them
for
Tuesday
at
9/8,
9:00
a.m.
Pacific
and
that'll
be
on
that
will
be
on.
There
will
be
of
Commons
webinar,
so
I
will
post
a
message.
C
I'll
post
the
final
link
here
in
the
agenda
once
I
get
it
and
I'll
also
send
a
a
blast,
those
both
on
its
Lac
and
on
the
mailing
list,
since
since
they
are
asking
for
people
to
register
ahead
of
time
and
we'll
do
one
more
blast
out
next
week
for
people
to
be
aware
of
when
that's
on.
So
that's
that's
really
I
think
what
day
is
that
I
think
it's
on
the
26
yeah
so
that
tentatively
on
the
26
of
my
head.
C
At
this
time-
and
we
also
have
cube
con
Clannad
upon
Europe-
the
virtual
experience
which
is
which
is
going
to
be
August
17th
through
20th-
it
will
the
cult.
So
all
the
call
for
papers
is
already
done.
Ok,
we
the
agendas
already
Hardy
out
in
terms
of
who's
speaking
for
it
and
it
will
be
hosted
virtually
so,
please
sign
up
for
it
I
if
you
have
not
done
so
already
simultaneously.
If
you
have
not
received.
C
So
if
you
have
not
received
that
the
people
to
contact
are
the
Estancia
of
cognitive
computing
foundation,
if
you're
having
trouble
finding
the
right
person
to
talk
with
and
that
scenario
come
ask
come
asked
me
on
the
slack
and
I
will
try
to
find
who
the
right
person
is.
So
we
can
work
out
what's
going
on
there,
we
we
also
are.
C
We
also
have
an
Edison
or
an
SM
con
and
Q
Khan
--use
the
way
we
should
just
pump
that
that
particular
part
here.
So
we
are
looking
to
to
drive
and
as
I'm
Connie
you
still
accept,
it'll
be
a
virtual
event,
and
so
there's
a
lot
of
there's
still
a
lot
of
logistics
that
we
need
to
do
from
from
a
mechanical
mechanical
perspective
and
as
far
as
you
know,
is
there
any
reason
why
we
would
not
have
an
endosome
con
you,
because
my
understanding
is
we're
still
long.
We.
C
So
there
we
go
we're
we're
still
on,
and
so
please
please
go
ahead
and
what
we
will.
What
we'll
do
is
we
will
get
more
information
on
how
will
host
it?
Well,
probably,
an
amusing
zoom
for
that
zoom
has
a
good
platform,
and
so
please,
if
you
represent
there,
please
be
ready
same
same
way.
You
would
be
beforehand.
This
will
actually
make
recording
a
lot
easier
and.
A
So
if
we
have
any
community
volunteers
who
would
be
willing
to
help
with
some
of
the
logistics
there,
I
mean
they
shouldn't
be
complicated
logistics.
It's
basically
things
like
you
know,
reaching
out
to
the
speakers
to
make
sure
that
they
understand
how
the
process
is
going
to
work,
that
this
is
still
happening,
that
kind
of
stuff.
If
there's
any
one
of
the
community
who'd
be
willing
to
volunteer
to
help
with
that,
it
would
be
very
much
appreciated.
C
Something
I
would
like
to
explore
because
for
me,
the
the
one
of
the
big
things
with
this
is
I
want
to
make
sure
that
we
have
this
community
aspect
as
well,
because
that's
the
real
reason
we
could
always
do
these
types
of
talks
on
these
taeyeon
the
weekly
meetings
and
have
an
ongoing
set
of
sessions,
but
I
think
the
real
value
in
it,
and
these
type
of
things
is
the
social
interaction
and
how
to
and
getting
to
meet
people.
So
what
I'm?
C
So
what
I'm
going
to
propose
to
propose
is
that
we
also
set
up
a
couple
slots
during
when
the
breaks,
maybe
I
doing
some
of
the
breaks
or
during
some
of
the
very
some
of
the
periods
that
we
we
set
up
slots
where
we
can
set
up
multiple
rooms.
People
can
promenade
from
one
to
the
other
and
just
need
to
meet
each
other
and
talk
in
a
free-form
environment.
So
I
think
in
that
way
that
the
community
can
get
to
know
each
other,
because
for
me
that
that's
a
huge.
A
A
I
think
we
probably
would
have
strongly
encourage
folks
to
do
is
to
hop
on
the
slack
channel
during
Acts,
because
one
of
the
things
that
I've
actually
experienced
with
various
the
virtual
events
that
I've
been
to
is
it's.
You
know
you
get
a
ton
of
stuff
that
goes
on
the
background,
at
least
that
I've
experienced
personally
with
the
slack
channels
right.
So
you
get
a
speaker
comes
up.
C
It's
you
know
we'll
do
the
best
that
we
can
on
our
side
and
make
sure
that
you
know
I'll
make
sure
that
I
present
myself
to
help
answer
questions
that,
as
the
heads
of
talks
go
through
so
there's
something
that's
really
not
clear
and
and
I'm
happy
to
to
bring
to
discuss
through
some
of
the
more
fine,
fine
grained
details
of
things
that
I
that
I
can
answer
so
yeah,
so
in
December
called
you
is
still
is
still
on.
We
will
have.
We
will
release
more
details
about
about
it
as
time
progresses.
C
If
you
are,
if
you
find
that
you
are
not
able
to
give
a
talk
for
for
some
reason,
like
your
your
you've
come
down,
sick
or
something's
happened
or
so
on.
Also,
please
get
a
hold
of
us
as
well,
because
then
we
can.
We
can
work
on
how
to
how
to
how
to
adjust
for
that
as
well,
but
yeah
I.
Think
in
this
particular
scenario
you
know
so.
C
I'm,
so
super
excited
to
to
see
the
way
we
have
a
very
strong
set
of
talks,
and
so
we're
so
I'm
glad
to
see
that
we're
still
gonna
be
able
Y
of
those
talks
out
there.
We
also
have,
oh,
it
is
North
America
coming
up
the
which
should
be
in
September,
28th
and
29th.
As
far
as
I
know,
that
is
not,
it
was
found.
C
Oh
and
yes,
Europe
has
been
postponed
and
I
have
not
seen
any
literature
come
out
on
that
just
yet
so,
when
I
seen
in
the
information
come
out
on
that,
I
will,
let
you
all
know,
but
considering
they've
been
pushing
back
events,
and
you
I
seriously
doubt
that
it'll
be
in
that
we're
going
to.
There
were
going
to
see
it
in
in
an
actual
physical
event.
At
this
point,
Q
Khan,
North
America,
is
still
on
as
normal.
Please
get
your
talks
in
you
are
running
out
of
time.
C
This
particular
week
in
terms
of
followers
has
has
been
no
change
in
the
status.
We
still
have
761
followers.
We
are
now
following
in
two
thousand
two
hundred
ninety-seven
and
we
have
1025
retweets,
tweets
and
retweets
that
we
have
done
with
folks.
That
call
reminders
the
last
week's
video
recap:
the
CNC
UX
weekly
webinars.
C
We
also
have
various
save-the-date
events,
such
as
the
virtual
elephant
and
testing
forum,
and
there
was
the
registration
for
virtual
cue
card.
We
also
have
retweeted
the
Linux
Foundation
training,
VMware,
open
source
work,
more
telecom,
TV
stuff,
more
things
you
added
towards
the
cloud
native
survey
and
the
CNF
test.
Bed
we've
also
posted
links
here.
So,
if
you're
interested
in
your
topic,
so
you
can
see
them
on
the
agenda.
We
linked
in
stats,
we've
also
added
to
followers.
So
we
recently
started.
C
C
We
also
plan
to
retweet
the
MSM
Connie
you
promoting
registration
and
share
more
information
about
an
SM
conics
things
go
past,
and
with
that
you
see,
we've
already
covered
in
the
main
agenda.
We've
already
covered
in
its
own
at
SM,
con
tu,
an
disabled
con
us
is
there
anything
that
we
want
to
say
about
that
in
the
agenda.
A
And
I
so
effectively
I
expect
we
probably
will
have
an
endosome
con
us,
but
we
are
just
starting
starting
to
plan
that,
because
of
all
the
disruption,
so
I
think
it
is
something
we
should
probably
work
out.
If
we
do
have
members
in
the
community
who
would
like
to
volunteer
to
be
part
of
that
planning
process,
that
would
be
fantastic.
A
C
Cool
and
I'll
I'll
see
if
I
can
find
some
some
potential
volunteers
as
well
and
and
some
of
the
people
who
are
not
present
but
yeah.
This.
This
is
a
these
type
of
things
are
primarily
around
just
from
from
a
work
scope
perspective.
They
can
be
at
different
levels
like
we
have
any
help.
They
will
take
I
mean
even
if
it's
just
like
responding
to
the
questions
or
so
on,
but
generally
the
the
the
planning
the
planning
around
this.
C
B
Looks
good,
okay,
so
quick
background
on
the
presentation
and
I'll
go
into
the
details
in
a
moment.
I
presented
this
at
the
network
cig
a
few
weeks
ago
and
Ed
was
there.
The
slides
were
about
ten
minutes
worth
of
content
and
30
minutes
of
discussion,
which
was
awesome.
It's
kind
of
the
reason
why
I
and
EDD
suggested
that
I
present
similar
content
here,
because
there's
also
opportunity
to
research
basically
lower
than
l7.
So
anyway,
if
you've
watched
the
recording
of
the
video
from
from
the
networks
a
course
on
my
slides
earlier.
B
B
So
you
know
overall,
this
is
around
networking
and
some
work
I've
been
doing,
get
started
out
as
work
for
my
own
startup,
but
really
I
hope
to
improve
the
overall
ecosystem
as
a
result
of
the
discussions
like
this.
So
quick
about
me.
My
background
is
product
management
on
other
platforms.
I
worked
at
companies
like
Google
and
nest
and
two
startups
and
everything
between
I'm,
currently
working
on
my
own
startup
and
I'm,
very
active
on
Twitter.
The
my
career
handles
beriberi
kicks
you're
familiar
enough
with
that
cereal.
B
That's
really
the
whole
story,
but
nonetheless
I.
Also
my
email
I
put
in
the
notes,
so
I
mentioned
work
an
IOT
platform.
This
is
super
high-level.
What
an
IOT
platform
is,
and
it
has
a
bunch
of
different
device,
messaging
capabilities
with
protocols,
security
updates,
but
really
in
you
know,
the
things
that
are
really
interesting
for
this
group
is
around
the
communication
between
let's
say
a
thing
and
the
platform
in
between
in
into
zooming.
B
It's
really
the
device
messaging
component
that
I'm
most
interested
in,
but
as
it
relates
to
this
overall
survey,
and
that's
just
one
type
of
networking
protocol
that
that's
really
interesting
for
us.
So
as
it
comes
into
IOT
and
it's
streaming,
there's
a
lot
broader
audience
here
and
there's
actually
a
ton
of
different
protocols.
B
Many
of
them
are
IP,
barring
and
as
a
small
start-up,
we
are
picking
one
or
two
particles
to
begin
with,
but
eventually
we
want
to
support
multiple
protocols,
and
that
requires
us
to
have
a
networking
infrastructure
in
place
that
enables
us
to
do
that,
and
you
know,
one
of
the
challenges
of
today
is
a
lot
of
platforms,
pick
one
and
you'd
sort
of
only
focus
on
that.
So
this
is
really
the
preamble
of
why
I
start
to
look
into
networking
protocols
in
general
and
in
native
protocol
implementations,
and
this
is
our
initial
architecture
all
right.
B
We
have
a
device
on
the
left
and
it's
communicating
with
our
cloud
infrastructure
on
the
right.
It's
using
one
of
these
IOT
protocols,
which
is
a
UDP
protocol
to
send
you
know
telemetry
data
and
and
control
data
back
and
forth
and
and
most
of
the
logic
lives
in
the
gateway.
This
gateways
is
in
application.
We
built
ourselves,
it
speaks,
is
protocol
and
it's
effectively
communicating
to
back-end
services
that
handle
the
response.
It's
pretty
typical
I
think
nothing
special,
nothing
fancy
the
actual
architecture
itself,
though,
is
while
it's
on
kubernetes.
B
It's
actually
not
companies
native
oli
effectively,
it's
a
VM,
it's
actually
a
container,
but
it's
also
running
the
same
application
on
our
desktop,
so
we're
not
quite
crowd
native
here
and
over
time.
You
want
to
move
to
more
cloud
data
and
architecture,
leveraging
things
like
proxies
and
across
the
network
service
meshes
and
things
like
that,
and
so
this
is
sort
of
the
way
we
think
about
evolving
to
a
more
cloud
native
way.
B
The
first
step
was
to
take
our
Gateway
and
implement
them
either
as
part
of
envoy
or
Iraq
envoy
around
it
and
about
a
year
ago
is
when
we
started
looking
into
it
and
it's
the
issue
I
raised
on
the
Envoy
team.
Well,
looking
at
how
all
seven
protocols
are
implemented.
Envoy,
actually
they're,
not
super
well
supported.
Http
is
very
well
supported.
B
Broadly
speaking,
the
cloud
native
landscape
is
optimized
for
HTTP
know
can
all
agree
that
make
sense,
but
as
a
result,
projects
from
kubernetes
all
the
way
down
to
individual
projects
that
are
being
spun
up
right
now.
I
have
a
lot
of
assumptions
around
the
networking
in
so
the
data
plane
and
even
the
control
plane
that
the
traffic
is
HTTP,
so
that
has
challenges
for
people
who
want
implement
non-hd
protocols
and
because
I
was
looking
at
IOT.
A
lot
of
my
use
cases
are
really
around
different
IT
protocols
and
and
ways.
B
Those
are
implemented,
but
through
discovering
and
chatting
with
the
community,
there's
actually
whole
other
domains
that
have
that
same
problem.
The
problem
in
that
they
are
not
running
hte
criticals
and
they
need
to
optimize
in
different
ways.
So
one
big
category
is
gaming
and
project.
Oconus
is
a
project
shape
from
google.
It's
the
game
serving
infrastructure,
that's
built
in
on
an
extensive
Eddie's
they
use
in
the
gaming
industry.
They
use
protocols
for
game,
state,
synchronization
or
real-time
communication,
that's
obviously
Nightbeat,
and
today
they
don't
really
have
a
good
solution.
B
Yeah
goddess
itself:
they
don't
have
it
built
in.
They
just
manage
the
game
servers
or
on
communities
and
say:
hey
it's
up
to
you
to
figure
out
how
to
do
game,
state
and
other
other
game
infrastructure
components
which
they
would
love
to.
Support
and
I
also
mentioned
real-time
communication,
and
one
in
particular
is
WebRTC
and
we're
using
to
some
degree
in
the
soon
call,
but
many
other
companies
use
it
as
their
full
solution.
Payan
is
a
is
a
really
cool
project.
B
It's
a
it's
a
whole
suite
of
packages,
written
goats
and
it's
a
native
project,
and
you
know
they're
looking
into
how
do
they
actually
run
it
on
on
official,
like
kubernetes,
the
creator
sean
and
the
project
lead
is
looking
into
how
you
do,
for
example,
load
balancing
for
WebRTC
video
traffic
on
IDs,
that's
really
an
uncharted
territory.
Ant
is
resolved
out
of
balance.
So
what
I
left?
What
I
came
away
with?
B
And
so
this
is
the
crux
of
this
work
and
it's
an
ongoing
living
document.
I've
had
the
opportunity
to
get
either
core
contributors.
Your
project
leads
to
to
expand
or
explain
or
correct
my
mistakes
of
my
survey
for
their
particular
project,
and
so
it's
quite
useful
at
this
point
and
it's
been
either
validating
some
of
the
ongoing
caps
if
there
were
caps
or
open
issues
for
those
maintainer
x'
who
actually
want
to
false
all
those
issues
or
just
highlighting
future
initiatives
than
they
may
may
be.
B
How
can
I
leverage
this
project,
and
so
SMI
is
a
service
mission
interface,
and
this
is
a
quick
overview.
Each
resource
in
the
SMI
has
this
concept
of
traffics
spec
and
that
trap
expect
allows
you
to
define
new
particles
and
even
in
the
in
the
definition
of
it,
it
says
each
resource
in
the
specification
is
meant
to
match
one
to
one
with
a
specific
protocol.
This
allows
users
to
define
the
traffic
you
make
protocol
specific
fashion,
so
the
takeaway
for
people
who
want
to
implement
alternative
protocols
is
SMI.
B
The
first
one
is
Oh,
make
sure
you
check
out
the
doc,
and
please
leave
any
comments.
It's
open
for
comments,
as
relates
to
the
network
service
mesh.
Where
does
that
them
connect
with
l7
protocols,
just
as
the
sort
of
correct
provision
of
enabling
these
these
application
protocols
to
work,
one
example
and
I
can
speak
to
it
a
little
bit
more.
Is
this
well
a
common
architecture?
B
This
is
IOT
specific
is,
maybe
you
have
your
device
services
and
your
application
services,
so
an
IOT
device
communicates
directly
with
something
like
our
gateway,
but
maybe
that's
a
more
robust
and
sophisticated
set
of
services
where
your
application
team
is
building
the
functionality
to
handle
that,
from
a
commercial
perspective,
we're
seeing
companies
who
actually
want
us
to
have
a
managed
device
cluster
that
they
can,
that
we
can
run
and
operate
within
their
own
deployment
and
they
their
application
team,
has
their
own
application.
Customer.
B
That's
really
interesting
from
a
cluster
cluster
communication,
but
also
from
a
a
managed
VPC
like
business
model.
I
think
it
might
be
some
opportunity
to
lemon
in
ascend
there
another
one
which
is
actually
related
but
different
for
IOT
deployments
that
are
maybe
not
clusters,
maybe
not
kubernetes.
So
imagine
a
local
network
or
a
you
know:
a
gateway,
a
deployed
network.
That's
one
domain,
one
node
network
domain
trying
to
communicate
with
a
even
another
on-premise
cluster
or
the
cloud
I
think
there's
these
sort
of
cross
domain.
B
Networking
challenges
that
and
I
know
from
experience
are
very
hard
to
implement
and
very
one
off
as
they
today,
especially
across
different
protocols.
The
other
area
is
as
implementers
of
these
protocols.
What
are
the
concerns
that
maybe
dip
below
the
actual
application
protocol
into
the
l4
to
l2
domain
start
layer?
And
you
know
whether
it's
routing
load,
balancing
congestion
control,
it
might
make
sense
to
implement
those.
B
You
know
l4
l3,
the
very
least
and
so
that
different
protocols
don't
have
to
think
about
those
those
types
of
concerns
and
the
last-
and
this
is
I-
think
one
last
thing
that
and
I
discussed
was
you
know
what
about
non
IP
protocols,
I
mentioned
IOT,
there's
a
bunch
of
IP
pairing
protocols,
but
they're
also
non
IP
protocols.
I
think
some
of
this
touches
on
the
the
telco
use
case
and
but
also
non
network.
B
A
Is
this
is
all
very
cool,
because
these
are
exactly
the
kinds
of
things
we
were
hoping.
That
would
be
so
when
you're
trying
to
build
something,
that's
going
to
be
so
much
and
generalizable
you'd
sort
of
imagine
what
the
problems
in
the
world
look
like
right
and
we
had
a
whole
set
of
problems
that
we
had
imagined
for
the
IOT
world
and
as
you're
well
aware,
real
problems
are
real,
not
imaginary
and
and
so
well
I.
A
Don't
think
we
did
a
perfect
job
of
imagining
the
problem
society
has
from
your
description
we
weren't
terribly
far
off,
and
so
some
of
the
architectural
whitespace
that
we
left
in
the
hopes
that
we
could
help
out
the
IOT
world.
It
looks
like
you
know:
we
we
have
some
of
that
space
here,
for
you
guys
right,
because
you
you
sort
of
are
the
you
know.
A
One
of
the
things
that
you
know,
we've
always
sort
of
pointed
out,
is
if
you're,
if
your
problem,
you
shaped
like
HTTP,
please
don't
talk
to
me,
the
envoy
or
the
sto,
or
the
kuma,
or
the
linker
D
people,
because
they've
got
a
killer
job
with
that
right.
They've
been
a
really
good
work,
but
if
your
problem
is
not
shaped
like
HTTP,
but
maybe
just
maybe
you
might
need
something
that
is
not
focused
on
it
and
it
sounds
like
you've
got
a
giant
pile
of
not
shaped
like
HTTP
yeah.
B
You
can
take
an
H
to
an
IP
header
and
do
whatever
you
want
with
it
in
in
prior
prior
companies,
there's
a
humongous
cost
benefit
and
various
forms
of
cost.
When
you,
you
can
kind
of
be
without
how
to
do
that,
marshalling
at
nor
marshalling
and
so
yeah
and
looking
at
the
NSM
vision
and
current
working
direction,
it's
well
aligned
with
with
IOT
and
again
those
non
IOT
use.
Cases
still
have
these
same
problems
or
are
challenges
that
are
not
HTTP
and
I.
B
Think
the
moment
you
you're
saying
about
the
practical
deployments,
it
will
likely
be
a
mix
of
it
because
because
your
application
will
have
HTT
p--
functionality,
which
is
probably
your
public
api
or
or
some
other
parts
of
your
serving
infrastructure,
and
then
your
your
non
HP
components.
So
this,
let's
take
a
WebRTC
deployment.
A
lot
of
that
keep
them
in
traffic.
B
That's
going
in
and
out
is
serving
the
okay
Shane
in
the
UI
and
the
you
quite
a
fat
client
that
talks
to
the
back
end,
but
then
there's
also
secondary
channel,
which
is
serving
the
real-time
communication
for
chat
and
state
sync
and
video
streams.
So
now
you
have
to
actually
manage
both
HTTP
and
on
HTTP
of
protocols
and
scaling
that
and
load
balancing
and
failover
all.
A
Those
come
on
it's
super
hard
for
all
of
us,
as
we
sit
here
with
our
iPhones
that
literally
have
supercomputer
level
powers.
To
imagine
how
resource
constrained
IOT
can
get
I
mean
the
other
one.
That
sort
of
strikes
me
is
if
you
can
do
a
more
intelligent
job
of
slicing.
Some
of
these
things
of
the
administrative
level
to
reduce
friction,
there's
a
whole
world
of
business
possibilities
that
open
up
in
IOT.
A
For
you,
I
mean
this
is
sort
of
like
one
of
the
things
that
really
impressed
me,
and
this
was
literally
circa.
2000
was
the
net
app
guys
really
nailed
this
with
storage,
because
if
they
sold
you
a
filer
like
and
and
one
of
those
just
started
gaining
wonky,
this
was
in
2000.
You
would
get
an
email
from
them.
That
said,
dis
43
on
shelf
12
is
wonky.
We
could
have
someone
there
tomorrow
morning
to
replace
it
is
that,
okay,
with
you.
C
B
A
B
Mean
I
keep
on
saying
that
phrase
over
and
over
and
a
lot
of
my
meetings
because
I
think
Kelsey
Hightower
said
it
was
talking
about
communities
recently,
and
this
is,
you
know,
I
really
hope
it's
boring.
I
hope
you
get
to
that
point
and
you
know
we
still
have
jobs
and
we'll
we
will
be
great,
but
no
one
will
be
so
frustrated
about
using
it
or
making
mistakes
about
using
it
or
trying
to
find
a
vendor
of
how
to
use
it
and
I
and
I
actually
hope.
Networking
gets
that
point
where.
A
There
still
others
yeah,
there's
this
beautiful.
So
if
you
haven't
read
the
technical
oversight
committee
at
the
CNCs
cloud,
data
definition
there's
a
beautiful
term
in
there
and
I
it
effectively,
the
term
is
minimal,
toil,
and
that
is
just
such
a
perfect
term,
for
where
we
want
to
get
right
and
minimal.
Toil
is
not
just
like
how
many
buttons
you
have
to
push.
It's
also
how
much
you
have
to
think
and.
B
Yeah,
in
you
know,
I
think
with
the
history
of
HTTP
and
Network
administration,
within
virtual
machine
infrastructure
and
code
Nicolaas
and
virtual
machine
infrastructure,
and
we
have
a
lot
of
experience
in
that
regard.
We
have
very
little
as
it
goes
beyond
sort
of
HTTP
traffic
and
workloads
and
I
certainly
don't
know
how
to
bridge
that
gap.
But
there's
a
lot
of
parallels
and
the
kinds
of
things
we
want
to
do
with
non
HTTP
traffic
and
again
like
tea
protocols
and
other
protocols
and
I
think
thinking
at
it
from
this
networks,
networks,
service
layer.
B
And
how
do
we
bridge
these
typical
mains
and
things
like
that-
are
a
key
piece
to
solving
that
and
getting
to
the
point
where
it's
boring
in
less
toil
and
yeah.
It's
kind
of
summery
I,
don't
know
how
to
had
a
best
leverage
the
work
everyone's
doing
here
and
had
it,
participate
in
and
help
the
ecosystem.
But
I
could
see
the
same
thing
with,
for
example,
they
also
familiar
so.
A
You
finally
solve
the
one
of
them,
which
is
how
to
hand
over
marketing.
You
know
I've,
occasionally
talked
to
IOT
cuz
like
when
she
lets
the
egghead,
the
IOT
terms.
Suddenly
it
was
a
thing
yeah
I've
had
in
terrible
conversations
with
some
IOT
vendors
at
one
point
who
have
occasionally
grumbled,
but
they've
been
this
for
40
years
now
and
then
suddenly,
there's
a
marketing
term
that
works
and
now
everyone's
excited.
B
Well,
I
mean
I,
think
you
think
network
service
missions
and
service
measure
are
a
great
lens
to
latch
on
to
at
least
for
now.
Yeah
I
think
that's
a
great
idea,
even
from
our
own
product,
offering
we're
focusing
on
one
protocol
with
one
very
specific
use
case,
as
it
relates
to
the
core
core
infrastructure
and
I
think
that
could
be
extended
on
to
a
network
service
mesh.
Okay,.
A
B
C
For
thanks
for
presenting
this
is
fantastic,
so
the
next
topic
was
on
the
was
on
the
vol
3
stuff,
because
we
had
some
questions
about
vo3
last
last
week
and
so
in
terms
of
VO
3.
Are
we
able
to
get
the
the
the
this
morning
where
there
was
a
really
beautiful
graphic?
There
was
that
was
the
contributors
leading?
Can
we
bring
that
bad
graphic
up
and
share
it,
I'm,
not
sure
where
it
was
stored
at.
A
E
Yep
I
have
provided
some
diagrams
for
real
free
if
you
have
some
salts
or
ideas.
You're
welcome
to
comment-
and
mostly
we
have
two
diagrams,
for
example.
Here-
is
a
abstract
diagram
of
basic
well
three
NEC
case
and
also
we
have
well
it's
use
case
of
deploy,
VL
free
energy
and
also
mostly
I
working
in
two
directions.
With
this
issue,
as
you
know,
vo
free
depends
on
some
stuff
like
inter
domain
and
fourteen
Pinter
domain,
and
currently
we
moving
to
new
DK
style
and
my
first
Direction
is
moving
and
adapting
features
from
monterrey.
C
We
had
some
questions
on
it
that
the
people
had,
and
so
what
we're?
Looking
to
sorry,
not
just
when
we,
the
previous
one,
the
new,
had
shown
the
one
with
the
the
graph
yeah.
So
so
this
particular
one.
What
we're
showing
off
is
three
clusters,
and
each
of
the
three
clusters
has
a
series
of
applications
that
are
on
them.
C
C
Now
these
that
is
not
really
seen
in
this
video
is
that
the
connections
that
were
making
have
we,
we
have
the
capability
to
drive
this
in
a
few
directions,
and
so
it's
not
like
it's
a
rigid
shape,
and
so
we
can,
if
you
want
to
plug
in
a
service,
then
the
subnet
that's
certainly
possible
simultaneously.
If
you
want
to
connect
a
point
to
point
like
maybe
you
have
two
databases,
one
is
in
like
domain-wide
and
the
others:
do
they
two
and
a
third
database
domain
three
and
you
wanted
to
do
synchronization
between
them
all
replication.
A
C
Perform
that
replication
with
without
having
to
worry
about
the
subnetting
of
the
rest
of
the
system,
and
so
we
I've
already
written
it's
called
points
to
play.
Type
am
so
we
wrote
a
point-to-point
I
Pam
that
is
capable
of
assigning
IP
addresses
that
is
based
upon
what
that
specific
set
of
services
is
currently
using
and
based
upon
what
the
remote,
what
the
remote
end
is
using
then
trying
to
find
something
that
I
can
correlate
between
the
two
of
them.
C
That
only
takes
into
consideration
the
minimum
set
of
networks
that
are
touched,
and
in
this
scenario,
it's
if
you
have
two
cards,
it's
what
what
subnet
should
I
not
interfere
with
on
pot
one
and
what
submission
I'm,
not
interfering
with,
ought
to
and
to
give
you
flexibility
on
how
to
drive
back.
That's
another
thing
that,
when
you're,
adding
and
as
well,
we
also
have
the
capability
to
journal
what
decisions
were
made
on
the
iPad
side.
C
We
separated
that
out
from
the
actual
iPad
itself,
because
then,
by
doing
journaling,
that
gives
you
the
capability
to
get
observability
on
what
your
your
iPad
decision
is,
makes,
and
if
your
iPad
ever
fails.
It
then
gives
you
the
capability
to
replay
the
decisions
made
in
order
to
recover
the
ipam.
C
If
your
iPad
does
not
have
that
information
and
it's
in
its
recovery,
and
so
of
course,
if
you
have
an
item
that
solves
those
problems
as
well,
you
can
just
leave
those
out
the
other
thing
that
is
not
shown
in
this,
but
is
something
that
we
are,
the
we've
done.
Some
work
on
is
DMS,
and
so
anytime
anyone
showed
you
a
l3
inter-domain
solution,
always
ask
about
DMS,
because
that
is
one
of
them.
C
It's
one
of
the
harder
things
to
solve,
and
one
of
the
things
that
we
have
is
we've
have
abstained
core
DMS,
a
fan-out
plugin
that
allows
you
to
to
add
and
remove
DNS
entries,
and
what
we'll
do
is
we
will
pass
in
DNS
information
through
the
context,
so
that
way
that
you're
able
to
to
establish
your
DMS
connections
and
remove
them
when
the
services
go
away.
So
so
this
is
just
a
small
taste
of
what
we
are
currently
building
in
order
to
establish
the
bridge.
C
Well,
three
paths,
and
because,
because
we're
trying
to
minimize
we're
trying
to
to
reduce
global
state
into
local
state,
then
from
a
scalability
perspective,
this
should
this
solution
should
work
out
a
lot
better.
As
we
add
more
and
more
clusters,
and
so
you
know
specifically
when
you
start
looking
at
things
like.
How
do
you
resolve
subnet
conflicts
and
how
do
you
resolve
routing
between
them?
And
so,
as
as
you
add,
more
systems
on
here?
C
Also
in
relation
to
to
some
of
this
work,
we've
been
migrating
a
bunch
of
stuff
off
of
the
off
of
the
mono
repo
into
the
into
the
SDK.
So
this
is
a
work
in
progress
once
the
SDK
is,
is
in
a
good
state,
then
we
should
have.
We
should
have
all
of
these
services
round
through
the
SDK
itself,
so
this
means
things
like
I
can
become
pluggable.
You
can
compose
the
iPad
using
the
SDK
which
respects
the
network
service.
C
/
API
implements
the
network
services
actually
API
in
order
to
add
in
things
like
ipam
DMS
support,
and
this
will
give
you
the
capability
to
take
what
we
written
and
you
can.
You
can
compose
things
for
the
reference
implementation
compose
them
with
things
that
are
within
your
infrastructure.
So
if
you,
if
you
want
to
use
something
a
different
day
to
play
another
than
VPP,
you
can
swap
that
out.
C
D
I
had
a
quick
one,
we
don't
have
much
time
so
if
you
can
just
quickly
answer
so
back
in
the
days
when,
when
this
was
first
presented
when
the
first
NSM
comb,
the
problem
was
I'm
pointing
here
on
my
screen,
but
I
would
try
to
describe
it.
So
the
link
between
the
VPP
scene
domain,
1,
&
2
and
you
know
also
the
same
width
between
1
&,
3
&,
the
twin
3,
is
this
VPP
managed
connection.
D
A
So
this
is
the
interesting
part.
That's
going
to
depend
very
much
on
which
feel
free
and
secant
came
up.
First.
Ok,
so
imagine
that
you've
got
that
basically
domain
2
and
domain
3
are
already
up
and
going
concerns
and
domain
ones.
Vl
3
and
as
he
comes
up
right,
it's
going
to
basically
look
around
and
say:
ok,
what
are
the
other
bl3
it'll
go:
ask
the
floating
Registry.
A
What
who
all
is
providing
the
EDL
three
interconnected
network
service,
but
I
need
to
go
talk
to,
and
it
will
find
the
feel
3
feel
3s
for
MSC
domain
2
and
domain
3
and
it
will
go
and
send
a
request
to
them.
Say:
hey
I'd,
like
a
connection,
so
in
that
case
domain
one
would
be
the
client,
but
if
a
domain
for
came
up
after
both
of
those
it
would
then
be
the
client
to
the
others
in
stringing
up
the
interconnect
that
make
sense.
D
C
Yes,
oh
I,
think
yeah,
there's
definitely
gaps
in
here
that
we're
gonna
have
to
answer
as
we
progress
forward
and
we'll
adjust
those
as
we
as
we
build
it
out
as
well,
but
in
a
nutshell,
like
from
all
the
iterations
that
we've
done.
This
is
where
this
is
where
we're
currently
building
towards,
and
so
the
key
behind
it
is
really
about
floating
registry
and
the
middle
ties
it
all
together
and
I'll.
See
you
about.
C
Up
sharing,
I
ended
up
manually
copying
over
to
the
description
of
the
network,
service
and
I,
would
service
endpoint
and
the
network
service
manager
to
the
second
cluster,
and
then,
when
I
performed
the
connection,
then
the
connection
just
worked,
and
so
that
registry
is
really
the
key
behind
it,
because
we
can.
We
can
have
that
registry
back.
This
is
an
anchor
that
binds
all
three
of
them
together
or
more
and
provides
the
and
provides
enough
context
for
the
reach,
dropping
the
connections
so.
A
The
other
thing
that's
kind
of
cool
here
to
realize
is
like
it
looks
like
there
are
various
components
here
in
the
system
right.
But
if
you
look
at
things
like
the
proxy
network
service
managers,
so
in
just
the
same
way
that
the
network
service
manager
on
a
kubernetes
node
is
effectively
managing
the
local
environment
for
the
clients
and
the
endpoints
that
are
running
on
that
node
and
allowing
them
to
communicate
with
the
outside
world.
The
proxy
network
service
manager
is
doing
a
similar
sort
of
behavior,
but
for
the
entire
domain
right.