►
From YouTube: TSVArea WG Interim Meeting, 2020-03-20
Description
TSVArea WG Interim Meeting, 2020-03-20
D
E
C
C
B
B
A
A
C
C
B
C
B
Well,
I'll
take
over
what
bag
is
talking
so
I'm,
probably
the
obvious
salient
event
for
the
area
is
we
are
changing
over
a
DS.
Mira
has
been
at
this
for
what
two
years,
three
years,
four
years,
okay
longer
than
I've,
become
you
at
ESD
area
and
obviously
has
put
a
ton
of
energy
and
insight
and
knowledge
elephants
into
everything,
she's
done
for
this
working
group
and
is
done
area
rather
in
her
working
groups
and
really
across
the
ITSI
ESG.
B
C
And
as
mechanism
here,
I
can
mean
thanks
as
Megan
here
I
can
welcome
Martin
it's
great
to
have
you
like
I'm,
happy
to
help
to
hand
over
to
you,
because
we've
been
working
a
lot
together
and
last
couple
of
weeks
and
I
think
we
will
do
great
I
hope
you
have
everything
you
need
now
and
it's
yours,
okay!
Well,.
B
Okay
moving
on
we'll
just
continue
in
Magnus's
absence
for
a
little
while
here,
okay,
so
this
is
the
very
busy
slide
that
it
kind
of
has
a
quick
one-line
summary
what's
happening
across
the
area.
I
just
like
to
call
all
tensions
of
the
new
people
we
have
coming
in
in
sweat,
David,
Novak
and
Lucas
pardhu
have
taken
over
as
working
group
chairs
at
various
groups,
as
you
can
see
there,
and
shortly
spencer
Shepler
bill
Cerveny
and
Brian
Trammell
will
be
stepping
down
in
their
respective
group
chair
positions
since
they're
now
replacements
for
them.
B
B
Otherwise,
you've
had
to
be
charter,
ins
and
MPD.
Spee
is
now
closed.
It
closed
earlier
this
week
as
a
draft
enter
the
RFC
edit
review
final
draft,
so
TCM
has
been
very
suddenly
retarted
to
handle
future
mptp
issues
and
then
we've
changed
the
quick
charter
as
their
work
on
the
base
drafts
lines
down.
There
Turner's
now
changed
to
cover
a
sort
of
the
next
wave
of
extensions
and
so
forth
that
have
been
cooking
for
a
while
now.
B
Finally,
in
general,
I
am
taking
on
uros
working
groups
and
Magnus
is
just
keeping
his
as
you
might
expect.
The
one
difference
is
that,
partly
because
mptp
is
winding
down
I'm
going
to
go
ahead
and
take
TS
vwg
from
Magnus
take
to
balance
the
load
a
little
bit
when
it
comments
or
questions
about
this
slide.
G
H
H
B
I've
already
gotten
synched
a
little
bit,
so
that's
I've
already
got
it
on.
H
I
B
Okay
list
Thank
You
Colin,
so
we've
been
somewhat
more
productive
in
terms
of
our
C's
publish
than
in
the
previous
interval.
We
had
none
between
105
and
106
and
since
106
7
things
have
gone
RFC,
as
you
can
see
there.
Also
six
drafts
have
entered
the
RFC,
editor
queue
and
we
have
seven
they're
sitting
around
and
the
RFC
editor
queue
since
before
106.
A
fair
number
of
them
are
related
to
a
big
of
our
block
and
by
a
bunch
of
RTC
web
stuff.
So
some
of
them
in
there
for
quite
a
while.
C
B
Okay,
review
team
update,
so
there
have
been
a
few
there,
gonna
be
a
few
changes
as
we
come
into
IETF
107
here,
obviously
I'm
stepping
down
as
I
from
the
review
team
after
a
very
short
tour
as
a
re
director
and
Mira
has
has
volunteered
to
stay
to
come
back
to
the
view
team
as
she
steps
up
from
being
an
ad,
furthermore,
of
art
in
Finland,
who
was
on
the
triage
team
for
quite
a
while
is
having
to
step
down
due
to
some
some
other
commitments.
B
But
you
know
we're
always
looking
for
more
volunteers.
For
this.
It's
it's
kind
of
a
factor
of
one
of
those
things.
We're
just
many
hands,
make
light
work.
You
can
see
here
that
people
do
one
or
two
draft
reviews
between
each
ITF
meetings.
So
it's
really
not
a
particularly
burdensome.
Ask
it's
good
opportunity
to
see.
What's
what
else
is
going
on
in
ITF
dipping
your
toast
and
some
other
some
other
areas.
So
if
you're
interested,
please
send
email
to
PSV
ADEs
and
we
can
get
you
on
the
a
team
and
thank
you
to
everyone.
B
B
Okay,
here
are
some
particulars,
so
there's
a
very
abbreviated
schedule
in
ITF
107
week
itself.
Is
she
decided
to
limit
the
agenda
to
slowly
boss
and
new
working
groups?
They
don't
have
established
ways
of
working
to
give
them
sort
of
maximum
oxygen
to
get
rolling,
whereas
other
working
groups
will
meet
in
different
weeks
in
a
minute.
So
there
are
no
actual
transport
area
groups
or
boss
meeting
in
during
IETF
week.
However,
there
are
four
things
you
may
find
interesting
for
of
all
online.
B
If
time
allows
that
will
be
a
talk
about
SRT,
which
is
a
udp-based
session
sip
like
protocol,
that
is
I,
guess
already
been
deployed
in
South
Korea,
and
there
is
some
overlap
with
rip
teas
that
has
gone
to
art
and
I'll
talk
about
rip
tea
in
a
second
but
there,
obviously,
if
it
sits
straight
over
UDP,
so
you
might
imagine
there
quite
a
few
transporting
elements
to
that
proposal.
So
that
may
interest
a
lot
of
people
here.
Mira.
Was
there
something
else
in
our
dispatch
that
we
wanted
to
call
attention
to.
B
Then
the
other
three
items,
if
you
love
quick
as
much
as
David's
Ganassi
does,
then
there
are
three
rebuffs.
And/Or
working
groups
in
other
areas
that
are
probably
seriously
involved,
quick,
others
mask
ripped
II
is
is,
as
I
already
mentioned,
is
kind
of
a
sip
ish
a
follow
on
sip
kind
of
effort.
That's
not
super
well
defined
right
now,
frankly,
but
it
is
certainly
looking
at
quick
or
hp3
as
possible
vehicles
for
what
they're
doing
so.
B
B
Okay,
so
there
are
seven,
there
are
seven
working
groups
who
are
planning
to
do,
have
tentative
plans
or,
in
a
couple
cases
firm
plans
to
do
an
interim
meeting
over
the
next
thirty
days
or
so
after
ITF
taps
is
a
regular
rhythm
of
working
group
meetings
and
those
will
continue
an
arm
cat
and
tram.
We're
gonna
sit
this
cycle
out.
I
would
encourage
you
to
pay
attention
to
the
working
group
mailing
lists,
and
also
you
can
go
to
that
link
there
on
data
tracker.
B
A
G
So
I,
just
I,
think
that
saying
that
were
taps
will
continue
with
its
regularly
scheduled
meetings
may
be
a
little
bit
inaccurate
and
I.
G
Don't
want
to
confuse
anybody
that
we
had
been
going
on
roughly
a
monthly
cadence
for
taps
virtual
interims,
and
our
intention
is
to
continue
that,
but
the
meetings
aren't
actually
scheduled
yet
so
I
don't
want
people
to
go
and
look
for
actual
dates
and
times
we're
trying
to
come
up
with
the
time
for
in
April,
and
we
haven't
landed
on
that
yet
so
so
just
want
to
clarify
that
and
I
think
that
addresses
basically
the
the
report
here.
A
little
bit
of
substance
is
that
we
did
a
thorough
review
of
the
taps
architecture
document.
G
It's
pretty
much
landed,
but
we're
going
to
keep
the
document
open.
While
we
do
the
interface
specification
and
get
implementation
experience,
and
that
gives
us
the
opportunity
to
go
back
and
revise
this,
it
turns
out
that
we
learned
stuff
through
that
process.
I'd
say
right
now:
we
are
in
the
final
stages
of
deep
review
and
revision
of
the
interface
specification
I'm
a
little
bit
behind
on
my
reading.
So
I
don't
know
exactly
where
we
are
yet,
but
I
think
that
this
is
soon
will
be
a
good
we're
going
to
do.
B
J
At
the
moment
there
doesn't
seem
to
be
any
dinner
burning
enough
to
require
that
so
I
think
we
are
at
the
moment
content
to
work
on
github
and,
to
a
lesser
degree,
by
email
we
had
also
before
you
know
everything
got
shut
down
and
talked
about
that
we
might
physical
interim
Eve's
to
virtual
in
terms
weren't
gonna
be
enough.
That
is
I,
think
we
can
scratch
out
highly
unlikely
and
basically
say
that
that
won't
happen,
certainly
not
the
formal
good
and
the
quick
dispatch
stuff
that
we
were
planning
on
doing
in
an
extra
hour.
J
J
Yeah
so
I
think
we're
gonna
do
a
remote
interrupt
whenever
we
get
the
next
drafts
out,
I'll
send
a
doodle
poll
and
we
still
have
a
bunch
of
stacks
that
aren't
on
27.
Yet
so
it
doesn't
seem
super
urgent.
On
the
other
hand,
we
don't
want
to
hold
anybody
back.
Who
wants
to
move
faster,
so
I
thought
that
is
going
to
happen.
So
I
think
the
interrupts
are
gonna,
keep
going
forward
and
they're
going
to
be
virtual
for
the
foreseeable
future,
I
think
and
we
can
have
them
as
frequently
as
people
like.
B
F
F
We
have
a
tentative
schedule
for
working
group.
Last
calls,
as
you
see
here,
the
rack
one
has
already
started.
We
arrived
in
four
weeks
since
I
wasn't
sure
what
the
right
amount
of
time
is,
whether
the
ITF
is
considered
to
being
happening
happening
or
not.
We
will
run
them
most
likely
one
after
the
other.
We
would
like
to
have
a
virtual
Entering,
not
at
the
date
which
is
currently
planned,
but
more
mid
or
end
April.
That
would
be
most
suitable
to
discuss
potential
outcome
of
the
working
group
last
calls
and
to
progress.
C
F
H
Haven't
helped
us
TSP
WG
is
actually
a
tale
of
two
working
groups.
Anybody
who's
watched
list
has
noticed
that
the
whole.
What
do
we
do
with
the
fourth
easy-easy
encode
point
for
s,
SC
et
cetera,
can
consume
all
of
the
time
and
effort
invested
in
it.
We
think
we
need
an
interim
meeting
for
that,
but
we
are
skeptical
chairs
that
we
can
make
any
decision
without
a
face-to-face
meeting
so
that
one's
going
that
one's
going
to
Madrid.
Then
we
need
a
second
interim
II
to
active,
actually
get
something
useful
done.
H
Try
to
cover
everything
else.
Those
it
says
here,
there's
a
lot
of
everything
else
in
TS,
vwg
things
that
will
likely
get
punted
out
of
intermediate.
All
the
way
to
IHS
108
are
the
first
bullet
on
ECM
decisions.
Udp
options
can
be
deferred.
While
we
try
to
get
some
other
stuff
done.
There's
a
couple
of
nap
drafts
that
in
one
case,
SCTP
net,
I
think,
is
making
progress.
We
need
to
finish
that
off
and
the
other
woman
is.
H
D
Ip
p.m.
yeah,
so
I
probably
should
have
sent
slides.
We
have
a
proposed
agenda
for
this
now
we're
going
to
try
and
do
a
90
minutes
virtual
interim
at
1500
UTC
that
is
sort
of
a
Fiat
noon.
Time
zone
pain
slot
for
the
key
contributors
like
just
looking
at
where
they
are
not
yet
confirmed
that
on
the
list.
H
B
K
Brian
Pulaski
here,
Dave
Novick,
can't
make
the
call.
Today
we
got
the
interim
agendas
out.
They
were
sent
out
by
the
IETF
this
morning.
Before
this
meeting,
we
basically
moved
our
two
days
of
meetings.
From
now,
we
scheduled
meeting
to
the
interim
meetings,
took
the
agendas
right
across
and
they're
published.
Now
nothing
important.
A
A
B
C
I
C
We
have
the
chair,
so
some
of
the
juiciness
so
for
memory,
we're
still
discussing
if
it
makes
sense
or
not
because
like
much
part
of
the
value,
is
to
have
actually
everybody
in
the
room
and
have
some
discussion,
and
we
probably
have
some
people
who
wouldn't
be
able
to
present
remotely.
So
it's
not
here
for
my
budget
so
for.
D
D
I
I
On
the
basis
that
this
was
mostly
the
ani
P
prize-winning
talks
and
the
goal
is
to
get
the
prizewinners
involved
in
the
meeting,
so
we
were
hoping
we
could
just
postpone
them
to
a
later
later
meeting
later
this
year.
That
is
looking
less
and
less
likely.
So
I
guess
we'll
probably
be
scheduling
those
talks
at
the
meeting
or
the
Bangkok
meeting
as
virtual
talks,
we'll
see
what's
happening
there.
C
I
I
C
I
C
Yes,
so
we
we
were
deciding
to
have
this
Tierra
meeting
to
at
least
give
a
short
update
before
the
next
week,
also
to
everybody
and
to
like
give
us
an
opportunity
to
test
this
ourself
in
this
setup,
but
also
to
other
chair
to
kind
of,
if
everybody,
the
the
possibility
to
test
the
setup
with
a
meeting
which
is
like
less
critical,
I'd
say
so
also,
if
you
have
any
questions
about
the
next
week
or
any
interim
meetings
or
how
to
how
to
run
this,
virtually
we
can
take
that
as
well.
Okay,
try
to
take
you.
G
Yeah,
okay,
I
just
wanted
to
say
that
I
think
that
the
interims
that
taps
has
been
running
online
have
been
working
very
effectively
for
one
thing:
that
I
think
that
you
end
up
with
better
dialog
everybody
sort
of
like
interacting
at
the
same
level
that
we
don't
have
a
represent
on
mics
and
I'm,
not
exactly
sure
what
of
the
many
differences
from
an
IETF
meetings.
So
I
actually
think
this.
This
plus
the
Oh
encouragement,
possibly
to
have
more
interims.
G
G
L
Yeah
thanks,
so
we
are
gonna
use,
just
a
regular
WebEx
meeting
for
the
plenary
and
see
how
it
goes.
We
didn't
have
a
lot
of
options
on
on
short
notice,
but
it
will
be
useful
to
get
people's
feedback
because
something
like
a
very
large
working
group
meeting
or
the
plenary
is
not
exactly
what
the
regular
WebEx
meeting
product
is
designed
for,
and
there
may
be
other
options
as
we
go
forward
with
more
virtual
meetings
in
the
future.
L
G
C
Also
I
wanted
to
add
a
point
about
Aaron's.
Are
you
comment
about
tips
and
or
meetings,
so
I
think
the
one
of
the
reasons
why
those
meetings
were
or
Wallace,
because
in
Terps
we
actually
look
at
the
issue
tracker.
We
use
github
and
we
go
like
one
by
one
and
we
have
a
chat
and
these
kind
of
things.
So
it's
very
different
dynamic
than
the
physical
thing
which
may
or
may
not
be
good
for
your
working
group.
C
But
it's
definitely
something
to
consider
that
if
you,
if
you
actually
want
to
use
the
interim
to
run
it
the
same
way
as
you
would
do
the
physical
or,
if
you
actually
want
to
establish
a
different
structure
for
it,
we're
getting
more
experience
in
this
in
this
area.
It's
probably
also
something
good
and
we
have
David
on
the
queue
I'm.
H
Going
to
come
at
the
TSB
WG
held
a
WebEx
interim
meeting
before
all
as
if
sudden
started
and
I
think
the
reflection,
a
reflection
as
a
chair
is
that
it
worked
very
well
for
information
sharing.
But,
as
you
saw
in
in
our
summary
you're
skeptical,
that
will
work
well
as
a
forum
for
making
a
difficult
decision.
H
C
M
Just
gonna
say:
I
was
just
gonna
ask
David
if
he
could
imagine
a
difficult
question
that
was
not
ECT,
one
related,
because
I'm
really
having
a
hard
time,
imagining
that
that
is
a
normal,
a
normal,
a
a
a
difficult
question.
That
is
the
normal
level
of
difficult
that
we
would
talk
about
at
the
IETF.
Well,.
H
Spencer's
funny
you
should
ask
I,
think
I've
just
kicked
the
can
down
the
tracks
on
some
RFC
3168
revision
questions,
which
is
whether
to
reopen
3168.
You
go
fix
of
all
things
easy
and
for
fragmentation.
That's
not
going
to
be
easy,
too
easy
to
deal
with
either.
Considering
that
there's
a
docking,
artsy's,
Enders
cube
and
strong
discourages
fragmentation.
So
I.
B
All
right,
well,
I,
I
think
we
all
hope
that,
wherever
in
whatever
state
of
lockdown
you
are
they
it's
comfortable
for
you
reasonably
and
we'll
see
you
out
on
these
interim
meetings
and
then
hopefully
in
Madrid.
Thank.