<scribe> Scribe: Clarke

Juhani, if you want to take over scribe (or just assist) that would be great.

<Russell_Berkoff> http://www.w3.org/2011/webtv/wiki/MPTF/MPTF_Discussions/Delivery_in_distribution_windows

Bob: I don't think we should form requirements around a CE-2014 model
... HTML5 is quite different
... Make it more generic to user agents

Topic is Issue-40

Issue-40

Russell: Going through updated items in use case

Bob: I agree with #2, I'm just trying to generalize it

Russell: #5 needs to be able to decrypt media
... This is really just the requirements from CEA-2014, not the implementation

Bob: Should we work #5 differently - DRM agent needs to work with a player
... I will write up some specific language and send to the reflector

<scribe> ACTION: Bob to update text on issue-40 [recorded in http://www.w3.org/2011/09/15-webtv-minutes.html#action01]

<trackbot> Sorry, amibiguous username (more than one match) - Bob

<trackbot> Try using a different identifier, such as family name or username (eg. bbrummer, blund3)

Bob: combining issues 18 and 39.
... differences in approach- list of items from cable industry and DLNA Bob-what does user agent need to do. Jan- more generic perspective in MPEG2 transport stream
... There is overlap. Jan's approach looks at it in a non-TV-specific manner
... Still work in progress
... New use case: issue-51 is merged version of issues 40 and 41

issue-51: http://www.w3.org/2011/webtv/wiki/MPTF/MPTF_Discussions/Delivery_to_ip

<trackbot> ISSUE-51 notes added

Bob: Issue-51 discusses range of devices from very open to very closed
... software, general purpose, field upgradeability, hardware support for content protection

<Juhani> +1

Clarke: correction- issue 51 replaces issues 42 and 43, not 40 and 41

Bob: will update both general requirements also
... Then will discuss what needs to be standardized
... DECE update
... Had discussion with Jim Taylor
... has DECE thought much about HTML implementation?
... supports streaming through LASPT
... identifies DECE approved streaming and content mechanisms for DECE content
... are not in general based on DECE CFF or common encryption mechanisms
... starting to discuss streaming format of DASH to address this problem
... Jim thought if HTML5 is just starting this, then DECE would want to support new format rather than existing LASPT formats

<scribe> ...New native streaming format is preferable and likely to be available everywhere

Do they want to participate directly?

Bob: yes

DECE link: http://www.uvvu.com/contact-us.php

Bob: you can get DECE documents from that link
... Look at system specification
... also has client requirements
... Common File Format (CFF) spec
... LASPT licensee requirements
... Those 3 documents are most important
... Jim is going to see about getting a formal liaison with W3C and DECE
... Jim would want to participate in this group
... DECE looking at becoming W3C member
... my suggestion is to invite Jim to participate as invited expert for now

I agree

issue 45: http://www.w3.org/2011/webtv/wiki/MPTF/MPTF_Discussions/Continuous_Streaming_2

issue 46: http://www.w3.org/2011/webtv/wiki/MPTF/MPTF_Discussions/Time_Synchronization

issue 46: http://www.w3.org/2011/webtv/wiki/MPTF/MPTF_Discussions/Program_Boundary

Initial 46 was 45 and initial 45 was 44

<scribe> ACTION: Clarke to work with bob on general language for issue 44 continuous update of "infinite" playlist [recorded in http://www.w3.org/2011/09/15-webtv-minutes.html#action02]

<trackbot> Created ACTION-78 - Work with bob on general language for issue 44 continuous update of "infinite" playlist [on Clarke Stevens - due 2011-09-22].

Should this be tied to manifest file?

Duncan: make a reference to DASH/manifest file example

Suggestion to adopt use case pending accurate updates

No objections noted

Duncan: Maybe add examples to issue-45

Bob: point out that HTML5 base for timed text tracks needs to work consistently for indefinite length streams

Russell: needs to be consistent with external clock?

Bob: just needs to be maintained for video tag
... it's clear for file-based content
... less clear for infinite streams
... need to make sure that's clear.

This is scribe.perl Revision: 1.136  of Date: 2011/05/12 12:01:43  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: Clarke
Inferring ScribeNick: Clarke
Default Present: Alex_Chen, +1.404.242.aaaa, +358.405.81aabb, +358.405.81aacc, +358.405.81aadd
Present: Alex_Chen +1.404.242.aaaa +358.405.81aabb +358.405.81aacc +358.405.81aadd
Agenda: http://www.w3.org/2011/webtv/wiki/MPTF/Agenda_Telco_15th_September_2011
Got date from IRC log name: 15 Sep 2011
Guessing minutes URL: http://www.w3.org/2011/09/15-webtv-minutes.html
People with action items: bob clarke