- Test - lists.nanog.org

Re: Has PSI been assigned network 1?
by Sean Doran 26 Apr '95

26 Apr '95

Hi - All our junior people are immediately deployed to projects. One such person was brought into our engineering group and practically immediately was given responsibility for making all of NYSERNET work and handling whatever escalations he could. Another is deployed in dialup and in assisting with routing matters. Another is busy dealing with research and resource planning for how we want to scale. I can think of innumerable engineering and operations tasks that need doing before deploying a junior engineering type to writing documentation. OTOH, we have been working with marketing on the customer handbook (http://www.sprintlink.net/ has various drafts), so I imagine that if we had a clever tech writer remarkably skilled at finding the right moment to talk to busy engineering folk, we could produce something. Funnily enough, that's what Vadim and I have already asked management for, however that's with a view to documenting our internal procedures so that we can scale up our own engineering and operations, not to mention all the other documentation that we need doing internally. So, to extend the point that Geoff made earlier -- any resource a busy operator has will get deployed into making that operator's part of the global Internet _work_, not into helping out other people. This is not due to a mean lack of altruism, but rather to the realities of life in a global network that doubles in size and traffic severy six-to-nine months or so. Now, if you go talk to our marketing about the possibilities of increasing revenue via some of the in-house documentation we're planning, you might have a big operator actually produce a book along the lines you are thinking, or putting together a page for beginning Internet operators. Try bouncing some ideas off our marketing types; I'd be happy to pass you on to one in private email. Sean.

2 1

Re: Has PSI been assigned network 1?
by Hank Nussbacher 25 Apr '95

25 Apr '95

On Sun, 23 Apr 1995 12:33:54 -0500 (CDT) you said: >Hank, > >Enduser filtering (CERN) is in principle completely different from what we >(might if not possible else) do: > >I am not supposed to filter anything between meetpoints and customers, >because I agree to some people who pay for it to provide Internet access. > >I would filter nothing at all (curretnly do filter nothing), which does >not mean that my suport hosts and networks are open. >Filtering comes alo into place when customers want only access between >certain networks, >but in general > >NSPs/ISPs are not supposed to filter at all. > >Routing is different. We filter routing updates (not access filters) to >accelerate BGP convergence. We filter what we announce to the outside >world (of course not all the trash we get in). I don't filter outgoing routing updates to speed BGP convergence. I do it so as not to pollute the Internet with leaked bad nets. It has happened to me and has happened to everyone. Just look at the recent nets that Australia was leaking. If the routing access lists were automatically created every day based on the data in the routing DB, then this would not happen. Of course, no one can force you but your service provider can filter what he/she hears from you based on the same rules. Then you have a double secure routing scheme. > >Mike >Michael F. Nittmann >nittmann(a)wis.com Hank Nussbacher

11 13

refresher - what's happening
by epg＠merit.edu 25 Apr '95

25 Apr '95

Hi, At 0700 EDT on Tuesday, April 25, all peering sessions on ENSSes: 128 129 130 131 133 134 135 137 139 140 141 142 143 145 will be commented out of the routing configuration files. If there is a catastrophic failure tomorrow morning, Merit will advise the ANS NOC to roll back to the previous configuration (the one installed on Tuesday morning). If it is determined that problems are isolated to individual autonomous systems, Merit will enable the sessions with those individual autonomous sytems. If there are individual routes from many sources which are unreachable, Merit will designate one emergency configuration time period at which all of the independent additions wil be made. If you are experiencing problems tomorrow after 0700 EDT, please call 1-800-456-6300 or 1-313-677-7333. The NOC operators will page a Merit engineer to help you. If you still have email access, you may send a message to trouble(a)ans.net. Thanks for your help in getting prepared for this day. --Elise

4 4

Re: Why Vadim likes statics
by Hank Nussbacher 25 Apr '95

25 Apr '95

On Mon, 24 Apr 1995 17:26:41 -0400 you said: >> This sounds a lot like the slippery slope of static routing being the >> most stable, so we should encourage its use Internet wide. I -know- >> Karl D. >> (and others that depend on dynamic routing for alternate provider >> fallback) will kick at this. > >On the contrary, Bill, being set up to propagate IGP information to your EGP >in situations where not absolutely necessary seems to be a perversion of the >whole intent of EGPs vs. IGPs. Perhaps it's time to rethink for a moment why >the whole Internet isn't just running one big IGRP or OSPF cloud. After getting burned numerous times by end node nets that polluted our IGRP cloud, we now connect all new single homed customers via static routes and filter out everything heard from them. If they are multihomed here we do IGRP and if they are multihomed across different ASs we do BGP. The customers also like it since it increases their bandwidth on their line rather than hearing routing updates all the time. For customers on 9.6kb and 19.2kb lines this made a difference. Remember when you bill on bandwidth used (ifInOctets/ifOutOctets) you are billing also for routing updates! Your customers will like you if you reduce their bill. >Robert E. Seastrom -- rs(a)digex.net Hank Nussbacher

1 0

Re: Why Vadim likes statics
by Robert E. Seastrom 25 Apr '95

25 Apr '95

> This sounds a lot like the slippery slope of static routing being the > most stable, so we should encourage its use Internet wide. I -know- > Karl D. > (and others that depend on dynamic routing for alternate provider > fallback) will kick at this. On the contrary, Bill, being set up to propagate IGP information to your EGP in situations where not absolutely necessary seems to be a perversion of the whole intent of EGPs vs. IGPs. Perhaps it's time to rethink for a moment why the whole Internet isn't just running one big IGRP or OSPF cloud. Kudos to the people who have realized that for singly-connected networks, the BGP advert. status of the network should change precisely as often as the policy (eg. ONCE, when you set the network up, and AGAIN if they change to another provider). Granted, there are a lot of people who are _not_ singly connected, but they (folks like Karl D.) are (a) running BGP themselves, and (b) sophisticated enough to pull up their own networks at the periphery of their cloud. The point I'm making is that you shouldn't be BGP peering with customers who are not multiply attached (that's what IGPs are for), and you should not be propagating your IGP information to your BGP except in rare cases. Let IGPs do what they are best at (dynamic information and reachability on a micro level) and EGPs do what they're best at (reachability and policy on the macro level) Simple, eh? By the way, yes, I am biased. I have been saying that this is the only sane way to do routing adverts to other providers for neigh unto two years now. ---Rob Robert E. Seastrom -- rs(a)digex.net Network Engineer, Digex International My posting, my opinions, not speaking for the company, etc. etc.

2 1

Re: Operations training materials
by geoffw＠nexsys.net 25 Apr '95

25 Apr '95

> > >Christian Huitema > > Please do not invoke the names of IAB folks as routing authorities > on the NANOG mailing list. > > Thank you. > > Sean. > I make no claim as to whether this person is a "routing authority" I mearly state that they wrote a book about Routing on the internet.

3 2

Re: Why Vadim likes statics
by Vadim Antonov 25 Apr '95

25 Apr '95

Bill, your "vision" about statics taking over made me laugh for quite a while. Nobody is about to replace dynamic routing with static. What Randy is talking about is a technique to avoid generation irrelevant rotuing updates. I.e. the rest of the network does not have to be informed that some of your interior LANs fell off, ok? >In the end, the Internet looks just like the telco mesh. At least telephones work; and work reliably. Unlike Internet. And telephone network is orders of magnitude bigger than Internet; and went through numerous radical technology changes without losing integrity. Guess, telco engineers did something right. --vadim

3 2

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

25 Apr '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 EDT: Total = As + Bs + Cs + Aggs Registered Networks 50556 = 29 5404 41583 3540 Configured Networks 47915 = 29 5398 39011 3477 Added Networks 88 = 0 3 51 34 Deleted Networks 216 = 0 0 192 24 IP address Net name Country Priority:AS ---------- -------- ------- ----------- 39.17.199/24 ASN4551-TESTNET C:US 3:3561 138.115/16 IGDS-NET C:US 1:297(145) 2:297(144) 147.146/16 NET-EQUIFAX C:US 1:2685 2:701(147) 3:701(134) 4:3561(147) 5:3561(218) 6:3561(27) 7:3561(11) 8:3561(144) 162.56/16 BARNETT C:US 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) 165.25.0/24 NET-CA-CC-GOV-ZA C:ZA 1:1957 192.34.248/24 HP18 C:US 1:2551(147) 2:1321 192.152.249/24 NET-CCPLNET C:US 10:93 1:3561(27) 2:3561(218) 3:3561(147) 4:3561(11) 5:3561(144) 6:1239(218) 7:1239(147) 8:1239(144) 9:1800 192.223.32/24 NETBLK-LAS C:US 1:1323 2:1321 193.8.177/24 MGB-ICS-2 C:CH 1:701(147) 2:701(134) 3:1800 193.56.15/24 DIGITAL-EUROPE C:FR 1:1800 2:1240 3:1133 4:1674 193.56.199/24 FR-ASFO84 C:FR 1:1800 2:1240 3:1133 4:1674 193.67.146/24 MSC-IRT C:NL 1:701(147) 2:701(134) 3:1800 193.78.23/24 NLNET-MAS C:NL 1:701(147) 2:701(134) 3:1800 193.79.144/24 ICL-BENELUX C:NL 1:701(147) 2:701(134) 3:1800 193.79.208/24 XXLINK C:NL 1:701(147) 2:701(134) 3:1800 193.81.239/24 PING-NET C:AT 1:701(147) 2:701(134) 3:1800 193.81.240/24 CAFESTEIN-NET C:AT 1:701(147) 2:701(134) 3:1800 194.112.28/24 PSG-NET C:DE 1:2149 2:174 194.115/16 EUNETDE-AGG-194-115 C:DE 1:701(147) 2:701(134) 3:1800 194.139/16 EUNETDE-AGG-194-139 C:DE 1:701(147) 2:701(134) 3:1800 198.69.144/21 TIAC8-B C:US 1:1800 2:1239(218) 3:1239(144) 198.69.224/19 TIAC32-A C:US 1:1800 2:1239(218) 3:1239(144) 198.70.40/21 TIAC8-A C:US 1:1800 2:1239(218) 3:1239(144) 198.79.162/23 NUNEZCCNET C:US 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) 198.79.164/22 NUNEZCCNET C:US 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) 198.83.165/24 USROBOTICS-NET C:US 1:1692 198.137.182/23 CENTIGRAM2 C:US 1:2551(147) 2:1321 198.150.48/22 LSELHL C:US 1:3561(27) 2:3561(218) 3:3561(147) 4:3561(11) 5:3561(144) 6:1225 198.150.68/22 CTENET C:US 1:3561(27) 2:3561(218) 3:3561(147) 4:3561(11) 5:3561(144) 6:1225 198.150.125/24 MBCO C:US 1:3561(27) 2:3561(218) 3:3561(147) 4:3561(11) 5:3561(144) 6:1225 198.150.126/24 BCSEW-NET1 C:US 1:3561(27) 2:3561(218) 3:3561(147) 4:3561(11) 5:3561(144) 6:1225 198.150.236/22 CTENET1 C:US 1:3561(27) 2:3561(218) 3:3561(147) 4:3561(11) 5:3561(144) 6:1225 198.178.214/24 FTYBIZ-NET C:US 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) 199.3.128/20 TIAC16-B C:US 1:1800 2:1239(218) 3:1239(144) 199.5.176/23 NETBLK-THOMAS-C C:US 1:2551(147) 2:1321 199.5.178/24 NETBLK-THOMAS-C C:US 1:2551(147) 2:1321 199.20.18/23 SAMFORD-NET C:US 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) 199.20.20/22 SAMFORD-NET C:US 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) 199.20.24/23 SAMFORD-NET C:US 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) 199.71.232/21 NETBLK-CA-NET-TEST C:CA 1:3561(27) 2:3561(218) 3:3561(147) 4:3561(11) 5:3561(144) 199.120.109/24 NET-DRIS C:US 1:1239(147) 2:1239(144) 3:1239(218) 4:1800 5:1323 199.120.110/24 NET-MEBBS C:US 1:1239(147) 2:1239(144) 3:1239(218) 4:1800 5:1323 199.120.197/24 NET-TLOGIC-NET C:US 1:3830 2:4388 3:1800 4:1239 5:1240 199.131.143/24 USFPL-NET1 C:US 1:3561(27) 2:3561(218) 3:3561(147) 4:3561(11) 5:3561(144) 6:1225 199.131.144/21 USFPL-NETBLK1 C:US 1:3561(27) 2:3561(218) 3:3561(147) 4:3561(11) 5:3561(144) 6:1225 199.131.152/22 USFPL-NETBLK2 C:US 1:3561(27) 2:3561(218) 3:3561(147) 4:3561(11) 5:3561(144) 6:1225 200.14.94/24 SEGEGOB C:CL 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) 202.40.148/23 STAR C:HK 1:701(147) 2:701(134) 202.44.238/24 TIAC-TH C:TH 1:701(147) 2:701(134) 202.66.18/23 STAR C:HK 1:701(147) 2:701(134) 202.66.18/24 STAR C:HK 1:701(147) 2:701(134) 202.66.19/24 STAR C:HK 1:701(147) 2:701(134) 202.66.20/23 STAR C:HK 1:701(147) 2:701(134) 202.66.20/24 STAR C:HK 1:701(147) 2:701(134) 202.66.21/24 STAR C:HK 1:701(147) 2:701(134) 202.66.22/24 STAR C:HK 1:701(147) 2:701(134) 204.50.96/20 NET-SENTEX C:CA 1:1240 2:1800 3:1239 204.118.250/24 NET-INTELE C:US : 204.118.251/24 NET-INTELE C:US : 204.118.252/24 NET-INTELE C:US : 204.118.253/24 NET-INTELE C:US : 204.118.254/24 INTELE-NET C:US : 204.118.255/24 NET-INTELE C:US : 204.126.132/23 HOWARDCC C:US 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) 204.165.254/24 TCB-254 C:US 1:3561(218) 2:3561(147) 3:3561(27) 4:3561(11) 5:3561(144) 6:560 7:701(147) 8:701(134) 204.180.64/19 TIAC32-B C:US 1:1800 2:1239(218) 3:1239(144) 204.231.97/24 INTERPAC1 C:IT 1:2149 2:174 204.239.83/24 UNBC-DMZ C:CA 1:1331 204.239.178/24 LEDCOR C:CA 1:1331 204.246.128/24 NET-INTELE C:US : 204.246.129/24 NET-INTELE C:US : 204.246.130/24 NET-INTELE C:US : 204.246.131/24 NET-INTELE C:US : 204.246.132/24 NET-INTELE C:US : 204.246.133/24 NET-INTELE C:US : 204.246.134/24 NET-INTELE C:US : 204.246.135/24 NET-INTELE C:US : 204.254.224/21 TIG C:US 1:701(147) 2:701(134) 204.255.72/22 IWORK C:US 1:701(147) 2:701(134) 205.149.0/21 EMF-NET C:US 1:3561(11) 2:3561(144) 3:3561(27) 4:3561(147) 5:3561(218) 205.151.190/24 COMBYNE-QC-CA C:CA 1:1324(36) 2:1324(32) 3:2493(35) 4:2493(91) 205.151.191/24 LASINC-QC-CA C:CA 1:1324(36) 2:1324(32) 3:2493(35) 4:2493(91) 205.161.128/20 TIAC16-A C:US 1:1800 2:1239(218) 3:1239(144) 205.166.48/24 MR-COM C:US 1:2551(147) 2:1321 205.167.36/23 NETBLK-GWCC C:US 1:3830 2:4388 205.205/16 INTERLINK C:CA 1:1324(36) 2:1324(32) 3:2493(35) 4:2493(91) 205.216/14 MCI-PROVIDER4 C:US 1:3561(27) 2:3561(218) 3:3561(147) 4:3561(11) 5:3561(144) 205.232.3/24 BROOME-NET C:US 1:1239(218) 2:1239(147) 3:1239(144) 4:1800 Deletions: --129.250.201/24 PREPNET C:US 1:1324(35) 2:1324(32) 3:3577 4:204 5:1206 --192.21.10/24(U) FORMTEK C:US 1:3577 2:1324 --192.21.13/24(U) FORMTEK C:US 1:3577 2:1324 --192.21.14/24(U) FORMTEK C:US 1:3577 2:1324 --192.21.30/24(U) FORMTEK C:US 1:3577 2:1324 --192.148.169/24 FORMTEK2 C:US 1:3577 2:1324(35) 3:1324(32) --192.190.203/24 PERFSIGNAL C:US 1:3561(218) 2:3561(147) 3:3561(27) 4:3561(144) --192.204.8/24(U) LEGENT-INTL1 C:US 1:3577 2:204 3:1206 4:1324 --192.204.9/24(U) LEGENT-INTL2 C:US 1:3577 2:204 3:1206 4:1324 --192.204.16/24(U) LEGENT-NYD1 C:US 1:3577 2:204 3:1206 4:1324 --192.204.17/24(U) LEGENT-NYD2 C:US 1:3577 2:204 3:1206 4:1324 --192.204.20/24(U) WESTMINSTER1 C:US 1:3577 2:204 3:1206 4:1324 --192.204.21/24(U) WESTMINSTER2 C:US 1:3577 2:204 3:1206 4:1324 --192.204.22/24(U) WESTMINSTER3 C:US 1:3577 2:204 3:1206 4:1324 --192.204.23/24(U) WESTMINSTER4 C:US 1:3577 2:204 3:1206 4:1324 --192.204.24/24(U) MTLEBO C:US 1:3577 2:204 3:1206 4:1324 --192.204.56/24(U) RAI C:US 1:3577 2:204 3:1206 4:1324 --192.204.90/24(U) AIU2 C:US 1:3577 2:204 3:1206 4:1324 --192.204.91/24(U) NET-AIU3 C:US 1:3577 2:204 3:1206 4:1324 --192.204.98/24(U) USS-NET-4 C:US 1:3577 2:204 3:1206 4:1324 --192.204.99/24(U) USS-NET-5 C:US 1:3577 2:204 3:1206 4:1324 --192.204.100/24(U) USS-NET-6 C:US 1:3577 2:204 3:1206 4:1324 --192.204.101/24(U) USS-NET-7 C:US 1:3577 2:204 3:1206 4:1324 --192.204.102/24(U) USS-NET-8 C:US 1:3577 2:204 3:1206 4:1324 --192.204.112/24(U) SEWICKLEY C:US 1:3577 2:1324 --192.204.113/24(U) SEWICKLEY-2 C:US 1:3577 2:1324 --192.204.126/24(U) WCCC-1-C-204-126 C:US 1:3577 2:204 3:1206 4:1324 --192.204.127/24(U) WCCC-1C-204-127 C:US 1:3577 2:204 3:1206 4:1324 --192.204.158/24(U) LGNT C:US 1:3577 2:204 3:1206 4:1324 --192.204.163/24(U) CHESCO-2-C-204-163 C:US 1:3577 2:204 3:1206 4:1324 --192.204.168/24(U) EMPRISE C:US 1:3577 2:204 3:1206 4:1324 --192.204.169/24(U) EMPRISE C:US 1:3577 2:204 3:1206 4:1324 --192.204.174/24(U) WCC-3 C:US 1:3577 2:204 3:1206 4:1324 --192.204.176/24(U) MERCY-1 C:US 1:3577 2:204 3:1206 4:1324 --192.204.177/24(U) MERCY-1 C:US 1:3577 2:204 3:1206 4:1324 --192.204.188/24(U) TRINET C:US 1:3577 2:204 3:1206 4:1324 --192.204.189/24(U) TRINET-2 C:US 1:3577 2:204 3:1206 4:1324 --192.204.208/24(U) CHESCO-CIDR C:US 1:3577 2:1324(32) 3:1324(35) --192.204.209/24(U) CHESCO-CIDR C:US 1:3577 2:1324(32) 3:1324(35) --192.204.210/24(U) CHESCO-CIDR C:US 1:3577 2:1324(32) 3:1324(35) --192.204.211/24(U) CHESCO-CIDR C:US 1:3577 2:1324(32) 3:1324(35) --192.204.212/24(U) CHESCO-CIDR C:US 1:3577 2:1324(32) 3:1324(35) --192.204.213/24(U) CHESCO-CIDR C:US 1:3577 2:1324(32) 3:1324(35) --192.204.214/24(U) CHESCO-CIDR C:US 1:3577 2:1324(32) 3:1324(35) --192.204.215/24(U) CHESCO-CIDR C:US 1:3577 2:1324(32) 3:1324(35) --192.204.216/24(U) CHESCO-CIDR C:US 1:3577 2:1324(32) 3:1324(35) --192.204.217/24(U) CHESCO-CIDR C:US 1:3577 2:1324(32) 3:1324(35) --192.204.218/24(U) CHESCO-CIDR C:US 1:3577 2:1324(32) 3:1324(35) --192.204.219/24(U) CHESCO-CIDR C:US 1:3577 2:1324(32) 3:1324(35) --192.204.220/24(U) CHESCO-CIDR C:US 1:3577 2:1324(32) 3:1324(35) --192.204.221/24(U) CHESCO-CIDR C:US 1:3577 2:1324(32) 3:1324(35) --192.204.222/24(U) CHESCO-CIDR C:US 1:3577 2:1324(32) 3:1324(35) --192.204.223/24(U) CHESCO-CIDR C:US 1:3577 2:1324(32) 3:1324(35) --192.204.254/24 PADER-2 C:US 1:3577 2:204 3:1206 4:1324(35) 5:1324(32) --192.245.96/24 VVI C:US 1:3561(218) 2:3561(147) 3:3561(27) 4:3561(144) --194.112.29/24 MICROTEC C:DE 1:2149 2:174 --199.5.176/24 THOMAS_BROS C:US 1:2551(147) 2:1321 --199.227.1/24 NETBLK-CYBERGATE C:US 1:1800 2:1239(144) 3:1239(218) --199.227.2/24 NETBLK-CYBERGATE C:US 1:1800 2:1239(144) 3:1239(218) --199.227.3/24 NETBLK-CYBERGATE C:US 1:1800 2:1239(144) 3:1239(218) --199.227.4/24 NETBLK-CYBERGATE C:US 1:1800 2:1239(144) 3:1239(218) --199.227.5/24 NETBLK-CYBERGATE C:US 1:1800 2:1239(144) 3:1239(218) --199.227.6/24 NETBLK-CYBERGATE C:US 1:1800 2:1239(144) 3:1239(218) --199.227.7/24 CYBER-BLOCK-C-227-7 C:US 1:1800 2:1239(144) --199.227.8/24 CYBER-BLOCK-C-227-8 C:US 1:1800 2:1239(144) --199.227.9/24 NET-CYBERGATE-1 C:US 1:1800 2:1239(144) 3:1239(218) --199.227.10/24 CYBER-BLOCK-C-227-10 C:US 1:1800 2:1239(144) 3:1239(218) --199.227.11/24 CYBER-BLOCK-C-227-11 C:US 1:1800 2:1239(144) 3:1239(218) --199.227.12/24 CYBER-BLOCK-C-227-12 C:US 1:1800 2:1239(144) 3:1239(218) --199.227.13/24 CYBER-BLOCK-C-227-13 C:US 1:1800 2:1239(144) 3:1239(218) --199.227.14/24 CYBER-BLOCK-C-227-14 C:US 1:1800 2:1239(144) 3:1239(218) --199.227.15/24 CYBER-BLOCK-C-227-15 C:US 1:1800 2:1239(144) 3:1239(218) --199.227.16/24 CYBER-BLOCK-C-227-16 C:US 1:1800 2:1239(144) 3:1239(218) --199.227.17/24 CYBER-BLOCK-C-227-17 C:US 1:1800 2:1239(144) 3:1239(218) --199.227.18/24 CYBER-BLOCK-C-227-18 C:US 1:1800 2:1239(144) 3:1239(218) --199.227.19/24 CYBER-BLOCK-C-227-19 C:US 1:1800 2:1239(144) 3:1239(218) --199.227.20/24 CYBER-BLOCK-C-227-20 C:US 1:1800 2:1239(144) 3:1239(218) --199.227.21/24 CYBER-BLOCK-C-227-21 C:US 1:1800 2:1239(144) 3:1239(218) --199.227.23/24 CYBER-BLOCK-C-227-23 C:US 1:1800 2:1239(144) 3:1239(218) --199.227.24/24 CYBER-BLOCK-C-227-24 C:US 1:1800 2:1239(144) --199.227.25/24 CYBER-BLOCK-C-227-25 C:US 1:1800 2:1239(144) --199.227.31/24 VILLAB C:US 1:1800 2:1239(144) 3:1239(218) --199.227.32/24 EPAGE C:US 1:1800 2:1239(144) 3:1239(218) --199.227.33/24 NETBLK-CYBERGATE C:US 1:1800 2:1239(144) 3:1239(218) --199.227.34/24 CYBER-BLOCK-C-227-34 C:US 1:1800 2:1239(144) 3:1239(218) --199.227.35/24 CYBER-BLOCK-C-227-35 C:US 1:1800 2:1239(144) 3:1239(218) --199.227.36/24 CYBER-BLOCK-C-227-36 C:US 1:1800 2:1239(144) 3:1239(218) --199.227.37/24 CYBER-BLOCK-C-227-37 C:US 1:1800 2:1239(144) 3:1239(218) --199.227.38/24 CYBER-BLOCK-C-227-38 C:US 1:1800 2:1239(144) 3:1239(218) --199.227.39/24 CYBER-BLOCK-C-227-39 C:US 1:1800 2:1239(144) 3:1239(218) --199.227.40/24 CYBER-BLOCK-C-227-40 C:US 1:1800 2:1239(144) 3:1239(218) --199.227.41/24 CYBER-BLOCK-C-227-41 C:US 1:1800 2:1239(144) 3:1239(218) --199.227.42/24 CYBER-BLOCK-C-227-42 C:US 1:1800 2:1239(144) 3:1239(218) --199.227.43/24 CYBER-BLOCK-C-227-43 C:US 1:1800 2:1239(144) 3:1239(218) --199.227.44/24 CYBER-BLOCK-C-227-44 C:US 1:1800 2:1239(144) 3:1239(218) --199.227.45/24 CYBER-BLOCK-C-227-45 C:US 1:1800 2:1239(144) 3:1239(218) --199.227.46/24 CYBER-BLOCK-C-227-46 C:US 1:1800 2:1239(144) 3:1239(218) --199.227.47/24 CYBER-BLOCK-C-227-47 C:US 1:1800 2:1239(144) 3:1239(218) --199.227.48/24 CYBER-BLOCK-C-227-48 C:US 1:1800 2:1239(144) 3:1239(218) --199.227.49/24 CYBER-BLOCK-C-227-49 C:US 1:1800 2:1239(144) 3:1239(218) --199.227.50/24 CYBER-BLOCK-C-227-50 C:US 1:1800 2:1239(144) 3:1239(218) --199.234.24/23 NETBLK-CDIE C:US 1:3577 2:1324(35) 3:1324(32) --199.234.24/24(U) CDIE-DOM C:US 1:3577 2:1324(32) 3:1324(35) --199.234.25/24(U) CDIE-DOM C:US 1:3577 2:1324(32) 3:1324(35) --199.234.40/22 NETBLK-SWITCH-DOM C:US 1:3577 2:1324(35) 3:1324(32) --199.234.40/24(U) NETBLK-SWITCH-DOM C:US 1:3577 2:1324(32) 3:1324(35) --199.234.41/24(U) NETBLK-SWITCH-DOM C:US 1:3577 2:1324(32) 3:1324(35) --199.234.42/24(U) NETBLK-SWITCH-DOM C:US 1:3577 2:1324(32) 3:1324(35) --199.234.43/24(U) NETBLK-SWITCH-DOM C:US 1:3577 2:1324(32) 3:1324(35) --199.234.48/21 NETBLK-LM2-DOM C:US 1:3577 2:1324(35) 3:1324(32) --199.234.48/24(U) NETBLK-LM2-DOM C:US 1:3577 2:1324(32) 3:1324(35) --199.234.49/24(U) NETBLK-LM2-DOM C:US 1:3577 2:1324(32) 3:1324(35) --199.234.50/24(U) NETBLK-LM2-DOM C:US 1:3577 2:1324(32) 3:1324(35) --199.234.51/24(U) NETBLK-LM2-DOM C:US 1:3577 2:1324(32) 3:1324(35) --199.234.52/24(U) NETBLK-LM2-DOM C:US 1:3577 2:1324(32) 3:1324(35) --199.234.53/24(U) NETBLK-LM2-DOM C:US 1:3577 2:1324(32) 3:1324(35) --199.234.54/24(U) NETBLK-LM2-DOM C:US 1:3577 2:1324(32) 3:1324(35) --199.234.55/24(U) NETBLK-LM2-DOM C:US 1:3577 2:1324(32) 3:1324(35) --199.234.58/23 OPM-CIDR C:US 1:3577 2:1324(35) 3:1324(32) --199.234.58/24(U) OPM C:US 1:3577 2:1324 --199.234.72/23 GASD-CIDR C:US 1:3577 2:1324(35) 3:1324(32) --199.234.72/24(U) GASD C:US 1:3577 2:1324(32) 3:1324(35) --199.234.76/23 PHSD-CIDR C:US 1:3577 2:1324(35) 3:1324(32) --199.234.76/24(U) PHSD C:US 1:3577 2:1324(32) 3:1324(35) --199.234.78/23 MKHS-CIDR C:US 1:3577 2:1324(35) 3:1324(32) --199.234.78/24(U) MKHS C:US 1:3577 2:1324(32) 3:1324(35) --199.234.80/23 WHS-CIDR C:US 1:3577 2:1324(35) 3:1324(32) --199.234.80/24(U) WHS C:US 1:3577 2:1324(32) 3:1324(35) --199.234.82/23 STASD-CIDR C:US 1:3577 2:1324(35) 3:1324(32) --199.234.82/24(U) STASD C:US 1:3577 2:1324(32) 3:1324(35) --199.234.84/23 NAHS-CIDR C:US 1:3577 2:1324(35) 3:1324(32) --199.234.84/24(U) NAHS C:US 1:3577 2:1324(32) 3:1324(35) --199.234.88/21 LVC-DOM C:US 1:3577 2:1324(35) 3:1324(32) --199.234.88/24(U) LCV-DOM C:US 1:3577 2:1324(32) 3:1324(35) --199.234.89/24(U) LVC-DOM C:US 1:3577 2:1324(32) 3:1324(35) --199.234.90/24(U) LVC-DOM C:US 1:3577 2:1324(32) 3:1324(35) --199.234.91/24(U) LVC-DOM C:US 1:3577 2:1324(32) 3:1324(35) --199.234.92/24(U) LVC-DOM C:US 1:3577 2:1324(32) 3:1324(35) --199.234.93/24(U) LVC-DOM C:US 1:3577 2:1324(32) 3:1324(35) --199.234.94/24(U) LVC-DOM C:US 1:3577 2:1324(32) 3:1324(35) --199.234.95/24(U) LVC-DOM C:US 1:3577 2:1324(32) 3:1324(35) --199.234.98/23 BRSD-CIDR C:US 1:3577 2:1324(35) 3:1324(32) --199.234.98/24(U) BRSD C:US 1:3577 2:1324(32) 3:1324(35) --199.234.100/23 WJHS-CIDR C:US 1:3577 2:1324(35) 3:1324(32) --199.234.100/24(U) WJHS C:US 1:3577 2:1324(32) 3:1324(35) --199.234.104/23 WAMS-CIDR C:US 1:3577 2:1324(35) 3:1324(32) --199.234.104/24(U) WAMS C:US 1:3577 2:1324(32) 3:1324(35) --199.234.120/22 DSL-CIDR C:US 1:3577 2:1324(35) 3:1324(32) --199.234.120/24(U) DSL C:US 1:3577 2:1324(32) 3:1324(35) --199.234.121/24(U) DSL C:US 1:3577 2:1324(32) 3:1324(35) --199.234.122/24(U) DSL C:US 1:3577 2:1324(32) 3:1324(35) --199.234.123/24(U) DSL C:US 1:3577 2:1324(32) 3:1324(35) --199.234.148/22 PINNATECH-CIDR C:US 1:3577 2:1324(35) 3:1324(32) --199.234.148/24(U) PINNATECH C:US 1:3577 2:1324(32) 3:1324(35) --199.234.149/24(U) PINNATECH C:US 1:3577 2:1324(32) 3:1324(35) --199.234.150/24(U) PINNATECH C:US 1:3577 2:1324(32) 3:1324(35) --199.234.151/24(U) PINNATECH C:US 1:3577 2:1324(32) 3:1324(35) --199.234.152/22 JWTN-CIDR C:US 1:3577 2:1324(35) 3:1324(32) --199.234.152/24(U) JWTN C:US 1:3577 2:1324(32) 3:1324(35) --199.234.153/24(U) JWTN C:US 1:3577 2:1324(32) 3:1324(35) --199.234.154/24(U) JWTN C:US 1:3577 2:1324(32) 3:1324(35) --199.234.155/24(U) JWTN C:US 1:3577 2:1324(32) 3:1324(35) --199.234.156/22 WAYNESBURG-CIDR C:US 1:3577 2:1324(35) 3:1324(32) --199.234.156/24(U) WAYNESBURG C:US 1:3577 2:1324(32) 3:1324(35) --199.234.157/24(U) WAYNESBURG C:US 1:3577 2:1324(32) 3:1324(35) --199.234.158/24(U) WAYNESBURG C:US 1:3577 2:1324(32) 3:1324(35) --199.234.159/24(U) WAYNESBURG C:US 1:3577 2:1324(32) 3:1324(35) --199.234.160/22 DICKINSON-CIDR C:US 1:3577 2:1324(35) 3:1324(32) --199.234.160/24(U) DICKINSON C:US 1:3577 2:1324(32) 3:1324(35) --199.234.161/24(U) DICKINSON C:US 1:3577 2:1324(32) 3:1324(35) --199.234.162/24(U) DICKINSON C:US 1:3577 2:1324(32) 3:1324(35) --199.234.163/24(U) DICKINSON C:US 1:3577 2:1324(32) 3:1324(35) --199.234.168/21 USS-CIDR C:US 1:3577 2:1324(35) 3:1324(32) --199.234.168/24(U) USS-CIDR C:US 1:3577 2:1324 --199.234.169/24(U) USS-CIDR C:US 1:3577 2:1324 --199.234.170/24(U) USS-CIDR C:US 1:3577 2:1324 --199.234.171/24(U) USS-CIDR C:US 1:3577 2:1324 --199.234.172/24(U) USS-CIDR C:US 1:3577 2:1324 --199.234.173/24(U) USS-CIDR C:US 1:3577 2:1324 --199.234.174/24(U) USS-CIDR C:US 1:3577 2:1324 --199.234.175/24(U) USS-CIDR C:US 1:3577 2:1324 --204.171.1/24(U) WESTMINSTER-CIDR C:US 1:3577 2:1324 --204.171.2/24(U) WESTMINSTER-CIDR C:US 1:3577 2:1324 --204.171.3/24(U) WESTMINSTER-CIDR C:US 1:3577 2:1324 --204.171.4/24(U) WESTMINSTER-CIDR C:US 1:3577 2:1324 --204.171.5/24(U) WESTMINSTER-CIDR C:US 1:3577 2:1324 --204.171.6/24(U) WESTMINSTER-CIDR C:US 1:3577 2:1324 --204.171.7/24(U) WESTMINSTER-CIDR C:US 1:3577 2:1324 --204.171.8/24(U) WESTMINSTER-CIDR C:US 1:3577 2:1324 --204.171.9/24(U) WESTMINSTER-CIDR C:US 1:3577 2:1324 --204.171.10/24(U) WESTMINSTER-CIDR C:US 1:3577 2:1324 --204.171.11/24(U) WESTMINSTER-CIDR C:US 1:3577 2:1324 --204.171.12/24(U) WESTMINSTER-CIDR C:US 1:3577 2:1324 --204.171.13/24(U) WESTMINSTER-CIDR C:US 1:3577 2:1324 --204.171.14/24(U) WESTMINSTER-CIDR C:US 1:3577 2:1324 --204.171.15/24(U) WESTMINSTER-CIDR C:US 1:3577 2:1324 --204.171.20/23 COMPCEN-CIDR C:US 1:3577 2:1324(35) 3:1324(32) --204.171.20/24(U) COMPCEN-CIDR C:US 1:3577 2:1324 --204.171.40/24(U) TELERAMA-CIDR C:US 1:3577 2:1324 --204.171.41/24(U) TELERAMA-CIDR C:US 1:3577 2:1324 --204.171.42/24(U) TELERAMA-CIDR C:US 1:3577 2:1324 --204.171.43/24(U) TELERAMA-CIDR C:US 1:3577 2:1324 --204.171.44/24(U) TELERAMA-CIDR C:US 1:3577 2:1324 --204.171.45/24(U) TELERAMA-CIDR C:US 1:3577 2:1324 --204.171.46/24(U) TELERAMA-CIDR C:US 1:3577 2:1324 --204.171.47/24(U) TELERAMA-CIDR C:US 1:3577 2:1324 --204.171.48/21 PENNET-CIDR C:US 1:3577 --204.171.48/23 TELERAMA-CIDR C:US 1:3577 2:1324(35) 3:1324(32) --204.171.48/24(U) TELERAMA-CIDR C:US 1:3577 2:1324 --204.171.49/24(U) TELERAMA-CIDR C:US 1:3577 2:1324 --204.171.50/24 PENNET-CIDR C:US 1:3577 --204.171.51/24 PENNET-CIDR C:US 1:3577 --204.171.52/24 PENNET-CIDR C:US 1:3577 --204.171.53/24 PENNET-CIDR C:US 1:3577 --204.171.54/24 PENNET-CIDR C:US 1:3577 --204.171.55/24 PENNET-CIDR C:US 1:3577 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. AS690 CIDR Squeezings Report: 12032 Nets, 196 ASs, 3584 Aggregates ------------------------------------------------------------------- 12032 (74%) of the ever-announced more-specific routes within aggregates have been withdrawn. 1178 of those were withdrawn within the last week. 420 the week before that. 16 the week before that. 196 ASs have registered aggregates in the PRDB. 177 of those are announcing aggregates. 91 have withdrawn at least one more specific route. 3584 Aggregates are configured. 2340 of these were Top-Level Aggregates (not nested in another aggregate). 1745 of these are being announced to AS690. 1066 of those have at least one subnet configured (the other 679 may be saving the Internet future subnet announcements). 864 have stopped announcing at least one configured more specific route. 832 have stopped announcing half of their configured more specific routes. 789 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 EDT: 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

Re: Has PSI been assigned network 1?
by Steven J. Richardson 24 Apr '95

24 Apr '95

>From list-admin(a)merit.edu Sun Apr 23 18:33:02 1995 >Received: from merit.edu (merit.edu [35.1.1.42]) by home.merit.edu (8.6.12/merit-2.0) with ESMTP id SAA13236; Sun, 23 Apr 1995 18:32:58 -0400 >Received: from chops.icp.net (root(a)chops.icp.net [199.0.55.71]) by merit.edu (8.6.10/merit-2.0) with ESMTP id SAA29211 for <nanog(a)merit.edu>; Sun, 23 Apr 1995 18:15:06 -0400 >Received: by chops.icp.net id <20655>; Sun, 23 Apr 1995 14:57:23 -0400 >From: Sean Doran <smd(a)icp.net> >To: michael(a)okjunc.junction.net, salo(a)msc.edu >Subject: Re: Has PSI been assigned network 1? >Cc: G.Huston(a)aarnet.edu.au, nanog(a)merit.edu >Message-Id: <95Apr23.145723-0400_pdt.20655+207(a)chops.icp.net> >Date: Sun, 23 Apr 1995 14:57:11 -0400 >Status: RO > >Hi - > > All our junior people are immediately deployed to >projects. One such person was brought into our engineering >group and practically immediately was given responsibility >for making all of NYSERNET work and handling whatever >escalations he could. Another is deployed in dialup and >in assisting with routing matters. Another is busy dealing >with research and resource planning for how we want to scale. > > I can think of innumerable engineering and operations >tasks that need doing before deploying a junior engineering >type to writing documentation. Ah! Since Sprint isn't interested in doing training, I'll stop answering questions from any Sprint staff. (I've wasted a lot of time talking to a succession of persons in position 'x', none of whom ever passed on information to anyone else or documented what their job entailed, I guess.) > So, to extend the point that Geoff made earlier -- any >resource a busy operator has will get deployed into making >that operator's part of the global Internet _work_, not into >helping out other people. Thanks--this explains why the Sprint NOC was so surly and unhelpful when I called. > This is not due to a mean lack of >altruism, but rather to the realities of life in a global >network that doubles in size and traffic severy six-to-nine >months or so. How about an abrogation of responsibility? > Sean. Steve R.

1 0

Re: Has PSI been assigned network 1?
by Dale S. Johnson 24 Apr '95

24 Apr '95

> > 2 - The RADB has a lot of old, now obsolete, data maintained by others. Do > > we have to ask each old maintainer to clean it out, or will it all be > > cleaned up as the changeover settles down? > > If this is true, it will have to be cleaned up. Maybe someone from > ISI or Merit can comment on this. There are some routes in the RADB that have been there since folks experimented with them a year ago. Part of the process of retiring the PRDB will be to copy all the routes from the PRDB into the RADB, watching for conflicts. When newer information from the PRDB contradicts older information from the RADB, the PRDB information will overwrite the RADB. So yes: the old stuff will get cleaned up by a somewhat brute-force process once, the day that the PRDB is retired. (Soon). --Dale

1 0