1. In Chicago we met near the Loop, To share the security scoop … Techies search for the clues, While the rest of us schmooze And that’s why they call it Stone Soup! Gavin Eadie, CSG Poet Laureate

2. Who’s Who in the Directory  State of the join-t with Directories  Penn State (20 min)  Minnesota (20 min)  Cornell (20 min)  Georgetown (20 min)  Wisconsin (20 min)  Cornell (15 min)  Threads and Common Solutions (panel?)

3. NSF Middleware Initiative R1  If you haven’t heard yet, 5/7/2002  http://www.nsf-middleware.org  Various components, not listed here  Directory specific  Groups Practices (RPR)  Metadirectories Practices (RPR)  eduPerson 1.5 (RPR) and eduOrg 1.0 (EXP)  LDAP-Recipe 2.0 (RPR)  commObject 1.0 (RPR)

4. Suggested Issues  Service Provisioning  Classes of Service  policy, attribute mgmt, state transitions, timing, deferrals, dependencies  Central Mgmt vs. Delegated Admin  Auto vs. Self selection of service (eligibility issues)  License mgmt  Groups: directory enabled apps  Unix Services, File systems, etc…  Directory as a source of data, maybe not dir enabled.

5.  Who has directory policy?  What would a directory policy say?  Who is not doing ent-dir/Kerb/win2k integration?  Who is not doing Internet2 core middleware? Person registry, yada yada?  How do you handle derivatives (spouses, visitors, special folk, not in core systems)?  Real-time identity mgmt anyone?

6.  I see dead people (logically and real)  How is ID mgmt done? Person registry  What apps are dir enabled?  When and how for enterprise identity mgmt infrastructure?  Going beyond people?  GRID integration anyone?  Are Directories part of the I in PKI?

7. Noted Issues from discussion  Levels of visibility (prvt, cmnty, wrld)  Why Paper Directories still?  Departmental Listings and Job Titles  Emergency information  Harvesting (difficult problems, policy)  Opt-in (managed data) vs. Opt-out  Note: diff between visibility and access  Dead people: important problem space  Attribute usage (firewalling, good app practices)  Is ID mgmt properly positioned with clout?  Library integration and population mgmt

8. Common Threads  Person Registry unites core business systems, implements identity mgmt functions and “publishes” data  Homegrown and “buy and build” solutions for Person Registry and ID integration/mgmt.  Identity mgmt implies marketing and PR  LDAP AuthN and attr repository for apps  Not just for white pages anymore  Not much policy