►
From YouTube: IETF-TOOLS-20220308-1900
Description
TOOLS meeting session at IETF
2022/03/08 1900
https://datatracker.ietf.org/meeting//proceedings/
A
A
A
A
A
B
C
D
A
A
E
So
robert,
this
is
great.
I
mean
this
is
something
we
can
definitely
talk
about,
but
my
my
conversations
with
alessandro-
and
I
think
we
should
ask
him
this
directly-
is
that
the
expectation
is
that
the
remote
chairs
will
be
able
to
manage
the
queue
in
medico,
just
as
if
they
were
in
person
and
the
expectations
are
in
person.
E
Okay,
I
didn't
understand
when
you
said
there.
I
thought
you
meant
so
the
the
idea
is
that
there
would
be
a
just
to
make
sure
I
understand
in
case
it
comes
up
on
one
of
the
medical
sessions,
the
cases
where
the
group
is
meeting,
but
no
none
of
the
designated
chairs
are
expected
to
be
participating
in
that
in
that
meeting.
A
All
right
we'll
go
ahead
and
start
moving
forward
through
the
agenda.
We
have
one
potential.
We
actually
have
a
a
an
rfc
in
the
I
forgot
what
ti
x
expands
to,
but
essentially
waiting
for
two
years
to
list
you?
Okay,
because
sorry
all
right,
you
I
don't
this
is,
I
think,
the
first
time
we've
seen
something
go
into
ti.
A
F
I
think
at
this
point
we're
waiting
on
feedback
from
sandy
and
john
about
proceeding.
So
it's
not
really.
I
think
kasara's
offered
the
option
and
now
it's
like.
Do
we
take
the
option
or
put
our
publish,
as
is
like
at
what
point?
Are
the
pdf
page
breaks
that
bad
this
one
just
seemed
more
egregious
than
usual?
So
I
think
that's
why
john
was
seeking
a
fix.
A
So
let
us,
let
us
know
for
the
rest
of
you,
haven't,
read
the
issue
that
we've
got
some
shortcomings
with
weezy
print
and
how
much
control
we
have
over
how
it
does
how
it
chooses
to
break
pages.
When
there
are
sections
of
content
that
it
thinks
are
an
unbreakable
block
and
in
this
particular
rsc
it
did
some
unpleasant.
A
For
the
preparation
of
the
new
server
and
the
move,
the
mailing
lists,
I
think
we'll
take
these
as
read.
Unless
anyone
has
any
questions
from
my
discussions
with
glenn,
we
should
be
in
a
spot
where
the
dev
team
can
will
start
assisting
with
testing
of
the
new
server
shortly
after
after
113
as
it
says
here
and
we'll
work
to
have
resources
available
to
do
so.
A
Our
subversion
to
track
conversion,
subversion
and
track
conversion
to
github
project
with
ribose
is
essentially
done
at
this
point.
We're
now
to
the
point
where
ribose
is
supporting
us
and
cleaning
up
rough
edge
cases
that
we're
finding
and
we're
not
finding
the
the
rough
edge
cases
so
much
anymore.
A
A
Contribution
mechanisms
that
we're
expecting
people
to
use,
as
they
suggest
code
that
we
add
those
is
going
to
be
that's
going
to
be
coming
fast
and
furious
over
the
next
couple
of
weeks.
What
you
saw
happen
with
xml
to
rfc
was
a
pretty
good
prototype
for
what
you're
going
to
see
with
the
data
tracker
and
mail
archive.
A
I
didn't
capture
it
here,
because
these
things,
both
of
these
repositories,
are
now
they've
moved.
There
are
all
kinds
of
places
where
we
have
pointers,
including
inside
the
data
tracker
itself,
to
how
do
you
report
bugs,
and
these
are
all
going
to
change,
to
open
a
github
issue
at
the
appropriate
repository.
A
Moving
services
off
tools.itf.org
as
before
the
long
pole
in
this
is
the
bib
xml
service.
You
can
see
from
the
links
that
we
have
in
the
section
below
on
the
bib
xml
service,
that
there
are
quite
a
few
remaining
issues
that
ribose
is
working
on
fixing
for
us.
I
started
converting
adapting
their
deployment
instructions
which
are
rather
generic
to
our
specific
and
deployment
environment,
so
that
we
can
queue
up
an
actual
deployment
of
the
service
on
our
infrastructure.
A
I'm
expecting
that
to
happen.
I
do
not
at
this
point,
think
that
we'll
have
that
deployment
in
place
before
this
ietf
meeting
it
will
likely
come
after,
which
means
that
our
ultimate
shutdown
of
tools.iatf.org,
basically
on
delegating
and
setting
up
a
redirections
for
the
domain,
is
not
going
to
take
place
until
that
time
frame.
A
Everything
else
is
pretty
much
ready
to
go.
I
still
need
to
build
the
final
set
of
redirects
and
we
are
anticipating
that
we'll
make
the
transaction
transition
without
having
an
immediate
replacement
for
bap
or
daily
dose.
Those
will
both
be
projects
that
we'll
pursue
as
schedule
permits,
but
later.
B
We
are
ready
to
allow
working
groups
to
sign
up
for
azul
extreme
and
we're
going
to
announce
that
availability
later
today,
the
working
groups
that
get
back
to
us
by
next
tuesday.
We
are
going
to
do
our
very
best
to
make
sure
that
their
zoop
stream
is
enabled
for
iitf
113,
and
then
the
plan
is
that,
after
the
meeting,
we
will
go
through
the
remaining
working
groups
and
actually
just
create
screens
for
all
of
them,
so
that
working
groups
have
them
by
default.
That's
basically,
it.
A
B
A
G
E
D
A
A
A
A
This
is
probably
a
good
place
for
me
to
interject
that
I
do.
I
am
beginning
to
see
a
plan
for
what
to
do
with
the
track
instances
that
we
eventually
move
out
of
so
we've
already
is.
I
mean
running
no
hitches
are
out
of
track
for
the
data
tracker
and
xml
rfc,
I'm
planning
on
creating
docker
containers
that
contain
working
instances
of
those
track
and
subversion
repositories
that
we
post
as
github
packages.
A
There
are
several
working
group
wikis
in
there
that,
where
the
plan
is
more
than
working
group
group
wikis
in
there,
where
the
plan
is
to
crowdsource
moving
their
content
into
wikijs
once
that
content
is
moved,
I
would
create
similar
packages
for
the
track.
Instance,
that's
been
moved
out
of
so
that
the
atf.org
service
of
track
can
eventually
be
shut
completely
down.
H
A
A
Greg
do
you
want
to
add
anything
to
the
way
the
common
bootstrap
thing
yeah?
So
we
have
been
testing
this
against
the
data
trackers
facelift
branch.
I'll
talk
more
about
the
facelift
branch
in
a
moment
have
found
some
questions
that
we're
going
to
take
back
to
spring
load
about
the
way
they
created
the
the
npm
there's
some
internal
references
that
we
think
are
probably
not
done.
A
A
In
the
interim
between
the
last
meeting
and
this,
we
did
have
to
make
a
few
adjustments
to
cloudflare.
Some
of
the
most
surprising
ones
were
that
many
attempts
to
submit
internet
drafts
were
being
blocked
by
cloudflare
and
cloudflare
saw
them
as
attempts
to
upload
cross
site
scripting
and
xml
insertion
attacks
and
many
other
things
of
that
nature,
and
I
basically
had
to
disable
the
entire
web
application
firewall
for
the
submit
endpoint
and
the
api
endpoint.
A
We
can
take
a
look
later
at
turning
it
back.
You
know
cut
turning
pieces
of
it
back
on,
but
that's
going
to
be
a
a
long
and
slow
process,
as
we
identify
the
rules
that
don't
result
in
a
ridiculously
large
number
of
false
positive
blocks,
and
we
also
need
to
look
at
how
to
make
the
block
experience
better
for
people
who
are
using
the
submit
tool
either
the
web
interface
or,
in
particular,
the
api
endpoint.
A
We
had
a
couple
of
valid
operational
vulnerability
report
reports,
one
of
them
we
addressed
already.
We
had
a
report
that
it
was
fairly
easy
to
if
you
were
able
to
get
your
hands
on
a
password
reset
link
because
of
shared
access,
network
terminals
or
whatever,
because
of
the
length
of
their
validity,
even
after
they
were
used,
we
were
exposing
people
to
at
least
nuisance
of
use,
so
we
modified
the
behavior
of
the
password
reset
endpoint
to
time
out
much
more
quickly
and
to
also
become
invalid.
D
A
Yeah,
the
the
the
the
signal
to
noise
ratio.
There
is
terrible
the
the
we
we
have
about
80
spam
20
people
telling
us
that,
oh,
my
goodness,
you're
exposing
all
of
these
internet
drafts
and
no
really-
and
you
know
we,
but
but
you
know
a
couple
that
came
through
valid.
We
have
a
second
valid
one
in
here
that
is
still
related
to
the
reset
mechanism
that
we'll
be
doing
work
on
over
over
this
next
cycle.
A
A
A
A
The
two
big
pieces
of
upcoming
data
tracker
work
that
we
want
to
focus
on
are
capturing
session
attendance
more
correctly,
so
that
we
have
the
ability
to
correctly
compute
the
set
of
people
that
are
nomcom
eligible
and
finishing,
really
restarting.
The
work
on
making
all
of
our
time
stamps
time
zone
aware
and
doing
finishing.
A
major
facelift
effort
that
lars
started
on
removing
our
dependencies
on
bootstrap
3
and
a
lot
of
other.
A
G
A
A
So
as
the
tools
team,
we
can't
just
arbitrarily
decide
to
go,
do
things
that
are
changes
to
the
vocabulary.
We
have
ostensibly
this
tmc's
authority
to
make
some
changes.
It
looks
like
we've
been
making
some
good
progress
there,
that's
going
to
lead
to
changes
in
the
best
documents
that
we
can
then
make
changes
in
in
the
code,
but
in
particular
we're
waiting
for
some
authoritative
declaration
of
what
the
grammar
changes
are
going
to
be
as
we
renormalize
the
grammar
to
deal
with.
A
You
know
what
things
can,
what
in
lines
can
land
inside
what
blocks
so
that
that's
more
universally
normalized
and,
and
things
like
that,
so
these
things
have
not
been
languishing
from
a
lack
of
resource
perspective,
coding,
recoder
resource
perspective
as
much
as
they
have
getting
answers
to.
You
know
what
it
is
that
the
the
code
should
actually
go
down
based
on
on
some
process.
G
Yeah,
since
we
are
on
github,
it
might
be
useful
to
to
have
some
labels
for
the
state
that
these
tickets
are
in,
but
because,
right
now
it's
really
daunting
and
knowing
some
some
of
this
is
waiting
on
on
seven,
nine
and
one
base.
Some
of
this
is
waiting
on
understanding
the
problem
in
the
first
place
and
so
on.
So
people
could
maybe
focus
on
contributing
more
to
those
various
triangular
stand
problems
and
so
on.
A
D
A
So,
as
we
mentioned
last
month,
we
have
the
data
tracker
security
review
report
from
zx
since
last
month.
After
further
conversations
with
jay
we're
thinking,
we
will
go
ahead
and
have
them
retest
and
I'm
talking
to
them
about
the
scheduling
for
the
recap,
and
that
will
result
in
an
updated
report,
will
be
a
little
bit
easier
for
us
to
frame
when
we
publish
it.
A
We
started
work
with
sirius
open
source
on
reviewing
our
database
systems,
focusing
first
on
the
data
tracker.
As
part
of
that
we
re-enabled
the
performance
schema
on
the
production
machine.
I
was
watching
fairly
closely.
It
had
a
measurable
bit
nearly
negligible
effect
on
the
overall
processing
time,
at
least
from
the
data
tracker's
perspective.
A
A
Move
to
the
refresh
of
ietfa
there's,
we
don't
want
them
to
be
in
the
middle
of
testing
when
that
move
happens,
and
there
is
a
reasonable
question
about
how
much
of
their
testing
would
be
invalidated
if
it
were
done
on
the
older
system,
so
we're
working
that
out
with
them
we're
currently
on
their
schedule
for
april.
We
may
need
to
push
that
back
into
into
at
least
may
and
as
we
figure
out,
what
the
cut
over
for
ietfa
is
really
going
to
look
like.
A
A
We've
been
preparing
for
the
rfc
editor
model
transition,
should
it
go
through
and
roughly
the
shape
that
the
draft
that
is
going
through
the
approval
processes
at
the
moment
lands
it's
going
to
be
fairly
easy
and
quick
to
add.
The
groups
set
up
roles
in
the
groups
and
shut
down
the
the
groups
that
are
are
shut
down
by
those
docs,
so
the
presence
for
those
groups
will
appear
fairly
quickly.
A
A
So
I
think
what
I'm
going
to
do
after
discussions.
I
started
discussions
of
this
with
several
people.
A
little
bit
earlier.
Ism
will
repurpose
the
existing
rsc
editor
group
to
be
a
top
level
group
and
not
really
have
any
members.
You
know
no
roles,
it
will
be
a
container
that
will
contain
the
r
slag
r
sab
and
rpc
as
children,
and
that
will
be
the
mechanism
where
they
hang
under
the
menus,
as
things
under
this
group
are
all
grouped
together.
A
A
A
E
Updated
the
text
there
to
hopefully
make
the
the
topic
a
little
bit
more
well
defined.
So
I
just
I
just
discovered
this
week
that
when
you're
on
a
group's
about
page
in
in
data
tracker-
and
you
click
on
the
link
to
go
to
the
data-
sorry,
the
java
log
for
that
group
that
you
actually
redirected
to
this
page
on
the
www
site,
which
talks
about
group
chat
in
general
and
then
from
that
page,
it's
possible
to
get
to
an
index
page
of
all
jabra
logs.
E
But
it's
not
currently
obvious
anyway.
This
I
I
don't
recall,
but
this
was
sort
of
unexpected
for
me
and
I
just
I
don't
recall,
couldn't
find
any
discussion
about
the
redirect.
So
I
wanted
to
see
if
it
was
something
that
people
had
some
history
on,
if
it's
still
the
currently
desired
behavior
and
or
if
there's
a
way,
we
ought
to
make
the
direct
links
to
the
java
logs
more
visible.
C
A
J
J
A
J
C
A
D
A
C
The
only
other
thing
I
have
is
it's
great
to
see
stuff
on
github,
specifically
the
data
tracker.
I
think
that
was
a
huge
lift
and
it's
going
to
make
so
many
things
easier.
I'm
already
like
excited
about
using
git
diff
instead
of
a
git
merge
instead
of
svn
merge,
which
is
a
pain.
So
this
is
this
is
excellent
work.
Thank
you
guys.