1 / 19

David Parrott Reuters/ Chief Technology Office 18 July 2001

Report on Reuters Response to MPEG-21 CfR Report to XACML Committee Face-to-Face Meeting. David Parrott Reuters/ Chief Technology Office 18 July 2001.

cadman-potter
Download Presentation

David Parrott Reuters/ Chief Technology Office 18 July 2001

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Report on Reuters Response to MPEG-21 CfRReport to XACML Committee Face-to-Face Meeting David Parrott Reuters/Chief Technology Office18July 2001 This presentation is a report of a meeting between Dr David Parrott of the Reuters Chief Technology Office and the XACML Committee which took place on 18 July 2001. The contents of this presentation relate to a fuller paper submitted as Reuters response to the MPEG-21 call for requirements (ISO/IEC JTC1/SC29/WG11 N4044: "Reissue of the Call for Requirements for a Rights Data Dictionary and a Rights Expression Language" dated March 2001) on 1 June 2001. The full MPEG submission contains greater detail of the issues, and the context in which the statements contained in the presentation are made. The full response submitted by Reuters on 1 June 2001 can be found at http://www.oasis-open.org/committees/xacml/docs/response-v1.0-public.doc. This presentation and the statements contained within it do not necessarily reflect Reuters current or future policy, position or plans in relation to the topics discussed, nor does it purport to cover all the relevant topics in this area. Reuters accepts no responsibility for the consequences of any reliance placed on the contents of this presentation.

  2. The Permissioning Problem Reuters Today • Private networks give tight access control • Reuters client-site components allow fine-grained permissions • Control is reduced on satellite feeds • Many data types, all with different permissioning models and implementations • Heavyweight subscription contracts.

  3. Digital Rights Management (DRM) • Managing: • Rights (IPRs, Permissions, Access Controls, Usage, etc)… • Obligations… • Audit trails… • … across the entire value chain (of IPR creators, publishers, distributors, consumers…) • Electronic, machine-readable contracts • In equal measures: • Legal Infrastructure • Business Infrastructure • Technology Infrastructure.

  4. Many Approaches to DRM • Standardised Markup for Expressing Rights and Obligations • Detection of IPR Infringement • Watermarking • Fingerprinting/Traitor Tracing • Tracking/Searching • Rights and Obligations Enforcement • Permissioning and Access Control (encryption technologies if appropriate) • Licensing and contracts • Sandboxes (protected environments).

  5. Why are we Interested in Digital Rights Management? Reuters needs to permission its data and protect its IPR… • Data is inherently valuable • Unified approach across “Slice and dice” service offerings • Unified approach across flexible and varied distribution channels • e.g., proprietary networks, satellite broadcast, public Internet • Broadcast mode delivery is required in many cases for scalability • permissioning restricts access to just those parts paid for • Third party content comes with complex and exacting distribution rules • plus regulatory requirements • Data flows are multi-directional and include contribution rights.

  6. DRM Rules & Consequences Content Encryption What Digital Rights Management is NOT (i) It is not just enforcement by locking up content in a layer of encryption • Restricted Actions: • View, Print, Save, … • No “fair use” • B2C dominated • Security/Trust Problems: • Software inherently unsafe • Trusted applications restrictive • Vulnerable to systematic attack • Proprietary Implementations: • Lacking interoperability • Closed user-base • Risk backing the wrong player

  7. . . . . . . Service Provision Reuters Channel Partner (Schwab) Value Add Data feed Processing Real-Time Customer (Banks) News feed Customer (Yahoo!) Custom Analytics Auto Trading Risk Mgmt . . . . . . What Digital Rights Management is NOT (ii) It is NOT the exclusive domain of “Eyes and Ears” B2C data delivery Vs

  8. T R U S T T R U S T Content, Permissions, Obligations, and Trust Permissions The most you can do with content Obligations The least you must do in order to gain access

  9. MPEG-21 • Content • Creation and Production • Distribution • Consumption and Usage • Packaging • Identification and Description • Representation • Intellectual Property Management and Protection • Financial Management • User Privacy • Resource Abstraction • Event Reporting

  10. Rights Expressions Everywhere Contributors Reuters Systems And Products Distributors Network Service Providers Customers

  11. Rules Rules Rules “Straight-Through” Rules Processing Contributors Reuters Systems And Products Distributors Network Service Providers Customers Rules

  12. Relational Database Web Access E-commerce Admin (Directories) Billing Real-Time Permissioning Microsoft Exchange Unified Rules Definitions Contributors Reuters Systems And Products Distributors Network Service Providers Customers Policies and Rules

  13. Requirements for Rights Data Dictionary & Rights Expression Language 3.1REQUIREMENTS FOR THE STRUCTURE OF THE STANDARD 3.1.1Division of the Standard into an Extensible Core and Standard Prelude 3.1.2 Inclusivity

  14. Requirements for Rights Data Dictionary & Rights Expression Language 3.2REQUIREMENTS FOR RIGHTS STRUCTURE AND MANAGEMENT 3.2.1 The Relationships between Rights and Obligations 3.2.2 Rights and Obligations Transfer (Inheritance) 3.2.3 Rights and Content Independence 3.2.4 The Types of Content over which Rights and Obligations Apply 3.2.5 Matching Rights and Obligations to Digital Objects 3.2.6 Matching Rights to Contexts 3.2.7 Location, Form, and Access Control of Data Dictionaries 3.2.8 Management of Issued Rights and Obligations 3.2.9 Fail-Over and Behaviour Modification 3.2.10 Privacy of Terms Expressed in the Language and Data Dictionary 3.2.11 Expression Evaluation

  15. Requirements for Rights Data Dictionary & Rights Expression Language 3.3REQUIREMENTS FOR RIGHTS AND OBLIGATIONS DEFINITIONS 3.3.1 Operational Specifications 3.3.2 Reporting 3.3.3 Acknowledgement of Source 3.3.4 Rights and Obligations for Real-Time Data 3.3.5 Rights and Obligations for a Stream of Digital Objects 3.3.6 Rights and Obligations for Transactional Data 3.3.7 Rights and Obligations for Database or Server Access 3.3.8 Usage Rights 3.3.9 Managing Communities 3.3.10 Contract Management 3.3.11 Business Models

  16. Requirements for Rights Data Dictionary & Rights Expression Language 3.4ATTRIBUTES ON WHICH RIGHTS AND OBLIGATIONS ARE PREDICATED 3.4.1 Temporal 3.4.2 Geographic 3.4.3 Environmental

  17. Requirements for Rights Data Dictionary & Rights Expression Language 3.5REQUIREMENTS PERTAINING TO TRUST 3.5.1 Identification of Trusted Entities 3.5.2 Trusted Time Services 3.5.3 Trusted Applications and Environments 3.5.4 Certifiable Audit Trails 3.5.5 Agent Authentication 3.5.6 Data Integrity 3.5.7 Agent Mandated Privacy 3.5.8 Confidentiality

  18. Requirements for Rights Data Dictionary & Rights Expression Language 3.6ADDITIONAL FUNCTIONAL REQUIREMENTS 3.6.1 Specialised Support for Business to Business (B2B) Commerce 3.6.2 Machine Processing of Digital Objects

  19. Requirements for Rights Data Dictionary & Rights Expression Language 4OTHER AREAS FOR CONSIDERATION IN BUILDING THE STANDARD 4.1 CHANNEL DEFINITION 4.2 OBJECT MODELS 4.3 WORKFLOW

More Related