►
From YouTube: CNCF Network Service Mesh 2020-05-12
Description
CNCF Network Service Mesh 2020-05-12
A
A
B
A
A
B
A
So
we're
gonna
put
that
on
hiatus
pretty
pretty
soon,
so
we
have
one
more
when
we're
meeting
in
that
area.
If
we
start
to
get
interest
in
people
in
in
those
time
zones
and
then
we'll
see
about
restarting
it
up,
we
also
participate
in
the
CN
CF
Telecom
user
group,
which
the
next
meeting
is
going
to
be
Monday
May
18th
at
3
a.m.
Pacific
time.
A
A
A
couple
major
things
that
have
happened
so
cube
Cod
has
beta,
has
gone
virtual
and
so
in
August
17th
to
20th
we
will
be
having
the
virtual
kook
on.
The
schedules
should
still
be
the
same
in
terms
of
in
terms
of
the
main
sessions
for
NSM,
as
the
tentative
approached
over
you
that
we're
going
to
take
is
that
we
still
want
the
SM
Khan
to
occur,
and
so
we
we're
working
out
details
on
as
to
what's
going
to
happen
with
that.
A
You,
if
you
have
registered
of
$50
for
a
us
for
an
SM
con
that
should
have
been
refunded
to
you,
since
the
reason
for
the
for
the
$50
was
to
ensure
that
that
people
who
signed
up
were
indeed
attending.
So
if
you
signed
up
look
out
for
that,
$50
reverse
on
your
credit
card
or,
however,
you
paid.
The
second
thing
is
this:
the
second
thing
we
did.
We
were
doing
with
that
money
was
paying
it
into
the
diversity
fund
in
order
to
help
people
get
to
keep
Khan.
A
So
will
we're
gonna
work
on
getting
details
about
about
the
next
set
of
some
NSM
con
@q
Connie
you
so
in
terms
of
of
other
events
moving
forward,
we
also
have
o
ne
s
Los
Angeles,
that
is
a
that
is
occurring.
It's
that
is
going
to
be
in
September.
The
o
ne
s.
Europe
is
currently
been
postponed
and
to
be
determined.
I,
don't
have
information
on
that.
Interestingly,
the
the
ona
s
has
been
doing
virtual
keynotes
and
virtual
many
conferences,
so
I
would
expect
considering
many
of
the
countries
there
are
continuing
just
postponed.
A
I
would
expect
this
to
probably
go
over
Childers.
Well,
the
final
one
cube,
conned
and
cloud
cloud
date
of
con
North
America
is
still
in
Boston
call
for
papers
are
still
open.
They
closed
on
June
12th,
so
that
is
one
month
away
from
now.
So
make
sure
you
get
your
your
entries
in
and
as
of
now,
there's
no
schedule
change
to
cube
con
North
America.
A
So
in
terms
of
announcements,
so
the
first
one
is
IDI.
It
is
not
showing
up
today
because
he's
feeling
he's
feeling
sick,
it's
non
kovat
related.
He
should
be
feeling
better
with
with
a
bit
of
rest,
so
I
other
other
things
that
are
going
on
in
terms
of
the
in
terms
of
the
community.
Is
we
also
with.
C
A
Actually,
I'll
save
those
for
for
these
for
the
main
call,
so
so
in
terms
of
social
media,
community
team.
So
in
terms
of
our
stats,
we
are
now
up
eight.
We
have
761
followers.
We
are
following
additional
10
people.
We
shout
out
18
different
retweets,
including
call
reminders.
Last
week's
video
recap
ciencia
webinars.
A
By
the
way,
if
you
haven't
seen
the
CN
CF
webinar
on
zero
trust,
please
make
sure
to
go,
see
it.
There
is
a
link
further
down
in
the
in
the
agenda
from
last
week,
and
you
can
also
find
it
if
you'd
look
up
zero,
zero
trust
and
you
put
my
name
Frederick
and
CN
CF
webinar
into
Google.
It
should
be
one
of
the
top
hits.
A
In
terms
of
major
events,
there
is
now
registration
for
open
source
summit
and
embedded
Linux
conference
day.
So
another
virtual
experience
you
can
sign
up
for
that
now,
they've
greatly
reduced
the
cost
of
this.
If
I
recall
properly,
I
believe
it's
I
think
$50
to
join
in
so
I
there's
a
lot
of
really
great
material
and
open-source
summit,
and
it's
actually
one
of
the
places
where
an
ascended
one
of
its
first
set
of
talks
so
highly
recommend
joining
em.
To
some
of
those.
You
learn
a
lot.
We
also
have
LF
networking
which
is
going
on.
A
They
are
providing
they're,
also
providing
their
training
courses
and
certifications.
We
tweeted
out
information
about
edge
networking
new
guides
that
they
put
out.
We
reposted
things
in
kubernetes
about
how
to
how
to
thrive
in
May
and
evolve
as
a
containers,
orchestration
platform
and
there's
support
for
open
source.
We
also
posted
a
telecom
TV
panel
discussion.
Tell
about
how
telecoms
must
have
a
clear
migration
to
cloud
native
if
I
recall.
This
is
actually
one
that
I
that
I
had
this
when
I
participated
in
no.
This
was
a
different
one.
A
I
participated
in
some
telecom
TV
stuff
before
in
the
past,
in
terms
of
in
terms
of
migrating
to
cloud
native,
definitely
recommend
taking
a
look
at
some
of
their
stuff,
so
it's
it's
also
hosted
people
like
Dan,
Brown
and
Taylor.
In
addition
to
myself
in
in
either
in
other
videos
in
terms
of
LinkedIn
stats,
we've
added
an
additional
follower
and
we've
reposted
everything
in
Twitter
into
LinkedIn
the
plan.
A
In
terms
of
our
plans
way,
we
intend
to
retweet
the
the
contributor
podcast
and
continue
to
promote
the
registration
for
NSM
con
EU
and
promote
the
sessions
there.
So,
in
the
terms
of
in
terms
of
the
agenda,
is
there
anything
that
anyone
would
like
to
bring
up
I
have
a
community
status
update
I
can
give,
but
before
we
do,
that,
is
there
any
topics
that
anyone
would
like
to
discuss
or
ask
questions
about.
D
This
is
a
Java
berry
here.
First
time
joining
I
actually
presented
last
week
at
the
Signet
working
about
a
research
project,
more
of
a
survey
of
l7
protocols
and
in
and
across
the
CN
CF
landscape.
It's
in
relationship
to
startup
are
working
on,
but
it's
really
to
identify
how
networking
is
implemented
and
some
of
the
assumptions
around
effectively
HTTP
in
a
lot
of
projects
and
where
their
opportunities
as
a
community,
we
can
improve
those
capabilities.
D
A
D
D
Yeah
and
we
had
a
little
interlude
about
that
in
the
it's-
an
area
I
have
to
go
deeper
in
because
a
lot
of
the
use
cases
are
definitely
layer.
Seven
and
the
model
as
long
as
layer
3/4
is,
is
doable
then
great,
but
there's
actually
lot
of
protocols
that
are
not
even
IP
based
or
our
sort
of
quasi
IP.
And
that's
where
ed
was
saying:
hey,
there's,
there's
some
stuff.
D
You
know
you're
all
looking
into
so,
for
example,
ultra
low
bandwidth
protocols
in
IOT
again,
because
my
background
focus
there:
they
they
don't
even
use
IP
framing.
So
how
do
we?
How
do
we
square
that
circle,
kind
of
kind
of
thing?
And
that's
what
definitely
piqued
my
interest
and
potential
area
I?
Think
of
discovery
and
conversation
yeah.
A
We're
definitely
definitely
well
aligned
in
that
space,
then,
because
that
is
squarely
one
of
our
one
of
the
things
that
we're
looking
that
we're
looking
at
not
that
specific
use
case
directly,
but
analogous
one.
So,
for
example,
if
you're
working
in
the
telecom
space,
they
also
have
a
variety
of
different
layer,
2
and
layer
3
protocols
that
they
use,
that
are,
that
are
not
necessarily
IP
based,
and
so
it's
it's
not
uncommon.
A
To
find
things
like
MPLS,
and
one
of
the
things
that
we
found
in
the
OpenStack
world
is
that
many
of
the
vendors,
because
Neutron
was
squarely
IP
and
Mac
based
internet
based.
What
people
would
do
is
they
would
say.
Oh
I
need
an
MPLS
label
and
there's
no
MPLS
cycle
that
was
available,
and
now
you
can
extend
the
API
a
little
bit
more.
So
it's
a
little
bit
more
flexible,
but
still
in
a
show
where
ok,
there's
no
MPLS
label
available.
So
how
do
I
inject
one?
A
There
use
cases
done,
and
we
end
up
with
fragmentation
at
that
point,
so
I
so
I
think
the
things
that
you
described
and
we
go
beyond
kubernetes
as
well.
So
this
isn't
just
like
this
is
not
only
for
kubernetes
networking.
It's
also
about
how
do
you
connect
things
that
are
that
are
outside
of
kubernetes
with
each
other
and
with
kubernetes
things,
or
to
do
things
where
there's
no
kubernetes
in
there
at
all
so
yeah,
so
I
think
I
think
will
be
relatively
well
aligned
at
a
future
time.
D
Over
it,
awesome,
yeah
and
I
think
there's
based
off
of
just
you
know:
it's
a
nice
conversation
and
this
one
there's
areas
I
want
to
go
and
extend
that
I
haven't
already
so
I'm,
even
more
than
happy
to
present
what
I
presented
to
the
cig
in
an
upcoming
meeting,
but
then
identify
some
of
those
those
opportunities.
So,
for
example,
what
happens
if
you
use
one
of
these
protocols
that
are,
you
know
not
l7
based,
and
how
would
you?
How
would
you
implement
that?
D
How
would
you
do
load,
balancing
congestion
control
security
and
all
those
things
or
how
do
how
do
network
operators
like
telcos,
but
also
these
up-and-coming
satellite
providers
who
were
working
with
early
on?
How
do
they
integrate?
You
know
their
call
it
like
l1
l2
protocol
and
actually
travel
all
the
way
through
so
yeah
I
think
this
is
there's
a
lot
of
interesting
ideas
and
opportunities
did
to
make
sure
we
build
the
right
things.
A
Yeah
as
a
person,
who's
worked
on
ham,
radio,
that's
also
very
exciting
to
me,
and
so
in
terms
of
you
in
terms
of
getting
them
to
to
communicate.
Yeah
I
you
yeah
that'll,
definitely
be
quite
interesting.
So,
let's,
let's
make
sure
that,
when
you're
ready
to
to
present
that,
let
us
know
and
we'll
we'll
make
sure
they
get
did
you'll
stick
around
the
agenda.
Great.
Thank
you
cool.
A
A
Instead
you're
only
building
things
that
have
that
have
changed.
So
that
is-
and
so
that's
that's.
The
first
thing
that
were
there
were
that
we're
focusing
on
he's
getting
that
I
guess
it
was
a
go
compiler
accelerator,
it's
very
similar
to
C
cache
if
you've,
if
you've
worked
with.
If
you've
worked
with
that.
A
So
another
thing
that
we're
working
on
is
for
the
new
SDK
I'm,
getting
very
close
to
having
a
full
full
working
example
showing
off
the
the
ICMP
responder.
So
we
have
a
working
ICMP
responder
in
the
main
repo.
This
is
this
one
is
using
the
new,
the
new
SDK
and
this.
This
includes
an
example
that
that
goes
from
from
from
client
server
and
back
includes
things
like
authentication.
It
has
has
code
in
there
demonstrating.
How
do
you
do
spiffy?
How
do
you
get?
A
A
As
a
as
a
floor
working
example
in
terms
of
in
terms
of
the
more
detailed
work
that's
going
on,
there
is
continued
to
work
for
inside
of
the
MSM
daemon
to
add
callbacks,
and
so
callbacks
was
an
interesting
thing
that
we've
added
into
our
G
RPC
tooling,
where
you,
when
you
connect
in
with
G
RPC.
One
of
the
problems
that
tends
to
arise
is
centered
around
bi-directional
communication.
A
So
G
RPC
is
a
server
client
based
model.
It
does
not
have
a
true
bi-directional,
even
though
I
believe
the
HP
framing
the
htv-2
itself
doesn't
support
it,
but
the
framing
system
itself,
I
believe
does,
and
what
we've
added
on
to
it
is
a
callback
system
that
does
not
modify
G.
Every
C
is
built
on
top
that
allows
you
to
create
callback
so
that
you
can
get
some
controlled
bidirectional
communication
between
multiple
systems.
A
What
this
will
allow
us
to
do
is
to
create
a
callback
that,
when
certain
events
happen
in
the
network
service
manager
that
will
be
able
and
within
the
client
that
will
be
able
to
get
that
bi-directional
communication
between
two
systems
and
not
have
to
work
with
multiple
with
multiple
sockets.
At
that
point,
another
thing
that
we
are
focusing
on
is
additional
work
on
the
VL
3
space.
So
we
have
registry
work
that
is,
that
we're
currently
focusing
on
specifically
with
some
code
generation
around
that
building
via
the
chain.
A
The
vol
3
is
our
is
one
of
our
main
efforts
that
we
are
driving.
So
basically,
we
can
do
l3
quite
quite
easily,
like
that's,
that's,
not
a
problem,
but
when
you
start
to
put
this
thing
into
production,
then
this
is
where
things
like.
How
do
we
make
sure
that
you
get
resiliency,
that
you
have
the
ability
to
load
balanced
across
multiple
nodes
as
across
across
cluster
organizational
boundaries,
so
that
you
can
and
how
do
you
make
sure
that
you
failover
properly
that
you
get
your
DMS
set
up
properly?
What
if
VMs
fails?
A
How
do
you?
How
do
you?
How
do
you
heal
it,
and
so
our
VL
3,
it's
a
milestone,
is
a
production
quality,
vol
3,
where
you
can
hook
up
multiple
clusters
together
and
have
them
interoperate
with
the
with
each
other
work
loaded
workload,
and
so
it's
the
production
version
of
that
use
case.
So
right
now
the
focus
is
on
is
on
the
the
registry
to
get
worked
on
in
that
space.
C
A
C
A
A
B
A
I'll,
ask
I'll,
ask
Andre
Andres
that
are
you
on
right
now,
yep
yep
yeah!
If
you
can,
if
you
can
have
your
have
some
of
your
team,
look
into
that
and
and
add
that
to
the
agenda
for
next
for
next
week,
and
then
we
can
go
over
the
reveal
three
use
case
next
week
in
more
detail
for
people
to
see
what
we're
doing
yeah.
B
A
A
So
I
gives
us
an
agenda
for
next
week.
Thank
you.
Thank
you
very
much
yeah,
and
so
this
stuff
is
still
relatively
early
and
it's
in
it's
in
its
lifecycle,
but
we're
working
really
hard
to
to
make
that
all
happen
and
in
terms
yeah
and
in
terms
of
the
new
repo
yeah.
Well,
we'll
continue
to
make
sure
that
that
stuff,
I
I
haven't
pushed
it.
A
I
have
not
merged
anything
into
master
just
yet,
because
what
I'm
doing
is
I'm
doing
an
initial
first
pass
where
I
get
things
to
to
work
and
then
I'm
going
to
break
it
down
into
small,
commits
that
I
can
push
up
in
a
more
controlled
way.
So
I
don't
want
to
push
to
I,
don't
want
to
push
a
large
set
of
changes
all
at
once.
So
that's
that's.
My
one
hesitation
at
getting
this
getting
this
out.
A
Asap
is
I
want
to
make
sure
that
that
we
give
the
changes
time
to
trickle
in
and
get
the
proper
reviews
as
well,
just
to
make
sure
we
keep
the
quality
high
so,
but
once
the
ICMP
responder
is,
is
up
and
running,
I'll
push
the
stuff
that
I
have
up.
Now,
it's
it's
part
of
a
branch
called
ICMP
server,
so
I'll
push
up
what
I
have
it's
very
messy
code
right
now,
because
I'll
push
it
up?
What
I
have
right
now,
but
I'm
going
to
continue
to
improve
it,
to
improve
that.
C
A
Cool
okay,
so,
and
another
thing
we've
been
focusing
on
is
VPP-
is
on
getting
wire
gar
support
directly
into
into
VPP.
So
for
those
of
you
that
are
not
familiar
with
wire
guard
wire
guard,
is
a
point-to-point
tunneling
cryptic
cryptographic
tunnel
that
you
can
that
you
can
use
to
connect
multiple
systems
together?
It
has
one
payload
that
payload
is
IP,
and
so,
in
terms
of
it
bow
has
mainly.
It's
now
been
built
into
the
mainline
kernel.
A
A
The
second
thing
that
that
we
can
do
is
build
that
support
directly
into
the
EPP,
so
that
means
we
don't
have
to
to
waste
any
kernel
interfaces
on
it,
and
this
actually
has
some
has
a
nice
property,
because
there's
a
limitation
on
every
system
is
how
many
kernel
interfaces
you
can
have
how
many
ARP
requests.
If
you
don't
do
any
tuning,
how
many
sorry?
How
large
is
your
is
your
our
table?
A
So
there's
there's
a
variety
of
different
knobs
that
and
limitations
that
you
have
in
addition
to
getting
the
performance
hit
every
time
you
have
to
recross
into
the
in
the
user,
space
and
kernel
boundary
in
order
to
send
those
messages
off,
and
so
this
will.
This
will
allow
us
at
the
end
of
the
day.
A
There
is
also
work
being
done
towards
towards
a
survey.
There
was
an
interesting
use
use
case.
That
was
brought
up
that,
and
so
people
are
familiar
with
the
first
two
use
cases,
which
is
you
load,
something
up
with
kernel
with
kernel
mode.
You
can
also
load
something
in
direct
mode,
which
is
you
do
the
full
Colonel
bypass
and
write
directly
to
the
device.
A
There's
a
third
use
case
that
popped
up
and
we'll
make
sure
this
gets
written
in
to
some
of
the
some
of
the
use
cases,
which
is
what,
if
you
have
a
device.
What,
if
you
have
a
system
and
let's
say
a
pod
or
something
else
that
needs
to
connect
in
to
through
a
specific
top-of-rack
port
in
order
to
reach
a
certain
network,
but
that
compute
is
not
on
the
same
device
or
is
not
on
the
same
node
as
your
as
the
system.
A
That
is
connected
up
to
the
to
the
s
that
s
our
OE
NIC
card,
and
so
there's
a
so
there's
a
example
that
was
put
forward.
That
showed
how
you
can
hook
up
a
remote
node,
that
this
could
be
a
worker
node
and
how
we
can
then
use
an
assembly
wire
in
a
remote,
asura
V
device
into
into
that
using
kernel-mode
forth
for
the
moment
and
showing
off
that
that
connectivity,
even
though
these
re
s
ROV
devices
on
another
system.
A
So
of
course
this
doesn't
this
doesn't
mean
requirements
in
terms
of
performance,
for
if
you
have
those
strong
performance
requirements.
But
if
your
requirement
is
not
a
performance
requirement,
but
is
a
I
need
connectivity
to
something
that
is
only
available
behind
the
top
of
X,
which
it
falls
very
nicely
in
that
environment?
A
The
last
part
is
there
there
is
work
going
into
the
new
SDK
for
getting
more
expressive,
open
policy,
agent
policies
so
before
we
were
only
taking.
In
the
token
of
the
last
thing
that,
if
that
you
connected
to
we're
now
passing
in
the
full
path
and
and
there's
a
there's,
gonna
be
examples
soon
as
to
to
show
off
how
that
works,
and
so
you
can
that'll
allow
you
to
to
cryptographically
check
the
entire
path
of
your
system
of
your
connection.
A
Those
in
those
scenarios-
and
so
this
also,
this
also
will
help,
because
there's
the
there's
a
set
of
discussions
going
on
in
the
spiffy
community,
the
specific
community
is
working
on
something
called
transitive
identity.
Transitive
identity
actually
have
a
full
working
group
on
this.
So
if
you're
interested
in
transitive
identity
go
hit,
go
hit
up
the
spiffy
spiffy
community
on
how
to
join
that.
What
transitive
identity
basically
is
is
like
how
do
you?
A
A
A
D
A
If
you
are
able
to
find
me
or
if
you
can't
find
me
ping
me
up
on
the
NSM
channel
on
the
cnc
of
slack
and
we'll
see
about
organizing
some
time,
for
you
to
talk,
sounds
great
and
yeah
then,
and
so
we
also
had
the
VL
three
stuff.
That's
going
on
so
definitely
I
had
make.
I
should
already
be
I'm
sure
you
have
a
message
on
that,
but
yeah
hit
me
up
on
on
the
slack
as
well.
A
Anyone
who's
interested
on
the
VL
three
stuff
and
I'll,
or
the
ICMP
responder
stuff
and
I'll,
see
about
getting
you
all
sneak
peeks
on.
What's
going
on
with
that
and
we'll
make
sure
that
we
go
over
the
VL
three
stuff
in
greater
detail
in
this
in
this
channel,
so
that
we
can
get
more
visibility
on
on
what's
going
on
in
that
space
with
that
I
I,
don't
think
we
have
anything
else,
that's
the
surgeon
to
discuss,
and
so
thank
you
all
for
attending
and
you
all
have
a
great
day
see
you
all.