►
From YouTube: IETF114 LPWAN 20220727 1730
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
A
A
Well,
please
move
it
just
next
slide.
So,
as
usual,
we
have
the
traditional
ietf
network
so
be
aware
that
we
have
a
code
of
conduct,
that's
bcp154
and
entire
harassment
rules.
A
Now,
if
you
feel
that
you're
a
victim
of
anything
related
to
harassment
or
bad
conduct,
please
contact
the
ombuds
team
and
you
can
see
the
link
of
this
page
and
you
will
see
the
exact
same
slide
on
every
other
meeting
and
obviously,
as
usual,
we've
got
rules
about
ipr.
So
if
you're
aware
of
ipr
a
new
ipr
undisclosed,
ipr
that
is
being
discussed
today,
please
mention
it
to
the
the
mic
or
to
the
chairs
or
on
the
mailing
list,
or
refrain
from
talking
about
that
ipr
at
all
next
slide.
A
So
we
have
two
types
of
participants
in
scavid.
As
you
know,
some
will
be
in
person
in
the
room.
Some
will
be
remote
if
you're
in
the
room.
Please
join
the
mythical
light
application
that
you
can
download
from
data
tracker
on
your
phone,
so
you
can
join
the
mcq.
The
chairs
will
be
handling
the
mcq
in
the
as
a
single
queue
from
for
remote
and
local
participants
for
remote
participants.
A
Please
keep
your
audio
and
video
off
unless
the
chairs
are
giving
you
the
the
right
to
speak,
and
yes,
if
you
can
use
the
net
set
to
avoid
decode
next
slide.
Please.
A
Okay,
so,
as
I
said,
we
have
a
pact
agenda,
so
we'll
be
going
through
the
agenda
bashing,
and
it's
going
to
be
me.
I
guess
then
anna
will
pass
the
status
of
the
shakeover
mbiot
lauren
the
sheikh
little
model
and
both
of
them
are.
You
know
at
the
latest
stage
for
this
working
group.
So
we
ask
we've
been
asking
the
document
publication.
A
A
Then
we
have
an
interesting
new
proposal
by
robert
bob
muskravich
about
having
a
shake
ip
number
note
that
this
work
is
not
currently
chartered,
but
who
would
like
to
to
test
interest
in
this
room,
then
I'll
be
talking
about
the
architecture
draft
that
has
evolved
and
we'll
be
discussing
about
opportunities
to
recharter,
based
on
the
recent
evolution
of
what
people
want
to
do
with
sheikh
next
slide.
Please
show
up.
A
A
Okay,
so
one
group
status,
we
basically
had
a
number
of
milestones
which
are
passed
and
for
the
chicago
six
fox
and
and
chicago
and
the
iot.
A
A
A
So
document
advancement,
as
I
already
said,
the
we
have
great
progress
for
the
nba
utn
young
data
model,
for
which
the
publication
request
method
was
pushed
and
the
early
iatf.
Let's
go,
reviews
started
fighting
for
the
young
data,
but
also,
I
hope
lauren
gives
us
the
status
on
that,
in
particular.
Are
the
young
reviews,
the
I
don't
think
anything
has
yet
started
for
the
nba
team
and
there
is
the
cubes
are
actually
loaded
for
many
of
our
id's
so
new?
A
As
you
can
see,
there
are
new
version
for
all
of
the
documents,
either
in
june
or
in
july,
so
we
we
are
working
and
progressing
very
well
in
this
group.
So
thank
you
all
for
this
next
line
and
yes,
as
I
said
at
the
end
of
the
the
meeting,
we'll
be
discuss
discussing
rechartering
and
basically
the
main
reason
for
that
is.
On
the
one
hand,
we
want
to
extend
to
new
technologies
and-
and
bob
is
discussing
the
some
basically
flying
object
networks.
A
A
A
A
A
So
looking
at
things
like
that
could
be
of
interest,
and
then
there
is
bob's
proposal
for
the
chic
next
header,
which
is
also
not
in
the
charter.
So
basically
looking
at
how
we
expand
chic
for
other
spaces,
larger
spaces
could
be
of
interest
for
this
group
and
they
would
like
to
take
the
sense
of
the
room
and
then
sense
of
the
working
group.
If
people
are
interested
in
pursuing
the
work
in
those
direct
directions
and
with
this
we'll
move
with
the
first
edge
of
the
item-
and
I
think
that's
anna.
D
Thank
you
very
much,
so
I
will
present
the
the
last
version
of
the
cheek
of
our
nbiot
draft
we
published
on
july
next
slide.
Please.
D
So
we
we
have
made
in
this
version
10
the
the
inputs
from
the
review
of
pascal.
Thank
you
pascal,
principally
the
references
were
arranged,
informative
and
normative.
We
also
updated
the
cross-reference
with
the
sections
most
of
needs
about
the
reference,
because
it
was
very
difficult
to
design
it
with
the
new
xml
version.
3
the
3gpp
references.
It
was
a
little
bit
complicated,
so
one
one
thing
that
we
can
we
can
say
of
this
draft
is
that
more
of
the
features
are
recommendations
for
3gpp
in
order
to
use
chic
for
for
the
nba
ut
network.
D
So
one
of
the
comment
of
pascal
was
if
we
need
to
define
an
mtu
size
of
1358
bytes.
So
the
thing
is
that
we
are
recommended
to
use
this
mtu,
even
if
the
3gpp
networks
accept
larger,
larger
sizes
of
1
1600.
So
it's
enough
for
a
normal
ip
packet.
D
So
the
other
comment
was
about
the
different
stack
we
have
in
the
in
the
draft.
So
again
we
we
have
divided
the
draft
in
three
users
cases.
The
first
one
is
the
use
of
cheek
in
the
radio
link
where
we
have
the
ip
pdc
plc.
Mac
stack,
chic
is
included
in
the
pdcp
layer
and
in
this
stack
you
have
a
segmentation
in
rlc,
so
most
of
the
fragmentation
we
decide
not
to
use
it.
D
We
only
use
the
the
compression
of
chic,
except
for
the
transparent
mode
where
there
is
no
segmentation
in
rsc,
and
then
we
decide
to
recommend
the
use
of
chick
fragmentation.
D
The
other
use
is
in
the
north
access
stratum
in
donas,
where
you
have
the
ip
packet
over
the
rrc
rlc
mac.
So
there
chic
will
be
using
the
error
c
layer
and
again
you
have
the
segmentation
in
rlc,
so
we
are
using
only
compression
but
not
fragmentation,
and
in
the
last
case
you
have
an
end-to-end
connection.
You
have
ip
over
cheek
over
mac
and-
and
that's
in
that
case
we
recommend
to
use
chic
compression
and
fragmentation.
D
A
Many
thanks
anna
do
we
have
any
question
in
the
room.
E
B
B
B
So
what
we
have
done
and
what
is
one
of
the
main
change
since
the
previous
version
is
that
the
timer
values-
and
I
will
explain
in
the
next
slide
so
next
slide,
please
so
we
we
are
here
all
the
modification
we
have
done
in
in
the
model
until
this
version
14..
So
the
first
one
was
to
clarify
the
old
one,
because
it
could
have
an
ambiguity,
because
you
have
a
l
on
the
one
that
are
very
similar
and,
of
course
we
cannot
change
the
standard.
B
D
B
And
the
main
change
is
in
the
way
we
manage
timer
before
it
was
you
win,
uint
64
and
which
engine
is
something
that
is
more
flexible
and
if
you
can
go
to
the
next
slide,
we
we
use
so
a
thick
duration
and
a
tick
number.
So
the
tick
duration
is
a
formula
where
you
have
two
power:
arctic
duration,
divided
by
10
power.
B
Six
that
give
us
when
the
fix
duration
is
zero,
a
unit
of
one
microsecond,
and
if
you
increase
the
tick
duration,
you
increase
this
unit
and,
for
example,
when
you
put
the
value
20,
then
you
have
about
one
second
for
extinct,
duration,
so
then
to
set
up
a
timer.
We
just
give
the
number
of
ticks.
We
we
want
or
six
number,
and
this
way
we
can
cover
different
range
and
different
usage
for
chic.
B
One
can
be
up
to
the
micro
second,
so
it
could
be
useful
for
real
time
and
we
can
go
if
we
increase
the
the
tigration
to
several
years,
a
lot
of
years
even
to
for
for
the
timer.
So
what
we
choose
to
use
as
a
default
value
is
20,
because
we
have
a
tick
of
about
one
second
and
the
maximum
timer
is
19
hours
and
the
row.
B
B
D
B
Propose
a
change,
so
we
have
to
discuss
on
that
on
on
the
mailing
list.
So
let's
next
slide,
please
is
to
add
a
new
leaf.
That
is
a
rule
nature
and
this
rule
nature
will
tell,
if
is
a
compression
or
a
fragmentation
rule
and
inside
each
definition
of
the
compression
content
and
the
fragmentation
content.
We
make
a
test
to
see
if
we
follow.
We
are
on
the
right
nature
and
we
don't
need
anymore,
no
cooperation
as
a
choice
because
it
was
ineffective
and
it
will
not
have
been
rich
at
any
at
any
time.
B
So
that's
a
significant
modification
we
made
from
the
model
and
it
will
be
published
in
with
the
new
version
of
the
of
the
drive
so
next
time
so
just
to
to
conclude
on
it,
something
that
came
when
we
had
to
write
the
security
review
or
security
chapter
is
that
right
now
the
young
data
model
we
are
using
is
just
respecting
what
is
saying
the
rfc
and
it's
a
way
to
have
something:
a
command
between
a
device,
a
core
or
a
chic
upper
chick,
and
maybe
your
repository
when
we
will
have
the
roof.
B
But
until
now
we
don't
you,
we
don't
identify
the
device
and
it's
something
that
is
very
important
and
we
need
to
have
this
in
the
architecture
graph.
So
next
slide
this
to
identify
the
the
device.
So
we
we
have,
I
think,
to
work
on
that
part.
So
how
we
do
the
notification,
for
example,
in
openshift,
we
have
two
kind
of
devices.
B
B
The
rfc
1999
39
that
define
a
url
for
this
device,
so
we
have
to
see
if
it's
convenient
with
a
compact
representation,
because
this
is
urn
and
they
are
in
a
ski.
So
there
is
other
work
at
the
atf
to
to
compress
url
and
urn.
So
maybe
we
can
use
it
or
maybe
also
use
the
arcade,
a
compact
notification
in
the
young
model.
B
So
that's
one
thing
that
would
be
important
to
to
define-
and
the
last
point
is
that
when
we
will
have
these
ids,
then
we
can
add
this
id
to
the
young
model
with
young
data
model
we
have
defined
and,
for
example,
if
we
don't
put
ids
it
could
be,
it
could
fit
a
point-to-point
model
if
we
just
put
the
device
id
we
are
in.
As
we
are
right
now
in
the
star
topology,
and
if
we
put
the
device
on
the
core,
then
we
can
reach
the
constraints
from
mesh
network.
A
Thank
you
very
much
loho
and
we'll
be
moving
to
sergio
so
sergio.
Can
you
jump
to
the
mic.
F
Hello,
I
will
present
a
compound
graph
in
this
case,
the
path
to
publication.
Can
you
put
the
next
slide?
Please.
F
There
you
go
well
one
of
the
biggest
changes
that
we
did
on
version.
Five
was
that
we
changed
the
the
way
padding
bits
are
handled
before
we
said
that
padding
bits
must
be
zero.
F
According
to
the
the
review
with
dominique
and
the
spirit
of
the
rfc
8724,
that
it
has
no
padding
bits
defined.
The
idea
was
to
to
not
specifically
define
the
padding
bits,
but
we
needed
a
way
to
actually
differentiate
the
the
last
window
from
from
extra
bits,
so
we
decided
that
we
will
use
m
bits
as
zero
that
can
be
used
when
you
need
to
add
more
than
inputting
bits
to
the
message.
This
way
you
this
mbit
signal
the
end
of
the
compound
other
changes
were
more
specifically
format.
We
remove
any
reference
to
the
receiver
award.
F
We
also
re
remove
any
bound
of
that
qi
compound
act
to
hack
on
error.
This
was
removed
in
introduction
and
in
many
other
areas,
and
also
we
provided
compressed
bitmap
examples
on
how
to
use
a
compound
with
with
compressed
bitmap
another
big
change
that
we
did
actually
was
that
we
added
the
complete
section
of
the
rfc
8724
section,
eight
four,
three,
the
aqua,
nero
mode
with
all
the
changes
on
how
to
use
the
compound
knack.
Actually,
it
was
difficult
to
to
read
where
the
specific
changes
had
to
be
done.
F
In
this
sense,
we
we
specified
that
the
rfc
that
jack
on
the
rfc8724
is
a
special
case
of
the
of
the
compound,
in
the
case
with
one
window
of
tiles
and
finally
well,
we
need
to
define
the
next
steps
on
on
this
draft
and
we
would
like
to
thank
also
dominique
for
all
the
for
the
review
and
all
the
on
all
the
work
that
he
has
done.
Thank
you
very
much.
F
F
F
F
Also,
we
stated
that
confirmed
that
we
confirmed
with
appendix
f
we
added
some
new
text
that
is
actually
well
in
this
case
that
we
recommend
a
message
to
be
sent.
It's
24
hours
to
enable
the
downlink
transmission.
F
Also,
well,
we
changed
some
terminology
of
how
we
we
it
was
written
the
draft
also.
Well,
we
added
some
information
about
the
ups
and
down
link
messages,
how
the
downlink
is
enabled
in
sigfox
and
well.
This
is
a
topic
that
maybe
we
can
discuss
at
the
end
regarding
the
detect
and
the
rule
id,
we
added
the
information
regarding
the
the
that
we
believe
that,
with
this
amount
of
rules
like
this
is
enough
for,
for
the
purpose
of
identifying
different
flows
in
the
in
the
transmission.
F
Also,
we
added
some
recommended
values
for
inactivity,
timer
and
retransmission
timers
and
fine.
This
is
yes
and
another
question
was
regarding
the
rcs
in
this
case.
This
was
also
presented
in
that
ietf.
We
changed
how
the
rfc
is
calculated.
Actually,
what
we
send
is
just
the
number
of
of
tiles
of
the
last
window,
and
and
that
way
we
are
able
to
recover
to
know
how
many
fragments
are
lost
in
the
last
window,
and
we
are
able
to
reconstruct
that
the
message
as
the
crc
is
already
checking
layer,
two
of
the
sig
folks
fragment.
F
A
Yes,
so
the
the
shepherd
as
people
guessed,
the
shepherd
for
the
first
document
is
I
likes
actually
and
the
second
is
anna.
So
that's
why
you
got
the
the
reviews
for
now
and
I
guess
you
will
get
the
review
from
alex
the
shepherd
review
from
alex
very
soon
that
mentioned
in,
but
alexander
could
not
be
with
us
today.
So
it's
very
sad,
but
yes,
we
will
do
without
him
and
now
yes,
please,
move
and
now.
D
Yes,
I
have
a
question
about:
do
we
need
to
to
wait
on
the
compound
act
has
been
published
to
publish
six
folks
or
we
are
going
to
send
it
both.
At
the
same
time,
oh.
C
A
A
So
even
if
the
the
shakeover
sick
fox
progresses
faster,
since
it
has
this
normative
dependency,
it
will
have
to
to
wait
in
miss
raf
at
the
rfc
did
our
queue,
but
it
won't
be
long
because
the
two
of
them
will
be
posted.
You
know
almost
simultaneously.
A
A
G
And
hold
the
mic
and
let
me
go
okay.
This
presentation
is
of
I
as
ip
pro
card
number
for
sheik,
and
this
did
not
come
out
of
my
work
on
forward
error
correction,
which
I
did
in
in
raw.
So
please
go
to
the
next
slide.
I'll
say
why
I'm
doing
this
and
networks
are
complex
and
one
of
constrain
links
is
within
the
path.
There's
end
points
no
know
the
constraint
but
have
no
control
over
it.
G
This
is
an
avionics
on
an
ethernet
on
the
plane
and
knows
it's
got
a
control
link
going
to
a
data
center
somewhere
in
the
on
on
on
the
internet
and
and
those
that
definitely
gets
there,
but
cannot
interact
with
it
directly.
All
ip
content
is
with
a
non-compressed
security
wrapper,
there's
that
as
well
example.
This
guide
esp
wants
to
compress
a
security
wrapper,
but
how
to
flag
this
I'll
then
do
a
special
spy,
which
is
how
the
draft
is
right.
Now,
dtls
much
of
the
udp
can
be
derived
from
dtls.
G
So
these
are
two
examples
of
how,
if
I
had
sheet
as
my
header,
I
can
do
things
so,
if
ipv6
next
header
worksheet
the
rules
can't
compress
the
transport
and
all
up
to
the
security
envelope
can
even
indicate
what
rules
for
within
the
security
envelope
can
also,
as
also
end
to
end,
so
I
gained
some
additional
controls
in
an
antenna
environment.
If
I
were
to
have
sheik
saying
that
this
payload
is
to
shake
apply,
the
rules
can.
C
G
Effectively,
when
you
do
this
sheet,
becomes
the
transport
layer
to
transmit
the
original
transport
layer
compress.
No,
why
have
udp
crc
when
I
have
the
the
icv
in
in
dtls
or
esp?
Why
do
I
have
to
also
carry
the
crc
as
well
squeeze
it
out
and
then
rebuild
it,
provide
new
and
then
provide
new
and
valuable
transfer
functions
like
an
end
to
end
forward
error
correction,
which
I
presented
earlier
presentation.
G
So
can
so.
This
is
the
the
how
here's
my
technical
slide
have
to
have
one
technical
slide.
It
review
the
current
protocol
numbers.
I
went
through
them,
there's
nothing
that
I
could
camp
on
to
do
this
now.
Is
there
any
protocol
number
I
can
use?
No,
I
can't
I
need
one.
So
we
have
a
chic
protocol.
Payload
a
rule
id
could
be
zero
bytes.
So
basically
you
have
your
your
rule.
I
you
have
the
the
chic.
G
G
Next,
better
value,
will
it
just
work
or
do
we
need
router
upgrades?
What
would
happen?
Will
the
routers
be
dropping?
Oh,
I
don't
know
this.
This
ip
protocol
number
drop
it
that
that's
a
six-man
question.
What
might
I
p
fragmentation
resulted?
G
Do
we
need
to
force
don't
fragment
because
with
what
what
is
being
done,
you
no
longer
have
a
transport
blank,
and
now
you
have
that
so
these
are
questions
need
to
be
answered.
What
else
could
go
wrong
happen?
Existing
not
fused
value,
really
bad
idea.
E
G
G
Is
this
a
field
of
dreams
isn't
what
the
internet
is
about,
though?
Let's
just
do
it
adopt
it
as
a
work
group
item
get
this
additional
functionality
for
those
of
us
who
want
to
use
it
and
to
end
take
advantage
of
all
the
good
work
you
have
done,
one
of
the
other
things
I
realize
again
looking
at
diet
esp
and
I'm
doing
a
tunnel
inside
so
once
I
have
chic
as
iv
protocol
number
I
have
seek
and
and
the
secret
says
this
is
esp
here's
our
process,
header
and
in
the
esp.
G
The
next
header
is
chic
again
for
how
long
press
that
that
esp
payload
inside
of
there.
So
actually
I
end
up
then
using
sheet
twice
in
that
case,
and
it
just
flows
in
the
stack
and
we
don't
have
and
we
limit
how
much
special
stuff
we
have
to
do
so.
It's
a
way
in
my
opinion-
and
I
ask
that
this
be
adopted
by
the
work
of
this
idea,
and
I
don't
think
we
need
much
of
a
document
to
accomplish
it.
A
Effectively,
there
are
no,
there
are
two
people
in
the
queue
I
happen
to
be
first,
so,
if
you
don't
mind,
can
you
go
back
a
few
slides
when
you
talk
about
the
transport
and
and
the
discussion
about
fragmentation,
not
fragmentation,
but
fact?
Basically,
so
you
you
mentioned
that
you
presented
that
at
the
raw
working
group
and
effectively
that's
something
which
relates
to
to
the
potential
need
for
rechartering,
which
will
come
later.
A
What
we
don't
have
is
a
fak
variation
for
the
fragment
reliability
and,
as
you
know,
the
lp1
networks
are
usually
very
asymmetrical,
like
the
device
can
sound,
but
the
gateway
don't
have
much
bandwidth
back
so
having
to
send
the
axe
is
the
pain
and
it
could
be
envisioned
that
effectively
fake
for
chic
fragments
could
be
a
a
new
possibility
for
a
sheikh
right,
an
alternate
fragmentation
technique
which
seems
to
fit
exactly
what
the
kind
of
thing
that
you've
been
discussing.
So
please
consider
that
and
and
come
back
to
us.
A
You
know
if
you
want
some
work
to
to
start
here,
knowing
that
the
transport
guys
will
have
to
tell
you
how
you
do
the
the
the
coding
or
something
it
cannot
come
from
us,
but
maybe
the
fact
that
we
are
using
the
coding,
the
recommend
could
be
a
work
here
if
we
were
shouted
for
it.
G
I'm
a
little
bit
too
old
and
I
dealt
too
much
with
ipv4
ip
level.
Fragmentation
starts
with,
oh
my
god.
I'm
doing
this
and
here
comes
ipv6
breaks
my
packet
up
and
then
things
don't
working
and
eric
just
correct.
We
know
ipv6
does
not
fragment
and
we're
okay
there.
So
my
concern
was
not
what
would
we
do
inside
of
secret
fragmentation,
but
what
happened
below.
C
G
A
Yeah,
because
we
we
fragment
so
you
can,
we
can
take
your
packet
cut
it
into
call
that
two
fragment
and
then
sell
two
tiles
and
send
the
third
tile
as
being
the
fact
and
it's
all
within
our
global
design.
And
then,
if
you
have
raw
something
that
can
be
distributed
over
multiple
paths-
and
you
don't
even
have
to
know
about
that.
So
so
there's
a
way
to
build
something.
Really.
Nice.
G
A
E
E
G
And
it's
like:
what's
the
hope
for
this
and
so
forth,
and
and
and
they
said,
the
effects
should
be
in
transport,
but
I
just
quickly
during
the
lunch
I
reviewed
the
traffic
framework
and
that's
all
really
in
in
streaming
of
applications
and
not
what
I
wanted
to
do
it.
So
it's
interesting
work
that
can
be
applied,
but
what
I'm
trying
to
do
it
has
really
nothing
to
do
with
what
they
did.
So
I
can
leverage
off
what
they
did.
So
it's
looking
for.
No,
where
does
this
property
belong?
G
A
But
yes,
we'll
see
what
interior
says
and
then
again
you
might
think
that,
instead
of
producing
the
ipe
thing
in
here,
you
could
produce
an
ergonomic
fragmentation
which
is
effectively
within
quarter
for
us,
but
we,
we
could
maybe
extend.
I
don't
know,
maybe
to
change
a
little
bit
the
charter
for
different
things.
But
this
is
there
any
other
question,
any
kind
of
feeling
about
the
idea,
whether
it's
a
good
idea
about
idea
in
the
room.
G
A
A
A
G
A
Oh
no,
I
already
loaded
them
because
I
could
have
done
that
so
now.
You
need
to
hand
me
the.
A
Okay,
so
you
know
it
was
a
long
time
a
request,
pushing
us
to
to
update
the
chic
architecture
and
we
we
basically
were
like
hey
chicken
architecture,
kind
of
documents,
steps
that
the
the
working
group
is
taking
and
and
the
agreements
that
we
are
reaching
the
mailing
list.
A
A
Uplink
downlink
and
you
know,
from
from
uplink
from
the
device
to
the
app
basically
because
the
compression
depends
on
those
information
and
guess
what,
when
you're,
going
peer-to-peer
or
forwarding
on
a
more
symmetrical
network,
then
the
implicit
once
the
app
on
the
device
goes
away
and
we
have
to
define
that
and
the
other
thing
and
that's
one
thing
that
that
bob
has
to
think
about
was
my
comment
in
his
initial
discussion
for
the
ip
next
header.
A
A
But
if
you
talk
over
ip
I
mean
this
device
could
have
multiple
sessions
with
that
other
device
and
so
finding
which
check
instance.
You
know
this
packet
is
for
becomes
harder
and
we
need
to.
We
need
to
signal
it
some
way.
Now
we
realize
that
most
use
cases
that
we
have
the
sheik
instance
lives
on
a
connection
or
a
session
of
some
sort.
You
could
establish
a
tcp
session.
A
You
could
establish
a
udp
session
like
in
the
ppp
draft,
but
there
is
something
underneath
there
is
a
peer-to-peer
security
tunnel
and
there
is
something,
and
so
basically,
if
the
rule
is
when
you
open
a
communication
pipe
between
two
devices
and
well,
there
can
be
only
one
shake
instance
over
that
particular
type.
And
so
you
don't
have
to
modify
shake
to
signal
the
instance
it's
basically
because
it's
it's
derived
from
the
pipe
that
supports
that
particular
communication.
A
Once
we
have
this
instance,
we
can
say
hey
well,
if
it's
unclear
who
should
be
app
who
should
be
device,
then
the
device
is
the
one
that
started
the
connection.
For
instance,
if
it's
about
tcp,
then
the
device
that
send
the
tcp
scene
would
be
would
be
the
the
the
the
device,
and
you
know
the
synap-
comes
from
the
the
server.
So
our
playing
case
is
along
the
path
of
the
tcp
scene.
Basically,
just
to
give
you
an
example:
we
don't
have
shake
about
tcp
as
far
as
I
know,
but
it
could
it
could
happen.
A
A
There
are,
there
are
cases
like
bluetooth,
energy,
where
there
is
a
hub
and
spokes
and
so
for
those
ones
we
do
just
like
we
do
with
gateway
and
devices
I
mean
the
hub
is
cotton
called
the
gateway
and
the
spoke
is:
is
the
device
side
so
for
those
ones
it's
kind
of
easy,
but
for
really
peer-to-peer
like
I
over
ip
something
it?
We
have
to
have
a
session
of
some
sort,
a
connection
of
some
sort.
A
So
we
can
identify
the
instance
now
what's
next
well,
there
are
number
of
things
that
have
been
tried
outside
could
have
been
done
here
and
an
example
of
that
is
chicago.
We
have
fun
since
the
draft
for
chicago
ppp.
We
propose
to
the
interior
and
I
don't
want
to
to
send
bad
waves.
You
know
in
bob's
direction,
but
we
we
held
that
draft
for
a
number
of
iatfs
with
no
review,
no
commands
no
interest
from
interior,
and
so
the
only
way
to
progress.
A
That
document
is
probably
to
bring
it
back
to
sheikh,
but
we
are
not
chartered
for
221,
but
we
are
not
chartered
for
shikkov
fool
when
foo
is
not
one
of
the
technologies,
so
extending
to
new
technologies
could
be
one
thing
that
we
could
consider
as
a
recharger,
and
that
would
enable
us
to
effectively
discuss
scala's
case
with
15
4.
That
would
enable
to
discuss
ppp
and
any
other
type
of
link.
A
Now
there
was
that
the
the
chic
n,
the
next
letter
for
sheikh
that
bob
has
been
talking
about.
So
I
understand
that
eric
suggests
to
move
it
to
to
interior.
At
the
same
time,
today
bob
proposed
a
throw
nigeria
to
do
network
coding
between
fragments.
A
I
mean
that
idea
is
not
new
right,
but
doing
it
inside
chick
would
be
quite
nice
because
even
for
traditional
lp
ones,
I
mean
you
would
save
the
the
retries
that
we
have
for
the
for
the
fragments,
because
we
have
some
homophobia
in
the
reliable
fragments
that
we
could
make
fragments
not
fully
reliable
but
a
lot
more
reliable
by
doing
fake
the
way
bob
presented
it.
I
not
sure
this
requires
a
recharge
ring,
that's
something
we
can
check,
but
basically
this
kind
of
fighters
also
something
that
could
impact
our
charter.
A
So
what
I
wanted
to
do
today
is
not
really
propose
your
chart
of
text
or
what,
but
basically
figure.
If
you
know
the
usual
suspects
in
the
room
are
willing
to
to
look
at
more
things
which
we
could
do
in
these
groups,
which
are
not
the
current
charter
and
discuss
that
about
the
mailing
list
and
just
to
sense
interest.
I
will.
A
E
A
H
Yes,
so,
regarding
the
lp1
architecture,
draft
first
things
for
the
updates,
including
these
extended
scenarios
beyond
the
original
lp1
architecture.
I
hope
that
perhaps
in
future
updates,
the
mesh
topology
might
also
be
explicitly
mentioned
and
then
on
the
point
of
check
over
foo.
Perhaps
we
might
also
consider
chic
parts
over
full,
for
example,
at
the
moment
in
the
1504
draft
that
we
have
at
six
load,
what
we
are
using
is
only
the
header
compression
part
of
chic
and
we
are
sticking
to
fragmentation
based
on
six
lowpan
or
six
low
fragmentation.
A
A
If
you
want
to
afford
fragments,
then
all
the
iraq,
your
system
goes
away
because
you
don't
know
how
to
route
the
air
q
back
and
probably
you'd
better,
do
something
like
the
lp
one
which,
which
was
I'm
sorry,
the
sixth
open
fragmentation
which
was
redesigned
for
this
and
and
you
kind
of
hint
that
in
your
document
already
talking
about
the
the
the
buffer
that
we
use
in
the
intermediate
nodes,
etcetera.
So
basically
we're
talking
about
rfc,
8930s
8931.
A
So,
yes,
I
mean
all
this
can
be
discussed,
just
just
a
reminder
that
we
put
in
the
architecture
of
things
which
are
kind
of
agreed
inside
the
working
group,
things
which
are
stabilizing
now.
The
discussion
over
the
mesh
you've
just
started
it.
It's
very
important
and
very
interesting,
but
we
need
more
inter
meetings
to
agree
on
what
goes
you
know
cast
in
stone
in
the
architecture
and
so
there's
no
text,
because
we
just
started
that
discussion.
I
was
not
ready.
A
I
did
not
have
a
feel
that
I
could
write
something
that
we
agreed
about
because,
as
you
know,
there
is
the
outcase
and
the
easy
case
right.
The
easy
case
mean
when
you
have
repo
and
then
non-storing
model
and
ingress
replication.
That's
the
easy
case,
and
the
hard
case
is
going
over
multiple
harp
with
shake
without
expanding
the
packet
at
every
help.
That's
hard.
A
Okay,
do
we
have
any
other
discussion
on
either
the
architecture
of
rechartering?
We
have
we.
We
are
now
in
the
richard
trains
discussion
and
there's
no
slide
beyond
the
fact
that
you
know
the
new
things
that
we
could
discuss
in
the
architecture.
Really,
you
know
she
cover
mesh
or
even
talking
about
the
next
header.
All
this
is
is
uncharted
for
us,
so
we
cannot
really
go
too
deep
into
those
things
in
the
architecture.
A
A
So
thank
you
all
for
attending
this
meeting
and
we'll
be
restarting
interim
meetings
after
the
summer
break
so
somewhere
in
september.
I
guess.