►
From YouTube: IETF99-CURDLE-20170717-1130
Description
CURDLE meeting session at IETF99
2017/07/17 1130
https://datatracker.ietf.org/meeting/99/proceedings/
A
B
B
A
B
C
C
C
We
have
one
draft
that
still
need
to
be
sent
in
SSH
as
well.
We
have
one
draft
the
one
we're
just
going
to
show
next
before
we're
done
with
the
current
draft
in
the
queue,
and
we
have
one
of
the
draft,
which
is
a
requesting
adoption
and
an
SSH
I
forgot
that
one
draft
is
being
revived
and
submitted
soon.
C
So
the
the
draft
we
would
like
to
to
have
a
look
at
is
the
recommendation
on
SSH
key
exchange.
A
so
I.
Don't
know
if
you
look
at
the
table
here
if
these
recommendations
fits
everyone's
and
if
not
you
please
to
raise
some
comments
or
even
better,
to
raise
your
comments
on
the
mailing
list,
because
we're
waiting
for
comments
to
send
this
draft
to
the
ice
tea.
D
D
E
I
guess
I
was
also
puzzled
by
the
allocations
of
the
NIST
curbs
in
particular,
why
people
are
happier
with
with
P
384
than
peach
of
d6.
I
I
mean
I
think
we
find
to
say
that
our
policy
is
that
we
think
people
don't
like
love
the
NIST
codes
that
much
we
want
to
move
the
IRT
F
curves
I
think
it'd
be
fine
to
say
that
we
want
this
curves
ever
staying
with
them,
but
I'm
not
aware
of
any
reason
why
you
would
favor
P,
3
or
4
P
256.
E
If
that's
basically,
some
message
community
think
that
nice
is
fine,
but
it's
not
like
not
justifiable.
I.
Think
I'm,
touching
all
around
at
this
moment,
but
again
I
mean,
like
I'm,
happy
to
further
the
consensus
of
the
community.
If,
because
the
community
is
that's
what
they
want
to
do,
but
I
really
document
I
didn't
think
it
was
I
didn't
think
it
made
me
very
sure,
arguments
why
this
should
be
the
case.
E
F
Sorry
I
took
my
nametag
off,
I'm
deb
foolish
men
are
saying
so
both
in
this
draft
and
his
diffie-hellman
draft,
he
references
our
CNS,
a
guidance,
which
is
why
he
should
Singh
P
256,
which
I
don't
care
about
one
way.
Other.
You
may
have
said
she
myself,
not
not
neither
here
nor
there
in
in
the
diffie-hellman
Draft.
F
He
adds
groups
15,
16
and
17,
and
here
he
only
has
groups
14
and
16
she's
a
little
I'm,
not
sure
yeah,
okay,
good,
okay,
good
and
if
he
was
gonna,
add
15
I
would
say
you
would
use
3d
for
which
he
also
does
not
do
in
his
diffie-hellman
draft
and
it's
difficult
and
wrapped.
He
uses
all
of
those
groups.
15
16
17
with
sha-512,
so
I'm
happy
to
see
that
he's
got
ECD,
H,
P,
3
4
here
with
sha
384,
but
I.
Don't
understand
that
diffie-hellman
group
saying.
F
F
E
I
guess
I
mean
we'd,
be
useful,
I
think
to
to
perhaps
start
with
some
overall
premises
of
what
we're
trying
to
achieve
and
biology
is
so
I
mean
so
I
understand,
I'm
the
CNS,
a
god.
It's
a
little
surprising
that
the
sort
of
deprecating
256
it's
not
PJ's
efficient,
let
that
paper
shot
so
like
on
sirs
I
mean
so
we
went
back
and
forth
from
this
namilama
still
recall
in
it.
E
I
think
you
know
the
if,
if
the
to
my
knowledge,
the
this
sort
of
implementation
and
side-channel
such
properties
of
p2p
sections
and
PD,
384
and
sha-256
and
Java
for
like
well,
for
you
call
it
and
that
the
questions
about
chronic
computers
and
and
so
to
understand,
sit,
they
can
be
good
to
sort
of
say
like
and
I
hate.
Just
on
the
Senkaku.
E
F
H
This
is
actually
following
the
same
thing
that
we
don't
need
be
denied
basic,
so
all
the
groups
that,
although
the
only
lists
things
that
are
immersed
or
suits
or
must
not
or
should
not
all
the
mayor
grams
are
ignored
because
there
is,
you
know,
tons
of
those.
So
so
it
actually
says
there
in
there,
everything
that
is
not
mentioned
explicitly
may
be
implemented.
C
E
So
I
guess
I'd
read
the
I'd
assumed,
so
that's
it.
Then
this
guidance
is
premise
on
the
notion
that
you
want
to
move
to
more
qua
somewhat
more
quantum
state,
algorithms
but
I
suppose
I
could
week
I'm
save
algorithms
in
some
worlds,
I
understand
it
and
that's
the
rationale
for
the
higher
sizes
of
the
keys
wrong.
With
this,
as
I
said,
I
mean
the
the
you
know
when
we
did
when
we
did,
you
know
X
to
5
or
9
X
4
for
8
I
mean
I.
G
E
I
say:
yes,
sorry,
oh
yes,
I'm
sorry
I
thought
this
yeah
I
guess
so
you
think
I
do
think.
We
need
to
have
a
consensus
for
our
policy
purposes
on
whether
we
think
256
bits
are
strong
enough
for
the
indefinite
future
and
and
if
we
don't
think
that
then
I'd
like
to
understand
why?
If
we
do
you
think
that
then
then
then,
as
I
say
generally
this
this,
this
assignment
a
sense
unless
you,
unless
you
have
somebody
using
credit
reason
for
that
from
the
stage
community.
G
E
What
I
mean
to
say
is
that
that
we
are
currently
designing
protocols
for
56
the
IETF
and
not
saying
when
you
plan
to
fault
them
out
like
anytime
soon,
and
so
it's
a
time
soon.
That
would
be
like
a
bit.
Then
we
shouldn't
let
that
because
I
first
was
like
this
is
irrelevant,
like
planet
TLS,
which
is,
is
I.
H
H
One
should
start
to
someone
which
is
in
IPSec,
we
for
say
settings
we
actually
moved
from
must
to
suit
not
just
to
keep,
because
because
I
mean
it's
implemented,
every
single
implementations
out
there
and
to
make
those
implementations
to
be
you
know
violating
must
not
because
they
still
continue
implementing
it
and
because
it's
a
back
part,
you
know
it
was
the
default
setting.
So
I
think
it's
actually
a
bad
idea
to
go
from
much
too
much.
H
Not
so,
but
it's
it's
of
course
you
know
something
that
we
can
tease
out
here,
but
I
think
it
will
be
better.
The
burden
should
not
like
me
to
did
not
be
sick
should
not
should
be
giving
us
enough.
You
know
Rob
for
people
to
say
that
should
not
use
it
that
I.
Actually,
it
could
be
much
that
you
Susan,
but
you
can
still
implement
it.
So
is.
D
F
Well,
he
didn't
want
the
ECD
H
256
made.
It
should
not
right
so
Quinn
made
the
same
point
right
so
don't
make
that
it
should
not
right
because,
from
your
point
of
view,
it's
not
on
the
way
out.
It
may
be
on
the
way
out
from
our
point
of
view,
but
it's
not
on
the
way
out
from
your
point
of
view,
so
it
shouldn't
be
a
should.
It
should
be
at
least
a
should
and
really
probably
ought
to
be
mom
more
than
that
I.
E
The
social
point
is
I
think
we
should
have
a
common
understanding
of
what
curve
you
think
are
good
workers
in
are
bad,
and
my
understanding
is
that,
outside
of
this
working
group
on
the
general
consumption
has
been
that
we
should
favor
P
256
over
P
3
for
and
that
in
general
should
be
or
256
over
the
next
step
up,
which
is
three
four
four
four
eight,
and
that
in
some
working
groups
we
we've
had
for
legacy
reasons.
We
decided
six.
E
G
F
G
If,
if
we're
saying
that
the
256
bit
sizes
are
fine
and
we
should
be
using
those
than
we
should
be
making
the
statement
there,
the
256
bit,
things
are
fine
and
we
should
simply
choose
between
the
ITF
ones
and
the
and
then
this
one's
as
circumstances
dictate.
So
if,
if
we
have
an
installed
base,
that's
that's
relying
on
NIST
and
we
use,
we
might
might
favor
the
NIST
once
over
the
the
idea
funds
and
vice
versa.
So
in
this
case,
what
I
think
you
should
do
given
what.
B
B
Yeah
toes
I'm
gonna,
we
gotta
cut
the
line
because
we
have
actually
more
important
discussion,
I
think
as
in
like
what
we
do
next
for
the
next
three
minutes,
so
you
wanna
move
ahead.
Let's
take
it
to
the
list.
I
think
we're,
basically
all
in
agreement
as
to
what
the
philosophy
of
what
we
want
is
alright
yeah.
H
The
plus
is
rational,
but
the
process
of
money
is
really
what
what
is
going
to
be.
What
we
think
is
going
to
be
happening.
We
have
currently
has
been
guessing
wrong
of
all
of
that
all
of
time
in
IP.
Second,
so
it's
actually
what's
nice
idea
in
the
beginning,
I'm,
not
sure
I
feel
really
very
useful
anymore,
because
I
mean
you
seem
to
be
very
bad
at
guessing.
B
Okay,
so
looking
from
that
on
the
list,
but
yeah
we'll
get
rid
of
the
pluses
and
minuses
will
coalesce
around
256
for
48
to
55
19.
Okay.
So
that's
that's
the
action
I!
That's
the
action
item.
The
chairs
have
confirm
I'm
a
list
that
that's
the
direction
will
get
rid
of
that
will
get
rid
of
they're,
trying
to
guess
the
future.
C
C
So
now
the
question
is:
why
are
we
regarding
the
charters,
so
I
built
up
a
table
just
to
figure
out?
Well,
we
had
many
objectives.
One
was
to
introduce
the
new
curves
Sasha
and
es
where
it
was
not
already
done,
and
the
other
thing
is
well
to
update
and
duplicate
some
of
the
algorithm,
so
in
SSH
well,
tomorrow,
up
to
what
I
know,
I,
don't
think
Sasha
or
a
yes
CCN
of
weather
GCM.
Well,
one
of
those
is
probably
missing.
So
I
don't
know
if
there
are
any
people
willing
to
feed
these
gaps.
C
F
C
G
Someone
Thompson
I
had
a
point
on
the
hose
a
line.
We
have
some
interest
in
updating
web
crypto
for
Edie
to
509
and
X
two
five,
five
one
nine,
so
we're
gonna
do
the
EC
dhes
stuff
for
that
you
don't
have
a
box
for
25.9
on
the
Jose
side
of
things.
But
I
need
to
talk
to
him
to
make
me
a
lot
about
that,
but
him
might
be
doing
some
work
there.
I.
G
G
The
w3c
web
crypto
is
it
actually
kind
of
goes
hand
in
hand,
and
you
want
to
make
sure
you
synchronize
identifies
and
usages,
and
things
like
that,
because
you
need
to
to
have
the
OS
a
pass
to
do
the
web
crypto
parts
properly
and
so
on
and
so
forth
from.
But
there's
this
at
least
we've
discussed
it
this
week
doing
that
and
so
okay,
if
the
working
groups
gonna
remain
alive.
This
is
a
great
venue
for
doing
that.
Sort
of
sort
of
work,
so
I'm
just
giving
you
a
heads
up.