Received: from cni.org by b.cni.org (5.65v4.0/1.1.10.5/13Aug97-0713PM) id AA31476; Tue, 19 Feb 2002 12:05:14 -0500 Received: from [192.100.21.10] (cliffords-pb.cni.org [192.100.21.10]) by cni.org (8.8.7/8.8.7) with ESMTP id MAA19962; Tue, 19 Feb 2002 12:01:57 -0500 Mime-Version: 1.0 X-Sender: clifford@mail.cni.org Message-Id: Date: Tue, 19 Feb 2002 09:04:26 -0800 To: cni-announce@cni.org From: Clifford Lynch Subject: Internet 2 Commons Call for Participation Cc: ted@internet2.edu Content-Type: text/plain; charset="us-ascii" ; format="flowed" Status: O X-Status: X-Keywords: X-UID: 5 Internet 2 has done some very exciting work over the past year or two on large scale network based videoconferencing. They are now planning the next steps, and have issued this call for participation in the development of their requirements as they look to a broader vision of network based collaborative technologies. The contact on this is Ted Hanss . Clifford Lynch Director, CNI CALL FOR PARTICIPATION Responses due 28 February Internet2 Commons Phase 2 Requirements Task Force In order to move forward quickly with useful services, the initial Internet2 Commons roll out focused on scaling up existing videoconferencing efforts, notably H.323 based on ViDe's architecture and the mbone tools and gateway services offered through VRVS (Virtual Rooms Videoconferencing System). Other more exploratory videoconferencing technologies were also included, such as the Access Grid, MPEG-2, and MJPEG. It is appropriate now to establish the scope and timing for the broader vision of the Internet2 Commons---one that includes a wide array of collaborative technologies. Therefore, we are creating an Internet2 Commons Phase 2 Requirements Task Force as a short term effort that will deliver a draft report for review at the spring Internet2 member meeting in Washington, DC (6-9 May). This task force's report will include recommendations, as appropriate, to the Internet2 Commons Management Team, Internet2 Membership, Internet2 staff, and/or the Internet2 Board of Trustees. The final report is expected to be delivered in June 2002. Participation in the requirements task force will come from individuals who submit a statement of interest by email to ted@internet2.edu by Thursday 28 February. This statement of interest, no more than a couple of paragraphs, should outline the area of interest of the potential participant. Selections, made by Thursday 7 March, will represent a balance of views and interests, ensuring broad and balanced input to the process. The Requirements Task Force, working with the Internet2 Commons Management Team, will meet though voice and video teleconferences and will solicit additional input through the same means. The Internet2 Commons Phase 2 Requirements Task Force should consider the following in its recommendations: - The technologies and services that should be included in the Internet2 Commons beyond videoconferencing. Application sharing, instant messaging, continuous presence services, streaming, archiving, interoperability tests, and accessibility have been mentioned. - Within videoconferencing, what should be the features and functionality of the phase 2 of the videoconferencing services? This will include implementing services under development by the VidMid area of the Internet2 Middleware Initiative and the need to more closely integrate various videoconferencing technologies and other collaborative tools (gateways, server support, etc.). - Appropriate coordination of the Commons with other efforts (other Internet2 projects and working groups, standards organizations, industry groups, and international efforts). Examples include more fully using and promoting IP multicast with the Multicast Working Group and deploying a measurement/performance monitoring infrastructure with the End-to-End Performance Initiative. - Actively and properly engaging the Internet2 corporate membership within the initiative, particularly in areas where there are overlapping and, particularly, emerging commercial interest. - Engaging academic conferences as users of Commons services to extend access to their events. - Defining the appropriate prerequisite levels of institutional readiness and investment for participation in the initiative. - Levels of service and appropriate funding models (base level, added-value with additional services and support, ...). The Requirements Task Force should propose timing with respect to the introduction of any new services and feature sets within those services. The report should provide a clear, motivating vision of this potentially complex, multi-component project to both the administrative and technical communities within Internet2. The report also should be accessible to other potential partner organizations (e.g., interested funding agencies) as well as the discipline-centered communities of leading end users that will be the early beneficiaries of the Internet2 Commons. References: Internet2 Commons ViDeNet VRVS Access Grid