►
From YouTube: IETF92-PAYLOAD-20150325-1520
Description
PAYLOAD meeting session at IETF92
2015/03/25 1520
A
C
A
C
C
Well,
good
afternoon,
everybody
this
is
the
payload
working
group
trying
to
see
that
in
making
typos
having
to
do
all
working
groups
and
our
lives
here
and
me
chairs
the
note.
Well,
you
should
be
aware
of
what
they
say
about
IPR
known
I
PR
so
you've
seen
it
already
for
a
couple
of
ten
times.
It's
Wednesday
today
agenda
the
payload
status
update.
Then
we
have
the
payload
format
for
the
map
codec,
which
I
will
present,
because
the
authors
are
not
here,
there
may
be
in
the
Java
room,
Jonathan.
C
Okay
and
we
have
the
SPT
291
ancillary
data,
and
we
have
the
thick
payload
and
the
vp9,
which
will
be
presented
by
Justin,
not
by
Jonathan,
Wright
least
I
got
the
presentations
also
from
him.
We
have
one
load
taker
whose
bow
anyone
I
would.
I
would
like
to
get
a
second
mode
taker
anyone
volunteers
to
take
note
just
action
items.
C
Ok,
Stefan
was
good
enough
to
do
that.
So,
okay,
no
problem,
so
the
document
status
we
didn't
have
any
RFC
published.
We
have
the
RTP
how
to
in
the
ethical
q,
I
think
it's
mixing
for
some
reference
we
have
in
is
G
processing
the
g7
1100
520
55,
there's
a
05
version
that
was
uploaded
today
and
I
hope
it
will
open
close
the
open
issues
after
the
discussion
that
they
had
aged
0
to
60
507.
C
A
A
On
top
of
that,
through
some
discussion
in
the
IMT
see
which
trickled
back
to
us
and
so
on,
but
more
mostly,
we
came
up
with
one
other
change:
that's
potentially
not
editorial,
and
that
has
to
do
with
this
decoding
order.
Number
presence
being
signaled
through
the
trend
through
the
mode
of
it
through
the
transmission
mode,
Mrs,
T,
srst
and
mr
empty.
A
C
A
I
present,
our
estimation
is
that
it
will,
you
know
if
I
wouldn't
tell
you
most
of
you
would
probably
not
even
seen
it,
because
the
changes
are
really
really
really
minor
and
eligible,
but
it's
still
a
non
editorial
change.
The
world
come
back,
but
it's
not
going
to
be.
There's
not
going
to
be
a
need
for
foreign.
You
know
to
review
all
the
whatever
90
pages
of
what
is
now
in
over
it
by
working
angles.
Okay,.
A
C
C
C
A
C
C
Color
with
rottier
they
were
covered
from
about
the
the
beverage
and
all
these
things
I
think
there
was
some
comments
on
the
list
which
I
didn't
feel
like
they're
all
fixed
okay.
So
we
will
try
to
see
how
to
finish
them.
Okay,
the
milestones
I,
don't
think
I
don't
want
to
go
to
that.
It's
just
there
there.
We
still
have
these
documents
that
there's
some
some
codecs
that
are
not
being
progressing.
C
We'll
have
to
go
back
to
those
people
and
see
if
they
intend
to
do
what
they
want
to
do
like
the
Bluetooth,
the
preamble,
one,
that's
that's
early
and
I
need
to
discuss,
and
because
we
are,
the
will
was
our
work
and
I
think
that's
the
MVC.
What
the
MVC
yeah
I
don't
know
what's
happening.
Is
it
you
Cree
Stefan?
You
look
every
see.
A
A
C
C
It's
the
we
have
the
Emil
p
payload
format.
C
C
Now
it
has,
it
has
3
mods
this
612
hundred
and
twenty
four
hundred
room.
This
is
not
that
important.
Now
as
I
read
it,
but
has
anyone
else
read
this
document?
Are
you
ready
to
okay?
So
they
have
some
I
sentiment,
a
response
on
the
list
on
some
of
these
like
they
have
they.
The
thing
is
that
the
right
thing
is
that,
first
of
all
that
they
expect
to
be
symmetrical
on
both
sides.
So
if
you
offer
12
to
2
2400,
600
and
1200,
it
means
that
you
can
dynamically
switch
between
them.
C
The
preferred
one
is
the
first
one
and
the
response,
the
the
the
offer
and
the
response
can
select
what
he
wants
and
he's
dictate
the
order,
and
it
needs
to
be
symmetric.
It
means
that
if
I
didn't
ask,
why
I
mean
that's
the
way
it's
used?
Okay,
they
want
it
to
be
symmetric,
so
I
didn't
care,
it's
something.
You
really
can
ask
why
it's
need
to
be
symmetric
and
inside
an
RTP.
C
C
The
other
things
there
too,
to
note
is
that
they
are
requesting
to
have
the
payload
subtype
name
will
be.
They
have
em
ELP
and
ELP
e,
and
they
have
also
ones
that
are
with
the
beach
right
inside,
like
the
1200,
the
600
and
I
said
we
don't
usually
like
it,
because
we
prefer
to
advocate
as
a
parameter
which
they're
having
the
definition,
but
they
said
it's
already
being
used
currently,
so
they
want
just
to
capture
the
weight
is
being
used.
Instead
of
of
changing
look
at
it,
send
the
comment
whatever
to
do.
C
E
Jonathan
I
Simon
have
a
little
scared.
This
unity.
We
asked
yesterday
over
stamping
they've
already
done,
rather
than
applying
our
best
practices
to
how
we
think
it
should
be
done.
So
hopefully
I
mean
if
they
are
they'll,
be
unhappy.
If
we
change
how
it
works,
then
I
don't
think
that'll
be
a
bit
outcome
for
anyone.
So
I
mean
I.
Think
that
I
mean
what
way
you
were
saying
is
like
you
know,
we
are
a
foundation
or
does
this
way,
so
we
can't
change
that
I.
Think.
C
They
only
the
only
point,
it's
about
think.
The
only
point
is
about
the
payload
subtype
limbs
and
we
can
discuss
this.
I
mean
I'm.
Just
saying
what
I
got.
I
sent
a
comment
about
it.
I
it's
on
the
mailing
list.
We
sent
a
comment.
We
got
a
response,
we
can
still
discuss
this,
but
I
mean
at
least
it's
a
lot.
It's
an
RTP
payload
for
an
audio
codec
search.
We
save
this
scope
of
this
working
group
and
that's
what
we
are
doing
it.
So
that's
a
problem.
The
issue
is
whether
we
can
progress
it
Aziza.
C
So
so
it
will
be
good
sent
also
in
this
on
the
mailing
list
and
we'll
take
into
consideration
before
adopt
adopting
it
as
a
as
a
work
item
in
the
working
good
to
see
that
they
are
okay
with
essential.
We
have
some
agreement
about
how
to
proceed
on
that
part.
Okay,
okay,
so
think
this
is
the.
This
is
the
information
about
this
one
okay,
so
the
next
presentation
we
have
is
the.
E
F
A
F
Okay,
so
simply
what
is
this
society
of
motion
picture
and
television
engineers?
It's
the
standards,
development
organization
for
professional
video
applications
and
today,
professional
video
inside
the
broadcast
plant
is
carrying
something
called
a
serial
digital
interface
or
SDI.
This
is
either
a
megabit
per
second
for
SD
or
1.48
gigabit
per
second
for
HD
serial
digital
signal.
That's
carried
over
75
ohm,
coaxial
cables.
F
So
in
order
to
do
this,
we
need
to
start
taking
a
look
at
how
we've
been
sending
video
of
our
SDI,
breaking
it
down
into
its
individual
components
and
mapping
these
into
an
RTP
infrastructure,
so
that
we
do
these
standards
compliant
/
RP.
So
some
of
these
elements
include
many
rfcs
which
the
IETF
is
already
developed.
One
is
RFC
4175
I,
believe
in
mr.
Collins
developed
this
for
the
carriage
of
uncompressed
video
over
IP
10
years
ago
works
just
fine.
It
seems
to
meet
a
lot
of
our
needs.
F
Another
one
is
RFC
3190
the
character,
24-bit
uncompressed
audio
PCM,
/
RTP.
This
has
just
been
adopted
by
the
audio
engineering
society
amias
as
their
80s
67
standard
and
that's
gaining
ground
in
the
audio
world
and
we're
bring
them
to
carry
audio
or
video
world
as
well,
potentially
1588
from
the
I
Triple
E.
The
precision
Time
Protocol
is
a
great
way
to
do
the
timing
that
we
need
in
order
to
time
our
systems
make
sure
the
audio/video
synchronization
and
that
we
can
do
frame
accurate
switching.
F
This
leaves
a
little
bit
of
something
called
ancillary
data
and
thus
the
internet
draft
bored.
So
the
serial
digital
interface
mocks
at
several
different
areas.
Boop
you've
got
the
active
video.
This
is
what
you
actually
see
on
your
television
at
night.
This
is
where
the
actual
video
is
carried
within
the
SDI
box.
F
A
C
F
So
what
is
ancillary
data?
Its
non
video
data,
which
is
embedded
in
the
STI
outside
of
the
active
video
area?
It's
typically
10-bit
words
and
most
of
our
applications
today,
unfortunately
not
matching
LT
octet
boundaries,
it's
identified
by
a
pair
of
the
data
ID
and
the
secondary
data
ID
and
as
d
id
MSD
ID
cynthy
terminology
it's
registered
through
cynthy,
including
the
active
format
descriptor,
which
helps
us
with.
We
go
from
16
by
9
representations
in
beyond,
convert
before
by
three
representations
to
make
sure
important
things
don't
get
cut
off.
F
The
screen
can
scan
data
for
movies
study.
One
of
four
messages
for
use
in
ad
insertion
triggers
DVD
vbi
photos
of
your
lyric
electra,
PVR
ancillary
timecode,
and
also
the
closed
captions
of
both
and
Celia
708
and
cea
608
closed
caption,
normally
dia,
subtly
registry.
So
closed
captions
are
very
important.
You
know,
frankly,
broadcasting
only
one
thing:
we
need
to
have
all
the
air,
the
u.s.
that's
closed.
Captioning,
that's
the
one
thing
we
can
get
fined
for
not
having.
We
can
have
no
video,
no
audio.
Nobody
cares.
F
Simply
registry
of
ancillary
data
types,
so
the
goals
for
this
payload
are
to
be
able
to
carry
ancillary
data,
whether
it's
from
standard
definition
or
high
definition,
video
sources
being
in
the
vertical
ancillary
area
or
horizontal
minutes
Larry
area,
either
in
the
Y
or
luminance
channel
or
the
sea
or
chroma
channel,
and
also
have
sufficient
information
provided
such
that
we
can
recreate
in
the
decoder
we're
in
the
STI
raster.
The
original
ancillary
data
came
from
this
is
for
it
is
important
for
some
specific
legacy
uses
in
the
future.
We
probably
won't
need
this.
F
Okay,
we
must
be
back
to
pc
conversion
problem.
You
get
the
point
on
top
and
black
is
typical.
Rtp
payload
orange
we've
got
the
ancillary
data
hearts
of
the
table.
Header
at
the
extended
sequence
number
the
length
knock
text,
the
counts
of
the
ancillary
number
of
ancillary
data
packets.
That
which
are
in
the
payload
and
then
blue
is
the
ancillary
data
packet
itself
with
weather
growing
or
luminance
line.
F
So
for
a
media
type,
we're
suggesting
it
be
under
video
because
it
is
highly
associated
with
the
use
of
video
and
that
it
be
cynthia
smpte
291,
which
is
the
name
of
the
standard
for
ancillary
data
packets
and
serve.
You
we'd
like
to
include
an
optional
sdp
format,
parameter
for
identifying
it
flow
is
made
up
exclusively
of
a
particular
ancillary
data
type
as
a
FN
PT
mmq
down
here
here,
indicating
the
div
0
x,
61,
st
id0
XO,
to
for
example.
This
is
608
closed
captions
in
this
particular.
F
F
C
Ok,
so
I
said
it
did
anyone
read
it
or
have
any
comments
on
that.
F
You
know
the
broadcast
industry
is
getting
its
head
kind
of
wrapped
around
how
that's
going
to
work
right
now.
I
think
we,
in
the
eve
of
the
AES
radius
of
70
kind
of
innovating
they'd
like
to
sip,
although
they've
found
that
more
challenging
than
I
think
they
first
expected
so
I
was
suspicion.
It's
going
to
end
up
being
like
web
services.
F
E
Better
yeah
sure
that
makes
it
so
the
other
question
I
have
to
assume
this
would
typically
be
tightly
associated
with
it.
Actually,
no
video
overall
relatives
will
be
together
and
though
he'll
welcome
to
be
constant
right.
Yes,
so
there's
the
usual
complexity.
Where
I'm,
like
this
guy
sitting
behind
me,
for
the
fact
that
you're
not
allowed
to
use
the
same
archetype
steps,
because
the
have
traditionally
randomized
you
will
have
to
have
various
complexity
exception.
E
We
should
go
where
the
where
you'll
have
the
computers
have
the
of
the
direction
signaling
mtv
timestamps
and
the
library
so
which,
given?
How
can
the
time
step
locked?
Everything?
Is
it's
probably
not
that
the
end
of
the
world
for
you,
but
should
look
at
the
make
sure
you
have
all
of
that
birthday
and
cozy.
F
F
Yeah
we
get
we
particular
cat
box,
aureus,
RFC
yeah,
and
you
know
we're
not
necessarily
ruling
out
the
use
of
the
RTP
header
extensions.
I
think
RFC
6051,
that
has
a
64-bit
time
staying
up
an
endurance
tension,
but
I
was
suspicion
like
abs,
67,
we're
going
to
try
to
stick
with
the
hawk
stores
in
the
stp
as
well
as
this.
D
D
Looking
the
draft
I
notice,
you've
copied
the
extended
sequence
number
thing
from
4175,
please
for
4175
that's
needed,
because
the
secrets
numbers
were
out
too
quickly.
It
wasn't
clear
to
me
if
you
had
enough
packets
in
this
format
that
you
actually
needed
the
extended
series
number
equally
I
can
see.
You
may
want
it
just
to
make
things
easier,
because
it's
the
same
as
the
rest
of
the
vid.
So
that's
something
to
perhaps
look
at
the
other
thing
which
I
think
you
should
take.
D
A
careful
look
at
when
you
think
about
bringing
this
into
the
warning
is
nothing
to
bring
things
in
along
with
the
unrest.
Video
format,
especially
at
school
experience,
is
that
the
rtcp
packet
rate
is
some
surprisingly
high
for
these
types
of
applications
and
the
video
that
the
counters
wrap
very
quickly.
So
it
may
well
be
that
a
lot
of
ER
tcp
extensions,
don't
quite
work
when
you're
sending
rtcp
at
the
fair
sentencing
thank
its
personnel.
D
F
With
regard
to
the
extent
the
header,
that's
our
the
extended
time
stamp,
I
went
back
and
forth
in
my
head
about
that.
I
figured
it's
hard
to
go
along
with
it,
because
we
don't
know
exactly
how
much
ancillary
data
people
really
wanna
push
push
broom,
it's
just
all
the
ones
for
unpacking
per
frame,
maybe
doesn't
matter
for
all
fish
out
of
your
packets
per
frame.
I
might
be
more
than
issue.
E
Relay
across
fitness
on
general
because
they
were
a
bit
about
the
use
of
media
tech,
video
above
early
video
because
officially
associated
with
video,
we
have
other
examples
of
metadata
article
formats
and
what
media
types
do
they
use.
Speaking
for
myself,
I
think
we
have
had
some,
which
typically
have
any
milk
really
like
fat,
will
use
typically
use
video
for
protecting
video
I'm,
not
sure
we
have
meditative
proper
as
opposed
to
a
pair
of
clothes
and
there's,
like
you
know,
cursor
position
uses
video
things
like
that.
So
I
think.
F
D
F
D
C
A
F
If
that
sounds
like
at
that
well
and
then
what
reason
you
want
to
be
able
to
mix
and
match,
for
instance,
if
we
have
an
English
version
of
a
German
version
or
french
version
of
the
audio,
and
we
have
to
make
a
couple
of
different
distributions
of
this
device.
Cable
will
pull
the
RTP
German
over
here
with
this
video
and
then
pull
the
French
for
that
videos.
I
think
the
flexibility
makes
it
reasonable
that
we
have
these
and
separate
our
community
sessions.
This
isn't
really
to
be
bundled
together
for
end
users.
A
A
E
John
flags
are
further
relate
for
us.
He
said
EJ's
approaches
the
corporate
farming
box
and
religious
about
to
have
a
video
data
which
might
still
wanna
have
this
type
of
vanilla
burger.
If
I
had
10.
You
basically
just
said
about
the
you
know
some
way
of
indicating
which
closed
captions
are
written,
which
in
mind
there's
the
outside
available
list.
Now.
F
Be
outside
the
scope
again,
the
goal
here
is
to
carry
cynthy
rich
tree
ancillary
data
in
the
city,
registration,
all
those
upper
level,
closed,
captions,
notnot
languages,
and
you
know
I
think
over
time
we
may
as
an
indicator
broadcast
industry.
We
may
want
to
take
a
look
at
breaking
the
closed
captions
out
the
separate
time
text
streams.
Unfortunately,
we're
not
at
a
point
where
we
can
really
do
that.
There's
still
too
much
legacy
built
around
is
608
the
708
closed-captioned.
A
Ben
campbell
jonathan
made
me
think
of
something
that
probably
not
something
need
to
worry
about
right
now,
but
if
you've
been
mentioning
the
use
case
of
identifying
springs
by
different
language
or
closed
captioning
by
different
language,
there
is
a
kind
of
pre
buff
effort
going
on
right
now
and
ryone,
which
includes
doing
some
language
tagging
for
our
TV
screens.
It's
really
more
designed
for
interactive
telephony
type,
in
fact
applications,
but
there
may
be
some
applicability
here,
at
least
when
it
comes
to
how
you
identify
these
things,
just
something
to
keep
in
mind.
Okay,.
F
Yeah,
that's
that's
great
information.
What
one
can
ways
you
have
a
closed
caption.
We
are
very
strict.
The
regulations
are
very
certain,
of
course,
by
the
FCC.
Now,
I'm
sure
shortly
will
be
enforced
by
telecommunication
regulators
around
the
world.
So
we
do
have
to
be
careful
about
exactly
what
you
know
how
power
carrying
labeling
these
things,
but
I
people
continue
to
watch
that
sometimes.
A
While
224
has
something
to
do
with
video
in
the
sense
that
it
controls
the
camera,
224
is
something
that
goes
from
the
receiving
end
to
the
sending
end.
Only
so
it's
a
totally
legitimate
use
to
control
the
camera
promises.
It
took
you
to
use
to
24
to
send
camera
control
information
from
a
system
that
has
never
seen
a
camera
in
its
life
right,
so
I
think
that's
a
difference,
because
this
stuff
is
really
clearly
basically,
as
I
was
here.
It.
C
E
E
F
C
B
C
C
B
B
So
there
are
a
couple
of
poppin
issues
that
have
been
carried
over
from
Honolulu.
The
first
one
was
how
to
be
associated
the
repair
package,
streams
to
the
source,
packaging
screams,
and
this
I
think
in
Honolulu
with
the
music.
There
was
no
final
decision,
so
since
it's
called
flex
back,
we
decided
that
we
would
go
with
the
dynamic
Association
would
be
armed
and
keep
the
stb
very
simple.
Thus
we
won't
have
a
good
music
again.
Perhaps
just
htp
direct
rate
can
vary
over
so.
B
E
B
Okay,
so
next
slide
place,
then
so
so
the
current
problem
is
perhaps
as
simple
as
that.
You
have
effect
RTP
stream
and
you
have
source
streams
from
different
media
sources,
so
you
want
me
to
even
we
do
have
to
cram
when
the
receiver
received
it.
There
is
no
actual
actually
currently
way
of
associating
them.
So
there
are
several.
B
To
Peter
Thatcher,
who
make
these
slides
than
the
next
four
in
Senegal
next
slide,
please
so
left
for
bias,
SRC,
which
is
basically
putting
and
it's
SRC
in
the
effect
stream
in
same
there
is
a
reference
to
certain
source,
RTP
stream
them
that's
as
simple
as
protection
in
having
severe
on
stupid
media
source.
The
next
time
the
next
one
was
hard
to
fit
using
em,
ideally
powered.
How
would
we
do
this?
This
is
kind
of
difficult,
especially
if
there
is.
B
Single
week
via
source,
like
just
read
a
1,
then
this
will
be
easy
and
it
would
be
sufficient
next
slide.
So
there's
also
proposal
of
doing
an
RTP
source
ID,
where
it
would
be
as
simple
as
adding
another
identifier
to
to
both
the
source
cream
and
the
repair
stream,
where
both
of
them
have
the
identifier
to,
and
you
would
be
able
to
receive
when
you
receive
that
you
will
be
able
to
map
them
next
slide.
So.
B
A
B
The
pic
so
this
would
look
like
in
the
article
hair
extensions
as
unexciting
one
for
the
sauce
streams,
which
would
be
on
every
packet
and
the
facts.
Teamwork.
Whenever
the
practical
drive
would
have
the
same,
so
you
will
be
able
to
associate
this
game
if
you
are
multiple
streams,
the
same
thing
you
are
correct,
so
so
I
guess
the
open
question
for
this
first
issue
is
which
of
the
three
mechanisms
or
four
mechanisms
are
ideal
of
just
using
SSRC
using
made
+
RS,
ID
or
just
RS
ID.
E
I
think
that
doing
s
Circe's
explicitly
as
a
developer,
a
terrible
idea,
because
I
mean
all
sorts
of
things
that
expected
all
the
recording
stuff
and
everything
else
is
out
of
scope,
whispered
and,
additionally,
I
think
we
also
need
to
solve
this
problem
for
our
TX,
which
isn't
already
defined,
feel
a
little
workout.
So
whatever
we
do
should
be
better
extensions
or
other
better
data.
So
I
think
that
we
should
say
we're
not
going
to
us
our
seeds
and
we
should
further
rescue
worker
with
scope,
which
is
either
injector.
E
B
B
C
D
D
E
E
C
Okay,
so
I
think
to
conclude
that
what
I
understand
is
I
think
what
Jonathan
and
I
agree
with
John
Kahn
is
that
you
have
a
solution
when
it's
in
a
separate.
This
one
is,
if
you
want
to
to
have
them
in
the
same
m
line,
or
also
you
need,
maybe
in
the
case
where
you
have
one
having
to
support
even
one
fax
stream
for
two
separate
em
lines,
or
things
like
that.
You
need
some
identifiers
for
that,
then,
in
this
case,
you
need
to
the
other
side.
C
I
think
people
agree
or
did
the
RSI
do
some.
Some
generic
token
is
needed,
but
I
think
it
needs
to
be
presented
in
their
music
right.
Does,
okay,
that
it's
not
to
pay
it
sets
at
a
payload.
Okay,
then
you
just
you
will
have
it
here
is
an
example
that
you
have
to
define
the
generic
this
generic
one
in
a
different
working
groups
0
through
that's
a
conclusion.
B
C
D
Contact
as
a
procedural
thing
to
make
this
go
quickly,
I
would
write
this
payload
format,
just
on
the
assumption
that
everything
is
sense
of
separate
Airlines
and
you
use
the
grouping
that
way.
This
can
be
done
very
quickly.
I
would
then
in
another
working
group,
do
this
other
stuff
and
then
that
draft
then
refer
to
this
and
r-tx
and
anything
else
where
it
useful
I'm
waiting
UT
couple
one,
and
so
that
would
you
you're.
E
D
E
B
C
E
E
A
B
B
B
A
A
So
again,
we're
trying
to
divorce
ourselves
of
anything
in
stp
will
try
to
make
everything
flexible
and
dynamic
at
the
sender's
discretion
in
RTP,
and
so
by
doing
this
we
can
eliminate
the
stp
part
and,
and
the
RTP
sender
can
dynamically
signal
whether
or
not
to
D
is
coming.
Here's
one
D
but
to
D
is
coming.
E
Actually,
like
most
motivation,
because
if
your
instance
in
one
of
the
cases
that
definitely
care
about
is,
if
you're
applying
the
fact
to
video
and
video
bandwidth
and
swing
around
so
widely,
you
want
to
be
dynamically.
Changing
your
structure.
You
know
like,
depending
on
whether
it's
decided
to
76
megabits
or
50
kilobits,.
C
B
So
we
have
couple
of
operations
based
basically
with
this
in
SD,
be
the
first
ones
the
type
of
protections.
If
you
go
with
the
flexible
one
that
we
could
do
away
with
this
top
pitch,
which
was
0
1
and
2,
to
indicate
that
it's
interleaved
on,
interviewed
and
and
or
both
if
you
do
it
dynamically
in
RTP,
that
there
is
less
use
of
signal
exist
in
stp.
However,
I
believe
there
might
be
some
cases
where
it
may
not.
They
might
be
static,
so
if
they
want
to
do
it
is
nice
to
be
so.
B
A
B
Just
remove
that
as
well,
so
the
last
open
issue
is
nds
TV.
This
is
again
the
length
of
the
depth
of
the
the
fixed
2d
protection.
The
main
point
was
that
conveyed
the
M&N.
We
can
only
go
to
56
cross
256
packets,
which
is
quite
many,
so
we
could
remove
it
and
be
happy
and
just
look
at
the
constraint
that
that
one
comes
out
a
predominately
56
well.
A
A
E
So
I
mean
I
think
that
if
we
need
fact
for
identity,
we're
going
to
have
a
modified,
primitive
as
easily
spent
a
sequence
on
the
family,
that
I
think
that
you
know
if
you're,
not
when
you
forgive
this
attentive
use
case
of
this
is
for
things
of
use
or
dressing
team
can
see
those
numbers.
I
think
that
you
know
being
able
to
protect
no
more
than
entire
signals.
Number
roll
over
is
entirely
fun.
Okay,
I.
A
B
So
so
the
proposal
is
to
remove
it.
I'm
here
no
objection
to
its
ok:
let's
remove
it,
monks,
okay,
so
next
steps
it
just
gotta
accept
it
as
a
working
group
document
that
some
work
still
to
be
done.
We
would
appreciate
feedback,
especially
interviews,
so
that
we
can
fix
this
quickly.
Going
forward,
perhaps
be
done
with
it.
Okay,.
G
All
right
craft
with
the
poultry
video
Jonathan
gaining
a
video
on
Big
John
Taylor
format.
So
if
you
cannot
click
overview,
much
better
compression
than
vp8
or
the
previous
generation
with
codecs
forty
percent,
our
team
quality
of
forty
percent
pure
bits,
the
Codex,
much
more
flexible
and
ask
for
eight
reference.
G
Pictures
in
each
reference
picture
can
be
a
different
resolution
than
the
frame
that's
actually
being
encoded,
does
off
sampling
or
down
seven
or
whatever,
to
basically
go
from
the
previous
frame
reference
frame
to
their
for
picture,
and
this
allows
or
basically
scalability
that
you
can
have
a
current
picture
at
720p,
be
predicted
from
a
base
layer
at
360p,
and
you
know
that
frame
that
should
be
cut
it
either
from
the
base
layer
and
a
spatial
sense
that
also
from
previous
temporal
frame
and
be
pretty
good
for
multiple
reference.
Pictures
and.
E
G
E
G
G
Do
full
scalability
and
dad
one
of
things
that
comes
along
with
this
is
that,
if
we're
basically
supporting
star
sending
a
stream
a
middle
box,
that's
aware
of
scalability
can
basically
drop
out
higher
layers
in
these
higher
layers
can
be
removed
without
affecting
the
integrity
of
the
lower
layer
next
slide.
So
we
introduce
some
terminology
into
in
this
document,
basically
defining
two
types
of
things:
a
superframe
and
a
layer
frame
and
the
superframe
our
mayor
fraim
is
this
is
saying
for
a
given.
You
know
special
size.
G
This
is
base
one
street
one
frame
captured
once
in
a
time
and
the
superframe
is
the
combo
this
across
all
spatial
layers.
So
this
basically
just
makes
it
easier
to
refer
to
much
other
concepts.
It's
referred
to
frequently
in
the
document
next
time,
so
the
packetization
covers
a
bunch
of
things.
One
things
we
need
to
talk
about
is:
if
is
a
frame
actually
something
you
know
what
layer
is
it
in,
but
especially
in
temporarily,
what's
this
prediction
structure
or
we're
coming
from?
G
Is
this
thing
discardable
much
the
bits
that
are
talked
about
in
one
of
the
presentations
yesterday
about
basically
having
frame
markings
in
RTP
header
extension
are
also
sir
presence
here.
You
know
it
indicates
winners
of
packets,
the
start
of
the
frame
packets
at
the
end
of
a
frame,
whether
it's
a
keyframe,
whether
the
frame
is
discarded
and
in
addition,
it
also
has
other
sort
of
things
about.
You
know
take
a
temporal
and
spatial
scalability
there
is.
There
are
two
modes
of
how
the
scalability
can
be
indicated.
G
You
can
either
say
here
are
all
the
pictures
that
this
particular
frame
depends
on
or
you
can
sort
of
say
well,
there's
a
sort
of
pre
de
there
there's
gonna
be
a
special
pattern
that
these
frames
are
going
to
follow
for
temporal
structure.
You
might
say
I'm
going
to
send
temporal
layer,
0
first
and
then
two
and
then
one
and
two
and
always
moving
the
structure
and
so
based
on
the
actual
sort
of
frame
number.
G
G
This
first
up
is
specified
the
scalability
structure,
and
then
you
can
refer
to
this
with
a
more
efficient
coding
of
the
packetization
and
allows
you
to
determine
which
are
there
actual
temporal
references,
you're
flexible
mode.
You
can
actually
basically
say
here
are
three
excesses
of
reference
pictures
that
this
thing
depends
upon
and
it's
more
flexible
as
the
name
implies,
but
it's
also
slightly
more
verbose
in
terms
of
how
many
bits
requires
the
packetization
header.
So
here's,
the
overall
big
picture
of
the
techno
sation,
looks
just
like
any
other.
G
Lee
80
and
ass
layer
indication.
That's
president
at
this
elbit
is
said:
we've
also
got
the
other
bits.
I
talked
about
earlier,
the
beat
bit,
which
is
the
beginning
bit
of
a
frame
or
being
a
packet
of
frame
II
for
the
in
packet,
in
a
frame
as
well
as
I,
for
you
know
key
and
some
other
things
as
well,
but
you
can
see
that
this
could
actually
be
several
bites
for
the
actual
packet
hair
next
slide
and
in
the
non
flexible
mode.
G
You
know
it's
Trump
down
a
little
bit
more,
and
so
the
actual
later
thing
is
determined
from
the
gof
index.
The
special
mayor
is
still
the
sky
explicitly
next
slide,
and
so
you
don't
need
to
send
all
these
bits
all
the
time
if
you're
just
doing
hi
poppy
stream,
you
can
do
a
just
a
single
bite,
the
technical
bite
and
you
don't
want
to
use
them
to
be
in
the.
G
You're
doing
just
temporal
and
not
spatial,
then
you
have
a
special
skill,
bony
structure,
the
SS
structure,
but
you
only
fill
in
later
04
special
scalability,
but
the
actual
temporal
narrowly
indicated
through
the
goth
index
and
if
you're
doing
everything,
then
you'll
fill
in
the
s
and
the
D
bits
as
well.
I'd
indicate
that
this
is
you
know,
layer,
0,
mayor,
one
spatial
risky
bet
on
overall
I'd.
You
know
this
can
be
good
fairly
efficiently.
You
know
in
you,
don't
pay
for
stopping
Nash
buddies,
oh
yeah!
G
This
is
this
is
the
way
that
you
know
early
on
the
stream.
You
would
send
this.
You
know
with
your
initial
keyframe,
basically
indicating
here
stuff,
that's
going
to
be
set
right
now
and
if
the
metal
box
then
decides
hey,
I'm
gonna
actually
started
pouring
the
base
layer
only
or
basic
plus
enhancement.
They
can
update
the
scale.
That
is
structured
and
say
here
are
the
layers
that
he
was
a
endpoint
Lashley
receiving,
and
then
you
can
decide
from
your
decoder.
Will
you
act
when
you
should
actually
emit
a
frame?
A
A
A
A
G
I
mean
we
went
up
to
figure
out
kind
of
how
we
have
this
preset
structure
the
Gotham
neck
stuff
with
like
out,
because
that
hasn't
explicit
E&P
feel
as
opposed
to
my
heavily
implicit
from
like
the
cough
structure,
but
yet
a
spit.
What
the
s
number
is
always
independent
and,
as
you
know,
occupied
by
three
kids,
okay,.
G
See
you
know,
p
p9
and
we
have
actually
be
non-running
side.
Chrome,
it's
a
behind
a
flag.
This
is
not
turn
on
by
default,
but
getting
the
packetization
so
standardized
as
one
of
the
things
that's
keeping
us
from
acting
front
of
the
switch
we
like
to
see
this
adopted
as
a
working
group
I,
don't
so
that
we
can
then
sort
of
give
us
on
the
standards
track
and
turn
into
an
RC.
Ok,.
C
So
again,
I
think
in
terms
of
in
general
terms,
I
mean
it's
in
disappeared
for
Matamata
pyramid
for
codec,
so
I
don't
see
any
anyone
thinks
that
it's
not
part
of
the
payload
working
group
took
another
pair
after
deep
enough
of
everything
that
I
don't
think.
So
anyone
objecting
that
it
said
item
for
the
working
group
to
work
on
anyway,
who
supports
that
is
working
for
the
working
toward
you
bring
work
going
ok,
so
we
will
ask
for
a
milestone
for
that
and
we'll
start
to
work
into
the
working
group
document.