Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

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.

 

Use/Business Cases Explored

PrinciplesMigrationIoTDNS

Block Chain

(e.g., OneName, NameCoin)		Distributed HashesPromise TheoryOntology
Is there a role for a Relationship Manager?Yes      
ScalableFULLY 

FULLY

v4, v6

    
ActionablePARTIAL 

FULLY

IANA, Registration

    
(Im)MutablePARTIAL 

FULLY

Immutable/Proxy/Forwarding

    
ContextualFULLY 

FULLY

Actually provides context

    
Transferrable (Delegation)NONE 

FULLY

Bought, Forwarded

    
ProvablePARTIAL 

FULLY

w/HTTPS DNSSEC

    
AcknowledgablePARTIAL 

FULLY

NMAP, other

    
RevocablePARTIAL FULLY    
ConstrainablePARTIAL 

FULLY

Subnets, Domains, etc.

    

 

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 
  • No labels