►
From YouTube: IETF-CORE-20230201-1500
Description
CORE meeting session at IETF
2023/02/01 1500
https://datatracker.ietf.org/meeting//proceedings/
A
B
A
B
A
B
A
Okay,
so
let's
get
started
and
welcome
everyone.
This
is
a
core,
an
entry
meeting
of
the
co-working
group,
I'm
Marcus,
my
coaches
are
Jaime
Jimenez
and
Kirsten
Norman
and,
as
usual,
the
not
well
applies
gets
familiar
with
with
them.
If
you're
not
already
is
not
just
about
IPR,
it's
also
in
the
special
about
our
color
conduct,
so
be
nice
and
professional.
We
want
another
and
we
have
a
pretty
slim
agenda
for
today.
A
B
A
B
C
You
could
put
lots
of
information
in
there,
but
it's
not
quite
clear
how
actionable
that
information
would
be.
So.
Instead
we
decided
to
to
revert
to
a
simpler
stage,
but
added
the
the
obsolete
status
that
was
suggested
by
Rob
I.
Think
that
that's
a
good
idea
to
be
able
to
carry
around
Sid
assignments
that
that
are
no
longer
used
in
the
version
of
the
module
that
the
Sid
fire
is
supporting.
C
So
that
was
the
the
item
status
and
then
there
was
a
discussion
about
a
per
Sid
file
status.
So
one
way
to
obtain
a
personified
status
would
be
to
look
at
all
per
item
status
entries
and
if
they
are
all
stable,
then
apparently
the
Sid
file
is
stable,
but
we
opted
for
a
a
bit
more
explicit
transition
from
an
unpublished
work
file
to
a
published,
definitive
Sid
file.
So
this
should
be
explicit
and
tools
never
should
make
the
decision
that
something
is
published
on
on
information.
C
So
that's
an
interesting
result
of
the
discussion
have
a
relatively
simple
status
per
item,
but
then
add
an
item
at
a
status
per
Sid
file.
So
we
can
can
make
it
easier
to
recognize
what
a
Sit
file
is
supposed
to
do.
We
also
discussed
whether
the
Sid
file
status
should
be
reflected
in
a
file
extension,
but
we,
we
saw
lots
of
tool
issues
come
up
when
we
do
that.
So
so
we
didn't
pursue
that.
We
just
said
there
should
be
a
personified
status.
C
So
these
can
be
taken
on
in
in
one
or
more
further
documents,
in
particular
the
the
whole
annotation
support,
which
is
important
for
for
certain
styles
of
using
gang.
That
requires
some
some
more
thinking
how
to
properly
do
this
in
sibo
in
in
the
Json
version.
Essentially,
all
the
map
keys
can
get
an
ad
design
prefix
and
then
have
a
different
meaning,
but
that's
not
really
something
that
we
should
be
doing
for
for
since
so
yeah.
Some
some
Innovation
is
required.
C
C
C
A
A
A
So
my
personal
take
is.
None
is
really
needed
to
even
heart
in
principle,
to
link
the
first
rata
to
the
cop
option,
numbers
registry
of
the
core
parameters,
just
thinking
of
the
placeholder
option,
numbers
reserved
for
for
future
location,
star
options,
but
it
would
be
just
to
give
more
context.
It
doesn't
really
add
anything
related
to
the
actual
registration
procedure.
A
C
My
my
main
problem
is
that
I
think
that
would
be
difficult
for
people
to
understand
why
we
are
linking
to
these
router
reports.
So
there
would
need
to
be
some
additional
explanation
and
I.
Don't
know
where
to
put
this
explanation,
except
maybe
into
a
rendition
of
the
correction
center
applications
document.
C
C
A
A
A
C
The
way
so
my
plan
was
to
to
submit
it
before
today's
meeting
and
then
the
usual
disaster
happened.
So
the
the
version
of
XML
to
RFC
on
my
laptop
suddenly
decided
it
no
longer
can
cooperate
with
the
version
of
Wheezy
print
that
I
have
on
my
laptop
now.
I,
don't
need
to
use
Wheezy
print
to
submit
drafts,
but
XML
drivers
seems
to
to
really
like
busy
print
and
try
to
engage
it
even
if
it's
not
needed
and
yeah.
That
was
an
interesting
hour
before
the
meeting,
but
I
didn't
through
with
it.
A
C
Yes,
so
the
the
the
target
attribute
and
the
the
ad
hoc
document
should
have
synchronized
working
last
call
from
my
point
of
view
of
you
so
for
the
Target,
as
we
would
I
say
this
as
an
author
for
the
ad
hoc
document,
the
call
ad
hoc
document
I
say
this
as
a
working
group
chair
and
yeah,
then
we
will
look
at
this
essentially
before
the
the
internet
draft
deadline.
So
we
might
even
have
an
updated
version
to
look
at
in
your
karma.
C
C
A
A
There
was
some
discussion
between
the
chairs
and
the
authors
of
co-opm
and
and
before
considering
to
to
proceed,
it's
good
to
have
a
pedagogical
overview
of
the
building
blocks
used
in
in
the
PM
document,
so
that
the
the
core
participants
get
more
familiar
with
those
to
better
understand
and
judge
the
draft.
So
we
are
going
to
have
this
this
sort
of
overview
as
a
presentation
from
Giuseppe,
mainly
and
other
cauthors
in
the
interim
in
two
weeks,
but
of
course
feel
free
to
propose
other
topics
by
then.
C
So
just
to
remind
people
of
what
was
going
on
there.
So
there
is
this
draft
that
that
brings
together
ippm
measurement
Technologies
with
car
and
the
the
car
people
said.
I,
don't
understand
this
draft.
There
is
ippm
Technologies
in
there
and
the
ippm
people
said:
I,
don't
understand
this
draft.
This
is
there
is
Car
Technology
in
there.
So
that's
the
typical
situation
of
a
draft
that
brings
two
technologies
together
and
in
the
end
the
chairs
decided.