►
From YouTube: 2023-04-06 meeting
Description
Instrumentation: Messaging
A
B
B
C
Yes,
so
I
don't
know
if
other
folks
will
join.
Let's
see.
B
B
C
All
right,
so
what
you're
talking
about
is
this
issue
here
right
about
the
yeah,
so
I
can
tell
that
I
follow
up,
followed
up
here
internally,
with
some
folks
I'm
still
doing
some
more
digging,
but
so
far
I
didn't
find
anything.
That
is
really
this.
This
that
this
attribute
kind
is
really
doing
anything
special.
C
We
also
record
it.
We
also
collected
it
in
our
instrumentations
I
think
it's
basically
the
same
name
or
it
was
destination
kind
and
Source
kind,
with
the
same
values,
q
and
topic,
but
so
far
what
I
learned
is
that,
apart
from
yeah,
basically
what
what
Christian
said
here
apart
from
showing
an
icon
or
offering
to
group
things,
not
not
really
much
but
I
I'm
still
too,
to
find
more
with
some
I
have
some
meetings
with
some
folks
too,
to
ask.
B
C
C
So
we'll
see,
but
it
doesn't
look
very
exciting
at
the
moment,
so
it
might
be
just
something
that
we
can
make
it
optional.
I
think
as
Milo
mentioned
here,
make
it
optional
and
and
keep
the
values
that
they
were
before
Topic
in
queue.
And
then,
if
there
are
more
that
can
be
added.
C
Or
we
don't
even
do
anything,
because
what
I
think
she
mentions
is
that
some
systems
have
way
different
things
like
rabbit.
They
have
exchange
type,
so
I'm,
not
sure
if
she
proposed
or
her
intention
was
to
add
exchange
type
to
the
list
of
values
or
an
entire
different
attribute
called
exchange
type.
B
Yeah
yeah
yeah
yeah,
okay,
good
to
know
in
that
case,.
B
B
C
B
C
This
yeah
I
I,
don't
know
I
I'm
not
opposed
to
any
any
other
other
things
I
think
if
there
is
books
either
like
he
has
apparently
Dwayne
has
value
or
wants
to
have
it
I,
don't
see
a
problem
in
in
rolling
back
and
coming
with
it
again,
leaving
it
with
Topic
in
queue.
I
think
the
also
think
that
was
in
the
that
sparked
it
was
that
we
should
open
up
the
enum,
because
I
think
it
was
like
this.
B
C
Nobody
was
that
allow
additional
values
or
something
that
was
yeah
false
and
then
it
was
proposed
to
open
up
to
true.
So
it
would
basically
put
anything
and
I
think
that
that
when
the
discussion
started
so
yeah.
B
I,
don't
know
if
you
have
court,
but
now
with
some
proposed
changes,
all
the
Norms
will
be
open.
C
Oh
yeah
I
think
I
saw
that
yes
yeah
yeah
and
then
then
basically
that
basically
solves
it.
I
think
yeah
yeah,
because
if
we
can
just
comment
con
with
this
back
and
then
if
there's
people
want
to
say
P2P
or
Pub
sub,
because
I
think
in
some
other
messages
that
makes
more
sense
like
Pulsar
I,
think
yeah
they
can.
They
can
add
that
yeah,
but
I
still
think.
If
it's
something
that
is
well
known,
it
should
be
in
the
semantic
conventions.
Yeah.
B
Anyway,
yeah,
let's
hope
that
Dwayne
provides
feedback,
as
I
said
before.
I
think
that
this
is
not
bad
to
have,
but
given
that
there
are
other
priorities,
I
could
focus
on
those
ones
and
if
Dwayne
or
anybody
else
can
provide
it's
almost
wrong
argument,
then
for
sure
let's
actually
include
this.
Otherwise,
it's
an
optional
thing
and,
as
I
said
before,
we
don't
if
we
don't
prove
any
value
right
now,
we
can
just
wait
for
the
second
version
or
even
though,
as
a
follow-up,
you
know
yeah.
C
Yeah,
it's
not
not
if
we,
even
if
we
add
now
it's
going
to
be
optional
anyway,
because
I
think
some
some
in
some
depending
on
the
library,
you
don't
you
don't
there's
no
way
to
to
know
this
for
like
from
the
producer
or
consumer.
There
is
no
way
to
know
so
it
has
to
be
optional
and
then,
if
it's
optional,
then
it
can
be
added
later
on.
I
guess:
no!
We
don't
no
problem
at
all.
I
think
yeah.
B
C
B
C
Yeah,
so
let's
see
I
will
start
from
bottom
to
top,
so
yeah
I
think
this
is
blood.
Miller,
create
this
issue,
but
I
don't
think
there
was
anything
yes,
I
think
this
is
they
want
to.
They
want
to
discuss
this
this
set
out
during
the
meetings
here.
So
there
was
no
movement
in
this
one.
C
Yes,
this
was
something
that
Johannes
wants
to
do.
I
think
I'll
I
will
offer
if
he
wants
help
on
splitting
things,
because
this
is
a
no-brainer
I
could
I
could
do
it
on
my
spare
time.
B
C
Guess
between
tasks,
so
he
wants
to
we
discussed
and
we
want
to
create
separate
emo
files
for
the
different
systems
instead
of
having
them
in
the
same
generic
or
general
document
yeah.
But
no,
no
movement
on
this
as
well.
C
Clarify
semantic
yeah,
I
think
this
is
also
no
movement.
It
was
something
about
the
spiral
a
long
time
ago.
I
think
he
has
a
the
table
that
we
have
there
with
the
spam
kind.
It's
a
bit
confusing
in
some
weird
cases
yeah.
So
this
is
something
that
also
we
need
to
take
a
look.
B
C
Standpoint,
yeah
I
think
this
is
the
second
to
be
honest,
but
it
was
a
long
time
ago.
I
don't
remember
fully,
but
I
think
there
was
some
like
profound
problems
with
what
we
have
today
in
no
no
way
to
express
what
we
have,
what
we
have
there
without
being
super
confusing
yeah,
but
I
guess.
This
is
also
something
that
we
need
to
discuss.
As
a
group
Amir
was
was
talking
about
it
a
lot
but
I'm,
not
sure.
If
it's.
C
If
it's
going
to
be
coming
to
to
the
meetings
again,
maybe
I.
B
Think
that
it's
yeah
this
week
is
Easter,
so
I
think
that
some
people
are
probably
thinking
this.
C
Week-
yes,
probably
yes,
yes,
this
other
one
here,
I
think
there
there
I
will
link
this
to
something
else,
because
in
the
span,
structure
and
I
find
a
comment
here
in
the
Otep.
That
Johan
is
writing
there
was
this
coming
from
Christian
as
well.
C
Apparently
there
was
some
discussion
in
the
dotnet
repo
about
the
fermentation
for
AWS,
Lambda
sqs,
and
what
what
Christian
is
described
here
is
that
in
a
batch
in
some
cases
this
was
in
the
concept
context
for
for
AWS
for
I,
think
SNS,
even
though
the
system
but
anyway,
so
it
was
like
when
you
send
a
bench,
you
could
use
the
last
message
on
a
badge
to
edit
at
that
at
the
context
from
the
last
message
in
the
batch
as
a
parent.
C
In
the
the
case
there,
that's
it's
a
long
discussion.
This
link
that
he
posted
here-
I
read
it
today,
but
it's
a
basically
for
that
particular
service
in
Amazon,
Amazon
SNS,
you
send
a
batch,
but
it's
just
the
API
is
like
that.
So
it's
always
a
list,
but
is
is
always
just
one
message
so
for
that
case
it
makes
sense,
but
he
discussed
here
that
maybe
we
should
also
put
a
diagram
or
something
that
highlights
this
case
and
I.
C
Don't
don't
really
think
it's
a
good
idea
to
be
in
the
generic
specification
because
I
think
it
in
most
cases,
that
would
be
really
bad
if
you
use,
for
example,
the
last
message
in
a
batch
to
say
it's
a
parent
because
you
could
potentially
just
mix
the
traits
together
and
I,
don't
know,
put
the
processing
processing
of
one
message
as
a
parent
of
another
I
think
that
will
be
really
messed
up.
C
Yeah,
that's
basically
what
they're
discussing
in
in
this
year.
So.
But
the
point
was
that
in
both
of
these
things
it
was
brought
it
up
the
not
or
swap
the
link
or
use
instead
of
adding
a
link
at
a
parent-
and
there
was
already
this
issue
here
so
I
will
I
will
link
them
together
later,
because
I
think
the
discussions
are
are
sparse.
So
now,
there's
discussion
in
here
discussion
in
there
and
I
think
I
probably
should
centralize
them
in
this.
C
C
Okay,
there's
one
from
cause
of,
inter
designed
to
me:
I
I
will
wait
until
we
are
closer
to
to
having
this
Otep
merged
and
then
I
will
take
a
look
at
what
the
impact
for
this
is
probably
have
to
change
the
existing
conventions
that
we
have
today,
but
I,
don't
think
it
would
be
too
much
of
too
much
of
a
problem.
C
B
C
Not
sure
why
it's
still
not
linked
but
I'll,
do
it
yeah
this
one
is
just
a
one
small
one.
Maybe
I
will
take
a
look
if
I
can
take
this
one,
because
I
was
also
looking
at
internally.
We
also
record
this
size,
but
this
also
might
be
that
it
conflicts
or
it
will
come
as
a
solution
with
the
ECS
proposal.
C
Now
that
was
merged,
yeah
I
have
to
look
that
this
is
because
there
is
a
bunch
of
these
attributes
in
HTTP
and
they
differ
from
messaging
like
payload
size
and
compressed
size
and
and
then
there's
math
and
then
yeah
this
just
to
to
make
sure
that
but
yeah.
If
we
have
this
in
HTTP,
then
I
guess
we
can
just
follow
the
same
that
they
have
probably
not.
A
C
C
Yeah,
the
the
ECS
one
I
think
through
the
mirrors,
is
on
it.
I
think
she's.
On
top
of
all
these,
yes
I
thought
the
the
proposed
that
she
did
with
the
HTTP,
so
I
think
that's
just
moving
yeah.
The
Matrix
is
I'll
shoot
purple
or
she
demoed
last
week.
This
one
I'm
not
sure
about
the
metrics.
What
what
we
will
propose,
but
I.
B
B
C
Yeah
I
think
yeah
I,
don't
know
if
I
think.
The
final
idea
is
that
the
metrics,
like
I,
think
the
initial
idea
was
that
before
declaring
the
semantic
conventions
table,
we
needed
Matrix
as
well.
So
like
a
combination
but
I'm,
not
sure
anymore.
If
that's
still
the
case,
if
the,
if
Johannes
had
in
mind
that
to
go
with
the
trace
conventions,
we
also
need
the
metrics
convention
to
be
declared
the
declared
stable
yeah,
but
I,
don't
think
they
have
to
go
together
to
be
stable
right.
The
we
can
just
declare
this.
That's.
B
Right
yeah
I
mean
yeah.
We
can
ask.
Let
me
level
my
impression
is
that
she
only
wanted
to
exercise
them,
Mark
the
messaging
trading
convention,
stable
first
and
at
the
same
time,
experimental
yeah.
So
that's
the
plan
just
for
your
information.
There
was
some
comments
somewhere
by
Josh
sured,
and
he
was
mentioning
that
he's.
B
There's
always
a
reason
that
if
we
publish
something
even
if
it's
Marcus
experimental
people
may
people
may
start
using
that
all
over
the
place
right
which
will
force
us
to
to
Market,
is
to
Market
as
de
facto
stable
or
something
like
that.
Otherwise,
even
though
it's
experimental
will
break
everybody,
so
there's
something
to
keep
in
mind,
so
we
may
even
we.
A
B
C
A
C
Okay,
we'll
see
what
they
say.
Yes,
we
can
then
I
guess
about
the
links
of
the
creation.
Do
you
know
if
anything
moved
on
that
on
those
things.
B
That
suddenly
hasn't
moved
so
Dave
Young,
who
is
in
the
GC
he
was
trying
to
help.
They
go
see
to
find
a
way
to
make
this
happen
without
breaking
many
things.
There's
I,
don't
know
what
to
do
on
this
front.
Basically
also
Joshua,
McDonald
I
was
proposing
that
that
links
our
events
in
indeed
and
basically
attached
to
a
you
know
the
way
we
represent
Links
at
this
moment.
That
would
say
the
same,
but
we
would
be
attaching
event
information
so.
A
B
Could
be
kind
of
hybrid
and
I
think
that
discussion
has
to
be
solved
even
before
this
yeah?
So
the
good
thing
is
that
we
have
time.
The
good
thing
is
that
people
I
mean
the
person.
The
first
person
opposing
Josh
idea
is
Pokemon,
so
I'm
hoping
that,
because
they
are
both
in
the
DC,
this
can
be
solved
relatively
fast.
You
know,
like
the
discussion
takes
place
fast
and
basically,
a
hard
call
is
made
later
on.
Once
that
happens,
we
are
unblocked
from
this
one
right,
yeah
in
the
meantime,
I
will
get.
B
B
Don't
want
to
yeah,
it's
like
you
know,
yeah
anyway.
So,
let's
see
what
happens
in
that
regard.
The
other
thing
is
that
I
was
actually
wondering
whether
it
there
is
any
messaging
system
that
is
extensively
used
from
go.
You
know,
most
of
the
story
can
see
in
Java.
Is
python
JavaScript,
oh
I,
don't
know
I,
guess
I
guess
they
do.
But
how
common
is
that
like
like?
They
would
need
to
add
it
right
away?
Can
they
yeah
I,
don't
know,
but.
B
Story
short,
we
have
to
wait.
One
more
issue:
I
can
actually
I
will
link
the
issue
to
this
original
issue
on.
C
That
one
yep
okay
yeah
it's
it's
not
a,
unfortunately,
not
that
easy
thing
again.
So
yeah.
B
But
once
HTTP
semantic
conventions
is
marked
as
stable,
we
will
we
will
Define
in
this
group
deadlines
and
then
we
will
have
to
start
pushing
people
for
real
yeah.
So
we
make
progress
so
that
time
will
will
come
eventually.
So
we
should
start
thinking
about
what
to
do.
I
think
that
all
of
these
blockers,
all
of
these
hard
rocks,
should
be
removed
by
them.
So.
C
C
So
what
I
I
was
looking
at
actually
on
it
today,
let's
go
over
there.
So
this
first
open
comment
was
what
I
mentioned
so
yeah
he's
already.
He
already
answered
it,
but
yeah.
C
It's
all
about
this,
this
situation
of
using
the
last
message
and
other
things,
but
yeah
we'll
see
what
I
don't
think
nothing
will
come
to
from
fridge
and
fruition
of
this
but
yeah
yeah,
and
then
there
was
some
comments
from
ludibila,
but
I
think
this
was
also
I.
Think
we
discussed
this
in
last
week
and
and
he
she
just
needed
to
write
them
down
and
then
Johannes
will
fix
it.
C
So
I
think
he
is
already
aware
of
those
and
then
what
I,
what
I
did
today
is
I
was
looking
at
the
at
the
document
again
and
I
found
it
actually
I
just
noticed
now,
but
I
found
that
isn't
it
weird
that
the
arrow
here
goes
from
published
to
from
producer
to
Consumer
on
the
link
shouldn't
certainly
be
the
opposite
way.
B
I
think,
logically
speaking,
that
makes
sense,
but
when
you
think
of
how
a
user
will
see
this,
you
can
create
confusion
so
yeah
we
can
probably
we
should
change
it
actually
on
the
initial
Dimension,
where
jmic
dimensions
that
that
actually
links
should
include
event,
information
I
think
he
uses
the
arrows
in
a
different
in
the
opposite
direction.
You
know.
B
A
C
C
To
producer
yeah
and
I
I
I
was
curious
about
it.
I
took
a
look
and
I
think
it's
not
I,
don't
think
you
know
I'm
certain
now
that
it's
not
possible
with
this
mermaid
thing.
They
don't
offer
offer
backwards
backwards,
Arrow
or
link
I
think
they
call
it
link.
I
I
found
this.
C
It's
41
already
asking
for
it,
but
you
can't
do
you
can
do
this
today
like
forward
and
you
can
go
back,
but
you
have
to
to
swap
the
so
in
our
case
you
would
have
to
do.
Where
is
it?
You
would
have
to
put
the
consumer
on
the
left
and
then
that's
what
not?
What
we
wanted.
C
Yeah,
so
that's
what
people
are
complaining
here:
it's
like
okay,
I
can't
do
it,
but
I
don't
want
to
invert
my
diagram,
because
my
diagram
makes
sense
that
way-
and
there
was
this-
this
user
here
that
that
said,
I
do
this
and
it
works
some
some
huge
hack,
yeah
and
then
I
tried
it.
It
actually
works
with
this
code.
Here
it
works.
So
then
it
will
look
like
this
right,
so
I
I
commented
yesterday.
C
B
C
All
of
them,
I
think,
would
have
to
change,
because
all
of
them
are
linked
like
this
and
then
the
other
thing
that
I
was
thinking
is
that
he
has
example
here
this
one
here,
so
the
one
on
top
is
only
for
a
link,
so
it
only
demonstrates
having
a
link,
but
the
one
below
also
represents
that
you
can,
you
can
add,
as
a
parent,
if
you
want,
if
it's
a
single
message
and
then
to
me
this
doesn't.
Doesn't
it's
not
clear
to
me
that
this
is
apparent,
not
sure.
C
B
C
Yeah
and
then
also
I,
think
for
this
specific
case,
I
think
it
makes
more
sense
to
be
top
to
bottom
diagram
because
he
has
like
now
left
to
right
like
this.
He
has
left
to
right
now
and
then
I
think
for
apparently
I
think
if
you
change
it
to
this
top
to
bottom
thing
here,
then
it
becomes
like
this
and
I
think
it
makes
more
sense
because
you
can
see
that
I
don't
know.
C
This
is
how
you
usually
consume
a
trace
and-
and
it's
not
like
one
after
the
other,
but
it's
at
least
below
yeah,
so
I
I
wrote
this
suggest.
Let's
see,
yeah.
C
C
Okay,
yes
and
then
the
other
thing
that
I
saw
that
I
commented
for
the
meeting
was:
has
a
diagram
for
so
for
pool
based
when
the
application
pulls
the
messages.
He
has
one
diagram
this
one
here
that
talks
about
like
it
is
the
liver
part
of
a
bet
of
message
to
Consumer
process
process.
C
Stance
for
a
single
message
can
be
created
but
are
not
covered
by
the
conventions
which
is,
which
is
fine,
so
I
think
it's
missing
a
diagram
like
this
for
the
push
based,
because
here
there
is
nothing
there's
this,
but
this
is
it's
for
patch
I,
think
yeah,
so
I
I
wrote
that
that
I
think
it
makes
sense,
because
it
makes
sense
that
the
both
cases
pull
and
push
at
least
for
me,
I,
I,
I
I,
think
it
makes
sense
that
the
same
like
scenarios
or
use
cases
are
are
laid
out
in
both
cases
and
I.
C
Think
the
majority
of
them
are
the
same,
but
this
one
is
not
there
like.
This
example
is
not
there
and
I
think
there
is
also
a
non-example
there's
no
example
as
well
for
because,
in
the
top
of
the
page
wheel,
there's
a
a
paragraph
saying
that
you
can
add
the
you
can
add
the
context
on
the
message
as
a
parent
on
the
process.
C
Pin
if
you
want
it's
not
not
expecting
this
convention,
because
it's
not
always
possible,
but
if
you
want
again
so
if
I
think
it's
because
it's
saying
that
I
think
we
should
also
have-
or
we
could
have
another
diagram
here
where
there
is
a
you
can
also
add
the
parents,
parent
relationship
to
the
publishing
one
and
Publishing
M2
here
from
from
this
and
also
say
something
the
same
like
better,
not
covered
by
the
conventions.
But
you
can
do
it
if
you
want
yeah
but
I.
C
B
C
That
makes
sense
yeah,
so
I
will
discuss
this
with
with
him
once
he's
back,
but
I
think
after
this
I
think
the
old
type
is
I.
Think
it's
pretty
good
to
go,
at
least
at
least
for
me
for
me,
yeah.
B
A
B
I
also
have
some
small
questions
for
him
and
I
will
go.
You
know
turkey
gun
actually
to
read
on
the
feedback
that
he
got
from
all
of
us.
It's
mostly
minor
storm.
That's
it.
You
know
so
yeah,
but
I
agree
that
the
IIT
in
good
State
I
was
a
little
bit
curious
about
the
process
supports,
but
yeah
I
think
that
the
process
process.
B
C
B
Guess
it
makes
sense
for
now
to
not
include
them
in
the
spec,
given
the
complexity
and
yeah.
C
I
think
the
the
problem
with
the
process
is
that
I
think
we
will
never
be
able
to
fully
put
them
in
the,
but
I
mean
we
can
do
as
he
did
already
here
like
you.
Can
we
can
like
somewhat
casually
say?
C
Okay,
you
can
do
this,
but
it's
not
covered
and
show
how
it
would
look
like
if
you
do
it,
but
I
think
we
can't
like
put
an
aspect
in
a
way
because
it
depending
it
depends
on
a
lot
of
things,
but
it
depends,
for
example,
on
the
library
that
is,
for
example,
like
in
the
messaging
library
that
you
use
because,
for
example,
some
libraries
you
say
like,
for
example,
in
the
pool
based
case
you
just
for
example,
you're
using
I,
don't
know
the
Azure,
I,
know
SDK
or
or
event
about
SDK,
whatever
some
some
library
right
and
then
what
you
do
as
a
developer,
say:
okay,
get
messages
of
this
queue
or
this
topic
or
something
and
then
it
just
gives
you
and
then
from
that
point
on
is,
is
already
over
from
the
library
right.
C
So
so
the
library
can't
can't
create
the
process
pan
manually
automatically
for
you,
because
it's
a
way
out
of
the
libraries
code,
but
someone
libraries
they
they
work
in
in
in
a
way
where
there
is
like
callbacks.
C
C
C
I
think
he's
the
author
of
I
guess
a
couple
of
of
messaging
sdks
in
JavaScript
he
wrote
several
for
several
systems
and
he
was
showing
like
demoing
the
difference
of
each
and
and
how
this
is
problematic,
because
it's
some,
you
can't
really
can't
really
do
anything,
and
then
you
would
have
to
require
the
user
to
do
it,
for
example,
to
create
the
process
fence
so
like,
for
example,
if
we
want
to
be
enforced
that
there
there
will
always
be
process
pens,
then
we
would
need
to
enforce
that
developers
like
the
writing.
C
The
applications
will
always
create
this
and
I
not
really
sure
if
this
is
even
possible
to
do
yeah.
B
Yeah
yeah,
yeah,
yeah
I
think
that,
based
on
some
libraries
I
think
that
with
so
for
some
of
those
ones
we
can.
We
could
create
this
out
of
the
box
for
the
ones
that
you
said
it's
not
possible,
so
the
developer
would
have
to
do
something
I
used
to
I'm
interested
in
this.
What
I
think
that
could
be
like
version
two
or
three,
where
we
say
you
know
like
if
you're,
if
like
there,
are
potential
ways
to
do
this,
and
you
know,
like
general
advice,
you
know,
and
how
you
can
do
this.
B
You
know,
or
even
right,
like
Library
by
Library
case
for
now.
I
can
imagine
that
this
is
enough,
of
course,
for
now,
and
we
can
iterate
later
and
some
of
these
things
that
that
you
know
they
said
that
this
is
not
covered
by
the
spec,
but
this
is
here
probably
we
can
include
that
in
a
parallel
docked,.
B
C
Yeah
yeah
I
think
that
will
make
sense.
Yeah
yeah
have
at
least
something
that
if
they
want
to
do
it,
if
there
is
a
guide,
a
guide
on
how
to
do
it
and
which
attributes
to
record
and
so
on,
I
think
that
makes
sense
yeah,
because
otherwise,
then
it
becomes
like
everybody
does
their
their
own.
B
Way,
yeah
exactly
yeah
exactly
lane,
and
then
you
have
to
basically
merge
those
ones
and
it
will
be
a
breaking
thing
for
people
who
are
trying
to
do
something
yeah.
So
even
if
we
cannot
unify
all
of
those
things
for
now
at
least
you
have
some
of
the
details
set
up,
so
we
don't
cause
a
bigger
problem
later
on.
A
C
Okay,
I
think
I
think
I
think
there
is
so
to
answer
here.
I,
don't
think.
There's
any
blockers,
but
I
will
write.
I
will
write
here
what
we
went
through
today
and
what
I
think
is
still
missing
and
then
Johannes
can
can
pick
it
up.
Yeah.
B
Yeah
one
thing
that
probably
we
can
have
a
comment
in
the
agenda
is
a
comment
from
my
side
that
the
TC
was
talking:
how
to
make
working
groups
work
better
and
faster.
You
know,
and
basically,
like
hotels,
require
at
least
four
apples
and
usually,
of
course,
other
people
are
not
involved
with
these,
so
that
can
become
tricky
so
because
of
that,
we
want
to
have
two
approvals,
like
one
DC
member
per
working
group,
a
lot
of
people
who
are
actually
approvers.
You
know
at
these
two
so
yeah
to.
C
Approvers
per
working
group,
you
mean
yeah.
B
Correct
yeah,
and
in
that
case
I
guess
Johannes
and
lumila
would
come
to
mind,
but
if
you're
anybody
else
is
interested,
we
can
probably
make
you
know
approvers
for
this
group.
You
know,
as
I
said
before
this
is
so
the
step
can
move
on,
but
also
the
PRS
that
we
later
send.
You
know
to
make
to
incorporate
this
into
the
actual.
Spec
are
not
you
know,
sitting
there
forever
yeah.
B
So
that's
something
to
keep
in
mind,
but
once
HTTP
smart
commissions
are
stable,
we
will
have
to
Define
deadlines.
Who
are
the
approvers
if
we
don't
have
them
already
and
so
on?
You
know,
but
yeah,
so
something
to
keep
in
mind
and
then
so.
In
the
meantime,
it's
a
good
thing
that
members
of
the
working
group
give
an
approval,
even
if
they
are
not
actual
approvers,
because
that
shows
that
there
is
agreement
in
the
group.
You
know.
B
C
Yeah
now
I
take
that
that
external
census
I
think
that's
what
we
have
been
doing
already
like
when,
when
we
open
PRS
and
yeah,
all
of
us
approve
I,
think
all
of
us
should
be
in
this.
It
was
something
that
I
think
that
did
really
in
the
beginning.
When
we
started
there,
is
this
inst
working
group
group
or
not
sure
how
that
causing
GitHub
yeah,
but
there's
this
group
in
GitHub
that
we
are
a
part
of
it
all
part
of
it.
C
Yeah,
so
we
are
a
part:
I
mean
Johannes,
Dwayne
I
think
we
are
all
part
of
this
because
we
all
got
added
by
Dead
at
some
point:
yeah
no,
but
we
already
I
think
we
already
do
this
in
for
your
TAP
I
think
we
just
need
yeah
to
now
finalize
all
these
small
things
and
we
all
approved
and
then
I
guess
we
can
go
forward.
Yeah.
B
Yeah
yeah
I
will
be
like
you
know,
messaging,
that's.
B
Well,
I
think
we
already
know
but
yeah
you
can
put
a
reminder
like
just
keep
in
mind.
Like
you
know,
start
thinking
about
approvals
and
the
organization
already
issue
will
happen.
B
Http
stability
is
a
blocker
once
that
happens
we
will
have
to,
and
the
other
thing
is
is
that
we
will
well
I,
don't
know,
I,
think
it's
a
good
idea.
You
know
that
we
had
meetings
on
Mondays,
but
nobody
was
showing
up,
but
once
the
HTTP
part
is
done,
I
could
expect
that
people
can
free
up
Cycles,
so
we
can
meet
more
often
two
times
a
week
is,
is
a
good
one,
I
think.
B
C
B
C
C
Right,
yes,
actually
hard
to
find
yeah
the
time
the
overlaps
with
everybody
but
I
guess
if
there
is
at
least
one
meeting
that
happens
outside
the
time
zone,
then
it
should
be
fine.
I
think
the.
B
Other
thing
is
that
we
get
like,
even
if
not
everybody's
there,
but
at
least
there's
initial
discussion.
You
know,
like
I,
don't
know
like
one
one
that
is
more,
it's
slightly
more,
not
European
friendly
another.
One
of
these
is
slightly
more
Europe
friendly,
for
example,
and
then
one
like
these,
where
all
of
us
are
expected
to
come,
you
know
that
that
would
work,
probably.
C
B
B
Let's
see
how
that
goes,
so,
let's
see
I'm
honestly
I'm
a
little
bit
not
concerned
about
cautious,
because
I
know
that
things
tend
to
get
slower
during
summer.
I
wonder
whether
we
will
be
able
to
finish
all
of
these
before
you
know.
Let's
see,
let's
see
how
things
are
are
going
there.
You.
B
Yeah
correct
because
I
remember
people
taking
long
holidays,
even
myself,
I'm
tempted
to
do
that.
So
so
that's
that's
the
thing.
You
know
something
to
keep
in
mind,
also
how
this
may
affect
you
know
things
yeah,
let's
see:
okay,
perfect
yeah!
Thank
you.
Thank
you.
So
much
then
yeah.
So
so.