►
From YouTube: IETF-TOOLS-20230912-1800
Description
TOOLS interim meeting session
2023/09/12 1800
A
A
A
A
A
B
A
A
A
C
A
A
We
have
an
open
ticket
with
cloudflare,
where
they're
looking
at
what
they
could
do
differently.
They've
offered
us
a
solution
that
would
work
with
ostensibly
would
work
with
what
they
offer
right
now,
where
identity,
digital
would
sign
their
name
server
records
themselves,
and
we
would
pass
this
stuff
into
the
dot
org
domain
by
way
of
cloudflare
we're.
We've
asked
identity
digital
if
they'd
be
willing
to
do
that,
and
waiting
to
hear
back
for
the
time
being,
we've
removed
the
secondary
name
servers
from
DNS.
A
D
D
A
C
C
E
A
A
So
the
last
thing
I'd
like
to
add
here
is
that
the
next
steps
for
moving
things
into
the
data
tracker,
since
we
moved
the
IB
agendas,
statements
and
appeals,
we've
got
the
framework
for
moving
those
kinds
of
artifacts
into
the
data.
Tracker
and
I
will
be
moving
the
iesg
variants
of
those
things
in
the
next
few
weeks.
A
Someone
move
on
over
the
last
few
weeks.
We
have
tried
a
different
way
for
deploying
the
irtf
website.
We
have
a
proposal
in
front
of
Colin
right
now,
he's
reviewing
where
the
website
is
being
served
out
of
blob
store
in
Azure,
just
because
Azure
was
had
the
the
feature
set
that
we
needed
to
be
able
to
make
it
easy
for
Colin
to
deploy
new
versions
of
the
website
and
have
good
previews
of
the
work
in
progress
from
the
repository
that
he
already
had.
A
C
A
A
We
have
a
bit
of
work
completed
that
will
change
these
models
so
that
everything
in
the
data,
tracker,
hangs
off
of
person
and
the
only
thing
that
knows
about
user
is
that
link
from
the
data
tracker
person
to
user
not
entirely
true,
they're,
still
a
little
bit.
That's
buried
under
the
covers
with
the
oidc
gearing,
but
the
primary
business
logic
that
we
have
when
we're
worried
about
documents
and
appeals
and.
A
F
A
A
During
117,
several
of
us
got
together
and
sprinted
towards
building
a
standing
dashboard
that
could
be
used
to
show
the
progress
of
work
in
the
ietf
Greg
did
a
bunch
of
of
wireframe
prototyping
started
talking
through
that
with
the
isg
see
what
the
isg
wanted.
There
will
be
continuing
conversations
with
the
isg
and
we're
planning
to
do
another
Sprint
again
later
this
later
this
week.
A
G
A
A
A
B
Think
Russ
was
the
person
that's
responsible,
for
it
he's
not
on
the
call
right
the
but
Ayanna
is,
is
is
designed
to
accept
this
level
of
requests,
in
fact,
orders
of
magnitude
greater
than
this
for
these
sorts
of
things
and
us
having
a
copy
of
it
in
case
Ayanna
fails
is
one
thing
but
are
serving.
The
copy
is
a
very
different
thing
and
I
don't
believe
that
we
should
be
serving
the
copy,
so
I
think
we
can
and
I
also
don't
think
we
need
to
worry
about
keeping
the
copy.
B
Personally,
you
know
right
since
that
time
Ayanna
is
now
globally
distributed,
has
all
sorts
of
different
things.
They've
invested,
you
know
tinted,
Williams
and
stuff,
so
they're
an
order
of
magnitude
different
from
the
way
they
were
before
so
I
think
we
already
have
an
agreement
in
principle
to
turn
these
things
off.
I
can't
find
the
reference
just
yet,
but
I
think
it's
on
tools,
discuss
lists
and
I
would
suggest
we
go
ahead
and
do
that.
C
A
B
C
A
A
Looming
issue,
that
is,
a
few
incidents,
have
raised
its
importance
with
the
quality
of
the
data
that
we
have.
We
had
this
metadata
associated
with
an
email
address
about
whether
that
email
address
is
active
or
if
it's
the
primary
email
address
for
someone.
We
have
large
parts
of
the
data
tracker
when
it
sends
mail
will
refuse
to
send
mail
to
an
email
address.
That's
inactive
and
we'll
hunt
for
the
most
recently
active
one
or
the.
A
And
use
that,
instead,
if
somebody
is
trying
to
send
mail
to
an
inactive
address,
this
isn't
implemented
everywhere
that
the
data
tracker
sends
mail.
The
submission
tool
is
notorious
for
just
sending
mail
to
you
raw
bits
that
come
in
as
author
email
addresses.
So
there's
there
are
issues
that
we
have
to
go
modify
the
way
the
data
tracker
sends
mail
to
always
pay
attention
to
active
or
not,
which
we
plan
to
leverage
on
dealing
with
having
the
data
tracker.
Do
the
right
thing
when
it
knows
a
participant
is
deceased.
C
A
In
that
initial
set
of
choices
and
didn't
end
up
getting
notified
because
the
data
tracker
was
using
an
address,
that
was
actually
a
bad
address
that
had
come
in
by
way
of
a
co-author,
submitting
an
internet
draft
and
getting
the
email
address
wrong,
and
this
didn't
get
straightened
out
until
after
the
challenge
period
ended.
So
that
person
didn't
end
up
on
this
nom-com.
A
We
need
to
put
some
pressure
on
making
sure
that
these
addresses
are
correct.
I
intend
on
the
page
for
someone
volunteers
for
a
nom
nom
come
to
make
it
very
clear.
These
are
the
addresses
that
the
day
your
tracker
will
try
to
contact
you
at
these
addresses
won't
be
used
so
that,
at
least
at
that
stage
there
is
a
little
bit
of
Polish
added
to
the
quality
of
the
data.
A
So
the
question
is
going
forward:
do
we
just
Mark
these
email
values
that
come
in
by
way
of
Internet
drafts
always
active?
Do
we
try
to
do
anything
retroactively
to
the
ones
that
are
inactive
for
the
people
that
we've
got
their
users?
We
previously
discussed
I
believe
on.
One
of
these
calls
having
the
data
tracker
at
whenever
they
access
use
the
messaging
framework
to
periodically
tell
them.
You
know,
with
the
yellow
box,
hey
by
the
way.
A
F
F
C
E
A
B
Take
the
the
full
list
that
I
get
given
from
Robert
I
create
a
populator
mailing
list
with
it.
I
then
use
the
mailing
list
to
send
out
the
survey
and
then,
when
I'm
done
with
the
survey,
I
export
that
list
of
of
members
again
and
the
difference
between
that
and
what
I
was
originally
given
are
the
five
plus
thousand.
You
know
who
are
definitely
dead.
Email
addresses,
I,
think
I've
done
it
twice
now.
B
I've
got
you
know
pretty
much
the
same
set
of
things
so
there's
for,
for
example,
there
is
a
a
particular
ISP
or
something
career
that
must
have
collapsed
and
there
are
like
100
plus
you
know
just
associated
with
that.
So
I
think
we've
got
some
good
data
somewhere
on
this,
but
we've
definitely
got
a.
You
know
at
least
a
one
in
ten
problem
here.
A
A
A
A
So
during
these
conversations
it
came
up
that
what
one
of
the
primary
motivations
for
signing
these
things
in
the
first
place
and
what's
in
RFC
54.85,
was
to
make
it
easier
on
the
Secretariat
when
responding
to
requests
about
internet
drafts.
When
was
this
the
internet
draft
that
you
published
and
when
it
when
was
it
made
available
to
the
community?
C
B
They
they
would,
they
do
for
documents,
but
for
for
us
everything
is
a
subpoena.
That
is
then,
a
you
know,
a
notified,
a
declaration
from
us
as
to
what
document
existed
at
what
time,
and
that's
the
only
way
that
any
of
these
lawyers
want
to
do.
It
is
that
declaration
from
us,
so
the
the
art,
the
signature,
doesn't,
do
anything.
A
A
A
E
When
you
started
to
ask
the
question,
I
was
looking
for
my
unmute
button,
because
I
was
about
to
say
something
there
I
I
think
you
are
in
the
same
isg
selectional
as
isg
is
so.
Yes,
we
will
go
to
the
yes,
no,
no
opinion
and
with
three
buttons
to
be
selected.
If
you
don't
select,
none
of
them,
you
are
not
content.
In
the
opinion,
no
opinion
is
kind
of
an
opinion
itself.
E
A
A
A
I'll
make
a
comment
here
again
that
I'm
still
struggling
with
trying
to
make
it
easier
for
the
Secretary
of
the
RPC
to
correct
all
their
names,
as
they
appear
in
the
the
entries
for
specific
versions
of
a
draft.
I.
Think
it's
going
to
require
an
actual
new
set
of
data.
Tracker
views
to
be
created
to
allow
this
editing
to
happen
sensibly
and
to
stick
so
still
a
work
in
progress.
A
A
A
One
of
these
is
changing
the
structure
of
the
XML
to,
as
mentioned,
avoid
stripping
the
tea
tags.
All
of
these
things
are
probably
good
fodder
for
people
to
pay
attention
to
when
they're.
Considering
the
do
we
republish
re,
you
know
make
new
XML
for
already
published
XML.
Do
we
re-render
and
when
do
we
re-render
so.
A
B
C
A
Yeah
I
think
we
touched
on
this
on
a
previous
call,
but
it's
worth
touching
them
again.
The
idea
for
ID
Nets
being
Rewritten
entirely
as
a
node.
You
know
a
JavaScript
library
thing
is
that
it
will
also
live
in
the
directly
in
the
editors
that
we're
building
for
the
RPC
that
might
have
good
reuse
for
authors
in
the
long
run.