►
From YouTube: IETF112-TSVAREA-20211110-1430
Description
TSVAREA meeting session at IETF112
2021/11/10 1430
https://datatracker.ietf.org/meeting/112/proceedings/
A
B
A
A
This
is
the
notewell
you've
seen
this
probably
about
eight
times
already
this
week
and
many
many
times
before
it.
If
you
have
any
questions
about
it,
just
please
type
it
into
your
favorite
search
engine.
Basically,
you
know
this
covers
some
behavioral
rules
and
some
so
just
how
to
handle
intellectual
property
at
ietf.
A
I
think
in
other
working
groups,
there's
been
a
bit
of
an
emphasis
on
the
code
of
conduct
this
this
cycle,
we're
really
asking
this
is
not
usually
a
problem
in
tsp
area,
but
in
at
least
this
meeting,
but
you
know
just
treat
each
other
respect.
Please,
and
you
know
if,
if
we
find
advan
examples
of
of
unprofessional
behavior
as
as
leaders,
we
will
try
to
call
that
out
and
establish
that
is
not
the
norm
on
how
we
want
to
do
things.
A
So
this
is
the
agenda.
We
we're
going
to
have
a
talk,
but
it
fell
through
at
kind
of
the
last
minute,
so
you
are
likely
to
get
out
of
here
early,
and
I
encourage
you
going
to
gather
and
mingle
after
this
we're
just
going
to
run
through
the
regular
review
of
what
the
what
the
area
did
we'll
open
up
for
open
mic.
So
this
should
be
a
quick
one.
We're
not
gonna
have
a
jab
rescribe,
because
I
think
zahed
and
I
can
probably
manage
looking
at
jabra
as
much
as
needed.
A
Okay,
all
right,
here's
what's
going
on
in
working
groups,
I
think
that
the
three
interest
main
things
are
ian
sweat
is
stepping
down
from
ippm
and
marcus.
Ilar
has
already
joined
and
he
will
start
this
week.
Thank
you,
marcus
for
volunteering
and
thank
you
ian
for
your
contribution
to
the
working
group.
Similarly,
tram
is
well.
My
intention,
as
I
announced
on
the
list,
is
to
shut
down
tram,
there's
one
document
remaining,
which
is
kind
of
in
deep
freeze
right
now.
A
Frankly-
and
nothing
has
happened
as
we're
good
for
a
while,
so
the
draft
has
expired,
so
it's
sort
of
nowhere
right
now,
but
should
the
work
to
do
pmtud
and
tram
resume
that
work
will
occur
in
the
tsvwg
working
group
and
tsvwg
will
have
custody
of
all
the
tram
rfcs
so,
like
I
said,
I've
announced
this
on
the
relevant
lists.
If
you
have
any
problems,
please
raise
them
at
open
mic.
I
plan
to
push
the
button
immediately
after
this
meeting
and
formally
close
it.
A
Cubic
is,
is
in
work,
group
last
call,
and
I'm
very
much
looking
forward
to
having
a
more
modern
connection,
control
formally
standardized,
and
then
there
are
a
number
of
reasons
that
we're
looking
to
bust
5681,
which
is
kind
of
the
core
loss,
recovery
and
document
for
tcp
and
we're
looking
for
authors
at
this
time.
So
if
this
is
interesting
to
you,
please
contact
the
tcpm
chairs.
B
We
have
been
putting
up
a
new
charter
for
isb
internal
review
when
there
were
some
blocks,
and
now
we
work
through
that
with
those
things
I
think
the
blocks
were
just
lift
off,
so
it
will
progress
then
or
next
phase,
and
the
focus
of
this
returning
is
more
like
doing
some
ops
and
management
work
and
addressing
work
along
with
the
transport
related
issues
that
they
have
been
doing.
I
mean
this
is
an
interesting
time.
C
B
Dtn
because
people
are
deploying
and
then
we're
getting
lots
of
input,
how
it
works
and
if
it's
before,
I
think
business
as
usual,
mostly
working
on
the
security
document
so
far,
and
also
this
rdm
and
version
2
documents-
quick,
I
think,
just
came
from
a
lot
of
us-
came
from
quick
working
groups,
so
you
already
know:
what's
going
on
there,
the
there
are
traps
in
the
edit
review,
I'm
going
through
them.
Those
are
very
good,
well
written
documents.
B
So
far,
I've
seen
decreasing
just
completed
the
working
last
call,
and
I
think
there
was
some
discussion
we
we
heard
in
the
today's
quick
meeting
about
multipath
week,
armcad
after
a
long
time
taking
up
work
that
I
think
that
is
the
last
working
document
working
document
to
work
with
this
is
about
how
you
send
the
feedback
taps.
I
will
say
business
as
usual.
The
taps
architecture
document.
When
past
the
working
last
call
and
then
interface
documents
is
working
lost
call.
So
that's
it
so
far
from
my
working
groups.
A
A
couple
of
other
things,
first
of
all,
I
neglected
to
thank
the
tram
chairs,
gonzalo
and
simone
for
your
actual
frankly
tram
predates
my
deep
involvement
in
the
area
as
a
whole,
but
you
know
obviously
there's
a
lot
of
documents
that
came
out
of
tram
and
they
they
were
the
ones
that
brought
it
along.
So
thank
you
for
your
contributions
to
the
itf.
A
I
I
also
want
to
talk
a
little
about
the
last
little
phrase
down
there.
There's
a
lot
of
multipath
work
going
on
in
the
area.
All
of
a
sudden,
you
know
mptcp
closed
a
couple
years
ago.
There
are
some
sctp
proposals
and
by
multipath
I
mean
sending
data
concurrently
over
multiple
paths.
Not
you
know.
Failover,
there
are
some
http
drafts.
That's
whose
status
is
in
seriousness
is
not
frankly,
certain
and
tsvwg
has
adopted
mpdccp
and
based
on
what
just
happened
in
quick,
it
looks
like
they're
likely
to
adopt
mp
quick.
A
I
I
think
those
drafts
are
all
properly
housed
in
the
individual
protocol
places.
That
said,
there
are
a
lot
of
common
problems
in
multi-path
like
scheduling
and
congestion
control.
That,
then,
my
view
are
not
really
resolved,
and
I
I
think
now
that
we,
I
think
quick
in
particular,
is
an
excellent
experimental
platform
for
for
multi-path
experimentation,
because
it's
likely
to
get
through
the
internet
and
like
we're.
A
C
Hey
thanks
yeah,
just
just
on
that
note.
The
the
the
presentation
that
was
just
given
to
the
quick
working
group
was,
you
know
effectively
a
very
small
core
of
what
multipath
quick
could
could
be
from
a
protocol
level
to
help
deliver
some
of
the
use
cases
and
a
lot
of
what
you
just
mentioned,
like
scheduling
and
stuff,
is
like
out
of
scope
but
clearly
needs
to
be
done
somewhere,
maybe
in
parallel,
maybe
somewhere
else.
I
don't
quite
know
so.
A
Yeah
zach
and
I
will
have
another
conversation
with
colin
and
if,
if
there's
a
lot
of
work
sitting
around
and
we'll
put
out
a
call
to
see,
if
there's
a
work
staying
around
out
in
the
wings
that
it's
ready
to
go
in
a
group
somewhere
and
then
a
lot.
Lastly,
sctp
there
are
a
lot
of
scp
drafts
flowing
around
tsvdwg.
A
Apparently
again,
it's
not
100
clear
how
many
people
how
many
of
those
are
going
to
be
adopted,
but
I
I
do
understand
that
there's
sort
of
an
infinite
stream
of
proposals
that
the
tsvwg
is
working
through
and
that
is
potentially
grounds
to
do
a
working
group
just
to
do
all
this
sctp
stuff.
And
I
think
the
question
is
how
much
that
work
benefits
from
being
in
the
tcwg.
A
Tcpg
is
obviously
quite
loaded
with
stuff.
So
if
it's
just,
if
they're,
just
a
bunch
of
people
sitting
on
their
hands,
while
the
until
the
sct
people
stop
talking,
then
maybe
it
makes
sense
to
be
its
own
group.
But
if
there's
a
lot
of
valuable
cross-fertilization
that
happens,
maybe
it
should
stay
where
it
is.
So
I
would
welcome
your
input
on
that.
As
well,.
A
Okay,
not
not
the
most
productive
interval
in
terms
of
documents,
but
there's
a
ton
of
things
sitting
in
the
ad
key.
It's
a
various
stages
of
a
d
and
is
g
of
l.
So
some
for
outside
us
and
some
of
that's
on
authors,
responding
to
feedback.
But
regardless
we
did
ship
one
thing
from
dtn
the
default
security
context
and
two
things
went
out.
The
rfc
door
wait:
90
40,
I
think,
was
before
anyway,
regardless
1997.
A
Of
course,
congratulations
to
al
and
his
co-authors
on
the
ip
capacity
metrics
draft,
which
was
spent
forever
in
rc
head
for
various
reasons
and,
of
course,
there's
a
bunch
of
stuff
sitting
in
the
queue.
That's
that's
waiting
on
things
most
notably
http
3,
but
certainly
a
lot
of
other
items
as
well.
You
can
see
at
the
bottom
there.
A
Tsv
art
review
team
discussion,
so
the
tsv
area
review
team
helps
us
in
our
av
reviews
by
by
like
highlighting
transport
issues
and
drafts
from
across
the
itf
if
they
are
judged
to
have
any
transport
implications
at
all.
So
thank
you
to
the
viewers
for
doing
these
reviews.
I've
got
there
in
parentheses,
the
number
of
reviews
they
had
to
do
in
the
last
cycle
since
ietf
111.
A
So
I
think
you
know
we're
certainly
interested
in
having
more
volunteers
and-
and
I
think
that
number
indicates
that
the
load
is
not
huge,
that
we
ask
people
to
review
less
than
one
draft
per
cycle.
So
thank
you
to
volunteers
for
having
a
big
enough
pool
to
make
the
workload
light
and
if
you
would
like
to
join,
I
think
it's
a
great
way
to
get
a
window
into
some
of
the
other
things
going
on
in
the
itf
that
are
of
interest.
So.
B
A
D
D
I
I
think,
I
think,
I'm
seeing
other
impacts
of
multi-path
that
that
could
come
up.
You
know,
I
think
one
of
the
things
I've
been
talking
about
for
a
bit
is
the
thing
about
the
difference
between.
Maybe
maybe
I
should
be
describing
this
as
low-level
scheduling
decisions
versus
high-level
strategy
decisions.
D
B
A
John,
at
times,
has
expressed
a
little
skepticism
that
he
has
the
right
skill
set
in
that
group
to
to
really
review
multi-path
condition
control.
So
if
it,
if
he
wants
to
take
it,
I'm
not
going
to
try
to
rip
it
out
of
his
hands.
But
I
think
that
I
think
the
point
that
I
would
like
to
make
is
is
that
we
now
have
four
multipath
transports
in
some.
Some
states.
A
B
A
B
B
D
Yeah,
I
mean
I'll
I'll
I'll,
just
say
one
more
thing
and
then
I'll
shut
up
and
turn
my
video
off,
but
the
thing
we
did
with
hip
in
the
past,
where
you
know
the
research
you
know
it
was.
It
was
the
same
problem,
but
this
the
research,
the
research
topics,
had
a
had
a
research
group
and
a
and
the
stuff
that
had
matured.
The
engineering
was
being
done
in
the
ietf
with
engineers
and
things
like
that.
But
I
mean
there
was
overlap
between
the
two
groups
and
things
like
that.