►
From YouTube: IETF-CELLAR-20220222-2000
Description
CELLAR meeting session at IETF
2022/02/22 2000
https://datatracker.ietf.org/meeting//proceedings/
A
B
A
And
let
me
let
me
do
that
real
fast,
just
in
case
somebody
else
is
looking.
I
do
so.
Oh
you're
you're
perfect.
Thank
you.
B
A
A
A
If
I
was
sharing
a
screen,
I
would
be
sharing.
A
This
one,
I
think-
and
I
would
be
pointing
it
here-
does
that
work
for
people.
A
Yes,
cool
excellent
and,
let's
see
so
far,
just
have
steve
and
martin.
A
Michael
had
a
personal
thing,
so
so
he
may
be
not
able
to
join
us,
at
least
at
least
on
time.
This
is
starting
to
be
like
spencer
and
and
michael
discovering
things
that
neither
one
of
us
you
know
both
of
us
can't
be
in
the
same
place.
At
the
same
time,.
A
And
just
for
extra
credit
as
long
as
we're
here
next
meeting
is
a
fifth
tuesday,
because
the
fourth
tuesday
is
during
itf-113,
so
that
will
be
exciting.
Also.
A
We
might
not
have
a
quorum
today
and
my
apologies
for
being
confused
about
that.
B
A
A
That
may
not
be.
That
may
not
be
a
good
thing
to.
A
B
So
at
some
point
I
will
not
wait
anymore,
but
the
three
issues
we
have
one
of
them
is
irrelevant
and
the
two
others
have
a
pull
request:
read
ready.
So
as
soon
as
we
merge,
we
can
publish
a
new
document
and
actually
start
the
reviewing
cool,
maybe
in
two
days
not
a
good
day
to
do
that.
But
I
will
see
you
during
the
coming
months
probably
emerge
in
one
or
two
weeks.
If
nobody
else's
comment
and
then
we'll
publish
version,
nine
of
the
documents
and
probably
start
asking
for
reviews.
A
Excellent
and.
C
Well,
I
was
kind
of
wondering
whether
at
what
point
we
should
publish
a
new
draft,
because
I
saw
that
certain
drafts
get
published
way
more
often
than
others.
C
The
document
has
changed
quite
a
bit
since
the
last
draft.
I
don't
know
at
what
point
we
should
decide.
A
new
draft
should
be
published,
should
it
always
be
just
when
it
the
last
one
goes
out
of
date
or
I
don't
know,
I've
not
been
involved
in
this
process.
A
So
the
spencer's
opinion,
so
one
thing
I
should
mention
for
you
is
that
itf
working
groups
have
a
lot
of
opportunity
to
do
things
their
own
way,
not
everything
but
a
lot
of
things,
and
so
the
so
the
thing
with
that
is
you
you,
you
don't
want
the
working
group
to
get
out
of
sync
with
what
you're
writing
in
the
document,
because
it's
a
working
group
document,
but
if
everybody
in
the
working
group
does
github-
and
you
know
they
can-
they
can
see
what's
happening
on
the
repositories
and
things
like
that,
it's
less
critical
for
you
to
publish
that
often
does
that
make.
C
A
If
you,
if
you
have
a,
if
you
have
a
big
bunch
of
stuff
coming
up,
it's
it's,
it
may
be
easier
for
people
to
figure
out
what
the
differences
are.
A
A
So
if
you
know
so,
if,
if
that,
if
that,
if
that's
helpful.
C
Yes,
I
thought-
maybe
I
don't
know
how
many
people
outside
of
the
working
group
chime
in
and
when
they
chime
in
they
usually
do
through
github.
So
it's
it
wouldn't
be
important
it
in
this
case
it
probably
isn't
important
to
the
outside
world
anyway.
So
that
was
what
I
was
wondering
about,
but
it's
clear
now.
A
Yeah
so
so,
like
you
know,
like
I
said
I've
for
for
the
you
know,
for
the
first
45
years
of
the
itf
or
whatever
it
was,
we
weren't
using
github,
and
so
what
we
were
using
was
the
mailing
list,
for
you
know
for
people
to
follow
discussions,
and
if,
if,
if
we
thought
there
were
people
on
the
mailing
list
that
are
not
in
you
know
in
the
github
repos.
Basically
that
would
be
the
ones
you
would
be
updating
it
for.
A
But
if
it's
the
other
way
around,
it's
not
so
critical.
C
Okay,
no,
I
didn't
have
any
other
issues.
A
Excellent,
so
let's
let's,
let's
declare
victory
and
and
go
ahead,
and
let
me
give
you
guys
your
rest
of
your
evenings
back
and
thank
you
for
being
here
and,
like
I
say
I
really
apologize
for
not
realizing
that
the
urls
changed
every
month.
So
so
that
was
interesting.
C
Yes,
well
I'll,
see
you
next
month,
then.