►
From YouTube: Network Service Mesh WG Meeting - 2019-02-05
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
A
A
A
C
B
C
C
C
B
C
A
C
C
C
A
D
C
Events
we
have
at
the
end
of
this
month,
Mobile
World
Congress.
So
these
I
was
on
me,
as
you
say,
and
I'm,
just
saying
that
but
I
kept
asking
for
an
architecture
discussion
and
it
would
be
nice
to
have
it
this
week
possible
Sarang
to
the
agenda,
so
I
think
the
agenda.
Let's
start
not
that
long
today
and
I
think
we
should
absolutely
I
think
I
think
we
should
get
to
it.
You
say
that
we
search
face.
I
always
say
always
face,
looks
for
Ian
with
feeling
so
well
so
Mobile
World
Congress
in
Barcelona.
C
A
Attend
that
I
say
I
think
that
that'll
be
something
that
they'll,
probably
it'll,
definitely
be
more
application
service
mesh
oriented,
but
we're
going
to
we're
gonna
try
to
expand
the
scope
a
little
bit
open,
so
we
have
ons
North,
America
and
San
Jose.
He
called
foreplay
versus
closed
that
Culver
paper
notification
is
not
accurate.
That's
that's
a
little
bit
more
aggressive,
so
we
need
to
find
out
what
the
real
dates
are.
A
F
C
C
Good
you
I,
can
you
add
it
I'll
add
it.
You
know
cool
yeah,
so
I
think
some
of
this
stuff
got
mixed
up,
so
I
fixed
them
up,
so
the
service
matched
a
color
paper
closes
on
February
8th.
The
container
world
has
already
had
its
call
for
papers
completed
the
schedule
published
and
we
have
a
network
source
mesh
discussion
or
a
talk
that
it's
being
driven
by
by
prem
from
Lumina.
So.
C
F
F
C
C
Part
of
the
part
of
what
the
requirement
is,
if
you're
an
open-source
project
or
one
of
the
triggers
to
become
a
a
CNC
at
landscape
project,
is
to
have
lots
of
stars,
and
that
number
is
300
so
and
invite
any
people
that
you
think
are
would
be
interested
in
starring
our
project
to
come
in
and
start
so
we
can
jump
in
from
I
think
it's
around
600
or
sorry
it's
about
60
at
the
moment.
So.
A
A
C
G
C
So
just
what
are
those
high-level
things
so
on
this
project
and
not
to
gang
up
on
you
and
Ed
with
Ian
here,
but
I
mean
I,
know
that
there's
several
of
us
that
are
more
than
willing
to
you
know,
help
work
on
this,
but
you
know
I've
been
anecdotally,
pressing
it
on
Google
Chat
trying
to
get
answers
to
questions
in
collecting
data,
but
actually
having
like
a
full
run
down
of
like
these
are
all
the
bits.
This
is.
A
G
Yeah,
that's
kind
of
when
I
mean
we
can
either
do
it
in
like
this
Tuesday
meeting
or
maybe
we
set
up.
You
know
a
specific
meeting
with
like
the
people
that
are
in
that
little
group
that
we
started,
but
you
know
like.
Obviously
you
don't
need
to
create
an
architecture
but
then
present
to
us,
because
then.
G
Yeah
I
mean
I'll,
definitely
reuse
work,
but
I
think
that
would
be
helpful
is
for
us
to
just
get
in
an
environment.
Let's
look
at
the
different
processes
running.
Let's
take
a
look
at
some
of
the
manifests.
Let's
take
a
look
at
like
how
things
are
stitched
together.
Like
you
know,
if
we're
gonna
describe
what
a
network
service
in
point
is
I
need
to,
like
legitimately
know
what.
G
Mutation
I
do
want
to
make
sure
to
keep
the
actual
calls
public
so
that
anybody
who
wants
to
sort
of
come
in
and
participate
can
I
suspect
that
mr.
McCall
is
getting
sufficiently
crowded
that
it
probably
won't
be
the
right
venue,
because
we
do
tend
to
be
running
up
against
the
line.
So
I
guess
the
question
is:
would
you
be
willing
to
go
start
a
doodle
poll
up
for
a
time
that
we
could
put
together
for
folks
to
get
together
on
a
call
and
sort
of
talk,
the
documentation
and
volunteers
through
whatever
it
is?
G
G
G
Would
be
helpful
yeah,
so
if
you
could
go
and
kick
off
like
a
doodle
poll
or
something
and
make
sure
to
CC
the
public
list
and
we'll
just
sort
of
figure
out
a
time
and
start
doing
it,
Sunday
yep
sounds
good
to
me
at
least
yeah,
and
so
the
reason
I
add
some
of
these
was
exactly
for
this
reason.
I
want
people
to
make
suggestions
as
to
what
will
be
helpful
for
them,
so
my
thought
was
we
could
spike.
C
Effective
than
we
actually
should
start
with
those
first
I
mean
one
of
the
things
I
want
to
be
super
clear
about.
Is
you
know
effectively
the
folks
who
are
working
on
putting
into
the
documentation
in
some
sense
of
a
much
better
view
of
the
kinds
of
gaps
in
the
correct
explanations
than
I
do,
or
than
I
suspect,
Frederic
or
Nikolai
does,
because
if
we
magically
knew
what
the
gaps
were,
we
would
just
go
fill
them.
So
you
know
it's
super
super
useful
to
have
another
set
of
eyes.
C
C
G
Do
we
need
to
have
special
privileges
to
access
this
because
I
don't
have
the
add
code
option,
and
this
is
a
bizarre,
the
tail
of
github.
So
basically,
if
what
you're
talking
about
is
I,
went
to
try
and
assign
myself
to
a
bug
and
I
couldn't
effectively,
you
can't
assign
yourself
to
an
issue
for
a
repo
and
fight
I,
can't
assign
you
to
an
issue
for
a
repo
if
you're
not
listed
at
least
as
a
read-only
collaborator,
okay,
and
so
if
anybody
is
like
hey
I
want
to
pick
up
a
shovel.
G
G
Slack
has
a
pricing
model.
That's
a
little
bit
unfriendly
for
open
source
projects
and
I
know
that
that
has
been
somewhat
solved
by
other
projects
in
CN,
CF
and
I
could
see
if
we
could
solve
it
in
a
similar
way.
But
I
have
also
heard
people
mention
spectrum
dot
chat
as
an
alternative
to
slack
so
no
I'm,
totally
open
to
having
the
disgustin.
C
E
C
Issue
I'm
finding
with
IRC
so
far
is
when
you
actually
chat
in
there.
Nobody
answers
one
but
two.
When
people
trapped
in
there,
then
I
haven't
unless
somebody's
recording
the
channel
I
haven't
actually
seen
a
record
of
anything
which
means
that
it's
said
to
people
who
are
present
at
the
time
and
then
it's
lost
for
all
time.
C
So
there
are
a
couple
things
there
and
you
know
I'm,
not
saying
user
by
the
way,
perfect
responses,
so
one
of
them
is
a
lot
of
folks
use,
something
like
IRC
cloud
which
keeps
you
always
on
and
therefore
keeps
and
always
going
record
of
the
channel,
the
other
one
that
I
will
mention
is-
and
this
is
this
is
sort
of
weird.
So
freenode
actively
asks
projects
not
to
build
public
archives
of
their
channels
and
that's.
G
C
Find
mailing-list
enormous,
ly
less
productive
than
chat
house.
Well,
they
are
when
you
don't
use
them
yeah,
so
I
mean
it's
it's
one
of
these
things
were
quite
honestly,
the
communities
fall
in
different
places,
depending
on
the
personalities
of
the
communities
I'm
happy
to
engage
with
folks
on
whatever
medium
they
reach
out
to
engage
so,
for
example,
I've.
G
G
Warning
a
specific
time,
because
we've
got
a
lot
of
folks
working
in
Europe
who
are
on
the
channel
then
so
you
know
lots
of
stuff
goes
on
on
the
channels,
so
I'm
not
quite
sure.
Well,
let
me
let
me
highlight
where,
where
this
tends
to
be
a
problem
right,
just
trying
to
document
the
architecture
which
has
been
agreed
among
people,
presumably
largely
on
IRC,
which
means
we've
got
no
record
of
the
agreement
or
why
they
chose
to
do
it.
G
That
way
or
anything
that
I
think
is,
is
a
fine
example
of
why
we're
in
a
moment
now
the
agreement
was
from
last
week
in
the
meeting
which
you
weren't
present
in
so
that
was
not
actually
am
I
outside
no
I
mean
that
may
have
been.
That
was
in
fact,
last
week
in
the
IOC
meeting
the
agreement,
we
document
the
architecture.
The
agreement
on
the
architecture
goes
like
a
long
while
before
that,
or
else
you
wouldn't
have
written
any
code
by
now.
G
So
my
point
stands
that
there's
some
of
this
stuff,
where
there's
early
discussions
that
are
known
by
the
people
that
have
it
well
in
Poorna-
what's
actually
happening
right
now.
What
we're
trying
to
get
better
about
that
and
I
just
switch
to
the
spec
board
is
where
we're
trying
to
encourage
the
writing
of
specs
so
that
that
are
actually
structured
in
a
way.
That's
intentionally
designed
for
there
could
be
conversation
around
the
middle
sort
of
a
good
example
of
this
right
now
is
the
monitor,
be
basically
the
metrics
piece
of
the
spec.
G
That's
been
going
on,
I
know,
Matthew
and
I
have
had
a
very
active
collaboration
around
that.
So
you
know.
Basically,
we
do
have
speckies
that
are
coming
up.
We
do
have
the
review
of
a
spec
board.
That's
literally
the
next
day,
I'm
up
in
the
meeting
and
the
way
their
structure
typically
is.
There
is
an
issue,
then
the
issue
will
point
to
a
Google
Doc,
because
it's
easier
to
collaborate
there
and
then
once
we
figure
out
what
we're
doing
that
will
roll
into
the
issue,
so
it
could
be
executed
on.
G
Yeah,
that's
the
that's
the
end
because,
like
you're
you're
correct
like
doc,
people
talking
on
IRC,
it's
like
even
finding
it
and
the
Patsy,
because
you
have
an
archive,
it's
a
in
Nance,
so
this
so
that
was
the
idea
toward
striving
towards
these.
Specs
was,
let's
find
a
way
to
get
the
community
to
surround
and
to
start
working
on
things
and
an
area
and
I
don't
want
to
tell
people.
You
can't
talk
on
IRC
or
you
can't
talk
on
slack
or
in.
C
Person
or
a
river,
but
whatever
comes
out
of
that,
should
drive
through
this
particular
through
this
particular
process.
I'm
will
evolve
this
process
to
to
to
be
more
accommodating
to
people
as
well
over
time.
So
right
now
we're
just
getting
started
with
this,
so
be
super
clear
about
is.
This
is
also
not
the
OpenStack
blueprint
process
right.
This
is
a
way
to
try
and
encourage
collaboration.
It's
not
a
mandatory
gate
in
the
system
right,
so
a
lot
of
us
who've
been
very
active
or
trying
to
utilize
it,
because
we
think
it
improves
community
engagement.
C
But
if
you
have
some
piece
of
work,
you
need
to
do
and
the
notion
of
going
and
writing
a
blueprint
who
are
a
spec
or
whatever
it
seems
overwhelming.
You
don't
have
to
write,
but
you
will
probably
lead
to
easier.
G
Contribution
because
the
spec
will
also
often
point
out
details
like
oh
yeah,
if
you
could
change
that.
This
over
here
is
probably
also
a
good
thing
to
change,
and
that
kind
of
thing
so,
okay,
so
we
seem
to
have
muddled
the
agenda
somewhat.
I
think
we
need
to
make
sure
that
we
capture
having
the
discussion
about
slack
and
there
in
the
agenda.
G
C
A
C
A
Okay,
I
hope
you
see
my
screen
shared
browser,
okay,
so
in
sync,
with
whatever
we
already
set
about
the
specs,
so
I
have
initiated
this
an
assembly,
this
process
spec-
and
it's
in
a
you,
know
doc
here.
So
this
is
just
quick
kind
of
announcing
that
this
thing
exists.
Please
go
there
read
it.
We
have
at
least
one
thing
that
we
would
like
the
voting
from
you.
It
would
be
code
naming
so
we
have
two
ideas
already
and
if
someone
has
more
ideas,
please
add
them
here.
A
G
A
A
F
This
is
good.
I
would
love
to
see
more
folks
participating
in
the
conversation
about
the
release
process.
The
other
thing
is
they
sort
of
look
at
the
release
process.
There
are
a
small
number
of
things
that
we
absolutely
have
to
agree
as
a
community
on
right,
a
lot
of
good
stuff
in
the
release
process,
but
there's
a
small
number
of
things.
We
have
to
come
to
an
agreement
about
and
I'm,
not
suggesting.
F
We
necessarily
agree
about
it
this
week,
but
we
probably
should
next
week
or
at
the
latest
the
week
after
yeah
I
mean
I,
think
those
things
fundamentally
come
down
to
what
is
the
intended
release
date?
Are
we
okay
with
you?
What
is
the
intended
throttle?
Branch
pull
date?
Are
we,
okay
with
the
branching
structure
of
just
pulling
a
throttle
branch
or
a
release
branch
from
master
which
most
people
do
expect?
That's,
okay
and
then
the
one
thing
that
I
actually
kind
of
liked
about
this
but
I'd
not
seen
before,
is
the
notion
of
essentially.
I
I
F
F
Kind
of
done
or
come
or
nearly
be
done,
and
then
one
week
later,
this
is
from
230th.
We
we
essentially
pack
the
first
release.
We
start
training
called
the
CI
cd6
texture
testing,
whatever
we
find
appropriate,
and
then
we
probably
find
some
your
small
issues.
I,
don't
know
books
performance,
whatever
you
find
so
two
weeks
later
after
we,
we
are
kind
of
completely
sure
that
we
run
through
all
the
things.
I
mean.
This
is
not
completely
specified.
B
It's
what
this
extending
testing
would
be.
It's
just
like
a
way
to
say.
Okay,
you
have
two
weeks
to
before.
You
declare
that
this
is
something
that
you
consider
stable
and
once
it
gets
to
1.1
or
8.1,
it's
a
minor.
It's
not
the
patch
it
it's
actually
the
paid
version.
So
once
we
get
to
party
version
one-
and
you
say
okay,
so
this
is
stable.
B
B
C
Approach,
you
know,
but
I
do
understand,
I
think
the
point
that
was
made
about
wanting
to
have
an
alpha
or
a
beta
version.
In
some
sense,
the
you
know,
and
sometimes
people
call
them
release
candidates
et
cetera
in
some
sense,
I.
Think
what
you're
suggesting
is
that
we
treat
the
micro
version
of
dot
zero
as.
C
C
There's
a
ton
of
other
good
things
in
this
document
of
interest
for
the
small
number
of
things
and
they're
good
for
setting
direction
and
I
like
them
a
lot,
but
the
the
sort
of
the
community
agreeing
on
sort
of
the
dates
and
the
basic
sort
of
branching
and
versioning
structure.
Those
are
things
we
have
to
all
agree
on.
You
know
the
other
stuff
is.
Is
you.
F
G
F
Know
the
first
release
should
have
us
our
v6
and
so
I'm
going
to
go
work
on
that.
Well,
ok,
sure,
that's
not
actually
a
problem,
but
if
somebody
says
oh,
your
release
date
is
terrible
and
by
the
way
I
want
to
use
you're
a
month
month,
versioning,
okay,
that's
not
something!
We
all
have
to
agree
on
right.
F
Okay,
so
yeah
I,
guess
that
we're
going
to
go
to
this
next
week
again
and
I
hope
that
you
get
some
comments
by
then
yeah.
My
hope
is
that
next
week
that
we
could
sort
of
come
to
agreement
that
okay,
these
will
be
the
dates,
we're
branching
and
versioning
structure,
etc.
So,
particularly,
if
folks
are
you
know
how
differing
views
about
that
like
that?
That
train
is
leaving
the
station?
Probably
next
week,
yeah
and
even
even
just
a
simple
+1
somewhere.
G
C
C
H
F
H
Readme,
which
explains
what
you
need
to
do,
but
it's
very
very,
very
easy.
So
there
is
this
make
file
which
essentially
just
describes
the
name
of
the
example
and
then
all
the
containers
that
you
need
to
build,
which
should
exist.
These
folders
here
under
the
example,
then
all
the
ports
that
are
going
to
be
deployed.
This
effective
eventually
reflects
to
the
naming
of
the
llamó
files
that
are
going
to
be
applied,
and
then
you
cannot
check
comment
and
from
there
on
all
the
targets
or
to
make
file
targets
that
are
data
needed.
H
They
are
generated
automatically
by
just
including
this
target
made
file.
So,
but
the
purpose
here
was
to
really
make
it
easy
without
knowing
much
and
without
going
into
all
the
details
of
the
beauty
infrastructure
to
just
be
able
to
put
all
those
pieces
that
you
need.
I,
particularly
like
this,
because
there's
a
psychological
weight
to
a
long
make
file,
even
if
you
only
and
there
isn't
a
lot
of
lines
visibly
following
I
think
is
gonna
also
be
good
in
this
case.
H
So
whatever
thing
I
do
want
to
comment
on
I'm,
actually
super
happy
that
we've
known
that
the
examples,
repo
and
while
I
don't
think,
there's
any
great
urgency.
I
think
it
would
probably
be
good
to
migrate
some
of
the
existing
examples
in
that
direction.
One
of
the
things
that's
actually
gone
on
in
the
lane.
Repo
is.
C
C
So
one
of
the
things
that
I
want
to
just
start
explicitly
here
that
here
we
don't
build
any
of
the
core
containers
or
anything
D
the
data
plane.
All
these
things
are
essentially
put
of
the
github,
so,
for
example,
here
in
differ
when
you
want
to
build
the
monitoring.
These
are
just
the
same
mo
file
that
you
find
in
the
main
repo,
but
they
just
rely
on
the
fact
that
we
can
download
all
the
containers
of
the
docker
hub.
Oh.
C
One
other
thing
I
didn't
want
to
throw
out
there.
We've
got
a
lot
of
me
big
file
machinery,
and
it's
done
lots
of
useful
things,
but
one
of
the
things
if
there's
someone
who's
interested
in
working
on
it,
that
would
be
super
cool,
is
a
lot
of
the
stuff
were
using
the
make
file
machinery
for
probably.
F
C
I
J
To
tell
when
we're
breaking
the
community
and
as
we
know
not
all
changes
are,
are
structural
in
nature.
So,
if
there's
something
that
semantically
breaks
with
in
a
change,
then
these
examples
act
as
integration
tests
where,
since
they
haven't
been
read
since
they
haven't
been
refactored
or
as
part
of
the
main
core,
we're
more
likely
to
catch
those
type
of
behavior
changes
and
and
be
able
to
report
them
as
as
breaking
changes
or
make
it
to
make
a
decision
to
refactor
back
to
the
non-breaking
version.
G
J
C
F
C
Basically,
what
we
have
at
the
moment
as
a
theory
is
data
planes
connecting
service
endpoints
to
service
clients,
and
that
has
its
uses
and,
as
I've
been
demonstrating
that
coupon
as
an
example
and
that's
fine,
but
the
issue
I
run
into
is
that
it
seems
to
me
that,
firstly,
we've
got
two
problems
with
this
model.
One
is
that
we're
talking
endpoints
and
clients,
as
if
there's
producers
and
consumers
of
network
of
networking,
which
I
don't
think,
is
how
the
world
works.
C
F
That
the
other
one
is
that,
as
things
go,
the
data
planes
that
we've
built
they've
been
using
kubernetes
networking
as
their
connectivity
just
to
get
make
a
point
and
get
things
passed
out.
The
door,
which
is
you
know,
fine
as
far
as
it
goes,
but
practically
speaking,
if
you're
doing.
If
you
look
at
nfe
as
an
example
of
how
fast
networking
works,
then
50%
of
this
is
done
with
SR
iov
interfaces
to
speed.
G
F
C
Nettie's
boxes
are
all
connected,
ruruta
versus
a
switch,
then
that
gives
me
different
use
cases
different
behavior,
the
same
data
plane
won't
necessarily
work
with
both
so
I
think
the
question
I
had
was
and
I
think
the
reason
we've
managed
to
avoid
this
so
far
is
we
have
really
looked
lowest
level
of
this.
What
we're
building
from
okay,
I
think
my
conflict.
A
B
What
a
service
mesh
would
be
for
people
who
want
to
consume
it
as
a
mesh,
but
we
have
a
way
of
building
a
service
mesh,
because
we
haven't
talked
about
the
low
level
building
blocks
that
we
ought
to
be.
Building
with.
You
know,
providing
without
giving
them
privileges
providing
a
container
with
sra
viens
face.
To
take
one
example:
providing
that
container
with
a
menace
which
isn't
really
or
providing
two
containers
with
shared
memories,
that.
B
Lets
us
do
that
the
sort
of
meshing
things
that
people
are
trying
to
grid
huge
containers
for
sure
graphs
has
been
working
since
october
november.
I.
A
I
mean
we
took,
we
talk
at
the
moment
in
terms
of
a
data
plane
that
connects
a
client
to
an
endpoint
he's
setting
aside
the
point
about
they're,
not
necessarily
being
things
like
clients
and
endpoints.
They
might
not
be
a
data
claim
involved
here
either.
You
might
just
want
to
connect
two
containers
together
for
fast
networking
purposes,
on
the
same
host,
which
you
know
around
the
same
host
so
at
and
I
know.
A
You
know
that
I
had
some
questions
around
this
too
right,
like
coz
MF
works
great
if
I'm
on
the
same
post,
and
there
are
gonna,
be
instances
where
I
will
want
to
dictate.
You
know
to
an
application
built
of
micro
services
that
hey
I
want
to
make
sure
that
this
is
how
you
deploy,
but
I
mean
you
know
this
whole
concept
of
us
going
truly
cloud
native
right,
like
not
recreating
openstax
problems
is
I
would
also
like
the
alternative.
If
I
do
have
an
extremely
you
know
fast
and
powerful
fabric
sitting.
A
Above
this,
you
know,
if
I've
my
network
engineers
have
taken
the
time
to
actually
put
this
whole
spine
and
leaf
thing
above
me,
then
I
would
also
like
the
potential
ability
to
intelligently
create
services
where
the
containers
have
their
own
interfaces
and
I
just
use
the
physical
network
northbound.
To
do
all
this
right,
without
necessarily
introducing
a
bottleneck
with
the
network
service,
endpoint
and
I.
Think
Ian
and
I
are
kind
of
both
wrapping
our
heads
around
this
from
like
different
angles,
but
are
trying
to
reach
the
same.
A
How
do
we
treat
an
element
of
networking,
but
we
have
been
conceptualizing
in
my
own
mind,
the
physical
network
around
this
is
that
if
you
what-
and
this
is
one
way
to
conceptualize,
it
is,
if
you
think,
of
the
Tor
port,
the
top
of
racks,
which
port
that,
let's,
let's
put
aside
the
SRA
movie
for
a
second,
let's
just
talk
about
the
physical
neck,
will
come
back
again.
Sorry
because
I
agree,
it's
important.
The
story
is
easier
to
tell
originally
without
so
I
just
have
a
physical
NIC
but
I've
plugged
into
my
containers.
A
A
local
mechanism.
I
would
actually
like
it
to
be
the
case
that
it
gets
from
the
physical
network,
some
kind
of
treatment
right
and
from
the
in
from
my
point
of
view
effectively.
What
that
means
is
that
the
tour
court
that
that
NIC
is
plugged
into
is
in
fact
providing
some
kind
of
a
network
service
that
you
would
like
it
to
provide,
and
so
that's
how
I've
been
sort
of
conceptualizing
this
so
far,
give
me
just
one
second
and
let
me
dig
up
the
sort
of
scribbles
I've
done
well
to
take
you
from
there
right.
A
Then
that
says
that
a
data
plane
is
a
network
service
and
the
data
plane
consumes
a
network
service
as
well.
If
it's
using
the
Tor
to
actually
get
its
connectivity
host
a
house
and
if
that's
the
case,
then
I
don't
necessarily
use
a
data
plane
to
connect
one
network
service
to
another.
So
my
point
is
that
our
lowest
level
of
building
block
before
we
start
talking
about
meshes.
You
know
and
I
use
the
equivalency
here
and
I.
Don't
want
you
to
get
distracted
with
the
way
that
we're
integrating
with
Envoy.
A
But
my
point
is
that
envoy
is
a
form
of
networking
that
builds
on
kubernetes
native
native
networking.
So
there's
a
high
level
and
a
low
level
feels
to
me
here,
like
we've
got
the
high
level,
but
we
haven't
got
the
low
level
here,
where
we've
got
things
that
you
know,
don't
need,
connections
that
reach
across
from
host
to
host.
We
just
need
touch
points
if
you
like,
very
local
things
that
are
on
host
or
hosted
to
network,
but
it
also
feels
like
if
we
take.
A
If
we
look
at
what's
inside
a
network
service,
then
we've
clearly
got
a
control
plane
element
than
a
data
plane
element.
The
control
plane
element
has
a
certain
API
that
we
like
and
be
respect,
and
is
you
know
defined
by
NSM,
but
the
data
plane
element
could
be.
You
know
VPP
in
a
container
or
it
could
be
the
kernel
being
controlled
via
container,
but
it
could
equally
be
a
physical
switch
or
the
physical
router,
with
all
that,
so
I've
been
trying
to
break
off.
A
Sometimes
you
draw
to
sort
of
lay
out
some
of
the
pretty
picture
pieces.
I've
got
some
scribbles
that
I
could
talk
to
if
that
would
be
of
assistance
at
this
point.
If
folks
are
interested,
is
that
something
you
guys
would
be
interested
in
at
this
moment,
yes
said:
I
have
similar
questions
and
I'll
be
interested
in
that?
No,
no,
it's
a
perfectly
valid
set
of
questions
yeah,
you
know,
and
it's
sort
of
part
of
the
reason
ever
written
them
down
yet
is
I
first
need
to
write
down
the
inter
domain
stuff.
A
Let
me
ask
you
a
different
question
before
you
start
down
this.
What
could
I
run
NSM
with
no
data
playing
at
all?
No,
not
currently,
why
not?
Because
something
has
to
be
able
to
handle
making
sure
that
you're
actually
connected
to
the
network
service
that
you
want
to
connect
it
to
and.
A
Have
to
be
able
to
do
that
for
you,
but
if
it's
local
to
me,
if
it's
local
to
my
host
or
you
know
again
the
physical
switch,
then
I
don't
need
a
day
to
plan
for
that.
So
I
think
perhaps
the
semantics
of
the
word
data
playing
are
getting
in
the
way
here.
So
what
I'm?
Looking
at
your
definition
as
you've
written
it,
because
again,
your
code
defines
it
at
the
moment:
hello,
I'm,
sorry
to
interrupt
I
I
having
a
lot
of
trouble
hearing,
but
I
think
this
is
a
conversation.
A
That's
real
relevant
to
me
so
police
yell
at
me.
If
I
are
yell
very
loud
at
me,
if
I
am
stepping
on
or
for
repeating
something
that
was
already
said.
I
think
some
of
this
might
be
clear
if
we
implement
bare
metal,
bare
metal
services
and
infrastructure
on
the
like,
for
example,
on
packet
net
and
put
VPP
on
the
data
plane
and
then
use
use
news
mammoth
to
connect
to
the
pod
and
then
have,
and
then
the
data
playing
of
the
network
service
match
data
plane.
A
Abstraction
would
quote
know
unquote
how
to
tell
of
the
real
of
the
putative.
For
example,
how
to
set
up
the
kinds
of
connections
were
or
looking
for
and
I
think
most
of
that
it's
probably
there
where
we
are,
but
it
to
me
that's
connected
in
some
way
to
the
SR
Iovine
discussion,
the
mpls
discussion
that
that
and
and
I
have
that
I
think
if
we
ask
if
we
implement
our
our
real
Network
that
like,
for
example
in
the
CI
that
that
way,
this
might
fall
out
and
I'm
trouble
hearing
you
Eadie
anyway.
A
Here
we
have
a
challenge
here
in
that
Intel
either.
So
one
of
the
following
things
have
to
be
true.
We
either
have
to
use
a
mechanism
for
talking
to
the
next.
A
But
there's
a
oh
there's,
one
there's
one
remaining
option:
we
could
turn
off
the
second
socket
on
the
server,
but
there's
a
fundamental
mismatch
where
DP
DK
is
very
insisted.
The
world
has
to
be
precisely
in
the
way
it
wants
it.
You
know,
that's
just
not.
How
played
the
cognitive
work?
Yeah?
That's
fine,
so
this
is
good
right,
you're
naming
things
that
need
to
resolve
themselves
in
order
for
us
to
make
things
useful
and
that's
completely
acceptable,
so
where's
that
on
our
tracking,
so
I'm
happy
to
put
that
on
the
tracking.
A
Maybe
maybe
I
can
I
can
go
from
an
end-user
potential
potential
and
users
viewpoint
is
I,
agree
a
bit,
but
yet
is
NSM
as
a
mesh
would
reside
whether
you
decide
to
add,
like
a
MAF
anniversary
sig
that
you
could
have
host
running
Silv
ports
or
you
can
actually
hardwired
the
Knicks
directly
to
a
container.
If
you
want
to
the
notion
of
being
able
to
abstract
out
of
service,
mesh
is
actually
represented
in
physical,
isn't
it
kind
of
independent?
A
You
have
your
pick
and
choose
and
we
might
go
fast
would
be
PP,
but
it
ended
up
being.
Sometimes
you
gotta
have
something
else:
oh
those
those
iterations
of
output.
How
to
represent
the
data
plane
ml
MSM
will
evolve
over
time,
able
to
Astra
being
able
to
attract
them
to
to
understand
that
there
is,
for
example,
locality
services
if
and
NS.
He
is,
for
example,
an
SRO
report
darn
you
have
to
have
the
logic
inside
the
NSM
to
say.
A
Dk
has
got
its
problems
and
it's
not
going
to
work
until
we
change
it.
But
my
point
is:
let's
stop
avoiding
this
conversation
because
VP
DK
is
broken.
Let's
have
it
because
we've
got
it
working
out.
If
it's
deep
UK
for
this,
we
can't
run
it
in
a
container.
Then
we've
got
nothing
quite
honestly.
Well,
the
problem
is,
you
can
run
it
in
the
container,
but
you
can't
run
it
in
your.
A
A
A
So
what
I
was
trying
to
say
is
that
I
think
we've
got
a
lower
level
of
abstraction
that
we
haven't
really
looked
at
yet,
and
yes,
maybe
it's
because
DK
is
not
ready
for
us,
but
I
think
we
need
to
be
making
our
preparations
I.
Think.
Basically,
what
you're
saying
is
no.
The
story
is
for
how
this
is
going
to
work
and
architectural
level,
discover
you're
likely
to
have
unforeseen
issues.
Sort
of
you
know,
I,
don't
know
and
try
and
get
them
resolved,
but
I
think
that's
actually
a
super
good
idea.
A
super
good
point.
A
The
reason
it
has
received
less
of
my
personal
attention
at
this
moment
is
I
know
if
I
were
to
go
off
and
write
some
code
to
try
and
do
this.
I
literally
can't
realistically
test
it
until
either
DP
DK
realizes
that
it's
not
going
to
have
dictatorial
controller
before
we
continue
on
they've
prepared
me
to
neuron
we're
already
a
few
minutes
over.
So
we
should
hunt
the
yeah
I'll.
Let
me
say:
gosh
I
think
suit
suit.
A
A
So,
let's
leverage
the
fact
that
I
work
for
a
giant
SP
and
get
people
to
work
for
us
and
then
second
I,
don't
want
to
take
a
single
bite
of
this
and
be
told
I
can't
have
the
rest
of
the
meal.
So
can
we
save
these
slides
and
all
that
for
like
these
architectural
meetings,
since
we're
already
over
the
hour?
A
Absolutely
all
right,
Ian
and
just
you
know,
get
offline
with
me
and
I
will
look
at
flexing
the
Charter
muscles
and
seeing
if
we
can
get
some
Intel
people
to
solve
some
of
our
challenges
for
us
go
ahead
and
put
me
in
that
as
well,
and
thank
you
closing
it
up
at
the
same
time.
Next
week
see
you
all
there
later
guys
there.