►
From YouTube: 2022-08-24 meeting
Description
Open cncf-opentelemetry-meeting-3@cncf.io's Personal Meeting Room
A
C
D
I
believe
Raphael
wanted
to
come
and
talk
about
the
pr
that
he
has
for
updating
the
minimum
TLS
version.
I
thought
he
was
going
to
put
that
on
the
agenda
opinion.
Okay,.
A
All
right
so
Anthony
or
or
who
is
going
to
be
a
discussion
on
the
TLs
versions.
E
Oh
yeah,
so
can
I
start
it
with
that
topic.
Sure
yeah
yeah,
so
I
noticed
that
the
current
version
of
The
Collector
allows
you
to
use
TLS
1.0.
If
you
don't
Define,
if
you
don't
have
the,
if
you
don't
explicitly
Define
the
minimal
tellers
version,
that's
just
for
the
receiver,
I
believe
for
the
exporter.
It
will
be
used
1.2,
but
the
the
reason
for
that,
because
we
are
delegating
the
decision
to
the
go
Library
so
I
think
that's
not
safe
to
provide
the
users
with
insecure
default.
E
A
A
There
is
a
discussion
in
there
and
I
I.
Just
don't
remember
right
now.
What
was
the
outcome
back
then,
but
I
am
in
favor
of
having
1.2
as
a
default
for
TLS.
Now
I'm,
not
I'm,
not
okay,
in
having
extra
knobs,
as
you
mentioned,
to
prevent
people
from
using
1.0
or
1.1,
because
people
do
have
good
reasons
to
do
that.
A
To
use
those
versions,
especially
on
Legacy
systems,
so
I
I
would
encourage
people
and
and
leave
warning
messages
on
the
logs
if
they're,
using
an
insecure
setting
but
I
wouldn't
prevent
them
from
using
those
insecurities
such
as,
if
they
have
to
right.
So
perhaps
they
they're
using
some
old
firewall
version
that
does
not
support
1.2
or
perhaps
a
load
balancing
or
something.
C
B
C
B
B
E
B
A
Server
provides
to
you
to
clients
right
I
mean
there
is
a
a
negotiation
of
the
of
the
contents
during
the
handshake.
Isn't
it
foreign.
E
Can
check
the
defaults
in
the
language
but
for
let's
say
for
reference
I
looked
briefly
yesterday
and
I
believe,
let's
say
even
python
python
or
in
Python
1.2
is
the
default
and
you
to
use
1.0
or
1.1.
You
have
to
make
some
chains.
Let's
say
it's
blocked
by
default
for
Java
I
believe
is
1.2,
but
you
can
explicitly
Define
1.0
I
didn't
look
into
other
languages,
though,
but
I
can
take
a
look
into
that.
B
E
B
Not
just
about
the
the
available
versions
in
the
languages,
but
about
our
specific
implementations
that
open
Telemetry,
we
have
sdks
for
many
languages
and
if
they
happen
to
be
using
a
different
version,
lower
version
than
they
may
not
be
able
to
send
to
the
to
the
collector
in
the
default
configuration
and
that's
highly
undesirable.
We
want
it
to
work
out
of
the
box.
A
Yeah
so
typically
for
TLS
connections,
there
is
a
handshake
phase
where
natural
protocol
is
agreed
on.
So
if
I
understand
that
we
are
providing
one
or
two
by
default
by
the
server,
so
the
full
the
server
offers
1.2
by
default,
and
if
the
client
cannot
talk
one
or
two,
then
they
try
to
get
one
at
one
if
they
cannot
and
they
try
1.0
right
now.
The
problem
is,
the
server
is
offering
1.0
by
default,
which
is
you
know,
the
client
in
C
is
1.0
sees.
A
Okay,
I
can
support
that
and
they
they
just
use
that
I
believe
so
now.
Rafael
would
have
to
confirm
that,
but
I
I
believe
the
only
change
here
is
on
on
the
order
of
the
ciphers
or
the
protocols
that
are
offered
to
clients
during
this
initial
handshake.
D
B
So
what
I'd
advise
to
do
is
create
an
issue
in
every
open,
Telemetry
sdks
repository
asking
to
confirm
that
they
are
okay
with
1.2
being
the
default
and,
if
not,
they
need
to
fix
it
on
their
end
and
only
after
we
have
the
confirmation
from
all
the
languages
make
the
change
here
in
The,
Collector
I
think
that
would
be
the
safe
bet.
Otherwise
there
is
a.
A
A
That's
true,
although
before
June
27th,
so
a
couple
of
months
ago,
before
that
we
had
1.2
as
a
minimum
version
already,
it
was
changed
recently
so
on
June.
A
Because
of
so
the
title
of
the
pr
is
fixing
incorrect
default
TLS.
Basically,
it
seems
there
was
a
a
mismatch
between
documentation
and
the
code
and
people
fixed
by
changing
their
code
to
be
1.0.
Instead
of
changing
the
documentation
to
specify
1.2.
A
D
B
Yeah-
it's
probably
it's
probably
just
sufficient
to
let
people
know
we
don't
have
to
be
blocked
by
that
because,
as
you
said,
if
it
worked
in
the
past,
we
would
have
discovered
that
there
were
problems
already
by
now.
If
we
haven't
heard
anything
then
probably
should
be
fine.
Just
let
people
know
that
this
is
the
change
we're
making.
B
It's
it's
probably
excessive,
just
just
what
what
Anthony
said.
I
think
it
should
be
sufficient.
Just
let
maintainers
know
posting
slack
Channel
and
maybe
join
the
maintainers
meeting
on
Monday.
Let
them
know
this
is
a
change
that
is
happening
in
The
Collector
and,
if
you're,
not
if
on
your
end,
you're,
not
using
1.2
or
higher,
then
please
do
because
otherwise
it's
not
going
to
work
with
the
collector
by
default.
D
I
think
Bogdan
is
the
one
who
proposed
that
we
reset
the
server
minimum
to
1.0
to
match
the
go.
Sdk
defaults
he's
not
here.
Do
we
need
to
make
sure
that
he's
on
board
with
this.
B
Yeah
thinking
on
the
on
the
pr
that
you
you
have,
maybe
he
has
something
in
his
mind.
E
Okay
yeah.
Actually
he
was
the
one
who
added
your
jersey
yesterday
to
the
as
a
reviewer,
but
yeah
we've
peeing
him
explicitly
about
the
the.
A
All
right,
the
next
item
is
a
a
review
request
by.
C
A
All
right,
I'll
ask
Jerusalem,
he's
been
working
on
the
routing
processor
and
he
his
strong
interest
in
in
the
query
language
as
well,
so
he
might
be.