OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

coel message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (COEL-21) MMI device reallocation, device tree & atom retrieval


     [ https://issues.oasis-open.org/browse/COEL-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Snelling updated COEL-21:
-------------------------------

    Description: 
A major concern for the regulators is the possibility of data breaches when devices move from one consumer to another. We need to specify the methods for deleting an reallocating fully and carefully.

The current assumption is that DeviceID will be swapped for ConsumerID in the Data Engine. Do all Data Engines need to do this? - probably not now that the DeviceIDs are standard IDA keys. Which approach is best to help ensure transparency? 

The MMI allows for the change to be made from one consumer to another and mandates that the old association is deleted. However, the SP has no way to validate this.

  was:
A major concern for the regulators is the possibility of data breaches when devices move from one consumer to another. We need to specify the methods for deleting an reallocating fully and carefully.

The current assumption is that DeviceID will be swapped for ConsumerID in the Data Engine. Do all Data Engines need to do this? - probably not now that the DeviceIDs are standard IDA keys. Which approach is best to help ensure transparency? 


> MMI device reallocation, device tree & atom retrieval
> -----------------------------------------------------
>
>                 Key: COEL-21
>                 URL: https://issues.oasis-open.org/browse/COEL-21
>             Project: OASIS Classification of Everyday Living (COEL) TC
>          Issue Type: New Feature
>            Reporter: Joss Langford
>            Assignee: David Snelling
>            Priority: Minor
>
> A major concern for the regulators is the possibility of data breaches when devices move from one consumer to another. We need to specify the methods for deleting an reallocating fully and carefully.
> The current assumption is that DeviceID will be swapped for ConsumerID in the Data Engine. Do all Data Engines need to do this? - probably not now that the DeviceIDs are standard IDA keys. Which approach is best to help ensure transparency? 
> The MMI allows for the change to be made from one consumer to another and mandates that the old association is deleted. However, the SP has no way to validate this.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]