►
From YouTube: IETF111-NWCRG-20210729-2200
Description
NWCRG meeting session at IETF111
2021/07/29 2200
https://datatracker.ietf.org/meeting/111/proceedings/
A
B
B
C
If
you
press
the
settings,
the
tools
on.
C
B
C
B
Here
we
are
sure,
yes
perfect,
that
was
the.
B
A
We'll
start
so
welcome
everyone,
we're
five
minutes
late,
which
is
fashionable.
Welcome
to
this
last
meeting
of
this
group,
which
has
been
going
on
for
eight
and
a
half
years
and
weinsan,
will
make
a
review
of
what
we
have
done
during
those
years.
A
So
the
goal
from
the
beginning
was
to
foster
research
and
network
and
application
layer
coding
and
with
the
goal,
to
improve
overall
network
performance
and
from
their
application
performance
codes
and
coding.
Libraries
looking
at
protocols
to
use
the
that
use,
coding
and
real-world
use
cases,
and
I
would
say
that
we
did
a
lot
of
work
on
codes
and
coding.
Libraries
as
mesa
is
going
to
mention.
A
We
looked
at
some,
maybe
less
at
protocols,
but
I
would
say
congestion,
control
and
other
aspects
of
the
networking
that
it's
needed
to
facilitate
the
use
of
coding.
And
there
was
a
lot
of
discussion
about
use
cases
and
work
in
progress
and
how
to
make
this
work
both
on
the
software
implementations
and
on
the
application
side
next
slide.
A
So
this
this
group
has
been
challenged
with
intellectual
property,
but
it
is
to
remind
everyone
that
when
you
talk
today,
we
do
follow
the
irtf
intellectual
property
and
that
everything
is
going
to
be
under
that
and
if
you
want
to
know,
there's
a
bunch
of
rfcs
and
and
information
about
this
in
in
the
policy
repositories.
A
Next
slide
same
thing
for
privacy
and
the
code
of
conduct.
You
know
this
is
an
iotf.
We
also
follow
the
ietf
in
this
and
there's
a
lot
of
information
about
anti-harassment
procedure,
which
also
this
group
has
been
challenged,
and
that
actually
should
not
happen,
and
we
actually
have
to
agree
to
that
next
line.
A
So
I
think,
even
in
these
days,
people
are
still
not
sure
with
the
irtf,
that
the
irtf
is
not
a
standards,
development
organization,
that
we
do
research
and
that
we're
interested
in
research,
even
if
that
research
eventually
may
lead
to
a
real
world
implementation
that
may
go
to
the
ietf.
We
are
not
a
standards.
We
are
a
research
organization
next
slide,
so
this
is
where
we
are.
We
have
obviously
a
charter
that
was
updated
through
the
years.
A
All
the
current
drafts
that
are
in
process
will
be
finalized
and
obviously
there's
a
gitlab
github
repository
for
all
the
again,
the
material
and
related
information
next
slide.
A
So,
of
course,
this
is
a
recorded
session
and
if
you
want
to
talk
press
the
race
hand
button
and
then
the
recording
is
going
to
be
available,
so
it
helps
a
lot
when
you
write
notes
next
slide.
A
So
we
don't
have
a
really
big
agenda
today,
because
most
of
the
drafts
do
not
have
updates
they're
all
finalized
they're
in
the
queue
to
become
informational,
rfcs
and
the
ones
that
are
not
in
the
informational
rfceq
have
been
either
abandoned
for
now
and
maybe
picked
up
somewhere
else
later.
But
for
the
moment
everything
that
needs
to
be
done
you
know
dealt
with,
has
been
dealt
with
so
we're
not
going
to
have
any
presentation.
Today
and
again.
I'd
like
to
to
thank
the
people,
who've
been
very
active
in
this
group
who
are
in
europe.
A
Besides,
venezuela,
I
can
see
cedric
and
nicholas,
and
I
know
it's
the
middle
in
the
middle
of
the
night,
your
your
your
carriage
was
transformed
into
a
pumpkin
10
minutes
ago.
So
I'm
very
happy
that
everybody
is
here,
and
so
the
only
presentation
is
going
to
be
being
sounds
network
coding,
research
group
status
after
eight
and
a
half
years
and
highlight
what
went
well.
A
B
B
B
B
As
I
said,
this
is
a
research
group
that
started
in
beginning
of
2013,
launched
by
brian
adamson
and
victor
foyo.
At
that
time,
lars
was
the
irtf
chair
and
we
held
our
first
meeting
in
orlando.
I
remember
during
atf,
86
or
some
time
ago,
and
then
a
few
things
happened.
B
The
group
went
up
and
down
during
the
2016
year,
there
was
very
little
activity
and
loss
was
about
to
to
close
the
group.
In
fact,
when
I
decided
it
shouldn't
be
done
like
that,
something
should
be
done
to
to
to
to
revive
this.
This
group,
I've
of
the
feeling,
was
an
important
topic
for
ietf
and
irtf,
so
brian
stepped
down,
and
I
volunteered
to
continue
the
activity
to
continue
to
capture
the
group
so
which
happened
end
of
2016.
B
the
next
year,
the
day
after
that
they
joined
me
and
together
we
did,
I
think,
great
things.
First
of
all,
we
finalized
the
ifc.
What
will
become
the
ifc
8406,
the
taxonomy
document,
which,
which
is
something
that
started
a
few
years
before
four
years
before
that
in
2013
and
nice
nice
document
with
many
many
of
us.
If
I
remember
correctly,
there
are
14
or
15
authors
for
this
rfc,
which
is
pretty
unusual,
but
it
was
well
the
output
of
this
of
this
group.
B
So
it
was
meaningful
to
have
so
many
efforts,
so
many
people
contributed
and
we
published
it
in
2018..
That
was
the
first
ifc
of
this
group.
We
now
have
a
second
ifc
5c
8975,
which
discusses
the
use
of
network
coding
and
coding
general
for
satellite
systems,
nice
ifc,
initiated
by
nicola,
who
is
present
and
emmanuel
russia,
and
it
has
been
published
earlier
this
year
in
january
this
year.
B
So
we
are
also
very
happy
with
this
with
this
second
rfc
and
as
said,
the
the
two
now
and
almost
three
very
soon
additional
documents
that
will
enter
the
last
step.
Last
standardization
step,
one
for
network
coding
for
ccn,
another
one
for
coding
and
congestion
control
and
last
one,
hopefully
the
bats
document.
I
will
come
back
to
these
three
documents.
The
the
work
is
not
finalized,
so
two
ifc
for
the
moments-
that's
nice.
B
But
in
fact
I
can
say
there
are
three
very
closely
related
rfcs
that
have
not
been
published
by
this
research
group.
But
I
initiated
the
work
on
those
ifcs
within
this
group,
so
they
are
closely
related.
In
fact,
those
are
for
the
effect
frame
systems
like
frame
framework,
so
it's
more
related
to
the
tsv
working
group
at
iatf.
B
But,
as
I
said,
this
is
closely
related
to
what
we
are
doing
here
in
nwcrg.
B
In
fact,
those
three
ifcs
explain
how
to
extend
the
fact
frame
system
framework
for
the
use
of
sliding
window
cuts
so
typical
of
network
coding,
but
in
this
particular
case
those
sliding
window
cuts
are
used
purely
end
to
end.
B
So
that's
the
reason
why
there,
it's
more
appropriate
to
this
tfc
working
group,
fake
frame,
has
also
been
initiated
not
in
a
tsv
working
group
but
in
the
previous
fake
frame
working
group
so
which
has
been
closed
in
the
meantime,
so
three
additional
ifcs
not
produced
by
nwcrg
but
closely
related
to
the
annual
crg
work
and
each
time
there
was
a
an
update
to
this
draft.
I
also
used
to
present
this
to
our
research
group
as
well.
B
Well,
at
least
the
interesting
part,
the
research
part
and,
of
course,
life
is
not
always
a.
B
Lawful
struggle,
sometimes
the
controversial
events,
and
we
had
one
in
particular
related
to
ipr
disclosure
last
year.
So
it's
pretty
strange
because
during
the
first
seven
years
of
this
research
group,
no
ipr
disclosure
has
been
made
ever
and
then
suddenly,
just
after
the
publication
of
ifc8681,
so
the
one
I
just
mentioned
before
on
the
sliding
window:
lc
fe
schemes
for
fake
frame,
just
after
its
publication,
we
add
this
ipr
disclosure
from
collab,
which
was
pretty
unexpected.
B
I
would
say
it
was
also
a
bit
uncomfortable
for
my
co-chair
for
marijuana,
since
she
is
co-inventor
of
this,
but
she
explained-
and
I
fully
agree
and
fully
spot
her-
that
she
does
not
believe
this
patent
applies
to
this
work.
So
she
never
made
any
disclosure.
So
that's
a
perfect
fine,
no
problem
for
that.
B
So
we
won't
go
into
details.
We
don't
want
to
to
discuss
this.
That's
not
the
point,
but
yes,
sometimes
we
are
facing
well
difficult
situation.
That's
probably
one
of
the
key
issue.
Key
topic-
that's
happened
during
this
along
this
research
group.
Okay,
so
let's
continue.
We
also
have
a
few
regrets.
B
B
We
change
this
for
coding
for
efficient
network
communications,
but
anyway,
random,
linear
network
coding
is
a
part
of
the
the
core
of
this
research
group
at
least
the
way
it
was
fought
initially
and
at
the
end
of
this
group,
we
have
no
nothing,
no
ic
describing
such
coding
schemes,
so
those
contrary
on
those
systems
are
meant
to
to
do
recording
within
the
network,
which
is
the
core
of
this
networking
id
by
the
way
codon
so
the
same
company.
B
We
initiated
two
internet
drafts
on
this
topic,
but
not
for
the
last
time
explained
at
some
point
of
time.
It
was
in
june
2018
that
they
had
no
reason
to
do
any
api
disclosure
for
this
document.
So
it's
a
bit
strange
well,
why
no
disclosure
for
this?
Whereas
there
is
a
disclosure
for
the
I'll,
see
if
random
sliding
window
I'll
see.
B
I
see
that's
uncomfortable
for
me,
but
anyway
that's
a
different
topic,
so
that's
the
first
regret
we
can
have.
The
second
grit
is
that
there
is
no
ic
describing
tetris,
so
the
crease,
which
is
a
cool,
a
pretty
cool
end-to-end
communication
system
with
a
sliding
window
included
as
the
core
protection
mechanism
within
this
protocol.
B
So
we
initiated
an
internet
draft.
I
was
also
part
of
the
co-office,
but
we
never
finalized
this.
For
various
reasons
we
also-
and
that's
the
third
recruit
regret,
can
have.
We
also
initiated
some
work
for
fec
fec
for
quick
and
rc
codes
for
quick.
We
add
those
two
internet
drafts,
but
we
never
managed
to
go
till
the
end
for,
for
several
reasons,
well,
lack
of
resources
for
sure,
but
also
because
of
the
very
long
standardization
process
of
quick.
B
B
So
that's
for
the
first
part
of
the
regret-
and
the
last
regret
I
can
have-
is
this
nice
activity,
but
swift,
so
the
sliding
window
fc
codec
accident
project.
B
We
are
not
very
far
from
the
end
from
having
something
a
workings
correct.
We
at
the
moment
we
can
do
encoding.
We
can
do
some,
we
can
initiate
some
decoding,
but
that's
not
well.
It's
not
finalized
does
not
work.
So
there's
still
some
extra
work
to
be
done.
I
would
like
to
thank
a
lot.
My
colleague,
celerique
aji,
who
is
he's
in
general,
spent
a
lot
of
work.
Lots
of
did
a
lot
of
work
on
the
topic.
B
That
was
a
great
project.
Even
if
we
didn't
manage
to
to
to
have
some
working
solution.
We
also
realized
that
it's
pretty
difficult
to
to
work
on
axon
project
remotely.
As
far
as
I'm
concerned,
I
never
managed
to
devote
a
few
days
for
those
action
sessions
remotely
there
are
always
it's
always
difficult.
We
are
always
bothered
by
extra
activities,
and
so
it
it's.
It's
also
one
of
the
reasons
why
we
didn't
manage
to
go
any
further.
B
B
This
is
what
we
explained
last
year
and
we
always
said
that
this
july
2020
will
be
the
last
meeting,
but
there
will
still
be
some
extra
work
essentially
within
isg,
with
those
two
documents
that
already
entered
the
isg
processing
wedding
queue,
so
the
first
one
for
network
coding
for
content-centric,
networking
and
name
data
networking,
so
a
nice
internet
draft
from
kazuya
and
hitoshi
and
silic,
wasteful
and
well
what
network
coding
can
do
to
help
ccn
communications
and
the
second
document.
B
The
second
internet
drafts
is
this
coding
and
contestant
control
documents
very
nice
stuff.
That
explains
what
are
the
good
which
what
how
we
should
use
coding
respect
to
congestion
control.
There
are
many
pitfalls,
many
mistakes
to
avoid,
and
this
cool
document
explains
how
we
can
do
that
in
a
better
way.
B
B
I
would
say
in
2015-
or
most
probably
I
remember
a
presentation
from
raymond
young
back
in
london
meeting,
so
I
don't
remember
which
iitf
meeting
it
was
but
was
in
london.
So
it
was
a
great
pleasure
for
us
to
to
have
raymond
very
famous
in
this
domain,
presenting
this
the
first
ids
around
bats,
and
then
afterwards
he
made
a
lot
of
well
a
few
additional
presentations.
Very
nice
presentation.
B
So
that's
something
very
cool
because
bat's
codes
are
deployed
in
china,
in
particular,
with
within
the
what
they
explained
is
those
smart
lamps,
for
instance,
and
that's
a
pretty
cool
stuff.
So
we
will
start.
The
research
group
last
call
very
rapidly
right
after
this
meeting.
I
think
the
document
has
been
updated
recently.
Yesterday,
so
that
will
be
step
for
our
group
for
this
document
and
then
we
will
continue
if
everything
is
fine.
B
This
is
last
meeting
and
I
wanted
to
to
have
this
session
essentially
to
thank
you
all,
because
I
think
we
did
a
nice
work
or
doing
this
eight
years
a
bit
more
than
eight
years,
and
it
was
very
a
pleasure
for
us
for
majors
and
myself,
and
I
guess
also
for
the
previous
chairs,
to
to
work
with
you
and
well
that's
a
bit
strange,
but
that's
the
end
of
the
story,
but
we
are
very
happy
to
be
here
and
I
think
we
did
a
good
job,
even
if
we
didn't
manage
to
finalize
all
the
activities
that
we
launched
at
some
point
of
time.
A
No,
I
think
you,
you
basically
summarized
what
we've
done.
I
think
we
yeah
we,
I
think
you
know
the
goal
was
to
foster
some
research
and
some
development
in
the
field
that
we're
coding-
and
I
think
in
this
we've
been
successful
and
I
think
it
was.
It
was
pleasure
for
me
to
work
with
you
and
and
with
well.
First
it
was
lars
and
then
and
then
colin
and
and
making
this
happen
and
again
pardon
me.
B
A
She
was
also
very
supportive
when
I
started
being
the
the
chair.
It
was
my
first
time
I
was
a
chair,
so
it
was
a.
It
was
a
bit
of
a
of
a
learning
curve
and
again
I
see
on
the
list.
A
number
of
people
who've
been
extremely
active
in
this
group
and
you
know
without
you
guys,
nothing
of
this
would
have
happened.
So
thank
you.
So
I
think
that's
it
colin
you're
in
the
queue.
C
Yeah
hi,
I
just
wanted
to
echo
all
the
thanks
to
to
to
you
mary,
jose
to
vance
to
all
the
other
contributors
to
the
the
group
over
the
years.
I
think,
as
founstein
showed
in
the
presentation,
I
think
there's
there's
been
a
lot
of
really
nice
work
coming
out
of
this
group.
C
I
know
it's
not
all
been
plain
sailing,
but
I
I
do
think
we've
learned
a
lot
from
from
the
group's
work
and
I
think
that
the
group
has
made
a
lot
of
really
nice
contributions
to
the
community
and
yeah.
I
fully
expect
we'll
see
a
lot
more
network
coding
work
getting
adopted
in
the
itf
in
future,
and
I
expect
a
fair
chunk
of
it
will
have
been
influenced
by
the
ideas
that
came
out
out
of
this
group
and
were
discussed
in
this
group.
So
yeah.
A
We
we
know
that
the
work
and
quick,
for
example,
I've
seen
christian
utmo,
mentioning
it
in
the
context
of
the
multi-um
multi-path
quick,
and
so
I'm
sure
people
are
going
to
continue
monitoring
it,
and
you
know
the
work.
Is
there
the
the
documents?
Are
there?
So
you
know
it's
it's
for
people
to
take
advantage
of
it.
A
Well,
I,
like
short
meetings,
and
I
guess
you
guys
want
to
go
to
bed
so
yeah,
you
guys
are
living
where
I
lived
when
we
were
in
bangkok
time.
So
if
there
is
nothing
else,
we
can
move
any
discussion
on
the
mailing
list
and
yeah
I
like.
Actually
I
feel
a
little
bit,
I
I
so
it
was
my
first,
my
first
research
group
and
also,
I
would
say
it's
the
first
one
that
I
close.
So
it's
you
know
we'll
be
nostalgic
at
this.
A
B
Let's
continue
on
the
list
for
the
next
few
weeks
and
hopefully
we'll
be
done
at
the
end
of
the
year.
So.
B
C
Goodbye
bye,
bye,
thank
you
and
I'm
sure
we'll
have
a
drink
to
mark
the
occasion
when,
when
we
eventually
meet
again
in
person.