►
From YouTube: IETF-TOOLS-20220111-1900
Description
TOOLS meeting session at IETF
2022/01/11 1900
https://datatracker.ietf.org/meeting//proceedings/
A
A
B
B
B
All
right
we'll
go
ahead
and
get
started.
Thank
you.
Everyone
for
joining
I'm
seeing
a
few
names
on
the
the
roster.
I
don't
recognize
for
those
of
you
that
have
not
been
to
one
of
these
before
this
is
a
coordination
meeting
between
the
people
that
are
developing
the
tools
and
the
folks
they're
deploying
the
tools
and
the
larger
uses
of
the
tools
like
the
rpc
and
iana
in
groups
like
that.
B
B
B
E
B
So
folks
should
be
aware
of
the
important
dates
for
ietf
113
as
we're
talking
about
making
this
fairly
major
transition.
It
looks
like
that
we've
got
a
narrow
window
between
when
the
schedule
is
published
and
we
get
into
the
the
crunch
of
draft
submissions.
So
we'll
have
to
choose
our
cut
over
date
fairly
carefully
in
that
window
or
consider
what
it
would
mean
to
wait
to
move
to
the
new
instance
until
after
1
13..
I
would
prefer
not
to
wait
if
we
can.
B
F
Yeah,
I
didn't
want
to
interrupt
anything
yeah,
just
I'm
basically
just
here
to
mention
that
this
becomes
more
and
more
relevant
when
we
have
the
new
rc
editor
model,
because
we
have
some
more
waiting
lists
then,
and
for
those
it's
especially
important
to
archive
them,
but
I'm
I
think
the
timeline
is
still
not
super
urgent.
I
don't
know
what
your
timeline
is
for
me
and
three,
but
for
the
new
rfc
editor
model.
It's
so
I
don't
know
a
couple
of
months,
maybe
half
a
year
where
we
until
we
actually
need
most
of
this
probably.
B
Okay,
so
I
would
like
to
propose
that
when
we
do
make
this
move,
that
we
don't
hold
it
behind
mailman
three,
that
we
actually
move
the
rsc
editor
lists
into
the
current
way
we
do
mailman.
I
don't
think
we'll
have
name
collisions.
That
would,
which
would
be
the
main
thing
that
would
suggest
that
we
wait
for
melon
three
and
then
move
them
to
mailman
three
as
we're
moving
everything
else
to
mailman
three
as
a
second
step
glenn.
Do
you
see
any
major
problems
with
taking
things
in
that
order?.
B
I
have
to
apologize
for
the
leaf
blower
my
background.
I
hope
my
microphone
isn't
picking
it
up
as
well
as
my
ears
are
okay.
So
let's
take
that
as
a
tentative
plan
and
unless
somebody
objects
to
us
moving
the
rsc,
editor
or
lists
into
the
same
processing
that
the
rest
of
the
itf
lists
are
we'll
cue
that
up
for
action,
probably
after
we
get
the
new
server
up.
B
Our
subversion
track
conversion
is
moving
close
to
its
end.
We
have
several
simple
projects
that
are
ready
to
move.
Hopefully
we
will
get
them
moved
this
week.
The
few
working
groups
that
had
track
instances
that
they
were
using
to
use
for
document
development
are
those
repositories
will
be
ready
this
week.
There
are
three
of
them.
Two
of
them,
I
believe,
will.
Let
me
move
this
week,
the
other
one
there's
still
an
outstanding
question:
alexi
you're
here
the
mail
exchange
that
we
had
with
john
clinton.
B
B
B
B
I
have
the
the
timelines
that
that
we're
currently
expecting
in
here.
As
always,
these
things
tend
to
be
a
little
bit
more
complicated
than
we
expect.
So
I'm
I
feel
it's
likely
we'll
slip
a
little
bit
off
of
early
february
and
into
late
february
for
the
data
tracker,
but
we're
going
to
shoot
for
that.
B
B
The
long
pole
is
still
the
web
xml
replacement
service,
which
I
believe
I
talked
about
later,
the
it's
close,
but
we
we,
we
still
have
a
ways
to
go
before
it's
done,
but
our
plan
is
still
to
actually
stop
allocating
tools.itf.org,
replace
xml2rc.tools.itf.org
with
author
tools
before
we
get
to
ietf
113.
This
means
people
in
general
are
going
to
be
using
author
tools
instead
of
the
xmlrc.tools.iftf.org
interface.
B
And
I
guess
the
things
that
I
want
to
call
out
that
are
left
on,
that
tools,
transition
plan
that
we
may
not
finish
before.
We
actually
de-allocate
the
you
know,
stop
delegating
the
domain
is
the
replacement
for
daily
dose
and
possibly
the
replacement
for
bap.
Although
I
think
we
have
an
interim
plan
in
place
where
we
can
stand
up
an
instance
of
map
with
its
current
web
interface
on
on
our
servers
without
too
much
difficulty.
B
H
B
B
If
you
follow
the
the
the
plan
we
have
right
now,
the
the
jabber
room
will
be
bridged
to
one
of
the
two
rooms
that
is
created
for
the
working
groups
and
at
least
for
the
short
term.
Medico
is
still
connected
to
jabber
and
we
will
be
talking
to
miyako
in
the
future
about
having
them
connect
to
zulip
directly.
F
No
worries
I
wanted
to
answer
the
question,
so
I
think
both
the
isg
and
the
iab
a
year
ago
committed
to
use
like
for
like
the
next
coming
year
and
then
decide
with
the
next
slate.
What
to
do
then?
So
I
think
if
we
want
to
transition,
it
would
be
better
to
do
that
in
in
march,
which
is
before
march
when
we
have
the
new
group
of
people
ready.
I
also
see
at
least
for
the
isg,
that
slack
is
used
quite
heavily
so
effectively
that
works
pretty
well
for
the
ihd.
F
I
wouldn't
want
to
interrupt
that.
I
personally
have
no
experience
with
sulip,
so
I
think
it
would
be
very
helpful
for
me
and
for
other
ihd
members
to
have
some
kind
of
a
test
set
up
and
get
a
little
bit
familiar
with,
so
that
before
we
switch
over
or
make
a
decision
to
switch
over,
but
in
any
case
I
think
we
need
we
need.
We
need
more
discussion
in
both
groups
when
we
have
the
new
people
for
the
next
term
before
we
can
make
a
decision.
H
H
I
fully
second
maria
on
this
and
especially
being
in
a
complete
virtual
world
right,
and
I
never
met
my
ihd
colleague
for
two
years
and
we
managed
to
get
some
kind
of
community
feeling
through
slack
and
it
would
be
very
hurting
if
we
cannot
move
this
community
feeling
to
zulu
right.
So
it's
not
only
a
tool
issue.
I
guess,
but
a
way
that
slack
is
always
open
whatever.
H
A
B
B
B
Roman
sent
the
announcement
out
that
started
the
clock
for
the
shutdown
of
the
ftp
services.
That's
currently
set
to
happen
on
april
18th.
There's
really
not
much
background
work
that
we
need
to
do
at
this
point.
All
the
redirects
are
in
place.
Pages
have
all
been
changed
to
point
to
the
right
places
when
we
get
to
april,
we
just
turned
ftpd
off
and
and
didn't
deal
with
the
crux
of
of
anyone
that
hasn't
managed
to
migrate
to
other
tools.
B
C
There
was
a
promise
to
take
a
look
at
them
after
a
year
of
operation
and
that
time
has
passed.
So
I
just
wanted
to
raise
the
question
in
the
tools
team
here
about
whether
or
not
there
were
any
unexpected
issues.
From
from
my
perspective,
things
have
been
working
pretty
much
as
we
expected
and
we've
been
able
to
make
some
observations
that
have
helped
us
in
terms
of
the
content.
But
I
guess
that
was
the
first
question
is
the
second
question
or
the
second
item
there
basically
points
out
there.
C
I
think
my
expectations,
sort
of
looking
at
eric
here
and
after
talking
with
roman,
is
that
that
step
would
include
sort
of
letting
the
community
know
about
that.
But
I
wanted
to
see
if
there
were
any
issues
on
the
tool
side
before
going
taking
that
step
and
and
then
I'll
pause
and
see.
If
eric
I
sort
of
put
eric's
name
against
this
item
as
well.
So
he
may.
H
My
only
point
right
I
mean
I
was
using
matamo
before
for
my
own
personal
stuff,
good
tools
and
I
would
love
to
get
this
kind
of
analytics,
specifically,
for
instance,
for
young
catalogue
right
where
we
are
investing
a
lot
of
money
there
and
whether,
if
it's
used
by
one
people
by
bonneville
class
once
a
month
right,
it's
not
worth
it,
and
hopefully
we
listen
to
this,
but
exclusively
it
was
learning.
So
at
some
point
of
time
will
to
get
this
now.
H
The
only
issue
with
the
young
catalog
is
not
only
about
web
pages,
which
is
easy
to
integrate
matamor
with
javascript
or
whatever,
but
also
api,
and
you
know
the
story
right
right,
so
we
need
to
get
some
tooling
around
it.
So
you're,
not
that
trivial
and
now
the
last
part
not
related
to
to
this.
I'm
just
curious
whether
and
I
should
know
whether
those
analytics
are
public
and
I
think
they
should
be
maybe
public
for
everyone
from
the
itf
community
and
whether
we
can
see
this
just
to
avoid
the
privacy
issue
right.
C
I
C
C
B
So
eric
there
was
a
pretty
strong
statement
about
who
would
have
access
to
what
the
analytics
were.
It
was
basically
operator
level
people
in
the
agreement
with
the
community
and
that
we
would
not
be
opening
these
things
up
to
the
two
people
at
large,
specifically
because
of
the
the
you
know,
even
though
we've
done
our
best
to
obfuscate
any
personally
identifying
information
that
would
make
it
into
the
analytics.
F
F
H
B
B
I
also
think
that
we
need
to
do
a
little
bit
more
work
to
come
up
with
a
uniform
way
of
capturing
the
kinds
of
things
that
that
eric
hinted
at
which
the
analytics
tool
won't
report
on
which
are
api,
accesses
and
direct
downloads,
and
things
of
that
nature.
More
weblog
analysis,
work
that
should
become
uniform
across
sites
and
that's
a
goal.
I
don't
know
that
it's
something
that
we'll
see.
F
B
Anything
else
on
the
web
analytics.
I
guess,
greg
one
quick
question:
the
conversations
you
had
with
roman
he
specifically
talked
about.
Were
there
any?
Was
there
any
specific
analysis
that
we
needed
to
go
back
in
and
do
about?
You
know
what
had
actually
been
collected
that
needed
to
be
done,
I'm
not
remembering
any
from
the
agreement,
but
he
would
be
the
person
that
would
have
had
it
on
on
point.
J
J
B
B
B
E
On
other
tools
and
there's
one
release
with
a
few
bug
fixes
on
the
iddif
comparison,
making
it
easy
to
use
and
changing
the
order
of
the
results,
and
then
you
can
have
a
look
at
the
look
at
them
on
the
release.
Notes
upcoming
work
is
the
main
priority
is
getting
this
to
a
production
server,
and
then
I
I
would
look
into
do
the
abn
faster.
B
E
B
On
the
data
tracker,
we
had
a
small
bug,
fix
and
and
minor
feature
release
earlier.
I
guess
it
was
late
last
week
when
we
did
that
release.
We
had
an
another
instance
of
an
issue
that
we
ran
in
into
december,
that
I
talked
about
in
detail
in
the
text
and
I'll
leave
it
mostly
for
you
to
read
the
text,
but
in
short,
we've
for
long
had
a
period
where
anytime,
the
data
tracker
gets
restarted.
It
has
to
warm
up
before
it
starts
serving
requests
at
speed.
B
So
we
have
avoided
that
issue
with
some
careful
restart
work
that
glenn
has
done,
but
we're
now
putting
a
lot
more
priority
on
on
avoiding
it
until
we
can
get
a
little
bit
deeper
into
understanding
it.
There
are
a
lot
of
things
underway
that
are
likely
to
make
things
different,
we're
working
on
putting
the
data
tracker
behind
cloudflare.
I
have
an
instance
of
the
sandbox
running
behind
cloudflare.
Already
I
have
the
secretariat
testing
it.
I
will
send
a
message
out
to
you
to
toolsdiscuss
to
get
more
people
testing
it.
B
So
we
have
a
little
bit
more
insight
into
the
way
that
the
the
tcp
handling
is
happening
as
as
requests
are
coming
in
and
we
are
pushing
on
improving
individual
view
performance.
I've
got
a
prototype
in
right
now
for
caching,
the
menu
content
by
login
that
survived
testing
yesterday
and
last
night
and
is
in
the
queue
for
merged
into
the
next
deployment.
The
next
deployment
for
the
data
tracker.
B
Next
point
on
the
data
tracker
is
that
we
have
an
issue
with
the
way
the
registration
data
is
currently
being
captured.
That
leads
to
saying
that
some
people
are
nom-com
eligible.
That
really
aren't
in
particular,
if
we
have
someone-
and
this
is
an
edge
case-
but
if
we
have
someone
that
signs
up
for
the
hackathon
and
the
meeting
but
only
attends
the
hackathon,
we
will
count
them
as
attending
the
meeting
right
now.
B
B
B
B
B
I
don't
know
if
it's
male
archive
proper,
but
there
is
the
male
processing
chain
will
have
to
be
heavily
touched,
will
have
to
be
essentially
re
rewritten
to
work
with
mailman
3..
There
are
notes
about
that.
If
people
are
interested,
if
you
go
to
the
the
notes
for
the
the
the
mail
processing
workshop
that
we
had
last
year,
you
can
see
quite
a
bit
of
discussion
about
the
things
that
we
will
have
to
update
in
the
regular
mail
handling
chain
in
order
to
make
the
transition
to
mailman
3.
K
Just
real
briefly,
I
want
to
point
out
that,
as
of
113
there'll
be
a
new
requirement
when
you
go
to
register
for
the
meeting,
you
will
first
need
to
log
in
using
your
data
tracker
credentials.
There
are
another
number
of
reasons
for
doing
that.
Some
benefits
it
provides,
but
that's
a
change
from
past
behavior.
B
So
greg
this
might
be
something
to
work
on
communicating
to
people,
especially
for
the
people
that
forget
to
register
and
are
doing
the
last
minute
panic.
Oh
my
gosh.
I
need
to
register
right
this
second,
that
the
way
that
they're
going
to
need
to
start,
if
they
don't
have
a
data
tracker
account-
is
to
create
one.
H
F
I
think
this
is
still
a
discussion,
the
secretary,
but
I
guess,
there's
also
some
kind
of
tooling
support
needed
in
case
we
convert
the
in-person
meeting
to
an
online
meeting
last
minute
and
we
also
need
to
convert
the
registrations.
Somehow
was
that
considered
or
is
there
no?
No
additional
tooling
or
implementation
work
needed.
L
B
H
We
extended
the
contract
with
pantheon
for
one
more
year
and
together
with
the
two
fathers
that
I
wrote,
benoit
and
joe
clark,
we
are
pushing
for
new
features,
you've
seen,
for
instance,
the
seed,
not
the
seed
from
segment
routing,
but
the
siege
from
the
seaboard
working
groups
and
would
be
nice
to
get
a
back
and
forward
transition
or
display
from
the
yang
to
the
seed
and
so
on,
as
well
as
extending
the
api.
Hence
my
interest
for
api
analytics
to
see
whether
it's
correct,
yeah
and
core.
It's
indeed.
B
B
B
That's
not
yet
present
to
show
up
isn't
is
not
the
right
thing
to
do
at
this
point,
but
if
anybody
thinks
otherwise,
please
say
so
now,
otherwise
we're
going
to
be
working
to
schedule
this
thing
in
at
the
next
reasonable
time
to
do
the
the
amount
of
work
that's
needed
to
to
make
the
transition
so
glenn
notes
that
such
a
transition
would
necessarily
happen.
After
we
have
the
new
server
online,
we
will
be
doing
development,
perhaps
in
parallel
on
the
sandbox.
B
B
The
only
places
that
we
would
run
into
trouble
is
whether
or
not
we
can
tell
in
the
mail
chain
at
the
right
places
that
we're
processing
things
that
will
eventually
be
fed
into
mailman
three
versus
into
mailman
two,
as
we
noted
in
the
workshop,
some
of
the
larger
pieces
of
work
will
require
a
complete
rewrite
of
post,
confirm
and
the
work
we're
doing
for
dkim
and
probably
the
ways
we're
handing
things
off
to
to
the
mail
archive
post
confirm
itself
is
still
python
2..
It's
one
of
the.
B
M
Yeah,
if
nobody
has
anything
else,
I
want
us
to
quickly
update
or
maybe
even
discuss
the
bootstrap
five
stuff
a
little
bit.
So
I'm
whenever
I
have
a
few
minutes,
I'm
like
checking
yet
another
template
and
see
if
it
works.
So
this
is
basically
requires
going
for
every
single
template
in
the
data
tracker
and
man
there's
a
lot
more
than
there
used
to
be
when
we
did
the
bootstrap
3
stuff
10
years
ago,
so
it's
slow
going
but
at
least
sort
of
I've.
M
There
was
a
whole
bunch
of
test
breakage
because
of
some
updated
javascript
stuff,
like
the
date
picker
and
the
auto
completion
stuff
that
rendered
completely
different
html
and
that
broke
all
kinds
of
tests,
specifically
the
selenium
stuff-
and
I
I
fixed
all
that
finally,
but
it
took
a
while
over
the
holidays.
Thank
god
there
was
nothing
else
to
do,
but
I'm
I'm
hoping
that
I'm
sort
of
get
this
done
within
a
week
or
two.
M
Hopefully,
the
problem
is
that
it's
it's
a
massive
change
right,
so
everything
looks
slightly
different
and
I'm
sure
there's
breakage,
even
though
the
tests
are
not
breaking
so
I'm
kind
of
wondering
I
mean
the
current
way.
We
release
the
data
tracker.
Is
we
don't
we
don't
really
have
a
development
branch
right
so
ideally
for
this
kind
of
thing,
I
think
we
want
to
have
a
development
branch
where
everybody
else
is
then
also
working
and
testing
their
stuff
on
the
bootstrap
5
version
and
fixes
things
before
we
go
to
production
with
this.
B
You
usually
do
it,
something
that
I
kind
of
did
breeze
through
earlier
is
before
that
we
strap.
Five
branch
comes
in
we're
going
to
get
the
time
zone
where
branch
in
and
that's
going
to
mean
back
porting,
the
the
time
zone,
wear
branch
back
into
the
the
bootstrap
branch,
and
I
I
very
much
agree
that
we
do
this
in
a
a
development
branch.
This
is
well
nick
and
casara
and
jennifer,
and
I
have
been
talking
about
how
we'll
use
github
and
having
you
know,
a
a
development
branch
and
a
release.
B
B
B
So
you
know
I
I
believe
that
it's
going
to
take
nick
a
few
weeks
behind
you
with
the
work
that
you're
doing
on
the
templates
to
go
back
in
in
actual
build
tests
for
the
javascript
that
was
not
tested
at
all
and
that
that
javascript
will
will.
Probably
you
know
that
that
testing
work
will
probably
uncover
quite
quite
a
lot
of
stuff
that
you've
been
discovering
with
the
templates
that
you
just
can't
discover
right
now,
because
there
aren't
selenium
tests.
B
B
M
Painful
because
I
didn't
know
selenium
before
oh
yeah,
but
I
think
I
got
it
to
the
point.
The
only
thing
that
occasionally
breaks
is
one
of
the
ajax
things
that
loads
person
auto
completes,
and
I
don't
know
why
it
works
like
in
in
99
of
the
cases
and
then
one
percent
it
times
out,
and
I
don't
think
it
does
this
on
the
other
branch
interesting.
M
But
then
again
I
didn't
run
the
tests
that
often
there,
so
it
might
just
fail.
There's
no
feel
there
as
well
the
the
other
thing
sort
of
I've,
not
so
I'm
basically
using
the
basic
bootstrap
five
template,
so
I've
not
themed
it
at
all,
which
means
it
looks
basically
completely
different
to
the
current
data.
Tracker,
look
and
feel
into
the
fonts
and
colors
and
everything
right.
It's
it's
looks
like
a
vanilla,
bootstrap
thing.
B
How
so
I
suspect
that
there
are
some
things
that
we
would
want
to
push
it
towards
looking
a
little
bit
closer
to
the
existing
data
tracker,
but
we've
got
this
other
project
that
is
out
for
dealing
with
basic
things
like
colors
and
fonts
inside.
You
know
the
way
that
the
links
are
presented
and
things
like
that
that
we
want
to
apply
across
all
sites
and
that's
ultimately,
what
we
should
be
pushing
this
thing
towards
the
question
that
I've
got
is
with
basic
scaffolding.