►
From YouTube: Policies and Telemetry WG - 2020-12-02
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
B
Yeah,
I'm
not
sure
oh
yeah,
okay,
the
snapshot
is
still
here.
Maybe
you
could
yeah.
You
could
present.
A
B
A
C
Resonates
sorry,
I
just
actually
sat
down
and
tuned
in
and
heard
my
name
so
you're.
I'm
sorry
that
so
you're
asking
about
client
versus
source
versus
destination
reporting.
A
C
A
Okay,
I
don't
think
newper
has
joined
john.
Is
there
more
that
you
want
to
say
about.
D
E
D
Don't
I
don't
have
that
much
to
say
I
just
noticed
that
we
were
talking
about
a
lot
and
that
we
could
probably
use
some
discussion,
but
I
certainly
cannot
leave
that
discussion.
A
Okay,
yeah,
I
haven't,
I
haven't,
been
intimately
involved
in
that
either,
so
I
don't,
I
don't
feel
comfortable
leaving
it.
I'm
certainly
not
up
to
date
on
the
multiple
design,
docs.
A
Does
anyone
have
anything
else
they
want
to
discuss
before
we
just
review
the
the
work
items
for
one
nine
that
will
be
presenting
to
toc
on
friday?
There's
not
much
agenda
here.
I
think,
because
last
week
was
short
with
the
holiday.
A
Okay,
well,
I
guess
I'll
just
quickly
open
this
up
just
so,
we
can
all
take
a
real,
quick
look.
I
haven't
transferred
any
of
this
over
to.
A
The
spreadsheet,
but
this
is
sort
of
what
we
I
tried
to
take
the
the
working
notes
from
last
meeting
and
consolidate
them.
So
if
you
see
your
name
next
to
something-
and
it
doesn't
make
sense-
please
let
me
know,
but
we
are
going
to
try
and
really
work
on
request
classification.
There
is
a
list
in
in
this
github
issue
and
we
want
to
finish
the
work
to
move
that
feature
along
to
beta.
A
There's
a
lot
of
ongoing
discussion
right
now
about
a
telemetry
api.
We
had
thought
focusing
on
tracing,
might
make
it
simpler.
It's
not
clear
that
it
has
so
this
might
change
to
be
something
other
than
tracing
as
a
start
for
one
nine,
but
that
is
still
a
p0.
A
I
want
to
continue
on
the
work
that
peter
had
been
doing
for
out
of
mesh
metadata
workloads,
so
that's
also
a
p0,
and
then
we
had
a
p0
that
carried
over
from
one
eight,
which
was
to
document
how
to
deal
with
metrics
expiry
for
prometheus.
I
saw
someone
on
the
github
issues
have
asked
if
they
could
take
on
that
work.
So
peter
I
don't
know
if
you've
engaged
with
them,
but
maybe
part
of
this
work
could
be
engaging
with
them
about
how
to
how
to
properly
build
that
in.
F
Oh,
I
haven't
noticed
like
someone
comment
on
it.
I
will
take
a
look
at
that
issue.
Okay,
yeah.
I
I
will.
I
can
try
and
send.
A
I
can
look
forward
to
after
this
meeting,
but
anyways,
that's
something
you
might
want
to
pay
attention
to,
and
then
the
the
other
big
item,
I
think
well,
if
everything's
at
p0,
is
to
work
on
what
it
means
for
how
we're
going
to
move
the
wasm
extension
stuff
into
into
beta
feature
status.
So
we
we
need
a
development
plan
there
with
some
sort
of
loose
schedule.
A
So
the
goal
was
to
develop
that
in
this
release
cycle
and
then
I
think
niraj.
This
is
the
one
near
and
dear
to
your
heart,
about
upgrades
and
support
documentation
of
how
you
get
around
mixer
adapters,
and
this
ties
in
I
think
a
little
bit
to
some
of
that
rate.
Limiting
discussion.
That
john
was
raising
yeah.
A
We
need
to.
We
need
to
get
better
at
that.
There's
a
question
here
I
mean
it
looked
like
there
had
been
and
ed.
I
know
you
had
commented
on
the
issue
about.
You
know
warnings
about
envoy
filter.
A
A
D
A
There's
a
lot
of
multi-cluster
work
that
has
sort
of
come
up,
including
the
request
that
we
design
a
dashboard
or
design
how
the
dashboards
will
work
with
multi-cluster
to
better
allow
or
you
know,
to
better
show
multi-cluster
support
as
first
class,
and
so
that
is
also
a
p0
that
I
I
will
be
looking
at
with
new
per.
A
B
Yeah,
you
can
add
my
name
here
and
maybe
add
some
descriptions
about
this
with
the
dashboard.
A
And
then
I
think
we
you
know
in
the
couple
weeks
ago
there
was
the
proposed
vrc
that
daniel
had
had
mitch
had
brought
up
and
written
up,
and
so
I
think
there
is
some
work
between
squat
and
daniel
to
to
really
help
shape
that
into
a
full-fledged
proposal.
For
what
extension
distribution
looks
like
and
how
that
will
function.
A
This
I
haven't.
I
think
we
need
to
do
more
work
on,
and
I
know
that
I,
my
name
is
next
to
this,
but
anyone
else
is
interested
in
better
transport
security
and
how
how
that
impacts.
Telemetry
be
happy
to
have
volunteers,
to
help.
Take
a
look
at
that
and
make
sure
that
we
are.
Our
working
group
is
involved
in
the
review,
at
least
of
the
existing
designs
and
work,
and
then
carolyn
is
going
to
continue
her
work
on
dashboards.
A
A
Well,
that's
all
that
I
had
on
the
agenda
for
today.
So
if
there
are,
unless
there
are
other
things
that
you
know
madara,
I
know
you
joined
a
little
late.
Is
there
something
that
you
had
on
your
mind
that
you
thought
we
should
talk
about
or.
E
So
I
I
just
wanted
to
inform
and
there
like,
there
hasn't
yet
been
concrete
steps
on
it
yet,
but
but
very
soon
there
will
be
so
we
we
want
to
re-energize
the
the
web
assembly
kind
of
part,
the
workgroup
it
has
been
whatever
falling
behind
for
a
couple
of
reasons.
One
of
the
things
is
is
already
mentioned
here
right:
the
the
work
item
that
that
had
danielle
and
quad's
name
on
it.
E
So
there
are
several
people,
including
red
hat,
that
have
reached
out
and
said
that
they
would
really
like
to
get
involved
and
help
move
the
story
along
faster.
E
So
there
is
a
very
high
chance
that
we
will
either
form
like
a
like
a
temporary
work
group.
That's
attached
to
up
to
our
current
work
group
or
and
then
start
tracking
that
work,
and
we
would
bring
this
to
the
toc.
A
And
are
you
going
with
a
full
charter
or
is
this
sort
of
like.
E
No
no
this
this
is.
This
is
going
to
be
a
like
a
like
a
time
bound
thing,
so
it
it
it
won't
be.
It
won't
be
a
full
charge.
It
will
be
like
for
the
next
three
to
six
months.
This
is
what
we
are
going
to
concentrate
on,
and
and
and
that's
it.
So
it's
like
a
you.
You
can
call
it
like
a
special
interest
group
inside
our
work
group
or
attached
to
our
work
group.
E
A
E
We
we
will
we'll
make
sure
that
it
is
like
the
notes
and
everything
is
recorded
and
everything
is
publicized
through
extensions
and
telemetry
group,
and
also
it
should
be
available
on
the
in
the
tlc
minutes.
E
A
G
Right,
no,
I
just
flashed
it
out
a
bit.
I
replied
to
some
questions
and
I
added
because
it's
come
up
repeatedly.
I
added
a
section
on
design
ideas
which
take
it
with
a
grain
of
salt,
because
it's
not.
This
is
not
how
it's
supposed
to
be
implemented.
It's
just
to
give
you
an
idea
what
it
could
look
like.
This
is
the
poc
that
we
have
in
in
maestro
right
now,
so
it
I
added
a
diagram.
Basically
that
shows
what
the
infrastructure
looks
like
in
in
maestro,
so
we
added
a
new
component.
G
A
Okay,
there's
nothing
else
on
the
agenda,
so
I
don't
want
to
just
fill
people's
time.
So
unless
someone
has
something
they
they
urgently
think
we
should
talk
about.
Maybe
we
should
just
adjourn
going
once
twice:
okay,
well,
happy
december
everyone
and
talk
to
you
in
a
couple
weeks,
if
not
sooner.