►
From YouTube: COSE WG Interim Meeting, 2020-10-07
Description
COSE WG Interim Meeting, 2020-10-07
A
C
A
Okay
and
then
one
more
more
with
the
administrative
notes
myself
and
people
will
try
to
do-
we
can,
if
anybody's
willing
to
help
that
would
be
greatly
appreciated.
We're
only
looking
for
action
items.
We
need
to
take.
A
So
jim
shot
as
most
you
may
know,
now
passed
away
on
friday,
greatly
missed.
He
was
very
instrumental
in
starting
up
this
working
group,
the
first
time
in
this
current
time.
D
B
D
E
So
so
this
is
lawrence
and
I
do
have
something
I'd
like
to
say
when
I
first
started
looking
at
at
cosine
about
four
years
ago,
I
was
like,
what's
august
sellers,
and
but
oh
you
mean
this.
Guy
is
working
on
itf
standards
and
has
a
side
business
running
a
winery,
and
I
thought
about
that
and
that
that-
and
I
was
thinking
about
retiring
leaving.
E
So
it
was
a
little
bit
of
a
model
for
me
like
that
sounds
good.
I
like
that
idea,
so
so
I
I
was
always
kind
of
intrigued
with
with
jim
for
doing
that,
and
I'm
kind
of
doing
it
now
so
somewhere,
someone's
saying
so
I
and
then
the
other
thing
is.
When
I
looked
at
cozy,
I
I
to
me
it
looks
like
a
standard
that
will
endure
for
a
really
long
time.
You
know
it's
really.
It
seems
like
it's
on
a
really
solid
basis
to
me.
A
F
Well,
this
is
hank.
I
just
want
to
answer
this-
that
when
I
stop
working
or
coming
to
itf
meetings,
jim
was
one
of
the
first
people
that
I
went
out
to
have
one
of
these
famous
lunch
meetings
with
so
so
we
we
had
a
famous
a
very,
very,
very
good
steak
and
we
had
a
very
continuously
over
the
past
meetings.
F
F
He
could
look
a
little
bit
grumpy
and
he
was
very,
very
forthright
with
his
opinions
and
I
think
that
made
talking
to
him
actually
easier
because
you
didn't
have
to
dig
through
all
this
pretentious
stuff.
You
sometimes
account
sorry
no
offense
to
anyone
here,
but
sometimes
this
happens
and
with
with
jim.
Well,
basically,
no
it
didn't
happen,
and
that
was
always
something
I
will
remember
fondly
because
yeah.
It
makes
me
smile
today
when
I
think
back,
and
I
think
that's
the
important
stuff
to
remember.
A
My
for
myself,
this
is
matthew
miller
when,
when
I
first
started
working
on
security
related
things
at
the
itf
jim
was
incredibly
patient
with
me,
as
I
was
trying
to
understand
how
various
cryptographic
algorithms
got
got
applied
and
if
you
used
and
abused,
and
I
really
appreciate-
I
really
truly
appreciated
that
at
that
point,
you
didn't
already
know
what
you
were
talking
about.
A
lot
of
people
would
do
you
and
he
took
he
took
the
time
to
help
help,
explain
and
help
walk
through.
A
A
All
right,
anyone.
G
A
G
I
missed
probably
all
so
just
want
to
chime
in
into
what
what
the
last
two
statements,
which
I
heard.
G
A
A
A
A
All
right,
let's
go
ahead
and
move
on.
Oh
yes,
as
we
all
know,
and
was
responsible
for
just
about
every
working
group
document
that
we
have
today
and
we
have
still
in
flight.
A
So
with
the
adas
we've
worked
out,
the
chairs
have
worked
out
some
plans
of
how
we're
going
to
move
progress
these
on
starting
with
our
our
core
documents,
the
8152
best
struct
and
alex
alex,
is
already
in
the
rfc
editor's
queue.
A
But
if
there's
anything
that
comes
up,
we
will
we
will
go
through
that
struct.
There's
still
a
few
nits
that
need
to
be
addressed
from,
I
believe
the
only
ones
left
are
the
ones
from
ben,
so
those
will
be
addressed
I'll,
be
making
those
edits
and
we'll
we'll
continue
to
progress.
That
document.
A
The
x509
document,
which
is
pulse
with
the
isg
and
his
market,
revised
id
needed
evo,
is
going
to
be
making
edits
to
that.
A
The
the
two
algorithm
documents,
the
hash
outs
and
and
8152
best
outs,
like
we
said,
are
in
the
rfc
editor's
queue
if
any
edits
are
necessary,
we'll
bring
them
up
with
the
with
the
working
group
and
the
travis
will
make
sure
those
get
up,
get
applied
and
directed
back
to
the
the
the
irc
editor
and
then.
A
Finally,
the
counter
signed
document
we
just
did
russ
housley
has
volunteered
to
work
as
editor
for
this
document,
so
we'll
take
take
him
up
on
that
and
a
new
revision
making
note
of
that
and
with
the
memorial
to
gym
will
be
included,
will
be
coming
sometime
soon
for
now,
russ
we
marked
directly
in
the
in
the
internet
drafts
as
the
editor
when
we
go
to
publication,
we'll
be
looking
to
remove
his
name
and
leave
it
solely
as
jim.
A
A
A
Next
up
we
have
was
certificate.
Compression
there's
been
a
quite
a
bit
of
discussion
on
on
the
list.
I
wasn't
sure
if
goren
or
if
you
had
any
comments
you
wanted
to
make
here
or
anything
you
wanted
to
talk
about,
specifically
with
where
that's
where
that's
headed.
G
So
yeah
yeah,
I
think
we
got
good
comments
as
always
from
jim
and
yeah.
We
need
to
get
back
on
those.
I
think
it's
it's
very
helpful
and
there
was
there
was
also
I
mean
there
was
there
were
several
responses.
One
was
on
the
on
on
the
draft,
which
I
think
will
will
address
in
pretty
soon,
and
then
there
was
sort
of
the
the
charter
proposal.
So
I
got
the
task
last
last
week.
G
Okay,
maybe
that's
a
separate,
separate
topic,
so
I
don't
know
if
there's
anything
more
to
comment
on
the
the
certificate
compression.
I
suppose
we
come
to
the
charter
later:
okay,
okay,
yeah,
so
yeah.
So
so
I
mean
there
was
basically
good
good
good
comments
about
about
the
different
message,
fields
and
and
john
responded
to
a
few
of
those
and
we're
working
on
responses
to
the
others.
So,
yes,
that's
where
we
are.
A
Okay
with
that,
okay,
unless
there's
any
other
comments
now
around
certificate
compression,
I
think
we
can
move
on
to
the
charter.
Again,
we've
seen
a
lot
of
discussion
and
I've
note
when
you
have
any.
Would
you
like
to
finish
off
your
comments.
G
Right
thanks,
so
we
sent
a
proposal
at
the
25th
of
september.
I
think,
and
I
didn't
get
as
far
as
I
I
could
see.
I
didn't
get
any
specific
comments
on
that
one.
G
So,
while
you're
showing
it,
I
could
just
give
the
background
so
the
there
was
a
charter
drafted
by
jim
in
a
couple
of
months
ago,
or
a
few
I
mean
straight
after
the
last
itf
meeting.
I
think
that
was
was
drafted
or
maybe
it
was
even
100
itf107,
and
that
charter
was
discussed
last
last
interim
and
then
we
had
some
proposals
over
email
by
john
that
was
discussed
in
in
that
interim,
and
people
were
happy
with
that.
G
Reformulate
one
of
those
sentences,
basically
yeah,
so
there
is
an
old
and
a
new
in
the
mail
I
sent
out
and
the
old
is
actually
after
incorporating
john's
proposed
changes.
So
that
was
what
we
discussed
last
meeting
and
the
news
is
what
I
yeah
okay.
Now
I
see
it
almost
there
is
some
icons.
At
the
left
hand,
side
is
covering
part
of
my.
G
I
don't
know
if
that's
possible
well
anyway,
so
there
is
a
so
so
the
old,
if
you
compare
the
old
and
the
new,
the
old,
the
first,
the
three
paragraphs,
the
first
and
second
last
paragraph
are
the
same
in
old
and
new,
and
the
middle
paragraph
is
replaced
so
emphasizing
that
the
main
objective
is
to
define
this
method
of
compressing
x509
to
meet
a
specific
profile
that
is
lost.
G
Right
so
that's
that's
the
proposal
and
any
comments
are
welcome.
F
So
this
is
hank,
so
I
I
approve
of
this
message
I
think-
and
so
I
like
the
addition
of
the
in
the
new
the
thought
paragraph,
it's
it's
concise,
which
is
very
appropriate.
Also.
I
like
carson's
comment
on
the
native
nature
here
that
it's
probably
basis
to
say
natively
signed.
F
D
G
G
That
is,
we
that
is
sort
of
in
causing
this
compression
to
happen.
So
it's
it's
not
any.
F
Yeah,
this
is
saying
so
I
think
compression
here
was
intended
to
be
a
intuitive
term
so
like
we
are
not
changing
the
structure,
the
semantics
of
the
structure
itself,
if
you're
just
realigning
the
encoding
here,
basically
the
rearranging
the
content,
so
it's
getting
smaller.
So
that
is
why
it's
not
just
a
simple
re-encoding
compression
and
as
a
result,
because
it's
smaller
but
but
effectively.
What
we
do
here
is
a
canonical
transformation.
We
can
transform
it
from
the
bigger
size
into
the
smaller
size
and
then
canonical
reconstruct
the
original
from
it.
F
So
it
also
behaves
like
a
compressed
item
and
we
decompress
it
in
the
end,
but
as
of
course,
we
are
not
using
any
compression
algorithms
here,
it
is
just
a
encoding
effectively.
So
so
that
is
maybe
not
the
best
choice
of
words.
I
think
it
was
chosen
again
because
it
is
an
intuitive
understanding
on
what
this,
what
the
effect
is,
but
it's
not
describing
the
method
very
well.
F
E
So
so
that
would
be
like
taking
the
expiration
field
and
encoding
it
like
in
a
seaboard
type
one
tag
or
finding
some
smart
way
to
encode
the
key
use
in
a
in
an
integer
or
something
that's
a
lot,
a
lot
tighter
and
easier
than
oids
right
right.
That's
that's
the
sort
of
thing
we're
looking
at
right.
G
D
Right
yeah,
I
think
I
have
a
good
handle
on
the
compression
part
and
or
efficient
re-encoding,
whichever
we
want
to
call
it,
and
so
then,
to
get
to
the
sort
of
the
the
native
signing
part.
The
idea
is
sort
of
that.
We
are
going
to
define
this
procedure
for
the
re-encoding
and
then
just
say
in
some.
F
Yes,
the
compression
requires
some
helper
structures
to
enable
this
canonical
reconstruction
and
these
consume
bytes,
because
you
have
to
retain
some
guidance
how
to
deconstruct
the
native
format
native
being
here.
There
is
someone
one
format,
so
you
can
omit
that
by
by
learning
by
basically
using
the
structure
or
reusing
the
structure
that
we
create
here
for
the
air
quote
compression
and
then
take
even
out
the
the
all
the
hyperstructures
that
we
might
need
to
retain
canonical
reconstruction
here
and
then
go
native,
a
native
means.
F
We
are
never
intending
to
reconstruct
a
a
asm1
certificate.
Here
we
can
can
convey
the
same
information
just
with
c
war
and
and
save
fuel
stack
on
the
receiving
end
point
as
one
and
see
where
that
is,
and
also,
therefore,
and
consequently
signed
it
on
on
the
super
level.
F
And
so
that
is
something
that
would
not
require
the
giving
side
to
no
asn
1
at
all.
But
it
would
retain
the
exact
semantics
of
the
certificate
and
the
information
intended
to
be
conveyed
by
the
certificate
right.
C
Whether
you
need
to
be
able
to
have
the
efficiency,
encoding,
irreversible
is
kind
of
orthogonal
with
whether
you
want
to
do
native
signing.
So
there
are
different
reasons
you
want
to
do
native
signing
so
that
a
constrained
device
can
can
check
the
signature
without
going
back
to
the
you
want
to.
C
C
But
as
soon
as
you
don't
have
a
signature,
you
no
longer
need
to
have
the
encoding
reversible,
and
this
is
what
what
hang
and
do
that.
You
then
can
leave
out
a
little
bit
of
of
the
technically
redundant
information
that
is
only
needed
for
the
reversible
recording.
D
I
I
guess
I
one
thing:
I'm
I'm
trying
to
get
in
my
head
is
the
that
we
are
trying
to
have
a
lot
of
overlap
and
sort
of
commonality
between
the
mechanism
that
preserves
the
der
signature
and
the
mechanism.
D
That
applies
a
native
cozy
signature,
so
that
in
some
sense
we
can
be
calling
it
the
same
body
of
work
just
with
different
sort
of
flavors
or
variants
for
the
different
use
cases,
because
I
think
that
will
be
an
easier
thing
to
sell
to
the
isg
than
saying
we're
going
to
do
two
similar
but
different
things
that
don't
necessarily
have
intrigues.
For
that.
F
Ben,
thank
you.
That's
exactly
the
point.
So,
if
you're
doing
the
the
more
efficient
encoding,
this
is
basically
80
to
90
percent
of
the
work.
If
you
would
do
the
native
signing
and
we
don't
have
to
reconstruct
things
side
of
the
coin,
so
there's
a
lot
of
synergy
here
and
it's
not
only
the
overhead.
It's
also
the
the
semantics
that
we
create
here.
So
the
the
lessons
learned
how
to
encode
more
efficiently
would
apply
to
both
tracks
of
this
coil,
both
sides
of
this
coin.
I
think
exactly.
A
A
D
D
A
Take
advantage
of
of
the
code
and
like
the
footprint
and
memory
efficiencies
of
code
of
cozy.
E
F
A
All
right
any
other.
A
All
right,
no
one's
going
through
grant.
Do
you
think
foreign
company?
Do
you
think
we
could
get
an
update
on
your
proposed
text
to
the
list
and
then
we
can
turn
this
into
a
pr
against
the
against
the
charter.
G
Sure
should
I
ben
do
you
want
to
start
ben
with
with
some
text
and
I
can
incorporate
that
or
should
I
start
making
a
pr.
A
Well,
I
I
have
it
open
on
my
desktop
to
submit
the
to
get
the
pr
and
and
approved
for
the
earlier
text
from
john
matson,
so
I
will
get
that
done
before
the
end
of
my
day.
Here
in
the
us
should
be
available
to
submit
to
open
a
pr.
Just
after
that,
I
think
if
you
can
open
a
pr
directly
in
github,
that
would
be
the
most
efficient.
G
Okay,
so,
but
my
question
was
really
to
ben,
then
ben
is
going
to
propose
some
text.
So
should
I
wait
for
that
or
should
should
ben
and
I
talk
offline
or
how
do
we
collaborate.
A
I
think
we
can
open
the
pr
now
we
can
hold
it
pending
ben's
note,
and
then
we
can
incorporate
that
whatever
way
is
most
efficient.
Okay,
fair
enough.
A
A
All
right
well,
without
that,
I
think
what
we
will
do
is
once
we
have
these
pr's
submitted
and
we
merged.
We
will
send
the
text
around
to
the
working
group
directly
again
and
get
feedback
for
where
we
can
go
depending
on
how
long
it
takes
to
turn
the
this
latest.
Cert
compression
or
get
it
merged
will
be
a
dependence
on
when
what
the
timeline
for
that
is.
A
A
Necessary
so
hopefully
we
can
all
have
that
done
within
the
next
week
or
two
and
we
can
send
that
our
event
to
the
working
group.
One
more
time
now
that'll
be
a
chair
action
to
send
to
send
the
work
to
send
the
charter
around
one
more
time
to
this
working
group
to
see
what
else
needs
to
be
done,
and
then
we
will.
A
I
think
that
actually
is
going
back
to
slides.
Hopefully
those
are
still
rendering
for
people.
A
Okay,
is
there
any
other
business
we
would
like
to
discuss
today?
We
still
actually
have
20
more
minutes
in
our
scheduled
session.
A
All
right
I'll
take
the
silence
because
there's
nothing
else,
nothing
else
to
bring
up
so
with
that.
I
think
we
are
adjourned.
The
next
meeting
that
we
have
would
be
with
itf
109
in
november
schedule.
Still
the
exact
schedule
still
to
be
determined.
A
So
I
guess
we
will
you
all
talk
synchronously
again,
then,
until
then,
we
will
see
our
word
on
the
mailing
list,
any
other
thoughts
from
anybody.
If
not,
we
will.