►
From YouTube: IETF-CELLAR-20220329-1900
Description
CELLAR meeting session at IETF
2022/03/29 1900
https://datatracker.ietf.org/meeting//proceedings/
B
Michael
said
michael
said
he
was
coming
along.
I
did
see.
I
did
see
him
in
person
last
week,
so
this
is.
That
was
a
rare
treat
I'm
here.
He
is
not
a
hologram
hi,
michael
hello,.
C
How's
life:
no,
I
just
got
back
yesterday.
D
I'm
just
still
I'm
just
still,
you
know
jet
lag.
That's
all.
D
B
Yeah
my
my
favorite
thing
with
the
weirdness
from
last
week
was
me
going
to
europe
and
finding
all
the
websites
I
use
every
day
suddenly
needed
my
consent
to
do
things.
D
D
American
websites
can't
be
bothered
to
comply,
so
they
a
lot
of
them.
Just
don't
allow
access
from
europe
oh
perfect,
including
the
us
government
websites,
apparently.
B
D
B
D
B
D
Basically,
I
mean
there's
only
so
many
direct
flights
to
montreal
and
I
didn't
want
to
take
an
indirect
flight
because
of.
D
The
concern
about
the
rules
being
different
in
different
places
and
and
if
I,
while
there
was
a
direct
flight
on
saturday,
it
would
be
a
direct
flight
which
would
then
arrive
in
in
montreal
and
I'd
be
unable
to
get
back
to
ottawa
because
there
isn't
a
train
on
saturday
that
late.
D
B
And
I
should
be
able
to
remember
how
to
do
chat
because
we
were
practicing
just
last
week.
B
Yeah
now,
since
we're
having
this
conversation,
where
does
this
one
think.
D
B
And
I'm
not
missing
anybody
christian,
I
think
christian
is
a
jabber
user
who
has
been
logged
in
since
we
used
our
jabber
room
since
for
the
meet
echo
or
sorry
for
the
media
media
over
quick
side
meeting
like
in
last
summer.
B
F
F
G
A
B
And
I'm
putting
I'm
putting
question
marks
at
the
front
of
these
that
he
had
asked
for,
and
we
will
know
to
skip
past
those
if
he
has
not
joined
okay,
great.
B
B
In
the
right
place-
and
we
have
some
attendees,
so
that's
good
draft
meeting
draft
meeting
minutes
are
from
actually
from
february,
because
we
had
a
very
small
group
of
people
who
were
able
to
find
the
meeting
last
month.
Does
anybody
need
to
review
those?
B
Cool
we'll
do
this
no
objections.
B
Excellent,
our
work
group
documents
that
yeah
that
should
probably
be
document
status
here
then
our
our
document
status
has
not
changed,
because
I
think
several
of
the
documents
were
waiting
on
things
that
we
were
going
to
talk
about
last
month,
so
that
and
then
we're
still
waiting
for
ffv1-2.
B
Before
we
send
anything
to
dispatch
and
we're
still
waiting
for
matraska
to
finish
up
before
before,
we
do
anything
with
a
ebml
updates
on
draft.
This
is
roughly
the
agenda
that
I
had.
B
Come
up
with
very
quickly
before,
just
before
the
just
before
the
meeting,
so
that's
kind
of
where
we
are
now
so
one
of
our
one
of
our
topics,
which
we've
talked
about
from
time
to
time
on
the
mailing
list
was
whether
flac
should
be
standards
track
or
informational,
and
I
would
like
for
us
to
go
ahead
and
nail
that
down.
B
B
So
where
I
think
we
are
on
this
is
that
we
were
trying
to
figure
out
whether
we
were
going
to
change
the
whether
flack
was
informational
or
standards
track
at
the
last
at
the
last
meeting,
and
we
talked
we've
talked
about
it
a
bit,
but
where
I
think
we
are
right
now
is
that
we
have
decided
not
to
change
it
to
informational
unless
we
needed
to.
D
B
So
we
just
do
need
to
push
the
push
that
pr
yeah
does
anybody?
Does
anybody
have
the
a
body
shares?
Have
a
have
a
pr
number
handy.
B
Okay,
great
so
we
can
say
close
close
for
now.
B
And
thank
thank
you
all
for
the
discussion
about
that.
That
is
actually
something
that
sort
of
matters,
especially
with
a
document
like
flac,
see
if
we
are
skipping
down
to
pushing
matraska-09
and
submitting
it
for
a
review
to
the
higher
powers,
which
is
the
best
agenda
item.
I
think
I've
ever
typed
in
this
working
group
did
we
have
any
discussion
for
that.
A
B
A
Basically
yeah,
I
finished
all
the
merging
everything
I
could
resolving
all
the
issues
that
were
left
about
some,
not
very
important
things.
There's
only
one
issue
left,
that's
unrelated,
so
I
think
it's
okay
to
publish
version
nine.
I
was
actually
going
to
do
it
like
two
weeks
ago,
but
the
window
to
send
xml5
was
close
for
some
reason.
A
B
Cool,
so
we're
ready
to
push
that
one.
A
C
B
If
you,
if
you
have
any
problems,
give
us
a
buzz
actually,
if
you
want
to
do
that
on
the
call.
D
So
the
submissions,
the
submissions
get
closed.
The
submission
system
gets
closed
for
two
weeks
prior
to
an
ietf
meeting,
so
we
just
which
was
last
week.
So
that's
why
it
was
closed
for
most
of
march,
but
it
opened
again
a
week
ago,
like
the
beginning
of
the
meeting
it
opens
again,
which
is
initially
people
were
weird,
but
it's
because
people
want
to
be
able
to
do
revisions
based
upon
the
the
meetings
that
happen
immediately
so
yeah.
D
So
just
be
aware,
you
know
we
can
let
you
know
there's
when
the
meetings
are
but
yeah,
so
you
actually
should
be
able
to.
I
think,
with
the
make
file
there.
I
think
you
can
do,
there's
a
make
submit
or
make
publish
or
you
can
upload.
You
can
just
use
a
web
interface
to
upload
it
to
the
data
tracker.
A
B
A
B
The
only
the
only
instructions
I've
ever
seen
about
that
we're
doing
it
in
in
github
and
github
and
unix,
or
something
the
command
line.
Interface.
B
Well,
let
me
let
me
let
me
ask
one
more
question
on
this
one
and
then
go
down
to
kodak
and
tags.
Michael.
D
B
B
Because
seller
has
a
in
matraska,
I
have
a
fan
club
outside
the
ietf.
Do
we
should
we
be
announcing
that
anyplace?
Besides
the
mailing
list.
A
A
Are
you
want,
I
don't
know,
should
we
send
something
to
the
mailing
list
or.
B
No,
no,
I'm
not
you're
you're
you're,
fine
right
now,
I'm
just
I'm
just
asking
the
next
steps.
So
this
next
step
is,
we
would
say:
has
anybody
in
the
working
group
got
anything
that
they
need
to
say
about
this
draft
before
we
request
publication
and
send
it
to
the
area
directors
so
yeah?
So
what
I'm
asking
is?
B
Is
there
a
reachable
community
that
we
should
send
a
note
to
about
that
and
you
could
just
forward
our
last
call
now
our
working
group
last
call
email
to
them
and
say
this.
You
know
this
is
these
are
the
dates,
and
this
is
when
it's
happening
and
stuff
like
that.
A
Well,
as
they
said
in
the
chat
we
can
send
on
the
metro
schedule
mailing
list,
although
it's
mostly
dead,
the
fm
pack
developer
list,
which
is
the
opposite
of
dead,
it's
way
too
busy.
So
it
might
be
unnoticed
and
yeah.
I
don't
know
where
else.
A
F
I
think
sending
to
the
fm
ffmpeg
list
would
be
fine
but
yeah,
as
you
say,
it's
way
too
hot.
Perhaps
people
will
notice.
A
A
D
A
G
If
shifted
like
three
oak
tufts
down-
oh
that's
even.
D
A
D
B
Okay,
cool
so,
and
that
that
was
just
is
it
was
that
jerome.
H
B
Cool
so
where
we,
where
we
were
on
that,
was
me
asking
if
it
was
appropriate
to
do
a
working
group.
Last
call
for
more
than
two
weeks
since
we're
asking
for
help
outside
the
idf.
B
Michael
does
that
sound
right,
so
you
say
that
again,
please
we're
doing
working
group
last
call
which
could
be
two
weeks
but
we're
asking
for
help
outside
the
ietf.
D
Yeah,
I
think
we
should
probably
set
it
to
four
weeks
just
because
of
the
the
pace
of
things,
and
we
should
probably
send
a
reminder
after
two
weeks
and
we
might
want
to
link
a
little
bit
because
we're
going
to
post
this
message
outside
the
itf
we
might
want
to.
B
B
And
so
okay
sounds
good,
so,
okay,
and
so
I
think
that
takes
us
down
to
codec
and
tags.
B
No,
let
me
let
me
share
something
soon,
as
I
remember
how
yes
this
and
yes,
I
guess
I
really
want
to
share
a
screen,
and
I
wanted
to
share
that
screen.
Yes,
okay,
cool,
okay,
so
that
takes
us
down
to
codec
and
tags.
B
And
there
were
a
couple
of
there
were
a
couple
remarks
about
that
further
down
in
the
thread
about
proper
references
to
the
renamed
element
and
asv3
codec
and
tags
have
the
new
tw
twdb2
tag?
B
B
B
Yeah,
you,
oh
no,
I'm
sorry
go
ahead.
H
F
B
B
Okay,
let
me
ask,
let
me
ask
that
question
so
the
go
ahead.
I'm
sorry.
B
So
I
was
looking
at
the
first
line
and
the
minutes
under
published
codec
and
tags,
and
I
was
asking
if
those
items
that
were
listed
on
that
first
bullet
have
a.
If
those
are
anything
about
updates
that
need
to
be
applied
before
we
would
put
out
008.
A
B
Similar
almost
perfect,
so
did
you
hear
the
question
whether
we
need
to
apply
any
more
updates
before
we
publish
dash
8
for
codec
and
tags.
A
B
Well,
there's.
A
D
D
Rushing's
sake,
but
let's
not
wait
more
than
a
week
or
something
it
makes
it
really
hard
for
people
to
review
documents
when
they're
not
there.
B
Also,
true
is:
is
there
any
so
if
we're
doing
I,
I
guess,
let
me
ask
the
other
question:
if
we're
doing
working
group
last
call
on
matraska,
will
anybody
want
to
refer
to
these
documents
during
working
group?
Last
call.
D
B
Okay-
and
we
are
so
I
it
would
be
so
I
think
the
right
thing
to
do
is
to
submit
an
update
before
they
expire
or
soon
after
they
expire,
and
I
was
just
looking
at
the
dates,
but
they
they
were
something
like
you
know,
they're,
something
like
the
10th
of
the
month.
You
know
of
april,
or
something
like
that,
and
so
you
know
the
next
week
or
so,
and
we
are
not
working
group
less
calling
these
two
yet
right
or
we
haven't
talked
about
it.
A
B
Okay,
yeah,
then
definitely
you
could
do
that
anytime.
So
we'll
just
we'll
just
publish
these
dash,
eight,
so
they'll
be
available
for
metroscore
reviewers.
B
B
B
H
E
H
Do
we
proceed
about
that
and
by
the
way
I
see
that
for
avi
we
didn't
say
a
codec
id2?
B
B
You
can
either
you
can
either
send
a
note
to
the
mailing
list
and
ask
me
or
michael
to
do
it
or
go
to
the
rc
rc
editor's
website
and
and
submit
you
know,
submit
there
either
either
either.
One
is
fine
with
us
and
if
you
do
it
on
the
rc
editor
website
for
a
working
group
document,
I
we
should
get
notification
from
that.
D
H
So
I
I
don't
get
it
so
we
we
upload
a
new
version
or
no,
we
upload
a
difference
or
no.
D
We
yeah,
so
let
me
share
my
screen.
There,
spencer.
B
D
Yes,
so
what
happens?
Is
you
go
to
the
rrc
editor
website
and
you
click
on
errata
and
it
asks
you
for
which
one,
for
instance,
I
know
this
one
has
errata
and
and
then
you
you
see
what
happens
and
so
effectively
what
you're
doing
is
you're
entering
a
bunch
of
things
and
it
says
section
says
blah
blah
blah.
It
says
this
and
it
should
say
that
and
that's
really
yeah.
E
D
That's
the
only
only
part,
so
if
you
this
was
on
which,
which
rfc
again.
B
D
Yeah,
okay,
so
you
do
9043,
there's
nothing!
You
click
on
report,
new
errata,
904.,
three
report,
new
errata,
okay,
report,
new
errata,
and
then
you
get
a
form
to
fill
out.
Basically,
okay,
okay,
sometimes
there's
an
error
in
one
of
the
formats.
Only
so
you'd
pick
that
you'd
say
which
one,
but
it's
probably
just
going
to
be
text,
and
so
technical
errata
means
that
we've
made
something.
We
said
something
wrong:
okay,
editorial
means:
we've
typed
something
wrong.
H
D
H
Okay,
so
what
we
do
first,
we
will
send
a
pull
request
on
the
ffv
one
web
github
repository,
so
it
is
accepted
by
everyone
and
then
I
we
sent
the
errata
either
day.
For
me,
okay,
yeah.
D
But
sorry
about
that,
I'm
gonna
be
off
now:
okay,
cool.
B
All
right,
okay,
and
so
can
I
say,
steve-
is
going
to
will
enter
errata.
A
F
B
F
B
H
If
you
check
the
ffv1
matrix
ffv1
specification,
I
will
send
a
link.
F
Yes,
okay,
but
the
this
was
specifically
about
the
id
one.
Wasn't
this
the
ffv.
E
H
Is
better
but
for
avi,
for
example,
there
is
no
public
registration,
so
we
just
force
it
to
everyone.
So
what
we
can
do
for
flack
is
just
to
say:
okay,
everyone
use
this
flak
kodak
id.
So
let's
do,
let's
make
it
public
in
the
specification.
Okay,
we
can
see
with
mp4
registration.
It
is
a
long
process
because
they
are
not
responsible.
H
But
first
we
we
can
still
put
that
in
the
flag
specification,
as
we
did
for
everyone
in
matroska.
F
F
Car
there
is
already
an
issue
for
what
does
it
say,
document
mappings
into
containers,
and
there
is
already
a
working
container,
that's
being
it
has
been
implemented
in
firefox
and
probably
others
I
I
think,
ff
and
pack
as
well.
H
B
Okay,
excellent
and
mike,
am
I
capturing
that
correctly
in
the
notes
which
you
all
might
know
if
you're
looking
at
the
notes,
but
if
you're
not,
then
it
would
look
like
this.
H
B
H
So
there
is
no
flag
registration,
but
we
will
ask
to
the
mp4
registration
to
to
register
a
flag
or
kodak
id.
B
B
Perfect
and
so
I'm
just
cutting
and
pasting
that
into
the
into
the
not
there.
B
B
Okay-
and
that
gets
us
through
all
of
our
special
agent
items-
and
we
still
have
14
minutes,
left
just
to
help
me
out
a
little
bit
here.
So
we
would
not
be
having
matraska
discussion
until
after
the
end
of
working
with
last
call
at
this
point
or
are
people
gonna
keep
working
on
stuff.
B
B
Let
me
open
that,
while
we're
still
here
well
we're
all
here
here,
so
I
will
not
get
terribly
lost
and
forget
things,
so
I've
got
a
batroska-9
and
excellent
cool,
so
I
will.
I
will
figure
out
what
to
do
with
that.
Okay,
but
thank
you,
but
thank
you.
Thank
you
guys
for
that
excellent
it'll
take
a
little
poking
around
with
that.
That's
what
they
that's,
what
they
pay
us
for,
of
course,
right,
I'm
kidding!
B
So
is
there
anything
that
we
need
to
talk
about
on
flack
on
this
call.
F
Not
sure
there
are
a
few
issues,
there
are
a
few
there's.
There
are
two
new
issues:
I've
posted
earlier
today
that
need
a
little
discussion,
but
I'm
not
sure
whether
the
working
group
should
discuss
in
this
or
general
people
on
the
flock
mailing
list.
F
I
found
two
shortcomings
in
the
flux
specification
points
where
the
specification
says.
Nothing
and
various
implementations
have
done
things
in
a
certain
way.
F
And
I
think
those
need
to
be
solved
before
the
specification
is
finished,
but
there
are
the
technical.
So
I
I
don't
know
who
should
decide
on
this.
B
No,
I
I
promise
you
I
I
only.
I
only
laugh
because
I'm
still
jet-lagged
so
can
you
give
me
the
issue
numbers
for
the
notes?
Yes,.
H
C
H
F
A
F
A
B
Excellent
and
if
I'm
not
hearing
any
other
things,
we
need
to
talk
about
right
now.
Thank
you
all
for
your
diligence
and
hard
work,
and
thank
you
for
putting
up
for
with
me
after
the
meat
echo
disaster
in
february,
we're
doing
better,
and
I
look
forward
to
seeing
you
all
in
april.