►
From YouTube: IETF-TOOLS-20220208-1900
Description
TOOLS meeting session at IETF
2022/02/08 1900
https://datatracker.ietf.org/meeting//proceedings/
A
So
as
before,
if
you've
got
the
bandwidth,
I
encourage
you.
You
share
video.
Let's
try
to
make
this
an
in
person
as
close
to
in
person
as
possible,
meaning
I
would
like
the
general
vibe
to
be
that
we're
sitting
around
the
table
talking
with
each
other,
not
that
we're
passively
listening
on
a
phone
call.
A
If
you've
not
used
medico
at
an
interim
recently,
there
are
a
couple
of
features
that
have
been
added
that
I
want
to
point
out.
Since
we've
got
a
small
group
here,
I
think
we
can
go
ahead
and
beat
up
on
their
server
and
have
everybody
connected
to
the
the
the
server
that's
doing
primary
mixing
if
you
start
sending
audio
using
the
microphone
button,
that's
above
the
number
of
participants,
tab
in
the
left
column
and
just
leave
that
open.
A
A
If
you
do
that,
you
will
remain
connected
to
the
primary
mixer
at
all
times
and
your
you
can
unmute
and
and
mute
locally
quickly
without
having
to
wait
for
me
to
go
to
switch
your
media
sessions
on
the
back
end.
A
C
B
A
A
A
A
If
you've
not
already
done
so,
please
skim
through
the
the
notes
page
for
the
meeting.
I'm
assuming
everybody
has
that
at
hand.
A
A
All
right,
let's
go
ahead
and
get
started.
As
you
know,
the
the
notes
page
is
quite
long.
I'm
planning
to
treat
most
of
the
sections
as
take
them
as
read
unless
somebody
brings
up
questions
I'll
mention
them
when
I'm
about
to
skip
over
them.
If
you've
got
something
in
them
that
I'm
planning
to
skip
that,
you
want
to
talk
about
just
interrupt
me,
please.
A
A
A
Move
everything
that's
installed
over
into
that
system.
Have
the
development
team
verify
that
everything's
working
and
then
schedule
a
cut
over?
There
is
an
alternate
approach
that
we
could
have
taken,
but
we're
not
currently
planning
to
which
would
involve
an
in-place
upgrade
of
the
os.
That's
currently
on
ietfa
running
on
the
older
hypervisor
and
the
older
hardware.
A
The
trade-off
here
is
having
an
ability
to
check
that
the
moved
systems
are
functional
before
we
have
the
cut
over
instead
of
repairing
any
damage
that
might
happen
from
an
in-place
upgrade
versus
continuing
to
run
for
a
few
more
weeks
on
an
os
that
is
past
its
point
of
getting
security
updates.
Basically,.
A
A
A
Does
anybody
have
any
any
issues
with
that?
You
know
fully
understanding
that
we've
got
the
risk
of
running
on
this
older
os
for
another
six
weeks
or
better.
D
I
think
that
growing
the
build
a
new
rod
gives
it
more
flexibility,
more
safety.
It
takes
a
little
bit
longer,
but
I
don't
think
it
will
take
significantly
longer
and
I
think
it
would
be
fine.
I
mean
I'll
provide
either
solution
that
the
ietf
wants.
D
D
A
So,
let's
our
plan,
unless
I
hear
otherwise,
is
that
we're
going
to
continue
down
this
building
the
new
server
I'd
like
to
track
it
kind
of
closely
glenn.
If
we,
if
something
comes
up,
that's
going
to
delay
getting
to
the
point
where
the
dev
team
can
test
at
the
time
frame
that
we've
been
talking
on,
please
let
me
know.
A
I'm
going
to
take
moving
the
rrc
editor
lists
over
to
itfa
as
red.
A
A
Xml
rsc
is
now
on
github.
It
is
going
to
get
they're
going
to
be
some
major
changes
in
what's
in
maine
before
we
really
start
developing
against
it,
we'll
be
beating
on
it
today
and
tomorrow.
Basically,
cly
will
become
the
main
branch
and
the
others
will
become
archived.
A
I
believe
that
we're
at
the
point
now,
where
any
future
xml
rfc
tickets
should
be
entered
as
issues
in
github
and
later
today,
I'll
be
working
on
closing
the
track
instance
to
new
changes
and
trying
to
find
a
way
to
put
a
banner
there
to
let
people
know
if
they've
got
older
links
to
that
to
move
to
the
newer
the
newer
location.
A
So
we've
been
doing
a
lot
since
the
last
meeting
on
moving
to
where
we're
doing
our
primary
development
on
github
nick
in
particular,
has
built
a
lot
of
tools
for
us
one.
That's
very
nice,
based
on
a
conversation
we
had
with
dkg
that
lets
us
continue
to
keep
very
close
control
of
our
private
signing
keys
for
signing
packages
at
pi.
A
By
that
will,
let
us
mechanically
do
or
pushes
sign
pushes
of
of
new
releases
into
pi
pi
without
with
a
very
low
probability
of
developer
and
operator
error
in
the
process
of
making
those
pushes
is
a
a
really
nice
piece
of
work
by
nick
we've
also
built
out
a
lot
of
ci
cd
on
these
repositories,
acting
using
the
rfc
to
html
repository,
which
is
the
thing
that
makes
the
htmlized
documents
as
a
testing
ground,
so
that
commits
to
the
main
branch
are
automatically
tested
pushes
are
automatically
tested
and
the
right
thing.
A
B
The
reason
I'm
asking
is
I'm
wondering,
because
this
will
sort
of
really
enable
the
community
to
participate
better
than
they
have
in
the
past
at
least
sort
of
the
the
non-core
people
that
are
on
this
call.
I
wonder
if
we
want
to
like
talk
about
this
plenary
for
five
minutes
and
basically
say
hey,
you
can
now
like
go
to
get
up
and
fix
stuff
directly.
That
annoys
you
yeah.
B
Okay,
so
that
would
be
new.
Probably
I
don't
know
what
the
time
zones
are
going
to
be
for
you,
but
if
you
make
me
slide,
I
can
talk
to
it
or
somebody
eric.
B
Whatever
time
it
is
all
right,
so,
let's
let's
plan
for
that
and
we'll
we'll
set
aside
some
time
there
cool
sure.
A
All
right,
fools.itf.org
we're
in
truly
the
very
last
stretch.
The
long
pole
is
bib
xml,
which
I'll
talk
about
separately.
Kasar
is
doing
the
a
set
of
final
things
to
get
the
author
tools
into
what
we
consider
a
production
mode
instead
of
a
development
mode.
That
should
happen
very
very
soon.
A
E
No,
I
don't
think
so.
I
think
we
may
have
a
an
error
in
the
template
to
do
with
the
word
joiner
discussions
taking
place.
We
have
a
a
number
of
suggestions
from
bob
briscoe
that
need
to
be
incorporated
into
it,
but
those
all
just
maintenance
stuff
that
could
just
continue
on
to
its
life.
So
you
know
I
I
mean
I
don't
see
anything,
I'm
really
looking
for
external
feedback.
That
says
whether
anybody
thinks
any
show
stoppers
here
at
all.
E
Whether
people
are
comfortable,
that
we
should
just
just
go
ahead
with
it
now.
A
So
if
that
bothers
anybody,
let
me
know
I
think
offline.
I
don't
know
that
we
need
this
to
burn
time
on
the
call
here
other
than
just
making
sure
everybody
sees
that
that
one
is
going
to
lag.
Similarly,
kasara
is
working
on
a
replacement
for
bap.
We
have
it
out
there.
If
we
need
it,
we
can
just
stand
up
the
the
really
simple
web
service.
A
That's
built
into
bill,
finner's
repository
that
bill
and
paul
kizebot
worked
on,
but
kasaria
is
working
on
something
better,
we'll
see
if
it's
ready
before
we
are
ready
to
cut
over
I've
been
working
with
henrik.
I've
got
the
final
set
of
redirects
located.
I
will
reformat
them
and
send
them
to
glenn
we'll
be
ready
to
go
once
we
are
happy
with
what's
happening
with
the
bibxml
service.
A
Now
that
service.
That
project
has
a
lot
of
hot
and
heavy
activity
going
on
at
the
moment,
where
we're
we're
now
pushing
edge
cases
around
ribose
is
finding
some
points
of
discomfort
with
their
use
of
relatin
has
some
expected
semantics
to
the
names
in
the
relative
format
that
they're
using
internally,
that
don't
mesh
well
with
the
semantics
of
names
of
things
that
we
have
in
the
ietf.
A
A
I
do
think
we're
pretty
close,
and
I
think
that
we'll
have
we'll
be
working
on
deploying
it
on
our
own
devices
over
the
next
couple
of
weeks,
and
I
am
hoping
that
in
the
span
of
three
weeks
or
so
from
now,
we
can
really
cut
over
to
it
and
start
the
the
tools.iatf.org
final
parts
of
the
tools.ihf.org
transition.
A
So
I
will
time
that
to
happen
after
whatever
the
draft
cutoff
is.
I
don't
remember
what
that
is
on
the
top
of
my
head,
but
it
won't.
We
won't
move
the
rug
out
from
everybody
during
the
the
hard
draft
submission
press.
A
A
Semantics
and
terminology
that
we
were
talking
about
he's
now
in
a
email
thread
with
the
ietf
leadership,
to
get
a
better
polish
on
what
that
is,
and
I
suspect,
that's
likely
going
to
spill
out
onto
other
seos.
F
A
A
I
believe
my
unders,
my
understanding
of
where
we
are
right
now,
is
that
we
need
to
figure
out
if
and
how
we
are
going
to
cause
new
rooms
in
zulu
to
have
the
notewell
what
that
was
going
to
contain,
and
when
it's
going
to
be
present,
I
think
glenn
was
looking
to
jay
for
direction.
On
configuration
of
that,
it's.
E
A
E
Sorry
rob,
I
think,
yes,
I
think
that's
me.
Actually
I
have
an
an
unanswered
email
about
the
stuff.
Now
I
need
to
go
back
to
so
I'll.
Have
a
look
at
that
today.
Yeah.
A
Okay,
I
wanted
to
reconform
reconfirm
that
we're
on
the
right
target
with
zulup.
I
am
planning
on
starting
to
work
with
midako
between
113
and
114,
on
changing
the
back
end
for
medico
to
zooloop
instead
of
jabber.
A
If
that
makes
anybody
uncomfortable,
let
me
know
at
the
last
meeting
we
I
suggested
that
the
iab
and
isg
consider
zulu.
The
end
result
in
the
meeting
was
a
very
tentative.
Well,
we
need
to
play
with
it
first,
I
think
I've
been
hearing
some
evidence
of
no,
we
really
don't
want
to
do
this
from
those
bodies
since
then,
and
that
they
want
to
stay
with
slack
am
I
am
I
correct.
A
So
I
then
ask
you
know:
for
future
working
groups
is
having
zulu
be
the
place
that
we
plan
to
have
them
do
work
still
the
right
thing.
If
the
leadership
doesn't
want
to
go
there.
B
Oh
no
yep,
oh
yeah,
sorry
that
was
unmuted
the
whole
time.
The
reason
leadership
isn't
doing.
It
is
because,
as
far
as
I
understand,
there's
no
way
to
not
have
it
be
archived
and-
and
that
was
a
concern
because
we
actually
have
slack
channels
there
that
are
mirroring
the
isg.
Only
iab
only
sort
of
lists
that
we
have
also
archived
so.
B
B
Sure,
that's
that,
but
that's
it
for
each
individual
id
to
figure
out
right
how
they
want
to
do
that
and
but
the
isg
overall.
I
think
that
the
overriding
thing
was
that
it's
not
possible
to
have
non-aircraft
conversations
either
or
one-on-one.
B
A
All
right,
unless
somebody
has
any
other
questions
on
zulu
I'll
move
forward.
A
Will
land
on
youtube
so
keep
that
in
mind?
As
you
can
comment,
okay,
go
ahead,
jay.
E
Yeah
sorry,
I
just
did
a
quick
search.
I
don't
understand
this
thing
about
archiving
missoula
zoo.
It
has
organizational
wide
message,
retention
policies
that
are
then
overridden
by
stream,
specific
message,
retention
policies.
E
It
doesn't
tell
me
in
the
documentation
how
long
that
message,
retention
minimum
is,
but
I'd
be
surprised
if
it's
much
more
than
a
day
or
something
so
it
looks
as
though
we
can
do
you
know
stream
specific.
You
know
messages
disappearing
after
a
particular
period
of
time,
so
I'll
investigate
that
a
bit
further.
A
Please
follow
the
link
that
I
have
at
that
first
sentence
on
tools,
workshops,
there's
a
github
repository
that
is
currently
in
my
area,
I'll
move
it
to
ietf
tools.
After
the
call,
there
are
a
series
of
workshops
that
we've
talked
about
before
we're
going
to
put
together
a
call
sometime
in
the
next
very
small
number
of
weeks.
A
General
tools
call,
but
anyone
in
the
community
will
be
welcome
to
join
t
prioritize
and
start
scheduling
which
of
these
workshops
we
will
will
execute
on
if
you've
got
ideas
for
new
workshops.
You
know
please,
please
contribute.
A
H
A
I'm
going
to
take
the
common
bootstrap
theme.
Work
is
read.
Please
follow
the
link
if
you
want
to
know
more
about
it
for
the
data
tracker.
The
high
point
I
want
to
talk
talk
about
you
can
read
through
all
of
what's
here
is
we
are
running
behind
cloudflare,
that's
successful
over
the
next
few
days,
we're
going
to
try
to
move
off
of
apache
and
mod
whiskey
into
engine
x
and
g
unicorn.
A
You
can
read
about
some
of
the
major
development
pieces
of
work
that
we
need
to
do.
We
did
make
a
change
in
direction
recently
on
when
the
when
we
were
going
to
pull
in
the
bootstrap
5
branch,
we're
going
to
bring
that
in
first
and
start
the
time
zone,
aware
branch
work
over
after
discussing
with
nick
and
cassara
and
jennifer.
We
think
we
want
to
re-implement
the.
A
Code,
that's
doing
that
migrations
anyhow,
so
that
we
all
are
very
familiar
with
it.
Instead
of
you
know
discovering
the
work
that
henry
could
rediscovering
the
work
that
henrik
had
previously
done.
F
F
I
got
from
what
lars
said.
I
don't
know
a
month
or
two
ago,
so
it
seems
to
me.
We
need
to
tell
the
community
before
we
release
that
one
yeah.
G
A
There
are
links
off
to
a
couple
of
notes,
pages
that
I've
created
that
show
the
kind
of
improvements
that
we've
seen
they.
A
They
are
not
massive.
There
are
things
that
we
can
do
to
move
them
closer
to
massive,
but
it
has
been
quite
a
bit
of
help
already.
A
H
A
So
we
are
looking
at
restricting
the
set
of
domains
that
by
default,
xml
rsc
will
fetch
x,
includes
from
cassar,
and
I've
been
working
out
a
set
of
ways,
and
we
think
that
we'll
implement
this
in
the
next.
You
know
in
the
next
release,
so
that
will
be
domains
like
the
xml
rsc.itf.org
or
its
replacement.
A
And
a
few
wildcarded
sites
that
would
let
people
pull
things
from
their
github
repositories,
but
might
not
put
that
one
into
xml
rfc
we're
doing
a
similar
thing
with
author
tools
with
def,
for
where
people
can
pull
things
by
url
for
arbitrary
diffing,
so
we'll
definitely
be
looking
at
the
the
locations
in
in
github
for
deaf,
this
all
comes
into
you
know:
do
we
really
want
people
to
be
able
to
cause
the
data
tracker
to
pull
pages
from
arbitrary
sites
once
we
might
run
into
problems
in
the
long
run,
with
the
both
the
content
and
just
the
act
of
doing
a
get
on
a
particular
domain?
A
We
might
move
further
later,
we'll
have
some
conversations
about
submit
the
the
submit
tool,
but
I
don't
think
we're
ready
to
launch
into
those
on
this
call
a
second
before
we
get
to
the
next
tools.
Call
we're
going
to
be
talking
about
what
we
would
accept
into
what
kind
of
includes
we
would
accept
into
the
repository
a
little
bit
different
than
what
we
currently
do
now.
I
So
I
saw
that
actually
just
a
couple
minutes
ago
that
the
the
poll
was
restricted
and
what
urls
it
would
fetch,
and
I
I
certainly
am
one
who
does
do
that
particularly
to
deal
with
you
know,
replies
to
incremental
replies
to
particularly
to
discuss
is
to
show
you
know
it's.
This
is
what
I
did
and
here's
the
two
text
files
that
I
stuck
on
yeah
often
it
was
github,
and
so
that
should
work
fine.
I
So
I'm
I
I
guess
I
guess
the
two
questions
are:
what's
the
process
for
getting
new
new
urls
new
prefixes
added
to
that
list,
how
far?
Where
does
it
have
to
go?
If
we
go
that
do
that
and
the
other
part
of
my
question
is:
has
this
really
been
a
problem
up
to
now
with
the
rfc
diff?
Have
we
really
gotten?
You
know,
abuse,
complaints
or
something
like
that
from
this.
A
So
this
is
all
rooted
in
things
that
we
learned
from
the
security
review
of
the
data
tracker
that
found
issues
in
xml
to
rsc,
as
the
data
tracker
was
using
it
and
the
constraints
that
we're
setting
up
are
basically
built
around
that.
A
I
So
I
agree
with
you
that
that
the
potential
there,
for
you
know
doing
something,
is,
is
a
problem
and
as
we
improve
the
performance
of
the
diff
tool,
actually
we
will
be
improving
the
ability
to
attack
right
the
more
capacity
for
doing
diffs.
You
know,
particularly
if
you
know
we
start
doing.
I
don't
know
some
kind
of
you
know
cloud
bursting.
You
know
the
day
before
the
cut
id
cutoff
date
or
something
like
that
to
have
extra
capacity.
Well,
that's
also
adding
capacity
to
attack.
I
I
A
Is
really
going
to
be
an
operational
decision,
so
I
think
it
would
be
me-
and
I
would
certainly
coordinate
closely
with
the
leadership
on
what
else
we
would
point
to
for
getting
requests
in
mail
to
the
secretariat
or
prs
against
the
relative
relevant
piece
in
the
code
would
be
the
right
way
to
ask.
So
is
it
it's.
I
A
Yeah,
maybe
I
my
initial
instinct
was
that
we
would
use
basically
the
same
metric
for
what
we
point
to
now
is
sort
of
what
we
use
for
what
we'll
make
references
to
inside
rfcs,
so
we'd
be
pointing
to
stable
places
and
sdos
and
things
where
we
have.
You
know
admin
that
we
trust
and
individuals
places
like
your
domain.
A
A
A
About
github
is:
is
that
you
can't,
while
you
might
be
able
to
put
content
there,
you
can't
really
control
how
that
content
gets
served
and
one
of
the
one
of
the
attacks
that
I
that
would
be
easy
to
mount
right
now
would
be
a
you
provide
a
url
that
has
a
slow
loris
on
the
other
end.
A
A
G
Yeah-
and
I
mean
we
work
with
what
I
call
the
proponents
or
the
the
founder
of
the
young
catalogue-
the
bernout
clay
is
the
joe
clark
and
and
a
few
others
to
make
a
list
of
about
10
that's
the
list,
which
is
there
and
basically,
I
am
feeding
from
the
top
priority
to
pante
on
the
contractor
by
opening
issues
and
checking
what
is
done.
So
it's
slowly
working
to
the
list.
G
A
C
A
Project
in
the
yang,
the
the
yang
catalog
organization
itself,
that's
useful
to
follow
for
seeing
what's
happening
or
where
the
focus
is
on
day
to
day
getting
catalog
development.
Michael,
you
started
to.
I
Ask
something
is
the
issue
of
said
numbers
with
this
in
clearly
in
your
scope,
there
were
some
questions
that
did
come
from.
I
think
you
eric
and
benoit
last
week,
so
I
just
want
to
make
sure
that
everyone,
everyone's
clued
into
the
the
challenge
or
the
whatever.
G
Yeah
and
sorry,
michael,
I
should
have
thought
about
you
as
well,
not
only
cast,
and
there
you
are
part
in
the
discussion.
G
I
think
we
need
to
get
aid
in
the
coming
days,
a
discussion
with
all
the
components
and
for
the
specific
for
the
seed
you
castle
and
everyone
that
wants
it
and
the
people
from
the
young
caterer
can
try
to
get
thing
because
working
on
the
google
doc
I
mean
it's
not
efficient
right.
Basically,
so
we
need
to
get
a
talk
on
this.
Okay,
never
try
to
find
it.
Okay,
actually
nighttime.
I
A
All
right,
unless
somebody
has
something
else,
we
can
move
on
to
the
data
track
security
view,
which
I
realized
I
hadn't
typed
in
things
I
started
to
I'll
finish
it
later.
A
The
dev
team
is
completing
the
last
actions
we
needed
to
work
on
to
remediate
the
issues
that
the
security
report
pointed
out.
We
got
all
of
the
major
ones
before
the
last
call.
There
are
some
minor
ones
that
we'll
be
working
with
fixing
over
the
next
couple
of
weeks.
A
We'll
then
prepare
a
document
that
goes
along
with
their
final
report.
A
The
report,
as
presented
from
them,
still
has
a
lot
of
sections
that
say
that
the
issues
are
unaddressed
rather
than
have
them
go
back
and
change
the
report
to
say
the
issues
are
addressed
and
planning
on
just
putting
a
companion
document
along
with
it
when
we
publish
it
that
notes
how
we
addressed
the
the
ones
that
the
reports
say
weren't
addressed
yet
so
we
do
plan
to
go
to
publish
the
the
final
report
with
all
of
the
dark
secrets
that
it
had
down
inside
of
it.
A
They
are
no
longer
relevant,
but
it
was
entertaining
what
what
they
were
able
to
extract.
I
E
Mean
just
want
to
double
check.
Nobody
has
any
objection
to
us
doing
this.
I
mean
I,
I
think
it's
entirely
along
aligned
with
the
principle
of
transparency
that
we
have,
and
I
think
this
is
the
normal
way
that
a
good
you
know
company
would
do
this
or
a
good
organization
would
do
this,
but
I
want
to
you
know,
make
sure
that
we're
all
along
with
that
plus
one
from
rich.
I
can
see
in
the
chat.
A
Yeah,
it's
a
little
hard
to
answer
that
without
having
seen
the
report,
so
I
saw
a
little
bit
of
hesitancy
on
some
people's
eyes.
We
can
certainly
circulate
the
the
report
among
the
team
before
publishing
it
on
the
website,
so
yeah.
A
A
All
right
we're
working
on
the
segment
work
for
the
next
security
review,
which
would
be
an
ietf
a
wide
review,
I'm
going
to
be
in
touch
with
jay
over
the
next
day
or
so
to
hopefully
finalize
that
and
start
getting
onto
zx's
schedule
for
for
that
review
and
everything
else,
I
think
we
can
take
as
read.
E
No,
I
was
gonna
say
if
nobody
does
I'd
like
to
just
finish
off
by
going
back
to
the
workshops,
briefly
sure,
so
the
the
the
lrc
public
budget
has
been
published
again
and
again
we're
making
a
significant
investment
in
tools.
You
know,
there's
a
strong
feeling
on
the
llc
board
that
there
is
a
certain
amount
of
technical
debt
that
needs
to
be
repaid.
E
We
have
nick
and
cassaro
on
board
now,
so
we
have
significant
amount
of
development
capabilities
and
things,
and
so
these
workshops,
I
think,
going
to
be
very
important
for
us
to
plan
the
work
ahead
and
we
have
clearly
two
sides
to
that.
One
is
to
tidy
up
and
clean
up
stuff
that
exists,
but
I
don't
think
that's
going
to
be
the
majority
of
the
work.
E
I
think
we're
going
to
be
able
to
relatively
soon
switch
to
a
more
forward-looking
approach
where
we're
able
to
do
some
really
interesting
new
things,
and
so
I
think
it's
going
to
be
important
for
us
to
talk
about
the
right
sorts
of
things
and
have
that
kind
of
engagement
around
that.
So
I
just
wanted
to
highlight
that
that
these
workshops,
I
think,
will
be
important
for
shaking
the
future
of
stuff.
So
I
mean
just
to
give
you
an
example.
E
The
type
of
things
that
some
people
have
spoken
about
in
the
past
are
us
having
say
something
like
a
plug
into
vs
code.
That
brings,
you
know,
pulls
in
all
of
the
the
stuff
you
need
to
to
create
an
id
with.
Those
type
of
things
are
now
possible
for
us
to
do.
I'm
not
saying
that's
the
right
one,
but
we
need
to
start
having
those
conversations
about
those
things.
E
So,
if
you
could
look
at
the
workshops,
a
bit
add
in
any
sort
of
thoughts,
ideas
of
the
directions
that
you
think
you
we
would
we
should
be
discussing.
Please
do
that
robert
and
I
have
done
what
we
can,
but
I
think
at
times
you
know
we're
quite
operational
and
if
you
know,
if
others
have
got
the
border
ideas,
that
would
be
useful.
A
I
have
a
question
about
the
call
this
was
quite
long.
They
did
the
take
as
red
approach
work.
Do
you
want
do
we
want
to
start
having
this
call
more
frequently,
or
do
you
think
that
calls
at
the
current
cadence
with
this
level
of
content
in
them
is
the
right
level.
C
C
A
A
The
move,
the
data
tracker,
align,
cloudflare
and
the
move
of
the
source
into
github
is
definitely
big,
big
big
things
for
us.
So
so
far
it's
going
smoothly
so.