►
From YouTube: IETF-CBOR-20211020-1400
Description
CBOR meeting session at IETF
2021/10/20 1400
https://datatracker.ietf.org/meeting//proceedings/
B
B
C
Yeah
yeah
there's
peter,
it
is
a
little.
I
think
we
need
to
make
a
feature
request
to
the
meet
echo
people
to
put
the
jabber
users
at
the
bottom,
so
that
we
can
easily
see
who
the
actual
participants
are.
D
C
E
Let
them
put
it
in
alphabetical
order,
probably
need
a
mode
which
is
participants
first,
and
we
also
need
a
mode
which
is
recent
speakers.
First.
A
C
B
C
Anyone
who's
been
in
many
meetings
with
warren.
Kumari
knows
how
important
it
is
to
cut
out
the
the
babble
at
the
beginning.
C
Yeah
warren
is
quite
a
character
and
it's
fun
to
to
chat
with
him
before
the
meeting,
but
it's
not
relevant
to
the
meeting
so
yeah
anyway.
C
Well,
we
have
the
we
have
the
usual
suspects
on.
So
I
suppose
we
can
go
ahead
and
get
started.
Yeah
yep.
B
B
The
current
agenda
is,
as
always,
in
the
minutes
being
prepared,
so
please
come
in
there
and
also
add
to
the
minutes.
If
you
find
the
free
time
there,
two
documents
are
in
the
working
group.
Currently
that
should
be
discussed
today
and
one
is
zebra
networking
address,
network
addresses
which
has
been,
which
has
its
discusses
clear.
So
this
should
manage
to
move
forward
and
see
profile
magic,
which
I
kind
of
a
lost
track
a
bit
as
a
shepherd.
B
So
this
I
think
this
can
go
ahead.
We'll
talk
a
bit
more.
There
frank,
carson
added
the
topic
of
a
new
request
that
came
to
him
and
me
as
the
export
experts
on
the
registry
for
registration
from
outside
the
itf
on
one
oneplus
one
tag
and
then,
if
there's
no
any
other
business,
the
only
thing
left
is
to
remind
everyone
that
cutoff
is
imminent
and
where
we'll
meet
again
comments
and
topics
that
people
would
like
to
bring
up
now,
so
that
we
can
plan
ahead
for
them.
A
I
just
wanted
to
let
the
working
group
know
the
authors
already
know,
but
the
seaboard
network
address
has
a
discuss
that
should
be
cleared,
meaning
I
have
to
ping
murray
to
get
him
to
remove
his
discuss
and
I
plan
to
do
that
tomorrow,
so
it
should
be
approved
tomorrow.
B
Yeah
on
on
the
topic
of
of
network
addresses,
yeah
francesca
basically
said
the
things
that
I
got
wrong.
So
is
there
anything
left
that
we
should
discuss
here
and
are
there
any
comments
that
we
that
should
be
brought
up,
I've
briefly
skimmed
through
them,
and
I
found
nothing
that
doesn't
look
like
it's
on
the
right
track.
A
And
I
have
to
correct
myself:
I
was
thinking
of
a
chord
document,
so
never
mind
that
one.
There
is
no
discussions
and
I
just
have
to
check
with
ben
on
this
document.
A
But
if
I
don't
get
any
answer
then
yeah,
then
it's
on
me
to
to
go
through
the
the
thread,
and
I
haven't
done
so
yet
because
yeah,
it's
it's
a
bit
split.
So
it's
a
bit
hard
to
to
follow,
but
I'll
do
that
as
soon
as
possible.
C
B
Okay,
if
we
don't
have
any
more
documents,
we
can
confuse
this
with
I'd
go
over
to
find
file
magic.
This
has
been
sitting
in
a
working
group.
Last
call
for
actually
a
few
months
now,
mainly
because
there
was
a
bit
of
a
lack
of
in
working
group
reviews
more
precisely.
I
missed
that
john
provided
the
review,
so
the
delay
is
probably
on
me.
B
I've
looked
through
the
reviews
that
have
come
in
both
from
from
john
inside
the
working
group
and
from
vanderboba
from
as
has
been
requested
as
an
as
an
art
review
and
a
few
comments
from
from
dale
on
inside
that
thread,
and
to
me
it
looks
very
much
like
there
is.
The
idea
is
a
typical,
weak
support,
but
no
objections
to
the
document.
B
So
if
no
yeah
cousin.
G
G
So
we
had
a
lot
of
brownian
motion
and
and
that's
great
and
the
document
is
better,
but
what
we
haven't
actually
done
is
the
the
last
round
of
editorial
gaming
and
we
probably
need
to
find
two
hours
or
so
before
monday
to
actually
do
that
and
and
finish
a
version
that
we
actually
can
sent
to
the
isg.
B
B
Okay,
either
way
with
the
with
the
state
of
the
comments,
I
think
that
we
can
conclude
the
working
group
last
call
positively.
B
You
still
do
your
update
and
then
I'll
update
the
shutter
right
up
as
soon
or
I'll
finish
the
shepard
right
up
as
soon
as
you
have
that
version
uploaded.
B
E
B
Well
then,
next
item
on
the
list
is
the
the
capture
registration
request,
a
customer.
You
want
to
say
a
few
words
there
or
shall
I
summarize
the
the
state
of
what
they
are
doing
and
then
you
go
on
to
why
you
think
it's
a
good
idea.
Please
do
okay,
so
the
capture
document
is
asking
for
and
I'm
posting
the
link
in
the
chat
again,
it
is
describing
a
way
to
is
describing
a
tag
that
indicates
that
that
what
is
tagged
is
a
group
of
positional
and
keyword
arguments.
B
Many
programming
languages
have
a
way
of
giving
arguments
to
a
function
that
says
argument
one
argument
to
argument
three
and
then
go
over
to
indicating
explicitly
more
of
the
some
of
the
more
exotic
arguments,
so
that
might
be.
They
probably
have
a
better
example
than
I
can
come
up
with
on
on
short
notice
that
can
be
x,
y
and
z,
coordinate
as
positional
arguments
and
then
a
boolean
argument.
B
Whether
or
not
this
vector
is
to
be
normalized
that
that
kind,
that
kind
of
arguments
the
tag
they
introduce
says
that
the
payload
of
the
tag
is
a
two
element
array.
The
first
element
is
in
the
first
element
of
that
is
an
array
of
positional
arguments,
and
the
second
is
a
map
of
a
keyword
of
keyword
arguments,
and
this
is
common
through
several
languages,
and
they
describe
that
they
like
to
use
it
also
in
situations
where
they
have
a
bit
of
more
volume
of
data
coming
through.
G
G
So
there's
little
question
that
this
is
a
useful
tag.
Calling
it
capture
is
maybe
a
little
bit
specific
to
the
platform
it
came
from.
I
forget
what
what
platform
it
was.
It's
one,
I'm
not
using
all
the
time
but
yeah.
G
If
it's
what
what
they
are
going
to
use
first,
maybe
they
get
the
right
to
to
name
it
and
so
that
that's
okay,
whether
it's
one
plus
one
or
one
plus
more,
depends
a
bit
on
on
how
you
actually
use
it,
and
if
you
look
at
procedure,
calls
in
in
many
environments
these
often
have
pretty
short
arguments.
G
So,
even
if
it's
not
a
constrained
environment,
it
may
be
worth
saving
that
bite.
But
it's
not
a
strong
argument
for
for
going
for
one
plus
one.
I
think
it's
a
borderline
and
I'm
a
little
bit
on
the
side
of
saying.
Okay,
that's
a
legitimate
request
from
a
specific
platform
that
is
not
entirely
exotic,
so
maybe
we
should
go
for
it.
On
the
other
hand,
maybe
we
should
have
another
planning
session.
G
How
many
tags
are
we
spending
out
of
which
space,
and
is
it
maybe
time
to
to
restrict
the
flow
of
tags
a
little
bit,
or
can
we
actually
be
more
liberal?
That's
maybe
one
one
metal
thing
we
we
should
be
doing
so.
Let
me
just
pull
up
the
numbers
here.
G
So
in
in
the
cody
md
I
have
put
in
my
tag
report
and
we
see
that
we
have
used
up
26,
27
percent
of
the
oneplus
one
range.
We
have
several
proposals
out
there.
That
would
take
sizable
chunks
out
of
that,
so
we
may
be
up
to
40
within
a
year
or
so,
for
instance,
zebra
practice
is
actually
using
a
sizeable
chunk
of
oneplus
one
tags,
but
we
we
haven't
even
reached
50
percent
and
and
we
we
are
close
to
to
the
the
10-year
milestone
for
sibo.
G
So
it's
not
like.
We
are
over
spending
at
the
moment,
but
of
course
yeah.
There
are
only
170
bullets
we
have
left
so
yeah
is
this
one
of
those
170
that
that's
really
the
question.
B
In
the
discussions
that
you
had
with
the
authors,
did
the
topic
come
up
of
whether
this
would
be
a
case
where
an
application
would
already
know
from
the
context
anyway?
What
is
in
there
and
does
not
always
use
the
tag.
B
That's
definitely
something
we
can
and
should
do
so
just
for
for
kind
of
to
get
a
bit
of
more
more
input
to
the
to
that
usage
constraints.
B
Do
any
and
do
people
around
the
group
have
the
impression
that
we
might
run
run
short
of
tags
due
to
due
to
registration
that
they
are
aware
of,
but
have
not
been
filed
yet
like
do
you
have
projects
in
the
pipeline
where
you
would
want
another
chunk
of
the
oneplus
one
space
or
just
have
a
expect
to
register
a
few
more
over
the
last
over
the
next
years.
G
Yeah
there's
one
one
more
proposal
which
is
coming
from
the
I
think
cascary
community,
some
functional
language,
where
they
essentially
need
a
tag
to
differentiate
between
different,
otherwise,
structurally
identical
data
structures,
and
they
are
definitely
going
to
use
the
use
these
tags
on
the
wire.
So
that's
the
place
where
the
the
answer
to
christian's
question
would
be.
G
Yes,
it
makes
a
difference,
and
so
the
main
question
there
is
how
many
oneplus
one
tags
do
they
actually
need,
because
at
some
point
of
course,
the
the
likelihood
of
a
data
structure
being
used.
I
mean,
if
you
don't,
really
need
one
for
15
different
structures.
So
at
some
point
they
can
go
to
a
one
plus
one
plus
two
and
that's
actually
what
the
the
current
proposal
does.
G
So
that
that's
one
thing
I
I
really
need
to
get
to
to
to
complete,
because
the
discussion
has
been
out
there
for
a
while,
but
it's
an
obvious
thing
that
that
makes
sense
in
a
language
where
you
would
have
the
the
compiler
assigned
numbers
to
these
different.
G
B
B
We
have
a
slot
on
thursday
1430
utc.
B
There
is
the
submission
cutoff
in
five
days
from
now,
so
everyone
who
wants
to
update
their
documents,
please
be
aware
of
this
and
into
rims.
We
will
resume
only
after
itf-112
and
there
we
should
coordinate
a
bit
with
the
other
groups
that
also
have
two
bi-weekly
interims
core
is
planning
to
do
theirs
around
february.
Second
plus
minus
all
of
14
days.
B
B
So
that
is
freshly
asking
for
conflicts
that
we
should
consider.
That
would
make
it
difficult
to
up
to
to
keep
using
the
1600
central
european
time
slot
that
we
have
right
now.
G
Yeah,
while
people
are
checking,
do
we
really
have
to
wait
for
february.
G
B
Mapped
this
back
yet
through
the
calendar
down
to
down
to
december
and
yet
january.
This
is
just
the
kind
of
the
representative
of
the
of
the
of
the
day's
model
of
14
days.
H
D
D
D
F
G
A
Unfortunately,
I
cannot
look
at
the
previous
at
the
calendar
for
previous
meetings
only
before.
E
So
I
owe
off
having
regularly
meetings
today
even
and
taps
is
today
and
my
impression
is
there's
a
couple
other
working
groups
that
are
intend
to
do
that
kind
of
pattern.
A
E
A
Too
yeah
I
know
the
usual
suspects,
but
I
don't
know
so
it's
good
to
know
like
those
that
I
like
in
other
areas.
For
example,
I
don't
really
follow
sean.
You
were
saying
sorry,
I
didn't
understand
you.
H
C
G
Yeah,
so
I
think
ipwan
has
had
regular
meetings
for
a
while,
but
not
bi-weekly,
and
we
may
also
consider
going
to
to
a
four-week
cadence,
with
which
I
mean
during
the
holidays.
That's
that's
a
natural
outcome
anyway,.
A
There
are
some,
not
this
working
group
but
other
working
groups.
I
see
they
schedule
on
top
of
each
other.
So
it's
it's
good
that
we
don't
do
that,
but
yeah.
It's
not
a
given,
apparently
that
the
chairs
check
that
so
yeah.
G
B
I
agree
we
should
consider,
especially
given
that
we've
completed
the
last
some
of
some
of
the
more
recent
meetings
in
about
half
an
hour,
so
yeah
be
careful.
G
B
Here
is
that
we
kind
of
keep
the
calendar,
keep
the
calendar
slots
occupied
for
the
bi-weekly
meetings,
but
if
it
turns
out
that
for
some
time
we
keep
we
keep
under
using
the
hour,
and
I
think
it's
convenient
it's
convenient
to
bulk
things
up
so
that
we
we
don't
have
too
much
say
message
overhead
in
in
terms
of
joining
meetings,
etc.
B
Then
we
could.
We
can
start
skipping
some
of
these
meeting
meetings
if
the
pressure
of
things
to
discuss
goes
under
some
low
water
mark
and
still
be
prepared
to
go
to
a
bi-weekly
cadence
as
soon
as
things
come
up.
C
D
H
Down
it's
it's
mostly
like.
Maybe
you
could
go
30
minutes
supposed
to
an
hour,
but
it's
better
probably
to
have
an
hour,
blocked
off
and
be
shorter,
because
then
people
get
free
time,
as
opposed
to
like
oh
we're,
going
to
run
longer,
because
people
will
just
schedule
in
the
other
30
minutes
and
as
as
barry
and
others
have
said.
Moving
the
work
forward
is
the
important
part.
B
Good,
I
see
someone
typing
typing
up
one
more
item
for
the
agenda.
A
I
just
wanted
to
remind
working
group
that
on
tomorrow's
standard
chat,
the
cd
cdl
control
document
is
scheduled
and
it's
all
green.
So
far.
So
that's
great,
but
there
is
a
number
of
people
who
haven't
commented.
Yet
ben
is
one
so
so
we'll
see
what
happens,
but
we're
also
in
is
to
retreat
virtual
asg
retreat
this
week.
So
we're
all
a
bit
slow.
A
But
yeah
this
is
we'll
have
some
update
tomorrow.
G
Yeah
I
like
ira's
pointer
to
the
the
crossword
work
and
so
on.
There's
lots
of
stuff
using
sibo
in
in
various
places
and
having
something
like
like
a
sibo
state
of
the
union.
Occasionally
is
maybe
something
we
should
be
planning
for.
So
we
have
a
standing
item
using
other
seos,
but
we
don't
have
an
item
using
our
own
seo
and
we
probably
should
start
doing
that.
B
D
The
wrong
buttons,
sorry
cddl,
just
as
a
data
point
hank
burkholtzer,
burkholtz,
injected
a
really
good
topic
in
last
week's
trusted.
Computing
group,
virtual
face-to-face
and
we
diverted
our
usual
joint
session
with
global
platform
and
the
mobile
work
groups
in
tcg.
D
Pretty
much
entirely
to
a
discussion
of
work
towards
a
cddl,
idl
and
integration
possible,
with
multiple
build
tools,
compilers
etc.
And
we
thought
it
would
be
an
interesting
topic.
And
maybe
we
would
get
more
than
our
usual
five
or
six
people.
And
instead
we
got
19
and
we
had
people
from
five
sdos
and
from
mitre
and
from
microsoft.
Research.
People
who
don't
usually
show
up
at
tcg
meetings.
D
And
I
wanted
to
say
that
there
is
a
great
deal
of
interest
in
an
improving
tool
chain
for
seabor
and
cddl
for
a
number
of
projects
in
other
sdos.
D
G
Yeah,
that
was
the
the
activity
I
was
not
talking
about
because
it's
officially
confidential
but
yeah.
There
is
a
lot
of
force
right
at
the
moment.
Moving
things
forward.
B
B
B
Okay
with
that,
I
think
we're
done
today.
Thank
you,
everyone
for
your
input,
your
approach,
your
work
on
the
document
and
looking
forward
to
seeing
you
in
virtual
original
we're
actually
anyway
at
itf
112.