Page Comparison

...

1. Administration:
   
   1. Roll Call
   2. Agenda Confirmation
   3. Call times - results of doodle poll: 7:30 PT / 10:30 ET / 15:30 UTC every second Wednesday starting 9 January 2013
   4. Call for nominations
      
      1. Chair - 1 nomination = Allan Foster
      2. Vice-Chair - 1 nominations nomination = Sal D'Agostino
2. Discussion / Action Item Review
   
   1. Attribute ecosystem - see Reference Docs on the bottom of the Scalable Privacy wiki page @ Internet2
      
      1. Discussion of Attribute Ecosystem issues
      2. Attribute Ecosystem slides
      3. Attribute Design Considerations I-D
3. AOB
4. Adjourn

Attendees

• Steve Olshansky
• Allan Foster

Quorum is 6 of 11 as of 20 November 2012

Non-Voting

• Ken Dagg
• Ken Klingenstein
• Sal D'Agostino
• Keith Hazelton

Staff

• Heather Flanagan (scribe)

...

• Call times
  
  • Calls will be bi-weekly; may change as further input is received from the group and a doodle poll created; for immediate purposes, we will have our next call in 2 weeks at this time
• Nominations
  
  • will send out an e-vote immediately after this call

Action Items

Discussion

...

New Action Items

Discussion

Attribute ecosystem - see Reference Docs on the bottom of the Scalable Privacy wiki page @ Internet2

1. Discussion of Attribute Ecosystem issues
2. Attribute Ecosystem slides
3. Attribute Design Considerations I-D

Beginning with the attribute ecosystem slides, and from there we can go a bit in to the discussion topics.

will be able to easily show 2 kinds of flow (and eventually more) : flows of attributes as distinct from flows in trust about the attributes; the slide deck will continue to evolve as we explore different aspects of the environment

• pay particular attention to slides 2 & 3 (high level elements and first stab at definitions) - is anything missing from this list of elements, and can we wordsmith the individual framing of terms?
  
  • KD: would like to introduce a difference between User (individual asserting attrib about a Subject) and a Subject (to whom attributes relate); in situations of powers of attorney where people are acting on behalf of others, it becomes very confusing to try and determine who we are talking about if we just have "User"
  • KK: not every user will need a Subject defined, so would need to go to the attribute ecosystem and have a bunch of users in the overall big picture, and then a few users with a subject associated with them; does Guardian also capture this idea?
    
    • KD: only case where that might not be true is in Law Enforcement, where a Law Enforcement official may be dealing with a Subject who is not a Guardian
    • SteveO: is the concern that if we use a term like "Agent" that would devolve in to too many rat holes?
• next thing to happen in this space will be for Ken K. to create flows in this ecosystem; we know that attributes are flowing in this ecosystem, and so is trust; there are also consent flows which may (or may not) be the same as trust; in both cases (trust and consent), data and metadata are both flowing along similar paths
  • note the last slide, "Decomposing Google" as a way to describe how one player may have so many roles

Any Other Business... Adjourn

...