See also: IRC log
Yves: propose to have it 1 hour later, but we should ask it to Silvia
raphael: any problems if it starts 1 hour later?
<mhausenblas> I'm fine with one hour later
raphael: proposal to start the telecon at 10:00 UTC
<mhausenblas> +1
<erik> +1
<scribe> ACTION: yves to make a poll for suggestions for telecon hour: 10:00UTC or 9:30UTC [recorded in http://www.w3.org/2008/11/05-mediafrag-minutes.html#action01]
<trackbot> Created ACTION-9 - Make a poll for suggestions for telecon hour: 10:00UTC or 9:30UTC [on Yves Lafon - due 2008-11-12].
<erik> +1
<Gui> +1
raphael: any objections for minutes (phoneconf and f2f)
<erik> +1
<mhausenblas> fine with me - no objections
jackjansen: I did not scribe all day
raphael: minutes accepted
... goes through the action items
raphael: encourages to fill the questionnaire
<rtroncy> michael, please fill http://www.w3.org/2002/09/wbs/42785/MFRAGF2F2/
<mhausenblas> ok
erik: please make your arrangement asap (preferable before 8/11/2008)
raphael: no agenda yet, suggestions are welcome
<Gui> http://www.w3.org/2008/WebVideo/Fragments/wiki/GhentLogistic
1. Use cases and requirements draft (Silvia)
raphael: take time to read it and
provide some comments
... any comments yet?
... suggest to take 2 nominates to review this document
jackjansen: I will volunteer
Guillaume: I will also review it
<scribe> ACTION: jackjansen and Gui to review the use cases and requirements draft [recorded in http://www.w3.org/2008/11/05-mediafrag-minutes.html#action02]
<trackbot> Sorry, couldn't find user - Jack
2. Types of Fragment addressing (guillaume)
raphael: idea was to describe 4 dimensions to address fragments
guillaume: description of possibilities of media types and these dimensions
yves: regarding linking to a
parent resource
... I will look more deeply into that next week
3. HTTP implementation (Raphael)
raphael: more information next
week
... 3th protocol: file implementation
<Gui> ://
s/file/file://
<Yves> file always get the full result, so identifying fragment forces seeking
<rtroncy> 4. RTSP implementation (davy)
<rtroncy> See: http://www.w3.org/2008/WebVideo/Fragments/wiki/RTSP_implementation
<rtroncy> Davy: I describe how to address a track and a temporal fragment in rtsp
<rtroncy> ... some feedback would be nice
<rtroncy> ... is there any more specialist of rtsp in the room?
<rtroncy> Jack: I will read it!
<rtroncy> ACTION: Jack to review the RTSP implementation document [recorded in http://www.w3.org/2008/11/05-mediafrag-minutes.html#action03]
<trackbot> Created ACTION-10 - Review the RTSP implementation document [on Jack Jansen - due 2008-11-12].
5. existing technologies survey (erik)
raphael: merge this to the state of the art page
erik: I can only look at it from
15/11/2008
... it will be ready at second F2F
Guillaume: how to give feedback on drafts?
raphael: write mail to the
mailinglist
... provide the version you have reviewed
... give comments section per section
raphael: caching discussion
... time ranges is really hard
<rtroncy> Jack: i think time is complex and cache should not necessary try to understand time ... thus only cache bytes range
<rtroncy> Davy: I do not say exactly the contrary, but i'm arguing about implementation
<rtroncy> Jack: caching time ranges requires cache server to do recombination ... so have knowledge about the various media container formats
yves: implementation hard or not, if we no it can be done, than there is no problem
Jack: caching based on byte offsets will work on 99% of the cases
<rtroncy> Yves: when the implementation is done ... it is done! We know it can be done ... implementation difficulty should not influence the design
jack: it would work with time ranges, but I see no advantages
Yves: with time ranges, you can directly request the fragment
jack: I fully agree
... I think we should leave this issue open
raphael: more discussion on the mailinglist
<erik> +q
<Yves> regrets for me next week (HTTP meeting)
<rtroncy> thanks davy for the scribing
<rtroncy> close ACTION-7
<trackbot> ACTION-7 Request a new time slot on the Zakim bridge closed