SCC Orientation Overview

1. SCC OrientationOverview C. Tilton

2. Charter(from the Rules of Association) • "The IDESG shall establish forums and procedures to review applicable standards and adopt those that support achievement of the NSTIC vision, conform to the Guiding Principles, and meet other established requirements. Additionally, the IDESG shall: • recommend standards be established when gaps are identified; and • advocate for standards to be established and adopted in a timely manner and be sufficient to keep pace with emerging technology and market trends."

3. Charter - How • The SCC will: • accomplish its work through collaboration with existing SDOs • not act as an SDO itself • investigate the need for profiles • Identify gaps in existing standards • The identification of standards will be requirements and use case driven • Based on these and identity ecosystem architecture • To this end, the SCC will work with other IDESG working groups and stakeholders

4. Standards • Are applied to SOMETHING • Within some CONTEXT • Something = ID Ecosystem • Context = Use Cases

5. Workplan

6. Ad Hoc Groups • The SCC divides its work among AHGs • Lead • Participants • Open to liaisons and non SCC members • Intent is to work/meet outside SCC meetings and report back

7. Cross-IDESG efforts

8. Approach Inventory IDEF Artifact Catalog what already exists Approved Work Products • Approved versions • Used across IDESG • Revised periodically • Part of ID Ecosystem Framework • Contributions from across IDESG • Maintained in accessible form

9. 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 • IDM model analysis • Terminology (approach) recommendations

10. 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

11. Tools • Collaboration platform • Developed requirements set • Secretariat provided MediaWiki appears to meet most of these requirements • Separate Wiki’s for use cases and terminology • In process of top level Wiki design • Will allow for input from any IDESG member • To be used in the context of a process!

12. AHG Presentations • Use cases Scott Shorter • Standards adoption Jamie Clark • Inventories Scott Shorter • Terminology Peter Brown • Functional model Graham Whitehead

13. Focus areas • Use cases Scott Shorter • Functional model Graham Whitehead • Wednesday breakout (1-3pm) • 1st hour: Workplan • 2nd hour: Collaboration process • Wednesday 5:30-7:30pm: Joint meeting with Security on Use cases, taxonomy, and functional model

14. 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 • Draft list of some potential use cases under development

15. Use Case WorkshopDraft Agenda • Introduction • Purpose of the workshop • Levels/types of use cases • Business/functional level • Concept of overlays • What’s been done so far • Use case plan • Use case template • Alternate formats • List of potential use cases • Sources of existing use cases • Example use case <privacy-enabled age verification?> • Walk through • Demonstrate use of template • Collaboration process • WikiMedia example • How do we best collaborate? • Solicitation/contribution of use cases • Commenting on use cases • [Potential:  Other groups introduce their use cases?] • IDEF use case artifact (formal deliverable)

16. 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).

17. Identity Ecosystem vs Identity Ecosystem Framework

18. Viva la difference! • Identity Ecosystem Framework • The underlying policies, procedures, standards, rules, specifications that describe and govern the identity ecosystem • Identity Ecosystem • The components that work together to perform the various roles and functions to achieve trusted online identities. • We are working to model the latter, not the former!

19. Functional Model – 2 thrusts • Functional model of the overall Identity Ecosystem • Generic functional model of existing IDM systems • Enumerating relevant existing IDM systems and standards • 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

20. 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

21. IdM Functional Models • Looked at • ISO • ITU-T • CertiPath • SAFE BioPharma • Kantara Initiative