►
From YouTube: IETF-LPWAN-20220531-1400
Description
LPWAN meeting session at IETF
2022/05/31 1400
https://datatracker.ietf.org/meeting//proceedings/
A
A
A
So
if
you're,
if
you're
witness
of
a
situation,
that's
embarrassing,
please
notify
the
ombuds
team
and
you
see
the
url
up
there.
So
contact
slash,
ombuds
team.
These
are
the
people
you
should
contact
in
case
of
misconduct
or
harassment,
type
of
behavior
and
with
this
let's
continue
with
the
meeting.
So
the
meeting
is
now
done
done
under
mythical,
meaning
that
the
presence
is
logged
automatically.
A
A
So
we
have
a
very
simple
agenda
today,
we'll
be
discussing
the
progress
on
the
data
model.
As
you
know,
the
the
data
bundle
document
is
complete
for
the
working
group
and
now
is
being
pushed
to
the
asg,
and
so
during
the
steps
we
we
have.
The
first
iitf
last
call
reviews
from
tom
perch,
and
we
also
have
some
discussion
by
eric.
So
so
lauren
will
present
the
status
on
that
we
had
a
number
of
action
items.
A
C
Sorry
to
interrupt
just
on
the
agenda
because
we
had
this
last
minute
submission,
so
there
are
two
slide
sets
that
were
just
added
to
the
material
meeting
materials
one
is
for
chico
or
six
fox,
and
the
other
one
is
for
the
compound
pack.
So
these
are
answers
to
some
of
the
questions,
so
I
suggest
that
we
have
so
that
there
are
five
minutes
requested
for
each
of
them,
so
to
try
to
keep
ten
minutes
to
address
these
two
drafts
at
the
end.
If
that's
okay,
if
we're
okay
with.
B
A
A
A
A
Okay,
so
yes-
and
I
will-
I
will
again
call
for
comments,
because
the
work
last
call
is
not
officially
closed,
because
we
are
missing
comments,
so
yeah
when
you
do
it,
please
ping
me,
so
I
can
actually
pull
more
comments
through
the
list.
Okay,
neet.
Thank
you
so
much
our
group
status,
no
big
change.
We
are
actually
progressing
very
well
now
for
most
of
the
documents,
the
the
at
the
iot.
As
we
said,
we
are
close
to
concluding
our
google
plus
core.
She
covers
sick
fox.
A
A
D
A
Yes,
but
it
doesn't
matter
yes,
we
need
to.
We
need
to
refresh
it
we'll
be
working
with
with
alex
and
maybe
new
authors
if
people
want
to
join.
But,
yes,
we
need
to
to
publish
a
new
version,
but
when,
even
if
it's
expired,
you
you
continue
working
as
if
it
was
not.
I
mean
if,
if
version
2
expires,
then
we'll
need
to
publish
a
version
3.
A
A
A
E
So
anna
this
is
eric.
I'm
I'm
really
afraid
that
you
are
wrong
on
this
case.
That
is
a
good
news
for
the
working
group,
because
the
architecture
document
has
been
adopted.
It's
already
dash
zero
one,
it's
not
mistaken,
but
it
expired
right.
So
I
sent
an
email
this
morning
european
time
so
that
we
can
get
more
people
working
on
it
because
that's
this
important
document,
all
of
us
in
this
group
knows
what
is
ap
one,
but
many
people
outside
of
the
this
working
group
doesn't
know.
E
D
Yes,
I
mean
I
after
your
mail,
I
decide
to
to
publish
the
document
as
working
group
document
and
not
as
personal
document,
but
it
gives
me
an
error
that
it
exists,
respecting
the
version
two.
So
I
think
I
it's
expecting
the
version.
The
personal
version
too,
in
order
to
be
able
to
publish
as
iitf
document.
A
C
So
so
let
I
think
that
there
is
a
synchronization
point
that
we
connected
yes,
but
because,
when
I
go
to
the
website,
I
don't
see
this
the
same
thing
as
this
photo
that
you
have
here
active
internet
drafts
in
the
working
group.
The
architecture
graph
doesn't
appear
there.
When
I
go
to
the
page,
I
don't
but.
A
F
A
Yeah,
it's
just
expired.
We
get
the
notification,
but
we
need
to
find
the
time
to
work
on
it.
It's
just
a
matter
of
dedicating
some
time,
but
expired
doesn't
mean
much.
I
mean
as
soon
as
we
publish
202,
then
everything
will
be
back
on
track.
Yes,
it's
more
of
an
indication
that,
yes,
we've
been
lazy
on
this
document.
We
need
to
do
some
progress.
C
Yes,
okay,
it's
clear!
Now,
thanks
thanks
juan
carlos
okay,
okay,
there
was
also
one
minor
point
I
wanted
to
to
say
for
people
that
are
following
the
discussions
at
the
core
working
group.
So
there
was
an
email
about.
You
know,
running
lightweight
mtm
over
nidd
and
that's
an
interesting
question,
because
right
now,
when
we
have
shake
typically,
you
can
have
ip
over
an
idd
for
a
zero
cost.
Let's
say
so,
then
that's
going
to
be
and
and
I'm
very
happy
to
see
that
christian
is
also
here.
C
C
Co-Op
and
white
attention
over
an
id
would
be
through
the
use
of
shake
I
mean
because
of
ip
right
because
of
the
use
of
ip.
So
I
mean
I
don't
know
there
was
that's
a
very
interesting
discussion.
I
think
christian
pitched
in
a
very,
very,
very
interesting
way,
so
in
any
way.
In
any
case,
I
mentioned
that
there
is
the
nba
ut
draft,
and
that
is
the
right
time
to
actually
go
and
do
some.
C
G
A
A
A
A
H
Okay,
so
I
will,
I
will
talk
about
so
we
publish
a
version
12
of
document
and
now
we
are
going
to
toward
the
version
13.,
and
this
is
thanks
to
next
slide,
please
I
can
do
it
thanks
to
the
review
of
tom
and
eric
that
are
very,
very
constructive
and
it's.
It
will
help
me
to
understand
me
more
the
process
to
do
a
young
model
and
also
to
to
improve
a
lot
of
the
documents.
So
I
think
it's
very
beneficial,
so
I
will
skip
quickly.
H
H
E
Not
really
the
same
thing
right,
free
amplifier,
it's
about
oh
name,
the
fields
and
you
make
a
very
sensible
thing
right.
So
the
content
of
the
subsection
is
perfectly
fine,
but
field
lines.
Field
position
are
perfectly
correct,
so
I
would
say
three
to
three
convention
for
philosophy:
five
years:
that's
how
you
name
the
fields
right
in
the
young
module,
but
3.4,
3.5,
3.6
and
so
on.
E
H
H
So,
after
that
we
have
things
that
have
to
be
discussed
also,
so
eric
raised
also
a
good
and
dangerous
remark,
because
in
fact,
at
the
beginning,
when
we
had
the
target
value,
we
had
a
union
between
a
string
and
a
bitmap,
and
we
removed
this
to
just
keep
the
the
bitmap,
because
it
was
very
difficult
to
uncode
and
it
creates
a
lot
of
ambiguities
and
in
fact
we
we
say
that
everything
is
binary.
So
we
we
keep
something
binary.
H
The
problem
is
that
we
didn't
say
how
to
convert
a
string
into
binary,
and
that
may
lead
to
some
problem,
and
it's
not
only
here
that
we
we
can
have
the
problem
so
in
the
young
model.
For
for
the
moment,
we
use
strings
only
for
your
e-path
for
newly
queries,
and
if
I
look
at
what
is
given
in
the
co-op
rfcs,
he
says
that
it's
a
unicode
string
that
is
in
codename
uft
at
it.
So
eight,
so
we
can
keep
the
same
representation
and
it
will
fit
well
for
co-op.
H
H
H
G
A
D
H
H
E
H
H
A
E
H
H
Then
here
we
add
the
reference
to
the
specification
and
it's
also
in
the
text.
But
here
we
have
a
reference
that
can
be
used
by
some
tools
and
we
will
do
the
same
thing:
the
reference
to
82,
7,
87
22
for
the
grouping
and
all
that
stuff,
and
then
this
reference
also
have
to
appear
in
the
inter
in
the
internet
draft.
So
I
will
do
it
in
the
next
version
and
the
last
point.
H
H
H
So
the
question
is:
do
we
extend
the
consider
security
consideration
and
put
a
reference
to
coreconf
and
the
fact
that
we
can
use
co-op
s
or
or
not?
And
then
we
have
to
look
at
the
module.
So
for
me,
any
element
in
the
young
model
is
relatable
because
the
way
the
goal
is
to
synchronize
rule
between
two
elements,
so
they
have
to
exchange
information.
A
A
E
I,
if
you
don't
mind
interrupting
here
right,
so
this
problem
about
the
young
sick
models
with
the
missing
security
templates
is
happening
quite
often,
and
I'm
just
having
a
dhcp,
which
is
another
group
of
mine
young
models.
So
you,
the
best
way,
is
really
to
copy
and
paste
the
first
two
paragraphs:
okay
and
the
one
starting
with
there
are
numbers
of
data
nodes,
blah
blah
you
copy
characters
by
characters.
But
then
the
big
issue
is
to
list
subtrees
and
data
nodes
and
state
why
they
are
sensitive.
E
A
Yeah,
that
was
what
I
was
getting
at.
I
mean
what
would
be
the
impact
of
a
forged,
a
set
of
rules.
Could
you
attack
the
router
that
does
compression
or
decompression
in
such
a
way
that
you
know
the
code
loops
or
the
code
does
buffer
violation
or
the
god
does
this,
or
does
that
and
it's
it's
not
just
model,
but
it's
what
you're
writing
it
somehow.
A
A
C
A
C
Yes,
thanks
eric,
so
given
that
we
are,
we
are
right
right
on
time
actually,
and
we
have
even
a
couple
of
minutes
there,
so
we
can
go
on
with
the
presentation
of
of
the
additional
slides
that
we
had.
So
let
me
see.
Actually
I
need
to
see
how
to
put
them
so
with
the
shakeover
sickbox,
the
compound
deck,
and
also
there
was
some
very
interesting
discussion
with
so
robert
bob
initiated
a
couple
of
discussions
about
gtls.
C
A
I
I
So
you
can
so
basically
we
have
well
a
version
of
five
or
in
the
github
repository,
but
we
haven't
put
the
new
version
in
this
new
version.
We
remove
any
reference
to
the
cheek
receiver
award
in
this
case.
Well,
it
was
a
mistake
of
mine
that
I
I
thought
the
receiver
award
was
part
of
the
appendix
d,
but
no
so
at
the
end.
I
I
I
So
in
this
case
those
end
bits
will
signal
the
stop
of
the
compound
act
and
if
you
need
more
padding
bits
after
the
m
bits,
you
can
have
any
any
padding
value
that
you
wanted
and
that's
how
we
think
that
we
are
able
to
to
to
have
this.
No
not
saying
what
the
padding
bits
should
be,
but
we
just
need
m
padding
bits
to
signal
the
end
of
the
compound.
I
I
I
A
A
I
A
I
I
In
this
case,
we
reviewed
the
text
that
we
got
and
we
added
a
new
text
that
in
this
case
it
is
that
is
recommended
for
the
fragment
receiver
to
send
an
oblique
transmission,
for
example,
an
empty
message
and
request
a
downlink
every
24
hours
when
no
cheat
sessions
is
started.
This
is
for
not
in
case
a
downlink
needs
to
be
sent
to
the
device,
and
there
is
no
opening
session
currently
so
that
there
will
be
every
24
hours,
a
message
that
will
allow
this
to
unblock
the
downlink
transmission
so
yeah.
I
I
Actually
in
cheek
over
sig
fox,
and
that's
the
the
minimal
thing
we're
waiting
this
this
update,
so
that
we
can
push
the
the
new
version
of
the
of
the
draft
and
just
to
say
this.
New
version
includes
a
bit
of
changes
in
well
includes
the
new
versions
of
the
messages
and
includes
a
variation
in
how
it's
ordered
the
different
modes
that
are
available.
A
I
We
need
to
when
we
publish
this
version
is
ready
for
working
group.
Let's
call
we
just
need
to
add
this.
I
don't
know
if
we'll
be
an
appendix
or
or
where
we
add
it
or
on
the
recommendation,
how
to
use
the
rule
ids,
but
other
option
is
to
push
the
version
five
now
and
and
then
in
version
six
with
the
comment
of
the
working
group.
Let's
call
add
those
details,
but
I'm
not
sure
if
that's
okay
or
should
we
wait
a
bit
and
do
that.
I
Okay,
so
for
me
I
will,
I
will
talk
to
juan
carlos
well,
I
I
know
he's
here
so
to
so
that
we
can
push
this
new
this
version
and
we
can
start
well.
Then
we
will
ask
you,
the
chairs,
to
start
a
working
group
last
call
and
from
there
we
will
move
forward
with
a
new
version,
with
all
the
comments
that
we
receive.
A
A
C
Yes,
I
mean
I,
I
just
put
what
bob
said
on
the
email.
I
put
it
on
one
slide
and
and
added
the
two
last
like
the
last
line
is
for
me,
so
that's
for
for
full
disclosure
right.
So
I
give
the
floor
to
to
bob,
because,
basically
the
point
was
to
say:
okay.
Well,
there
is
the
this
this
question
about
dtls
in
chic
how
they
work
together.
There
have
been
some
work
and-
and
it's
really
interesting
to
hear-
because
bob
comes
with
a
real
use
case,
so.
B
I
think
okay,
thank
you.
Thank
you
for
the
introduction
I
started
out
by
looking
at
the
diet
esp
which
is
right
now
chic
like,
but
we
want
to
move
it
to
full
chic
and
the
question
came
up
is
how
do
you
know
inbound
that
this
esp
header
has
been
compressed
with
sheik
and
we
can
play
games
with
the
spy
and
our
spy
tables
to
say?
Oh,
this
must
be
as
she
compressed
and
by
the
implied
chic
rule.
B
We
can
kind
of
do
that,
but
it's
dangerous,
but
once
you
get
to
dtls,
it's
I've
looked
at
it
and
I
don't
think
it's
at
all
possible
to
play
that
game
with
dtls
and
also
get
the
udp
header
compression,
which
is
very
important
and
so
to
do
that.
I'm
looking
at
a
rather
dangerous
song
of
introducing
a
new
ip
protocol
and
of
course,
we
know
of
firewalls
and
gateways
and
other
things
about
adding
something
there.
B
This
is
important
in
the
way
that
I'm
seeing
to
do
end-to-end
sheet,
because
I'm
looking
at
multi
interface
communication
starting
up
first
wi-fi
switching
cellular
switching
to
uhf
back
again
or
maybe
simultaneously
over
multiple
to
make
sure
the
message
gets
through.
So
you
can
have
the
same
packet
going
three
different
ways
and
you
hope
one
of
them
gets
through
to
the
end
point.
A
C
A
Okay,
so
I
was
saying
we
we
have
a
similar
primance
on
serial
link.
Basically,
so
what
we
are
doing
is
we:
we
are
defining
a
new
pvp
compression,
so
a
new
ipcp
compression
for
for
ppp,
and
so,
if,
if
you
do,
if
you
transport
a
ppp
session,
then
you
would
generate
this
now
you're
having
it's
very
major,
because
we
are
compressing
and
now
I'm
asking
you
to
add
layers
of
our
layers
just
to
transport.
You
know
your
eyepiece,
it's
probably
a
bad
idea,
but
there
was
just
mentioning
that
that.
H
A
A
Send
it
over
to
the
sheet
processor
but
agreed,
but
compared
to
how
we
do
it
at
the
the
ppp
layer.
It's
we.
We
don't
say
it's
still
the
same
session.
If
you
like,
we
sing
on
a
session
the
old
same
way.
It's
just
that
we
have
signaled.
First,
that
this
section
will
be
so
you
need
to
have
a
point-to-point
session.
It
starts
there
because
there
can
be
a
lot
of
traffic
between
devices.
A
B
And
if
I
need
to
have
like
two
different
ones
with
esp
or
or
with
dtls,
I
have
the
the
cid
or
the
spy
to
to
just
to
to
indicate
which
sheet
groups
are
to
be
used
so
that
there
is
a
way
to
to
accommodate
that.
But
there
is
this
specific
use
case
and
when
particularly
looking
at
at
the
the
popular
mavelink
protocol
nobody's
out
there
using
it
yet,
but
it
looks
like
someone's
getting
set
up
and
it's
like
what
can
I
do
in
in
this
arena?
B
B
A
B
Yeah,
I
will
fold
you
the
message
that
we
had
on
the
on
the
ipsec
me
list.
Scott
floor
came
up
with
with
again
how
we
can
play
games
with
since
ike
assigns
the
inbound
spy
since
the
no.
You
know
what
spies
you
get
are
controlled
through
ike
you
can
control
which
spy
you
set
so
that
when
it
comes
in,
you
can
say
oh
yeah.
This
is
really
a
cheat
compress,
even
though
I
only
got
one
bite
of
the
32
bytes
of
the
four
bytes
of
the
spy.
B
C
Right,
I
think
so,
just
just
one
point
I
mean
tcp.
Also
you
have
like
the
I
mean
you
can
have
the
ports
and
all
that,
but
you
need
to
signal
some
way
that
they
I
have
tcp
on
top.
So
on
the
ip
layer
you
don't
know
what's
happening
or
your
theoretically
don't
know
what's
happening,
but
you
say:
okay,
I
have
tcp
on
top.
C
C
Where
probably
we
need
to
to
do
that
additional
work
of
of
maybe
stating
some
number
of
some
set
of
of
defined
predefined
check
rules
that
could
be
used
for
you
know
for
bootstrapping,
or
you
know
there,
there
is
something
else
right
I
mean
the
way
we
currently
do
when
we
want
to
run
shake
over
ip
is
like
we
encapsulate
ip
and
udp,
and
then
we
say
okay.
Well,
there
is
the
udp
port.
On
the
other
side,
and
I
mean
then
you
start
using
chick
on
top
of
that
over
ip
udp.
C
C
So
why
not
start
you
know
describing
it
and
so
that
their
description
is
already
there,
but
try
to
have
this
discussion
on
a
specific
document
and
to
see
where
it
goes.
So,
maybe
maybe
the
conclusion
would
be.
You
know
it's
too
complex
and
we
do
it
in
another
way
and
maybe
the
conclusion
is
okay.
We
just
need
to
assign
a
protocol
number
and
then
we
need
to
solve.
We
need
to
con
to
consider
these
other
considerations
in
the
architectural
document,
for
example,.
A
B
I
don't
think
I
need
a
ball
for
this.
I
mean
somehow,
we've
got
to
get
it
in
front
of
the
six-man
people
to
see
what
sort
of
a
panic
it
causes
for
them.
That's
gonna
be
eric's
job,
probably,
but
it's
I
can
over
the
next
week.
I
can
rough
out
a
draft
put
it
to
the
list
and
then
we
can
start
a
discussion,
see
where
it
goes.
A
I'm
asking
bob,
because
if
you,
if
you,
if
it's
v6
only
then
it
doesn't
have
to
be
ulp,
it's
just
a
next
header,
and
if
it's
a
next
header
that
you
know
something
you
you
place
indeed
this
well,
you
have
to
find
where
you
place
it,
but
the
next
header
would
tell
you.
Oh
it's
check
it.
It
could
also
have
a
session
id
or
something
because,
like
I
said,
you
need
a
little
bit
more
than
just
saying
it's
check.
You
need
to
say
well.
B
A
D
A
Endpoint,
you
need
to
keep
that
in
mind.
It's
designed
for
point
to
point
so
so
there
is
an
implicit
knowledge
that
everything
that
is
going
between
these
two
guys
is
a
single
chic
session,
and
if
you
go
over
ip
and
far
far
away,
do
you
have
a
single
chic
session
between
two
guys?
Could
there
be
that
you
have
more?
There
are
questions
to
to
answer
with,
with
with.
D
A
B
At
the
point-to-point,
because,
as
you
indicate
doing,
the
multiple
introduces
all
sorts
of
variability
and
complexities
and
then
that
you
can
get
quickly
buried
in
the
weeds
if
we
keep
the
use
case
straight
forward.
I
let
me
put
some
things
together
next
week,
pascal
and
and
get
it
out
and-
and
the
only
reason,
maybe
for
for
the
hot
above
higher
visibility-
is
that
this
is
a
new
header,
a
new
next
header
value,
and
what
do
six?
What
does
six
man
have
to
say
about
that.
A
D
B
H
A
B
C
B
A
A
But
yeah
you
are
breaking
up,
but
yes,
we
will
follow
up
on
the
mailing
list
and
we
are
at
the
top
of
the
house.
We
will
pass
the
top
of
the
hour,
so
I
guess
we
have
to
let
people
go,
but
thank
you
bob
that
that's
a
very
interesting
thought
and
very
interesting
discussion.
So
let's
follow
up
on
the
remaining
list.