►
From YouTube: REGEXT WG Interim Meeting, 2020-04-27
Description
REGEXT WG Interim Meeting, 2020-04-27
B
C
B
A
E
C
Yeah
presentation
number
two
similar
approach
with
respect
to
rfc
7483,
which
is
the
json
response
document
right.
So
now
now
this
one
actually
had
a
little
bit
more
to
look
at
most
of
what
we
saw
in
7482
were
actually
either
errata
or
stuff
that
came
up
on
list.
7483
has
been
one
of
the
places
where
we've
had
a
little
bit
more
discussion
and
commentary
around.
You
know
what
actually
goes
into
a
json
response,
but
purpose
and
approach
exactly
the
same.
C
C
C
C
C
C
D
C
D
C
Was
I
I
had
stopped
editing
this
document
at
a
time
when
we
were
trying
to
put
the
kibosh
on
changes
getting
ready
for
ietf
107.,
yes,
and
so
there
have
been
some
additional
comments
received
on
list
that
I've
queued
up
for
discussion
and
resolution
after
we
had
this
particular
presentation.
So
I
I
know
jazdeep
gave
me
some
mario
gave
me
some
patrick
gave
me
some
and,
and
so
now,
once
we
get
past
this,
the
next
step
will
be
go
back
triage.
C
Those
comments,
cue
up
anything
for
discussion
that
needs
to
be
queued
up
and
if
there's
anything
there
that
we
identify
as
something
that
looks
like
as
a
real
protocol
issue,
I'll
capture,
those
on
the
working
group
wiki
and
we'll
simply
park
those
there
for
now,
and
eventually,
maybe
think
about.
You
know
how
we
deal
with
those
in
the
context
of
protocol
evolution.
B
Question:
okay:
go
ahead,
yeah!
I
I
I
think
you
answered
this
scott
in
in
the
end
of
year.
The
very
end
there,
but
I
wanted
to
call
it
out
more
specifically
and
and
precisely
I'm
assuming
that
what's
really
going
on
here
is
is
we
have
to
decide
or
I
guess
this
working
group
gets
to
have
a
point
of
view
and
then
make
a
proposal
about
evolving.
These
particular
rdap
standards-
and
you
know,
do
we
get
ownership
of
that
and
then
do
these
documents
become?
B
You
know
the
path
forward
and
does
it
belong
to
this
working
group,
so
that
might
be
a
discussion
that
has
to
that
will
ultimately
have
to
happen
with
with
the
area
director.
I
wanted
to
call
out
more
explicitly
exactly
what
was
going
on
there
when
you
said
we'll
have
to
decide
going
forward.
I
think
that's
what
you
mean.
These
are
standard
track
documents.
These
are
technical
changes.
B
C
Yes,
scott,
holland.
Back
again,
no,
I
think
you've
got
it
there.
Jim,
I
mean.
Let
me
just
push
back
one
thing,
though
technical
changes,
as
I
said,
we're
trying
to
ensure
that
we
don't
do
anything
here.
That
ultimately
requires
software
changes
unless
you
know,
while
you've
implemented
something
you've
misinterpreted
the
text
or
you
know
otherwise
made
some
assumption.
C
That
is
somehow
at
odds
with
what
we
think
the
original
intent
of
the
document
was,
but
ultimately,
when
we're
done
we're
still
talking
about
rdap
level,
zero.
Okay,
these
are
individual
submissions.
For
now
I
might
ask
barry,
you
know
for
his
opinion
on
whether
or
not
the
working
group
would
have
to
get
involved
or
documents
that
aren't
proposing
any
protocol
changes.
C
I
know
that
in
the
case
of
like
the
security
considerations
document,
for
which
we
have
no
captured
errata
and
no
known
deficiencies
when
we
talked
about
this
at
the
last
face
to
face
barry's
suggestion
was
that
we
could
simply
go
into
the
data
tracker
and
submit
a
request
for
a
status
change
and
that
would
not
necessarily
require
development
of
an
integer
draft
and
working
it
through
the
working
group
process.
So
that's
kind
of
what
I'm
thinking
right
now.
B
E
C
C
Sure
yeah,
so
so
my
intention
is
to
start
working
on
those
again.
You
know
going
through
the
the
notes
that
I've
captured
on
list
where
we
have,
for
which
we
have
some
other
corrections,
and
hopefully
you
know
getting
those
paying
attention
to
that
feedback.
Getting
some
on
list
discussion
started
and
then
updating
the
documents
as
we
resolve
the
comments
received.
So
over
the
course
of
the
next
couple
of
weeks.
I
will
expect
to
update
both
of
those
drafts.
F
A
All
right
thanks
everyone.
We
have
well,
first
of
all
the
thesis
slides
on
the
same
one
as
the
one
we
have
present
in
the
last
wednesday's
joints,
cut
off
and
and
and
the
the
individuals
meeting.
So
if
you
attended
the
the
last
one
presentations,
this
is
the
things
like
that
has
different
liberty
and
we
got
some
good
feedback
from
guess
what
as
well.
So
if
I
reach
the
second
slide,
I
mentioned
about
the
questions,
comments
that
raised
four.
A
Since
we
have
the
bias
of
the
bad
presses
of
domains,
different
investors
and
registrars
wanting
to
make
a
standard
of
it
so
that
things
becomes
consistent
standards
that
will
be
effective
for
both
the
producers,
which
is
the
recipe
for
the
reports
also
to
consume
the
register
side
of
the
marketing
report.
So
this
slide
just
I'm
showing
some
examples
of
what
reports
produced
by
whom
and
how
similar
or
how
much
signal
they
are.
A
In
order
for
the
report
to
be
centralized-
and
it's
not
only
include
the
definitions
but
also
have
the
two
registry
in
diana
to
get
the
the
other
definitions
there
or
one
for
the
fields
for
the
columns
here
and
then
the
sentence
is,
will
be
similar
to
the
usb
expressions,
which
is
either
registry.
It
will
be
first
compressor
and
every
column.
Things
have
to
be
properly
defined,
where's
the
reference
and
where
they
use
the
next
fourth
lines.
One
was
defining
the
draft
session
tools
about
what
they
feel
support
there.
A
So
I'm
just
gonna
skip
them
in
giraffe.
It
was
screwed
by
the
the
category
or
there
where
they
are
related,
but
they
were
just
square
pages
for
using
document
management,
so
they
could
easily
be
arranged
alive,
and
then
we
also
see
the
second
registry
for
the
reports
and
again
this
will
be
the
one
that
talks
about
what
to
record
what
builds
it
and
what
the
methods
are
there.
A
And
these
examples
of
the
reports
and
the
interviews
that
is
unrelated
to
it
and
there
are
open
sessions
there
again.
This
will
be
meant
to
advance
the
epp
extensions
registry,
like
format
it's
not
yet
properly,
but
it's
not
yet
completely
write
out
in
the
draft
right
now
so,
but
someone
has
mentioned
in
the
previous
presentations
that
we
are
not
acknowledged
and
we
know
that
we're
going
to
complete
those
parts
of
the
writings.
A
There's
some
baseline
direct
requirement
for
it
all
important
expect
to
be
csv
commercialized
values.
The
first
line
is
always
about
the
column
headings.
The
unrecognized
column
headings
for
now
in
the
dot
interface
should
be,
or
maybe
you
know
there
are
lots
of
discussions
in
the
previous
presentations
about.
A
How
are
we
going
to
extend
the
report
of
the
ideal
report
so
allowing
the
consumer
to
take
no
more
fears?
They
don't
recognize
this
one
of
the
way,
and
this
is
still-
and
we
welcome
all
kinds
of
feedback
suggestions
for
for
getting
this
dress
now.
There's
another
discussion
need
by
property
would
probably
would
not
be
in
the
scope
for
this
drive,
for
this
is
the
file
name.
What
means
one
element
should
be
there
to
get
the
refill
name.
A
The
tld
involves
the
report,
the
name
of
the
report
industry,
maybe
fishings,
and
some
operation
issues
like
if
some
large
records
or
some
large
registry
have
not
you
know
found
him
can
go
quite
large
over
a
gigs
of
raw
data
is
not
uncalled
for
big
registry
and
registrar.
So
when
it
grows
to
such
a
large
size
should
we
need
to
get
a
file
or
we
just
never
need
to
be
yourself,
because
this
is
just
intense
internet
bandwidth
is
actually
freedom.
A
G
Thanks
just
a
quick
suggestion,
or
whatever
I
don't
know,
but
from
the
of
the
fields
with
multiple
values
on
how
to
separate
them,
instead
of
overall
the
various
characters
that
can
create
all
their
opponents
like
a
chroma,
can
you
can
happen
in
address?
I
don't
know
there
are
some
characters
in
even
that
can
be
used
for
that,
for
which
their
purpose
is
exactly
to
specify
field
separation,
and
things
like
that
when
talking
about
one
c
character,
which
is
called
side
separator,
or
anything
like
that.
D
F
D
D
We
scheduled
this
meeting
thinking
that
this
would
be
automatically
recorded,
but
jim
and
I
just
after
the
beginning
of
the
session,
we
concluded
that
the
it
was
not
recording
so
probably
the
first
half
of
this
of
this
session
is
not
in
the
recording.
So
that's
completely
our
fault.
Sorry.
For
that,
then
I
want
to
thank
all
the
presenters.
I
think
everything
worked
very
well
doing
this
remotely
for
the
first
time
for
everybody.
B
Say
thanks
to
everyone,
I
I
know
that
I'm
sure
that
folks
have
been.
But
since
I
am
talking,
I
know
that
folks
are
probably
bored
with
hearing
my
voice
all
the
time,
and
you
know
we
often
suffer
with
not
having
antoine
with
us
too
often,
and
so
it
just
seemed
entirely
appropriate
to
for
me
to
be
quiet
and,
and
let.
E
A
B
But
thanks
very
much
antoine
and
thanks
to
all
for
for
going
through
this
and
and
yeah,
I
guess
I'll
apologize
for
not
recording
too.
You
know
antoine,
and
I
did
meetings
several
times
over
here
to
practice
this
we
actually
did
and
to
make
sure
that
we
knew
how
to
work
everything
it
could
make
all
the
parts
work
the
way
they
should
yeah
halfway
through
this
thing,
we
just
like
wait
a
minute.
What
about
recording?