►
From YouTube: IETF-CELLAR-20211123-2000
Description
CELLAR meeting session at IETF
2021/11/23 2000
https://datatracker.ietf.org/meeting//proceedings/
A
B
A
A
A
A
A
And
there's
a
you
can
raise
your
hand
if
you
want
to
join
the
queue
or
not
so
that's
sort
of
you
don't
have
to
join
the
queue
before
you
turn
your
audio
on,
but
that's
so
so
you
can
you're
you're
allowed
to
run
up
and
grab.
The
mic
is
the
point
you
don't
have
to
be
polite,
but
you
can
be
polite
by
putting
your
hand
up
first
and
then
this
we
almost
never
use
slides
in
this
one.
A
A
A
B
B
B
Cool
and
so
that
gets
us
that
gets
us
down
to
news
you
can
use,
which
was
just
the
no
time
to
wait
coming
up
in
early
december
and
I'm
getting
from
dave
rice,
I'm
getting
emails
about
that
now,
since
I'm
registered,
so
that'll
be
fun
and
let's
see
we
did,
we
did
do
the
final
dates
for
the
2022
seller
meetings.
They
were
approved
by
rit
and
added
the
data
tracker,
so
those
should
all
be
reasonable.
B
Now,
the
one
thing
that
we
is
worth
calling
attention
to
is
that
the
we
do
you
know.
As
usual,
our
november
meeting
was
slightly
complicated,
so
our
in
our
december
meeting
wasn't
going
to
happen
so
we're
having
a
meeting
in
between
basically
the
ietf
in
november
and
the
end
of
the
year,
so
it'll
be
in
early
december.
B
B
A
C
A
A
D
D
E
E
I
don't
know
the
plan
for
now,
I'm
trying
to
get
rid
of
the
rest
of
the
issues
and
pull
requests
merging
things
as
we
go
on,
there's
almost
nothing
left,
there's
still
some
probably.
I
will
work
on
that
in
december
and
after
but
even
now
we
can
start
reviewing
because
it's
going
to
take
a
long
time.
I
think.
A
E
E
E
B
A
I
don't
know,
I,
I
don't
think
it's
2022.,
I
don't
know
what
the
right
answer
is.
So
I
think
the
question
is:
are
we
trying
to
advance
matraska,
ffv1
or
flack?
First,
I
think
we
where
we
want
to
do.
I
think
we
want
to
do
matraska
first,
but
I
think
it
depends
also
on
you
know
we
have
limited
number
of
people
and
they
are
all
working.
A
B
A
E
A
D
A
B
A
One
issue
I
have,
I
think
I
have
with
you-
know
people
reviewing
matraska
right.
So
we
have.
I
don't
know
how
many
here
I'm
trying
to
get
to
the
bottom.
You
know
we
have
a
lot
of
content
in
you
know,
chapter
eight
schema
and
it's
pretty
hard.
I
would
say
it's
pretty
hard
for
people
who
aren't
implementing
to
have
any
particular
comments
on
that
and
you
know
then
we
have
the
other,
the
other,
the
rest
of
the
document
right.
So
all
I'm
trying
to
say
is
that.
B
Right
the
thing
that
that
people
could
be
telling
us
can
we
understand
it,
do
we
can
we
imagine
that
we
could?
Can
we
imagine
that
we
could
implement
it?
You
know,
basically
they
they
may
not
be
able
to
provide
the
detailed
review
that
somebody
who's
implementing
it
could
and
that's-
and
you
know,
and
that's
that's
kind
of
what
ietf
review
is
shooting
for
after
that.
A
E
A
Think
we
have
a
shorter
well,
we
might
put
it
in
the
form
of
a
table,
but
anyway,
there's
some
stuff
here
to
discuss
about
about
the
different
about
what
are
the
things
that
matraska
creates
and
not
so
I
guess
spencer
and
I
need
to
read
that
and
provide
some
feedback
as
to
ayanna
considerations.
Language.
I
don't
quite
understand
part
of
it.
So.
A
A
Probably
some
allocations
that
we
haven't
documented
there.
That's
the
rest
of
the
file
right.
So
that's
what
I'm.
I
think
we
have
to
be
sure
that
we've
gotten
correct,
as
is
the
piece-
and
I
think
that's
the
part
that
that
the
implementers
don't
don't
have
as
clear
a
view
of
of
to
what
the
iana
is.
B
B
A
E
B
B
A
B
A
B
A
Martin
did
yeah,
so
martin
did
start
a
anew
and
I
would
say
that
at
this
point
we're
in
a
position
with
a
good
position
where
we
could
mix
and
match
as
we
wished,
and
I
I
haven't
looked
at
your
work
yet
martin,
so
I
don't
know,
I
don't
know
whether
it's
better
worse
happier.
You
know,
I
have
no
idea,
you
may
just
prefer
it,
but
the
point
is
that
you
don't
have
to
worry
about
whether
or
not
you
want
to
go
and
take
text
from
the
previous
document.
C
C
So
the
email,
in
my
opinion,
is
enough.
Yeah,
it's
enough
and
we
are.
We
are
pretty
confident
that
the
original
author
is
fine
with
what
we
do.
So
I
like
that
the
email
was
very
positive,
so
maybe
we
can
merge
that
and
after
that
we
pick
from
martin
interesting
parts
when
we
don't
need
to
to
to
rewrite
everything.
So
we
can
pick
a
paragraph
part
per
paragraph.
D
A
I
really
think
we
should
mix,
I
think,
yeah.
I
don't
think
you
need
to
prefer
it.
So
I
think
it's
a
really
good,
actually
a
really
good
thing
to
have
gone
through
and
done
that,
because
you
know,
if
nothing
else,
it's
probably
rewrites
are.
Usually
you
usually
improve
things
right,
but
so
I
would
say
I
just
encourage
you
guys
to
to
pick
and
choose
whatever
pieces.
You
want
and
you
know,
go
forward
right
and
maybe
we're
close
to
done.
I'm
not
sure
on
that.
I
haven't
looked
at
the
document
very
much.
C
C
D
D
C
A
D
A
Don't
know
what
info
you
you
want
to,
you
don't
have
to
put
your
your
street
address.
I
usually
don't
I
just
put
my
company
in
my
country
and
it's
useful
to
have
the
country
because
we
have
stats
somewhere
about
where
people
come
from
yeah.
I'm
fine
with
that,
and
I
don't
have
any.
I
don't
if
anyone
wants
to
know
my
street
address
it's
already
in
google,
but
I
don't
need
to
I
don't
need
to.
A
A
C
A
C
B
A
Yeah,
I
would
agree
with
that.
That
would
be
the
major
major
difference
at
this
point.
He
we
can
list
him
as
a
major
contributor,
but
if
it's
going
to
be
hard
to
get
a
hold
of
him
during
auth48,
then
it's
just
a
hassle
for
us
to
get
through
things.
He's
he's
he's
yeah.
I
think
we
should
you
know
if
he
wants
to
be
involved.
We
should
welcome
him
but
yeah.
I
I've
merged
that
pull
request
with
the
license.
I
I
up
arrowed
it.
B
B
B
C
E
C
C
A
B
B
E
B
E
A
E
E
B
B
B
B
E
B
A
C
All
is
there,
so
why
not
being
there
so
for
a
multitasker
plant,
but
in
any
case
we
do
the
remote
part
as
every
year.
It
is
just
that
the
remote
part
will
be
used
more
than
usual
right,
exactly
at
least
there
will
be
some
people
on
site
for
sure,
except
if,
if
there
is
a
lock
down,
but
for
the
moment
the
log
down
is
only
from
8
p.m.