Higher Ed Deliverables

This is meant to be a collaborative area to arrive at the deliverables we have promised the Mellon Foundation for the next CSG meeting. The meeting is scheduled for May 7-9th. This means we need to have the deliverables completed by April 23rd.

Regular weekly meeting: 2pm Thurs

Grant Status: Approved

Latest news: Our Mellon champion, Ira Fuchs, is going to present to his board to get approval for our initial grant. This will take place in mid-march.

Mellon Grant PR: MellonGrantPR

CSG Status: Mitchell has got Jack to identify 17 domain specialists. Jack is in the process of dividing them into our 7 topic areas

Chao sent out email requesting domain specialists to nail down scope of deliverables and to answer a mini-survey about inter-operability for Lou.

Documents:

• Higher Ed Application Surveys
• Meeting notes: NYC Dec, Berkeley Jan

Topics Areas [topic owners in brackets]:

• Identity, Authentication and Authorization [Aleks]
• Security [Aleks]
• Email [Ducky]
• Calendar [Katie]
• Contacts [Aleks]
• Inter-operability [Lou]
• Deployment and central-management [Pieter]

Next Steps (from 2/27/03 meeting):

• Katie to speak with Oren on questions listed on her calendar pages
• Aleks to publish security framework by next meeting
• Ducky to write up similar problem to Katie by next meeting
• Lou to write up Chandler interoperability plan with IMAP and do another rev of twiki write-up on questions to ask CSG
• Chao to check with Juergen on creating wiki area to collaborate with CSG [Talk to Juergen. He has a bugzilla task with a 3/4/03 milestone tied to it]
• Chao to check with Rys on DB requirements around sharing issues:
  • database will authenticate at attribute level access control
  • database will allow one machine to be designated as "proxy" machine and will collect workgroup sharing info such as "free/busy" time

[ I touch base with Rys and confirmed requirements for DB -chao 3/5/03]

• • what is our plan for user discovery?

Next Steps (from 2/13/03 meeting):

Topic owners (Katie, Aleks, Lou):

1. List of questions to ask domain experts on topic requirements
2. Strawman proposal for requirements as we know it today
3. Gaps that can block you from gathering requirements (e.g. sharing is ill-conceived right now)

Chao:

1. set up wiki for project communication and collaboration
2. update Ducky

Mitchell:

1. finalized list of domain specialists for each topic area with contact info from Jack McCredie
2. survey results from CIOs regarding inter-operability requirements
3. set up meeting with CIOs regarding feature requests and prioritization of features

Issues

• Need a security person for Aleks to hand over

More background info

1. LDAP Higher-Ed plan: http://www.georgetown.edu/giia/internet2/ldap-recipe/
2. Xerox PARC’s Bayou project: http://www2.parc.com/csl/projects/bayou/
3. SAML: http://www.oasis-open.org/committees/security/
4. FERPA: http://www.ed.gov/offices/OM/fpco/ferpa/
5. Internet2 Middleware Project: http://shibboleth.internet2.edu/

-- ChaoLam - 14 Feb 2003

• CSGsecurity.html: Security Meeting Notes by atotic 02/21/03

---

---

Copied from CSG Twiki by -- PieterHartsook - 24 May 2004