►
From YouTube: IETF-TOOLS-20230314-1800
Description
TOOLS meeting session at IETF
2023/03/14 1800
https://datatracker.ietf.org/meeting//proceedings/
A
A
C
A
A
A
If
someone
could
take
volunteer
to
watch
the
notes
for
me,
I
noticed
from
the
last
call
that
there
were
some
people
contributing
on
the
notes.
My
windowing
I
can't
conveniently
get
the
notes
in
in
addition
to
looking
at
the
face,
if
there's
something
that
needs
to
be
brought
to
the
verbal
part
of
the
conversation
from
the
notes
jump
in
and
do
that,
could
somebody
please
explicitly
volunteer
to
do
that
for
me
now.
A
A
I
would
propose
that
we
stop
it
and
work
with
the
people
that
really
want
to
use
these
things
on
getting
them
to
use
a
more
modern
ask
for
the
things
that
they're
really
interested
in
and
if
they're
really
interested
in
trying
to
get
everything
convinced
them
that
they
get
everything.
Once
and
not
over
and
over
and
over,
and
then
incrementally
use
apis
to
get
the
additional
things
that
they
need.
A
A
A
A
A
We're
just
waiting
for
the
removal
of
DNS
SEC
on
that
particular
Zone
to
expire
through
cash
before
we
initiate.
The
transfer
will
be
going
through
this
with
the
other
zones,
while
we
might
be
getting
them
ready
to
move
I,
don't
plan
to
move
them,
starting
from
now
until
after
we
get
past
116
so
that
we
don't
disrupt
the
the
meeting
with
this
activity.
So
we'll
pick
this
back
up
right
after
116.
A
A
A
A
A
D
A
Next
item
is
the
RPC
tools
refresh
project.
Everyone
should
have
seen
the
note
that
Jay
sent
to
the
tools
discuss
list
about
the
plan
that
we
have
for
implementation,
Gene
and
I
have
started
on
building
out
user
stories.
We
plan
to
have
many
discussions,
while
we
are
in
Yokohama
with
members
of
the
community
members
of
the
RPC
pushing
to
make
sure
that
we're
going
to
as
we're
making
the
transition
of
these
toolings,
we
build
the
right
thing,
shared
understanding,
a
good
idea
of
where
we're
going,
and
why
is
the
goal
of
of
these
conversations.
A
I
expect
to
begin
implementation
of
the
parts
that
we
have
confidence
that
everybody
agrees
on
what
needs
to
be
done
very
soon
after
1
16.,
but
after
we
do
the
postgres
and
Django
for
transition,
because
the
new
things
that
are
going
to
be
coming
into
the
data
tracker,
we
definitely
want
to
build
on
scaffolding.
That
is
only
going
to
be
available
to
us
once
we're
on
Django
4..
A
So
Alexa,
just
as
a
an
early
introduction
and
a
teaser
for
some
of
the
Alexis
sorry
teaser
for
some
of
the
conversations
that
we're
going
to
be
having
is
you
know
where
the
Errata
data
lives,
so
in
the
conversations
that
Gene
and
I
have
been
having?
It
seems
to
us
at
the
moment
to
me
in
particular,
but
I
think
that
conversations
need
to
to.
A
A
A
C
I,
like
it,
it
seems
reasonable.
I've
seen
you
know,
lots
of
other
GitHub
projects
use
it.
So
it
seems.
Okay,
probably
is
worthwhile
because
it's
sheep
relatively
cheap
to
do
compared
to
other
forecasting
and
planning
things
and
hey.
Do
you
want
to
present
the
slide
at
the
working
group
chairs
lunch?
A
B
So
it
is
good
for
conveying
very
big
tasks
at
hand
of
having
it
filled
out
would
be
nice,
for
instance,
clicking
some
of
these
there's
no
description,
so
somebody
unfamiliar
with
these
items
might
scratch
their
head
at
what
these
are
and
is
there
significance
in
where
they
are
listed
within
a
column?
Perhaps
a
small
read
me
all
right.
A
A
All
right
we're
now
down
to
the
RFI
section,
so
we'll
start
going
a
little
more
quickly,
but
if
there
is
something
that
needs
to
be
discussed
raise
a
flag,
let
me
know
for
the
infrastructure
strategy.
We
did
get
responses
to
the
RFI.
A
team's
been
formed
to
digest
those
responses
and
turn
them
into
action
for
the
rfps
we
expect
to
meet
this
week.
A
As
we
discussed
at
the
last
meeting,
we
simplified
the
number
of
addresses
used
to
report
May
or
issues
to
the
tools
team
as
to
help
the
tools
team,
we're
in
the
process
of
reconfiguring
places
like
the
footer
and
the
data
tracker
to
point
to
the
new
tools,
help
Alias.
Let
the
tools
help
Alias
is
in
place
already.
E
E
A
A
A
E
Data
tracker
Robert
go
ahead.
Yeah
I
just
wanted
a
quick
update
on
that
one.
So
far,
we've
heard
from
one
working
group
chair
that
they
still
need
some
work
on
their
transition.
So
I,
don't
think
that'll
stop
anything
else,
that's
going
on,
but
we
are
working
with
them,
but
otherwise
we
haven't
heard
any
concerns
about
the
transition
plan.
E
A
E
D
D
For
auto
tools,
there
are
several
map
fixes
and
improvements,
especially
on
ID
Define,
RFC
div.
There
are
some
cases
where
IDT,
fixed
slower,
so
I
have
set
up
timeouts
now
to
fall
back
to
RFC.
Deep
ID
is
taking
long
time
to
give
back
results
to
someone
right
now.
It's
I
have
20
seconds
of
timeout,
so
it's
taking
too
long,
then
it's
our
IDE
fill
fall
back
to
our
rcd.
D
D
D
A
E
A
A
B
A
A
Eric
is
also
not
available.
I'll
ask
him
to
send
an
update
on
what's
happening
in
Yin
catalog
separately
off
the
top
of
my
head.
The
activity
that
I've
seen
on
the
Yang
catalog
project
for
the
last
month
has
focused
on
the
the
primary
user
interface,
particularly
around
search
and
singing
the
correct
things
about
whether
or
not
the
data
that's
being
described
on
a
given
output
page
is
from
a
Ying
module
that
has
finished
going
through
a
process
that
makes
it
a
an
official
thing
you're
using
the
word
ratified.
It
makes
me
very
nervous.
A
A
I
have
to
add
is
a
related
to
the
IMAP
user,
remapping
topic
that
we
have
been
tracking.
There
has
not
been
progress
on
remapping
users,
but
there
has
been
progress
on
changing
the
way
we
authenticate
users
that
will
be
leveraged
eventually,
in
the
usually
remapping
concept,
we
have
a
an
API
that
we
created
over
the
weekend.