*Action Items*
Carry Over
[AI] {John-Paul and Jim} will examine the domain model diagram for consistent terminology.
[AI] {Group} will collect university mailing list policies and send them to SteveO if OK to post on the WG page.

New
[AI] {Jill} will develop the distribution list for VO survey.
[AI] {Jill} will incorporate the group’s comments into the object model and finish page four of the model.
[AI] {Jill} will send an e-mail to those presenting on behalf of the WG at the Fall I2MM with suggestions for topics and duration of discussions.
[AI] {Jill and Jim} will discuss domain model and object model prior to Fall I2MM.
[AI] {Jill} will follow up to find NSF and Department of Energy projects supporting VO’s.

*Attendees*
Jill Gemmill, University of Alabama at Birmingham (Chair)
Paul Russell, Notre Dame
Jeff Eaton, Carnegie Mellon University
Jim Phelps, University of Wisconsin, Madison
Bob Morgan, University of Washington
Lisa Hogeboom, Internet2
Steve Olshansky, Internet2
Ann West, EDUCAUSE/Internet2

*Discussion*
The mailing list survey will be sent out today. The group is in the process of identifying an appropriate VO survey beta test candidate. An inquiry has been made to JISC and to the technical support group of the DOE to solicit a beta candidate and other VO survey respondents.

Object Model Discussion – Jill Gemmill developed an object-oriented model to supplement the domain model diagram. The object model further facilitates the identification of middleware enabled areas of mailing list software. The object model identifies mailing list components and processes. Properties of the list may include a variable name creation date, a name of one or more list managers or moderators, storage for archives, rules, and a membership list. All of these properties are essentially empty data sets until a list is created. The model also identifies activities performed by the list such as sending messages to members, changing member rules and archiving. These activities are internal to the mailing list software. The mailing list software acknowledges that the content of messages has been evaluated by list rules prior to being sent out to the membership list. The “authorize submitter” function refers to rules external to the list and external to mailing list management software to permit an individual to post to the list.

The list manager has one or more management rules. In this model the list management software might have a federated membership or an identity management service. The model supports two types of membership lists. A membership list internal to the list management software reading and writing to the data store and another list that only reading information in the data store.

Both of the group’s models, the diagram and object, will be discussed at the Fall I2MM.

The group will support several sessions at this year’s Fall I2MM. For more detail, please see http://events.internet2.edu/2004/fall-mm/.

The group will hold an E-Mail Security BoF, jointly hosted by Salsa, on Sunday, September 26 from 7:00PM – 9:00PM. Sender ID has been discussed and subsequently eliminated as a discussion topic for the BoF due to recent developments. Several other topics are being considered for the meeting. The Purported Responsible Address (PRA) approach might be a BoF topic.

Other potential topic suggestions should be sent to the list for consideration. One desired outcome of the BoF is the formation of another Internet2 working group focusing on e-mail security.

As the next regularly scheduled call would fall during the Fall I2MM it will be canceled. The next call is Wednesday, October 13, 2004 at 12:00PM ET.