July 28-30 2009 Minneapolis, MN Presentation_DECE...Agenda Item Comments Target Outcome Start Time...

DECE Face-to-Face Meeting

0DECE CONFIDENTIAL

July 28-30 2009

Minneapolis, MN

Agenda Item Comments Target Outcome Start Time

User Experience – Report from Sub-group (S. Fierstein, MSFT) Review initial E.L.

deliverables

Update 9:00 a.m. BWG

Initial DECE launch geographies (B. Fox, SPE) Follow-up on

prior discussion

Update & proposed

recommendation for

MC

9:45 a.m. BWG + LWG

BREAK 10:30 a.m.

LASP Policies• LASP Verification Language (R. Wheeler, Fox)

• LASP-specific conformance issues (J. Carey, CableLabs)

Review and agree

new proposed

language

10:45 p.m. BWG + LWG

Fraud Input & discussion 11:30 p.m. BWG + LWG

Business Working Group: Day 2

1DECE CONFIDENTIAL

• Initial Requirements Review (S. Ng, NBC/Universal)

LUNCH 12:00 p.m.

Retailer Policies and Perspectives (D. Adams, BluePrint) Discuss emerging

retailer perspectives

1:00 p.m. BWG + LWG

BREAK 2:30 p.m.

Device Policies• Review/discuss TWG questions to BWG (P. Fahn, Samsung)

• Device-specific conformance issues (J. Carey, CableLabs)

Input & discussion 2:45 p.m. BWG, LWG,

TWG

Picture Formats (S. Guthrie, ALU) Update from sub-

group

3:45 p.m. BWG + TWG

Coordinator Policies (BWG/TWG Chairs) Kickoff discussion 4:15 p.m. BWG , LWG,

TWG

ADJOURN 6:00 p.m.

User Experience – Report from Subgroup

S. Fierstein, Microsoft

2DECE CONFIDENTIAL



deliverables



prior discussion

Update & proposed

recommendation for

MC

9:45 a.m. BWG + LWG

BREAK 10:30 a.m.



Review and agree

new proposed

language




3DECE CONFIDENTIAL


LUNCH 12:00 p.m.



1:00 p.m. BWG + LWG

BREAK 2:30 p.m.




TWG


group

3:45 p.m. BWG + TWG


TWG

ADJOURN 6:00 p.m.

Initial DECE launch geographies

B. Fox, SPE

4DECE CONFIDENTIAL



deliverables



prior discussion

Update & proposed

recommendation for

MC

9:45 a.m. BWG + LWG

BREAK 10:30 a.m.



Review and agree

new proposed

language




5DECE CONFIDENTIAL


LUNCH 12:00 p.m.



1:00 p.m. BWG + LWG

BREAK 2:30 p.m.




TWG


group

3:45 p.m. BWG + TWG


TWG

ADJOURN 6:00 p.m.

LASP Policies

LASP Verification Language – R. Wheeler, Fox

LASP-specific conformance issues – J. Carey, CableLabs

6DECE CONFIDENTIAL

LASP-specific conformance issues – J. Carey, CableLabs

LASP Policies Document: Open Comments

Open Comments

• 3.1.1. After TWG completes the certification appendices to the Specifications, work with the TWG to

determine which requirements should be mandatory for certification. For example, UI guidelines may

be part of certification but may not be mandatory whereas compliance with DECE Use Cases will be

mandatory. Will DECE exercise flexibility with respect to certain requirements?

• 3.1.4. This is the body we recommend the Management Committee establish to review such appeals.

• 3.2. Fox requests verification.

• 3.3.2.1. Note to TWG: DECE Specifications should clearly indicate which provisions are "applicable to LASPs”

• 6.1.1. Should we add any other access? Give them all (the console)

• 7.1. Link LASP must make a one time link made by Administrator and binds the two accounts LASP

7DECE CONFIDENTIAL

• 7.1. Link LASP must make a one time link made by Administrator and binds the two accounts LASP

Account/DECE Account

• 8.1. Needs to be defined

• 8.2. Verify with TWG if relevant

• 11. Steve Weinstein: “In the retailer document we have the provision in this parallel paragraph about

responding to requests by the coordinator or a customer service organization for problems. I would think the

same words should be here. Unless DECE thinks that the support org will not take any calls regarding

DECE content not being available on a LASP, LASP problems with becoming a linked LASP, etc. I think this

will not be the case.”

• 12.1. LWG to add any additional privacy information it deems appropriate



deliverables



prior discussion

Update & proposed

recommendation for

MC

9:45 a.m. BWG + LWG

BREAK 10:30 a.m.



Review and agree

new proposed

language




8DECE CONFIDENTIAL


LUNCH 12:00 p.m.



1:00 p.m. BWG + LWG

BREAK 2:30 p.m.




TWG


group

3:45 p.m. BWG + TWG


TWG

ADJOURN 6:00 p.m.

Fraud

S. Ng, NBCU

9DECE CONFIDENTIAL



deliverables



prior discussion

Update & proposed

recommendation for

MC

9:45 a.m. BWG + LWG

BREAK 10:30 a.m.



Review and agree

new proposed

language




10DECE CONFIDENTIAL


LUNCH 12:00 p.m.



1:00 p.m. BWG + LWG

BREAK 2:30 p.m.




TWG


group

3:45 p.m. BWG + TWG


TWG

ADJOURN 6:00 p.m.

Retailer Policies and Perspectives

D. Adams, BluePrint

11DECE CONFIDENTIAL



deliverables



prior discussion

Update & proposed

recommendation for

MC

9:45 a.m. BWG + LWG

BREAK 10:30 a.m.



Review and agree

new proposed

language




12DECE CONFIDENTIAL


LUNCH 12:00 p.m.



1:00 p.m. BWG + LWG

BREAK 2:30 p.m.




TWG


group

3:45 p.m. BWG + TWG


TWG

ADJOURN 6:00 p.m.

Device Policies

Review/discuss TWG questions to BWG – P. Fahn, Samsung

Device-specific conformance issues – J. Carey, CableLabs

13DECE CONFIDENTIAL

Device-specific conformance issues – J. Carey, CableLabs

Device Policies Document: Open Comments

Open Comments

• 7.1. Fox verification proposal

• 8.1. Steve Weinstein subgroup examining device authentication options

14DECE CONFIDENTIAL



deliverables



prior discussion

Update & proposed

recommendation for

MC

9:45 a.m. BWG + LWG

BREAK 10:30 a.m.



Review and agree

new proposed

language




15DECE CONFIDENTIAL


LUNCH 12:00 p.m.



1:00 p.m. BWG + LWG

BREAK 2:30 p.m.




TWG


group

3:45 p.m. BWG + TWG


TWG

ADJOURN 6:00 p.m.

Implications of Content “Holdback” Periods

Next Steps Identified yesterday:

�Usage model workarounds (e.g. local solutions?)

�UX and brand impact mitigation (What “bad use cases”…how to minimize dissatisfaction from that which we can’t work around?)

�Role & Policy Implications

–Overall architecture: Coordinator, metadata

• Fleshing out issue and options

• Agree on next steps and team to do

Discussion Today

Discussion Guide

16DECE CONFIDENTIAL

–Retailers (Obligations? Functionality requirements? Promotional / customer service things they may do that architecture needs to support?)

–DSP’s and LASPs

�Further research on contractual situation and business options (Studios)

�Confirm / discuss current-market benchmark (Amazon/CinemaNow…is iTunes relevant given no locker?)

team to do them

• By when



deliverables



prior discussion

Update & proposed

recommendation for

MC

9:45 a.m. BWG + LWG

BREAK 10:30 a.m.



Review and agree

new proposed

language




17DECE CONFIDENTIAL


LUNCH 12:00 p.m.



1:00 p.m. BWG + LWG

BREAK 2:30 p.m.




TWG


group

3:45 p.m. BWG + TWG


TWG

ADJOURN 6:00 p.m.

Coordinator Policies

BWG / TWG Chairs

18DECE CONFIDENTIAL

Coordinator Policies – Potential Discussion TopicsIntentionally broad “menu” list, to be triaged for where discussion needed…

Role Confirmation What Coordinator does for…

• Account creation and maintenance

• Device registration and maintenance

• Storage and management of rights tokens

• Streaming administration

PoliciesWhat needs to be specified?

• Privacy and data management, retention policies, etc.

• Parental controls

• Transition / termination obligations (if replacement CO)

• Performance and robustness levels (e.g.

Discussion Guide

19DECE CONFIDENTIAL

• Streaming administration

• Metadata above and beyond what’s linked to a single content asset

• API construction for 3rd party web services / client SW development

• DECELLC.com website development and operation

• Other…

• Performance and robustness levels (e.g. response time / uptime / fail safes, investment in redundancy)

• Geo points-of-presence and compliance with local regulation

• Management of financial transactions

• B2B customer service and B2C customer service support

• Other…

Date post:	10-Sep-2019
Category:	Documents
Upload:	others
View:	1 times
Download:	0 times

July 28-30 2009 Minneapolis, MN Presentation_DECE...Agenda Item Comments Target Outcome Start Time...

Documents