Automated Internet Mailing List Services (list)

Charter

Chair(s):
     David Lippke, lippke@utdallas.edu

Mailing Lists:
     General Discussion:  ietf-list-wg@utdallas.edu
     To Subscribe:  ietf-list-wg-request@utdallas.edu
     Archive:  pub/ietf-list-wg@ftp.utdallas.edu

Description of Working Group:

     This working group will concern itself with "list servers",
     i.e., advanced mail exploders/reflectors which provide services
     such as automated subscription, archive maintenance, and
     coordination with similar systems on the network.

     The group will initially focus its activities towards
     establishing a baseline user interface.  Although most current
     systems support a command set patterned after Eric Thomas'
     BITNET LISTSERV, there is wide variance in the options
     supported and in the general patterns of interaction.  This
     results in a great deal of user confusion.  The working group's
     interface definition will address this by establishing a set of
     commands, options, interactions, and procedures which will
     (hopefully) be supported by all list servers as a subset of
     their full repertoire.

     As a part of the user interface work, the group will also
     define an authentication service for users' list server
     transactions.  Toward this end, and to address the privacy
     issue, the group will consult with the SAAG.

     The second phase of the group's work will be to provide for the
     interconnection and coordination of list servers.  Experience
     with the BITNET LISTSERV has shown that it's important for
     users be able to view the collection of list servers on the
     network as an integrated whole.  Ideally, users should only
     have to deal with their local mailing list service---which
     knows where all public lists are, what they are, and is able to
     act on the user's behalf with respect to them.  Interconnecting
     list servers allows this "integrated user view" to be created
     and also lets issues such as traffic minimization, timely
     distribution, and load sharing be more easily addressed.
     Consequently, the working group will define the conceptual
     models, communication methods, and extensions to prior work
     which are necessary to bring this interconnection and
     coordination about.

                                   1





     It's anticipated that further work on on issues of
     authentication and privacy will continue in parallel with the
     "integration" effort --- perhaps manifesting itself as a
     separate RFC which extends the user interface definition
     produced during the first phase.

Goals and Milestones:

Jul 1991   Review the group's charter and begin work on the user
           interface definition.

Nov 1991   Resolve outstanding issues with the user interface definition
           and prepare document for IESG submission.  Begin work to
           address the interconnection/coordination issue.

Jan 1992   Submit user interface definition document to IESG as a
           proposed standard.

Mar 1992   Focus the interconnection/coordination work.  Finalize and
           document settled issues.

TBD        Submit interconnection/coordination definition document to
           the IESG for publication as a proposed standard.



                                   2