►
From YouTube: 2022-05-04 Monthly Multicast W3C Community Group Meeting
Description
Notes here: https://docs.google.com/document/d/1eoGvNcbh26wUPEGZOHJWzd4Y1gKZIAUx3_0NWaghNwg/edit
Meeting series here: https://github.com/w3c/multicast-cg/tree/main/meetings
A
A
A
A
So
I
guess
the
the
bulk
of
what
else
was
on
the
agenda
was
just
kind
of
going
over
where
we
got
to
on
on
sort
of
getting
started
with
the
you
know,
the
specification
and
a
demo
that
will
that
we'd
like
to
run
I'm
really
happy
with
the
progress
thanks
everyone
who
worked
on
it.
That
was
it's
it's
refreshing
to
see.
You
know
a
bunch
of
check-ins
happening
and
it's
been
a
lot
of
work.
This
happened,
I
think
so.
That's
that's
great.
A
And
I
guess
what
do
we
do?
I
put
all
the
items
in
there
that
I
wanted
to
say
happened
so
yeah,
it's
been
productive
thanks
to
mac
leo
and
max
leo
and
kyle.
We've
got
a
bunch
of
check-ins
happening.
We
made
a
fork,
we're
you
know,
adding
stuff
in
there
we've
been
max
especially
has
been
really
helping
to
tighten
up
the
initial
draft
specification
dock
for
the
quick
extension
I'm
a
little
worried.
The
quick
working
group
is
gonna,
think
it's
too
complicated
and
they're
not
gonna
want
it.
A
I
think
I'm
intending
to
propose
it
as
experimental,
which
I
think
is:
okay,
oh
and
anything
else.
We
should
really
get
into
I'd
almost
like
to
just
sort
of
open
it
up
as
a
as
a
rest
of
the
working
session.
Unless
we
have
questions
like
things
that
we
would
that
we
would
next
address
in
the
next
working
session,
we
have
things
like
clarifying
what
the
demo
will
look
like.
A
I,
I
think,
getting
the
push
api
accepting
some
data
first
is
like
the
first
step
of
that,
but
but
we
can
just,
but
I
think
it's
something
that
can
proceed
in
parallel
as
soon
as
there's
something
that
can
forward
through,
like
it
doesn't
have
to
have
the
multicast
transport
part
working
in
order
to
have
a
useful
demo
app
that
runs
in
a
browser
that
can
receive
pushed
data
from
you
know
from
the
server
initiated
unidirectional
data.
The
way
we're
trying
to
to
send
so,
I
guess
yeah
kyle
max.
B
A
I
want
to
finish
the
frames
there's
like
still
four
or
five
of
them
missing.
I
think
I
did
all
the
control
frames
right
unless
the
count,
I'm
not
really
sure
what
distinguishes
a
control
frame
from
from
a
not
control
frame,
the
stream
boundary
might
be
a
control
frame.
I'm
not
sure.
I
think
it's
about
whether
it
goes
whether
it
contributes
to
the
to
the
flow
control,
because
it's
not
part
of
a
stream
or
something.
A
And
also
like
the
the
stream
boundary
frame
that
maybe
should
be
control,
I
thought
maybe
it
was
associated
with
the
stream
sufficiently
that
that
it
shouldn't,
but
anyway,
so
there's
still
some
more
frames
to
add.
So
I
was
going
to
finish
doing
that.
I
took
a
little
a
quick
little
break
to
to
take
a
look
at
the
at
the
push
command
because
because
leo
had
some
questions
and
was
that
a
reasonable
kind
of
here's,
something
that
kind
of
works
or
kind
of
does
something
I
wanted
to
get
that
integrated.
A
But
I
gotta
get
back
to
the
frames
and
finish
those
up.
I
think,
but
then,
after
that,
we
gotta
start
like
doing
logic
with
the
frames
or
something,
and
we
also
have
to
get
inbound
push
data
right.
So
those
are
kind
of
the
two
keys
for
getting
this
part
working.
But
then
the
other
piece
is
going
to
be
dependent
on
the
inbound
push
data
and
that
would
be
doing
something
in
a
web
transport
web
app
which
which
would
be
able
to
take
the
multicast
as
well
yeah.
B
E
B
A
A
A
A
B
A
So
it
sort
of
takes
it
outside
of
the
it's
like,
not
part
of
the
core.
I
think
where
the
sockets
are
maintained.
So
there's
like
it's,
it's
like
one
of
the
test
tools
is
sort
of
how
it's
structured
right.
So
the
client
itself
is
a
test
tool.
You
know
once
it's
inside
chromium,
then
it'll
be
something
something
totally
different
again
right.
So
the
idea
is
that
it's
going
to
be
like
most
of
the
quick
core
library
stuff
is
about.
A
You
know
once
you've
got
a
packet,
then
how
do
you
interpret
it
and
all
that
kind
of
thing
right?
But
then
they
do
include
some
drivers
and
there's
a
few
different
drivers
right.
There's
the
the
simple
server
and
the
e-pull
server
that
are
that
are
both
sort
of
treated
similarly
but
have
a
different
way
that
they
get
kicked
off
and
started
depending
on
which,
which
executable
you
build
or
you're
running
right.
A
A
C
C
A
C
C
A
C
Well,
no,
I
mean
you
know
a
pipe
is
a
natural
thing
to
to
use
if
for
for
for
blocking
stuff,
but
for
non-blocking
things
I
it
just
like
they.
There
are
so
many
weird
corner
cases.
I've
found
with
with
pipes
that
it's
it's
you'll
end
up,
you'll
end
up
with
with
perverse
like
you
know,
corner
case
behavior
and
that's
not
something.
You
want
a
server.
A
A
A
C
I'm
still
yeah,
I
mean
I'm
still
trying
to
figure
out
grpc
right.
It
may
be
that
there's
a
natural
way
to
do
this
with
that
that
doesn't
involve
proto
buffs.
It's
unclear
to
me
right
because
grpc
and
protobuffs
are
you
know.
Basically,
you
know
two
halves
of
the
same
thing.
So
so
if
it
turns
out
that
there
isn't
or
if
there
isn't
an
accepted
pattern
for
this
kind
of
thing,
or
if
the
pattern
is
hey,
you
should
open
up
a
socket
and
stream
the
data
over
then
we'll.
C
A
Let's
not
ftp
is
really
special,
okay
yeah,
I
guess
so.
It
looks
like
it
looks
like
my
appeal
for
use
cases.
I
don't
have
my
my
audience
here
yet
if
I
I'll
I'll
probably
send
an
email
then
to
to
people
like
eric
and
dom
and
see
if
I
can
get
them
to
contribute
just
a
you
know
a
few
paragraphs
about
like
why
it
would
be
helpful
for
them
and
if
you
think
of
anybody
else,
you
know
I
I
sent
something
to
ramp
already.
A
A
Oh,
I
did
yeah,
yeah
and
and
lucas,
so
sam
actually
made
some
some
good
comments.
Also
on
the
on
the
the
latest
spec.
The
answer
I
got
was
they
probably
won't
be
authors
on
this
one.
You
know
they're
they're
not
expecting
to
be
authors.
We,
you
know
that's
a
bit
of
an
independent
question
of
whether
we
end
up
collaborating
but
yeah
they're,
aware
of
it,
and
sam
has
been
commenting
on
the
on
the
multicast
on
this
multicast
extension.
A
A
A
A
So
I
guess
maybe
what
I
should
say
is
towards
the
end
of
this
month.
I'd
like
to
be
in
a
place
to
get
a
few
other
people
from
the
quick
working
group.
To
take
a
look,
I
think,
we're
you
know
we're
the
way,
we're
fleshing
it
out.
It's
going
pretty
well,
I
think
we've
made
a
lot
of
improvements
and
there's
there's
decent
stuff
there
they're
going
to
hate
how
complicated
it
is.
I'm
pretty
sure
it's
you
know
it's
like
10.
A
A
You
know
so
this
is
a.
This
is
a
pretty
heavy
extension.
You
know
in
terms
of
just
how
much
it
adds
to
the
functionality
and
things
that
you
have
to
parse.
That's
part
of
why
I
want
to
make
it
experimental.
I
think
it'll,
take
a
few
rounds
of
it'll.
Probably
take
some
operational
experience
before
we
can
say
with
confidence
that
it's
that
it's
good
the
way
it
is-
and
I
guess
that's
the
other
thing-
I'm
still
working
on
trying
to
get
a
few
events
done
with
multicast.
A
A
A
Probably
just
to
add
encryption,
the
way
ambi
does
it
or
not,
not
encryption,
just
to
add
the
integrity.
The
way
ambi
does
it
and
maybe
to
skimp
on
that.
For
for
the
first
couple
of
events,
I'm
not
really
sure
I
would
strongly
discourage
that
because
I
don't
I
don't
want
traffic
injected
really,
but
you
know
in
in
general.
I
think
this
will
be
better
received.