Agenda
FINAL CSG Workshop and Meeting Agenda
The University of Virginia
12-14 May 1999
Wednesday 12 May 1999
CSG Workshop
7:45 Continental Breakfast
8:00 CSG Workshop: Schema Design
Coordinators: Bob Morgan and Paul Hill
Volunteers: Mark Poepping, Michigan, Princeton, Stanford
Please see Addendum C for the detailed agenda.
12:00 Lunch, Cold buffet, Blue Ridge/Commonwealth Rooms
1:00 CSG Workshop: Schema Design (continued)
5:00 Adjourn
Group Dinner - Boar's Head Inn
6:00 Cocktails, Patio
7:00 Dinner, Tavern
Thursday 13 May 1999
CSG Workshop and CSG Meeting
7:45 Continental breakfast
8:00 CSG Workshop: Security Organization
Coordinator: Phil Long
Volunteers: Bob Mahoney, Steve Worona, Sandy Senti, Mark Poepping
Please see Addendum D for the detailed agenda.
10:30 Adjourn
CSG Meeting
11:00 I. Introductory Remarks (Worona)
11:05 II. Long Term Issue 1: Web Application Development
Coordinator: Tim Sigmon
12:05 Lunch, Hot Buffet, Ednam Hall
CSG Meeting (continued)
1:00 III. Organizational Members Updates (Vaught)
Possible reports from:
EDUCAUSE (Katz/Luker)
Merit (Aupperle)
Net@EDU (Williams)
CREN (Boettcher)
Internet2 (Hanss)
DLF (Waters/Millman)
CIC Schools (Jackson)
JSTOR (Fuchs)
CNI (Lynch)
Others
1:45 IV. Long Term Issue 2: IT Investment Models / Financing
Coordinator: Dave Lambert
2:45 V. Short Slots (Worona)
A. Network charging survey (Bruce) [30 minutes]
3:15 Break
3:45 VI. Technology Tracking Group Reports (Worona)
The TTG's whose owners have requested time are:
TBD
5:00 Adjourn
Group Dinner - Colonnade Hotel, Garden Room, Virginia Campus
6:00 & 6:30 Bus leaves for Campus
6:15 - 7:30 Reception (Lawn tours available)
7:30 Dinner, Garden Room
9:00 & 9:30 Bus leaves for Boar's Head Inn
Friday 14 May 1999
CSG Meeting
8:15 Continental Breakfast
8:30 VII. Organizational Issues (Worona)
A. Steering/Membership Committee Issues
B. CSG Secretariat Renewal
C. Treasurer's Report
D. Logistics for Next Meeting
E. Logistics for Two Meetings Ahead
8:45 VIII. Long Term Issue 3: IT Architecture Redux
Coordinator: Ken Klingenstein
9:45 Break
10:15 IX. Long Term Issue 4: IP Telephony
Coordinator: Dave Lambert
Volunteers: Georgia, CMU, Virginia
11:15 X. Session Proposals for Next Meeting (McCredie)
12:00 Adjourn
12:00 Lunch (box lunches available)
12:00 Apple WebObjects Presentation
Please see Addendum E for details and agenda.
1:00 Adjourn
Addendum A: Candidate TTG Topics
Get in touch with Steve Worona to get a topic on the agenda, add
topics, or volunteer to coordinate open topics.
Authenticated DHCP; drop-in connections Mark Poepping
Authentication/security Bob Morgan
Campus network architectures Doug Gale
Campus network funding models Jack McCredie
Charging for printing Phil Long
Collaboration tools Steve Carmody
Community networking Ken Klingenstein
DCE Steve Kellogg
Digital Libraries David Millman, Steve Worona
Directory services Mark Poepping
Distributed computing architecture Bob Morgan
Fiber-optic connector technology Rich Kogut
E-mail Terry Gray
Human resources issues Jack McCredie
Internet-2 applications Ted Hanss
Internet-2 resource allocation Ken Klingenstein
Network Commerce Jeff Schiller, Sandy Senti
Network computers Bob Morgan
Network-based calendaring Paul Hill, Greg Jackson
Policy Steve Worona
Service level agreements Ken Klingenstein
Video Ed Sharp
Web authorization tools Sandy Senti
Why Higher Education is Different Ken Klingenstein
Wireless technologies Alex Hills
These TTG's currently have no owner:
Computer/network security (proposed by Jack McCredie)
Departmental LANs
Financial management
Higher-Ed objects
Information Technology Architecture
Internet-2 technology
Metadirectories
Version control and software distrib
WWW
Workflow
Addendum B: Current List of Members of the Common Solutions Group
* Brown University
* Carnegie Mellon University
* CNI
* Columbia University
* Cornell University
* CREN - Corporation for Research and Educational Networking
* Digital Library Federation (DLF)
* EDUCAUSE
* Georgetown University
* Harvard University
* Merit
* MIT
* Pennsylvania State University
* Princeton University
* Stanford University
* University Corporation for Advanced Internet Development
* University of California - Berkeley
* University of California - Office of the President
* University of Chicago
* University of Colorado - Boulder
* University of Maryland
* University of Michigan
* University of Utah
* University of Virginia
* University of Washington
* University of Wisconsin - Madison
* University System of Georgia
* Yale University
Addendum C: CSG Workshop: Schema Design
Detailed Agenda
CSG Workshop on Directory Service Schema Design and Data Management
In the last couple of years, several factors have come together to
cause many institutions to add Directory Service (DS) to the list of
key infrastructure services that enable campus computing (along with
IP connectivity, DNS, authentication, email, etc). Much attention has
been given to role of the Lightweight Directory Access Protocol (LDAP)
standards, and LDAP-supporting directory products, in enabling this
new infrastructure. What makes Directory Service a key component is
its potential for providing consistent management and effective
distribution of information about the fundamental data elements of the
institution: people, groups, classes, computers, services, etc. The
processes involved in defining these elements, managing the data,
getting applications to use them successfully, etc, are largely
independent of the protocols and products per se, and have been
evolving for many years. Traditionally they have been haphazard,
involving "data fiefdoms", mysterious massaging of data as it moves
between systems, misinterpreted attributes, days of delay while updates
propagate, lost entries, etc. The vision of doing better is compelling.
This workshop will focus on these processes and how to use DS
technology to improve them. We observe that the issues in this area
are very similar from one campus to the next, but that there has been
little sharing of experience due to the fact that these processes are
closely linked to campuses' unique administrative systems and business
practices. The time is ripe for moving forward together.
The scope of discussion includes:
* campus DS deployments, emphasizing schema and data-management
issues
* models and modeling methods for institutional entities and
relationships
* schema design: good examples, references, tools, standards
* support for complex (relational et al) relationships in DS
* use of vendor-supplied schema vs home-grown schema
* role of traditional RDBMS systems re DS
* role of LDAP DS re NIS, AFS, DCE, rdist, etc
* role of general-purpose DS re Novell NDS, Microsoft ADS, etc
* use of multi-directory synchronization, aka "meta-directory"
* relation of data warehouse to DS
* coexistence of white pages service with infrastructure DS
* how to do all this without using a DS
* support of "namespace" design: names, IDs, principals,
accounts, email addresses
* effective application use of DS: identification, searching,
caching, notification, etc
* commercial apps support of standard DS
* data politics: keeping owners, consumers, brokers all happy
* DS support for authorization and policy management
* DS and PKI: certs in directory, DNs and attributes in certs, etc
Presenters from MIT, Princeton, Stanford, University of Michigan, and
University of Washington (yes, the usual suspects) are scheduled.
There is the possibility of one or two vendor presentations. We
encourage presentations, or even extended rants, from any and all
other attendees. Contact rlmorgan@cac.washington.edu if you'd like a
slot or have questions. We expect a good portion of the day will be
devoted to open discussion of the above issues.
The list above obviously covers a lot of territory; we can't do more
than touch on many of these topics. We hope, in any case, to
accomplish these things:
(1) define this area as strategic for campus infrastructure
development;
(2) collect some best practices among the set of functions that many
(or at least some) campuses are doing well today;
(3) identify key issues and technical topics for further research.
We suggest that attendees come prepared with information about how
their campuses manage this kind of information today, including
particular successes and problem areas (a more detailed survey-like
instrument on may be available before the workshop).
Addendum D: CSG Workshop: Security Organization
Detailed Agenda
The overall goal of the Security Workshop (Thursday, May 13th, 8-10:30
AM) is to understand our evolving institutional approaches to security.
Our speakers plan to comment on trends, to identify key issues and the
biggest challenges and to consider any options for common action at the
CSG.
The agenda of the workshop is:
Introduction, Phil Long, Yale
Three perspectives on security:
Bob Mahoney, MIT
Sandy Senti, Stanford
Barbara Fraser, CERT
Summary and Conclusion, Phil
Addendum E: Apple Proposal to CSG
Immediately following the adjournment of the CSG meeting at UVa,
Apple computer is inviting any interested members to stick around for
an hour (noon-1pm) to hear a presentation on "WebObjects", a technology
for "application serving" keyed to PeopleSoft, SAP, Oracle, and other
such environments. You'll get your CSG boxed lunch in either case, but
please RSVP to Karen Kitchen (kwk@umich.edu) if you do plan to stay, to
aid in logistical planning.
Apple's proposal below speaks of the CSG as a group, but presumably can
be applied to whatever individual member institutions wish to take
advantage of it. (The proposal already limits itself to CSG's
PeopleSoft users in particular.) Based on feedback from those in
attendance, we may wish to schedule a slot at the Stanford meeting in
October to consider a more formal CSG-wide collaboration with Apple.
--- Apple's Proposal to CSG ---
Several members of the Common Solutions Group are exploring web
applications, standalone or in conjunction with SAP, Peoplesoft, Oracle
and other enterprise systems. One of the most mature technologies for
web application serving is WebObjects, from Apple Computer.
>From Apple PR: "Launched in 1996, WebObjects was the first
application server on the market and remains the industry's best
selling application server platform, with over 3,000 customers. Key
features include: a reusable object architecture; unparalleled
performance which allows for applications to be created and deployed
quickly; and multi-platform support for Mac OS X Server, Windows NT and
UNIX (Solaris and HP UX)." For more information, see:
http://www.apple.com/webobjects
Apple Enterprise Systems would like to make a proposal to CSG. In
short, AES would treat the group of CSG members working with Peoplesoft
as one single customer with respect to their consulting and development
services. In return that group would to work together, and with AES
(and Peoplesoft), to define commonly useful WebObjects modules for
Higher Education. What's in it for Apple is interesting the cream of
the HiEd market in this technology; what's in it for CSG is the
potential to divide costs for such work.
The agenda for the noon-1pm session on Friday, May 14 is:
1. an overview of 2 or 3 specific examples of existing
WebObjects deployment relevant to PeopleSoft,
2. the business proposal to the PeopleSoft contingent of CSG
that would involve cost sharing and collaboration, and
3. a decision on a method and time to revisit and refine the
proposal among interested parties.
Contact person at Apple is Joseph Bishop (bishop@apple.com).
Common Solutions Group: StoneSoup.org