Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!psuvax1!psuvm!PUCC!GETTES From: GETTES@PUCC.BITNET (Michael R. Gettes) Newsgroups: bit.listserv.nodmgt-l Subject: RE: BITNET Restructuring Proposal Message-ID: Date: 8 Feb 90 16:27:36 GMT Sender: Node Management Discussion Reply-To: Node Management Discussion Organization: Princeton University, CIT Network Systems Lines: 37 Approved: NETNEWS@PSUVM Gateway Comments: cc: Peter Olenick In-Reply-To: Message of Thu, 8 Feb 90 08:06:00 PST from On Thu, 8 Feb 90 08:06:00 PST Paul Rothi said: >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. As for the immediate impact of restructuring as proposed, there should be no interruption of service and no impact to end or mid-level sites as the core is established. It was understood in the development of the proposal that the implementation of the core had to take place without noticeable impact. What may change is the paths that are taken to reach other nodes on the network. Creation and removal of connections with the mid-level sites can be handled in a case by case, migratory manner. > 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. Procedures for obtaining routing tables will not change. If a node does not know how to obtain a routing table now, I suggest they contact BITNIC. No node updates will be required to end sites. Some mid-level sites will be affected (like the example of GWUVM), but this can easily be handled in a case by case, migratory manner. The core sites will handle their own updates, most likely with coordination from BITNIC or some other coordinating committee. >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. All new connections have been determined and outlined by the proposal. All sites proposed in the core already have IP connectivity, so they only need to acquire the VMNET software. Most already have it or have ordered it. /mrg