Time restricted usage control implementation

Owned by Vineet Singh, created
Last updated: Jun 09, 2021
1 min read

Add your comments directly to the page. Include links to any relevant research, data, or feedback.

Status

In progress

Impact

High / Medium / Low

Driver

@Vineet Singh 

Approver

@Razak K M

Contributors

@Michael Lux (Unlicensed)      

Informed

@Gerd Brost (Unlicensed)@Mayank (Unlicensed)@Sagar Singh (Unlicensed)@Waseem@saureen (Unlicensed)

Due date

Jun 15, 2021

Outcome

Background

Time restricted usage control description

Options considered

 

Option 1: Time embedded in Data

Option 2: IDSCP2 in Apps

Option 3: Standardized App Inferface for UC

 

Option 1: Time embedded in Data

Option 2: IDSCP2 in Apps

Option 3: Standardized App Inferface for UC

Description

  • Header in data that has details about the time constraints

  • The application is reading the data and enforcing it

  • IDSCP2 implementation to communicate between containers (metadata and headers in IDSCP2 manage usage control)

  • Other standard apart from IDSCP2 like REST

  • The interface consumes data, policy for implementation

Pros and cons

Simplicity

  • No possiblity to or very difficult to configure on protocol level

  • Not standardized, data format is app specific

  • Standardized IDS messages

  • Configurable outside of app

  • IDSCP2 implementation required within application

  • No passing of UC to apps implemented in Connectors yet, unknown effort

  • Managable implementation effort

  • No full IDSCP2 implementation required, only REST server or similar

  • To be standardized/ implemented, especially passing from Connector to App

Estimated effort

small

Very Large

medium

Action items

Outcome