jason: is the
'currentSegmentDownload' a best guess of seconds based
percentage? or real seconds?

Duncan: best guess based on
average bitrate

Schedule

Clarke: deadline of Dec 15 for
HTML5
... we should work offline to get our proposal tight and use
wikipage to send recommendations

MarkW: unlikely that timeframe is
possible
... benefit of approach 3 is enable experimentation....
... only add details to approach 1 to just report bitrate
selected

Clarke: we could get everything
into html5, or try to influence implementations that drive back
to standards

Duncan: setting the level
valuable, and querying the available levels

Kilroy: there need to be ability
to set max bitrate ceiling, but beyond that requires more event
feedback to enable heuristics
... at early state of adaptive streaming, enabling apporach 3
(all in JS) gives advantages

MarkW: unlikely HTML5 group may
accept

<ph> proposed resolution: go
for option 1

<mav> Kilroy, do you think
option 3, as you described, can be proposed by 12/15?

MarkW: timing of socializing this
is issue

Clarke: let's continue the
discussion using the mailing list and the wiki by Tuesday

<mav> What exactly has to be
complete by 12/15? Does the proposal need to be finalized?
Socialized?