►
From YouTube: 2022-03-02 Monthly Multicast W3C Community Group Meeting
Description
Notes here: https://docs.google.com/document/d/1dcvvcHm59bqO5QWP-sfjclW6HhdPQt9L9g0UNJfUKR8
Meeting Series: https://github.com/w3c/multicast-cg/tree/main/meetings
A
Okay
right
so
recording
has
started.
Okay.
Welcome
thanks
for
coming.
I
was
hoping
a
few
more
people
would
start
showing
up
to
these
because
max
is
is
coming
right
along
and
there
was
another
one
or
two
chris
sent
his
his
regrets,
chris
leonard,
so
he
had
a
conflict
today
and
couldn't
make
it.
But
let's
see
and
and
gaian
has
been
talking
on
the
on
the
mbond
list,
but
I
guess
didn't
make
it
today,
anyway,.
A
Let's
see
so,
I've
got
these
notes
with
a
couple
of
thoughts.
I
wanted
to
go
over
anything
else.
Anybody
thinks
I
should
speak
to
or
questions.
B
Is
there
the
the
you
know,
I
haven't
done
anything
with
the
with
the
multicast
security
document
anytime
recently,
what,
since
I,
since
I'm,
not
going
to
be
in
vienna
and
on
vacation,
so
I'm
not
really
going
to
be
attending
any
working
group
sessions,
except
for
my
own?
Is
there
anything
specific
that
you
want
me
to
do
prior
to
113.
A
Actually,
just
is
it
expiring,
I
don't
know.
B
A
I
think
just
keeping
it
alive
is
probably
enough
for
now.
I
I
do
think
so
the
so
I
started
that
that
quick,
multicast
document,
it's
like
barely
it,
has
an
abstract
that
I
think
might
be
okayish
with
just
a
few
more
revs
and
and
then
the
the
intro
that
is
probably
too
rambly
to
stick
and
one
and
and
basically
all
that's
in
there.
Yet
is
the
pointer
to
that.
A
To
that
security
considerations,
doc,
plus
the
outline
which
is
kind
of
roughly
based
on
on
the
multi-path
quick
kind
of
trying
to
cover
roughly
what
they're
trying
to
cover
and
adapt
it
to
what
we're
gonna
need
for
the
multicast
part.
I
think
it's
gonna
wind
up
being
a
fairly
long
document
in
the
end,
there's
there's
a
lot
of
sections
and
a
few
of
them
are
gonna,
be
a
bit
complicated,
but
but
I
have
kind
of
a
start
at
getting
somewhere
there.
A
I
think
the
target
is
to
have
something
reasonable
to
present
in
philadelphia.
I.
A
Anything
crazy.
I
was
gonna,
be
there
for
vienna
too,
but
unfortunately,
crazy
is
craziness
happened,
yeah,
so
yeah,
I'm
I'm
hopeful
that
can
go
somewhere.
I
think
that
there's
a
lot
of
advantages.
I've
been
talking
with
a
few
potential
collaborators.
I
don't
have
a
an
okay
from
them
yet
to
to
publicly
say
exactly
who
they
are.
But
but
you
know,
there's
there's
a
few
reasonable,
guesses
and-
and
you
might
be
right.
A
That
would
be
awesome,
but
no
no,
the
now
actor
is,
is
not
one
of
them
yet,
but
yeah
we're
we're.
A
This
approach,
I
think,
has
a
lot
to
recommend
it,
namely
that
it's
invisible
to
the
application,
which
is
actually
a
big
advantage.
A
I
think
this
is
has
a
lot
of
potential
to
to
get
somewhere,
assuming
we
can
kind
of
clear
the
security
hurdles
appropriately
and
I
think
the
the
security
consideration
stock
is,
although
we
didn't
get
a
lot
of
engagement
on
that,
I
do
think
it's
gonna
be
critical
for
for
having
it
all
written
down
like
what
we're
aiming
to
achieve
here
and
being
able
to
compare
that
against.
You
know
what's
reasonable
and
what
the
the
quick
proposal
actually
does.
B
A
A
This
is
not
lucas's
dock.
This
kind
of
takes
things
down
a
layer,
so
lucas's
dock
was
was
working
at
the
application
layer
on
on
h3,
and
it
was
you
know,
so
the
the
way
that
it
was
gonna
do
the
the
so
it
used
alt,
service
and
h3
push
and
said
that
you
know
these
are
required
elements
and
had
a
sort
of
you
know,
cross
layer,
the
the
alt
service
sort
of
gave
information
about
the
multicast
stuff,
and
there
was
no
authentication
at
the
transport
layer.
A
It
was
only
at
the
app
layer
with
the
h3
objects
that
were
transported,
so
it
was
that
one
was
aimed
only
at
segment
transfer.
So
the
the
new
approach
is
operating
in
the
quick
transport
layer
instead,
so
it'll
be
using
quick
frames
to
do
the
server
to
client
advertisement
that
there's
a
separate
multicast
stream.
It'll
use
quick
handshaking
instead
of
instead
of
the.
A
I
think
it
was
all
service
and
just
sort
of
optional
for
the
client
to
use
it
in
terms
of
like
how
the
client
would
decide
whether
to
attempt
a
multicast
stream
join
in
the
in
lucas's
doc.
A
And
so
there's
there's
some
key
differences
here,
and
the
idea
is
that
it's
basically
just
it's
almost
like
a
an
alternative
path
for
for
a
server
for
a
generic
server
to
client
data
stream.
So
it
could
carry
h3
push,
but
it
can
also
carry
datagrams.
It
can
also
carry
anything,
that's
appropriate
for.
B
A
A
About
it,
yeah,
okay,
cool,
so
it's
not
and
it's
so
it
it
is
coupled
to
the
to
the
individual
unicast
streams
right
and
those
individual
unicast
streams.
I
think
our
intent
is
to
start
with
just
like
it's
gonna
do
multi-path
packing
on
the
unicast
path.
That's
and,
and
just
do
the
the
just
like
multipath.
B
A
B
A
Is
the
intent
is
the
intended
operation
here
you
know
so
there
will
be.
So
I
think
there
are
several
unique
things
about
this
about
this
architecture
that
are
going
to
need.
You
know
defining
in
this
document.
Well,.
B
One
is
one
that
I
can
think
of
immediately
is
is
that
the
multicast
source?
B
B
You
know
for
the
unicast
traffic
right,
so
they're,
somehow
gonna
have
to
share
state
cdn
nodes
are
going
to
need
to
know,
are
going
to
need
to
have
access
to
the
same
stream
at
the
you
know,
to
the
same
stream
of
quick
packets
right,
the
same
sequence,
numbers,
etc.
Okay,
yeah.
That
seems
like
a
complicated
problem.
A
So
it's
complicated
operationally
a
little
bit
and
we'll
need
to
have
probably
a
demo
server
that
can
do
that
kind
of
fan
out.
A
You
know
where
there's
a
where
there's
an
upstream
source,
that's
providing
the
stream
of
probably
the
whole
stream
of
packets,
but
maybe
maybe
in
some
cases
it
can
just
send
the
authentication.
A
You
know
the
packet
hashes
that
we'll
be
using
for
for
because
the
the
packet
hashes
will
be
coming
on
the
on
the
main,
quick
stream
in
a
you
know,
a
sequence
of
frames
for
that
until
we
like
once
again,
I
think
we
can
eventually
transition
to
to
doing
the
other
thing
in
the
in
the.
A
The
one
that
the
one
that
you
wrote
about,
what
was
it
called
the
women.
B
A
Yeah
alta,
I
think
we
can
eventually
transition
the
authentication
stream
to
use
alta,
but
we're
going
to
start
with
just
there's
an
authentication
stream.
That's
packet,
hashes,
coming
in
the
coming
in
the
unicast
channel
and
yeah
that.
A
It's
about
30x,
so
sorry.
B
A
A
A
So
30x
is
nothing
not
to
be
sneezed
at,
so
so
that's
the
plan.
It
would
be
awesome
if
I
could
get
something
running
by
philly
in
july.
I
don't
know
if
that's
going
to
happen,
but
but
that
would
be
a
stretch
goal
I
would
say,
and
the
and
the
main
goal
here
would
be
to
just
have
the
doc
written
with
with
enough
to
to
be
talked
about.
A
A
So
that's
the
intent
with
that
thing.
I
think
I
think
that's
the
main.
A
The
main
thrust
of
what
we're
gonna
try
to
to
make
happen
this
time.
I
I
think
I
think,
that's
the
the
best
path
anybody
has
suggested
or
thought
of,
and
several
people
seem
to
think
that
it's
got
some
potential,
so
yeah
ecker
will
still
think
it's
a
bad
idea,
I'm
afraid
so.
A
We'll
still
have
to
have
that
discussion
that
they
didn't
want
to
have
just
because
nobody's
interested
if
we
can
get
people
interested
but
yeah,
and
on
that
front,
lenny
offered
to
have
mbo
and
d
make
a
statement
or
request
or
something.
I
think
I
think
it
might
make
sense
for
mbo
and
d
to
officially
request
quick
to
consider
this
or
something
I'm
not
sure
whether
we
should
do
that
in
vienna
or
just
in
in
philadelphia
as
as
a
precursor
there
but
yeah.
We
need
to
you
know
the
point.
A
You
know
it's
a
it's
critical
to
the
deployment
like
to
the
incentive
structure
for
making
multicast
successful
to
to
be
able
to
offload
http
with
multicast,
and
we
have
a
proposal
that
that
is
aiming
to
do
this.
A
We
will,
at
that
point,
have
a
proposal
aiming
to
do
this
and
therefore,
please
do
give
this
through
consideration
like
just
I
don't
know
how
that's
going
to
land,
but.
B
So
I
wonder
so
I
don't
know
you
know
you,
you
said
you
you
don't
you
know.
You've
you've
been
talking
with
some
people,
but
you're,
not
you're,
not
at
liberty,
yet
to
reveal
who
they
are,
but
I'm
just
wondering
if,
if
any
of
those
people
are,
are
you
know
kind
of
big
wigs
from
the
from
the
development
of
quick
and
if
not,
if
it
makes
sense
to
try
and
find
some
of
those
folks
and
get
them?
B
A
B
A
Sure
that's
a
good
idea,
and-
and
I
will
I
think,
it's
going
to
take
having
a
sane
doc
to
get
them
to
look
at
it,
but
I
do
hope
at
least
like
someone
like
martin
will
actually
read
it
and
give
some
feedback.
You
know
his
his
feedback
during
sex
dispatch
was.
We
need
a
proposal
before
we
can
really
talk
about
this
in
the
with
the
security
considerations.
So
I
I
I
feel,
like
I'm
essentially
directly
following
up
on
what
what
he
said.
Well,.
A
Yeah,
well,
you
know,
I,
I
don't
think
anybody
quite
did
that
they
just
said
that
nobody's
interested.
So
we
shouldn't
bother.
I
guess
that's
on
it
anyway.
A
But
yeah
having
a
proposal,
I
think,
goes
a
long
way
toward
addressing
that
at
least
but
yeah
it's
hard
to
get
just
the
level
of
engagement
there.
The
other
thing
I
would
like
to
do
is
is
have
it
in
a
state
where
we
could
start
using
it.
If
we
just
roll
stuff
out,
that's
that's
making
use
of
it.
That
will
increase
interest
as
well,
and
so
that's
another
reason.
A
I
would
love
to
have
a
prototype
running
and
so
I'll
likely
try
to
take
a
look
at
that
and
see
see
what
we
can
do,
because
it
doesn't
have
to
be
in
the
browser
to
start
using
it.
So
just
an
app
that
that
integrates
this,
so
I'm
gonna,
if
that's
in
shape,
where
we
can
use
it
on
the
kind
of
timeline
where
we're
trying
to
roll
something
out.
A
I
will
make
an
attempt
to
to
make
use
of
it,
because
I
think
that
will
also
increase
the
security
properties
relative
to
just
sort
of
not
worrying
about
it,
which
I
think
is
going
to
be
the
instinct
for
for
a
lot
of
the
people
that
want
to
just
use
the
that
want
to
that.
Want
multicast
to
work,
but
don't
care
about
quick
and
browser
integration
which
we
have
some
of
and
it's
the
progress
is
incredibly
slow
but
non-zero
and
and
positive.
A
Let's
see
anyway,
that's
that
status.
What
was
the
other.
A
Yeah
lim
crx.
I
was
happy
about
the
progress
on
that.
A
Yeah,
I
guess
I
guess
that's
that's.
Most
of
the
report
I
wanted
to
cover
is
just
the
sort
of
gradual
solidification
of
the
of
the
strategy
on
how
to
get
into
the
browser.
A
You
know
the
the
feedback
on
the
browser
side
was
well
we're
you
know
like
from
web
transport,
for
example,
was
that
well
we
need
this
solved
at
the
quick
layer
and
so
solving
it
at
the
quick
layer
seems
like
in
line
with
that,
and
the
feedback
from
the
security
people
was
well.
We
need
a
proposal,
so
it
seems
like
it
solves
both
of
these
still
no
guarantee
that
it'll
go
anywhere,
but
but
but
it
is
responsive
to
those
points
of
feedback,
so
I
guess
yeah
anything
else.
B
I
don't
have
anything
at
the
moment.
I
mainly
you
know
like
if
there's
anything
you
want
from
me
prior
to
113.
Just
let
me
know.
A
Okay,
you're,
I
know
you
must
be
pretty
busy
but
yeah
when
we
have,
I
think,
we're
trying
to
arrange
a
couple
of
meetings
as
as
follow-up
next
steps.
I
think
some
of
them
got
pushed
back.
A
B
C
B
A
There
are,
there
are
many
challenges
and
there
are
many
yeah.
There
are
pros
and
cons
for
sure,
but
the
pros
are
pretty
good.
So
just
getting
that
traction
and
in
conjunction
with
the
isps
in
particular.
B
Remember
the
the
john
goodman's
line
from
big
lebowski,
like
our
problems,
are
solved.
It's
like
nope.
A
B
Yeah
and
my
my
regrets
for
for
missing
113,
but
I
have
had
this
vacation
planned
for
a
year
and
it
is
a.
It
is
an
attempt
to
redo
a
vacation
that
got
rudely
interrupted
by
kovid
the
year
before,
and
it
just
happens
to
be
that
the
only
week
the
only
week
my
girlfriend
has
off
is
the
week
of
113.
So,
oh
well,
all
right!
Well,.
A
A
B
So,
for
just
just
one
other
one
thing
regarding
114
are
you?
Are
you
aiming
for
like
for
like
a
barb
off
or
something
at
114
or.
A
A
I
know
quick
has
been
very
busy
from
time
to
time,
but
now
they've
got
the
the
main
drafts
published.
I
think
they're
main
they
do
have
several
things
they're
they're
trying
to
accomplish,
including
they
just
adopted
the
multipath,
of
course,
and
that's
going
to
need
a
bunch
of
discussion
I
bet
and
and
they're
trying
to
get
out
the
new
drafts
for
for
the
version
negotiation.
A
I
think
they
want
to
have
a
v2
just
to
prove
out
the
version
negotiation,
if
I
understood
correctly,
so
I'm
probably
going
to
have
to
catch
up
on
the
quick.
A
You
know
like
watch
the
watch,
the
quick
meeting,
videos
and
stuff.
I
know
they
do
a
lot
of
like
just
going
through
the
the
issues
list
during
the
during
the
session,
so
just
I'm
not
sure,
you're
muted.
I
think.
B
Yeah
yeah
they're
they're
real
working
sessions.
Right
they
don't
they
don't
screw
around.
A
Yeah
yeah,
so
I'm
gonna
have
to
do
some
catching
up
on
like
how
to
how
best
to
engage
with
quick.
I'm
hopeful
that's
going
to
get
easier
when
things
are
in
person
again,
but
yeah
we're
I'm
going
to
have
to.
I
don't
know,
make
that
I
haven't
been
going
to
any
of
the
quick
sessions.
Really.
I've
watch
them
from
time
to
time.
A
Yeah,
but
now
that
it's
now
that
we
have
a
quick
proposal,
I'm
gonna
have
to
fit
into
that
workflow.
Somehow,
if
it's
gonna
go
anywhere
so.
A
A
A
So
because
it
might
be
that
we
can
do
it
just
inside
the
quick
engine,
yeah
the
quick
engine
and
so
web
transport,
for
example,
can
you
know
it
can
look
like
just
doing
web
transport
datagrams
and
you
get
what
you
get
and
the
the
app
doesn't
know
or
care
that
it
came
through
multicast?
A
And
so
I
think
that
would
be
like
the
other.
Annoying
thing
is
that
I
know
chrome
took
out
the
the
server
push
because
it
had
like
an
internal
cache
that
was
complex
or
something
so
so
the
the
that
is
one
of
the
things
that
you
can
reasonably
do
with
the
with
a
sort
of
one-way
stream.
A
A
If,
if
datagrams
is
not
enough
so
and
it
might
not
be,
I
think
I
think
I
think
what
like
lucas's
draft
was
done-
kind
of
the
way
that
bbc
wanted
to
do
it,
as
I
understood
it,
and
that
was
a
server
push
based
architecture
where
it's
just
you
know
you,
you
do
a
server
push
and
now
the
clients
all
have
your
segment
and
then
off
off
they
go
so
the
you
know.
B
Yeah,
I
feel,
like
I
feel,
like
there's
been
a
lot
of
like
like
server
push,
is
definitely
out
of
fashion
and
you're.
It's
it's
gonna
it
I'm
not
sure
how
open
people
are
going
to
be
to
reviving
it.
But
maybe
you
know
if
there's
a
really
compelling
use
case.
C
B
The
complexity
and
the
fact
that
people
weren't
really
using
it
that
led
the
you
know,
led
the
hdbis
working
group
and
then
quick
to
be
like.
Why
do
we
have
this
thing?
Yeah.
B
Martin
thompson
put
together
a
document,
basically
explaining
it
was
either
martin
or
or
ben.
I
can't
remember,
put
together
a
document
explaining
what
the
limitations
of
server
push
were,
and
you
know
as
justification
for
for
effectively
axing
it.
So
it
might
be
worth
reviewing
that
I'll
see
if
I
can
find
it.
A
Yeah
thanks,
if
you
could
send
that
to
the
list
or
or
put
it
in
the
notes,
maybe.
B
A
I'm
pretty
sure
I'll
have
the
same.
Okay,
yeah
good
that'll
be
helpful.
The
on
the
plus
side,
like
with
datagram
support.
You
can
do
that.
You
can
do
that
just
in
the
in
the
web.
App
right,
so
you
don't
need
you
don't
need
the
underlying
thing
to
have
the
server
push
in
order
to
make
it
work,
if
you,
if
you
can
take
care
of
it
in
the
web,
app
off
of
your
datagrams,
which
is
like
the
the
way
that
my
demo
worked
right.
A
It
was
it's
doing
it's
just
receiving
the
udp
payloads
and
then
it's
essentially
doing
its
own
server
push
cache
inside
the
app.
A
All
right,
I
I
don't
know
if
that's
gonna
make
bbc
happy,
but
it
might,
it
might
be
enough
for,
like
me
and
ramp,
and
maybe
with
a
with
a
decent
library
it
would.
It
would
also
be
enough
for
bbc's
use
usage
if
we
can't
get
server
push
kind
of
put
back
in,
but
we'll
probably
have
to
have
some
some
demos
running
and
some
you
know
some
actual
delivery
somewhere
in
order
for
that
to
be
compelling
enough
for
them
to
want
to
to
want
to
pick
something
back
up.
A
Unfortunate
but
yeah,
okay,
I
think
that's
it
then
I
think
we've
rambled
long
enough.
Thank
you
both
for
coming
yeah.
Send
me
that
doc,
if
you
can
find
it.
A
A
Yeah,
that
would
be
good.
I.
B
A
A
C
A
In
the
transport
layer
part-
and
that
sounds
like
it
might
be
tricky
but
we'll
see.
B
A
A
I
think
I've
got
it
in
the
notes,
but
there's
the
there's
the
current
editor's
draft-
it's
it's
not
very
long,
so
you
can
read
it
quickly.
No
cool
but
yeah
feedback
is
is
of
course,
very
welcome
in
the
and
the
repo
is
a
very
fine
place
to
open
issues
or
make
prs
if
you've
got
them,
and
I
guess,
since
this
is
a
w3c
forum,
is
there
anything
web
related?
We
should
talk
about.
A
A
Think
it
is
an
open
question
there
might
be
a
need
to
to
enable
or
disable
via
either
api
support
or
or
browser
support,
in
terms
of
because,
like
in
the
security
consideration
stock,
we
talked
about.
A
So
the
idea
being
that
this
this
opens
up
some
new
information
leakage
because
of
the
multicast
joins
to
the
local
network
right
so
in
the
same
sense
that
the
enhanced
privacy
mode
in
the
browser
like
avoids,
leaving
breadcrumbs
for
local
administrators
to
find
or
or
other
users
of
the
local
computer.
A
A
If
you
disable
multicast
when
you're
in
private
browsing
mode,
then
you
avoid
leaving
breadcrumbs
for
local
network
administrators
because
you're
you're,
just
dealing
with
with
the
secured
unicast
traffic
now
and
they're,
because
the
the
sort
of
assumption
is
that
if
someone
knows
what
groups
you're
joining,
then
they
can,
they
can
figure
out
what
content
you're
consuming
so
and
it
doesn't
do
anything
about
the
traffic
analysis.
A
But
but
in
terms
of
hiding
your
activity
from
local
network
devices
and
administrators,
there's,
probably
some
privacy
considerations
there,
and
so
the
browser
needs
to
be
able
to
disable
it.
At
least
I'm
not
sure
if
the
page
needs
to
be
able
to
disable
it
to
to
prevent
use
when
it's
when
you
know
the
page
itself
wants
to
maintain
privacy
mode
or
some
such
or
or
the
opposite
right.
A
If
the
page
has
to
enable
it
to
allow
for
it
right-
maybe
that's
the
maybe
that's
the
way
to
look
at
it,
so
I
probably
do
need
a
privacy
considerations
section
there
because
of
the
web
support
and
I
don't
think
that's
in
there
yet.
C
A
Yeah
I
felt
like
they
hadn't,
really
had
a
lot
of
objections
or
thought
that
anybody
or
things
that
anybody
raised
much
when
we
talked
to
them
was.
I
am
am
I
wrong
about
that?
A
C
C
Having
yeah
having
been
involved
in
some
of
the
design
sessions,
for
that
there
was
a
lot
of
consideration
given
to
what
information
gets
exchanged
between
devices
before
the
secure
connection
is,
is
established,
and
so
you
know
keeping
that
to.
C
A
And
the
information
leakage
due
to
multicast,
so
I
think
I
I
do
think
it's
right
to
leverage
that,
and
I
think
second
screen
is
one
of
them.
I'm
not
sure
it's
the
even
really
the
only
one.
You
know,
there's.
A
There's
just
even
using
mdns
names
domain
names
that
the
result
in
local
discovery
leaks
some
information
in
the
same
kind
of
way.
A
So,
like
apple
recently
added
some
controls
on
that,
for
instance,
you
know
you
had
to
you
had
to
have
permission,
what
do
they
call
it?
There's
like
a
you
know,
your
app
has
to
be
blessed
and
and
permitted
to
do
this
in
order
to
be
in
order
to
be
able
to
use
that
and-
and
it
has
to
like
register
what
names
it's
going
to
use
and
explain
why
it
needs
to
to
do
local
discovery.
A
And
joining
of
multicast
had
the
same
kind
of
thing
attached
to
it.
There
was
tommy
paulie
talked
about
it
in,
I
think
the
the
mbondia
at
112.
If
I
remember
it,
it
might
have
been
111,
but
I
think
it
was
112.
A
And
that
might
happen
in
the
browsers
too.
In
some
sense,
I
guess
it
seems
to
be
like
the
a
direction
to
to
go
to
sort
of
address
the
privacy
concerns
for
for
these
kinds
of
local
network
issues,
and
I
think
multicast
really,
like
apple,
got
this
right
it.
It
does
fall
in
the
same
category
of
exposing
some
information
to
the
local
network.
That
has
some
potential
to
be
sensitive,
but
there
are
many
good
reasons
to
do
it.
That
should
be
permitted.
A
You
know,
and
so
there's
that
that
balance
of,
like
you
know,
noticing
that
there's
some
risk
with
this,
but
then
permitting
it
in
in
a
sort
of
tracked
way
that
prevents
that
allows
for
preventing
of
abuse
by
you
know
by
block
lists
that
the
browser
can
maintain,
or
some
such
or
or
some
some
kind
of
benevolent
authority
can
maintain
so
yeah.
A
I
I
guess
I
do
anticipate
that
being
the
direction
to
solve
that
kind
of
problem,
and
it
seems
like
there's
some
progress
happening
there
and
I
think
it's
not
really
just
specific
to
second
screen,
like
apple,
is
the.
A
C
A
Yeah,
I
think
my
strategy
at
this
point
is
to
come
back
to
that
after
getting
a
little
more
traction
at
the
lower
layer,
and
I
think
that
I
think
it
probably
will
have
to
be
addressed,
but
I'm
hoping
that
I
can
just
take
what
somebody
else
is
doing,
but
I
probably
should
keep
an
eye
on
second
screen
and
maybe
there's
others
watching
this.
I
I
don't.
C
C
I
guess
where
this
gets
interesting
is
that
we're?
You
know
it's
not
just
a
browser
api.
It's
it's
a
combination
of
that
potentially
plus
the
networking
aspects,
so
I
don't
know
how
this
unusual
that
kind
of
thing
will
be
for
them.
I
assume
that
they've
been
through
this
kind
of
similar
thing,
like
with
web
transport
and
with
webrtc
and
so
on.
So
you
know
it,
it
will
be
something
that
they'll
be.
C
You
know,
they'll
be
familiar
with
this
kind
of
you
know
this
kind
of
space,
but
yeah
when
we
get
to
that
point,
we
will
want
to
have,
you
know,
have
their
review.
I
think.
A
All
of
great
notes
here.
A
Just
put
a
comment
with
the
link
that
I
just
found
so
all
right,
cool
anything
else.
A
A
But
I
think
I
think
I
think
saying
that
the
page
should
explicitly
enable
it
is,
is
a
good
control
to
add,
in
is
my
guess,.
C
A
A
A
I
guess
there
might
be
a
question
of
whether
whether
you
enable
it
just
for
datagrams
or
for
also
server
push
or
whether
there's
like
other
things
that
might
be
baked
in
in
the
use
case
layer.
A
So
there
might
be
other
apis
that
have
to
go
either
into
the
quick
library
for
its
usage
or
and
then
be
sort
of
used
by
the
browser
or
or
all
the
way
into
like
a
you
know,
something
that
the
page
has
to
express
to
to
put
it
in.
A
A
A
That
makes
sense
all
right
great,
I
think,
20
minutes
ago
I
said
we
were
done
so
now
I'll
call
it
for
real
all
right,
thanks
for
coming
guys,
really
appreciate
it.
I
hope
it
really
helps
to
have
this
kind
of
sanity
check
on
me.