►
From YouTube: Ambient Mesh WG meeting 2023 06 21
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).
A
C
D
I'm
not
currently
I
wrote
a
talk
a
while
ago.
I
don't
even
know
if
we
have
consensus
the
beta.
What
needs
to
be
you
know
classical
beta
for
ambient,
but
I
haven't
done
any
work
related
to
the
board.
I
mean
if
you
have
bandwidths,
feel
free
to
jumped
in.
D
B
Okay,
so
I
guess
this
dog
I'm
looking
at
a
list
of
proofers,
this
is
never
approved,
so
maybe
the
first
thing.
The
first
order
of
business
is
just
review.
The
stock
finish
reviewing
the
stock
and
get
it
approved.
D
D
Yeah
and
also
keep
in
mind
everybody,
each
of
us
may
have
different
priority
right.
So
if
you
need
something
in
beta,
the
most
important
thing
is
actually
have
you
know
identified
person
be
willing
to
work
on
that.
That's
the
biggest
thing
we
have
to
look
out
for
right.
F
D
A
Have
we
even
making
progress
towards
consensus
like
have
you
been
I
I,
don't
remember
seeing
the
doc
for
a
while,
so
I
feel
like
it's
just
kind
of
got
forgotten,
maybe
by
by
a
lot
of
folks
I
mean.
Do
you
want
to
just
kind
of
drive
that
forward
and
and
like
maybe
maybe
that's
the
focus
of
next
week's
meeting.
D
Yeah
I
think
we
made
some
progress
so
last
time
when
we
meet
about
the
document
we
mentioned,
the
biggest
thing
before
the
dark
can
be
approved
is
to
API
stability
right.
So
I
think
there
are
some
progress
made
towards
that
API
stability
portion,
particularly
there
are
some
changes
around
like
service
entry.
You
know
workload
entry,
you
know
that
API
will
continue
to
use
except
it
was
optional
address.
I
think
there
are
also
some
discussion
on
how
authorization
policy
is
supposed
to
be
bind
to
a
waypoint.
A
So
Lynn
I
think
I
think
what
I'm
asking
is
who
owns
this
document
or
is
that?
Is
it
you
effectively
like?
Yes?
Yes,
we
understand,
there
are
open
questions,
but
somebody
needs
to
drive
them
to
a
resolution.
I
guess
is
that
you
or
somebody
else
owning
this.
D
Yeah
so
I
started
a
document,
so
I
consider
to
be
honor,
but
if
there's
somebody
else
who
is
willing
to
be
co-owner,
you
know
happy
to
have
the
help
too
I.
A
Mean
I
think
that's
fine.
As
long
as
we
have
somebody
you
know
that
owns
it
so
I
I,
guess
I
guess
the
action
for
you
is
to
just
kind
of
drive
that
right,
like
you,
know,
throw
it
on
them.
If
there's
unresolved
stuff,
let's
throw
it
on.
You
know
next
week's
meeting:
let's
let's
get
the
appropriate
people,
you
know
there
and
and
figure
it
out.
B
Then,
if
you
need
help,
I
am
more
than
willing
to
help.
You
drive
this.
If
we're
just
talking
about
going
through
and
make
sure
all
the
all
the
items
are
closed.
D
Yeah
so
I'm
thinking
about
how
we
tackle
this
right
I,
don't
think
it
would
be
easy
to
reach
consensus
on
what
needs
to
be
happened
to
declare
MBA
in
beta
and
I.
Don't
want
that
discussion
blocking
everybody
else
implementing
code
in
ambient
to
driving
towards
beta,
so
I
think
we
should
do
try
to
get
consensus
in
parallel.
We
should
probably
have
the
board
accurately
reflecting
these
work
items,
so
maybe,
for
instance,
you
could
potentially
help
with
the
board.
D
If
that's
okay,
to
make
sure
the
board
captures
all
the
different
work
items
and
then
we
can
I
I'll
I'll.
Try
to
you
know,
tag
different
people
and
see
if
we
can
join
consensus,
what
needs
to
be
in
beta
and
then
in
parallel.
We
can
get
the
board
updated
okay.
So
what?
What
do
you
think.
G
I
mean:
is
it
safe
to
I'm
wondering
if
we
can
make
this
easier?
Is
it
safe
to
say
that
if
you
know
someone
is
willing
to
have
a
company
of
a
vendor
somebody's
willing
to
put
person
hours
behind
one
of
these
tasks
that
it's
going
to
make
it
to
Beta
like?
Is
that
a
pretty
pretty
safe
statement.
D
Yes,
I
think
so
the
biggest
thing
we
can
decide
is
the
racial
is
like
any
open
source
projects
right
yeah.
If
there
are
resource
backing
for
it
within
the
time
window,
I
think
the
the
confidence
of
having
it
part
of
the
beta
will
be
much
higher.
G
Right
I
could
completely
agree
so
I'm
I'm
wondering.
Can
we
circuit
this,
like
we've
got
the
things
that
have
names
on
them
and
they
did
that
commitment
on
them.
We
can
put
that
as
part
of
a
beta
candidate,
and
then
you
see
what's
left
if
there
are
things
that
are
left,
that
we
as
a
community
are
not
wouldn't
be
comfortable
shipping,
a
beta
without
then
I-
think
that's
part
of
the
conversation.
That's
where
conversation
happens
right
where
the
people
who
are
making
quote
unquote
funding
decisions
can
see.
G
Oh,
if
I
put
somebody
on
this,
then
this
is
what's
going
to
get
left
out.
Maybe
I
take
half
of
a
per
you
know.
People
can
can
make
decisions
about
who
works
on
what
we
can
also
look
for
other
community
contributions
from
folks
who
might
not
be
istio
istio
vendors
to
do
some
of
this
work,
but
I
think
that
you
know
just
have
we've
got
names.
We've
got
a
sense
of
what's
being
worked
on.
G
Maybe
we
start
by
just
putting
that
in
the
data
and
see
what
we're
going
to
be
missing
because
as
it
stands
right
now,
it's
it's
not
easy
to
see
what
is
part
of
what
we're
working
toward
as
far
as
a
beta,
what
might
slip
and
where
the
resources
might
be
needed.
Does
that
make
sense.
D
Yes,
you're
right,
in
fact,
that's
what
I've
been
asking
folks
to
do
when
I
first
present
this
so
far,
I
have
to
say
kiss,
you
might
be
the
only
person
added
your
name,
so
we
definitely
need
more
people
to
kind
of
sign
up
for
different
items
on
the
stock
right.
G
Yeah,
maybe
I
don't
know
for
the
folks
feel
like
a
like.
The
doc
is
not
the
right
right
place
for
this
I'm.
Seeing
some
some
comments
in
the
chat
about
you
know,
did
she
putting
this
in
a
in
the
project?
G
What
what's
going
to
be
best
for
everybody
to
to
be
able
to
consistently
kind
of
track?
This
stuff.
B
Confident
so
here's
my
two
cents,
the
content
of
the
board,
especially
where
we
draw
the
line
in
terms
of
what's
in
scope
for
beta,
will
need
to
come
from
this
drive
ambient
to
Beta
doc
because
as
far
as
I
know,
this
is
the
dog,
the
only
dog
that
we
have
right
now.
That
says
these
are
the
items
that's
needed
for
beta
the
p0s
and
p1s
and
P2,
and
so
on.
So
that
said,
we
don't
need
to
have
the
stock
block
the
work
that
we
have
in
board.
B
There
are
items
on
here
that
we
I'm
just
gonna,
go
out
there
and
say
that
all
the
p0s
identified
in
stock
are
in
scope
for
beta
and
we
can
have
people
working
on
those
and
see
who
are
the
resources
of
working
on
those
and
if
we
don't
have
a
resource
working
enemies
items.
Let's
ask
a
community
for
for
volunteers.
B
So
I
can
take
a
step
at
organizing
a
board
and
make
sure
that
we
are
tracking
these
items
in
the
board.
Looking
for
assignments,
then,
can
you
lead
on
closing
on
the
stock,
essentially
scope
for
beta.
D
Yeah
that
sounds
good,
so
do
I
have
the
right
approval
on
the
doc.
So
right
now,
I
listed
a
Toc
members,
but
we
could
potentially
adjust
the
approval
as
if
needed.
B
Let
me
ask
another
way:
besides
the
five
here:
are
we
missing
anyone.
G
Another
question
I
have
to
we've
got
a
couple
of
those
of
those
spa
Coopers
there
is
there
anything
that
is
in
your
mind,
that
is
holding
this
dock
up
from
being
approved.
G
B
Okay,
so
then
it's
decided
then
we'll
lead
to
closing
on
this
comment
and
I
will
work
on
organizing
the
board.
I
will
reach
out
to
so
Keys
I'll,
probably
even
shout
out
to
you
and
then
as
well
as
Nathan
and
John,
about
the
content
of
a
board
right
now
and
I'll
map
these
to
the
items
that
are
called
out
here.
B
G
And
I
just
I
just
thought
of
this
because
it
pops
up
in
slack
a
couple
of
days
ago,
seeing
a
couple
of
a
little
bit
of
community
feedback
from
people
looking
for
pad
easier
releases,
and
they
don't
feel
that
they're
missing
ambient
announcements
here
and
there
do.
We
feel,
like
we've
done
a
good
enough
job
at
kind
of
getting
the
word
out
about
Ambience
and
having
appropriate
dots
on
the
seoio
page
right
now.
There
are
two
docs
on
a
coio
that
I
can
tell.
D
Oh
yeah,
that's
a
great
question:
I
think
we
need
more
work
and
honestly
I
would
have
prefer
our
home
page.
Maybe
we
have
a
buying,
like
a
banner
say:
hey
ambient
is
in
1.18
as
Alpha,
something
like
that
right,
because
that's
the
most
of
people
confuse
it.
People
are
confused
about
whether
ambient
is
in
1.18
and
people
are
confused
the
status
of
the
ambient.
So
we
can
make
it
as
a
banner
on
the
right.
Everybody
goes
there.
They
would
be
able
to
see
it.
D
F
Yeah
I
was
just
going
to
add
to
that
I.
Don't
know
if
Mitch
is
on
the
call,
but
I
know
Mitch
and
I
are
working
on
a
survey
and
I
think
Mitch
is
trying
to
track
down
what
channels
he
can
utilize
from
the
you
know
the
the
cloud
native
Foundation
to
get
that
out
there
so
I.
B
Well,
unless
I'm
incorrect
I
think
we
can
easily
fix
that
by
just
having
ambient
to
these
announcements.
I
G
That
was
gonna,
be
my
question.
Like
do
we
feel,
like
the
people
I
see
at
least
maybe
a
mismatch
potentially
in
the
people
who
are
experts
on
ambient
and
the
people
who
are
writing
about
ambient?
G
Just
because
those
you
know
there's
not
always
that
time
to
do
that,
which
is
certainly
understandable.
Do
we
feel
like
we
need
to
a
couple
of
ways
you
can
we
can
approach
that
one
is?
We
can
make
more
people
Comfort,
confident
enough
on
ambient
to
write
about
it,
who
aren't
necessarily
the
ones
Making
Mr,
PR's
or
those
you
know
us,
those
of
us
making,
PRS
and
accurately
working
on
it,
got
expertise
dedicate
some
time
to
to
writing
it.
D
D
Then
you
know,
then,
the
initial
time
I
put
in
right
the
feedback
and
everything
it's
just.
We
have
a
very
high
standards
which
might
deter
people
from
contributions.
So
that's
something
it
was
keep
in
mind
too.
B
D
A
Lynn
regarding
the
standards
for
docs
have
those
changed
since
that
working
group
was
dissolved.
A
D
B
So
niranjan
has
an
up
for
a
while.
J
Yeah
thanks
this
may
have
already
sort
of
been
answered
by
the
discussion,
but
is
there
some
user-facing
Doc
currently
about
which
custom
resources
are
supported
by
ambient,
or
is
that
also
like
one
of
the
areas
like
we
were
looking
to
add
at
some
point.
D
K
Earth
one
thing
I
think
I,
recall
and
John
is
probably
the
creator
of
it,
but
I
do
think.
There
was
at
least
an
issue
created
where
we
talked
about
what
ambient
docs
were
going
to
be
needed.
So
we
should
have
at
least
sort
of
a
documentation,
roadmap.
D
K
Yeah
and-
and
you
know,
to
go
back
to
the
doc
work
group
I-
don't
know
that
the
standards
of
become
more
difficult.
Actually,
they
probably
have
become
less
but
I.
Think
the
the
one
of
the
key
issues
is
probably
the
number
of
reviewers
has
become
much
less
so
the
unfortunate
thing
you
know
it
just
means:
there's
there's
fewer
people
to
to
review
the
PRS
to
try
to
get
the
feedback,
maybe
in
as
timely
a
manner
as
as
we
used
to.
K
Well,
the
TOC
basically
had
had
talked
about
this
issue
and
at
the
point
in
time
the
TOC
was
basically
becoming
reviewers
and
or
they
had
created
a
an
additional
group
of
reviewers
to
try
to
help
with
that.
K
But
I
think,
that's,
probably
you
know
gone
away
as
well,
so
I
mean
Toc
could
probably
try
to
re.
You
know
re-review
that
that's
probably
a
good
thing
to
do.
A
Yeah
yeah,
it's
probably
worth
just
revisiting
the
topic
in
general
I,
don't
know
that
anything
will
come
of
it,
but
yeah.
A
Let's,
unless
you
know
all
all
of
these,
companies
are
willing
to
volunteer
resources.
C
K
K
D
Yeah
sure,
so,
basically
what
Doc
review
requirements
is
higher
than
code,
because
doc
previewer
right
now
needs
one
maintainer
from
the
code
networking,
for
example,
on
top
of
that,
it
also
needs
an
English
reviewer.
I
I
Requiring
that
requirement,
maybe
some
person
that
is
in
the
docs
maintainers
group,
is
saying
that
they
want
someone
to
look
at
it,
but
there's
no,
that's
not
a
real
requirement,
but
I
think
it's
good
that
that
is
happening
because
there's
there
is
two
bonuses:
people
that
know
how
to
write
Docs
and
then
there's
people
that
know
what
the
doctors
are
saying
is
correct
and
without
those
two,
it's
worse
than
not
having
docs
right
right.
I
It's
different
in
code
like
actually
it's
not
that
different
in
in
code
in
Google
we
have
readability
reviewers,
who
are
experts
at
the
language,
and
then
we
also
have
Percy
Express
the
code
base.
Now
we
obviously
don't
do
that
in
East
yo,
which
is
perfectly
fine,
but
it's
not
a
crazy
topic.
I
think
to
have
two
different
sets
of
reviewers,
ruining
different
things,
because
we
don't
have
networking
docs
writers
and
Telemetry
docs
writers
and
all
these
different
groups.
If
we
did,
that
would
be
amazing.
I
G
I
mean
the
unfortunate
reality
is
that
it
just
it
takes
a
long
time
for
new
people
to
become
maintainers
and
reviewers
and
to
learn
the
code
base.
Like
I
just
hear
it's
a
complicated,
it's
a
complicated
piece
of
software,
and
so
we
want
to
make
sure
that
we
are
being
safe
for
that
documentation,
but
it
doesn't
solve
a
problem
when
people
leave
or
or
no
longer
work
on
istio.
G
It
takes
time
to
replenish
those
people.
I
think
we're
just
in
that
in
this
situation.
Right
now,
I've.
C
G
People
who
are
trying
like
I'm,
you
know
it,
takes
I,
think
30
PR
to
become
a
maintainer
which
isn't
you
know,
I
think
it's
fair.
It's
fairly
reasonable.
All
things
consider
if
it's
just
complexity
but
I
mean
it
just
takes
time.
Sorry,
Nathan,
I
cut
you
off.
A
Oh
no
I
I
was
just
going
to
say
with
respect
to
like
docs,
though
I'm
not
I'm,
not
sure,
there's
been
a
real,
concerted
effort
in
the
program
to
to
really
replace
kind
of
replenish
the
you
know
the
the
lack
of
the
working
group
that
was
dissolved,
so
I
I
feel
like
that.
That's
why
I
was
kind
of
like
hanging.
Maybe
it's
a
POC
topic.
A
Maybe
we
should
revisit
like
seeing
if
we
can
get
folks
to
dedicate
some
resources
to
actually
you
know
making
this
a
little
bit
of
a
smoother
process,
but
you
know,
obviously
it's
you
know.
Maybe
that's
not
in
the
cards.
K
Hey
no
I
agree,
but
we
should
we
should
at
least
from
a
Toc
standpoint.
We
should
probably
talk
about
it.
We
can
add
that
to
the
next
month's
agenda,.
B
So
my
take
it
on
is
this
right?
I
look
at
dogs
at
the
same
level
of
importance
as
release
without
the
RMS.
We
don't
have
a
product.
We
don't
have
a
product
release
without
dogs.
We
also
don't
have
a
problem
with
release.
So
the
way
we
solve
the
RM
problems,
we
have
rotations
and
we
have
each
of
the
vendors
essentially
nominating
people
for
RMS,
and
we
are
going
to
need
a
similar
body
for
dogs,
given
that
this
is
the
the
first
major
update
to
a
steel
docs.
In
a
long
time.
B
So
Eric
Lin
can
one
of
you
put
this
on
a
TLC
agenda.
K
E
Hey
I
just
mentioned
this
on
the
chat
but
I'm
a
new
member
and
I
would
be
happy
to
find
ways
to
contribute
either
with
docs
or
code.
Is
there
a
ramp
up,
roadmap
or
mentoring
procedure
that
I
can
work
with
to
kind
of
become
productive.
G
C
B
E
Yeah
I'm
a
new
member
I'm
I'm
interested
in
contributing
either
to
docs
or
to
code.
Is
there
a
ramp
up
procedure?
Is
there
I
mean
we've
been
talking
about
contributing
to
dogs
as
well?
But
you
know
either
dogs
or
code
and
How
can
I
work.
Is
that
a
ramp
up
roadmap?
A
Mean
if
you're
willing
to
contribute
docs
I
mean
welcome
on
board.
E
A
Actually
think
writing
Jacks
might
be
a
good
way
to
get
started,
so
we
don't
really
have
an
onboarding
per
se,
but
you
know
if
it
sounds
like
somebody's
got
a
doc
somewhere.
A
Maybe
John
made
it
that
basically
lists
a
bunch
of
things
that
we
should
write
docs
for
so
maybe
we
can
just
give
you
one
of
those
topics
and
have
you
work
with
you
know
one
of
the
Z
tunnel,
slash
istio
Developers
to
to
sketch
that
out,
maybe
as
like
a
kind
of
like
a
first
onboarding
project
that
at
least
kind
of
give
you
get
you
familiar
with
what
you
know,
some
of
the
some
of
the
bits
and
pieces
of
what
we're
building
and
and
whatnot
I
don't
know.
B
So
I
posted
the
link,
the
keys
posted
in
chats
right
in
the
note
doc.
Sanjeev
take
a
look
at
this
one
first
in
terms
of
the
documentation,
reviewers
or
requirements
or
responsibilities,
and
then
in
there
there's
another
link
to
how
to
review
contents
guide.
B
That's
see,
that's
just
that's
working
with
GitHub.
B
D
E
A
Lynn,
would
you
want
to
point
him
at
what
needs
to
be
done
there.
D
E
Oh
okay,
contact
you
on
Slack.
C
D
H
You
have
a
hand
yeah
I
was
thinking,
maybe
if
some
of
those
like
blog
translations
or
like,
like
you
mentioned
Nathan,
mentioned
John,
had
a
list
of
ambient
related
documentation
that
needed
to
be
done,
or
at
least
was
broken
apart.
H
It'd
be
great,
maybe
if
those
are
translated
into
issues
on
GitHub
and
were
labeled
with
good
first
issues,
I
mean
just
I
think
making
it
easier
for
newer
people
to
know
what
to
contribute
to
and
then
just
having
those
be
like
smaller,
broken
down
tasks,
because
I
think
some
of
the
remaining
like
good
first
issues
are
really
broad
like
add
more
test
coverage,
but
it'd
be
great.
If
you
could
point
to
where
to
add
the
test
coverage
or
point
to
what
exact
doc
or
what
exact
blog
to
translate
into
a
doc.
A
So
serialize
John's
brain
into
issues,
yeah.
A
G
Yeah
I
posted
a
link
to
that
that
lists
issue.
G
J
Yeah
I
just
wanted
to
kind
of
follow
up
on
this
kind
of
sort
of
distinction
between
the
like
the
blogs
and
the
documentation,
because,
like
I
also
noticed
this,
when
I
was
reading
about
certain
istio
features
like,
for
example,
Discovery
selectors,
there's
a
Blog
for
it,
but
not
like
a
document
for
it.
So
like
just
just
going
forward
like
what
I
guess
like
what
is
purpose
of
the
blog
and
like
what
is
the
purpose
of
the
doc.
D
Foreign
yeah,
so
I
wish
we
have
a
page
there
that
can
answer
your
question,
so
my
understanding
could
be
biased,
so
block
I
I
think
it's
not
like
a
living
documents.
It's
one
time
more
showcase,
a
particular
feature.
That's
added
just
new
recently
added
to
upcoming
release
or
a
release.
That
was
just
a
release.
Well,
the
talk
is
it's
a
living
thing
where
we
intend
to
keep
it
updated
for
every
single
release.
A
That
that
sounds
about
right
to
me
as
well,
although
yeah
yeah
so
so,
I
think
if
I
remember
right.
C
D
A
Yeah,
right
and-
and
you
know
to
to
Lynn's
earlier
point
about
docs
reviewing
taking
a
long
time,
I
think
blogs
allowed
us
to
kind
of
circumvent
some
of
that
process
as
well
like
I,
think
the
quality
of
the
blogs
may
not
be
quite
as
as
high
as
as
the
as
a
regular
docs
certain
and
certainly
not
maintained,
either.
B
All
right
so
see
Next
Step.
There
are
a
few
things
that
we
can
get
started
so
first
Eric
you
will
bring
to
toc's
attention
about
getting
more
resource
and
contribution
to
the
dogs.
B
Thank
you.
As
far
as
the
the
blog
articles
and
turning
to
a
documentation,
do
we
have
consensus
on
that's
what
we
should
do.
B
L
I
was
gonna,
say
it
seems
like
a
good
jumping
off
point,
since
some
of
this
is
already
like.
You
know
at
least
partially
tested
and
proven
out
that
the
blog
Works,
as
opposed
to
just
starting
from
scratch
and
trying
to
come
up
with
it
off
the
top
of
your
head.
B
Okay,
do
we
have
a
list
of
those
block
articles.
D
D
I
think
we
have
a
lot
of
people
interested
in
helping
with
stocks,
so
I
think
what
Jackie
suggests
it's
good.
We
should
break
into
individual
items,
make
sure
people
are
not
step
on
each
other's
toes
and
then
they
can
feel
comfortable
to
contributing
so
John.
Maybe
I'll
take
a
pass
on
this,
and
then
you
can
chime
in
to
see
if
I
miss
anything
on
the
dark
side.
H
D
B
All
right
anything
else
on
people's
mind.
B
All
right,
if
there's
nothing
else
done,
let's
I
wish
everybody
a
great
day.