►
From YouTube: IETF-TOOLS-20220614-1800
Description
TOOLS meeting session at IETF
2022/06/14 1800
https://datatracker.ietf.org/meeting//proceedings/
A
A
A
So,
given
that
jay
and
lars
are
are
likely
to
be
delayed,
a
lot
of
the
hot
topic
information
I'd
like
to
hold
on
to
until
they
are
present.
A
So
my
agenda
bash
is
to
jump
forward
to
the
development
projects
section
and
then
we'll
jump
back
to
the
beginning
after
we.
B
A
while
for
you
to
cut
in
and
try
again
sorry
yeah,
I'm
just
looking
for
the
notes
and
the
link
in
the
data
tracker
for
this
meeting
doesn't
seem
to
lead
me
to
a
notes.
Page
that
looks
correct.
A
A
All
right,
so
I'm
going
to
start
in
with
a
discussion
of
the
data
tracker
at
that
point
under
development
projects
help
me
keep
an
eye
out
for
when
jay
and
lars
join,
hopefully
they'll
turn
on
video
and
it'll
be
dead
obvious.
A
So
we
had
several
releases
since
the
last
call
the
major
things
that
happened
where
we
shifted
the
data
tracker
codebase
to
run
on
python39,
have
production
running
on
three
nine.
It
is
three
nine
and
not
a
more
recent
version
of
python,
because
that
was
what
was
relatively
straightforward
for
glenn
to
install
on
the
system
was
that
was
beyond
three
six.
A
We
added
support
for
the
groups
and
streams
needed
for
the
rfc
editor
model
and
added
them
to
the
menuing
links
place.
Support
for
the
roles
are
all
in
place.
What's
not
yet
in
place
are
ballots
for
our
sab
for
the
new
editorial
stream.
When
we
work
this
out
for
the
the.
A
Irtf,
so
it
shouldn't
be
too
difficult
to
make
it
available
to
r
sub,
but
it's
not
a
trivial.
A
trivial
lift.
A
A
Some
of
the
things
that
are
already
in
there
are
affixed
to
the
issue
that
we
ran
into
where
old
draft
versions
have
a
chunk
of
text
on
the
page
that
you're
looking
at
that
claimed
that
they
were
active,
that's
been
replaced
with
something
that
is
a
little
bit
more
truthful
about.
The
current
state
of
the
document
points
out
what
that
was
active
at
the
time
that
it
was
revised.
A
So
a
bunch
of
small
fixes,
we've
got
a
number
of
prs
that
are
in
process
that
we
hope
to
bring
in
fairly
soon
there's
a
list
of
them
in
the
notes.
A
We
are
going
to
start
back
into
the
time
zone,
aware
time
stamp
work
later
this
week.
The
development
team
will
be
meeting
to
re-familiarize
ourselves
with
the
problem
and
the
work
that
was
done
to
date
and
then
start
brainstorming
on
different
approaches,
and
we
can
take
than
the
one
that
we
had
started
down
with
entering
before,
so
that
we
can
possibly
get
through
this
transition
without
a
four-hour
outage.
As
the
previous
plan
had
entailed.
A
A
A
C
A
A
D
D
I
don't
know
what
fighter
version
was
updated
to
3.10
there's
some
upcoming
ongoing
work
with
springload.
I
have
added
a
link
to
all
those
issues
there
I'll
move
on
to
xml
to
rx6.
There
are
no.
I.
A
Have
one
quick
question
on
the
website
I
saw
in
some
of
the
communication
with
spring
load,
more
discussion
of
single
source
for
the
noel
text.
A
Is
that
landed
on
a
design
or
is
it
still
is
the
conversation
still
at
the?
We
need
to
figure
this
out
level.
D
A
Because
we,
when
one
of
the
things
to
remember,
is
we
want
the
data
tracker
to
and
and
places
like
the
wikis
and
whatnot
to
be
able
to
find
that
same
chunk
of
text
and
reuse.
It.
B
Yeah
I'll
this
is
greg
I'll
say
that
that's!
I
didn't
understand
that
as
a
requirement
in
before.
A
Id
guidelines,
the
other
places
where
the
data
tracker
has
places
where
it
presents
them.
A
So
the
shepard
report,
for
example,
is
currently
being
put
into
wikijs,
and
the
data
tracker
is
supposed
to
present
it
to
people
so
that
they
can
edit
directly
into
it,
and
we
need
to
have
an
answer
for
you
know
having
just
one
copy
of
these
things
and
not
having
to
keep
other
places
in
sync.
A
A
D
So
I'll
move
on
to
xml
to
rfc,
there
are
several
releases.
You
can
read
the
release
notes
there.
D
Major
changes
are
support
for
python
3.10,
fixed
non-latin,
name
rendering,
and
I
have
updated
the
docker
images
and
writing
that
script
right
now.
It
makes
all
the
images
really
quick,
especially
on
new
mac
machines,
upcoming
work,
the
better
one
major
change
would
be
dropping
the
support
for
python
3.6.
D
E
Hey
casara,
I
have
a
question
for
you,
this
number
792
about
use
bib.itf.org,
I'm
wondering
if
that's
going
to
help
when
we
use
that
option
add
x,
I
include
if
it's
right
now
it
puts
in
the
urls
for
the
citation
library
for
us
when
we're
converting.
I
can
I
don't
know
if
this
is.
It
requires
a
separate
ticket
or
not.
E
D
This
this
changes-
I
I
didn't
so
one
except
rc.
There
are
default
resources
for
citations
and
this
changes
to
add
bit.itf.rg
as
the
main
one
they
all
citations
should
work,
because
we
will
be
setting
up
three
direct
predictions
when
we
move
to
big.idf.j.
E
A
So
ryan,
I
see
you
joined.
We
have
jumped
forward
to
give
time
for
jay
and
lars
to
join
before
we
go
through
the
the
hot
topics
we
are
at
the
mail
archive
and
registration
system.
Part.
If
you
just
want
to
speak
to
it,
you
can
type
in
notes
later.
F
Sure
there
aren't
any
updates
for
the
mail
archive
registration.
I've
been
working
on.
F
The
feature
to
switch
back
and
forth
or
switch
from
remote
to
on-site
should
be
deployed
today.
A
So,
on
yang
catalog,
the
end
catalog
project
had
a
large
series
of
major
releases
over
this
last
three
weeks.
They
sent
a
fairly
good
summary
to
the
mailing
lists
for
for
yang
catalog.
Eric
was
will
put
together
a
report
at
some
point.
He
wasn't
able
to
get
it
in
by
the
meeting
today
because
of
the
some
cisco
is
having
its
big
open.
A
Meeting
this
week,
he's
also
worked
out
a
work
plan
for
our
contract
with
pantheon
for
the
rest
of
the
year
and
expects
that
he'll
have
that
he'll
be
able
to
show
us
that
in
in
the
next
few
days,
so
we
can
track
what's
going
on.
A
I
entered
a
few
notes
about
what
we've
been
seeing
with
web
analytics.
My
perspective
is
pretty
dataset
data
tracker
centric
greg.
Do
you
have
anything
that
you
want
to
add
to
this?
That's
more
general.
A
A
A
A
A
Misinformed
about
how
it
wanted
to
construct
its
url
or
was
attempting
to
be
malicious
and
the
agent
that
presented
the
request
goes
ahead
and
runs
the
javascript
that
comes
back
in
the
response,
so
the
request
gets
recorded
into
the
analytics,
and
there
is
enough
of
that
that
it's
hard
to
see
the
real
traffic
separated
from
from
from
that
garbage
traffic
and
we're
needing
tea.
A
At
least,
I
would
like
to
find
a
way
to
filter
those
things
out
so
that
we
can
look
at
them
separately.
A
All
right,
real,
quick
through
the
tail
end
of
this,
I
still
don't
see,
jay
or
lars,
we'll
just
go
back
to
the
top
of
the
meeting
without
them.
In
a
moment,
we've
had
no.
A
On
the
any
new
actions
on
on
the
database
review,
I
say
that
I
think
glenn
may
have
done
a
recheck
of
the
recommendations
that
they
made
last
and
I
think
I've
got
a
piece
of
mail
that
I
need
to
follow
up
on
from
glenn.
That
talks
about
our
next
steps
on
that
zx
security
has
been
working
their
way
through
the
statement
of
work
for
the
web
services
running
on
ietfa
and
sending
reports
we've
been
addressing
the.
A
More
pressing
issues
that
they've
been
reporting
as
they've
been
coming
in
and
we
are
queuing
up
work
for
some
of
the
ones
that
are
less
pressing.
There
hasn't
been
anything
particularly
massive.
A
A
A
Finish
the
cycle
of
remediation
of
the
the
small
issues
that
we've
that
they've
identified,
we
do,
as
said
before,
indeed
published
the
revised
reports
for
all
of
these
things.
A
Time
zone
where
times
temp
transition,
so
let's
go
ahead
and
roll
back
up
to
the
front
of
the
agenda,
we'll
try
to
catch
jay
and
lars
up
separately
in
the
hot
topics,
the
big
one,
rfc
production
blocking
issues.
We
have
nothing
and
thank
you
alice
for
the
the
nod
towards
cazar's,
quick
work.
A
A
I've
glenn
has
put
together
a
set
of
zone
files
and
redirect
configuration
based
on
data
that
I
pulled
off
of
the
existing
service
and
the
information
that
we
had
gathered
at
the
tools
transition
plan.
A
He
has
those
ready
for
me
to
review.
I
plan
to
review
them
later
today
and
assuming
we
find
no
issues,
they'll
be
ready
to
turn
on
as
soon
as
we
have
this
bib
xml
service
moved,
and
what
this
means
is
that
the
tools.itf.org
homepage
is
going
to
start
redirecting
to
authors.ietf.org
xml
to
our
the
xml.
A
Rsc.Tools.Itf.Org
is
going
to
start
redirecting
into
author
tools.
Other
subsites
of
tools.ietf.org
are
going
to
redirect
as
according
to
that
tools
transition
plan,
even
though
we
have
signaled
this
to
the
community
for
well
over
a
year.
I
expect
that
there
will
still
be
shock
and
surprise
when
the
change
happens.
A
D
B
I
just
yeah
I
put
this
as
I
was
most
not
mostly,
but
partly
tongue-in-cheek
in
the
in
the
chat,
but
I
do
think
that
some
sort
of
persistent
post
that
summarizes
the
changes
the
time
would
be
be
a
useful
reference
to
point
people
to
when
the
questions
come
up
about
what.
Where
did
you
move
my
cheese?
B
Okay,
yeah
I'll
think
some
more
about
that,
but.
A
For
the
data
tracker
that
I
mentioned
before
is
a
change
to
the
models
so
that
we
explicitly
model
who
attended,
which
session
medico
will
tell
us
at
the
end
of
the
session
who
attended,
they've
already
been
telling
giving
us
blue
sheets,
which
just
have
names
instead
or
at
least
in
addition
to
at
the
beginning,
we
will
start
actually
getting
a
foreign
key
relationship
between
session
and
person
so
that
we
could
construct
those
blue
sheets
ourselves
and
then
use
this
for
nom
com
calculations,
numcom
eligibility
calculations
going
forward
in
the
process
of
putting
this
together
and
researching
the
the
the
functions
for
the
new
numcom
eligibility
calculations.
A
We
discovered
that
there
is
a
bit
of
a
disconnect
in
the
code
and
in
at
least
the
current
leadership's
heads
around
what
counts.
A
A
So
I
am
anticipating
that
we
will
continue
to
use
the
current
calculations
with
the
full
understanding
of
you
know
the
calculations
that
we
had
before
with
the
understanding
that
just
paid
was
sufficient
and
that
we'll
end
up
with
an
rsc
that
clarifies
and
we
can
shift
over
to
where
we're
whatever
that
rsc
clarification
results
in
for
for
the
rules.
A
A
Yeah,
one
of
the
things
that
zdx
security
pointed
out
to
us
is
that
our
certs
and
configuration
for
our
web
services
allow
the
use
of
tls-1011
and
I
started
to
communic.
I
started
a
conversation
with
the
isg
about.
A
Whether
or
not
we
should
turn
that
off
and
if
we
needed
to
tell
anybody
ahead
of
time,
I
was
hoping
to
get
the
final
feedback
on
how
that
conversation
went
in
the
isg.
On
this
call,
I
will
follow
up
with
eric
and
lars
and
find
out
what
the
isg
thinks
we
need
to
do
with
respect
to
telling
anyone
or
not.
I
think
it's
pretty
clear
from
the
first
part
of
the
conversation
that
everybody
on
the
isg
is
just
fine
with
with
it
with
it
being
turned
off.
G
Do
you
have
any
any
stats
from
our
logs
how
much
use,
if
there's
any
use.
A
Yeah
there
is
a
small
amount
of
use
most
it's
easiest
to
get
that
from
looking
at
cloudflare's
dashboard
right,
the
it
is
not
zero,
but
it's
also
very
small
compared
to
tls
one.
Two
and
above.
G
So
could
it
be
old,
bots
or
something
say
again,
could
it
be
old
web
bots
or
something.
A
I
wish
there
was
somebody
from
the
isg
here,
so
we
have
an
rsc
that
deprecates
these
things
and
tells
people
to
quit
using
them
that
we
we
published
as
an
ietf
consensus
document.
H
A
H
H
D
A
A
Our
zoop
service
is
now
fully
deployed.
We
haven't
seen
anybody
complain
about
the
deployment,
yet
anybody
on
the
call
has
has
seen
complaints
that
I
haven't
please.
Let
me
know.
A
Medico
has
been
looking
into
integrating
the
midco
chat
directly
with
zulup.
There
are
some
design
questions
around
how
to
use
the
api
we
engaged
with
the
zoo
community.
Earlier
today
on
getting
a
better
story.
They
pointed
us
to
some
dark
corners
of
the
documentation
that
we
hadn't,
spotted
before
that
looked
fairly.
Promising
should
be
able
to
report
in
a
few
days
about
whether
or
not
this
integration
is
going
to
be
as
easy
as
we
anticipate.
A
There
was
an
effort
between
the
last
tools
call
and
this
one
to
update
the
configuration
of
the
working
group
mailing
lists
to
include
the
global
white
list
for
those
working
groups.
It
didn't
have
it
configured,
we're
also
going
to
do
a
little
bit
of
work
with
the
secretariat
to
make
it
easier
for
them
to
periodically
check
this.
A
My
suggestion
is
once
a
month
to
make
sure
that
the
working
group
lists
have
have
this
list
configured
and
we've
identified
the
set
of
remaining
lists
that
don't
have
the
global
white
list
configured
to
in
there
allow
these
non-members
configuration
and
we'll
be
going
through
them
manually,
one
by
one
to
determine
whether
or
not
they
should
and
and
adding
adding
it
if
they
should.
A
So
these
turn
out
to
be
things
like
the
teams
for
previous
meetings.
The
sisters
list,
things
like
this
right.
A
And
we've:
okay:
we've
got
two
other
things
here:
jay
initiated
a
survey
for
the
tools
workshops,
the
intent
was.
The
survey
would
close
at
this
call
I
was
hoping
jay
could
give
us
a
feel
for.
A
A
Authorization
configuration
matches
what
is
in
the
document
that
we
have
that
talks
about
how
we
plan
to
use
that
wiki
that
documents
currently
a
google
document
that
hasn't
been
widely
advertised,
and
I'm
asking
we'll
be
having
a
conversation
with
jay
a
little
bit
later
about
when
that
document
can
be
more
widely
distributed,
and
more
people
have
a
chance
to
to
take
a
look
at
it.
The
essence
of
it
is
that
we've
set
things
up
to
where.
A
A
A
The
plan
for
quite
some
time
has
been
that
we
will
just
move
the
important
bits
by
manual.
Labor,
volunteer,
labor,
unimportant
bits
would
get
archived.
My
intent
was
to
archive
them
in
by
making
the
track
instances
available
as
a
docker
image.
A
There's
an
ongoing
conversation
about
whether
or
not
an
automated
conversion
of
the
track
wikis
into
a
wiki
js
instance
that
could
just
be
left
up
as
an
archival
ins.
You
know
read-only
instance
makes
sense.
A
I
have
concerns
about
the
fidelity
of
these
automated
translations.
What
we
saw
of
the
move
of
the
track,
wiki's
nt,
the
github
wikis,
doesn't
leave
me
feeling
comfortable
that
we
won't
lose
a
great
deal
of
information
at
the
very
least
in
things
like
the
structure
of
tables
in
in
such
a
process.
G
A
G
G
A
Okay,
that's
what
we
had
on
our
agenda,
we're
now
to
the
open
microphone
part
of
this.
Anybody
have
any
anything
that
they
would
like
to
discuss.
We've
got
15
minutes
left.
If
we
want
to
use
it
or
I
can
give
that
back
to
you
for
the
rest
of
your
days,.
H
I
I
Explain
what
I
was
after
here:
there
are
some
people
who
will
have
to
to
watch
what's
going
on.
Where
should
they
look.
I
A
And
I
will
see
you
at,
I
think
we've
got
one
yeah.
We've
got
one
more
of
these
before
we're
in
philadelphia.
So
we'll
talk
to
you
soon.