Child pages
  • IRM in the Wild

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

A Look At IRM in the Wild

The following table is a working document which reflects the various "IRM in the Wild" use cases the IRM WG is discussing and how each applies to the IRM Principles as they are currently defined.

Table of Contents
minLevel2


 

Use/Business Cases Explored

PrinciplesMigrationIoTConnected Road to/from CarDNS

Block Chain

(e.g., OneName, NameCoin)
Distributed HashesPromise TheoryOntology
  SalesForceStrong Device Identity (SDID) - Low Computing PowerSDID - High Computing Power      
Is there a role for a Relationship Manager?YesYesYesYesYes    yes (basically, this is the role of the ontology engine here)
Scalable
Status
colourGreen
titleFully

Status
colourYellow
titlePartial

Reality of IoT

Raw device data stream, vs. identity (asset token)

Status
colourGreen
titleFully

Has to be

Status
colourGreen
titleFully

Has to be

Status
colourYellow
titlePartial

Yes - Road handles multiple cars but traffic and road usage is applied

Status
colourGreen
titleFully

v4, v6

Status
colourGreen
titleFully

  

Status
colourYellow
titleABox
instances, wip

Status
colourGreen
titleTBOX
rules

Actionable
Status
colourYellow
titlePartial

Status
colourGreen
titleFully

By the nature of the of the asset token and platform

Status
colourYellow
titlePartial

 

Status
colourGreen
titleFully

 

Status
colourGreen
titleFully

Status
colourGreen
titleFully

IANA, Registration

Status
colourYellow
titlePartial

  

Status
colourGreen
titleFully

Defined in TBox

(Im)Mutable
Status
colourYellow
titlePartial

Status
colourGreen
titleFully

Depends on info available from the device

Status
colourYellow
titlePartial

Status
colourGreen
titleFully

Push - TBD

Status
colourGreen
titleFully

Immutable/Proxy/Forwarding

Status
colourGreen
titleFully

  

Status
colourGreen
titleFully

TBox ->'Reasoner' ->ABox
Contextual
Status
colourGreen
titleFully

Status
colourGreen
titleFully

Depends on constraints of the device

Nothing that excludes this

Status
colourGreen
titleFully
Status
colourGreen
titleFully
Status
colourGreen
titleFully

Status
colourGreen
titleFully

Actually provides context

 

Status
colourYellow
titlePartial

  

Status
colourGreen
titleFully

TBox ->'Reasoner' ->ABox
Transferrable (Delegation)
Status
colourRed
titleNone

Status
colourYellow
titlePartial

As token of "agency"

Need to re-mint token (new JWT)

Status
colourYellow
titlePartial

In terms of Ownership NOT Identity Change (Change vs. Transfer)

Status
colourYellow
titlePartial

In terms of Ownership NOT Identity Change (Change vs. Transfer)

Status
colourRed
titleNone
- Today

Status
colourYellow
titlePartial
- in the Future - when automated vehicles are on the roads

Status
colourGreen
titleFully

Bought, Forwarded

Status
colourGreen
titleFully

  

Status
colourGreen
titleFully

Ontology referentials
Provable
Status
colourYellow
titlePartial

Status
colourGreen
titleFully

If HoK (signed JWT via JOSE)

Status
colourYellow
titlePartial

Requires gateway

Status
colourGreen
titleFully
Status
colourGreen
titleFully

Status
colourGreen
titleFully

w/HTTPS DNSSEC

Status
colourGreen
titleFully

  

Status
colourGreen
titleFully

Ontology referentials
Acknowledgable
Status
colourYellow
titlePartial

Status
colourGreen
titleFully

Allows it to be assigned, you can show this

Status
colourYellow
titlePartial

As capable as the device is

Status
colourGreen
titleFully
Status
colourGreen
titleFully

Status
colourGreen
titleFully

NMAP, other

Status
colourGreen
titleFully

  

Status
colourGreen
titleFully

Ontology referentials
Revocable
Status
colourYellow
titlePartial

Status
colourGreen
titleFully

Delete the token, there is an endpoint for access token status

Status
colourRed
titleNone
Status
colourGreen
titlefully
Status
colourGreen
titlefully
Status
colourYellow
titlePartial

Status
colourGreen
titleFully

(although challenging for the right-to-be-forgotten)

  

Status
colourGreen
titleFully

Ontology referentials
Constrainable
Status
colourYellow
titlePartial

Status
colourYellow
titlePartial

From the device perspective - not referring to back-end

Status
colourYellow
titlePartial

Difficult to add constraints - limited options

Status
colourGreen
titlefully
Status
colourYellow
titlePartial

Status
colourGreen
titleFully

Subnets, Domains, etc.

Status
colourGreen
titleFully

  

Status
colourGreen
titleFully

Ontology referentials

TBox ->'Reasoner' ->ABox


 

Architecture Notions

NotionNotes/Comments
Scope it/ Profile 
Bounded for use/links to the real worldSAML, UMA?
Are components a viable approach?

OAuth/JWTs

OpenID Connect

At the IdP layer as backend or data store, "contextual identity store"

Can't change the apps

Hack the IdP

Hack the manager be it the IdP or the AS

Is it a rule generator?

"Contextual claims compiler"

Co-opt the IdP

Human Understandable

 
Are there simplifying assumptions? 
IRM provides the context for AuthZ? 
Build up the attributes from IdP in order to meet need for a claim 
Semantic aspects 
Autonomous 
Distributed Ledgers