Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!psuvax1!psuvm!PLU!ROTHI_P From: ROTHI_P@PLU.BITNET (Paul Rothi) Newsgroups: bit.listserv.nodmgt-l Subject: RE: BITNET Restructuring Proposal Message-ID: Date: 8 Feb 90 16:06:00 GMT Sender: Node Management Discussion Reply-To: Node Management Discussion Lines: 34 Approved: NETNEWS@PSUVM Gateway X-VMS-To: IN%"NODMGT-L@BITNIC.BITNET" I have two concerns regarding the restructuring of BITNET and its effects on small end nodes. 1. Typically we have much smaller operating budgets than the larger core sites or mid-level sites. As a result, we may not have the same level of expertise with all the subtleties of BITNET networking. As this restructuring plan progresses, or is finalized, we will need to have clear instructions telling exactly what to do to remain a functional node with minimal disruption to our users. Examples here include where to get routing tables, or how generate them ourselves, and updates that may be required to our node entries at the BITNIC. 2. If new connections must be made with regional or mid-level nodes, this needs to known up front so budget allocations can be made. 3. Also, if any new software will be required to remain functional under the new topology, that too must be known in advance. Software for large platforms is not cheap and may have significant impact on a relatively small budget. I give my support to the overall concept! The idea of a more formal structure and fault tollerance is appealing. Please, keep us all informed as this progresses. Finally, when all is ready for conversion, publish a **single** detailed list of instructions for sites at all levels to follow to remain functional as, and after the conversion is done. -------------------- Paul Rothi Telephone: (206) 535-7525 Pacific Lutheran University BITNET: ROTHI_P@PLU Computer Center Tacoma, WA 98444