►
From YouTube: IETF-CBOR-20210714-1400
Description
CBOR interim meeting2021/07/14 1400
A
B
A
B
A
B
And
just
out
of
curiosity
did
any
of
you
put
the
meat
echo
captures
attendance
note
into
the
into
the
minute,
because
I
don't
see,
who
put
that
there
might
might
have
been,
might
have
been
barry,
but
he
can't
be
here
today.
So
I
can't
ask
him
right
away.
B
B
B
How
do
we
ensure
that
the
list
of
tags
stays
usable
which
comes
out
from
the
earliest
from
the
from
the
other
documents?
B
B
I'm
hearing
none
I'd
like
to
give
a
brief
update
on
where
the
documents
that
are
currently
in
the
working
group
are.
If
they
have
changed
recently,
one
is
cddl
control
which
wasn't
an
extended
working
group
last
call
for
lack
of
for
lack
of
document
reviews
hank
just
provided
one
today,
so,
which
is
largely
positive
with
just
a
few
knits
and
and
texture
remarks
that
I'm
positive
can
be
worked
in
easily,
with
which
I'd
conclude
I'll
conclude.
The
working
group
last
call
positively
so
carson
I'd.
B
Ask
you
to
work
in
anything
that
you
would
like
to
pick
out
of
that
out
of
that
document.
Out
of
that
review
into
the
document,
and
when
that
is
done
and
uploaded
we
can
we
can.
We
can
forward
this
out
of
the
working
group.
B
B
If
you,
if,
if
that
happens
before
during
the
during
the
freeze,
I
can
even
look
at
the
document
as
it
is
being
in
the
editor
copy
and
push
the
button
on
the
shepard
review
on
being
done.
When
the
documented
shepherd
review
reflects.
A
A
B
The
two
documents
network,
addresses
and
file
magic
are
both
in
a
very
similar
shape.
Michael
thanks
for
uploading.
The
latest
versions
before
the
cutoff
is:
are
they
still
from
your
point
of
view
and
a
change
where
you
don't
see
anything
added
to
that
that
that
would
need
to
be
done
further.
C
B
Worse
well
then,
I
I
started
working
I'll
start.
A
working
group
last
call
on
them
for
for
the
duration
of
the
of
for
the
duration
until
the
itf,
unless
any
comments
come
up
here
now
on
the
document,
but
I
don't
expect
any,
but
that
sounds.
C
A
Okay,
so
gustan
seems
to
have
some
some
audio
problems,
so
the
the
reason
I'm
showing
my
slides
the
whole
time
here
is
that
for
some
reason
my
computer
takes
a
long
time
to
actually
start
screen
sharing.
So
a
discussion
that
came
up
was
in
the
context
of
the
network.
Addresses
tags
was
whether
we
would
say
anything
about
the
existing
tags
that
do
something
with
network
addresses
and
that
kind
of
brought
up
the
more
general
issue.
A
A
viable
part
of
of
the
sibo
ecosystem
and
tags
are
pretty
important
because
they
are
the
main
extension
point.
We
also
have
the
simple
values,
but
those
have
only
very
specific
usages
and
actually
so
far
we
haven't
allocated
anything
there
yet
which
might
change
with
seabor
pact.
But
tags
really
are
used
a
lot
and
they
are
a
part
of
the
batteries
included
approach
of
cbo.
A
So
you
are
likely
to
already
find
a
tag
for
what
you're
trying
to
do
at
least
that's
what
most
people
find
and
if
they
don't
find
it
well,
then
they
can
go
ahead
and
register
one
and
it's
a
pretty
easy
process.
So
actually
some
of
the
ranges
are
under.
First
come
first
served
and
it's
a
vast
space,
so
we
are
never
going
to
run
out
of
the
entire
space.
But
of
course,
short
tanks
are
better
than
long
takes.
A
So
we
have
to
be
a
little
bit
careful
about
the
the
space
with
the
short
tanks.
A
So
the
designated
expert
only
sees
the
the
first
32k,
the
the
fcfs
space
actually
began
at
256
with
70
49
and
with
eight
nine
four
nine.
We
decided
to
expand
this
a
little
bit,
so
we
have
a
little
bit
more
control
over
the
oneplus
2
byte
tag
space
as
well,
so
just
to
to
have
a
little
bit
of
a
numeric
foundation
here.
The
the
scars
part
here
is
the
oneplus
0
part
where
7049
allocated
nine
tags,
since
three
more
have
been
allocated
and
there
are
12
free.
A
So
we
we
have
gone
through
half
the
space
here
in
one
plus
one
slightly
less
less
efficient,
seven
tags
were
allocated
with
70
49
57
tags
have
been
registered
since
and
about
170
are
free
in
the
oneplus
2
space
43
have
been
registered
since
1749,
and
we
have
a
lot
to
free
and
the
oneplus
4
and
oneplus
8
space
are
essentially
abundant,
so
we
don't
really
have
to
care
about
that.
A
But
that's,
of
course
not
the
only
problem
we
not
only
have
to
avoid
running
out.
We
also
have
to
make
sure
that
the
tank
space
is
accessible
and
isn't
such
a
disaster
as
the
port
number
space,
where
people
typically
don't
find
ports,
they
they
might
want
to
use.
That's
really
a
rare
accident
if
that
port
isn't
already
widely
used
like
port
80
or
25.
A
Nobody
looks
into
that
registry,
so
we
have
to
think
about
evolving
that
space
as
something
that
that
is
accessible
to
developers,
and
so
what
happened
in
the
first
eight
years
was
that
we
had
this
initial
land
rush
when
when
749
came
out,
so
we
had
tax,
for
instance,
for
the
pearl
community.
A
Later
the
hesker
community
came
in
and
so
on,
and
then,
after
this
initial
land
rush,
we
had
some
some
pretty
steady
growth,
so
people
registered
something
but
also
standards
registered,
something
like
cozy,
cut
and
other
internet
drafts,
which
are
not
yet
standards
like
the
time
tag
which
is
being
used
in
the
haskell,
and
there
also
have
been
a
few
efforts
actually
generating
some
structure
there.
A
So
8746
is
for
array,
shaped
structures,
and
that
is
a
nicely
laid
out,
a
set
of
24
tanks
that
can
be
used
for
this,
and
we
are
trying
to
do
something
similar
with
the
map
like
tags.
So
this
is
where
we
are,
and
I
don't
think
that
there's
anything
that's
completely
going
wrong
here.
Of
course,
not
not
all
tanks
that
have
been
allocated
in
particular
in
fcfs
are
examples
of
wonderful,
great
design,
but
that's
not
necessary.
A
If
somebody
has
a
specific
need,
they
can
just
come
in
register
their
tag
and
and
get
their
work
done.
We
also
have
had
very
little
problems
with
squatting
so
far,
so
take
42
was
the
the
only
tag
where
we
had
squatting
that
we
didn't
notice
when
we
allocated
take42
to
yang
zebo,
and
so
we
had
to
change
the
yang
siwa
to
avoid
the
conflict
between
gangster
and
published
open
source
software.
A
Okay,
so
do
we
need
to
do
any
clean
up
so
that
there
are
tags
that
replace
older
ones,
and
I
think
the
network
address
case
is
the
first
real
case
that
that
is
getting
close
to
working.
Our
last
call
here,
some
tags
complement
others.
So
when
we
defined
tech
37
in
2013,
we
really
just
didn't
think
about
the
fact
that
mime
is
mostly
binary,
so
somebody
went
ahead
and
and
actually
registered
257
in
the
the
first
come
first
served
space
at
the
time.
A
It
would
have
been
much
more
reasonable
to
have
a
single
tag
for
for
both,
so
that
that
also
opens
the
question
whether
we
could
have
fixed
the
tag
37,
but
that's
of
course
difficult
in
a
registry
situation,
and
then
we
have
other
tags
that
simply
extends
previous
one,
so
take
two
to
68
and
just
to
70
are
slightly
more
flexible
numbers
than
the
one
that
have
take
four
four
five
and
something
else
I
forget
so
that
that's
again
a
question
could
we
have
extended
the
the
already
registered
one,
but
we
run
into
a
problem
here.
A
So
if
somebody
comes
in
and
says,
I
want
to
take
a
network
address
right
now
they
find
tags,
5254
and
261
and
essentially
have
no
guidance
which
one
they
should
use.
But
in
that
case
it's
pretty
obvious
that
5254
are
the
preferred
ones
because
they
are
simply
shorter,
but
in
other
cases
it
may
not
be
so
clear.
So
how
does
the
implementer
navigate
this?
A
We
could
put
more
information
into
the
registry
now.
This
first
of
all
requires
a
document
that
that
describes
what
information
we
put
in
the
registry,
but
then
in
particular
it
will
require
continuous
working
group
actions
to
actually
update
the
the
registry.
So
that's
something
we
should
not
do
lightly.
So
if
we
really
want
to
do
this,
it
will
require
some
some
continuous
attention
and
there's
also
a
little
marketing
aspect
here.
A
We
really
should
encourage
people
to
register
something
and
and
not
have
them
register
something
and
then
come
in
as
the
head
teacher
and
say
that
that
gets
an
f
and
we
have
a
better
tank
here
that
you
should
have
been
thinking
of.
That's
really
what
we
don't
want
to
tell
people
so
just
having
a
naked
entry
in
the
registry
not
recommended
or
something
that's,
not
so
nice.
A
So
the
the
approach
that
I
had
in
mind
was
to
create
a
separate,
informative
document
and
the
first
attempt
at
that
actually
exists
as
staff
from
an
seaboard
notably
takes,
and
this
of
course
needs
a
lot
of
love.
I
mean
we
are
back
to
this
thing,
except
that
we
don't
have
to
do
it.
A
We
we
can
update
this
on
our
own
schedule,
and
the
intention
is
to
run
this
as
a
living
internet
draft
for
a
while
and
maybe
actually
publish
this
at
some
point
when
we
think
we
have
a
first
set
of
stabilized
commentary
on
the
tags
that
that
we
actually
can
try
and
say
that
is
the
state
as
of
2025
and-
and
we
want
to
publish
this
so
the
only
thing
we
could
improve
at
some
point
is
to
actually
get
the
registry
to
reference
this
document,
and
that,
of
course,
would
require
some
status.
A
I
don't
know
how
how
flexible
ayanna
is
in
adding
information.
Maybe
we
need
to
publish
something
to
to
make
sure
we
get
this
reference
in
there,
so
that
that's
my
view
of
the
situation.
I
think
it
was
good
that
brian
carpenter
brought
this
up,
but
I
think
we
are
mostly
in
good
shape
here,
except
somebody
would
need
to
find
more
time
to
actually
work
on
this
notable
tax
document.
A
A
I
think
we
don't
have
any
other
chair.
Can
you
chair
from
the
jabber.
B
Let
me
try
this
I
I
was,
I
was
one
very,
very
short
of
just
doing
old,
chia
stuff
from
via
text
like
in
the
good
old
days.
Probably
but
yes,
one
one.
One
rough
comment
only
on
this
is
that
I've,
when
I
saw
the
slides
I've
looked
over
the
the
charter
and
I
think
think
that
we
are
within
the
charter's
range
of
maintaining
the
sibo
ecosystem,
with
both
both
with
changes
to
the
registry
and
with
with
providing
commentary
here.
So.
B
B
Probably
I'm
just
checking
the
so
probably
one
thing
that
will
need
to
happen,
and
that
might
be
a
good
out.
Good
discussion
outcome
for
here
is
to
consider
whether
whether
notable
text
is
at
least
within
from
from
the
scope.
It
has
not
necessarily
from
the
content.
I
read
it
to
be
adopted,
because
then
this
would
be
easier
to
justify
as
a
living
document
that,
to
some
extent
represent
represents
what
is
happening
in
the
working
group
and
then
thus
more
easily
can
be
referenced
from
the.
A
A
B
On
the
on
the
point
of
a
working
of
describing
older
tags
as
not
recommended,
I'm
not
sure
what
the
procedure
is
there,
but
document
tags
registered
with
from
from
outside
itf
usually
have
basically
that
entity
the
reg
the
entity
that
registered
it
as
change
controller
is,
can
can
can
would
they
be
in
a
position,
at
least
theoretically,
I'm
not
sure,
even
from
from
a
normal
point
of
view,
to
withdraw
their
registrations
or
change
their
registrations,
in
that
they
say
that
they
are
not
active,
actively
used
anymore
or
deprecate
them
themselves.
A
Them
yeah
generally,
that's
a
good
question,
but
generally,
I
think
that
that's
not
what
I
would
expect
to
be
the
the
standard
procedure
because
well,
the
the
person
that
did
the
registration
at
the
organization
may
have
moved
on
to
a
different
place
and
so
that
it
may
just
be
difficult
to
to
get
the
random
fcfs
registration
amended.
A
So
I
I
also
I
wouldn't
write
anything
like
not
recommended,
except
if,
if
there
is
really
a
a
bad
flaw,
so
if
the
tag
definition
creates
a
security
problem,
then
maybe
we
want
to
point
this
out,
but
I
think
most
most
tags
that
we
don't
want
to
recommend
really
are
just
suboptimal.
So
there's
nothing
wrong
with
using
them.
But
it's
not
not
in
the
short
list
of
things
that
people
should.
B
B
A
A
B
Now,
yes,
I'm
I'm
sorry!
This
is
I'm
I'm
at
our
campus,
I'm
inside
our
campus
at
a
rome,
and
this
is
occasionally
flaky
I've
I
had
hoped
to
pick
the
best
spot
anyway.
B
B
It
might
be
a
good
idea
if
you
could
find
someone
to
co-author
this
with
you
just
just
to
ensure
that
any
low
that
comes
from
it
can
be
balanced
a
bit
better.
But
I'm
aware
that
in
a
small
working
group
this
might
be
a
difficult
thing.