<glennd> The 7-1-15 Minutes were approved without change
<glennd> Review of Action Items from previous call
<glennd> Ingest was added to the diagram per last meeting discussion. Also added Enterprise/CDN operated edge cache bubble to the Smart Edge (Glass of Viewing)
<nilo> Shouldn’t CDN be added to the Distribute bubble in Core block?
Action Item – Glenn to add CDN to Distribute bubble in Core block
There were no other comments
<glennd> A viewing device is accessing content from a source on the network. A cache exists on the network which may have some or all of the content elements. The viewing device connects to the cache and queries the cache for the content source using a URI which contains the content identifier and segment identification for the sought content element. If the content element is not in cache, the device will get the content from the original source Caches assist in obtaining content. May be multiple caches. Caches may have all or part of content. If viewing device does not find content on an advertised cache, it will get the content from the original source.
There was no further discussion
<glennd> A viewing device is accessing content from a source on the network. A cache exists on the local network but the device is not aware of the cache. The cache advertises itself on the local network so that it maybe discovered by devices. The device finds the cache and adds it to its list of known caches. The viewing device connects to the cache and queries the cache for the content source using a URI which contains the content identifier and segment identification for the sought content element. If the content element is not in cache, the device will get the content from the original source . In UC-1 there is no discussion on how device finds a cache. Cache exists on local network, advertises itself.
<digitaldale> What constitutes a cache? How does it advertise itself – as what?
<nilo> Since it is on local network, there are some local network services that do advertise themselves like UPnP/DLNA
<glennd> DLNA has a content source but is this really a cache or a source?
<nilo> A device can identify itself as a source. DLNA has concept of gateway or media server that caches content. Local devices can discover and obtain media. The media server is essentially a cache since it may or may not have the complete file.
Action Item: Glenn will add note on DLNA and any other services that may fall into this category in the gap section.
<glennd> We can go into it further when discussing UCs in more detail, gap analysis
<glennd> Submit additional UCs as members think of them
<nilo> Content items may be interposed within other content to create the version that is streamed to the end consumer such as linear TV, video-on-demand, where previews and advertisements can be placed before, after and within the main content item. The number, position and length of these interstitial content items are determined by business agreements between the actors identified below. There are standards such as Ad-ID, EIDR, that can identify the ad and content respectively. SMPTE is working on a specification to insert such identifiers into content items. SCTE has defined specs for signaling position of interstitials and alternative content.
<glennd> I understand SCTE only applies to broadcast, not web TV
<nilo> Not OTA broadcast but by cable, others.
Action Item: Nilo will add note Streaming UC-4 as to what types of content SCTE is applicable to.
<glennd> For user generated content, are there standards that can be used? YouTube allows ads between content items, not within the content
<nilo> Could be done in principle but not used.
Action Item: Nilo will add note to Streaming UC-4 about standards for e.g. inserting ads in YouTube content.
<glennd> Could see the need for longer form user content
<glennd> Is there any additional information that should be passed onto GGIE members about the upcoming Web and TV IG TPAC meeting?
<kaz> Time, date. Speak to chairs of TV Content, others, about items they may want to add to the meeting
<glennd> Need to start thinking about issues for 2016 that GGIE should address so we can begin to schedule
Next call: July 29th at 11:00 AM ET.
<glennd> If anyone will be at the IETF meetings in Prague the week of July 19 please contact me.