►
From YouTube: IETF-LPWAN-20230131-1500
Description
LPWAN meeting session at IETF
2023/01/31 1500
https://datatracker.ietf.org/meeting//proceedings/
D
B
B
E
E
A
Okay,
this
is
this
is
a
intermitting
that
we
set
up
every
other
week,
so
once
every
two
weeks,
so
it
was
15
years
15
days
ago,
and
there
was
another
one
15
days
from
now
14
days
and
it's
all
on
the
lp1
page
on
ATF
data
tracker,
the.
If
you
need
more
information
and
all
this
please
just
ping
me
on
email.
D
A
D
A
D
D
A
A
B
F
To
do
yes,
yes,
no,
hello,
Pascal!
Thank
you
very
much.
Thank
you
all
and
hello.
Everyone
very,
very
nice
to
see
you
here
so
yeah,
let's
get
started,
so
this
is
some
official
meeting
of
the
lp1
working
group,
and
so
it's
an
official
ITF
meeting
and
a
search
for
ITF
policies
apply
local
various
topics
such
as
patents
or
kind
of
code
of
conduct.
F
F
So
with
this
we
can
move
on
to
the
agenda.
So
this
is
the
the
agenda
that
was
published
before.
So
we
have
a
big
point
about
the
re-chartering
and
this
today,
then
we
have
a
presentation
in
the
discussion
about
the
shake
data
model
with
both
48
so
congrats
for
getting
until
here
the
last
thing
last
mile
to
to
go,
and
then
we
have
a
discussion
about
the
architecture
and
next
steps.
F
E
Yes,
it's
maybe
just
a
primer
on
let's
say
I'd
like
we
discuss
a
bit
about
the
specification
of
chic,
but
there
may
be
some
some
stuff
that
we
can
publish.
That
would
make
it
easier
to
to
use
seeking
scenarios
when
you
use
Shake
over
something
with
tuning
and
all
that
stuff.
So
yeah,
just
just
a
heads
up
on
what
we've
been
walking
on
with
Mario
and
we
will
develop
that
in
the
main
list.
But.
F
B
F
Okay,
so
that's
good,
so
let's
I
propose
that
if
you
have
some
time
at
the
end,
you
can
talk
a
little
bit
more
about
it
and
if
not
I
mean
you
can
you
can
send
in
the
mail
and
and
we'll
and
and
don't
forget,
to
request
this
lot
for
for
the
next
time
and
you'll
have
a
proper
slot
about
that
over
that.
But
that's
excellent!
That's
excellent!
Okay!
Perfect!
F
Thank
you
very
much
Council,
so
moving
on
yeah,
so
we
have
the
state
of
the
different
drafts
and
the
that
are
in
the
in
the
different
states.
Let's
say
so.
We
have,
of
course,
the
Sheikh
young
data
model
and
Aloha
Montana
I'm,
going
to
talk
a
little
bit
more
about
that
later,
that
the
Android
in
author
48
and
we
have
she
cover
and
the
iot
that
is
in
the
RFC-
editor
queue.
F
F
Finally
did
my
homework
and
I'm
very
happy
about
this,
and
thanks
also
to
Sergio,
for
you
know,
for
making
the
last
changes
so
the
about
the
Chic
compound
deck,
so
I
put
I
published
the
the
shepherd
review,
so
I'm
not
sure
what
should
be
done
next
so
do
we
I
mean
it
is
sent
to
the
isg.
We
need
to
push
a
button
somewhere
or
I.
Don't
remember
from
here
what
was
what
was
the
next
stage,
foreign.
B
F
F
C
F
Okay,
so
so
actually
that
sounds
first
of
all,
really
great
that
we
have
another
like
a
review
with
some.
You
know
some
new
insights
and
to
me
it
seems
that
it's
almost
in
the
same
so
I'm
not
sure
what
what
content
Mario
want
to
talk
about,
but
I
get
the
feeling
it's
it's
in
the
same
Deen
like
having
read
a
bit
more
like
readability
or
like
finding
some
minor
errata.
G
B
G
B
G
G
B
F
B
A
A
There
were
some
issues
right,
it
was
the
war
group,
let's
go,
and
then
there
were
some
issues
on
it
and
then
we
fixed
it
and
blah
blah
blah
blah
blah
and
then,
to
be
honest,
we've
kept
this
shepherding
for
a
long
time.
So
it
was.
It
was
really
time
for
us
to
complete
the
shipping,
but
she
doesn't
work.
A
Will
have
a
little
slot
and
I
guess
Alex
you,
you
mentioned
pretty
much
everything
else,
that's
being
discussed
here,
so
we
can.
We
can
move
on
to
the
next
slide
and
the
next
slide
was
on
the
read
chartering
so
maybe
I
can
take
over
we,
we
discussed
it
twice
already.
This
is
the
third
time
we
discussed
the
recharging
text
in
this
meeting.
First
time
was
during
the
main
idea
of
meeting,
and
then
we
discussed
it
through
the
interims,
so
one
and
two
so
so
so
it's
Fourth
type
yeah
well.
A
The
first
intro
was
not
really
about
the
tax,
but
since
we
have
we
discussed
about
recharing
at
the
atf-115
and
then
through
the
interims
we've
been
discussing
the
text
already,
and
so
there
we
go.
The
background
text
is
kind
of
stabilized
I,
don't
see
custom
anymore
today,
but
we
with
cast
and
help.
We
are
very
much
stabilized
the
background
text.
We
feel
it's
useful
for
the
ASG
to
understand
what
comes
next.
A
A
This
one
has
changed
a
little
bit
since
last
time,
because
we
discussed
about
the
scope
of
the
group
and
so
the
text
after
the
description
of
last
last
time.
You
know
mostly
the
first
sentence
looks
now
like
what
you're,
seeing
so
the
scope
of
the
groups
to
enable
benefits
of
shake
for
to
to
report,
identity
networks
and
non-lp,
UI
Networks
and
and
so
we
include
Zero
Energy
Scavenging
devices,
as
we
include
dtl,
and
also
we
list
a
number
of
tools
for
which
we
could
do
Chicago
film.
A
A
C
A
We
need
to
write
that
down
because
that's
a
great
command
do
you
yeah,
we
could
generalize
it
so
so
make
the
second
sentence
of
the
second
paragraph
a
bit
more
generic
and
give
this
as
a
example.
We
see
I
I
still
wish
to
list
it,
because
it's
very
very
important
for
us
that
it
happens,
and
when
we
go
talk
to
Interior,
we
can
tell
them
hey.
You
know,
that's
really
something
that
we
are
chartered
to
work
with
your.
A
Mean
maintenance
is
always
part
of
the
charter,
but
it's
the
next
slide,
but
yes,
I
mean
keep
be
patient.
Please
bear
with
us,
but
you
will
see
that
maintenance
is
always
part
of
a
charter.
Part
of
the
reasons
why
you
reach
out
there
is
to
to
ensure
that
you
do
the
maintenance
of
the
previous
chart.
That's
for
sure.
A
So
for
this
one
I
I
keep
that
I
mean
look
I.
Keep
that
we
need
to
make
the
second
Center
in
general,
but
I
mean
if
you
look
at
the
first
sentence.
I
was
worried.
That's
what
it's
seeing
right!
I
mean
we
could
instead
of
saying
for
this
in
the
second
sentence,
we
could
say
as
an
example,
but
this
first
sentence
is
very
generic
and
much
of
saying
no,
do
you
think
it's
foreign.
C
A
A
C
A
But
I
mean:
do
you
want
to
share
the
chatter
to
be
more
specific
about
that?
Or
is
it
you
know
the
goal
at
the
end
of
the
day?
Is
we
need
to
Signal
the
staff
session?
We
need
to
signals
playing
applications
playing
device
when
we
know
all
this,
but
basically
the
prime
comes
because
we
have
new
networks
which
are
multi-hop
and
can
be
peer-to-peer
as
opposed
to
hierarchical
and
and
so
at
the
end
of
the
day,
we
need
more
data
plane
signaling
for
the
Chic
session
right.
C
A
A
B
D
A
B
A
Need
to
move
on
so
let
me
just
save
what
they
have
so
I
I'm
saving
on
the
Dropbox.
What
I
just
said
moving
on
so
the
point
content
that
you
made
about
chick
maintenance.
It's
the
first
item.
It's
no
surprise
in
this
Charter,
so
the
work
that
you
seem
to
be
willing
to
conduct
would
fit
I
guess
in
item
one.
B
B
A
Okay,
okay
multi-hub
is
not
from
the
previous
Charter
you're,
always
one
step
ahead
from
us
here.
So
so
the
way
the
slides
are
cut
those
they
generate.
What
we
need
to
do,
then
there
is
this
slide
two,
which
is
what
we
continue
on
the
previous
Charter
and
then
there
is
slide
three
and
what
comes
new
for
the
new
chapter
and
everything
multi-hop
is
new.
So
it's
the
next
slide.
A
F
B
E
A
A
A
F
G
And
the
word
to
do
it
as
soon
as
the
working
group
is
ready
to
with
a
charter,
you
send
a
text
to
me:
I
put
it
into
the
data
tracker
and
it
starts
internal
consultation
within
the
ISD
and
iub
for
about
two
weeks
between
two
teleschat.
Basically,
then,
it
goes
for
kind
of
a
last
call
right
so
basically
to
the
community
to
get
any
feedback,
but
basically
again
it's
pretty
much
as
soon
as
you
ask
me
to
do
it.
G
A
A
C
C
C
So
the
thing
was
about
a
union
that
was
made
that
you
know
the
type
Dev
and
I
would
like
to
move
this
Union
into
the
the
structure
by
itself,
because
it's
some
validation
tools
doesn't
see
it
when
it's
in
the
type
def.
So
that's
the
main
change
and
the
other
change
I
wanted
to
to
Pro
I
wanted
to
propose
is
to
add
something
to
distinguish
a
co-op
option
from
Co-op
overheaters.
C
So
we
got
the
notification
for
r48
this
morning,
and
so
we
have
now
the
nice
LFC
number
is
96
and
96
63,
no
89
that
I
don't
remember,
but
and
this
so
I
will.
There
is
some
details
to
change
our
proposed
changes
by
the
FCA
editor.
But
it's
not
that
that
difficult
to
to
answer
to
these
questions,
I
wait
Anna
to
come
back
to
to
do
this,
and
so
next
week
we
will
have
a
new
version
and
we
will
discuss
also
a
realize
the
editor
to
to
modify
the
young
data.
C
A
B
A
A
Well,
I
wanted
to
basically
Pour
at
least
the
people
in
this
call
to
see
if
everybody
agrees
that
what
law
is
saying
makes
sense,
I
do
agree,
but
but
to
make
sure
there
is
no
nothing
I'm
missing
at
least
that
people
in
this
call
can
see,
and
the
email
is
depending
on
the
mailing
list
as
well.
So
I
guess
when
Nana
comes
back.
If
there
is
no
position,
please
do
those
changes
and
go
ahead
with
the
OS
48.
G
C
C
Another
point
I
would
like
to
to
ask
to
the
group
is
that
now
we
are
about
to
as
a
young
data
model,
so
I
think
it's
now
time
to
request
seeds
for
this
young
data
model,
and
the
other
point
is
that
we
don't
I
I,
think
we
don't
have
to
use
the
default
seed
numbering
because
we
raise
already
that.
That
issue
is
that,
for
example,
rule
ID
length
and
Rule
ID
value
are
far
away
in
the
data
model,
which
means
that
it's
not
very
efficient
to
cut
them
in
using
C
bar.
C
G
F
So
actually
there
is,
there
are
two
types
of
yes,
so
ever
yes,
you're
right
to
some
extent,
so
there
are
two
seed,
Registries
two
levels,
so
the
Big
Blocks,
it's
not
Ariana.
That
is
going
to
so
it's
like
on
a
very
high
level
and
then
for
for
some
rfcs
that
request
see
the
location.
There
is
going
to
be
a
registry
about
that,
and
actually
it's
I,
if
I
recall
correctly,
I
need
to
double
check
the
document.
It's
it's
just
a
column.
F
Yes,
yes,
no,
no
I
mean
it's
I
I
understand
that
it's
it's
it's
not
as
straightforward.
As
you
know,
it's
not.
How
can
I
say
it
was
simple,
a
simple
answer
to
to
this
one
right,
but
in
any
case
you,
you
have
no
place
to
to
request
to
see
the
location
today
so
okay
and
that
that
will
come
right
that
will
come
and
we'll
we're
waiting
for
the
RFC
for
for
some
time
now,
and
we
had
some
last
disc.
F
C
A
This
with
this,
we
can
move
to
the
next
item,
which
is
the
next
steps
for
the
architecture
document,
and
you
know
that
this
is
a
document
that
is
a
very
dear
to
us
and
even
and
I
guess
Laura.
You
are
behind
I've
been
working
on
some
suggestion
and
the
thread
has
started.
Anna
has
started
started
responding
to
this,
so
what
I
did
is
I
kind
of
collected
the
comments
by
Ivan
and
even
since
you're
with
us.
Maybe
you
can
argue
or
explain
what
you
had
in
mind
with
those
commands.
So
there
are
two
slides.
A
A
H
So
I
think
it's
better
now
so
yeah.
So
the
idea
was
to
what
I
did
was
with
Lauren.
We
read
a
bit
carefully
again
this
draft
and
we
think
we
should
change
the
the
arrangement
or
ID
or
at
least
make
me
make
more
clearer
how
the
sections
are
organized
and
then
how
to
add
some
content
to
each
one
of
the
sections,
because
the
main
point
is
that
we
now
are
going
from
one
hop
topology
to
a
star
topology.
H
Yeah
so
they
well
yeah.
So
that's
the
main
argument.
Anna
told
us
that
maybe
we
can
start
just
saying:
where
are
the
main
use
cases,
and
then
from
that
we
can
build
General
topology,
but
it's
it's
kind
of
tricky,
because
what
will
be
this
architecture
in
this
point?
Maybe
a
multi-hub
topology
is
the
general
one
and
then
a
multi
one
hop
over
an
star.
Topology
is
a
subset
of
that
one.
So
that's
that's
the
idea.
So
the
idea
is
just
to
review
the
document
and
then
to
rearrange
the
sections
yeah.
A
Well,
that's
said
it
is
a
big
vague,
but
your
text
was
more
specific.
So
so
that's
good!
Yes,
we
we
are
clearly
going
to
something
which
covers
multi-hop
as
well
as
single
hub,
but
yeah.
At
the
end
of
the
day,
as
soon
as
you
define
a
Chic
session,
you'll
you'll,
whether
it's
Monday
Hub
or
a
single
Hub
below,
doesn't
matter,
you
still
have
two
nodes
talking
to
one
another
over
the
bike,
whether
it's
one
Mac
address
to
one
Mac
address
of
our
single
Hub
or
whether
it's
of
our
tunnel
point-to-point
tunnel.
H
A
It's
a
collapsed
version
where,
like
Laura,
for
instance,
just
to
give
you
know
the
most
used
example
the
some
of
those
parameters
that
we
have
are
kind
of
collapsed
right,
because
you're,
one
hop
and
and
the
session
is
not
signaled
but
implicitly
it's
there
and
we
have
takes
for
that.
But
it's
not
that
we
are
not
covering
it.
It's
more
like
you
want
a
different
organization
right.
C
It's
it's.
What
we
thought
is
that
it
was
better
to
start
with
what
we
know
right
now
about
the
start,
topology
and
server.
This
can
be
extended
to
other
kind
of
topologies
and
then
say,
but
you
see
it's
the
same.
It's
acting
in
the
architecture
view
it's
the
same,
and
then
we
enter
into
the
the
definition
of
this
architecture,
all
the
elements
and
that's
all,
but
it
doesn't
change.
The
content
is
Murphy
organization.
A
I'm,
comparing
what
you
have
on
that
slide
and
what
we
have
on
the
original
document.
A
the
document
has
some
introduction
like
something
on
lp1
Technologies
and
profiles,
something
on
shake.
So
it
basically
says
what
what
the
Sheikh
and
the
Sheikh
profile
is
all
before
it
really
goes
into
architecture.
A
A
A
That
is
already
in
the
document
which
doesn't
which
is
not
clearly
positioned
in
your
proposal
and
I'm,
trying
to
say:
okay,
if
I,
if
I
wanted
to
go
towards
what
you're
proposing
what
do
I
do
with,
for
instance,
the
current
section
2,
which
is,
if
you
want
Technologies
and
profiles,
three,
the
broad
thing
about
help
you
want
and
I
I,
don't
even
see
it
in
your
new
proposal,
anymore,
I,
don't
know
what
to
do
with
it,
which
is
very
small
right.
It's
mostly
something
which
says
hey.
A
There
is
what
lp1
has
been
producing
and
then
three
seven,
six,
seven,
eight,
seven,
two
four
Etc,
it's
just
some
you!
So
you
could
tell
me
hey
your
section,
took
it
going
intro,
okay,
I'm
good,
say:
section
two
goes
introduction,
so
our
current
section,
three
about
chick,
pretty
much
becomes
your
section
two
kind
of
a
line
because
they're
about
eight
seven
to
four,
but
you
want
to
regroup,
Shake
applicability
in
section
two
right,
so
she
applicability
Anna.
You
want
to
take
the
current
section
2,
which
is
a
P1
profile.
It.
A
Mean
whether
whether
we
collapse
two
and
three
into
a
two
what's
more
interesting,
is
you
want
your
section
2
to
focus
on
Startup
energy
right?
You
don't
want.
You
want
the
current
support.
The
current
support
is
tall.
We
get
the
network
Gateway
and
we've
got
the
devices
talking
to
the
Gateway.
It's.
D
C
But
it's
scary,
for
example,
we
have
5.1
that
take
the
lp1
architecture
and
maybe
it's
too
far
away,
maybe
it's
better
to
to
put
it
at
the
beginning
and
say:
okay.
This
allows
that.
But
we
have
some
limitation
and
then
we
we
open
it
to
our
example.
And
then
we
go
to
the
architecture,
all
right,
which
is.
D
G
B
B
B
A
Mean
what
what
is
Shake
used
for?
That's
for
that's
the
current
section
for
Chica
pregabality
and
that's
where
we
say
compressing:
several
stream
goes
dlms
existing
mp1s.
It
applies
to
more
than
just
existing
mp1s,
but
clearly
it
applies
to
existing
a
few
words.
So
so
she
kept
the
ability
section.
Four
now
I
I,
don't
mind
that
that
we
keep
it
three
section
or
we
collapse
that
into
one
session.
A
As
a
section,
I
I
doesn't
really
matter
yeah.
We
could
make
it
a
single
section
if
you
want
to
so
it
would
be
not
just
two
and
three,
but
basically
two
three
and
four
that
you
would
like
to
to
collapse,
but
even
the
beginning
of
five,
when
it
has
to
do
with
star
networks,
I
guess
I'm
trying
to
understand
right.
F
A
A
F
F
A
A
B
A
B
A
I
I'm,
not
too
happy
to
have
I
mean
the
point
that
you
remainder
like
having
one
store
architecture
and
then
one
generic
architecture
I
want
a
single
architecture
which
does
star
engineering.
Okay,
and
basically,
we
wanted
to
show
that
store.
Lower
is
just
a
generic
one
where
you
collapse
number
of
things
and
the
session
is
not
signaled,
but
it's
still
implicitly
there.
A
H
A
A
A
A
A
B
F
A
Well,
you
could
sing
all
the
sessions,
it's
just
that
loja.
For
instance,
there
is
one
session
per
device,
so
the
session
ID
is
read
up
the
MAC
address
of
the
device,
because
there's
only
one
session,
that's
pretty
much
it,
and
then
it
goes
all
the
way
to
to
the
network
server
and
so
that
the
peers
are
on
network
server.
F
F
Okay,
so
I
mean
I
think
that
that's
really
the
the
important
question
here
and
like
how
do
we
structure
that
so
we
are
past
the
hour,
so
maybe
even
maybe
you
can
I
don't
know
we
can
go,
get
that
to
the
mailing
list
or
you
can
just
like
think
about.
You
know
how
that
fit.
With
put
your
proposal
of
reorganizing
the
SEC,
the
sections
I,
don't
think.
That's
like
a
big
issue
there
and
I've.
F
F
Okay-
let's
maybe
get
back
to
this
question
on
the
next
interim
or
the
mailing
list,
because
it's
we're
it's
a
super
interesting
discussion
that
is
like
a
big
chunk
of
a
work
and
we're
not
going
to
be
able
to
to
get
them
to
any
meaningful
I.
Think
yes,
Eric!
Thank
you
very
much
for
for
being
here
so
yeah.
Thank
you
as
well.
So
let's,
let's
stop
here
and
we'll
continue
on
the
mailing
list
and
enter
the
next
interview.