►
From YouTube: IETF98-CURDLE-20170327-1710
Description
CURDLE meeting session at IETF98
2017/03/27 1710
A
B
D
Anybody
want
to
be
the
jabber
scribe.
Thank
you,
yo.
Anybody
want
to
take
minutes.
It's
really
easy,
really,
really
really
easy.
I'll
give
you
a
cough
drop.
I'll.
Give
you
to
cough
drops
seriously.
We
can't
proceed
DJ,
all
right,
Melinda!
Thank
you.
Anyone
who
goes
to
certificate
transparency
now
as
to
volunteer
to
take
minutes.
E
D
Alright,
the
blue
sheets
are
going
around
there
on
that
side
of
the
room,
that's
them
over
by
now.
You
have
all
seen
the
note
well
at
least
three
times.
Oh
my
now
yeah,
okay,
there
we
go
now,
I'm
using
the
mic.
I
am
rich.
This
is
daniel
60,
so
you've
all
seen
to
know.
Well,
basically,
it
says
if
you've
got
any
IP
r,
you
must
have
disclosed
that
you've
got
the
IPR.
Otherwise,
please
leave
the
link.
D
Without
further
ado,
most
of
this
meeting
is
probably
going
to
be
asking
for
people
to
commit
to
reading
the
drafts
there
in
a
couple
cases
help
Shepherd
a
document
through
their
short
they're,
very
straightforward,
they're,
easily
separable,
there's
not
a
lot
of
relationships
among
all
of
them.
It's
not
like
you
have
to
send
in
understand
all
of
HTTP
before
you
can
understand
h2.
So.
G
Okay,
so
this
drop
I
think
this
dress
is
one
of
our
priority.
G
We
have
discussions
about
assigning
your
IDs,
so
we
took
a
decision
which
is
requesting
the
ini
ark
and
putting
this
whole
idea
to
under
this
arc.
There
has
been
some
discussions
about
pre
hash.
This
is
non
pre,
ash,
signature,
I
think
the
consensus
is
that
we
should
use.
We
are
only
defining
the
draft
for
non
pre
hash
version
variant.
So
I
guess
want
to
comment
that
I
think
that
that
also
should
be
said
for
all
the
drive.
If
we
should
say
that
clearly
it's
it's
a
basically
a
design,
choice
and
yeah.
G
D
G
H
G
G
D
So
all
right
should
we
post
a
draft
probably
pretty
quickly,
and
then
we
are
ok
and
then
we'll
forward
it
out,
though
yo
yo
yo,
just
sync
up
with
the
ipsec
box.
A
G
Edss
signatures,
so
nothing
really
much
to
say
we
one
person
is:
we
only
had
one
reviewer,
so
it's
pretty
shaped
but
a
well.
If
possible,
we
would
like
to
have
another
reviewer.
So
anyone
volunteering.
G
Next
slide,
this
one
is
well
has
more
reviews,
I,
don't
think
we
need
really
another
reviewer.
Any
questions
regarding
this
draft.
G
Next
draft
yeah
they're
all
in
Lascaux,
so
all
those
so
this
draft
yeah
it's
about
to
use
of
share
too
yeah
I.
Think
we
it's
it's
almost
the
same.
We
well.
We
would
need
more
reviews,
especially
I,
think
it's
more.
The
way
to
graph
is
written,
but
it's
pretty
good.
It's
pretty
well
shaped
and
almost
ready,
it's
a
very
short
drat.
I
think
less
than
10
pages.
So.
I
D
G
Yeah
this
drafty
well,
is
also
pretty
much
ready.
Some
changes
have
been
submitted
to
the
least
he
has
been
considering
various
implementations.
So
I
don't
think
it's
very
clear,
but
it
would
be
better
to
have
some
other
feedbacks.
Other
reviews,
it's
mostly
to
see
if
the
text
is
clear
rather
than
a
contact
I
mean
so
that's
pretty
easy
to
go.
Yeah.
G
Yeah,
this
one's,
so
okay,
yeah
I,
get
very
confused
with
the
name
of
the
draft,
so
this
one
is
adding
a
new
gfield
new
key
exchange:
algorithms
based
on
the
new
other
kernels,
the
curves
yeah.
It's
only
adding
a
one
point
or
two,
so
please
say
you
agree
with
a
draft,
and
so
we
can
move
that
forward
next
slide
and.
D
B
Just
one
question
about
SSH
in
general:
what
happens
if
you
put
with
the
existing
applications
or
app
that
are
out
there?
If
you
have
nests
SH
key
for
an
algorithm
that
isn't
understood,
did
the
widely
used
versions
of
ssh
do
something
sensible
or
do
they
fall
over
and
die?
Has
anybody
looked
into
it?
I.
J
B
D
K
G
D
L
D
F
Is
dkg
sorry
I
actually
haven't
read
this
at
all,
but
I'm,
assuming
these
are
finite
field
routes
that
here
that's
fine
I,
actually,
don't
think
that
you
should
say
use
the
same
groups
that
we
specified
for
40
of
us,
although
I
do
think
we
should
have
specific,
specified
groups.
So
I'm
not
sure
why
ecker
recommended
that
you
use
the
exact
same
groups
that
we
did.
It's
fine
to
have
two
different
protocols
use
different
sets
of
groups
as
long
as
they're
strong,
primes,
usual
usual
constraints,.
A
J
F
Just
to
to
provide
mean
the
rules
for
generating
groups
that
are
strong
are
not
complicated,
like
we
understand
those,
and
so
you
might
want
to
not
use
them
across
domains.
If
there's
some
weird
something
gets
cross
domain
that
we
don't
understand,
there's
a
bunch
of
situation
with
cross
domain
attacks
because
you're
using
a
similar
protocol
and
things
hook
together.
It
turns
out
that
something
TLS
looks
like
something
an
association
can
be
reused.
I,
don't
see
that
here,
but
I
don't
know,
and
if
you
avoid
using
the
same
groups,
you
can
avoid
that
problem.
F
If
Greta,
these
are
the
same
groups
as
I
them,
then
now
you
die
you're.
Just
the
question
is
I
vs
SSH,
so
I'm
totally
fine
with
using
one
set
of
groups
for
one
protocol
to
avoid
any
possible
cross
protocol,
condemning
a
condition
that
I
don't
understand.
I'm
not
going
to
have
a
specific
answer.
Oh
I,
don't
know
I.
J
D
L
Don't
think
I
those
groups
has
any
equities
here.
Like
you
know,
we
may
have
some
overall
ITF
question.
What
we
should
do,
but
it's
not
like
jealous,
cares
what
I
mean
other
than
as
a
general
matter
of
principle
cares
what
I
safe
does
anything
that
me
adam
says
these
are
just
this
is
just
you
know.
M
M
D
G
Well,
we
we
have
well
when
the
CMS
draft
and
the
peak
eggs
draft
will
be
sent,
will
we
have
a
receipt
of
requests
to
for
a
GSS
update,
and
so
that's
going
to
be
the
next
coming
draft.
O
I'm
sorry
I
was
late.
Did
we
talk
about
draft
p
kicks
and
did
we
settle
on
absent
null
or
both,
if
not
I'd,
like
the
darker
added
since
we're
all
here,
so
nope
rehash
all
that
I
understood?
That
was.
O
The
word
optional
in
algorithm
identifier
and
as
a
result
a
bunch
of
people
were
forced
to
specify
null
as
a
parameter
when
none
was
needed
and
then
they
had
it
optional
back
in
the
next
release,
and
so
there
is
some
some
code
that
doesn't
remember
that
or
does
not
yet
know,
hear
that
optional
is
there
and
they
insist
on
some
parameter
and
so
I
prefer
to
not
do
that.
But
get
people
update
their
code
and
the
bottom
line
is
that
we
have
one
place
in
that
document.
O
G
D
M
Think
they're
so
document,
okay,
I,
think
you're,
also
a
lot
of
other
algorithms
that
are
actually
using
saying
that
you
must
not
have
you
know
you
first,
let's
have
now
they're,
so
if
they
don't
support
that
they
don't
to
portos
sequence,
all
girls,
either
so
I
think
the
chiverses
need
to
fix
it.
Their
stuff,
fun.
D
I'm
not
sure
how
to
phrase
the
question
without
annoying
people,
but
then
yeah,
well,
okay,
so
yeah
absent
break
some
Java
in
both.
So
how
many
want
to
support
those
hum
absence
or
brick
city?
Okay,
all
right!
So
it's
absent
simplest,
cleanest,
break
some
java,
none!
D
No!
No!
I
hated
this
one
s
when
sequel
had
the
problem
too
right.
No,
you
carry
an
explicit
I'm,
not
here
and
then
both
so
how
many
people
are
in
favor
of
supporting
both
how
many
people
are
in
favor,
having
no
there's
an
explicit
I'm,
not
here
how
many
people
are
in
favor
of
having
no
indicator
when
there
is
no
option.
A
O
G
G
H
Try
you
have
mirror
hitter
Goodman
on
the
list
said
that
there's
actually
no
weakness
that
we
know
of
with
PK
SI
s
1
point
5,
so
it
might
as
well
stay
with
that.
It's
true
that
it's
that
it's
easier
to
make
proofs
about
PSS,
but
there's
no
weakness.
Why
I
add
some
new
stuff
when
we
already
have
because
he
s
1
point
5,
not
my
arguments,
pretty
good
yeah.
F
M
H
M
E
M
But
I
mean
I
mean
yeah,
then
I'd,
basically
also
actually
just
moved.
A
basic
was
using
1.5
old,
also
and
now
in
the
bin,
which
defied
the
Liberator
to
sleep
in
search.
We
actually
only
departed.
You
know
to
say
that
the
PSS
system
under
the
soup
to
speak
on
which
of
course
causes
you
know
issues
because
people
actually
have
to
implement
it
when
take
them
into
signature
algorithm.
They
can't
just
make
a
very
simple.
You
know.
M
J
N
A
D
All
right,
yeah,
thanks
for
coming,
we'll,
probably
wrap
up
at
the
next
IETF.
Everything
will
just
be
in
the
last
call
next
class
next
idea.
For
probably
that's
certainly
the
last
face
to
face
unless
somebody
comes
up
with
a
whole
bunch
of
new
drafts
and
mechanisms.
Thank
you
all
for
your
participation
see
you
later.