Internet 2 Applications Group
Current Action Items
Version of 2 April 1997

These are the action items for completion or substantial progress by
the end of May 1997.

The Applications group will sponsor working groups to focus on specific
areas of interest. We will work with the Engineering group to ensure
that we don't establish overlapping or redundant activities.

	Action 97-1: Identify the initial set of working group topic
	areas, with the expectations for these groups and a specific
	mission for each group. Those discussed include (with some
	clustering): infrastructure (security, directory,
	program-to-program communications, accounting/billing);
	measurement (application tracking, networking/systems
	management); collaboration technologies (teleconferencing,
	chat, whiteboards); virtual labs (remote experimentation);
	streaming media (multicast, IP telephony); reliability and
	scaling (high bandwidth, numbers of people, latency); and
	applications interfaces (replication, caching, file systems,
	resource reservation).  There was also discussion of
	application specific working groups: telemedicine, immersion
	environments, digital libraries, and art/music instruction.

	Action 97-2: Establish the support structure for the working
	groups (e.g., listservs, conferencing tools--all with
	archives---for status sharing and interaction)

	Action 97-3: Seek and identify the members of the working
	groups

The campus application representatives are the key liaisons between the
campus and faculty and the Internet 2 project.

	Action 97-4: Define the expectations of the applications
	representative as a technical contributor and as an information
	conduit in and out of the campus

	Action 97-5: Applications representatives are to establish
	local I2 interest groups on their campuses

	Action 97-6: Applications representatives are to represent the
	interest of the faculty and campus community back to the I2
	project (initially by putting up a campus I2 applications web
	page, with pointers from the I2 web site)

	Action 97-7: The I2 project staff will provide a template for
	the campus I2 status page, to help structure the information

	Action 97-8: The I2 project staff will provide a standard
	overview presentation (in PowerPoint and HTML formats) for
	applications representatives to use in consistently describing
	the I2 effort on their campuses

The Applications group will establish a profile document, which will
consist of a set of requirements, recommended standards, and
recommended products.

	Action 97-9: Produce a listing of requirements

	Action 97-10: Produce an initial set of recommended middleware
	standards

A role of the I2 project is keeping the campuses informed of  relevant
applications activities

	Action 97-11: Survey "relevant/interesting things" going on
	anywhere in the broad internet community and put and maintain
	links on the I2 home page (e.g., standards groups, vendor
	activities, universities)

We cannot complete this work alone. Therefore, we need to partner where
possible among ourselves, with government agencies, and with vendors.

	Action 97-12: Establish guidelines and process for partnerships

Our bottom line is deploying compelling applications that exploit the
functionality of Internet 2 and advance the research and education
missions of higher education.

	Action 97-13: Establish a timeline for I2 applications
	demonstrations/testbed

	Action 97-14: Identify a set of exemplar applications that
	validate the initial set of requirements and that are
	responsive to the demonstration and testbed needs