►
From YouTube: IETF104-QIRG-20190326-1120
Description
QIRG meeting session at IETF104
2019/03/26 1120
https://datatracker.ietf.org/meeting/104/proceedings/
A
All
right,
it's
11
21,
let's
go
ahead
and
get
started.
Shall
we
so
welcome
to
the
quantum
internet
research
group
qi,
RG
meeting
proposed
research
group,
I
guess
I
should
have
in
the
title
still
I'm
rod
van
Meter
I'm
chairing
the
session
this
morning
and
we
have
a
jabber
scribe.
Maybe
maybe
we
need
a
note-taker
any
volunteers.
A
Excellent,
we
have
a
volunteer
for
note-taker.
Thank
you.
Let's
see
so
first
up
today
am
I.
Using
this
thing,
it
seems
to
be
a
little
bit
off.
So
yesterday
we
had
the
tutorial
I.
Think
probably
most
of
you
who
are
here
were
in
the
tutorial.
If
not,
you
want
to
watch
it.
It's
available
up
on
the
YouTube.
Already
quality
seems
to
be
very
nice
in
terms
of
a
you
know,
audio
and
video.
So
today,
here's
meeting
we're
gonna
cover
some
IDs
and
some
some
stuff.
A
A
So
the
agenda
for
today,
let's
see
so
that's
where
we
are
drafts,
we're
going
to
talk
about
there-
are
several
drafts
already
up
and
everything
is
in
data
tracker.
At
this
point,
therefore,
we're
going
to
cover
and
then
a
fifth
short
report
on
what
happened
at
the
hackathon
on
Saturday
and
Sunday.
So,
let's
see
first
up
white
tech.
You
want
to
come
up.
A
A
A
And
also
as
a
reminder
when
you
do
comment
up
and
ask
questions,
please
give
your
name
and
please
I,
know
everybody's
used
to
saying
their
own
name,
but
please
to
say
it
slowly
and
clearly,
so
the
note-taker
can
pick
it
up.
That
would
be
a
big
help
or
take
you
want
this
use
the
left/right
arrows,
not
the
other
things
hanging
on
the
way
puts
us
in
full-screen
mode,
all
right.
There
you
go.
B
Okay,
hi
everybody
I'm
Wojtek
I'm,
a
postdoc
researcher
at
qt-kt
Delft,
which
is
part
of
the
quantum
Internet
Alliance,
and
what
I'm
here
to
present
is
essentially
what
I
want
to
actually
pitch
an
idea
of,
say,
work.
We
could
do
as
a
research
group
together
they
draft
up
online
is
normally
like
my
idea
and
proposal
of
what
it
could
look
like,
rather
than
an
actual
proposal
of
a
document
that
should
go
forward
in
its
current
form.
So
what
I
want
to
propose?
B
B
B
A
B
Okay
continuing
so
where
am
I
coming
from
with
this
idea?
Essentially
so
the
classical
internet
one
was
built,
it
had
a
set
of
goals,
guiding
what
what
trade-offs
should
be
made
and
how
what
it?
What
is
the
fundamental
goal
I
should
achieve
for
the
classical
Internet?
It
was
essentially
I'm.
Gonna
read
out
from
a
paper
by
David
Clarke.
The
top
level
goal
for
the
DARPA
internet
architecture
was
to
develop
an
effective
technique
for
multiplex
utilization
of
existing
interconnected
networks.
B
The
goal
of
the
classical
internet
was
you
had
our
PI
and
you
had
a
bunch
of
other
networks
which
wanted
to
connect
to
and
they
wanted
to
connect
all
of
them.
They
had
a
bunch
of
secondary
goals
which
they
defined
as
like
what
other
goals
they
want
to
achieve
with
architecture
for
their
internet
protocol
for
the
tcp/ip
stack
and
they
are
in
the
order
of
priority
as
they
define
them
and
for
they
primarily
wanted
the
Internet
communication
to
survive.
Despite
losses,
they
wanted
to
provide
different
types
of
services.
B
They
wanted
to
accommodate
a
variety
of
networks.
They
wanted
to
promote,
distributed
matters
or
the
resources
cost
effectiveness.
The
ability
to
connect
with
a
low
level
of
effort
and
that
resources
must
be
accountable,
and
if
you
read
David
Clarke's
paper,
the
design
philosophy,
the
dark
pension
of
protocols.
Essentially,
he
summarizes
that
the
first
few
goals
were
achieved
spot-on,
but
the
last
few
goals
were
kind
of
sidelined
and
only
partially
achieved
and
there's
also
an
RFC
195,
a
to
be
specific,
which
outlines
a
set
of
principles
for
the
classical
internet.
B
And
so
this
is
just
a
summary
of
where
I'm
coming
from
and
what
there
is
for
the
classical
Internet
in
terms
of
goals
and
principles.
And
the
question
is
what
are
our
goals
and
so
I
submitted
a
draft
which
is
more
like
an
idea,
a
proposal
of
what
a
document
that
achieves
this
could
look
like
in
which
you
suggest
basically
there's
a
suggestion
that
perhaps
our
priorities
should
be
more
about,
because
we
don't
have
the
goal:
the
same
goals
of
the
classical
Internet.
B
Why
I
think
we
need
that
is
a
bit
essentially
like
the
trade-offs
must
be
made
it's
difficult
to
achieve
a
good
for
everything.
Architecture.
Question
is
like
what
should
we
prioritize
when
we
were
building
and
quantum
internet
for
the
purposes
of
users
and
applications
and
network
operators
essentially
serve
as
a
guide
for
all
the
people
who
are
designing
the
network
and
questions
the
qrg
community
here
is
essentially
like
what
people
in
the
community
find
it
useful
for
us
to
define.
B
Such
goals
would
be
useful
to
work
together
to
define
these
principles
and
as
a
curator
right
place
for
it
and,
as
an
output,
I'd
see
essentially
a
document
for
as
a
published
by
the
QR
AG,
outlining
these
goals
and
principles
and
outlining
the
thought
process
by
which
we
reached
them
and
possibly
also
an
academic
publication,
because
there's
still
a
lot
of
academics
working
on
this
who
should
be
involved,
I.
Think
so,
specifically,
we
had
there's
a
lot
of
physicists
who
are
interested
in
this,
but
I.
A
A
D
B
E
Hi
Jim
Jones
so
involved
in
a
in
a
project.
That's
building
networks
that
connect
European
national
research
networks
together
and
we're
interested
as
part
of
that
project
in
potentially
exploring
quantum
key
distribution.
So
I
think
the
question
would
be
in
building
that
network.
What
are
the
considerations
for
putting
this
in
place?
Perhaps
alongside
it?
Do
you
need
separate
darf
fibers?
Can
you
use
existing
wavelengths
in
some
way,
so
those
sort
of
considerations
for
people
that
are
building
existing
networks
as
to
how
this
may
or
may
not
sit
alongside
it
would
be
very
useful.
Thank.
B
A
A
B
A
A
F
So
my
goal
today
is
to
just
give
a
brief
presentation
of
what's
in
the
draft.
I
will
not
go
into
too
much
details,
because
I
would
like
to
more
have
feedback
from
you
of
if
there's
questions
or
comments
or
what
to
improve
so,
maybe
just
before
I
start,
who
has
had
a
maybe
a
brief
look
at
the
draft
of
the
audience,
could
I
see
a
raise
of
hands?
F
So
this
the
scope
of
the
draft
is
to
try
to
define
the
service
and
the
interface
of
the
link
layer
from
higher
layers
in
a
quantum
network,
and
but
it
doesn't
concern
a
protocol
that
realizes
this
service.
But
I
would
just
like
to
point
out
that
we
recently
put
a
paper
online
but
does
propose
a
protocol
that
satisfies
this
service
and
you
can
find
it
on
this
link.
It
will
also
be
up
in
the
end
of
the
presentation
in
this
paper.
F
We
we
also
fully
implements
this
protocol
in
a
discrete
event
simulation
and
we've
done
some
quite
extensive
simulations.
But
that's
a
separate
thing.
That's
you
can
look
at
this
paper
if
you
interested,
but
the
draft
I'm
talking
about
today
is
more
to
try
to
define
the
deserve
service
and
interface
of
a
link
layer
and
just
to
get
started
as
you're.
F
F
But
for
those
of
you
who
had
a
look
at
it,
just
a
short
sort
of
recap,
the
idea
is
that
a
higher
layer
essentially
sends
a
message
which
is
to
create
entanglement
or
requested,
create
entanglement
of
one
or
more
and
entangled
pairs.
And,
together
with
this
message,
one
can
also
specify
a
desired
minimum.
Fidelity
again,
this
was
explained
yesterday
in
the
tutorial
or,
but
it
means
with
fidelity
together
with
the
maximum
waiting
time
that
the
application
or
the
higher
layer
is
willing
to
wait
for
this
entitlement
to
be
generated.
F
And
the
reason
for
this
is
that
there's
usually
a
trade-off
between
how
high
fidelity
you
can
have
and
how
fast
you
can
go.
So
usually,
if
you
want
higher
fidelity,
you
have
to
wait
longer
and
the
higher
layers
can
then
give
an
idea
of
to
the
link
layer
of
how
long
it's
willing
to
wait
and
what
minimum
fidelity
its
it
needs.
F
The
the
reason
for
this
is
that
in
some
cases
you
can
actually
go
faster
or
generate
content
faster
if
you
measure
it
directly
and
if,
if
you
want
to
know
more
about
this,
you
can
also
ask,
but
for
the
main
forum
any
time
I
would
like
to
maybe
have
some
more
discussion
with
some
specific
questions.
So
one
question
is
from
from
above
is
this
service
that
we
define
in
this
paper?
What
an
application
or
high
layer
actually
wants
requires?
F
Is
there
something
that's
missing
or
something
that's
redundant
in
the
draft,
but
also
from
below?
Is
this
from
a
hardware
point
of
view
feasible
to
implement
in
delft,
wait
we
we
have
a
hardware
which
is
built
on
nitrogen
vacancies
in
in
diamonds,
so
we
come
sort
of
from
this
point
of
view,
but
it
it
would
also
be
very
interesting
to
see
groups
with
other
hardware,
whether
what
we
defined
here
make
sense
for
them
and
what
limitations
that
could
be.
F
Maybe
some
hardware's
can
only
do
subsets
of
the
commands
that
we
specify
and
watch
such
subsets
could
they
be,
but
also
the
continued
work
on
the
draft.
So
this
is
the
first
time
I
I
write
a
draft
on
defining
an
interface
of
the
lincare.
So
for
me
it
will
be
very
helpful
for
if
someone
would
like
to
that,
has
done
this
before
to
contribute
and
maybe
say,
what's
what's
missing
what
should
be
clarified
to
go
forward
with
the
draft.
I
should
also
say
that
I
actually
missed
missed
named
the
draft
when
I
uploaded
it.
A
A
G
G
Of
like
an
IP
address,
okay,
so
if
it
so
I
saw
that
it
could
be
like
a
MAC
address
for
classical
network,
but
you
mention,
but
like
it's
kind
of
IP
address.
So
in
this
case,
like
you
measure
at
this
moment,
you
mention
about
like
an
already
it's
already
to
what
bits,
but
could
be
more
if
I'm
sure,
but
in
in
future
there
is
a
lot
of
quantum
computing.
Compute
computers
depend
on
this
per
net,
so
could
it
could
be?
We
should
consider
a
little
bit
more
wider
space
yeah
for
that.
Thank.
F
A
H
I
A
Actually
I
had
a
question.
I'd
already
prepared
a
question
on
this
exact
topic,
so
not
not
as
chair,
but
as
a
personal
question
here
the
I
had
saw
it
seen
the
same
thing.
I
think
as
I
understand
that
this
remote
node
ID
is
a
specifier
for
a
neighbor.
Is
that
right?
That's
right!
This
is
not
a
a
network-wide
identifier,
no
yeah
right,
yeah,
okay,
so
this
is,
it
only
has
to
be.
The
number
space
has
to
be
big
enough
to
identify
everybody
who
could
possibly
be
an
immediate
neighbor
for
the
creation
of
physical
entanglement,
yeah.
F
Right
there
is
a
response
to
this,
so
there
is
a
node
ID
in
the
in
response,
which
we
plan
to
use
to
essentially
identify
the
entanglement,
and
the
idea
is
that
this
entanglement
ID
should
be
unique
in
the
network
also,
and
it's
built
from
the
ID
of
the
node.
So
in
that
sense
it
actually
also
needs
to
be
unique
in
the
in
the
network.
Okay,.
I
F
I
And
is
it
usually
on
the
other
side
of
this
say
Ethernet
yeah?
It
could
be
right,
okay,
and
if
these
are
defined
to
be
point-to-point,
then
you
don't
need
a
node
ID,
because
it's
always
the
thing
on
the
other
side.
Do
you
expect
that
the
receiving
node
look
at
this
packet
and
say
remote
node
ID
field
equals
my
node
ID?
Therefore,
I
should
use
it.
Otherwise.
What
do
you
do?
Do
you
forward
it?
Do
you
drop
it
on
the
floor?
There's
a
sender
was
an
error.
These
are
sorts
of
things.
I
F
I
J
Naivete-
is
what's
the
topology
relationship
between
the
classical
network
and
the
quantum
network,
and
that
would
help
me
understand
what
you're
trying
to
do
with
the
remote
node
ID.
So
you
know
obviously
that
may
change
from
you
know
you
know
different
implementations,
but
that
might
be
something
that
that
would
help
those
of
us
new
to
this
field
to
understand
what's
going
on
and
how
those
relate
back
and
forth.
Yeah.
F
E
Tim
John
I
just
like
to
echo
that
comment.
It
kind
of
goes
back
to
my
earlier
comment.
The
other
thing,
if
I
understood
yesterday's
tutorial
correctly,
was
that,
in
order
to
move
quantum
state
from
one
place
to
another,
you
need
to
send
a
couple
of
real
data
bits
so
again,
understanding
how
that
fits
in
with
this
would
be
useful
as
well
yeah.
E
K
Okay,
Santino
also
affiliated
with
qtek,
somehow
I'm
very
interested
in
the
capacity
of
this
network,
because
if
you
look
from
an
application
side
of
things,
you
can
request.
I
want
high
fidelity
high
capacity
quickly
for
my
application,
that's
not
possible
yet
in
current
staying
with
the
hardware.
So
how
can
you
deal
with
that
in
this
type
of
protocols?
Yes,.
F
So
they
can
certainly
be
messages
coming
back,
which
is.
This
is
unsupported.
For
example,
if
you
request
a
very
high
fidelity
in
a
very
short
time,
the
hardware
might
not
be
able
to
respond
to
this
so
and
then
you
can
say
unsupported
and
then
it's
up
to
you
to
decide.
Do
you
want
to
continue
yeah
so.
K
F
L
Hello,
League
America
Russia
in
order
to
provide
authenticity
or
the
remote
node,
so
a
in
order
to
withstand
the
visitors
means
oh
man
in
the
middle
attacks.
Their
motto
should
be
authenticated.
That
means,
if
you
incorporate
your
protocol
in
the
IP,
then
these
remote
node
ID
could
be
irrelevant
because
because
the
node,
the
node,
will
be
authenticated
at
IP
level.
L
H
Hey
Tobias
again,
it
looks
a
little
bit
similar
that
you
could.
So
if
it's
not
an
IP
address,
if
it's
a
local
link,
it
could
be
something
like
art.
So
mapping
between
an
IP
address
and
an
actual
node
with
a
MAC
address
kind
of
thing,
which
is
your
remote
node
ID.
Is
that
something
which
could
be
an
idea
to
just
define
like
layer
between
IP
and
quantum
mech.
F
So
I
should
say
that
the
the
task
of
the
remote
ID
or
the
purpose
of
the
remote
ID
in
the
create
message
is
basically
to
if
you
have
different
physical
interfaces
to,
for
example,
a
mid
point
where
you
can
create
entanglements.
You
just
need
to
specify
which
other
physical,
remote
node,
but
the
in
the
response
in
there.
Okay
that
and
has
been
generated.
It
has
a
different
purpose.
Actually,
so
there
it
is
used
to
identify
the
generated
entanglements
based
on
the
IDS
of
the
nose
that
hold
the
generator
in
entanglement.
F
I
N
Define
aside
the
N,
is
it
a
goal
like
to
reuse
much
stuff
as
possible
on
a
classical
Internet
and
anything
new
you
create?
They
have
to
justify
your.
Why
you're
choosing
that
particular
parameter
like,
for
example,
remote
ID,
it's
something
they
envision
like.
We
could
only
create
new
stuff
if
it
doesn't
work,
because
we
have
those
requirements.
N
A
As
both
chair
and
an
individual
I
would
say
absolutely:
yes,
we
want
to
avoid
reinventing
things.
We
want
to
use
everything.
We've
got
possibly
all
right,
let's
see
so
this
is
currently
at
the
status
of
an
individual
submission.
I
was
not
planning
on
taking
this
one
yet
forward
as
an
actual
RG
working
item.
I
think
we
can
keep
this
as
an
individual
draft
for
at
least
another
draft
or
two
yeah
veteran
okay.
So
let's
do
that?
A
Let's
keep
this
as
an
individual
draft,
but
this
discussion-
all
of
these
questions
were
really
outstanding
and
every
single
one
of
these
needs
to
be
answered
in
India
in
the
draft
as
we
go
forward.
So
the
I'm
certain
our
note
taker
did
an
excellent
job
there,
but,
but
if
anything,
if
anything
doesn't
show
up
in
the
draft
eventually
it'll
get
your
please
bring
it
back
up
on
the
on
the
mailing
list.
As
we
go
anything
else,
good
thanks
thanks
all
right.
Next
draft
up
is
actually
mine.
A
A
So
we
put
up
a
draft
on
connections
set
up
in
a
in
a
quantum
network,
we're
doing
a
bunch
of
simulation
work
at
the
moment,
but
we're
trying
to
make
it
as
hardcore
realistic
as
we
can
in
terms
of
all
of
the
work
you
have
to
do
to
bootstrap
the
entire
network
and
as
well
as
actually
getting
the
connections
going
on.
So
this
is
a
framework
document
for
how
we
are
currently
establishing
connections
inside
inside
our
simulator.
How
many
people
have
actually
looked
at
the
draft?
A
This
one
was
posted
right
around
the
deadline,
so
probably
only
a
handful
okay,
so
comments
always
welcome
the
so
the
idea
is
you
want
to
create
a
connection
across
multiple
hops
from
place
to
place.
The
middle
nodes,
as
we've
said,
have
to
perform
the
entanglement
swapping
the
error
management,
so
Bill
Monroe
wants
to
connect
from
there
to
the
quantum
internet,
distributed
data,
IT
computing
house
or
Quidditch
the,
and
this
means
that
we're
going
to
have
to
find
a
path
through
this.
A
We
are
not
talking
in
this
document
about
the
actual
routing
process,
that's
separate,
but
we're
talking
about
the
set
of
messages
that
have
to
pass
from
a
place
to
place
in
order
to
make
all
of
this
work.
So
this
is
planning
the
sequence
of
operations
and
then
convey
that
sequence
to
the
nodes
constraints
and
assumptions.
A
One
of
the
things
again,
where
the
physicists
sort
of
failed
to
realize
what
happens
in
even
a
medium
scale
network,
let
alone
something
like
the
Internet-
is
that
there
are
a
great
number
of
characteristics
of
the
links
and
no
codes
that
are
on
the
entire
network
that
are
a
priori
unknown
to
you
when
you're
starting
to
try
to
try
to
create
a
connection.
So
part
of
what
we're
trying
to
do
here
is
figure
out
how
you're
going
to
collect
that
information
that
allows
you
to
decide
how
a
connection
should
operate.
A
A
Although
at
the
moment
this
draft
only
covers
single
network
path
creation,
it
doesn't
yet
cover
inter
AS
or
the
equivalent
of
that
information
that
each
node
does
not
have
is.
It
does
not
know
about
what
every
node
on
the
network's
entire
hardware
capabilities
are.
It
doesn't
know
what
the
fidelity
of
the
entanglement
is,
that
will
be
created
and
about
the
or
the
amount
of
memory
in
every
node
and
doesn't
know
about
the
local
operations,
and
certainly
when
we
go
from
single
network
to
internetworking.
As
with
a
SS.
A
I
A
Are
links
between
entanglement
capable
repeaters?
Thank
you.
Thank
you
for
the
clarification.
Sorry,
one
of
the
things
that
we
didn't
say
when
in
the
Q&A,
with
with
axel,
is
at
the
level
of
creating
this
entanglement,
there's
always
really
hard.
Your
super
hard,
real-time
stuff,
that
it
has
to
go
with
this.
That's
not
specified
in
this.
You
know
really
low
level
physical
layer
signals
and
those
will
have
to
be
carried
in
the
same
channel
as
the
actual
optical
signals
that
are
creating
the
entanglement.
A
But
then
there
are
sort
of
soft
real-time
messages
for,
for
that
get
exchanged
for
hey
did
that
work,
and
what
are
we
gonna
do
next
right,
so
those
could
be
carried
over
a
separate
IP
like
infrastructure,
and
that
does
not
necessarily
have
to
have
the
same
topology.
But
of
course
you
have
to
be
able
to
identify
who
those
other
nodes
are.
So
only
the
really
low-level
signals
have
to
go
in
the
same
channel,
but
of
course
you
have
to
be
able
to
talk
to
the
other
to
the
other
quantum
nodes
by
some
classical
mechanism.
I
A
If
we
succeed
in
defining
all
of
this
is
running
over
IP,
then
yes,
the
alternative
would
be.
You
know
somebody
somebody
tries
to
create
an
entirely
separate,
classical
Network
for
doing
this.
We
can
do
it
over
I,
don't
know
s
s7
or
ATM,
or
take
your
pick
right.
No,
let's
do
it
over
IP,
right,
absol.
A
A
A
A
Pretty
much
right
yeah,
this
is
the
the
actually
that's
a
good
point.
I
didn't
say
that
and
I
meant
to
say
at
the
beginning
this,
because,
as
I
discussed
yesterday
in
the
tutorial
this
at
this
level,
these
first
generation
networks
building
this
entanglement
end-to-end
is
a
distributed
computation.
This
is
not
stored
and
forward
stuff.
All
of
these
knows
s
abcdefgh.
I
all
of
these
nodes
are
going
to
be
involved
in
building
this
entanglement
and
so
they're
all
going
to
be
cooperating.
A
There
is
going
to
have
to
be
state
at
those
notes
yeah
some
of
the
earlier
work.
We
did
we
sort
of
sort
of
fudged
at
the
edges
and
some
simulation
work
that
we
did
earlier
and
we
did
it
without
what
you
would
consider
really
to
be
connection
level
state
in
this,
but
the
reality
everywhere,
as
as
we
get
more
and
more
detailed
in
the
design,
we're
finding
that
it's
really
going
to
require
state
for
those
connections
at
the
nodes.
Yes,.
O
A
This
the
diagram
represents
the
quantum
in
the
quantum
topology
and
we're
assuming
that
s
has
a
way
to
get
classical
messages
to
a
or
B
or
C
or
anybody
else
in
this
network.
But
you
know
the
way
it's
getting
them
to
this
is
we
are
forwarding
this
hop-by-hop
through
the
through
the
through
this
through
this
network,
there
is
no
requirement
that
that
classical
communication
infrastructure
have
the
same
topology,
but
you
have
to
be
able
to
reach
all
of
the
nodes
that
you
might
need.
A
O
A
The
natural
thing
is
for
the
topology
topologies
to
match
up,
but
it's
not
a
requirement.
There
might
be
multiple
hops
between
s
and
an
a
on
the
on
the
the
on
the
classical
network,
but
there
are
not
in
the
quantum
network.
Ok,
ok,
let's
see
so
we're
running
a
little
short
on
time.
Let's
make
this
the
last
question.
A
Sort
of
stuff
or
sorry
I
builds
what
the
set
of
rules
describing,
what
each
node
and
the
network
should
do,
and
it
sends
them
back
and
they
sort
of
go
hop
by
hop
and
each
node
takes
its
share
of
the
of
that
connection.
Information
off
of
it
and
sends
it
on
back.
You
know
in
theory
it
could.
It
could
also
be
your
unicast
I
in
that
figure
in
the
upper
right.
A
There
were
a
couple
of
questions.
The
questions
already
on
the
mailing
list.
Somebody
asked:
is
this
similar
to
segment
routing
and
the
you
know?
The
I
know
some
of
the
older
literature
on
things
like
Waypoint
routing
and
a
little
bit
about
about
things
like
that.
Those
are
the
kinds
of
things
I
had
in
mind,
but
I'm
not
very
familiar
with
segment
routing.
If
segment
routing
can
do
this
can
carry
this
kind
of
information.
I'd
be
entirely
happy
to
build
this
overtop
of
segment
routing.
We
have
not
defined
packet
and
formats
or
anything
like
that.
E
A
E
A
A
Well,
we
assume
there's
classical
hardware
monitoring
all
of
this,
and
so
the
sooner
or
later,
all
of
the
monitoring
stuff
will
figure
out.
You
know
that
one
of
the
nodes
in
this
path
actually
failed.
It
could
be
you
know,
maybe
D
fails
in
the
middle
of
this.
What
to
do
about
that
and
how
to
route
around
failure.
We
haven't
gotten
that
far
in
design
stuff.
Yet,
thank
you
all
right.
A
A
There
are
not
slides,
but
you
will
find
in
the
drafts
or
at
the
bottom
of
the
of
the
page.
You
will
find
that
the
draft
calls
Qi
RG
Advent,
which
should
probably
been
an
advert
ever
or
no
I.
Guess
that's
abbreviation
for
advertising
entanglement
in
it.
I
get
it
advertising
quantum
entanglement
Ericsson
capabilities.
A
A
If
not
we'll
take
that
up
on
the
mailing
list,
for
whether
or
not
whether
or
not
we
want
to
take
that
drive
that
draft
forward
I,
don't
think
any
of
the
authors
of
it
are
actually
here.
So
the
alright
so
we'll
bring
that
up
on
the
network,
then
or
on
that
sorry,
on
the
mailing
list.
Alright,
so,
let's
see
last
last
presenter.
D
Here
show
to
Europe
okay,
so
tonight
I
am
is
speaking
so
I
will
talk
about
a
brief
summary
of
the
hackathon
and
my
project
aconitine,
so
in
the
Hakkasan
this
time
off.
So
we
hard
work,
one
group
of
quantum
networking
and
we
had
a
three
project
and
one
node
that
is
implementing
routing
on
the
simulator
are
called
similar
occurrence
acts
are
implemented
and
then
my
project
is
discontent
being
so,
I
will
talk
about
this
and
the
last
one
is
about
blockchain
integration,
content
networks.
So
what
we
saw
the
content
in
group
did
in
this
hackathons.
D
So
first
we
define
zircon,
tamping
and
now
writing
draft
the
interactive.
Now
it
will
be
to
appear
in
next
IDF
IOT
F,
so
quantum
network
is
consist
of
actually
two
types
of
brains,
so
you
know
the
fastest
quantum
playing,
of
course,
so
huge.
So
of
course
we
want
to
send
a
photon
and
I
want
to
create
an
entangled
pairs
and
in
classical
internet.
D
D
So
in
quantum
version,
so
this
those
are
correspond
to
dolls.
So
the
purpose
is
actually
to
generate
a
bill
appears
between
two
internals
and
this
success
to
Janette
bear
appears
confirms
that
the
nodes
on
the
entire
path
between
the
two
paths-
haba
ability
to
execute
integrant
swapping
for
routine
of
course,
and
that
Integra
knows
what
involves
proper
and,
as
everything
has
to
be
proper
and
actually
in
Cuzco,
need
to
work.
D
It
was
you
know
in
pushy
dream
and
manages
well
in
lay
a
to
the
CRC
code
works
and
in
rheya,
3
and
IP
haters
are
checked
device
checksum,
so
an
in
quantum
network.
We
have
to
take
care
of
validity
of
their
peers,
so
if
it
is
a
kind
of
measure
of
errors
in
contact
information
theory
so
done
problem
in
Kentucky
talk
is
that
so
the
changing
cost
of
the
repairs
are
so
expensive.
So
actually
no
we
don't
want
to
waste
the
consume
bill,
ps4,
so
quantum
pin.
So
because
we
won't
do
these.
D
D
D
D
N
A
N
D
A
A
Great
anything
else,
good
thanks,
Jota
any
other
business,
any
anything
else.
If
not,
we
will
adjourn
and
we
will
see
you
on
the
mailing
list
and
we'll
schedule.
The
next
Q
IRG
via
the
May
meeting
via
the
mailing
list,
see
you
online
blue
sheets.
Please
return
to
the
front
and
anyone
who
doesn't
who
hasn't
signed
it.
Please
do
so.