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: :routtab tableformat for NJEF Message-ID: Date: 7 Feb 90 16:53:34 GMT Sender: Node Management Discussion Reply-To: Node Management Discussion Organization: Princeton University, CIT Network Systems Lines: 44 Approved: NETNEWS@PSUVM Gateway In-Reply-To: Message of Wed, 7 Feb 90 11:09:31 CET from On Wed, 7 Feb 90 11:09:31 CET Berthold Pasch +49 (6221) 404-242 said: >If there are no objections or better proposals, then I'll specify >the NJEF tableformat in :routtab as shown above. Yes, I have a problem with this. I will restate that this kind of information is not necessary within BITEARN NODES. This is a "table-format" problem and not a routing problem. If NJEF nodes need some additional information in their routing table, that happens to be tied to network topology, then they should devise a program that figures out network topology and the associated links and do the right thing with generating a routing table. I believe this to be the case for HOMEBREW site as well. We should be providing a routing table in a generic format, something similar to what a standard pathalias map looks like (which I will show below), and then auxiliary software would be developed to convert this generic map into a routing table of appropriate format by software developed or acquired by the local node. I do not like the idea of riddling the BITEARN NODES file (and especially the :routtab tag) with additional tidbits of information that is not necessary. And, saying that a limit of 4 or 10 is ludicrous -- Murphy says it WILL exceed whatever theoretical limit you set. I vote no for this additional information being introduced into the :routtab tag and to adding this type of information to BITEARN NODES in general. A few lines from the PUCC MAP produced by pathalias. I have a program that then turns this map into a RSCS routing table. acadia punfsv2!cornellc!utorvm!unbmvs1!dalac!acadia!%s acmvm punfsv2!cunyvmv2!cunyvm!acmvm!%s acusd punfsv2!ucbcmsa!uclacn1!uscvm!ucivmsa!sdsc!acusd!%s acuvax punfsv2!ricevm1!uhou!utgate!acuvax!%s aearn punfsv2!cunyvmv2!frmop22!cearnv2!aearn!%s aeclcr punfsv2!cornellc!utorvm!mcgill1!qucdn!uottawa!aeclcr!%s agu punfsv2!psuvm!psubit!gwuvm!agu!%s ainuni01 punfsv2!cunyvmv2!frmop22!cearnv2!aearn!ainuni01!%s aip punfsv2!yalevm!sbccvm!hofstra!aip!%s akron punfsv2!ohstvma!csuohio!akron!%s If you will notice, you get more information with a pathalias map then you do just a routing table. ACADIA is routed via the link PUNFSV2. But, it also shows the full path taken from PUCC to ACADIA. Additionally, from this map I can display all the published links for any node on the network with one pass of this file. /mrg