*Action Items*

New
[AI] {Terrie} will incorporate Sympa developer’s comments into the January 19, 2005 minutes and circulate the revised minutes to the group via the list.
[AI] {Jill} will request a working group side-session at the Spring I2 Member Meeting if the track session proposal is not accepted.
[AI] [SteveO} will create a ‘wishlist’ section on the WG’s website. This first item posted to the ‘wishlist’ will be a solicitation seeking an individual interested in packaging and maintaining Sympa for Fedora Core.
[AI] {John-Paul and Jill} will add flow logic to page five of model integration document.
[AI] {Group} will review charter, objectives and deliverables to determine WG’s next steps.

Carry Over
[AI] {Paul, Serge and Olivier} will begin developing a list of generic topics addressing spam and mailing list management software.
[AI] {SteveO} will gather email policy links from survey responses and incorporate them on the WG’s web site.
[AI] {Jill} will notify EDUCAUSE of Mailing List survey results to be placed in the EDUCAUSE library.
[AI] {Jim} will incorporate Sympa developers’ comments into the WG’s models.
[AI] {John-Paul} will prepare discussion points for Mailman discussion.
[AI] {Jim} will follow up on status of UW-Madison and INQ.
[AI] {Jim and John-Paul} will discuss local-interface preference storing of attributes. And, will send a brief summary of the discussion to the WG via the list.
[AI] {SteveO} will gain a better understanding of Sympa documentation and translation requests and coordinate follow up w/ Renee and Jill.
[AI] {Jill} will develop VO survey distribution list, and will follow up with NSF and DOE for possible VO survey candidates.

*Attendees*
Jill Gemmill, UAB (Chair)
John-Paul Robinson, UAB
Paul Russell, University of Notre Dame
Lisa Hogeboom, Internet2
Steve Olshansky, Internet2

*Discussion*

The group discussed the model integration document. In addition to clarifying middleware enabled functions of mailing list management software, the model integration document also includes a brief description of middleware enabled functions, input and output required for the functions and specific services provided by the function. Message validation occurs with SMTP software prior to the message being sent to the mailing list. The group decided that this service/function is better named a ‘message filter service’ instead of a message validation API. Spam elimination along with other filtering rules (i.e. offensive speech and topic adherence) generally occurs in functions outside mailing list software. However, it was agreed that some services like spam elimination should also be addressed in mailing list management software. The method by which filtered messages are transported to the mailing list can be either SMTP or HTTP.

The message archive interface may be different than authenticating an individual attempting to send a message. Perhaps these two functions can be combined into one function. Usually, the result of authentication resolves to a specific identity, although other authentication results could be a known/unknown identity verification or valid/not valid verification.

Within the authorization attribute, policy and subsequent authorization decision there is a subtle difference between having a read-privileges database and requesting the service to provide the data. A common name for these functions is desirable.

A member management API can provide gathering members and gathering moderators services to add, remove and find people.

Preprocessing services, initial filtering or initial processing, workflow, encryption and message signing are associated with authorization and authentication. Some post processing services might be middleware aware (i.e. differing news servers, etc.). This will be added to the beginning of the model integration document.

The group discussed its charter, objectives and deliverables. The group will request (again) involvement from Mailman developers, complete the VO survey and then deliberate next steps for the WG.

The next call is Wednesday, February 16, 2005 at 12:00PM ET. The call in number will be distributed with the agenda prior to the call.