►
From YouTube: 2022-07-05 meeting
Description
cncf-opentelemetry@cncf.io's Personal Meeting Room
A
A
A
Okay,
let's
start,
then
thank
you
so
much
for
joining.
I
only
see
a
few
items,
so,
let's
get
rolling
the
first
one
is
about
a
change
in
the
puerto
ripo.
There
is
this
experimental
old,
trace,
config
message
in
the
protocols
that
nobody
is
using.
So
I
think
that
it's
a
good
call
from
dealer
and
removing
that,
since
we
don't
need
that,
we
can
add
it
later
if
as
needed.
B
I
said
this:
we
are
great
with
christian
that
we
would
clarify
the
net
peer
net
host
name
attributes
and
introduce
new
for
the
low
level
socket
communication.
B
A
Yeah
is
anybody
from
the
java
group
this
here
from
the
java
instrumentation
group
tigran?
Maybe
it
looks
great
to
me
to
be
honest,
fantastic,
but
I'm
afraid
that
somebody
may
have
a
saying
I
mean
we
are
missing
that
as
a
breaking
change
anyway,
but
yeah.
Let
me
book
the
yeah.
A
Yeah
java
group
yeah,
otherwise
I
think
it's
good
to
go.
I
didn't
want
to
honestly
to
review
that.
I
mean
to
approve
that,
because
technically
it
means
that
they
can
go.
I
was
waiting
for
from
trask.
Okay.
Let
me
poke
him.
Oh.
A
Or
yeah
I
mean,
since
they
are.
The
group,
like
you
know
that
have
made
most
of
the
progress
lately
on
the
instrumentation
side
or
anybody
from
the
instrumentation
group
just
to
totally
verify
that
this
is.
This
is
good
to
go.
Otherwise,
it
looks
great.
B
Thank
you
so
much.
I
have
a
small
request.
There
is
a
pull
request
for
the
fix
in
build
tools.
I
have
an
agenda,
it's
approved
by
christian,
and
if
somebody
can
merge
it,
it
would
be
awesome.
C
You
is,
is
there
any
other
change
imminent?
That
would
be
released
soon
or
should
we
should?
We
just
do
a
point.
One
release
right
now.
C
A
Thank
you
so
much
for
that.
Okay,
moving
forward,
johannes
and
joao
context,
propagation
requirements
for
messaging
semantic
conventions.
A
D
Yeah
so
I
joined
the
messaging
semantic
conventions
working
group
and
we
have
been
working
on
on
on
stabilizing
the
the
current
semantic
conventions
and
johannes
has
this
ltap
open
and
he
asked
me
to
bring
this
up
because
it
doesn't.
It
didn't
have
much
movement
recently,
so
we
have
a
lot
of
approval
from
people
from
inside
the
group
that
is
working
on
this,
but
not
not
much
from
from
others
yeah.
D
So
if,
if
you
can,
if
you
can
take
a
look
and
and
and
give
approvals
or
if
something
doesn't
make
sense
to
you
leave
your
comment,
basically,
the
otep
makes
it
makes
it
explicit
how
context
propagation
should
work
in
messaging
systems.
Today,
the
current
current
conventions,
it's
implicit,
that
the
context
has
to
be
propagated
with
the
message
in
itself
and
they'll
tap
just
make
this
explicit
in
how
this
will
be
done
and
how
to
do
in
in
in
each
protocols
and
also
mentions
that
each
protocols
has
a
draft.
D
Has
a
draft
drive
to
spec
on
the
on
the
w3c
on
how
this
is
done
in
each
protocol
and
so
on?
So
if
you
have
some
time,
please
take
a
look
and
and
leave
your
comments
there
or
your
approvals.
A
A
Oh
by
the
way,
on
the
semantic
conventions
for
messaging,
I
just
spoke
yuri,
who
had
a
a
few
comments
and
he
didn't
answer.
Oh
great
great,
thank
you
yeah,
otherwise,
yeah
I
mean
I
read
them
and
they
don't
seem
blocking.
They
were
more
about
clarifications,
but
if,
if
he
doesn't
answer
soon,
I
think
we
are
ready
to
go
on
that
front
on
that
front,
yeah
all
right,
great
okay.
So
if
there's
nothing
else
to
talk,
we
can
go
back
to
to
work
going
once
going
twice.
A
Okay,
so
thank
you
so
much
everybody
stay
safe
and
yeah.
See
you
next
time.