As many of you know, UCAR has a very diverse computing environment, with some of our services managed centrally and others managed at a divisional or even a personal level. To assist in the coordination and management of our computing resources, we have several technical committees that meet on a regular basis. We also maintain mailing lists for exchanging technical information, such as email@example.com for e-mail to system administrators regarding UNIX topics, and firstname.lastname@example.org for e-mail regarding PC and Macintosh topics. Among our technical committes are:
The ITC (Information Technology Council) is composed of a cross section of UCAR and NCAR staff, including the chairs of DSAC, NCAB, and CSAC (the groups described below). It was formed to identify important principles to guide the creation of a UCAR-wide information technology (IT) strategy. The function of the ITC is to develop a road map for gaining robust and flexible IT systems that employ these principles and serve UCAR and its associated communities effectively, now and for years to come. Recent ITC activities include several workshops as well as extensive sessions with a broad group of staff to create an information model reflecting UCAR's organizational structure, its processes, and the resources consumed and generated, as the basis for enhancing UCAR's information systems. ITC's home page can be found
on the Web, and you can e-mail the committee at email@example.com. The ITC chair is Jack Fellows (firstname.lastname@example.org).
DSAC (Desktop Systems Advisory Committee) meets to discuss the use of individuals' desktop systems and the support of such systems. Among the issues currently being discussed are the use of e-mail and attachments, cost-effective hardware and software purchasing agreements, and ways to exchange documents with a minimum of inconvenience. See
DSAC's home page
, and you can e-mail the committee at email@example.com. The chairs are Tim Fredrick and Mike Daniels (firstname.lastname@example.org).
NCAB (Network Coordination and Advisory Board) meets to discuss UCARnet and its support--that is, the networking through which NCAR systems transfer information. NCAB is represented by and coordinates closely with the SCD Network Engineering and Technology Section and is available to address concerns regarding networking at any of UCAR's locations. Issues include the current upgrade to "standard service" for our various locations, the ongoing maintenance of UCARnet to provide the most reliable network possible, and the future direction of networking. The group maintains a
Web page, which includes a "state of the network" provided by the NETS group. NCAB is chaired by Mark Bradford (email@example.com). The e-mail alias for the entire committee is firstname.lastname@example.org.
CSAC (Computer Security Advisory Council) meets to discuss management of UCAR systems in terms of their security and safety. CSAC is represented by and coordinates closely with the SCD Distributed Services Group and NCAR's new security administrator, Rich Johnson (email@example.com).
UCAR is on the verge of implementing a "security perimeter," which will allow outbound connections but will restrict inbound connections, for the most part, to "exposed hosts" only. Groups that have opted to be inside of the security perimeter (sometimes called a firewall) will enjoy protection against hacker attacks because UCAR can focus its attention with regard to security on the relatively few exposed hosts. More details will be forthcoming, and some of the specifics can be found on CSAC's
web page. CSAC is chaired by Greg Woods (firstname.lastname@example.org), and like NCAB, CSAC is a group to which you can bring your specific concerns about UCARnet security and the safety of systems connected through UCARnet to the Internet. The e-mail alias for CSAC is email@example.com.