14
SCC Activities C. Tilton

SCC Activities C. Tilton. Standards Are applied to SOMETHING Within some CONTEXT Something = ID Ecosystem Context = Use Cases 2

Embed Size (px)

Citation preview

SCC Activities

C. Tilton

2

Standards

• Are applied to SOMETHING• Within some CONTEXT

• Something = ID Ecosystem• Context = Use Cases

3

WorkplanPriority Work Item Lead

1 Use Cases S. Shorter2 Standards Adoption Policy J. Clark3a Standards Inventory S. Shorter3b Catalog of Terms and Definitions S. Shorter4 Inputs to the Identity Ecosystem

Functional ModelG. Whitehead & P. Brown

5 IDESG Accepted Terms and Definitions P. Brown6 Standards Gap Analysis TBD7 IDEF Standards Registry TBD

4

Cross-IDESG efforts

Vocabulary Use Cases

Functional Model Standards

5

Approach

Inventory IDEF Artifact

Catalog what already exists Approved Work Products

• Contributions from across IDESG• Maintained in accessible form

• Approved versions• Used across IDESG• Revised periodically• Part of ID Ecosystem Framework

6

SCC Role in Use Cases

• Recognized need & stepped forward as coordinator• Like all SCC activities/work products, IDESG is the

consumer – SCC is the enabler– IDESG must be an active participant (contribute,

comment, approve)– Collaborative process must be defined

• We have provided a starting point– Draft use case document and template [ready for MC

review, provided to all Chairs, or sent to MC] – Draft list of some potential use cases under development

7

SCC Role in Terminology

• As for Use-Cases, SCC has stepped up as enabler and coordinator

• Proposed methodology– Lightweight– Inclusive– Being finalized in response to comments

• Will start with concepts that are core to IDESG• Will maximize use of existing and agreed

terminologies

8

Functional Model

• What is a functional model of the ID Ecosystem?– A conceptual architecture– Identifies the component elements (functionally)– Identifies the relationships between these elements

• Our focus on functional model is strictly identifying the technical components and describing in some detail how the technical components work together to support Identity Ecosystem functionality.

• Starting point: – Figure 4 - Identity Ecosystem, found on page 26 of the NSTIC

document (dated April 2011).

9

Identity Ecosystem vs Identity Ecosystem Framework

10

Functional Model – 2 thrusts

• Functional model of the overall Identity Ecosystem• Generic functional model of existing IDM systems

– Enumerating relevant existing IDM systems based on open standards– Key among these include:

• ITU-T X.1250 Baseline capabilities for enhancing global identity management and interoperability using public telecommunication networks and services

• ISO/IEC 24760-1 A framework for identity management - Part 1 (also Parts 2 & 3)

• OASIS, Kantara, OpenID, etc.– Next steps:

• Synthesize a generic model representing commonality & key aspects of each IDM system considered

• Document the converged results as a baseline Functional Model most representative of existing systems

• Going forward, this Functional Model will be updated as appropriate based on technical design requirements derived from the IDESG adopted use cases for functionality and privacy protection

11

Functional Model

• The SCC is a supporting actor in this effort!

• We STRONGLY believe that this is a key IDESG activity and deserves attention.– Needs a HOME, Champion, and focused effort applied– A “sanctioned” activity

12

Status to Date

• Activities underway– Strawman

development/collaboration/ approval process flow/ definition

– Collaboration platform requirements

– Inventories (all areas)– Standards adoption policy

• Artifacts (available, but in progress)

– Draft charter– Workplan– Use Case Plan– Terminology Catalog– Standards Inventory– Comment templates

13

Approach

• Collaborate on ALL our activities and work products• Collaborate on defining the end-to-end process– 2 aspects:

• Define workflow to get to end goal• Define collaboration mechanisms

• In addition– Invite participation in the SCC Ad-Hoc Groups– Liaison/rapporteur activities– Joint meetings– Topic/work area meetings

14

Need

• Collaboration platform– In process of developing requirements set– Once draft is ready, we will share and solicit inputs

on this as well.– To be used in the context of a process