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-53) Identity assurance

    [ https://issues.oasis-open.org/browse/COEL-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62770#comment-62770 ] 

Joss Langford commented on COEL-53:

In discussion on 17 June we agreed that the best approach would be to leave the current structure as is and add COEL classes for the assurance of identity and then atoms can be created when this occurs. This is more flexible than combining with the Segment Data as it allows for identity proofing after initial registration.

The COEL IDA function is for a system-anonymous assertion of sameness that an Operator can link to a strong identity if they require. 

ACTION: conduct an assessment of the security of IDA unique pseudonymous keys within the system to identify weakest areas and identify any simple changes that could be made to the specification. 

ACTION: identify additional COEL classes for identity assurance - processes and levels.

> Identity assurance
> ------------------
>                 Key: COEL-53
>                 URL: https://issues.oasis-open.org/browse/COEL-53
>             Project: OASIS Classification of Everyday Living (COEL) TC
>          Issue Type: Bug
>            Reporter: David Snelling
>            Assignee: Joss Langford
> Only the Operator controls of assurance of identity. The pairing between Operator and Consumer dictates the quality of the atoms in the ecosystem. A range is of atom qualities is acceptable but knowledge of the quality level will help with analysis.

This message was sent by Atlassian JIRA

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