►
From YouTube: CBOR WG Interim Meeting, 2020-03-11
Description
CBOR WG Interim Meeting, 2020-03-11
A
A
B
A
B
A
A
A
B
A
Yeah,
so
maybe
let's
wait
for
that,
but
we
can
still
we
can
still,
since
we
are
here
today.
We
can
still
discuss
about
the
preferred
time
if
we
need
to
choose
the
time
so
that
in
case
we
need
to
choose
a
time
and
it's
first-come.
First-Serve
we
get
a
good
peek.
So
my
proposal
is
to
keep
this
time
because
it
seems
to
work
so.
D
D
D
C
C
C
A
A
C
C
D
A
A
A
B
B
B
B
Trying
to
find
the
right
position
on
the
spectrum
of
on
one
end,
equating
floating
point
integer,
as
just
a
number
tribe
like
Jason
does,
and
on
the
other
and
accepting
that
most
implementations.
Don't
do
that
most
implementations
we
have
today
actually
have
very
separate
floating
point
and
and
integer
words
and
Laurence
has
already
pointed
out,
for
instance,
for
for
each
we
don't
want
to
have
floating
point
times
in
many
cases
and
so
on.
B
B
A
A
B
B
B
A
B
B
Why
Mike's
proposal
currently
has
a
1
plus
plus
2
check,
because
texture
dates
are
longer
anyway,
so
I'm,
sorry
that
I
completely
forgot
about
Jack's
input
there
I
somehow
lost
track
of
that,
but
I
think
York
had
a
pretty
good
proposal
there,
and
given
that
we
need
to
do
something
for
the
driving
license
people
we
I
think
we
now
have
two
options.
One
is
just
register
the
the
tag.
B
B
We
are
in
the
expert
review,
a
part
of
the
tags,
so
I
think
that
that
would
be
an
expedient
way
still
in
a
reasonably
expedient
way
to
solve
the
driver
license
problem,
but
also
doing
something
that
gets
us
a
permanent
solution
to
york's
problem,
which
what
we
see
is
not
just
immature
to
york,
but
others
other
people
obviously
have
as
well.
So.
B
You
don't
have
to
wait
for
another
year
to
do
that.
We
can
do
this
right
away
what
we
don't
have
to
actually
wait
for
for
a
decision,
whether
we
want
to
put
that
into
the
same
document
or
not,
and
so
on.
So
procedurally
I
think
we
should
do
the
textual
and
numeric
version
of
the
date
tag
as
a
new
internet
draft
then
get
the
registration
out.
B
So
in
the
RFC
339
there
is
a
production
called
full
date,
which
is
just
a
year
month
date,
and
there
is
another
production
called
date
time
which
is
built
out
of
old
age
and
the
time
of
day
and
take
zero
references,
the
date
time
production
and
doesn't
allow
using
the
full
date
Russian
doesn't
allow
you
to
leave
off
the
time.
I
see.
Thank.
B
B
D
D
B
The
doors
did
you
see
the
new
version
of
the
freezer
document.
Now
this
has
a
section
that
shows
how
to
put
a
B
and
F
into
a
CD
real
and
it
uses
the
daytime
and
Folgate
productions
of
RFC
33:9
as
examples
ok,
so
we
don't
have
that
a
B
and
F
support
in
CDA.
Yet,
but
in
the
long
run,
that's
I
think
where
we
want
to
be
okay.
A
B
A
A
A
A
B
A
A
A
B
C
G
C
A
B
Yeah,
so
maybe
we
should
combine
this
with
a
quick
State
of
the
Union
on
on
the
seaboard
based
security
work
like
cozy,
and
each
and
and
all
that
we
probably
cannot
go
into
a
lot
of
details
of
the
out.
But
I
think
it
would
be
a
good
thing
to
put
out
a
reminder
that
this
kind
of
work
is
happening
now
are.
D
Like
six
time
sets
also
I
just
wondered
if
you're
getting
frustrated-
oh
no,
there's
three
different
ones,
eight
date,
time
time
and
date
and
I
only
sent
them
once
each
there's
three
different
data
types,
III.
Oh
there's
a
bug
where
everything
says
comes
up
twice
in
the
chat.
This
almost
happens.
It's
not
doing
it
in
mine,
oh
dear.
D
B
E
A
B
A
C
F
A
A
E
A
C
Everyone,
but,
but
if
anything,
I
think
the
Seaboard
working
group
is
among
those
that
could
most
reasonably
cancel
the
in-person
meeting,
because
we
had
so
many
in
terms
and
we're
making
things.
But
there's
working
groups
where
apparently
the
chairs
have
never
actually
interact
with
a
remote
attendee
yeah.