►
From YouTube: IETF-CORE-20230510-1400
Description
CORE meeting session at IETF
2023/05/10 1400
https://datatracker.ietf.org/meeting//proceedings/
A
B
B
C
C
A
C
D
A
B
A
B
So
my
plan
was
to
have
a
dash
13
submitted
for
this
meeting.
Of
course,
that
didn't
quite
work
out
but
I
think,
except
for
two
things
that
still
need
to
be
done.
We
have
that.
So.
Can
you
increase
the
point
size,
some
more
right,
better
or
even
more
use?
The
whole
screen
always
use
the
old
screen
more
more.
C
B
So
interesting,
interestingly,
all
the
changes
got
focused
into
two
areas,
so
we
have
one
area
that
you
are
showing
right
now,
which
adds
rules
that
go
beyond
the
cdd8
specifications
or
the
CDA
specification
gives
you
the
overall
structure,
but
it
cannot
express
some
things
and
we
already
had
text
about
trailing
now
values.
Of
course
we
could
write
cdgl.
That
removes
those,
but
this
is
very,
very
tedious.
B
One
is
that
we
had
this
discussion
about
an
empty
pass
versus
a
knife
path
and
since
both
seem
to
have
the
same
meaning
in
both
actually
only
consume
one
bite
in
in
the
encoded
sibo
data
item
we
kind
of
flipped
the
coin,
and
to
me
it
seems
that
that
we
are
closer
to
the
actual
semantics
if
we
do
require
an
empty
array
here,
so
this
fits
with
the
semantics
that
the
empty
array
has
in
the
CI
reference.
The
path
is
actually
given.
B
C
B
B
B
B
B
B
So
I
think
that
that
is
a
useful
to
point
out
that
there
is
no
need
to
actually
do
excessive
checking,
in
particular,
if
you
don't
even
have
the
parts
that
you
would
need
for
for
checking.
So
we
we
can
have
intermediary
intermediaries
that
check
less
and
kind
of
avoid
ossification
by
by
having
each
intermediary
check
everything.
B
B
B
In
the
direction,
so
we
can
see
more
of
of
the
early
text
of
that
section
right
which
is
scrolling
down
for
me
and
scrolling
up
for
other
people.
You,
you
see
the
the
little
editors
comment
here
with
the
starting
with
a
so
I
think
Christian
was
was
pointing
out
that
life
is
easier.
If
you
don't
have
indefinite
length
items
in
extensions
and
I
think
actually
we
could
go
ahead
and
say
sia
eyes
shouldn't
be
using
indefinite
links
representations
at
all.
B
B
B
On
the
other
hand,
an
implementation
that
that
writes
an
indefinite
length
array
open
and
then
starts
processing
a
path
bite
by
bite
that
that's
not
entirely
weird,
so
yeah,
let's,
let's
maybe
have
a
little
bit
more
discussion
about
this,
and
the
final
change
is
at
the
end.
So
if
you
can
scroll
up
some
more
or
scroll
down
depending
on
which
part
of
the
world
you.
B
Good
enough,
yep,
okay,
so
here
we
have
the
fix
that
dots
in
hostname
items
in
host
name
elements
are
not
reserved,
so
normalization
will
turn
back
any
percent
encoding
that
you
might
have
had
there.
So
that's
just
not
possible
to
have
a
DOT
in
in
the
host
name
element.
So
this
is
now
you
know
clarified,
and
the
last
one
we
see
on
the
screen
is
that
mandate.
That
extensions
should
not
use
well,
must
not
use
indefinite
length
encoding.
B
B
B
A
C
D
B
A
B
Yeah,
that's
a
little
bit
of
a
simple
weirdness.
What
Cris
really
Define
is
a
data
model
specification
and
what
representation
you
actually
use
in
the
encoding
is
kind
of
a
layer
below
but
saying.
If,
if
you
are
handing
around
to
your
eyes
on
their
own,
please
send
them
in
in
a
definite
length
encoding.
That's
a
good
thing
to
do,
but
if
it's
part
of
a
gigantic
data
structure
like
a
cosmic
or
something
actually
requiring
the
the
CI
item
in
the
crossword
to
be
definitely
length
encoded.
B
Is
that
puts
a
requirement
on
the
implementation
that
that
may
be
really
hard
to
do,
because
there
may
be
other
things
that
that
I
mean
there
may
be
an
image
of
the
code
for
a
device
in
the
Hedge
crossword.
So
you
may
have
some
need
for
for
indefinite
links
encoding
for
other
parts
of
the
cosmet.
So
it's
hard
to
instruct
the
sibo
encoder
to
to
actually
avoid
indefinite
length
encoding
for
the
actual
Cris
that
that
are
happening
in
that.
So
that's
why
I'm
always
a
little
bit
careful
with
mandates
like
this.