►
From YouTube: IETF105-HOTRFC-20190721-1800
Description
HOTRFC meeting session at IETF105
2019/07/21 1800
https://datatracker.ietf.org/meeting/105/proceedings/
A
B
B
The
idea
of
this
session
is
to
have
a
series
of
introductory
talks
to
give
folks
who
are
doing
something
new
in
the
IETF,
a
way
to
get
the
word
out,
and
so
it's
especially
good
for
things
that
cross
areas
are
new
to
the
IETF,
maybe
coming
in
from
the
IRT
F
or
a
boss.
That
sort
of
thing
to
just
give
a
very
short
synopsis
with
some
coordinates
on
how
to
get
involved
or
learn
more.
B
So
if
you've
made
dinner
plans,
I
think
you'll
still
be
able
to
to
make
them,
but
the
way
that
we're
going
to
do
that
is
through
very
strict
time
limits,
so
we're
using
the
large
set
time
management
method,
and
so,
at
the
end
of
four
minutes,
if
the
speaker
hasn't
concluded,
you
should
hear
this
sound
at
which
point
I'd,
like
everybody,
in
the
room
to
start
clapping
and
thank
our
speaker
very
good
guys,
have
got
the
right
idea.
Now
all
that
comes
down
to
my
ability
to
push
the
button
correctly.
B
Let's
see
on
the
material
site,
you
should
find
all
the
slides
that
you're
gonna
see
tonight
as
well
as
abstracts.
That
summarize
the
talks
and
include
the
coordinates
for
finding
out
more
information.
So
there's
not
gonna
be
any
time
for
a
QA
yeah.
It's
really
intended
to
be
something.
That's
very
concise.
Give
you
the
flavor
of
something
new
move
on
to
the
next
thing.
I
hope
you
find
it
interesting
and
so
Brian.
If
you
would
come
up
our
first
speaker
and
I'll,
get
your
slides
up.
C
C
A
C
C
So
what
use
the
service
type
request
turned
on
IP
address
to
forward
packets
at
the
network
edge
we're
not
talking
about
the
core
of
the
network,
abstract
a
service
as
something
called
a
service
action
type,
which
is
a
small
integer
indicating
the
service
is
a
very
generic
idea
near
the
user.
The
packets
are
routed
by
the
service
action
type
and
not
by
the
address,
and,
of
course
before
you
ask
the
obvious
question
right
here:
each
one
of
the
available
services,
which
is
how
it
turns
out
to
work
backwards.
C
So
here
are
some
examples
of
service
action,
types,
reach
ability
on
ipv6
reach
ability
on
ipv4
discovery,
service,
computation
service,
a
storage
service
and
there's
a
list
of
others
in
the
draft
packets
are
and
the
format
derived
from
ipv6.
This
is
a
low-level
protocol,
but
there's
a
service
action
type
instead
of
a
destination
address,
because
users
don't
care
about
destination
addresses,
and
there
are
other
goodies
that
look
like
a
lair
violation,
because
actually
this
thing
is
intentionally
a
lair
violation.
This
entire
code
is
probably
not
worth
looking
at
more
important.
C
C
Why
are
we
talking
about
this
in
edge
deployments
of
IOT,
in
particular
the
physical
MTU
and
the
bitrate
Oh?
In
some
cases,
extremely
low?
That's
well
known
so
packet
size
matters
a
lot
he
edge
routers
the
edge
routers
may
be
constrained
themselves.
That
has
an
other
implications.
Besides
the
problem
of
bandwidth
and
period,
header,
decompression
and
header
compression
had
a
decompression
use
resources
128
bit
addresses
used
memory
so
for
a
certain
class
advertised
there
is
a
strong
case
for
both
reducing
packet
size
and
reducing
the
head
of
decompression
and
compression
overhead.
C
What
why
are
you
doing
by
using
shorter
addresses
murti
on
the
shorter
addresses,
not
transmitting
unnecessary
bytes
and
avoiding
any
fancy
compression
decompression
algorithms
at
the
level
of
processing
the
IP
header,
how
you
define
an
address
length
n
within
a
domain
wall,
addresses
within
the
domain
or
assumed
prefix
in
front
of
that
of
128
n
bits
and
there's
lots
of
bit
bytes
and
the
headers
that
you
can
get
rid
of.
If
you
think
about
it,
and
we
use
a
flexible
header,
encoding
octet
to
tell
the
lowest
layer
of
software
how
the
header
has
been
encoded.
B
E
So,
what's
a
main
target
problem:
first,
the
traffic
in
real
networks,
especially
metro
network,
is
always
heavily
unbalanced.
Although
we
have
ecmp
or
using
built
such
kind
of
technologies,
surely
they
don't
really
work
very
well
and
second,
the
traffic
is
always
changing
so
fast
and
traditional
traffic
engineering
technology
cannot
adapt
the
traffic
in
real-time.
So,
with
the
ICANN
technology,
we
can
provide
guaranteed,
never
load-balanced
in
real-time
millisecond
level
and
as
well
as
SLA
assurance
and
high
availability.
E
F
Hi
so
Adam
and
Bob
and
I
are
working
with
various
international
standard
setting
bodies
and
government
agencies
on
a
really
critical
problem.
Go
next
slide
about
yeah.
So
it's
just
this.
A
small
unmanned
air
vehicle
can
very
rapidly
get
close
to
a
crowd
or
a
piece
of
critical
infrastructure
without
being
observed
on
route
and
some
public
safety
person
armed
with
only
something
that
he's
likely
to
be
carrying
needs
to
be
able
to
quickly
identify
that
thing.
Is
it
a
friend?
Is
it
a
fall?
Can
we
look
up
its
flight
plan?
F
Maybe
can
we
establish
communications
with
its
operator
and
know
for
sure
that
it's
the
operator
of
that
aircraft
that
we're
talking
with
this
problem
of
mapping
a
physical
location
to
a
trustworthy
identity
seems
to
me
related
to
the
identifier
locator
split
in
the
internet
and
where
we're
trying
to
go
between
a
logical
location
and
an
identity,
and
so
we're
looking
at
the
use
of
hip
to
do
this
and
I'm
gonna?
Let
a
hip
expert.
Take
the
rest
of
the
time.
G
Speaking
with
us
to
an
atom,
we've
worked
out
value
of
hits
as
the
remote
ID
for
you
ace.
It
provides
a
trustworthy
identity
to
pair
with
physical
and
logical
location.
Data,
as
you
know,
hits
our
value.
Ipv6
addresses
can
be
used
directly
over
the
broadcast
of
broadcast
media.
If
that's
what
you're
transmitting
like
Bluetooth
Bluetooth,
the
five
is
one
of
the
thighs
for
this
with
prove
ownership
using
the
high
for
the
signature
for
mobility
and
multihoming,
so
in
case
you're
using
multiple
files
on
this
particular
you
a
would
supported.
G
You
can
use
the
hip
face
IPSec
for
secure
communication.
If
that's
what
you
desire
need-
and
we
can
come
up
to
a
secure
registration
of
the
full
identity.
Bootstrap
on
a
first
come
first
owned
for
the
ID.
That's
what's
available
there,
but
it's
not
exactly
what's
needed
for
this
case.
There's
some
work
needs
to
be
done.
The
original
design
of
hip
talked
about.
Hierarchal
hits
I've
done
a
draft
on
this
since
then,
and
because
of
ownership
and
other
registry
issues,
hierarchal
hits
will
definitely
be
a
value
for
this.
G
We
need
to
have
an
expanded
registration
process
of.
What's
in
the
current
on
documents
in
terms
of
a
federated
registrated
registration
authorities
to
tying
the
various
metadata,
the
actual
physical
location
and
ownership
and
other
information
about
the
device,
some
of
the
new
crypto
support,
which
is
out
there
taking
advantage
of
seaboard
where
we're
appropriate
and
since
they
keep
on
in
the
work
talking?
Oh
look
at
hip
as
a
whole
off
method.
That's
we've
seen
so
far.
G
B
H
Hello
Sharon
from
mixer
I
wanna
talk
Sharon
from
mixer
I
want
to
talk
to
you
about
a
cool
problem
and
RFC
draft
that
solves
it.
It
has
to
do
with
the
sharing
of
physical
information
of
a
on
the
road
between
cars
and
it
makes
use
of
grid
of
the
earth
actually
gonna
go
grid
of
the
earth
called
h3
and
an
overlay
network
which
can
make
those
tiles
of
the
earth
addressable
cordless.
H
So
just
as
a
background
on
the
problem,
we
distribute
hundreds
or
thousands
of
cameras
each
week
to
drivers
for
them
to
drive
around
they're
paired
with
their
phones.
They
do
it
because
of
insurance
in
motivations
and
the
insurers
want
them
to
do
that.
But,
as
a
result,
we
actually
have
tens
of
thousands
of
eyes
crawling
the
physical
space
and
the
public
domain
in
every
major
US
city
and
because
of
the
peering
to
the
phone.
It's
not
just
cameras,
they
actually
understand
what
they
see
with
the
eye
and
they
are
connected
using
a
network.
H
H
H
This
addressing
scheme
allows
me
to
share
information
between,
let's,
say:
mobility:
car
going
here:
mobility
car
going
there,
this
cars
is
this
guy
cars
future
and
vice
versa.
They
can
publish
and
subscribe
to
it.
In
tests.
We
were
able
to
communicate
a
red
light
bridge,
another
four
milliseconds,
a
bit
of
a
lab
conditions
between
a
camera
on
the
junctions
and
all
the
cars
approaching
and
affected
by
it.
So
if
you're
interested,
it's
discussed
in
the
list
working
group
tomorrow
and
happy
to
have
more
participants.
I
The
motivation
for
this
work
is
for
data
center
that
they're
hiding
speeds
that
are
making
network
transfer
complete
faster
in
fewer
out.
It
is
short.
Data
burst,
require
low
latency,
while
longer
data
transfer
requires
high
throughput.
So
these
are
two
requirement
there.
The
our
DNA
is
the
common
protocol
in
data
center
network.
However,
the
congestion
control
is
not
optimized
for
different
user
generated
interoperability.
I
Allowing
for
flexibility
running
an
optimized
congestion
method
in
the
network
interface
card
in
having
fast
congestion
notification
to
the
sender
can
improve
the
our
DMA
data
trend.
Transfer.
It's
common
in
a
deficit
of
Network.
The
TCP
traffic
is
mixed
with
the
our
DMA
traffic
and
the
causes
conflicts
between
priorities
between
them
and
what
we're
saying?
Is
there
a
better
method
that
could
solve
the
problems
mentioned
above
while
addressing
interoperability
so
that
our
DMA
traffic
can
be
treated
it
more
efficiently?
I
So
we
have
two
documents
on
the
open
control,
architectures
the
requirement
document
and
the
architectural
document.
There
is
why
not
discuss
the
problems
of
the
country,
mode,
direct
memory,
access
fabric,
congestion
handling
technology
and
the
requirement
for
better
performance
and
the
architecture
propose
an
open
control
architecture
of
host
networks
for
the
high-performance
RDMA
fabric,
to
provide
better
congestion
and
the
league
for
HPC
and
distributed
storage
application.
I
The
architecture
itself
is
seen
in
this
slide.
There
are
there's
the
sender.
The
reaction
point
in
the
receiver
is
the
notification
point,
but
the
switch
can
serve
bosses.
The
congestion
point,
but
also
is
the
congestion
point,
but
also
can
provide
notification.
So
there's
can
be
a
net
to
me,
control
Channel
and,
of
course
they
make
to
me
control
channel.
I
That
will
provide
the
information
to
allow
the
sender
to
response
better
and
faster,
so
the
design
configuration
is
provide
better
information
about
the
congestion,
stay,
stay
to
the
sender
faster
and
more
accurate
from
the
network
and
notify
the
sender
the
reaction
point
from
their
network
support.
It
can
support
proactive
response
from
the
notification
point
and
support
our
DMA
transport
different
to
our
DJ
transport.
So
this,
what
we
are
talking
about
is
something
that
would
be
transport
agnostic
and
support
multiplex,
the
traffic
of
our
DNA
in
TCP.
I
J
Am
Condon
and
if
we
had
coordinated
better
I,
probably
would
have
gone
just
before
Ronnie,
because
this
is
very
similar
topic,
but
I'm
kind
of
approaching
it
from
a
little
bit
of
a
more
higher
level,
not
a
specific
solution.
Ronnie
has
some
some
drafts
that
that
describe
that
solution.
Someone
talked
about
strat
strategies
to
dramatically
improve
congestion,
control
and
high
performance
data
centers.
So,
first
of
all,
data
center
congestion
is
different
than
the
internet.
Congestion.
J
I
think
we
all
know
that
a
few
handful
of
transactions
can
cause
a
lot
coming
in
from
the
web
can
cause
a
lot
of
activity
inside
a
data
center,
so
data
centers
have
much
different
environment.
There's
different
bandwidth
delay.
The
switches
are
implemented,
different
and
small
buffers
high-speed
links.
You
know,
then
different,
Internet,
routers,
there's
a
lot
more
homogeneity
in
the
network
design.
It's
not
so
random.
The
traffic
is
very
concentrated.
Servers
and
storage
are
all
in
close
proximity
and
there's
a
lot
of
different.
J
The
traffic
profiles
are
kind
of
well
known,
highly
coordinated,
correlated
and
typically
they're
managed
with
a
lot
fewer
people
under
a
single
management
domain.
So
all
this
means
that
these
data
center
congestion,
the
environment
in
which
it
runs,
is
much
different
than
the
internet,
and
we
know
we
do
internet
standards
here,
but
but
we
also
do
have
focused
on
data
center
standards,
DC
TCP
as
an
example,
so
the
data
center
needs
low,
latency,
low
overhead,
high
efficiency
and
high
throughput.
J
So
one
thing
the
data
center
kind
of
has
in
common
with
the
Internet,
is
there's
this
trend
to
do
more
over
UDP,
something
like
we've,
seen
a
lot
of
activity
with
quic,
for
example.
So
what
if
we
you
know
could
do
something
that
that
was
more
sort
of
quick
like,
but
not
quick.
You
know
as
heavy,
perhaps
for
specific
for
the
data
center,
and
maybe
we
did
something
that
was
Datagram
congestion
control
like
but
again
focused
on
the
congestion
problems
of
the
Internet
of
the
data
center.
J
It
would
need
to
be
Hardware
off
loadable,
but
maybe
with
less
emphasis
on
security
and
crypto
and
all
the
threading
kind
of
stuff
that
things
have.
It
would
need
to
be
really
common
congestion
control,
as
described
in
the
previous
talk,
and
ideally
we
need
to
have
the
network,
visibility,
marking
and
signaling
abilities
from
the
network
itself.
So
the
ITF
has
this
expertise.
So,
let's
leverage
and
not
leave
it
to
the
UDP
application
riders.
Let's
see
if
we
can
do
something
we
know
datacenter
congestion,
is
different.
J
The
authors
of
these
papers
have
done
a
lot
of
work
on
congestion,
trees,
so
there's
kind
of
two
types
you
know
in
network
and
in
congestion,
and
it's
constantly
moving
moving
around
in
cast
or
in
network
we've
got
solutions
today,
such
as
ecmp
ecn,
even
even
in
a
lossless
environment,
ecn
with
priority
flow
control.
All
of
these
have
various
pros
and
cons,
but
they're
not
completely
addressing
the
the
needs
that
we
see
so
some
ideas
of
augmenting
ecn,
with
with
a
data
center
focus
for
a
UDP
layer.
J
You
know
adding
more
feedback
from
the
switches
in
the
packet
headers.
Perhaps
you
know
marking
delay
inside
packets
so
that
we
can
get
really
fine
grain
view
of
what's
going
on
being
able
to
figure
out
is
this
congestion?
We're
experiencing
right
now?
Is
it
in
network
or
is
it
in
caste?
You
know,
because
maybe
we
would
take
different
approaches
being
able
to
speed
up
notifications
to
the
source,
so
they
can
quench.
You
know
in
a
way
that
addresses
it
and
then
implementing
fast
mechanisms
in
the
switch
to
respond
immediately.
J
So
so
what
like
to
do
is
discuss
the
technical
approach
and
feasibility
of
these
ideas
in
a
side
meeting.
So
we
have
a
side
meeting
tomorrow,
Notre
Dame,
it's
the
same
one
that
was
announced
and
we're
also
providing
remote
participation
for
that,
and
then
we're
going
to
be
requesting
a
ETF
mailing
list
as
well,
so
I
think
I
made
it.
We
also
have
a
whole
bunch
of
references
in
this
deck.
If
you
want
to
read
them.
A
K
High
I
will
presume
to
walk
showing
but
sure
we
can
leverage
an
existing
networking
agents
to
build
service
from
John
Chang
in
most
of
her
existing
deployment
service.
Functional
trains
are
controlled
by
a
central
control
point
which
computable
ideal
placement
of
virtual
functions
such
as
IDs
firewall
and
prepare
for
M
raising
some
program,
since
it
creates
failure
and
the
network
scalability
issues
it's
oddly,
interoperable
with
resistant
networks
and
it
under
exploit
existing
protocols
or
network,
for
instance,
service
function.
K
Training
program
is
mainly
a
routing
program
because
you
have
to
route
traffic
for
a
set
of
white
bone
between
two
before
which
medicine
ation.
So
what
her
purpose
is
to
augment
her
entire
entire
gateway
protocol
and
make
a
function
aware.
You
know
in
order
to
build
solution
path,
I
will
quickly
remind
how
integral
from
functions
you
have
a
gateway
which
are
connecting
networks,
shank
combination
and
building
a
network
view
and
based
on
what
it
a
to
compute.
K
L
L
So
IDF
is
quite
a
unique.
We
have
many
contribution
from
universities
and
we
even
have
research.
Am
I
TF,
but
in
my
personal
views,
there's
a
skill
and
gap
in
our
networking
area
as
a
whole,
so
our
innovation
and
the
design
highly
rely
on
experience.
I,
don't
find
a
well-defined
body
of
knowledge
or
a
set
of
approaches
that
can
help
us
to
make
design
choice
and
understand
the
trade-off
behind
those
decisions.
So
I'm,
not
the
only
one
have
this
feeling.
L
So
these
are
very
interesting
paper
from
Jennifer
Luck's,
folder,
Princeton,
Princeton,
University,
he/she
coated
the
some
doubts
from
people
inside
and
outside
networking
community.
So
is
networking
a
set
of
protocol
acronyms
or
a
keep
of
head
formats,
or
we
are
just
a
big,
a
bunch
of
boxes.
Of
course
Jennifer
defeated
as
though
all
these
questions
elegantly,
but
at
the
end
of
the
paper
she
also
suggested
that
we
can
make
the
question
we
ask
more
precise
and
the
way
we
answer
them
more
rigorous
and
the
week.
L
Maybe
we
can
not
so
much
value
new
problems
over
deep
answers
to
existing
questions.
We
need
to
encourage
more
seller
and
the
complete
and
the
deeper
research.
So
why
IDF?
So
in
one
way,
this
theory
can
help
IDF
to
explain
and
predict
the
outcomes
from
new
design
and
facing
your
problems,
and
also
it
can
help
us
for
can
help
new
generation
to
inherit
and
make
their
own
contributions
so
on
the
other
way
why
IDF
or
can
can
help.
So
we
have
both
rich
and
very
successful
experience
and
expertise.
L
In
theory,
we
have
so
many
academic
participants,
so
why
now
now
we
are
facing
some
new
requirements
such
as
deterministic
and
bounded
Adelaide
services.
So
we
may
require
more
theoretical
analysis
than
before,
so
is
that
the
other
is
imposing
IP
is
proposed
to
apply
Network
calculus,
a
kind
of
queuing
Theory
to
the
time
sensitive
networking
problem.
L
So
there
are
several
useful
reference.
Of
course,
this
in
one
way,
is
in
one
handiest
and
mathematical
foundations
and
tours
and
on
the
other.
Yes,
the
theory
of
the
Adhan
hope
the
seamen
proposed
a
framework
long
time
ago.
I
don't
think
I
have
time
to
adjust
the
details,
but
if
you
are
interested
contact,
us
me
and
my
friend
can
learn
from
China
Mobile.
Thank
you.
M
Okay,
this
is
about
software
management.
If
you
don't
use
these
standards,
which
is
really
the
entire
software
industry
outside
networking.
So
you
you,
you
know
every
every
company
starts
the
same
way.
You
write
a
little
service.
We
start
including
more
services
to
do
your
function,
and
then
you
learn
about
micro
services.
It
becomes
this
and
of
course
you
get
this
and
of
course
you
need
a
management
plan
to
to
make
sense
of
it.
It's
all
so
for
each
one
of
those
little
boxes.
M
M
You
find
performance
metrics
any
which
way
you
can
and
if
it
has
a
security
model,
you
got
to
somehow
integrate
with
that,
so
every
single
service
you
have
to
do
this
with
and
if
it
looks
like
a
lot
of
work,
it
is
a
lot
of
work,
but
a
lot
of
companies
are
cheating
because
they're
finding
recipes
on
the
Internet
to
help
them
get
a
jump
start
or
they're
only
mapping
the
pieces
that
they
they
think
they
need
before
they
go
into
deployment,
and
this
is
a
problem
because
they
find
out
after
deployment.
M
They
forgot
something
so
clearly.
This
is
a
lot
of
work
and
the
standards
for
yang
Andres
conf
solve
this
entirely,
but
the
industry
as
a
whole
and
to
give
you
an
idea,
the
scope
of
this
problem,
puppet
labs.
They
estimate
there
are
now
more
people
in
the
management
plane
than
there
are
in
the
data
plane.
So
more
people
writing
software
about
software
than
the
software
itself
solving
problems.
M
So
this
is
a
very
large
problem
and
so
in
2015
I
became
aware
of
these
standards
and
wrote
a
implementation
of
the
the
yang
and
the
rest
comp
specs
in
go.
I
started
there,
so
I
wrote
a
little.
My
first
project
was
this
bartender
and
it
has
a
Raspberry
Pi
and
some
relays
and
some
pumps-
and
it's
got
a
little
interface
to
make.
M
Oh
the
animation
work
so
but
I
didn't
put
it
all
in
restaurants,
so
there's
a
yang
model
for
the
bartender
and
you
can
assign
a
pump
to
a
particular
liquid
and
even
when
you
make
your
recipe
you're
going
through
a
rest
conf
and
it
was
really
no
special
tools
on
the
JavaScript
to
get
this
to
work.
Rest
comp
really
is
designed
really
well
to
make
it
palatable
to
the
industry
as
a
whole,
which
is
what
his
design
was
so
and
I
really
like
how
rest
comp
has
different
modules.
M
So
if
you
know
amazon
published
a
yang
for
alexa
skill,
I
could
add
that
in
and
all
of
a
sudden,
you're
saying
Alexa
make
me
a
mai
tai.
So
since
then,
I've
used
this
in
lots
of
different
industries.
Iot
schools,
malware
detection,
the
standards
work
really
really
well,
but
of
course,
that's
only
so
good.
M
So
when
we've
arrived
is
when
I
can
tell
say,
Pedro
duty,
which
is
a
system
for
alerting
you
to
say,
hey
postgrads
when
there's
a
slow
query,
paged
me
about
it
and
I
didn't
have
to
involve
DevOps
I
didn't
have
to
program
anything,
and
this
is
all
possible
with
the
standards,
but
none
of
these
tools
know
about
these
standards
or
implementing
them.
So
I'm
really
here
to
talk
about
this.
M
This
problem
in
industry
as
a
whole,
see
if
this
problem
resonates
with
anybody,
I
realized,
I
tip,
is
concerned
about
networking,
but
there's
definitely
a
bigger
hole
and
I
estimate.
This
is
there.
There
are
actually
10
million
developers.
This
could
actually
help
them
out
so
and
I'm
one
of
those,
because
without
these
standards
I
find
using
these
standards
in
outside
networking.
It
really
doesn't
doesn't
really
solve
the
bigger
problem.
N
Hi
everyone
I'm
here
to
talk
about
like
aetherium,
improvement
proposals
and
there's
no
time
for
introduction
for
just
in
jumping.
So,
as
you
may
know,
or
may
not,
a
theorem
is
the
second
largest
cryptocurrency
just
based
on
the
market
cap.
There
is
a
possibly
the
number
of
developers
and
tools
that
are
based
on
that
all
right.
The
first
and
hold
blockchain
DLTS
theorem
is
a
home
for
en
su
sitio
naming
services
they
trying
to
do
that
Etha
TLD
and
also
do
DNS
SEC
in
the
blockchain,
also
for
IP,
FS
or
essential
file
system
applications.
N
There
are
a
lot
of
more
apps
there,
so
I'm,
mostly
document
looking
processes
here
so
etherium
is
one
of
the
healthiest
essential
dev
cycles
within
amongst
the
blockchain
and
cryptocurrency
projects.
We
see
it
far
from
the
perfect
from
perfect
some
of
the
circle
and
challenges
that
essential
decentralization
requires
a
non-hierarchical
in
the
Adamas
cycle
and
it's
really
hard.
N
So
they
have
this
e
IP,
which
is
in
theorem
improvement
proposals
which
was
inspired
by
bitcoin,
improve
a
proposal,
and
that
was
inspired
by
pet
Python
enhancement
proposals
which
that
also
was
enjoyed
by
IETF
request
for
comment,
and
there
are
some
aspects
that
we
dropped
on
this
path.
We
don't
know
where
exactly
but
like
security
consideration
section
on
the
IP,
it's
not
there,
I'm
really
trying
to
put
add
it
back
and
it's
gonna
be
added
in
the
next
month.
Probably
so
there
is
some
other
process.
N
This
is
like
the
process
today,
I'm
gonna
go
quickly
on
on
these,
and
the
slides
are
there
for
more
details.
So
after
discussing
in
the
forums
and
getting
community
support,
the
EIP
author
would
add
the
CIP
there.
So
security
concession
is
missing
there,
we're
trying
to
add
it
there
and
then
goes
to
a
selected
track.
So
the
track,
the
core
track
is
actually
the
consensus
protocol
and
the
protocol.
It's
a
really
critical
one.
It
has
resulted
in
Forks
in
the
network
and
another
controversy.
There
are
some
others
that
look
ERC.
N
N
So
when
it
gets
a
community
support,
it
gets
the
work-in-progress
draft
and
basically
they
write
these
usually
major
major.
And
if
it's
a
quarry,
I
peonies
implementation,
the
miss
you
thought,
I
didn't
talks
about
the
proof
of
concept.
After
that
it
does
in
the
IP
number
and
goes
to
a
draft
mode.
Here.
The
EAP
author
would
discuss
and
further
make
sure
the
draft
to
have
any
way
that
actually
makes
sense,
and
it
has
some
more
support.
And
after
that
it
goes
to
last
call
this
process.
N
If
there
are,
there
are
any
security
implementations
and
that
needed
to
be
checked
your
menu
and
test
tests,
and
it's
more
on
a
non-official
one,
and
after
that,
if
it's
a
courier,
pikas
accepted
and
all
the
clients
at
least
three
of
the
clients
there,
like
four
or
five
ATM,
clients
need
to
implement
that
to
get
that
actually
in
a
final
state,
if
it's
not
core,
then
it
sometimes
is
standard.
It
just
goes
to
the
public
to
find
out
state.
N
So
this
is
overall
what
I
just
talked
about-
and
this
is
the
first
attempt,
as
far
as
we
know,
to
visualize
this
and
have
something
to
show
that
this
is
the
process
usually
and
still,
even
with
this
process,
it
happens
on
github
proposals,
PR
full
request,
everything
happens
there.
There's
this
form,
if
they're
your
magicians,
that
people
discuss
there
and
your
magicians
there
for
the
EIP
magician
and
also
this
is
the
call.
This
is
like
a
chord
f
call
that
actually
the
decisions
happened
there.
N
So
why
am
I
talking
about
this,
so
I've
been
involved
in
also
write
a
process?
We
need
that
our
ITF
people
to
find
the
gaps
and
missing
pieces
in
this
and
in
this
process,
and
we
find
modules
I'm
open
to
any
discussions
and
comments.
And
this
is
how
you
can
reach
me
and
I
would
be
happy
to
talk
about
anything.
But
watching.
O
Hello,
everyone,
my
name,
is
Jim
I'm
from
Poway
I'm
here
to
discuss.
What's
the
next
step
of
young
in
I
have
actually
a
little
bit
of
background
from
me.
I
used
to
share
so
SM
usm
in
office
area
who
deliver
young,
be
the
model
for
era
VP
in
and
actually
we
witnessed
a
young
take
off
and
a
phalaris
ship,
but
we
still
feel
there's
some
problem.
O
So
that's
why
I
bring
these
topical
here
and
so
young
day
tomorrow,
I'll
get
a
lot
of
traction
actually
operator
began
to
plan
to
employ
a
young
bear
model
and
but
the
the
reason
for
that
actually
young
actually
not
only
happy
to
automate
as
a
networker,
but
also
allow
operator
to
peel
the
more
agile
service.
Young
actually
can
model
the
service
from
the
top
and
also
allow
you
to
model
the
collaboration
operation
of
the
device.
Allow
you
to
configure
the
protocol
on
the
device
get
a
net
with
set
hopper,
so
usually
the
younger
model.
O
O
You
know
we
can
reference
the
integrity
vendor
in
the
operated
test
report
we
can
see.
Actually
Medical
has
widely
adopted
it,
but
for
younger
the
model
still
and
early
into
a
adoption
stage.
So
what's
the
reason
behind,
so
we
see
actually
because
many
operate.
Actually,
you
know
not
engaging
idea
for
this
young
data
model
development
actually
for
some
operator
who
already
deployed
these.
O
Can
technology
may
not
aware
I
developed
this
young
teen
model
even
for
the
operator
who
actually
know
what
I
am
doing,
but
they
don't
know
how
how
this
llamada
put
together
to
deliver
a
service
to
fulfill
the
service?
Actually,
so
there's
a
critical
cat.
Actually
they
were
leader.
The
idea
of
young
beta
model
actually
like
a
sufficient
input
from
the
operator,
so
to
actually
is
actually
one
of
the
approach
a
way
proposed.
O
Actually
we
can
define
young
they
the
model
framework
actually
to
have
operator
to
how
to
indicate
a
younger
model
in
the
same
namespace,
and
so
we
have
a
chapter
actually
posted
in
OBS
authority
that
will
be
discussed
in
okay,
say
session
on
one
Wednesday
and
try
this
chapter.
Actually,
we
work,
together
with
operators
I
try
to
fill
this
gap
to
help
right
operator
to
provide
such
guideline.
How
to
you
know,
figure
out
how
even
a
layer
model
can
put
together
and
in
addition,
we
we
think
you
know
standard
work
is
not
enough.
D
Okay,
I'm
full
hon
Baker,
and
this
is
the
mathematical
mesh.
Oh,
so
internet
security
is
broken.
It's
broken
because
users
are
finding
security,
it's
just
too
much
effort
and
you
can't
solve
that
by
asking
them
to
try
harder.
It's
broken
because
applications
are
not
solving
the
real
problem.
I
mean
like
looking
at
all
the
data
breaches
the
data
at
rest
breaches.
D
D
So
you
can
glue
all
your
devices
together,
so
they're
worn,
gestalt
contact
management,
so
you
can
connect
all
the
people
that
you
connect
to
together
and
have
access
to
all
their
public
keys
on
all
your
devices
and
a
secure
control,
plane
messaging,
which
is
end-to-end,
secure
and
traffic
analysis
resistant,
Oh
wrong.
So
it's
based
on
the
principle
of
I'm
using
more
advanced
cryptography
than
in
Bruce
Schneier
book.
One
key
cryptography
is
great
des.
D
You
know
you
can
do
a
lot
with
this,
but
two
key
is
better
because
you
can
separate
out
the
roles
of
encryption
and
decryption
if
one
is
good
and
two
is
better,
why
don't
we
try
three
four
five
separate
the
roles
out
more
and
we
can
do
more
cryptography
and
more
cryptography
means
more
security.
Yes,
there's
a
bunch
of
small,
powerful
concepts
here.
D
I
can't
go
through
these
at
all,
but
basically
there's
five
basic
technologies
here
and
it's
a
grab-bag
and
they're
all
designed
to
work
together,
but
you
can
also
use
them
a
la
carte
in
your
projects
going
to
be
talking
about
this
at
sex
dispatched
tomorrow
at
1:30-
and
this
is
the
wrong
set
of
slides.
It
seems
a
she
sent
in
I'm
about
to
start
releasing
this.
So
if
you've
got
strong
opinions
on
it,
please
talk
to
me
before
I
release
it,
because
the
minute
I
have
users
I'm
going
to
start
protecting
legacy
encode.
D
If
you
want
to
change
anything
tilt
before
I
release
the
code,
there's
a
whole
bunch
of
drafts
and
the
drafts
are
based
on
running
code
that
comes
from
the
reference
library,
it's
all
in
MIT
license
or
C
sharp
or
that
good,
sir,
and
the
objective
here
is
to
provide
people
with
kind
of
like
a
psychic
learn
for
cryptography.
If
you
look
at
the
advanced
in
AI,
that's
happened
over
the
past
ten
years.
That
happened
after
the
AI
people
made.
It
really
easy
for
people
to
add
AI
into
application
with
things
like
pandas
and
scikit-learn.
D
So
the
reference
codes
and
attempt
to
do
that's
the
same
thing
for
cryptography
and
you've
got
all
the
same
goodness
of
blockchain,
pkcs7,
PGP,
x.509
and
so
on,
but
in
a
much
smaller
library,
because
if
you
make
all
the
systems
use
a
same
unified
approach,
you
can
get
rid
of
a
lot
of
code.
I've
got
rid
of
two-thirds
of
the
code
over
the
past
two
years,
so
meetup.
So
we
will
talk
about
sex
dispatch
tomorrow
at
1:30.
Please
be
there
or
talk
to
me
afterwards.
Thank
you.
B
P
I'm
either
Luba
chef
and
I
really
want
to
talk
to
you
about
law,
packet,
loss,
detection
in
encrypted
protocols,
I'm.
Looking
at
quick,
alright
I'm,
a
transport
guy,
I
love
to
think
of
my
networks
as
just
dump
pipes,
but
really
for
them
to
be
a
dump
pipes.
There
could
be
somebody
inside
that
pipe
who
is
looking
for
leaks
and
can
find
and
page
them
quickly.
P
If
it's
senior
TCP
flow
in
the
pipe.
It's
pretty
good.
She
can
look
at
sequence,
numbers
at
numbers
figure
out
if
there
is
leak,
see
it
if
it's
upstream
downstream.
If
she
is
looking
at
a
quick,
slow,
not
as
good,
there
is
no
really
no
bids
to
look
at
to
see
if
the
respect
at
loss.
So
it's
a
I
think
it's
a
problem
and
there
is
a
propose.
A
solution
that
uses
two
bit
1
bit
is
a
cube.
It
stands
for
square
signal.
It's
very
simple
sand!
That's
an
essence!
P
64
when
you
send
in
packet,
64
of
them
come
zero,
cubed,
64,
one
64
0
so
forth.
The
other
packet,
the
other
surahs
are
bit
is
an
else
for
loss
event
a
bit
and
it
is
set
when
there's
a
special,
unreported
loss
counter,
which
is
greater
than
zero
and
unreported
loss.
Counter
is
maintained
by
the
sender
when
there
is
a
packet
that
the
sender
sent
and
the
Penn
center
deems
it
lost
it
increments.
The
counter
when
the
packet
with
l1
is
sent,
the
counter
is
decremented.
P
So
if
you
can
see
the
picture,
there
are
two
packets
in
red,
they've
been
lost
about
one
or
TT
to
one
or
two
or
later
sender,
determined,
they've
been
lost
and
it
sent
two
packets
with
l1.
Okay.
How
can
we
use
that?
How
is
it
useful?
So
end-to-end
loss
is
pretty
simple.
It's
just
a
fraction
of
packets
with
l
equals
one
bits
that
absorber
observed
upstream
loss
is
basically
how
many
bits
with
a
particular
Q
value
are
missing
from
a
block.
P
Please
see
us
will
be
a
here
Monday
tomorrow,
8:30
to
9:30
for
a
side
meeting
and
we'll
talk
about
it
in
TS
vwg
on
Thursday,
that's
going
to
be
focused
on
protocol
details
as
well
as
privacy
and
ossification
risk
and
then
on
Friday
onmyoji
will
actually
present
lots
and
lots
of
data
and
talk
about
it.
And,
of
course
you
can
talk
to
us.
Thanks.
Q
R
R
R
R
R
S
Hello,
everyone,
my
name
is
Stuart
Cheshire
and
some
of
you
may
know
I'm
the
creator
of
zero
configuration,
networking
and
dinner
service
discovery
and
what
Apple
calls
Bonjour
I'm
sure
everybody
knows
it's
used
widely
and
Apple
products.
What
a
lot
of
people
don't
realize
is
it's
now
in
most
Linux
distributions,
it's
used
by
chromecast
it's
on
Android
and
it's
starting
Windows
10,
it's
even
in
Microsoft
Windows.
S
Anywhere
in
your
software
that
you
have
somewhere
for
a
user
to
type
in
an
IP
address
or
a
host
name,
you
can
use
DNS
service
discovery
to
give
them
a
list
of
options
to
choose
from.
Instead,
if
you
have
iPhones
here,
you
can
tap
on
AirPrint
and
you
pick
the
printer.
You
want
there's
no,
where
to
type
an
IP
address.
If
the
thing
you
want
doesn't
show
up,
you
fix
that
by
fixing
the
network,
not
by
typing
in
IP,
addresses
on
the
client
devices.
Traditionally
this
is
used.
S
Peer-To-Peer
multicast,
what's
great
about
that
is
it
requires
no
infrastructure.
You
just
hook
up
two
laptops
with
an
Ethernet
cable,
no
switch.
They
can
discover
each
other
two
phones
using
peer-to-peer
Wi-Fi,
no
access
points.
They
can
discover
each
other
services,
that's
great
for
small
networks,
but
it's
inefficient
on
large
networks
because
it
impacts
every
device
on
the
network,
even
the
ones
you're
not
talking
to
you
right
now.
It's
slow
on
Wi-Fi,
because
multicast
is
sent
to
low
rate
and
multicast
SAR
batched
with
the
beacon.
S
S
So
we
want
to
discover
things
that
are
multiple
hops
away
without
flooding
the
multicast.
And
if
you
do
this
with
your
iPhone
today,
you
send
a
multicast
but
the
printers
not
nearby.
We
solve
that
by
adding
a
Discovery
proxy.
Your
device
now
makes
a
TCP
connection
by
sending
IP
packets
multiple
hops
through
that
network.
The
discovery
proxy
can
then
do
the
multicast
on
your
behalf
and
send
the
answer
back.
You
discover
the
printer.
You
can
now
make
an
end-to-end
TCP
connection
and
use
that
we'd
love
you
to
get
involved.
S
You
can
join
the
DNS
SD
mailing
list.
You
can
check
out
the
code
from
the
IETF
hackathon.
We
have
an
open,
wrt
package
for
this
little
open,
wrt
router.
In
about
five
minutes.
You
can
add
a
discovery
proxy
to
this
and
have
one
running
on
your
own
home
network,
we'll
be
showing
this
at
the
hack
demo
happy
hour
tomorrow,
just
a
cross
over
there.
So
you
can
come
and
see
it
working
for
yourself
and,
of
course,
come
to
our
DNS
SD
work
group
meeting
on
Thursday.
Thank
you.
T
So
first
about
the
motivation
I
seen
tonight,
he
involves
we
could
say
we
have
already
experienced
IP
the
first
generation,
but
they
are
still
some
challenges.
For
example,
the
isolated,
the
networked
islands
of
the
limited
program,
program,
programmability
and,
most
importantly,
and
the
network
is
still
on
its
own
and
the
application
and
the
network
are
isolated
at
the
carpet.
And
now
we
have
SRA
six.
We
could
say
we
are
entering
a
new
generation
YP,
the
second
generation
and
I.
Sorry,
six
has
its
own
mission
and
first
it
is
a
based
on
ipv6.
T
So
it
has
the
affinity
to
IP.
So
it
could
be
much
easier
to
integrate
the
network
domains
and
also
it
has
the
programmer
ability.
So
it
has
the
programmer
programmable
fields,
so
you
could
convey
more
information
from
the
applications
to
the
network,
so
in
that
case
you
could
integrate
the
application
and
the
network
make
them
to
work
together.
So
here
are
the
ipv6
extension
hiders.
We
have
the
hop
by
hop
and
destination
options,
hiders
and
also
the
routing
header.
T
I
sorry
choose
one
of
this,
so
we
have
the
arguments
fields
and
also
that
he
are
we
you
we
could
use
to
convey
some
information
from
the
applications
and
that
are
the
foundations
for
the
application.
Aware.
Ipv6,
all
eyes
are
basics.
Networking
we
call
it
AP
+
6.
So
basically
we
are
actually
make
use
of
the
ipv6
extension
hiders
to
convey
some
informations
from
the
applications
into
the
network.
T
So
the
network
could
make
the
fine
granular
traffic
operations
to
do
the,
for
example,
the
resort
network
resource
assessment
to
guarantee
the
SLA,
so
it
could
be
applied
to,
for
example,
the
fixed
mobile
broadband
like
the
b2c
scenarios
and
also
the
mobile
broadband,
and
for
the
solution
side
we
could
have
the
host
decide
solution.
That
is
the
application
directly
put
the
information
into
the
ipv6
hiders.
All
it
could
be.
T
The
network
side
solutions
that
is
the
network
edge,
could
attack
the
application
and
provide
the
information
about
the
application
and
can
wing
it
into
the,
and
we
are.
We
are
going
to
have
a
side
meeting
on
Thursday
Thursday
morning
and
we
have
the
agenda.
You
could
refer
refer
the
related
drafts
we
listed
in
the
side
meeting
wiki.
Okay,
thank
you.
U
V
Q
Great,
my
name
is
Joseph
Potvin
I'm,
the
executive
director
for
Excel
rhythms
foundation.
Some
colleagues
and
I
have
initiated
a
project
called
an
internet
of
rules.
I'll
say
right
away.
If
you
think
it's
a
terrible
name
that
we
should
not
be
calling
what
we're
doing
that.
Please,
let
us
know
I'll
restrict
this
to
the.
Why
and
the
what
of
what
we're
doing
I
could
explain
how
there's
running
code
behind
this
we're
doing.
Q
Alpha
testing
right
now,
but
I've
had
a
very
interesting
conversation
over
the
last
two
days
as
part
of
the
hackathon,
and
there's
lots
of
different
ideas
about
and
good
ideas
about
how
to
do
this
next
so
very
happy
to
see
what
Rodney
was
talking
about
a
few
sessions
here
ago.
We're
actually
working
on
the
generalization
of
how
words
like
must,
must
not
required
shell
and
so
forth,
actually
get
deployed.
Q
So
if
you
can
imagine
any
IOT
implementation
and,
let's
say,
there's
some
Court
decision
in
some
province
or
state
and
that's
gonna
affect
privacy
rules
in
terms
of
how
data
moves
around
from
in
to
all
sorts
of
IOT
devices,
exactly.
How
is
that
new
rule
going
to
get
deployed?
You
can
even
say
how
it's
going
to
get
deployed
through
the
equipment
providers.
How
is
even
that
rule
expressed
and
say,
English
or
or
Spanish
going
to
get
deployed
to
the
45,000
suppliers
of
these
IOT
devices?
Q
This
affects
issues
in
money,
finance,
Commerce,
Tax,
international
trade,
machine
control
systems,
internet-based
networking
whatever
it
is.
The
gap
in
this
space
is
so
huge.
It's
hard
to
see.
So
it's
hard
to
communicate
this
sometimes
because
most
people
are
looking
for
little
gaps.
This
is
an
enormous
gap
next,
so
the
problem
is
enormous.
Q
Lee
wasteful
error-prone
redundancy,
each
of
you
who
is
not
from
Canada
when
you
pay
your
hotel
bill
right
now,
you're
actually
supposed
to
be
zero
rated
on
the
value-added
tax,
but
you're
going
to
pay
it,
and
if
you
were
to
try
to
claim
it
back
on
the
way
out.
Good
luck
to
you.
Little
rules
like
that
come
in
and
they
were
just
simply
not
deployable.
Today,
that's
tax,
but
any
of
these
other
domains.
You
have
the
same
kind
of
problem.
It
requires
a
domain-specific
language
which
we've
prototyped
right
now
and
not
prototype.
Q
We've
actually
implemented
an
alpha
and
an
optimized
algorithm
search.
We're
not
dealing
with
if-then
statements.
We're
dealing
with
given
X
facts.
Con
has
a
context
when
there's
an
input
fact
for
a
circumstance.
Then
Zed
ought
to
be
the
case.
So
these
are
just
three
facts.
Next,
the
actual
software
we
have
deployed
begins
by
interacting
with
an
API
there's
a
small
component
piece
and
auxiliary
piece
called
lichen.
You
can
use
it
or
not,
use
it.
It's
a
it's!
A
reference.
Implementation
create
your
own.
Q
If
you
like,
roll
your
own,
that
provides
the
context
FAQ
and
the
input
info
fact
up
to
the
server
in
the
server
is
a
distributed
set
of
servers
with
the
collection
of
algorithms
which
implement
the
rules,
and
these
algorithms
are
simple,
declarative,
tabular
or
tuple
oriented
programs.
We
deliver
those
back
as
output
facts.
We
do
not
inject
them.
We
stop
at
the
point
of
delivering
back
the
fact
there
that
there
is
a
rule
and
here's
what
it
is
and
next
place
so
excel.
Go
that
domain-specific
language.
Q
It's
think
of
programming
in
terms
of
control,
tables,
decision
tables
and
so
forth,
with
a
few
reserved
words
very,
very
minimalist.
It's
deliberately
not
turing-complete
and
it
uses
all
any
standard
schema
when
it
comes
to
identifying
what
industry.
It
is
what
what
jurisdiction?
It
is,
what
product
type
it
is
next,
please
intro,
Libre,
sorry
notice,
I,
okay,
that's
the
search
engine
and
then
next
slide
I'm
presenting
in
this
room
on
Tuesday
thirty.
U
W
X
Hi,
so
I'm
gonna
talk
a
little
bit
about
multiple
provisioning
domains,
a
term
that
you've
probably
heard
and
maybe
know
what
it
means,
but
I
think
a
lot
of
people.
Don't
so.
Hence
the
talk.
So
the
point
of
this
is
back
in
the
1990s.
You
had
a
host.
It
was
probably
sitting
on
your
desk.
It's
connected
to
a
network.
It
got
DNS
and
IP
addresses
somehow
from
the
network,
and
everything
just
worked.
That
was
great
good
times.
X
Times
have
changed,
and
so
recently-
and
you
know,
certainly
in
the
20
teens
and
even
before
that
it
was
not
uncommon
to
have
a
host
connected
to
more
than
one
network.
Typical
scenarios.
Vpn
is
a
classic
typical
scenario,
but
a
less
well
less
well
understood
scenario
is
when
you
have
a
host
is
connected,
say
a
phone,
for
example,
that's
connected
to
your
cell
service
provider
and
to
a
wireless
network
which
may
have
a
captive
portal
on
it.
X
Anyway,
so
so
the
host,
so
if
a
host
looks
up
a
service
using
using
using
the
DNS
server
that
it
got
from
from
network
a,
it
is
and
then
tries
to
use
the
answer
it
got
on
network
B.
If
that
service
is
actually
only
reachable
on
network
a
it's
gonna
fail,
so
we
need
to
be
able
to
associate
networks.
We
need
to
be
able
to
associate
things
like
DNS
servers
and
IP
prefixes
together
and,
of
course,
in
the
2020s.
Things
are
even
more
exciting.
This
is
starting
now,
but,
but
you
know
you
can
see
there.
X
X
The
answer
is
with
provisioning
domains.
The
provisioning
domain
is
a
connect
collection
of
configuration
information,
that's
known,
to
have
come
from
the
same
source.
So
in
the
previous
example,
where
we
had
network
a
and
network
B
networking
and
network
B
were
both
different
provisioning
domains
and
similarly,
in
the
2020s
example,
where
we've
got
provider
a
and
provider
B,
those
are
both
also
different
provisioning
domains.
X
So
how
do
we
communicate
with
this
to
the
hosts
in
the
2010s?
Usually,
we
would
just
notice
that
we
had
two
network
interfaces,
and
so
we
would
be
able
to
set
up
an
ad-hoc
provisioning
domain.
We
would
just
assume
that
information
that
we
got
on
interface,
a
and
interface
information,
that
we've
got
an
interface
B
are
not
interchangeable
and-
and
we
would
just
do
that
automatically
without
being
told
that
doesn't
work
so
well,
if
you
have
a
border
router
and
you're
behind
the
border
router
and
the
border
router
is
connected
to
two
different
homes.
X
So
the
original
work
was
done
in
the
myth
working
group.
We
produced
a
document
called
the
multiple,
multiple
provisioning
domain
architecture,
which
explained
the
problem
that
I
just
explained
to
you
in
quite
a
bit
more
detail
and
more
accuracy,
but
didn't
actually
solve
it.
And
then,
just
recently,
a
number
of
folks
in
the
interior
working
group
been
working
on
a
document
called
draft
and
area
providing
domains,
discovering
provisioning
domain
names
and
data.
X
So
this
is
using
an
RA
option
to
explicitly
state
that
this
prefix
and
all
the
information
about
this
prefix
is
in
its
own
provisioning
domain,
which
has
this
name
and
so
that
work
is
almost
done.
I'm
mostly
telling
you
about
this,
because
I
think
it's
really
useful
and
you
want
to
know
please
come
to
inter.
Y
V
V
We
did
a
follow
on
to
the
tcp
over
satellite
working
group
in
1997
to
2000
talking
about
very
long
RTT
interaction
with
slow
loss
recovery.
We
I
brought
a
proposal
for
a
TCP
over
cellular
to
the
IETF
and
the
ad
suggestive
structured
approach.
Instead
of
doing
TCP
over
food
links,
Aaron
and
I
co-chaired
the
pilk
working
group
1999
to
2004,
and
we
had
specific
recommendations
that
we
issued
as
BCPs,
most
of
them
for
specific
link
characteristics
and
that
was
adopted
actually
by
web
form
version.
V
2
of
life
was
good
for
a
while
things
have
probably
changed
since
2004.
A
lot
of
stuff
is
on
here,
there's
actually
probably
more
things
that
have
changed
that
then
I
didn't
put
on
the
slide.
Things
like
CD
ends
and
stuff
like
that.
But
you
know
it's
been
going
on
ever
just
to
pick
one
of
them.
Well,
weren't.
Thinking
about
multipath
at
all,
we
were
thrilled.
We
could
get
one
path
to
work
so
I'd
like
to
do
at
ITF
105.
V
V
Petha
were
now
working,
I'd
like
to
talk
to
them
about
what
is
engineering
and
what
is
research
so,
what's
ready
for
the
ITF
to
make
recommendations
for
and
what's
not
ready
for
the
ITF
to
make
recommendations
for
independent
this
that
wimpy
no
chance
meeting
the
thing
so
like
I,
say
the
thing
I'm
saying
here
that
I
need
to
make
pretty
clear.
Is
that
I'm
talking
about
I'm
talking
about
producing
BCPs
for
protocol
designers,
because
we
still
get
a
lot
of
product?
V
My
favorite
one
was
you
know
if
you
read
my
PhD
dissertation
from
10
years
ago
with
it,
you
would
clearly
say
that,
and
that
was
the
best
route
that
was
the
best
recommendation.
We
had
I
think
the
ITF
has
done
better
in
the
past.
I
think
we
could
do
better
hope
to
see
you
on
Wednesday
morning
and
Thursday
afternoon.
B
W
C
W
So
we
should
we
should
finish
with
much
lesser
than
50
minutes.
I
only
have
a
single
page
here
and
I'm
gonna
give
a
simple,
okay
announcement
on
the
loops
path,
because
this
is
one
of
the
very
first
sessions
of
ITF.
So
I
want
you
guys
who
were
possibly
just
here
and
with
your
jetlag
aware
that
this
time
the
session
starts
from
10
okay.
So
tomorrow
morning,
10
o'clock,
we
are
going
to
have
debuff
loops,
which
stands
for
the
local
optimization
on
path
segments.
W
Okay,
the
pet
okay,
give
a
very
simple
description.
The
path
of
a
long-haul
Network
can
be
naturally
or
purposely
partitioned
into
multiple
segments
via
possibly
like
tahno
stitching,
so
loops
aims
to
provide
a
loss,
recovery
locally
over
some
specific
segments.
So
that's
the
basic
idea
of
loops.
So
here
are
two
pointers
of
the
drafts.
So
please
read
them
and
please
join
us
tomorrow
morning:
10:00,
okay,
thanks.
Z
Z
It
could
be
a
user
all
sorts
of
things
like
that,
and
this
would
get
hopefully
real-time
updates
from
as
many
TL
DS
and
then
possibly
later
on.
Second
and
third
level
domains
as
possible
and
then
it'll
aggregate
that
and
ship
it
out
to
whoever
wants
to
get
it
in,
hopefully
real-time
or
near
real-time
formats.
Z
Z
If
you
just
want
to
see,
we
have
a
very
simple
web
page
up
there,
and
we
also
have
a
form
where
you
can
fill
it.
If
you
want
to
get
more
information
as
we
get
more
data
than
ships
out
we're
in
the
process
of
trying
to
stand
up
or
merge
with
a
be
taken
under
some
other
existing
non-profit,
an
independent
agency
or
an
organization,
so
we
can
have
a
independent
status,
build
something
that's
hopefully
available
to
the
community
at
large
and
we're
hoping
to
make
it
free
to
end-users.
B
All
right,
thank
you.
So,
the
last
session
there
less
talk
is
mine,
so
I
know
some
of
you
know
about
this
and
been
participating
in
it,
but
not
everybody.
Maybe
so
this
is
kind
of
a
hobby
law
side.
Project
I've
been
doing
at
ITF
meetings,
which
is
to
try
to
do
a
little
social
event.
That's
modeled
on
the
sitcom
outrageous
opinion
session,
and
it
was
the
ideas
to
do
some
satirical
talks.
I
was
calling
it
bad
idea,
Pecha
Kucha,
for
a
while
trying
to
generalize
it
to
not
strictly
be
Pecha
Kucha
format.
B
We've
got
several
folks
signed
up
now
and
I
saw
a
few
come
into
my
inbox
during
the
session.
So
I
think
the
list
is
growing.
It's
Thursday
night
at
9:30
in
Duluth,
which
I
think
is
the
room
right
next
door
to
here.
If
you're
interested
in
giving
a
talk,
you
can
do
a
Pecha
Kucha,
which
is
a
very
structured
twenty
slides.
Each
slide
is
up
for
20
seconds
should
be
mostly
text
free,
yeah
or
you
can
just
do
a
short
lightning
talk.
B
It
has
to
be
less
than
seven
minutes
and
the
way
to
get
time
on
the
agenda
is
to
send
me
an
email
with
a
talk,
title
and
and
then
I
need
slides
by
six
o'clock
on
Thursday,
so
everybody's
invited
there
will
be
some
beer
and
I
hope
to
see
you
all
there
and
thank
you
for
coming
here.
If
you
have
feedback
about
this
or
the
Pecha
Kucha
talks,
please
send
me
an
email,
I'm,
always
happy
to
get
feedback.
So
thank
you.
Buddy
go
have
dinner
and
enjoy
the
week.