►
From YouTube: IETF-TOOLS-20230711-1800
Description
TOOLS meeting session at IETF
2023/07/11 1800
https://datatracker.ietf.org/meeting//proceedings/
A
C
B
A
We're
a
couple
of
minutes
in
we'll
go
ahead
and
start
I
am
expecting
Jay,
at
least
let's
figure
people
will
be
joining
as
we
go
along.
A
This
is
a
tools
team
meeting
it's
being
held
as
an
interim.
The
meeting
recording
will
be
posted
to
YouTube.
Keep
that
in
mind
as
we're
going
through
the
meeting.
If
you
can
share
video,
please
do
share
a
video
we'd
like
to
make
all
of
these
sessions
as
much
like
meeting
around
the
table.
As
as
we
can.
A
A
Again,
hearing
nothing
so
there's
been
a
flurry
of
activity
on
the
tools
discuss
list
as
more
people
are
running
into
the
issues
with
the
chair
and
group
male
aliases
failing
to
deliver
particularly
to
users
of
Gmail.
A
We
are
attempting
to
accelerate
the
rework
of
post-confirmed
e,
which
is
the
tool
that
we
have
to
address
this
to
both
do
a
better
job
at
not
breaking
dkim
signatures,
which
it
will
do
in
a
few
cases
now
and
to
extend
the
demarc
rewriting
into
the
draft
end
group
aliases.
A
It
is
a
a
big
lift
to
move
from
the
python
2
using
the
mailman
python
2
libraries
directly
to
wrapping
the
use
of
the
libraries,
probably
by
avoiding
them
completely
and
just
using
the
mailman
T
command
line
options
to
get
the
things
that
we
need
the
rest
of
it.
The
move
to
Python
3
will
be
immediately
beneficial
because
we'll
get
the
much
more
advanced
mail
handling
libraries
in
the
Python
3
standard
Library
compared
to
python
2..
Anybody
have
any
questions
about
that.
One
for
the
moment.
A
All
right,
the
next
thing
to
report
on
is
where
we
are
on
moving
our
domains
into
cloudflare.
All
of
the
domains
that
are
listed
in
the
card
in
that
link
are
both
they're
hosted
at
cloudflare,
both
as
the
registrar
and
the
primary
DNS
provider.
A
We
have
as
we
made
this
transition
went
through
a
period
where
the
each
Zone
went
unsigned
for
a
few
days
and
then
became
signed
later
with
a
much
more
modern
signing
algorithm.
A
This
went
very
smoothly.
The
lack
of
signature
went
almost
unnoticed.
We
did
get
one
inquiry
from
someone.
That
was
just
curious.
Why
we
didn't
do
the
follow
the
path
where
we
kept
the
zones
signed
through
the
Transitions
and
we're
helping
to
explain
what
was
in
the
way
so
that
in
the
future,
the
state
of
what
is
available
to
you.
A
And
then
we
were
running
into
issues
with
moving
off
of
a
very
old
algorithm
for
the
signature
that
we
had
so.
D
E
A
Putting
domains
into
cloudflare
and
enabling
the
cloudflare
is
the
DNS
primary.
We
moved
many
of
the
names
in
the
zones
to
the
proxies
all
the
names
that
were
primarily
related
to
http
https
that
had
an
unintended
consequence
for
some
of
the
bear
domain
names
where
we
found
that
there
were
people
using
FTP
and
rsync
against
the
bear
domain.
A
Name,
we've
been
addressing
those
as
we've
found
them,
guiding
people
to
using
names
that
aren't
being
proxied
through
cloudflare
and
providing
better
documentation
for
what
to
do
with
these
alternate
access
mechanisms
going
forward
as
we
make
it
through
the
it
transition.
That's
upcoming.
These
services
are
going
to
be
on
completely
different
machines
using
a
bear.
The
bear
domain
name
for
them
isn't
isn't
going
to
work
so.
A
A
They've
been
things
like
the
RPC
staff
getting
challenged
because
the
much
of
the
interaction
with
the
the
scripts
that
they
had
looked
like
SQL
injection
attacks
to
the
default
web
application,
firewall
rules,
and
we
just
tuned
those
rules
away
for
people
that
were
were
logged
in
so
we
are
also
still
working
towards
restoring
digital
identity
used
to
be
Affiliates
as
the
secondary
DNS
providers.
A
This
is
something
that
cloudflare
advertises
that
we
can
do,
but
it
is
not
yet
working.
So
we
have
an
active
ticket
open
that
we're
tracking,
with
cloudflare
and
working
with
digital
identity.
To
get
this
in
place
for
all
of
all
of
our
domains.
A
A
A
For
the
next
topic
archiving
the
older
meeting
wikis
such
as
the
older
docu
wikis,
that
are
hanging
off
the
registration
website,
Alexis
and
I,
have
been
working
to
make
sure
that
these
are
fully
ingested
into
the
internet
archive.
That's
the
the
plan
for
how
these
things
will
be
archived,
we're
very
close,
there's
a
class
of
of
assets
that
had
not
been
scraped.
The
last
time
Alexis
and
I
looked
at
it
and
she
was
looking
at
what
she
needed
to
poke
at
the
archive
to
get
them
to
be
scraped.
A
I'm,
not
planning
to
report
on
this
again
at
the
next
meeting.
Unless
there's
a
problem
you
can
assume
by
the
time
we
get
to
the
next
one
of
these
that
this
is
just
done.
A
G
A
F
A
F
B
F
Yeah,
but
the
new
one
right,
not
every
page
I
mean.
Of
course
we
have
an
IG
private
Wiki,
which
is
fine
for
the
multiple
reason,
but
the
archive,
that's
what
I'm
I
meant
from
the
previous
one
is.
Everything
has
been
converted.
I
know
that
many
nodes
I
mean
the
informal
notes
has
been
converted
for
sure.
G
A
All
right,
because
Sarah
you
want
to
Talk
briefly
about
the
IB
website
transition.
C
Yep,
an
IAB
for
new
library
website.
That's
temporary
website
available
right
now,
so
we
can
migrate
things
from
the
website.
C
A
Yeah,
so
the
we're
just
starting
work
on
transferring
the
appeals
out
of
the
WordPress
instance.
The
the
old
ID
website
is
using.
The
structure
of
those
appeals
is
irregular.
So
there's
a
bit
of
modeling
decision
to
make
on
how
these
will
be
represented
inside
the
data
tracker
they're
not
going
to
get
moved
before.
117
I
suspect
that
this
will
happen
in
the
middle
August
time
frame
and
it's
a
precondition
for
switching
to
the
new
IAB
website.
A
So
I
suspect
that
at
the
earliest,
the
switchover,
at
least
for
the
parts
that
rely
on
the
data
tracker,
would
have
to
wait
until
the
end
of
August
I.
Don't
know
what
the
current
plan
for
moving
the
rest
of
the
content
is
when,
when
the,
when
that's
expected
to
to
be
done,
Liz
or
Cindy,
do
you
have
a
feel
for
that?
Yet
so.
G
Yesterday
was
really
the
first
time
that
I
had
actually
had
a
chance
to
start
moving
anything
over,
because
this
was
delivered
right
as
a
bunch
of
meeting
deadlines
were
hitting
moving.
The
content
itself,
I
would
expect
would
be
maybe
a
couple
of
weeks.
The
bigger
issue
is
that
there's
a
bunch
of
content
that
the
IAB
needs
to
review
and
possibly
rewrite,
and
that
will
take
longer.
G
A
And
it's
probably
in
August,
September
kind
of
reveal
is
my
rough
feel:
go
ahead,
Mallory
just
jump
in,
don't
don't
bother
with
the
queue.
H
Perfect
thanks
yeah
I
mean
I'm
now
the
rat
from
the
iib,
the
tool
scene
I've.
Second
time
joining
you
all,
maybe
we'll
get
to
have
face
to
face
time
in
117,
just
to
get
to
know
each
other
better,
but
I'm
taking
notes.
So
this
has
been
a
helpful
update.
I
have
also
met
with
Miriam,
just
specifically
about
some
of
this
stuff.
I
think
she
was
concerned
with
not
all
of
the
things
we've
requested
from
the
tool
team
or
the
websites
there's
other
issues
that
we've
documented
properly
on
our
side.
H
So
she's
wanting
to
pass
along
those
institutional
memory
to
me
so
I've
got
sort
of
a
page
full
of
notes
and
all
right
to
the
IAB
after
this
about
progress.
So
I
just
really
appreciate
you
giving
those
specifics
on
timeline
and
like
the
road
map
I
think,
is
one
of
the
things
Mary
identified,
as
maybe
wanting
to
have
more
clarity
on
and
there's.
H
Nothing
really
I
think
that
I
need
to
flag
for
you
that
you
don't
already
know
I
think
in
addition
to
the
content
moving
over
I'm
aware
that
there
are
some
issues
in
GitHub
that
are
open
still
so
I
don't
know
if
that
is,
if
those
issues
are
wrapped
up
in
the
content,
migration
and
additional
development,
it
sounds
like
you
want
to
get
the
content
moved
and
then
you
want
to
close
some
of
those
tickets
and
if
that's
the
case,.
H
I
just
have
notes
so
I
do
have
a
separate
one.
Just
on
the
data
tracker
and
this
in
the
portion
of
my
notes.
Just
on
the
website,
it
sounds
like
miria
has
six
open
issues
related
to
the
website
in
GitHub,
and
she
said
also
that
Cindy
might
have
opened
some
as
well,
and
maybe
during
also
the
transition
of
content
that
you're
doing
Cindy.
You
might
uncover
more
but
I
just
I'm,
suggesting
that
even
in
August
September,
whenever
we
hit
the
next
Milestone,
there
may
actually
be
additional
development.
H
All
right,
I
think
that
was
it
I
I
just
yeah,
really
grateful
for
the
update
and
we'll
talk
soon
in
a
couple
weeks
before.
A
H
A
Jennifer,
would
you
like
to
walk
us
through
what
we
discovered
looking
at
the
instrumentation
that
we
added
to
the
data
tracker.
I
Sure,
well,
I
hope
my
microphone
is
working.
I
think
this
might
be
the
first
time,
I've
used
it
good.
I
I
So
we've
been
looking
at
the
who's
using
which
endpoints
and
how
and
the
draft
numbers
coming
in
through
those
part
of
the
motivation
being
that
we
are
we're
still
seeing
some
drafts
being
submitted
using
the
old
synchronous
API,
which
we
would
like
to
make
it
go
away
and
as
we
were
going
through,
that,
we
also
sorted
to
look
at
the
number
of
submissions
coming
in
with
XML
and
text
and
table
to
also
parse
out
whether
the
XML
is
V2
or
V3,
and
whether
it's
directly
pre-coded
as
XML
or
converted
from
markdown
using
crandoun
or
a
mark.
I
And
so
in
the
notes
page
there.
There
are
the
statistics
that
we
got
I
think
it's
just
about
a
little
shy
of
1400
submissions.
Since
the
10
point,
3.0
release
came
out
and
I.
G
I
85
percent
of
those
are
through
the
UI
and
the
rest
through
almost
all
through
the
asynchronous
API,
which
is
great
still
a
handful
of
of
submissions
using
the
synchronous
one
and
that
number
there
is
going
to
be
nine
of
them.
I
Some
of
those
are
multiple
revisions
of
the
same
draft,
so
it's
a
oh
that's
fewer
than
that
looks
like
there
and
it
looks
like
if
you
look
at
the
I
guess:
I'm
in
the
XML
versus
markdown
division
there
in
the
third
section,
but
almost
50,
50
I,
think
55
to
45
in
favor
of
people
using
direct
XML
over
markdown
about
a
third
of
them
are
still
writing
in
in
V2
and
I.
Guess,
that's
what
I'm
seeing
there.
A
And
I
have
already
sent
direct
mail
to
this
submitters
that
we're
using
the
synchronous,
API
and
with
pointers
on
how
to
move
to
the
async.
So.
F
F
J
A
Translate
I,
don't
know
nothing
great,
so
it's
hard
to
tell
just
from
the
text
if
it
was
used,
a
tool
that
produced
it.
There's
not.
There
aren't
artifacts
left.
We
do
know
from
a
very
small
number
of
people
that
were
having
trouble
submitting,
that
they
gave
up
and
submitted
a
text
version
because
they
couldn't
get
their
XML
version
well,
groomed
enough
to
be
accepted
so,
but.
J
J
A
We've
got
an
issue
to
improve
the
quality
of
error
that
comes
back
when
someone
does
a
submission
and
one
person
that
we
were
working
with
had
some
attributes
in
the
primary
SVG
tag
that
rsvt
profile
does
not
allow
and
they
had
not
run
it
through
SVG
check
before
it
hit,
submit
and
down
inside
the
equivalent
of
SVG
check
is,
is
run,
and
it
was
airing
out
in
the
area
that
was
reported
was
very
opaque,
and
this
is
an
improvement
that
we
will
make
before
we
get
to
the
118
submission
cycle.
A
E
A
Ways
to
get
insight
into
why
something
is
being
submitted
text
only
I
mean
we
could
go
as
far
as
adding
to
the
submission
form
if
you're
submitting
text
only
a
you
know,
comment
field
that
says
you
know.
Please
tell
us
why
you're
not
submitting
XML
just
a
voluntary
thing
that
people
could
like
give
us
data
on.
J
That
would
be
useful,
I,
think
and
I
guess
that
looking
at
the
numbers,
a
significant
amount
of
the
XML
submissions
must
have
come
through
the
async
UI
since
there's
no
other
big
block
and
so
I'm
I'm.
Given
that
Martin's
make
file
and
upload
directly
for
you,
I
guess:
I'm
really
surprised
that
people
aren't
using
it
more.
J
J
Just
you
know,
there's
other
stuff
and-
and
you
may
also
be
able
to
find
some
of
the
evidence
of
the
make
files
in
the
form
of
the
venue
and
other
stuff
in
the
that
some
provided,
because
I
think
that's
a
useful
thing
to
know
about
the
adoption
and
I
guess:
I'm
also
really
surprised
at
the
number
of
mmark,
not
that
popular
the
seller
working
group
likes
it,
but
not
to
the
tune
of
55
submissions.
A
So
any
ideas
that
you
have
I
mean
feel
free
to
drop
by
code
Sprint,
or
we
can
talk
during
the
week
at
1
17
about
ways
that
we
can
further
mine.
The
information
that's
there
to
try
to
identify
classes
of
submission.
A
So
we're
basically
at
the
block
of
what
I
ex
end
of
the
block
of
the
the
hot
topics
for
discussion.
The
last
hot
topic
that
I
had
was
to
ask
the
group
whether
or
not
we
should
cancel
the
August
8th
call.
We
quite
often
do
cancel
the
tools
call.
It
happens
right
after
each
ITF
meeting.
So
unless
somebody
has
a
strong
desire
to
hold
that
August
8th
meeting
and
I
will
cancel
it
later
in
the
week.
A
Acknowledging
your
request
earlier
Eric
for
the
read
through
of
the
the
rest
of
this
I
think
feedback
I've
gotten
generally
from
other
people
is,
is
that
we
can
mostly
just
read
it
offline
I
do
want
to
call
in
and
make
sure
that
people
take
the
time
to
read
the
T
paragraphs
at
the
end
of
the
data
tracker
report,
we'll
talk
more
at
the
next
tools
meeting
about
the
implications
of
some
of
the
work
that
we're
doing
getting
ready
for
RPC
tool,
modernization
on
the
V1
API
in
particular,
we
may
have
some
users
of
the
API
that
are
going
to
be
disrupted
and
I.
A
The
RPC
has
also
been
waiting
on
a
rework
of
the
author
information
for
several
drafts.
The
plan
had
been
to
regenerate
all
of
the
information.
I
took
a
look
at
how
disruptive
that
was
likely
to
be
and
found
that
there
is
quite
a
lot
of
data
that
has
been
gathered
over
the
decades,
correcting
author
information
manually
by
the
Secretariat
that
will
be
overwritten.
A
To
just
have
it
regenerate
the
all
of
the
author
information
and
give
the
person
that
requested
the
Regeneration
an
opportunity
to
do
a
manual
correction
and
leave
a
little
bit
more
track
in
the
database
about
what
has
been
manually
corrected
or
not
so
that
in
the
future.
If
we
want
to
do
a
big,
automated
pass,
we
can
do
so
knowing
whether
or
not
data
should
be
preserved
as
already
validated
by
a
human.
C
On
XM
at
RFC,
the
third
third
bullet
point.
So
there's
a
draft
PR
that
allows
Unicode
in
all
elements
for
people
who
are
interested
have
a
look
at
it
and
you
can
check
out
that
branch
and
run
crops
against
it
and
see.
What's
the
output
is
yeah
I,
don't
think
it's
going
to
get
much
anytime
soon,
but
for
your
information.