March 1995 - Test - lists.nanog.org

Re: Internic address allocation policy
by johnr＠geo.net 20 Mar '95

20 Mar '95

I for one, think that this resource would be less "scarce" if it were not free. As an ISP who has and is investing substantial sums of money in our operation, I cannot afford to be put out of business due to lack of IP addresses. Speaking for my company and its customers, we would be more than willing to pay for IP space if we could be assured of getting it when we need it to service our customers! Hopefully, a market approach to assigning IP space would take into account large blocks and Class B's being held and not used at all. I happen to know of a small high tech company in Silicon Valley that holds more than one class B, and could barely spell Internet last year when we talked to them about attaching. Kind Regards, John A. Russo GeoNet Communications, Inc.

1 0

Re: Internic address allocation policy
by johnr＠geo.net 20 Mar '95

20 Mar '95

> > From: Alan Hannan <alan(a)mid.net> > Subject: Re: Internic address allocation policy > > I know of several companies that would be willing to spend over $10,000 for > a class B network. Money is not the issue. Your idea of a (more efficient) > distribution center makes sense, however, this should be achieved through > group concensus and appointed councils, not by who wants to make money. > >If T.J. Rogers was dead, he'd be spinning in his grave right now. > >If you want something done efficiently, you want it run by people who are >damn well hungry for money, not by appointed councils. I couldn't agree with you more Paul.

1 0

Re: Internic address allocation policy
by Vadim Antonov 19 Mar '95

19 Mar '95

From karl(a)mcs.com (Karl Denninger): > But others have reported to me that they have been asked for them, and I > was a personal witness to one of those requests. If Sprint, PSI, and > Alternet have them on file with the NIC I want to FOIA those documents! Dunno about others but Sprint provides InterNIC with extensive documentation on allocations and the technical reasons for doing this and that. We have automated facilities for producing the data on address space utilization. It is not bias on part of InterNIC, it is lack of proven usage history and proper documentation which makes life of people who go directly to InterNIC miserable. (I have complaints about InterNIC not allocating more than 1024 Cs a POP, so now i have to maintain three dozen of CIDR blocks instead of six the SprintLink's address allocation sstrategy requires, and have to limit per-customer allocations by small blocks; but i cannot say they are unfair). --vadim

1 0

Re: Internic address allocation policy
by Vadim Antonov 19 Mar '95

19 Mar '95

That silly argument boils down to the very simple observation: Authorithy should be in hands of those who can _enforce_ and _verify_. I.e. InterNIC shoudl go out of address allocation business completely and ISPs should step in. Can they enforce? You bet. If you try to announce network 1.0.0.0 as a SprintLink's customer you'll see filters in place before you say "amen". Can they verify? Sure. I'm declining lots of bogus requests for address space -- and then proceed with explaining how to use subnets or whatever. I can always check how the access link is loaded, what routes are really announced etc. Recently somebody asked me to route, like, 12 class Bs, over a 56k link. Turned out they need three class Cs, but grabbed lots of Bs back then when InterNIC was very liberal. The allocation should be performed by service providers in the "food chain" order -- to ensure reasonable aggregation. I.e. nation-wide and world-wide service providers should allocate blocks to regional ISPs, etc. Do "big" service provider need to be "checked" by users? I don't think so because they bet millions on the future of the Internet and won't willingly destroy the market. The fierce competition in the area also ensures that they won't use the address allocation as means of sqeezing small service providers out. And at least two of them fear anti-trust litigation more than coming of Antichrist. You may like it or dislike it but nation-wide backbone providers effectively run the Internet nowadays. It is a rare case when big businesses actually introduced some common sense in the way things are done architecture-wise. Why not to do the same with the address allocation? --vadim

1 0

Re: Internic address allocation policy
by Finger in the Infodike 19 Mar '95

19 Mar '95

Very interesting debate... let's look back in time to the turn of the century, when our fair city had several competing phone companies. The largest, AT&T, drove the rest out of business by refusing to connect to them. Hence they became a monopoly and claimed that it was "natural" for the phone company to be a monopoly. The "natural monopoly" lasted until fairly recently, when the government broke it up. I think that the Internet could well face the same set of issues. In particular if, say MCInet became convincingly dominant, they could easily put the rest of you guys out of business by refusing to connect you. I think that the only thing that can prevent the Internet following the same course as the telephone network is government anti-trust regulation, which I would hope to see, since I value free competition. -- Walt -------

1 0

InterNIC RS
by hwb＠upeksa.sdsc.edu 19 Mar '95

19 Mar '95

Okay, it seems to me that people here perceive there is reasonable concern about on or more of the following intertwined but separable problems: 1. policies for the current mode of operation do not map to today's real requirements, or are unreasonable 2. there is no reasonable response time, things get delayed or even lost 3. the InterNIC is a US Federal instrument which makes them bad by definition Really fixing issue (1.) will require more than "I don't like X," it will require deriving solid guidelines with community consensus, and that take the global picture and its future evolution into account. I think it would be great is people would create better guidelines and get the service providers etc. to sign off on it. I suspect best would be a consolidated position coming from the IEPG, perhaps with NANOG taking the first cut? Issue (2.) I suspect to be a resource issue. May be the InterNIC should be held more accountable for their actions and submit weekly status reports (perhaps automatically generated?) or so of what they did. That would at least help for a better understanding of the work volume. Above and beyond that, I think the InterNIC registration service is run by a private for profit corporation, under contract to NSF. They will likely take money from private corporations to be used for allocating more resources to the handling of commercial requests. Why don't you all just fund a staff person (or however many it takes) for commercial service providers there, and make them accountable to your requirements? Also, how long does it take to get an Ethernet Type field or a 3 byte Ethernet address prefix? Who does that these days? IEEE? (3.) is perhaps harder, as we are dealing with perceptions here. I am not convinced that anyone is purposely trying to interfere with the requirements of private industry. I suspect it more to be a lack of guidelines with consensus, and general resources. Again, the RS is a private corporation, and in and of itself not "bad." Obviously there is a need for central coordination, and that may require more than one thinks at first, in terms of resources. Are you all prepared to pick that up? Would you, e.g., be willing to offer to NSF to pick up the InterNIC funding and make the RS accountable to private industry?

1 0

IP foresight
by Finger in the Infodike 19 Mar '95

19 Mar '95

Just to put a little perspective on this whole debate about forseeing your IP address needs, I was cleaning out my desk and found a copy of a message sent on June 5, 1984 to me (then haas(a)utah-20.arpa) thanking me for getting the X.25 connection to Japan working. The whole Internet has evolved in the 11 years since. I'm a fairly serious amateur student of technology history, and I'm not aware of any other technology that has grown at comparable speed. I think it would be nice if we gave the folks at the InterNIC a break, and recognize that they are attempting to deal with a situation which is basically impossible. The only thing which I can see offering any real hope is IPng, with RFC 1597 as a plausible stopgap - at least I hope it's plausible since I'm recommending it to clients, most of whom are paranoid about security and want a firewall anyway. -- Walt -------

1 0

Re: Internic address allocation policy
by Phil Dykstra 18 Mar '95

18 Mar '95

Speaking as a national network with millions of dollars invested (AAI), I tried for three months to get a Class B assigned. The total number of hosts didn't justify it, even though it was nationwide with many geographic sites that we wanted to subnet, and even though we are doing research in ATM SVC signalling, ATM multicast, NHRP, etc. So we got a CIDR block of Class C's, and as expected, many of our systems are turning out not to handle the required subnet masks without hacks. While this has all been a pain I wished to avoid, we do really need to get this CIDR stuff to work everywhere, and we really are running out of address space. So while I agree that address space struggles with the InterNIC aren't pleasant (or quick), I think they are doing what needs to be done to conserve a scarce, dwindling resource. - Phil

1 0

decreasing traffic
by epg＠merit.edu 16 Mar '95

16 Mar '95

We are about six weeks away from the retirement of the NSFNET backbone service. In looking at the traffic statistics for the various access points to the NSFNET service, most ENSSes have seen a reduction in traffic into the backbone, but there is still a significant amount of traffic which still traverses the NSFNET. Merit has posted a histogram on nic.merit.edu:/nsfnet/statistics/ top10.transition.ps which shows the number of packets into the nodes of the backbone in the last 6 months (Sept'94 to Feb'95). The 10 nodes which are shown on this graph are the top 10 originators of traffic into the backbone in February 1995. If you are attached to one of the nodes highlighted on our graph, please be aware that these attachments to the NSFNET Backbone Service will be retired as of April 30, 1995. More detailed information about the packets and bytes on the NSFNET Backbone Service can be found on nic.merit.edu:/nsfnet/statistics/*. --Elise

1 0

Additions to the NSFNET policy-based routing database
by smm＠twain.merit.edu 16 Mar '95

16 Mar '95

------------------------------------------------------------------------------ The PRDB and this "NWG report" will be retired very soon. Details below. ------------------------------------------------------------------------------ The following changes have been made to the NSFNET policy-based routing database and will be installed on the backbone by 08:00 EST : Total = As + Bs + Cs + Aggs Registered Networks 49309 = 30 5337 40795 3147 Configured Networks 46396 = 30 5280 38003 3083 Added Networks 212 = 0 9 160 43 Deleted Networks 56 = 0 0 56 0 IP address Net name Country Priority:AS ---------- -------- ------- ----------- 151.2/16 ITNET-WAN2 C:IT 1:1849 2:701(136) 3:701(134) 4:1800 155.179/16 SWBT C:US 1:1800 2:1239(218) 3:1239(144) 158.166/15 CECNET1-2 C:LU 1:1128 2:1800 3:1133 4:1674 5:1239(144) 158.168/15 CECNET3-4 C:LU 1:1128 2:1800 3:1133 4:1674 5:1239(144) 160.84/16 BWNT C:US 1:701(136) 2:701(134) 165.233/16 RENNIESNET C:ZA 1:1800 2:1239(218) 3:1239(144) 166.164/16 NETBLK-CDPD-B C:US 1:1334 2:1800 3:1240 4:209 5:210 167.140/16 QVC C:US 1:1324(35) 2:1324(32) 170.39/16 CASHWAYS C:US 1:2386 2:1321 170.49/16 BNR2 C:US 1:3561(218) 2:3561(11) 3:1225(130) 4:1225(129) 5:1225(131) 6:1239 7:1240 8:1800 170.91/16 SJENNET C:US 1:1239(144) 2:1800 3:1239(218) 192.5.85/24 UOC-NETS C:US 1:3561(218) 2:3561(11) 3:1225(129) 4:1225(130) 5:1225(131) 192.5.87/24 UOC-NETS C:US 1:3561(218) 2:3561(11) 3:1225(129) 4:1225(130) 5:1225(131) 192.31.14/24 MI-NET C:DE 1:1800 2:1240 3:1133 192.92.201/24 CALLNET-201 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 192.94.111/24 ENL-NETS C:GB 1:1849 2:701(136) 3:701(134) 4:1800 192.100.61/24 MEMEX C:GB 1:1849 2:701(136) 3:701(134) 4:1800 192.107.58/23 ENEA-BRA-1 C:IT 1:293(144) 2:293(145) 3:1133 4:1674 5:1800 192.139.120/24 SESNET0 C:CA 1:1800 2:1239 192.139.121/24 SESNET1 C:CA 1:1800 2:1239 192.139.122/24 SESNET2 C:CA 1:1800 2:1239 192.139.156/24 UNIBASE2 C:CA 1:1800 2:1239 192.139.157/24 UNIBASE02 C:CA 1:1800 2:1239 192.139.158/24 UNIBASE03 C:CA 1:1800 2:1239 192.139.159/24 UNIBASE04 C:CA 1:1800 2:1239 192.139.160/24 UNIBASE05 C:CA 1:1800 2:1239 192.139.162/24 UNIBASE07 C:CA 1:1800 2:1239 192.139.163/24 UNIBASE08 C:CA 1:1800 2:1239 192.139.164/24 UNIBASE09 C:CA 1:1800 2:1239 192.139.165/24 UNIBASE10 C:CA 1:1800 2:1239 192.139.166/24 UNIBASE11 C:CA 1:1800 2:1239 192.139.167/24 UNIBASE12 C:CA 1:1800 2:1239 192.139.168/24 UNIBASE13 C:CA 1:1800 2:1239 192.139.169/24 UNIBASE14 C:CA 1:1800 2:1239 192.139.170/24 UNIBASE15 C:CA 1:1800 2:1239 192.139.171/24 UNIBASE16 C:CA 1:1800 2:1239 192.139.172/24 UNIBASE17 C:CA 1:1800 2:1239 192.139.173/24 UNIBASE18 C:CA 1:1800 2:1239 192.139.174/24 UNIBASE19 C:CA 1:1800 2:1239 192.139.175/24 UNIBASE20 C:CA 1:1800 2:1239 192.139.176/24 UNIBASE21 C:CA 1:1800 2:1239 192.139.177/24 UNIBASE22 C:CA 1:1800 2:1239 192.139.178/24 UNIBASE23 C:CA 1:1800 2:1239 192.139.179/24 UNIBASE24 C:CA 1:1800 2:1239 192.139.180/24 UNIBASE25 C:CA 1:1800 2:1239 192.139.181/24 UNIBASE26 C:CA 1:1800 2:1239 192.139.182/24 UNIBASE27 C:CA 1:1800 2:1239 192.139.183/24 UNIBASE28 C:CA 1:1800 2:1239 192.139.185/24 UNIBASE30 C:CA 1:1800 2:1239 192.175.159/24 NETBLK-VANGUARD C:US 1:1324(35) 2:1324(32) 3:3577 192.175.219/24 NETBLK-VANGUARD C:US 1:1324(35) 2:1324(32) 3:3577 192.188.20/24 DAI C:US 1:1240 2:1800 192.203.174/24 ILE-NET C:US 1:1800 2:1240 3:1239 4:209 5:210 192.254.60/24 APLABS60 C:US 1:1740(218) 2:1740(135) 193.38.144/20 MEMEXNET C:GB 1:1849 2:701(136) 3:701(134) 4:1800 193.43.16/23 BDP-NET C:IT 1:293(144) 2:293(145) 3:1133 4:1674 5:1800 193.51.138/24 FR-PHARELILLE2 C:FR 1:1800 2:1240 3:1133 4:1674 193.51.139/24 FR-SCLILLE2 C:FR 1:1800 2:1240 3:1133 4:1674 193.52.205/24 FR-ENSEM-MTP1 C:FR 1:1800 2:1240 3:1133 4:1674 193.52.206/24 FR-ENSEM-MTP1 C:FR 1:1800 2:1240 3:1133 4:1674 193.52.207/24 FR-ENSEM-MTP1 C:FR 1:1800 2:1240 3:1133 4:1674 193.52.217/24 FR-ENSEM-MTP2 C:FR 1:1800 2:1240 3:1133 4:1674 193.54.93/24 FR-NY-ENSIC1 C:FR 1:1800 2:1240 3:1133 4:1674 193.54.94/24 FR-NY-ENSIC2 C:FR 1:1800 2:1240 3:1133 4:1674 193.54.95/24 FR-NY-ENSIC3 C:FR 1:1800 2:1240 3:1133 4:1674 193.168.78/23 INFOPARTNERS C:LU 1:1128 2:1800 3:1133 4:1674 5:1239(144) 193.168.88/21 TELINDUS-NETWORKS C:LU 1:1128 2:1800 3:1133 4:1674 5:1239(144) 193.186.32/24 UNISYS-VIENET C:AT 1:701(136) 2:701(134) 3:1800 194.36.84/22 RMPLC-AGGR C:GB 1:1800 2:1133 3:1239(218) 4:1239(144) 5:3561(218) 6:3561(11) 194.57.124/24 FR-DRCNRS C:FR 1:1800 2:1240 3:1133 4:1674 194.58.225/24 PLUSCOM C:RU 1:701(136) 2:701(134) 3:1800 194.59.36/22 RRZ-FRANKEN C:DE 1:1800 2:1239(144) 3:1133 194.60.203/24 ALDIE-NET C:GB 1:1849 2:701(136) 3:701(134) 4:1800 194.97.0/19 DE-ROKA-194-97-0 C:DE 1:1800 2:1240 194.113.47/24 BLITZ C:DE 1:1800 2:1240 3:1133 194.125.0/20 IOL C:IE 1:1849 2:701(136) 3:701(134) 4:1800 194.127.175/24 UB-STEINKAMM C:DE 1:1800 2:1240 3:1133 194.135.28/24 NETTON C:RU 1:701(136) 2:701(134) 3:1800 196.10.224/24 PIX-PE C:ZA 1:1957 198.9.91/24 NET-PCCNEB C:US 1:93 198.9.92/24 NET-HCCNEB C:US 1:93 198.54.203/24 TELKOMNET-C1 C:ZA 1:701(136) 2:701(134) 3:3561(11) 4:3561(218) 5:1240 198.54.204/22 TELKOMNET-C2 C:ZA 1:701(136) 2:701(134) 3:3561(11) 4:3561(218) 5:1240 198.54.208/23 TELKOMNET-C6 C:ZA 1:701(136) 2:701(134) 3:3561(11) 4:3561(218) 5:1240 198.77.165/24 NIH-NET165 C:US 1:3561(218) 2:3561(11) 3:86 198.79.90/24 ISDNET-BLK2 C:US 1:3561(218) 2:3561(11) 4:86 198.79.91/24 ISDNET-BLK2 C:US 1:3561(218) 2:3561(11) 4:86 198.79.92/24 ISDNET-BLK2 C:US 1:3561(218) 2:3561(11) 4:86 198.79.93/24 ISDNET-BLK2 C:US 1:3561(218) 2:3561(11) 4:86 198.79.94/24 ISDNET-BLK2 C:US 1:3561(218) 2:3561(11) 4:86 198.79.95/24 ISDNET-BLK2 C:US 1:3561(218) 2:3561(11) 4:86 198.81.250/24 WINCOM-DMZ4 C:CA 1:1325 198.81.251/24 WINCOM-DMZ5 C:CA 1:1325 198.81.252/24 WINCOM-DMZ7 C:CA 1:1325 198.83.14/24 TRANE-GENIX C:US 1:1325 198.99.91/24 NET-PCCNEB C:US 1:93 198.99.92/24 NET-HCCNEB C:US 1:93 198.99.171/24 WYOGOV C:US 1:1800 2:1240 3:1239 4:209 5:210 198.112.14/24 DELPHI-14 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 198.115.152/24 DELPHI-152 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 198.115.153/24 DELPHI-153 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 198.115.154/24 DELPHI-154 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 198.124.128/23 XANTH-DOE-GOV C:US 1:293(145) 2:293(144) 198.246.154/24 CHECKFREE C:US 1:1800 2:1239(144) 3:1239(218) 198.247.48/20 IA-NETBLK-1 C:US 1:3561(218) 2:3561(11) 3:1239(144) 4:93 198.247.64/18 IA-NETBLK-2 C:US 1:3561(218) 2:3561(11) 3:1239(144) 4:93 199.74.230/24 NET-CCCKNEB C:US 1:93 199.74.231/24 NET-CCCLNEB C:US 1:93 199.75.170/24 NEH-NET170 C:US 1:3561(218) 2:3561(11) 3:86 199.75.173/24 STMS-STERLING-VA-US-1 C:US 1:3561(218) 2:3561(11) 3:86 199.75.208/23 DC-IGC-ORG C:US 1:3561(218) 2:3561(11) 3:86 199.75.210/24 DC-ICG-ORG C:US 1:3561(218) 2:3561(11) 3:86 199.75.212/23 STMS-STERLING-VA-US-2 C:US 1:3561(218) 2:3561(11) 3:86 199.77.81/24 ISDNET-BLK2 C:US 1:3561(218) 2:3561(11) 4:86 199.77.82/24 ISDNET-BLK2 C:US 1:3561(218) 2:3561(11) 4:86 199.77.83/24 ISDNET-BLK2 C:US 1:3561(218) 2:3561(11) 4:86 199.77.85/24 ISDNET-BLK2 C:US 1:3561(218) 2:3561(11) 4:86 199.77.90/24 ISDNET-BLK2 C:US 1:3561(218) 2:3561(11) 4:86 199.77.91/24 ISDNET-BLK2 C:US 1:3561(218) 2:3561(11) 4:86 199.77.92/24 ISDNET-BLK2 C:US 1:3561(218) 2:3561(11) 4:86 199.77.93/24 ISDNET-BLK2 C:US 1:3561(218) 2:3561(11) 4:86 199.77.95/24 ISDNET-BLK2 C:US 1:3561(218) 2:3561(11) 4:86 199.79.206/24 INET-NCG C:US 1:1239(147) 2:1239(218) 3:1239(144) 4:1800 199.81.22/24 NETBLK-FEDEX101 C:US 1:1330 199.81.24/24 NETBLK-FEDEX101 C:US 1:1330 199.92.17/24 NET-FKCHS-ME C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.94.192/19 NETBLK-NEARNET-BBN C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.94.192/24 NETBLK-NEARNET-BBB C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.95.72/24 KESMAI72 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.95.73/24 KESMAI73 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.95.74/24 KESMAI74 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.95.75/24 KESMAI75 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.120.88/23 NET-IWCC C:US 1:1239(218) 2:1800 3:1239(144) 199.120.106/24 NET-SIOUXLAN C:US 1:1800 2:1239(144) 3:1239(218) 4:1323 199.120.107/24 NET-UOMHS-3 C:US 1:1800 2:1239(144) 3:1239(218) 4:1323 199.164.164/24 QUESTREL C:US 1:701(136) 2:701(134) 199.170.184/22 NET-JKCG C:US 1:1800 2:1239(218) 3:1239(144) 199.190.223/24 MONROERIC-CBLK C:US 1:1239(218) 2:1800 3:1239(144) 199.208.158/24 DDN-NIC4 C:US 1:3830 2:1800 3:1240 199.221.59/24 WEYERHAEUSER-NET C:US 1:1331 199.231.128/21 RFSINET C:US 1:1800 2:1239(218) 3:1239(144) 199.233.72/24 GOLGOTHA C:US 1:1800 2:1239(144) 3:1239(218) 199.240.123/24 VITALIMG C:US 1:3561(218) 2:3561(11) 3:1239(144) 4:93 199.245.93/24 INVEST C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 200.0.136/24 MINREXT-PERU C:PE 1:1800 2:1239 3:1240 200.14.192/24 SAVAL-NET C:CL 1:3561(218) 2:3561(11) 3:86 202.47.0/24 STI-PH C:PH 1:1239(144) 2:1800 3:1239(218) 202.72.0/22 GLOBALLINK-HK C:HK 1:701(136) 2:701(134) 202.242.8/21 OUENET C:JP 1:297(144) 2:297(145) 202.242.89/24 JSCSNET C:JP 1:1239(144) 2:1800 3:1239(218) 202.243.128/20 SPINS C:JP 1:1239(144) 2:1800 3:1239(218) 202.245.32/19 JMANET C:JP 1:701(136) 2:701(134) 3:1800 4:1239 5:1240 202.249.64/18 MITI-100 C:JP 1:297(144) 2:297(145) 202.249.128/19 MITI-100 C:JP 1:297(144) 2:297(145) 202.251.92/23 NARAMED C:JP 1:297(144) 2:297(145) 202.254.227/24 SUNET C:JP 1:297(144) 2:297(145) 204.29.144/24 PSYBERNET C:US 1:1239(144) 2:1800 3:1239(218) 204.50.61/24 NET-IRENYX61 C:CA 1:1240 2:1800 3:1239 204.73.60/22 NETBLK-SMMC3 C:US 1:3561(218) 2:3561(11) 3:1225(130) 4:1225(129) 5:1225(131) 6:1239 7:1240 8:1800 204.75.249/24 RSCNET2 C:US 1:3561(11) 2:3561(218) 3:2150(135) 4:200(128) 5:200(144) 204.78.64/18 ESCAM-K12-FL C:US 1:3561(218) 2:3561(11) 4:86 204.80.163/24 MINJUS C:PE 1:1800 2:1239 3:1240 204.87.235/24 NET-MVANGEL C:US 1:1800 2:1239(218) 3:1239(144) 204.96.179/24 WHOLEFOODS-DOM C:US 1:1239(147) 2:1239(218) 3:1239(144) 4:1800 204.107.32/19 FOUNDATION-CLINIC C:US 1:1240 2:1800 3:1239 204.126.116/23 FL-EOG C:US 1:3561(218) 2:3561(11) 4:86 204.128.134/24 NET-NLIS C:US 1:1239(144) 2:1800 3:1239(218) 4:3830 204.128.195/24 OSBON C:US 1:2386 2:1321 204.128.203/24 SDINTERNET C:US 1:3830 204.128.226/24 ATTITUDES C:US 1:1321 2:2386 204.130.214/24 LSMSA C:US 1:3561(218) 2:3561(11) 3:86 204.138.158/24 JANNA-NET C:CA 1:1240 2:1800 3:1239 204.149.88/24 CYBERNET-NETS C:US 1:1329 204.149.89/24 CYBERNET-NETS C:US 1:1329 204.149.90/24 CYBERNET-NETS C:US 1:1329 204.149.91/24 CYBERNET-NETS C:US 1:1329 204.149.92/24 CYBERNET-NETS C:US 1:1329 204.149.93/24 CYBERNET-NETS C:US 1:1329 204.149.94/24 CYBERNET-NETS C:US 1:1329 204.149.95/24 CYBERNET-NETS C:US 1:1329 204.150.72/24 ANS-C-BLOCK3-150 C:US 1:1335 204.152.54/23 LECHTERS C:US 1:3561(218) 2:3561(11) 3:86 5:1879 204.153.60/22 CAPGEM-NET C:US 1:1800 2:1239(218) 3:1239(144) 204.164.112/24 HADCO2-112 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.164.113/24 HADCO2-113 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.164.114/24 HADCO2-114 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.164.115/24 HADCO2-115 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.164.116/24 HADCO2-116 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.164.117/24 HADCO2-117 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.164.118/24 HADCO2-118 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.164.119/24 HADCO2-119 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.168.20/24 NET-NYSERNET C:US 1:1239(218) 2:1800 3:1239(144) 204.181.89/24 COXSMITH.COM C:US 1:1239(147) 2:1239(144) 3:1239(218) 4:1800 204.187.104/24 NET-MMLTD C:CA 1:1240 2:1800 3:1239 204.199.192/19 OSCEOLA-K12-FL-US C:US 1:3561(218) 2:3561(11) 4:86 204.212.160/24 PUNKNET C:US 1:1239(144) 2:1800 204.212.161/24 SANSUM C:US 1:1239(144) 2:1800 204.220.145/24 ICONOVEX C:US 1:3561(218) 2:3561(11) 3:1225(130) 4:1225(129) 5:1225(131) 6:1239 7:1240 8:1800 204.220.155/24 NET-CRAY-C2 C:US 1:3561(218) 2:3561(11) 3:1225(130) 4:1225(129) 5:1225(131) 6:1239 7:1240 8:1800 204.221.16/20 THELINK C:US 1:3561(218) 2:3561(11) 3:1225(130) 4:1225(129) 5:1225(131) 6:1239 7:1240 8:1800 204.221.32/22 THELINK1 C:US 1:3561(218) 2:3561(11) 3:1225(130) 4:1225(129) 5:1225(131) 6:1239 7:1240 8:1800 204.225.155/24 NET-IMS C:CA 1:1240 2:1800 3:1239 204.248.0/24 SUPERTREKNET-248 C:US 1:1239(218) 2:1800 3:1239(144) 4:3561(218) 204.248.1/24 SUPERTREKNET C:US 1:1239(218) 2:1800 3:1239(144) 4:3561(218) 204.248.36/24 EKLEKTIA-DOM C:US 1:1239(218) 2:1800 3:1239(144) 204.252.180/22 UPSTEL C:US 1:701(136) 2:701(134) 204.252.240/20 WEBNET C:US 1:701(136) 2:701(134) 204.253.184/21 SHOUTING C:US 1:701(136) 2:701(134) 204.254.0/20 COMPUTOPIA C:US 1:701(136) 2:701(134) 205.132.48/21 CAMPNETSYS C:US 1:1239(218) 2:1800 3:1239(144) 205.160.38/24 IADB.ORG C:US 1:1800 2:1239(218) 3:1239(144) 205.160.39/24 IADB.ORG C:US 1:1800 2:1239(218) 3:1239(144) Deletions: --198.77.74/24 EAGLENET-C-77-74 C:US 1:3561(218) 2:3561(11) 3:86 --198.77.75/24 EAGLENET-C-77-75 C:US 1:3561(218) 2:3561(11) 3:86 --198.205.32/24 ALCATLDN-C-205-32 C:US 1:3561(218) 2:3561(11) 3:114 --198.247.48/24 NET-IA-REGENTS C:US 1:93 --198.247.49/24 ICN-DIALUP C:US 1:93 --198.247.50/24 IA-GW-FRELAY C:US 1:93 --198.247.51/24 IA-GILBERT C:US 1:93 --198.247.52/24 IA-ANKENY C:US 1:93 --198.247.53/24 IA-BURLINGTN C:US 1:93 --198.247.54/24 IA-NTAMA C:US 1:93 --198.247.55/24 IA-CRWASH C:US 1:93 --198.247.56/24 IA-GW-ICN C:US 1:93 --198.247.57/24 NET-WMPENN C:US 1:93 --198.247.58/24 NET-MIU2 C:US 1:93 --198.247.59/24 NET-MIU3 C:US 1:93 --198.247.60/24 NET-MIU4 C:US 1:93 --198.247.61/24 IA-AMES C:US 1:93 --198.247.64/24 NET-IA-EXNET64 C:US 1:93 --198.247.65/24 NET-IA-EXNET65 C:US 1:93 --198.247.66/24 NET-IA-EXNET66 C:US 1:93 --198.247.67/24 NET-IA-EXNET67 C:US 1:93 --198.247.68/24 NET-IA-EXNET68 C:US 1:93 --198.247.69/24 NET-IA-EXNET69 C:US 1:93 --198.247.70/24 NET-IA-EXNET70 C:US 1:93 --198.247.71/24 NET-IA-EXNET71 C:US 1:93 --198.247.72/24 NET-IA-EXNET72 C:US 1:93 --198.247.73/24 NET-IA-EXNET73 C:US 1:93 --198.247.74/24 NET-IA-EXNET74 C:US 1:93 --198.247.75/24 NET-IA-EXNET75 C:US 1:93 --198.247.76/24 NET-IA-EXNET76 C:US 1:93 --198.247.77/24 NET-IA-EXNET77 C:US 1:93 --198.247.78/24 NET-IA-EXNET78 C:US 1:93 --198.247.79/24 NET-IA-EXNET79 C:US 1:93 --198.247.80/24 NET-IA-EXNET80 C:US 1:93 --198.247.81/24 NET-IA-EXNET81 C:US 1:93 --198.247.82/24 NET-IA-EXNET82 C:US 1:93 --198.247.83/24 NET-IA-EXNET83 C:US 1:93 --198.247.84/24 NET-IA-EXNET84 C:US 1:93 --198.247.85/24 NET-IA-EXNET85 C:US 1:93 --198.247.86/24 NET-IA-EXNET86 C:US 1:93 --198.247.87/24 NET-IA-EXNET87 C:US 1:93 --198.247.88/24 NET-IA-EXNET88 C:US 1:93 --198.247.89/24 NET-IA-EXNET89 C:US 1:93 --198.247.90/24 NET-IA-EXNET90 C:US 1:93 --198.247.91/24 NET-IA-EXNET91 C:US 1:93 --198.247.92/24 NET-IA-EXNET92 C:US 1:93 --198.247.93/24 NET-IA-EXNET93 C:US 1:93 --198.247.94/24 NET-IA-EXNET94 C:US 1:93 --198.247.95/24 NET-IA-EXNET95 C:US 1:93 --198.247.96/24 WARTBURG-C-247-96 C:US 1:93 --198.247.97/24 WARTBURG-C-247-97 C:US 1:93 --198.247.98/24 WARTBURG-C-247-98 C:US 1:93 --198.247.99/24 WARTBURG-C-247-99 C:US 1:93 --198.247.103/24 WARTBURG-C-247-103 C:US 1:93 --198.247.116/24 NET-IA-NIACC C:US 1:93 --199.184.191/24 NET-COMLAND C:US 1:1800 2:1239(144) 3:1239(128) Expanded listing, sorted by country, then by organization: ========================================================== The "Expanded Listings" section of this NWG report has been retired since it is sorted by countries and network organization addresses. The replacement configuration generation system is based on the Internet Routing Registry (briefly called the "Global Routing Registry"). See the file ftp.ra.net:pub/radb/OVERVIEW for more information. The remainder of this report will also be retired shortly. ========================================================== The following Midlevel/Regional peering sessions have also been added: AS 1239 - SprintLink - ENSS 147 Peer: 192.41.177.241 - Sprint - (192.41.177.241) AS 3561 - MCI-RESTON - ENSS 147 Peer: 192.41.177.181 - MCI - cpe2.washington.mci.net Peer: 198.32.130.227 - MCI - cpe3.chicago.mci.net AS690 CIDR Squeezings Report: 11180 Nets, 183 ASs, 3118 Aggregates ------------------------------------------------------------------- 11180 (83%) of the ever-announced more-specific routes within aggregates have been withdrawn. 1305 of those were withdrawn within the last week. 170 the week before that. 410 the week before that. 183 ASs have registered aggregates in the PRDB. 164 of those are announcing aggregates. 87 have withdrawn at least one more specific route. 3118 Aggregates are configured. 2102 of these were Top-Level Aggregates (not nested in another aggregate). 1612 of these are being announced to AS690. 1019 of those have at least one subnet configured (the other 593 may be saving the Internet future subnet announcements). 874 have stopped announcing at least one configured more specific route. 840 have stopped announcing half of their configured more specific routes. 801 have stopped announcing most (80%) of their more specific routes. See home.merit.edu:pub/nsfnet/cidr/cidr_savings for more detail. ----------------------------------------------------------- ========================================================== The configuration reports which reflect today's update will be available for anonymous ftp on nic.merit.edu by 08:00 EST : configuration reports -- nic.merit.edu:nsfnet/announced.networks: as-as.now as-gw.now ans_core.now country.now net-comp.now nets.doc nets.non-classful nets.tag.now nets.unl.now NSS routing software configuration files -- nic.merit.edu:nsfnet/backbone.configuration: gated.nss<NSS number>.t3p Information is also avaiable through the PRDB whois server. Type "whois -h prdb.merit.edu help" for details. -------------------------------------------------------------------------- PRDB CHANGES: (Updated January 19, 1994) As of 1/19/95, ACKs and NAKs will no loger be required (or even read) in the processing of NACRs. In early 1995, as part of the transition to the new Internet Routing Registry (IRR), the Policy Routing Database (PRDB) will be retired. Many of the functions of the PRDB (including generation of router configurations for NSFNET) will be produced based on data from the Global Routing Registry. This change to the NSFNET Backbone service will involve the following changes: - The method for submitting new nets to be routed over AS690 will change. Instead of submitting a NACR to nsfnet-admin(a)merit.edu, you will need to submit a "route template" to auto-dbm(a)ra.net . - Additions and entries to the new registry will be made by the Home AS which creates the route for each net, rather than being submitted by a AS690 peer AS. - Most of the PRDB reports (listed above) will no longer be produced. Equivalent information for most of these reports is available from the global Routing Registry. These are major changes to the system. These changes are being made in order to migrate NSFNET customers and the global user community to a global Internet Routing Registry system, which will be more capable of supporting user needs after the termination of the NSFNET Backbone services in April 1995. For more information, set your web browser to http://www.ra.net/rrinfo.html , or use anonymous ftp to obtain the files "OVERVIEW" and from the directory "ftp.ra.net:pub/radb". Merit would like to minimize the number of problems that this transition may cause you. In order to help us help you through the transition, please send your concerns, your needs, and suggestions on how we can make this happen smoothly to merit-ie(a)merit.edu. The archived discussion list "db-disc(a)merit.edu" also exists for discussion of PRDB and RADB issues. Send a message to "db-disc-request(a)merit.edu" to subscribe. --Dale Johnson (dsj(a)merit.edu) -------------------------------------------------------------------------- Please send all requests for configuration changes to nsfnet-admin(a)merit.edu using the NSFNET configuration forms. The forms are available on-line from the nic.merit.edu machine. Use ftp and the anonymous login to get on the machine. Do a "cd nsfnet/announced.networks" and get the files template.net, template.net.README, template.gate, and template.as. *** Note: As of March 1, 1994, NSFNET AUP NACRs must use the template.net *** (NACR) version 7.1, or the NACR will be returned unprocessed. ******************************* --Stephen McNutt Merit/NSFNET smm(a)merit.edu --Steven J. Richardson Merit/NSFNET sjr(a)merit.edu

1 0