►
From YouTube: IETF-CELLAR-20221028-1200
Description
CELLAR meeting session at IETF
2022/10/28 1200
https://datatracker.ietf.org/meeting//proceedings/
A
A
B
B
E
B
C
E
A
B
Last
time
you
go
talk
to
music
I'm,
just
a
slight
schedule.
Change
Alexander
Alexandria
graciously
moved
his
time
slot
till
450
that
afternoon,
to
give
the
ITF
seller
working
group
a
bit
more
time
for
their
session.
So
that
way
we
will
have
this
for
the
next
45
minutes
and
it
will
be
a
working
group
meeting
we'll
have
people
joining
remotely
Michael
Richardson
will
be
moderating,
but
if
people
in
the
room
want
to
ask
questions
or
participate,
when
we
just
put
other
hand,
it
will
pass
the
bike
around.
F
F
C
F
And
what
the
work
itself
and
I
said
normally
would
be
longer,
because
I
thought
we
had
half
an
hour.
We
get
more
time
than
that.
Most
of
the
work
in
the
ITF
happens
by
email.
The
ITF
itself
started
around
1987
and
I'll
come
back
to
that
and
we
have.
We
now
have
this
sophisticated
tool
called
meat
Echo,
which
you
are
seeing
now,
which
is
used
by
five
or
six
other
conferences,
and
it's
a
it's
not
zoom.
F
F
F
What
I
think
it
is
is
that
we're
designing
some
new
beautiful
architecture
for
the
future,
involving
you
know
something
there
in
in
practice.
My
experience
is
it's
it's
mostly
arguments
and
when
they
go
badly,
they
they
work
out
like
on
Friends,
where
no
one
quite
listen
to
each
other,
and
we
were
on
a
break
and
we
shouldn't
have
split
up
or
something
like
that.
So
the
ITF
is
the
internet.
F
C
F
The
layer
is
everything
below
that
point
down
to
the
just
above
the
physical
layer,
so
we
don't
design
connectors
and
we
don't
design
electrical
systems,
but
from
that
layer
all
the
way
up
and
above
us
HTML.
The
thing
we
heard
this
morning
about
the
problems
with
the
browser.
What
was
it
called?
The
the
Ukraine
thing
where
the
browser
and
the
infinite
scroll
and
you
have
a
robot-
can't
go
by
well,
that's
not
our
problem!
That's
an
HTML
JavaScript
problem!
There's
another
Urban
centers
organization
above
us
that
deals
with
that
and
I.
F
Don't
do
that
so
well,
I!
Don't
personally
do
any
of
that
stuff.
I'm
involved,
mostly
in
in
network
security,
stuff
and
I,
was
actually
brought
into
code
share
this
working
group
with
these
fine
gentlemen,
because
apparently
you
know
something
about
how
to
get
the
document
through
the
process
and
that's
a
little
bit
of
a
Arcane.
F
In
the
government,
Department
understands
that
you
know
getting
your
documents
or
your
policy
up
through
the
right
approvals.
Is
you
know
a
job
in
itself,
but
I
have
met
all
those
people
that
have
done
those
things
and
we're
a
relatively
small,
very
open
community,
and
if
you
have
some
interest
in
somehow
getting
involved
in
HTTP
or
quick
or
DNS,
or
anything
like
this,
you
can
do
it
for
essentially,
you
know
cost.
We
don't
have
a
membership
and
we
are
a
meritocracy.
F
A
F
The
IHF
and
said
we'd
really
like
to
standardize
what
is
essentially
and
it
was
from
the
2015
and
when
did
I
get
on
2018
yeah,
it's
Terry.
So
basically
there
was
a
pillow
from
Mozilla
who
was
overworked
and
they
needed
some
help.
So
this
working
group
we
published
artists
in
7894,
which
is
ebml,
extended,
binary
markup
language.
E
F
For
version
zero,
one
and
three
I
got
that
already
in
August
of
2021
and
the
patronka
document,
which
is
of
course
an
instance
of
ebml
well
I,
think
we're
pretty
close
right
guys.
So
there
almost
all
of
our
meetings
and
while
the
itap
meets
three
times
a
year,
even
in
pandemic,
we
still
have
three
one
week
online
plenary
sessions,
even
though
it
would
have
made
more
sense
to
have
it
differently.
F
E
F
Group
meets
only
it's
what
we
call
virtual
interims,
so
that
means
they're
completely
online.
We'll
use
this
tool
that
you're
seeing
now
and
they're,
mostly
working
group
sessions.
We
try
to
avoid
slide
where,
as
you're
seeing
now,
anyone
can
join.
There
are
no
fees,
there's
no
membership
and
it
really
is
a
narutocracy
stay,
smart
things
and
we'll
listen
to
you.
F
F
F
You
often
need
to
to
log
in
that's
not
because
we're
afraid
of
our
intellectual
property
being
stolen,
but
because,
if
you
contribute
something-
and
it
turns
out
that
what
you
contributed,
you
had
intellectual
property
right
claims
on
then
that
gets
us
in
trouble.
In
other
words,
you
wind
up
being
in
a
position
to
sue
the
other
people.
F
We
do
a
lot
of
our
work
on
GitHub,
so
these
guys
have
whatever
400
some
opening
issues
at
times
and
we
try
to
work
through
them
figure
out,
which
ones
are
important
and
close,
the
ones
that
with
pull
requests
that
matter
and
finally
there's
a
mailing
list
and
that's
an
image
of
the
archive
of
it.
So
without
logging
in
or
doing
anything
else,
you
could
follow
the
mailing
list.
F
F
B
B
G
G
F
C
F
F
C
A
F
F
F
Asked
him
is
that
we're
ready
our
document
is
ready.
Would
you
please
review
it,
and
if
it's
okay,
then
you'll
Advance
it
to
the
next
thing
next
level
and
then
what
will
happen
is
that
those
other
Fortune
people
will
review
it
and
it
will
get
a
series
of
comments
and
discusses
and
it
works
by
rough
consensus
is
not
the
same
as
the
Quaker
system
of
consensus,
but
it's
similar.
So
you
could
have
objections,
but
you
can't
touch
anything.
No,
that's
what
the
point
is
so.
C
G
G
F
G
F
A
200
Page
document,
but
and
also
his
his
cohab,
has
just
returned
from
maternity
leave
a
week
ago.
So
he's
been
holding
the
floor
down
for
two
people
for
four
months,
so
imagine
if
he
will
catch
up
in
the
next
couple
weeks
and
I
hope
that
we
will
be
in
at
the
isgq.
Why
Christmas,
perhaps
earlier
wow
depends
on
how
many
comments
he
has
about.
C
G
F
That
one,
so
he
should
be
okay
with
that,
most
of
them,
okay,
so
Milestone
review.
Okay.
So
one
of
our
other
documents
is
this
flock
system
and
Jerome
was
talking
this
morning
about
I
noticed
that
yeah
EML
plaque
and
you
know,
trust
as
your
container
your
single
file
container
for
the
what
was
it
called
yeah
there
you
go
raw
cook,
so
that's
the
implementation
of
our
spec,
essentially
right.
So
that's
really
cool
to
really
hear
about
it.
Yeah.
C
C
F
G
B
D
2001
and
the
original
walls
are
wrote
a
nice
documents
about
how
far
supposed
to
work
or
how
it's
like
a
structured,
but
a
lot
of
details
were
missing
So.
Currently
we
have
a
document
where
all
the
details
should
be
in
and
it
should
buy
now
be
a
document
where
you
don't
have
to
look
at
the
source
code
of
flight
implementation
to
make
your
this
document
became
I
think
four
times
as
large
as
it
was
in
first
place.
D
F
I
just
mentioned
Martin,
that's
a
big
propaganda.
Okay
about
time.
Yeah
about
time
has
basically
jumped
into
this
and
welcome
to
Spring
and
this
year.
Yes,
yeah
so
basically
jumped
in
pretty
late
and
took
over
this
and
we're
extremely
helped
police
about
this
and
I.
Don't
think
you've
been
involved
in
the
ipf
at
all
ever
before
right,
so.
F
Oh,
this
is
small
working
group.
Some
American
groups
have
300
members
and
you
know
process
the
same
time,
but
ours
is
and
we
need
people
to
read
the
documents
right
and
particularly,
if
you
read
the
document-
and
you
say,
I,
don't
understand
something
that
is
so
useful.
It's
terribly
useful
or
this
sentence
is
nonsense.
You
might
even
say
that
that's
really
really
useful
to
us.
F
G
G
F
We
have
a
separate
document.
You
can
implement
the
trial
schedule
without
a
codex,
which
would
be
bizarre,
but
it
might
be
interesting
if
all
you
cared
about
was
say
showing
what
the
the
player
that
simply
wanted
to
show
you.
What
the
chapters
of
the
movie
were
right.
That
would
be
a
possibility.
We
never
need
to
decode
the
Codex,
because
you
remember
playing
the
content,
but
you.
C
F
Say,
oh
I
need
something.
What
can
we
do
something
for
my
phone,
so
the
list
of
kodaks
that
we're
always
trying
to
get
out
to
trying
to
try
to
come
up
to
step
slightly
back,
so
the
list
of
codecs
is
in
a
separate
document,
and
in
that
document
we
have
a
list
of
codecs
and
it'll
be
a
lot
of
50
of
them
around
that
muscle
yeah
in
that
list,
and
one
of
the
things
that
that
document
is.
F
It
says
that
if
you
have
a
new
code
app
and
you
want
to
have
an
identity
for
it,
then
there's
a
process
by
which
we
ask
you
to
go
through,
and
you
can
say
you
basically
just
email
a
thing
and
it'll
go
into
a
table
and
we
have
a
there's
a
paid
people
in
California
who
keep
track
of
this
table.
It's
just
an
XML
table
and
there's
a
if,
if
the
person
who
asks
follows
the
right
instructions
which
in
some
cases
just
needs,
you
know,
my
name
is
Bob.
F
F
Okay,
all
right
so
so
that
happened,
and
we,
our
next
step
I,
think
is
going
to
be
working
on
the
metropica
Kodak.
We
need
to
write
the
ionic
considerations
for
this,
which
just
means
we
have
a
whole
bunch
of
different
things.
I
was
going
to
put
up
a
slide,
but
I
thought
we
would
run
at
a
time
there's
a
whole
bunch
of
of
different
possibilities
from
you
have
to
have
an
ietf
consensus
document.
F
That's
been
extensively
reviewed
in
an
RFC
published
like
that's
like
the
highest
level
to
any
documents
in
a
stable
place
will
be
fine
to
you
know.
I
wrote
this
document
of
this
other
standards
organization
and
they
did
something
would
be
fine
down
to
this
is
my
name
and
address,
and-
and
you
can
contact
me
here
and
then
you
know,
there's
a
whole
range
of
different
things
and
we
assigned
questions.
It's
probably
going
to
be
more
towards
the
lower
end
of
things
you
know
for
that.
F
If
someone
comes
along
and
proves
they
are
not
a
a
Sandlot
that
you
know
will
give
them
a
number
and
will
be
done.
We
just
have
to
write
that
down
in
the
document
and
see
how
it
works.
We
said:
there's
no
flat
issues
left,
that's
that's
from
last
time
and
then
I
guess
one
of
the
last
things
that
I
think
we
have
about
five
minutes
left
here.
G
F
F
We
have
a
new
version
of
ffv1
that
we
are
I
guess
in
planning
yeah,
and
so
one
of
the
questions
is
essentially
is
you
know
there
are
some
bits
and
pieces
that
V3
doesn't
do
and
we
have
a
V4
concede,
but
we
don't
yet
have
a
I
would
say
a
a
big
enough
reason
to
step
forward,
and
so
you
might
have
some
ideas
of
things
you
want
in
a
video
Codec
that
you
could
help
share
with
us
would
be
great,
even
if
you
don't
know
how
to
implement
it.
Requirements
are
as
good
as
implementation
right.
G
I
don't
know
you
remember:
we
had
some
changes,
people
discover
books
in
the
specifications
and
also
we
found
some
issues
as
well.
So
there's
like
eight
Errata
to
add
to
the
documents
and
we
postponed
it
until
microscore
was
ready
in
case
we
did
changes
in
the
document
and
now
that
in
my
first
case
with
the
type
we
can
actually
go
back
to
Vietnam,
send
the
aerator
and
actually
found
the
way
to
do
it.
So
I
will
probably
do
it
this
weekend.
F
So
that's
cool,
so
the
RFC
there's
a
site
called
the
RFC
RFC
editor.org,
which
is
the
authority
of
site
for
all
of
the
rfcs,
all
nine
and
a
half
thousand
of
them
and
on
that
website.
So
the
rfcs
are
immutable,
which
is
often
very
frustrating
to
people
when
they
find
spelling
mistakes.
We
don't
reissue
them
ever.
F
So
what
we
will
do
is
two
things
design
that
you
can
host
in
Nevada,
which
is
what
Steve
is
going
to
do
and
there's
actually
way.
If
it's
done
in
XML
that
we
can
show
you,
the
RFC
plus
the
Errata
and
we'll
say
to
you.
But
this
is
not
normative,
because
we
can't
be
sure
you
know,
and
then
what
will
happen
is
we'll
respin
and
we'll
produce
a
new
RFC
with
a
new
number
with
the
Errata
included.
F
F
G
G
But
the
whole
Matrix
has
to
be
specific.
Specification
is
based
on
one
big
XML
file
that
is
generating
actually
the
specifications
of
the
elements
in
matroska
and
that
code
is
also
used
in
entering
tools
and
also
in
my
tools
and
carefully
data
and
machine
and
I
regenerated
all
the
code.
The
recently
so
now
everything
is
stable,
and
so
basically
the
code
matches
exactly
the
stack
from.
F
G
F
B
G
G
F
And
actually
it's
a
bit
of
a
pain
in
the
ass,
because
what
we
would
really
like
is
all
of
the
encoders
writers
to
start
using
the
new
one
immediately,
but
of
course
that
would
be
stupid
because
the
players
don't
don't
know
about
it.
So
what
we
actually
need
is
all
of
the
players
to
start
supporting
both
as
there
and
then
some
few
years
in
the
future.
We.
F
A
G
G
F
F
G
B
E
F
That's
usually
well
accepted
and
the
only
time
it
it
doesn't
happen
is
with
you
know,
someone
saying
we
should
do.
You
know
oil
this
ocean
and
everyone
else
is
like
yeah
I'm
done,
I'm
going
home
right,
so
yeah
we
can
exist
for
as
long
as
there
is
work
to
do.
But
what
they
do
like
us
to
do
is
to
to
bite
off
small
chunks
at
a
time
and
say
what
we're
going
to
do
and
then
do
it
and
then,
based
on
that,
we
get,
you
know
extended.