Generic Internet Service Description (gisd) Charter

NOTE: This charter is accurate as of the 33rd IETF Meeting in Stockholm. It may now be out-of-date. (Consider this a "snapshot" of the working group from that meeting.) Up-to-date charters for all active working groups can be found elsewhere in this Web server.

Chair(s)

David Sitman <david@ccsg.tau.ac.il>

Operational Requirements Area Director(s):

Scott Bradner <sob@harvard.edu>
Michael O'Dell <mo@uunet.uu.net>

Mailing List Information

General Discussion:gisd-wg@ripe.net
To Subscribe: majordomo@ripe.net
- In Body: subscribe gisd-wg
Archive: ftp://ftp.ripe.net/ripe/archives/gisd-wg/current

Description of Working Group

GISD collects short descriptions of Internet service aspects. Internet service in GISD means the interaction of Internet service providers among themselves and with their users. GISD aims to provide a common frame of reference and vocabulary to talk about an Internet service. For each aspect of the Internet service, it describes different options for service provision in use in the current Internet. GISD is merely descriptive and does not proscribe or mandate. The GISD document is intended to be a living document, collecting the work of many contributors.

The GISD Working Group will update and revise the GISD document to assist network service providers in a better understanding and description of what Interent service means.

- Update and revise the GISD document that lists the areas and aspects of interest to TCP/IP network service providers.

- Identify additional GISD areas and aspects appropriate to GISD.

- Identify areas of overlap with other IETF working groups.

- Create a reference document of GISD terms.

- Establish procedures to ensure the ongoing maintenance of the document and identify an organization willing to do it.

Goals and Milestones

Nov 93: Review current GISD draft and add any additional areas and aspects felt essential.
Mar 94: Draft of GISD will be prepared. Submit as Internet-Draft.
Jul 94: Follow-up with final amendments and submit to RFC Editor for publication as an FYI RFC.