- Test - lists.nanog.org

SNMP vs 1.1.1.1 (fwd)
by Michael Dillon 18 Apr '95

18 Apr '95

I mentioned some of the thread re: 1.1.1.1 on portmaster-users because there seemed to be an implication that Livingston's Portmaster had a problem in its PPP implementation. Now I get a question that I don't know enough to answer. Perhaps one of you could help this fellow.... ---------- Forwarded message ---------- Date: Mon, 17 Apr 95 21:37:38 CDT From: Kevin Sears x3-5160 <searsk(a)iscmed.med.ge.com> To: portmaster-users(a)msen.com Subject: SNMP vs 1.1.1.1 Greetings, What does SNMP and IP address 1.1.1.1 have in common(seen a few postings on this topic tonight wrt Ascend ISDN routers and Netmanage's Chameleon)? I had a Sniffer on my 3.x.x.x subnet looking for a Portmaster problem when I noticed that I was getting SNMP get next requests from a device in another part of GE directed to my Portmaster on subnet 3.x.x.x with an address of 1.1.1.1. My portmaster's ethernet address was in that packet(i.e. 1.1.1.1) so I'm surprised. What gives? ============================== Kevin Sears Systems & Network Support Tech OnLine Center GE Medical Systems PO Box 414, m/s-W595 Milwaukee, WI 53201 Internet: searsk(a)med.ge.com Voice: 414-524-5160 FAX: 414-524-5305

2 1

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

18 Apr '95

>From list-admin(a)merit.edu Tue Apr 18 03:33:58 1995 >Received: from merit.edu (merit.edu [35.1.1.42]) by home.merit.edu (8.6.12/merit-2.0) with ESMTP id DAA02559; Tue, 18 Apr 1995 03:33:55 -0400 >Received: from VM.TAU.AC.IL (taunivm.tau.ac.il [132.66.32.4]) by merit.edu (8.6.10/merit-2.0) with SMTP id DAA01097 for <nanog(a)MERIT.EDU>; Tue, 18 Apr 1995 03:16:12 -0400 >Message-Id: <199504180716.DAA01097(a)merit.edu> >Received: from VM.TAU.AC.IL by VM.TAU.AC.IL (IBM VM SMTP V2R1) > with BSMTP id 4716; Tue, 18 Apr 95 10:17:42 IST >Received: from VM.TAU.AC.IL (NJE origin HANK@TAUNIVM) by VM.TAU.AC.IL (LMail V1.2a/1.8a) with BSMTP id 4461; Tue, 18 Apr 1995 10:17:42 +0200 >Date: Tue, 18 Apr 95 10:13:35 IST >From: Hank Nussbacher <HANK(a)taunivm.tau.ac.il> >Subject: Re: Has PSI been assigned network 1? >To: Curtis Villamizar <curtis(a)ans.net> >cc: Peter Lothberg <roll(a)stupi.se>, nanog(a)merit.edu >In-Reply-To: Message of Mon, 17 Apr 1995 12:00:24 -0400 from <curtis(a)ans.net> >MIME-Version: 1.0 >Content-Type: Text/plain; charset=US-ASCII >Content-Transfer-Encoding: 7BIT >Status: R > >On Mon, 17 Apr 1995 12:00:24 -0400 you said: >>Curtis >> >>BTW- You might try a traceroute to an address in 140.222/16. That's >>the ANS backbone. For example, traceroute 140.222.32.62 would verify >>that you could reach ANS NY POP. Traceroute 140.222.1.1 would give >>you a !H as soon as you reach an ANS interface (look for t3.ans.net in >>the DNS if the response is not from a 140.222 address). > >Will 140.222.0.0 continue to work? We 'ip default-network 140.222.0.0' >and will have to change if this NSFnet backbone net ceases to exist. AS 690 = NSFNET/ANSnet backbone AS, with backbone net 140.222/16 Just because NSFNET is going away doesn't mean that ANSnet is disappearing; "reports of [its] death are extremely exaggerated"... ;-) Steve Richardson/Merit >I would bet lots of smaller ISPs have this net out there in their >routing tables as gateway of last resort. > >Thanks, >+---------------------------------------------------------------+ >| Hank Nussbacher | >| Inter-University Computer Center IBM | >| Tel-Aviv University Rechov Weizmann 2 >| Ramat Aviv ISRAEL Tel Aviv ISRAEL | >| | >| Work phone: +972-3-6408309 Work phone: +972-3-6978852 | >| Work fax: +972-3-6409118 | >| Home phone: +972-9-920165 | >| Home fax: +972-9-920166 | >| | >| Internet: hank(a)vm.tau.ac.il or hankn(a)vnet.ibm.com | >| | >| Crash dummy of the Israeli Information Highway | >+---------------------------------------------------------------+

1 0

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

18 Apr '95

On Mon, 17 Apr 1995 12:00:24 -0400 you said: >Curtis > >BTW- You might try a traceroute to an address in 140.222/16. That's >the ANS backbone. For example, traceroute 140.222.32.62 would verify >that you could reach ANS NY POP. Traceroute 140.222.1.1 would give >you a !H as soon as you reach an ANS interface (look for t3.ans.net in >the DNS if the response is not from a 140.222 address). Will 140.222.0.0 continue to work? We 'ip default-network 140.222.0.0' and will have to change if this NSFnet backbone net ceases to exist. I would bet lots of smaller ISPs have this net out there in their routing tables as gateway of last resort. Thanks, +---------------------------------------------------------------+ | Hank Nussbacher | | Inter-University Computer Center IBM | | Tel-Aviv University Rechov Weizmann 2 | Ramat Aviv ISRAEL Tel Aviv ISRAEL | | | | Work phone: +972-3-6408309 Work phone: +972-3-6978852 | | Work fax: +972-3-6409118 | | Home phone: +972-9-920165 | | Home fax: +972-9-920166 | | | | Internet: hank(a)vm.tau.ac.il or hankn(a)vnet.ibm.com | | | | Crash dummy of the Israeli Information Highway | +---------------------------------------------------------------+

1 0

Re: Has PSI been assigned network 1?
by Dave Morton 18 Apr '95

18 Apr '95

>>BTW- You might try a traceroute to an address in 140.222/16. That's >>the ANS backbone. For example, traceroute 140.222.32.62 would verify >>that you could reach ANS NY POP. Traceroute 140.222.1.1 would give >>you a !H as soon as you reach an ANS interface (look for t3.ans.net in >>the DNS if the response is not from a 140.222 address). > >Will 140.222.0.0 continue to work? We 'ip default-network 140.222.0.0' >and will have to change if this NSFnet backbone net ceases to exist. >I would bet lots of smaller ISPs have this net out there in their >routing tables as gateway of last resort. > >Thanks, Hank, why don't you just default to EBONE as we do ? Dave

1 0

Re: Final transition steps
by Sean Doran 17 Apr '95

17 Apr '95

Um, are these April 21 disconnections going to be permanent, or is this just a test of limited duration (six or seven hours, say)? If the turn-off is going to last a long time then the NSFNET International Connectivity Project will need MERIT to process and have installed, no later than this Wednesday, a NACR with changes to about 16000 prefixes. We can prepare the NACR this weekend. We will also need to know whether this is a full turn-off of the NSFNET backbone service next Friday as it will affect our immediate plans for turning up an ICM DS3 connection to MAE-EAST+, effectively moving the timing of that forward a few days. (To get the ICM DS3 up and running on time for the 21st (instead of before the 30th) we have some timing issues that are pretty critical, namely provisioning the DS3 and installing all the equipment. It is unclear that this is possible on the MFS side (never mind the paperwork process, which we probably will just have to ignore in the short run). What is clear though is that current connectivity to MAE-EAST is insufficient for making 21 April a happy day -- ICM is transiting SprintLink's (too full) DS3 to MAE-EAST, and using the FIX to reach the fednets and the networks which have not yet transitioned; the current DS3 can't support moving 10Mbps from the FIX, and don't even mention the ethernet that ICM still has today). I am not opposed to the idea, nor to the implementation of this push towards finding alternate connectivity. However, I'm pretty annoyed that we got very short notice of what appears to be an early shutdown of the NSFNET backbone service. This is especially irritating as a shutdown on the 21st will dramatically affect routing worldwide, and force a rewrite of a number of transition schedules which have been in place for quite some time. However, let's run with it. We'll know early in the week when Peter, Vadim and I have spent alot more time on moving ICM transition forward how bad things will be at 9am on the 21st as opposed to the evening of the 26th, and then again late at night on the 30th. Right now, I humbly request that MERIT wearing its RA hat quickly (i.e., this weekend, and certainly no later than Wednesday morning) locates an RS at FIX-EAST so that ICM can more rapidly bring up safe peering with the FIX-EAST connectees than we had initially planned (i.e., we need to have functional peering and transit set up this week instead of using this week to debug things with the fednets who are facing disconnectivity as of the 30th). This RS should be seeded from the ENSS145 configurations rather than any other source. Having something in place at FIX-EAST which does the same filtering that the AS 690 PRDB mechanism did has now been made much more urgent than it was yesterday, so that we can avoid rushing direct peerings, which traditionally has resulted in serious routing botches that the whole world notices. Sean. - -- Sean Doran <smd(a)icm1.icp.net>

3 2

Re: Final transition steps
by Elise Gerich 17 Apr '95

17 Apr '95

Push, The following peering sessions will be unaffected: PacBell NAP ----------- CRL AS 2041 Net99 AS 4388 Route server AS 2882 ANS AS 1321 AS 1688 ANS CIX AS 1957 Sprint NAP ---------- Sprintlink AS 1239 CERFnet AS 1740 Route server AS 2884 Test-RS AS 2886 networkMCI AS 3561 MAE-East -------- Netcomm AS 2551 Route server AS 2885 Interpath AS 3407 networkMCI AS 3561 Net99 AS 3830 B3net AS 4136 Alternet AS 701 Sprintlink AS 1239 CERN/Dante AS 1674 PIPEX AS 1849 Europe RS AS 1879 PSI AS 2149 AADS NAP -------- networkMCI AS 3561 AADS AS 3421 ANS AS 1323 AS 1688 FIX-West -------- NASA AS 297 AS 372 ESnet AS 293 AS 3429 DREN AS 668 DSI AS 2699 Milnet AS 568 network MCI AS 3561 NASA-test AS 1263 Sprintlink AS 1239 Anyone wishing to peer with ANS post-April 30 should contact ANS directly. --Elise >Pushpendra Mohta writes: > > > Sorry- Last nagging question. AS1740 has a AS690 peer at the NY NAP. > Since I dont see the NY NAP ENSS on this list, should I assume > that that peering wont be affected ? > > > > Elise Gerich writes: > > > > >Pushpendra Mohta writes: > > > > > > Elise > > > > > > Will this apply to the peers at the NAPs ? The New York NAP > > > in particular ? > > > > > > --pushpendra > > > > > > Pushpendra Mohta pushp(a)cerf.net +1 619 455 3908 > > > Director, CERFnet http://www.cerf.net +1 800 876 2373 > > > > > > > To better clarify which Autonomous Systems will be effected by the > > April 21, 1995 action, here is a list of the NSFNET Backbone Service > > nodes and the associated Autonomous Systems that are proposed to be > > effected. Due to some information that we have received from one > > or two organizations, this list may be modified. > > > > --Elise > > > > City ENSS# Associated AS# > > -------------------------------------------------------------------------------- > > Ann Arbor, MI 131 237 MICHnet > > 1225 CICnet > > > > Argonne, IL 130 683 Argonne > > 1225 CICnet > > > > Boston, MA 134 560 NEARnet > > 701 Alternet > > > > Boulder, CO 141 58 Los Alamos > > 278 MexNet > > 297 NASA > > 2648 NIST > > > > Champaign, IL 129 38 UIUC > > 555 MSC > > 698 UIRnet > > 1224 NCSA > > 1225 CICnet > > > > College Park, MD > > (FIX-East) 145 293 ESnet > > 297 NASA > > 568 Milnet > > 668 DREN > > 699 DSI > > 1800 ICM > > > > Houston, TX 139 114 Sesquinet > > 297 NASA > > 3354 THEnet > > > > Ithaca, NY 133 174 PSI/NYSERnet > > 133 gated testing > > > > Lincoln, NE 140 93 MIDnet > > > > Palo Alto, CA 128 199 BARRnet > > 200 BARRnet > > > > Pittsburgh, PA 132 204 PSCnet > > 1206 PSCnet > > 3577 Prepnet > > > > Princeton, NJ 137 97 GES/Jvncnet > > 1250 Princeton > > > > Salt Lake City,UT 142 210 Westnet > > > > Seattle, WA 143 685 NorthWestNet > > 73 NorthWestNet > > > > San Diego, CA 135 195 SDSC > > 1740 CERFnet > > 1838 CERFnet > > 2150 CSUnet > > 22 NOSC > > > > NASA Ames, CA 144 200 BARRnet > > > > > > --pushpendra > > Pushpendra Mohta pushp(a)cerf.net +1 619 455 3908 > Director, CERFnet http://www.cerf.net +1 800 876 2373 > >

1 0

Re: Has PSI been assigned network 1?
by Vadim Antonov 17 Apr '95

17 Apr '95

Well, you can always do filtering of routing updates at your ciscos. If i understand correctly Ascends are not directly connected to MAE-East. --vadim there are about a dozen ISP's extensively using ascend's which have this hole. our original RFP to them dealt with this issue but they did not execute they keep trying to fix this, but so far no go we have tried to keep this quiet so that microsoft/uunet/psinet/etc..... don't get extensively hacked we have had two occurences of this so far in one year that I know of though there are probably more marty

1 0

Re: Has PSI been assigned network 1?
by Vadim Antonov 17 Apr '95

17 Apr '95

PSI allows people to negotiate PPP addresses, and then propagates everything everywhere w/o even token filtering. I.e. any idiot can subscribe to PSI service and kill the Internet. --vadim Date: Sun, 16 Apr 95 21:02:04 MET DST From: Peter Lothberg <roll(a)Stupi.SE> To: schoff(a)psi.com, nanog(a)merit.edu, postel(a)isi.edu Subject: Has PSI been assigned network 1? Or why are they announcing it to the rest of the Internet through their box at MAE-East??? bash$ whois 1.0.0.0 No match for "1.0.0.0". The InterNIC Registration Services Host contains ONLY Internet Information (Networks, ASN's, Domains, and POC's). Please use the whois server at nic.ddn.mil for MILNET Information. traceroute 1.1.1.1 traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 40 byte packets 1 sl-dialup-2.sprintlink.net (192.157.36.128) 252 ms 245 ms 223 ms 2 192.157.36.1 (192.157.36.1) 251 ms 250 ms 251 ms 3 sl-dc-1-S3-T1.sprintlink.net (144.228.0.225) 252 ms 262 ms 253 ms 4 icm-dc-1-F0/0.icp.net (144.228.20.101) 275 ms 269 ms 252 ms 5 psi-mae-east-1.psi.net (192.41.177.235) 268 ms 254 ms 241 ms 6 washington2.dc.isdn.psi.net (38.146.99.110) 261 ms 271 ms 262 ms 7 1.1.1.1 (1.1.1.1) 457 ms 1284 ms 543 ms bash$ traceroute 1.1.1.2 traceroute to 1.1.1.2 (1.1.1.2), 30 hops max, 40 byte packets 1 sl-dialup-2.sprintlink.net (192.157.36.128) 253 ms 253 ms 246 ms 2 192.157.36.1 (192.157.36.1) 246 ms 243 ms 228 ms 3 sl-dc-1-S3-T1.sprintlink.net (144.228.0.225) 249 ms 447 ms 313 ms 4 icm-dc-1-F0/0.icp.net (144.228.20.101) 274 ms 251 ms 278 ms 5 psi-mae-east-1.psi.net (192.41.177.235) 265 ms 257 ms 266 ms 6 core.net228.psi.net (38.1.2.7) 286 ms 278 ms 276 ms 7 core.net99.psi.net (38.1.2.10) 338 ms 370 ms 279 ms 8 core.net228.psi.net (38.1.2.7) 306 ms 326 ms 290 ms 9 core.net99.psi.net (38.1.2.10) 335 ms 308 ms 325 ms 10 core.net228.psi.net (38.1.2.7) 372 ms 353 ms 341 ms 11 core.net99.psi.net (38.1.2.10) 376 ms 385 ms 377 ms 12 core.net228.psi.net (38.1.2.7) 438 ms 375 ms 365 ms 13 core.net99.psi.net (38.1.2.10) 384 ms 441 ms 371 ms 14 core.net228.psi.net (38.1.2.7) 394 ms 426 ms 474 ms 15 core.net99.psi.net (38.1.2.10) 427 ms 540 ms 565 ms 16 core.net228.psi.net (38.1.2.7) 521 ms 500 ms 489 ms 17 core.net99.psi.net (38.1.2.10) 530 ms 483 ms 527 ms 18 core.net228.psi.net (38.1.2.7) 567 ms 493 ms 561 ms 19 core.net99.psi.net (38.1.2.10) 779 ms 462 ms 670 ms 20 core.net228.psi.net (38.1.2.7) 531 ms 620 ms 613 ms 21 core.net99.psi.net (38.1.2.10) 562 ms 728 ms 598 ms 22 core.net228.psi.net (38.1.2.7) 812 ms 566 ms 835 ms 23 core.net99.psi.net (38.1.2.10) 661 ms 678 ms 574 ms 24 core.net228.psi.net (38.1.2.7) 647 ms 820 ms 666 ms 25 core.net99.psi.net (38.1.2.10) 649 ms 625 ms 628 ms 26 core.net228.psi.net (38.1.2.7) 900 ms 634 ms 733 ms 27 core.net99.psi.net (38.1.2.10) 648 ms 659 ms 656 ms 28 core.net228.psi.net (38.1.2.7) 776 ms 979 ms 834 ms 29 core.net99.psi.net (38.1.2.10) 715 ms 689 ms 734 ms 30 core.net228.psi.net (38.1.2.7) 782 ms 785 ms 677 ms ---Peter

2 1

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

17 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 50794 = 29 5393 41893 3479 Configured Networks 47890 = 29 5337 39109 3415 Added Networks 130 = 0 5 77 48 Deleted Networks 50 = 1 2 42 5 IP address Net name Country Priority:AS ---------- -------- ------- ----------- 135.182/16 EASYLINK C:US 1:701(147) 2:701(134) 140.250.41/24 MILES C:US 1:3561(218) 2:3561(147) 3:3561(27) 4:3561(11) 5:3561(144) 6:560 165.2/16 HIW-INN-NET C:US 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) 165.37/16 BOFA7 C:US 1:1740(218) 2:1740(135) 168.105/16 HAWAIIMED C:US 1:3381 170.8/16 ARTRAC-B C:US 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) 192.54.99/24 UMD-UNCON C:US 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) 192.54.108/24 SYZYGY C:US 1:1334 2:1800 3:1240 4:209 5:210 192.80.74/24 NET-AWARE74 C:US 1:3561(218) 2:3561(147) 3:3561(27) 4:3561(11) 5:3561(144) 6:560 7:701(147) 192.80.75/24 NET-AWARE75 C:US 1:3561(218) 2:3561(147) 3:3561(27) 4:3561(11) 5:3561(144) 6:560 7:701(147) 192.122.131/24 NCB C:SG 1:3561(218) 2:3561(147) 3:3561(27) 4:3561(11) 5:3561(144) 6:97 192.206.129/24 KENETECH C:US 1:2551(147) 2:1321 192.206.130/24 KENETECH2 C:US 1:2551(147) 2:1321 193.229.0/21 NET-KOLUMBUS C:FI 1:1239(147) 2:1239(218) 3:1239(144) 4:1800 193.229.8/24 NET-KOLUMBUS C:FI 1:1239(147) 2:1239(218) 3:1239(144) 4:1800 194.58.93/24 SW-LAN C:RU 1:701 2:1800 3:1240 196.3.96/21 EMUNET C:MZ 1:1239(147) 2:1239(218) 3:1239(144) 4:1800 196.24.128/21 EMUNET C:MZ 1:1239(147) 2:1239(218) 3:1239(144) 4:1800 198.61.16/20 YORK-CUNY C:US 1:1662 2:174 3:1239(218) 4:1239(147) 5:1239(144) 6:1800 198.83.28/22 JOHN-JAY C:US 1:1662 2:1239(218) 3:1239(147) 4:1239(144) 5:1800 198.83.112/21 KINGSBOROUGH C:US 1:1662 2:1239(218) 3:1239(147) 4:1239(144) 5:1800 198.83.120/22 QUEENSBOROUGH C:US 1:1662 2:1239(218) 3:1239(147) 4:1239(144) 5:1800 198.83.124/22 MCC C:US 1:1662 2:1239(218) 3:1239(147) 4:1239(144) 5:1800 198.83.132/24 TELEADVISE-NET C:US 1:1325 198.83.171/24 WINCOM-DMZ8 C:CA 1:1326 198.83.172/24 WINCOM-DMZ9 C:CA 1:1326 198.83.173/24 WINCOM-DMZ10 C:CA 1:1326 198.83.174/24 WINCOM-DMX11 C:CA 1:1326 198.112.58/24 CWPUBLISHING-58 C:US 1:3561(218) 2:3561(11) 3:560 4:701(147) 5:701(134) 198.136.128/24 NET-DSMC C:US 1:1239(147) 2:1239(218) 3:1239(144) 4:1800 198.140.161/24 NET-PARTYLINE C:US 1:1239(218) 2:1239(147) 3:1239(144) 4:1800 198.178.137/24 NET-LOGICRAFT C:US 1:2551(147) 2:1321 198.180.213/24 BAKERNET C:US 1:1800 2:1239(144) 3:1239(218) 198.203.164/24 BFI-INC C:US 1:3561(27) 2:3561(147) 3:3561(11) 4:3561(218) 5:3561(144) 198.244.0/21 RIDLEYSD C:US 1:701(147) 2:701(134) 198.244.8/23 RIDLEYSD C:US 1:701(147) 2:701(134) 199.20.16/20 ASC-NETBLK C:US 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) 199.30.16/22 NETBLK-MICOM C:US 1:2551(147) 2:1321 199.30.20/23 NETBLK-MICOM C:US 1:2551(147) 2:1321 199.30.22/24 NETBLK-MICOM C:US 1:2551(147) 2:1321 199.75.228/23 JBHS-WI-K12-MD-US C:US 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) 199.120.187/24 QUICK-C C:US 1:701(147) 2:701(134) 199.171.28/23 NETBLK-WIZARD C:US 1:3830 2:701 199.176.152/24 AADS-CHAMPAIGN C:US 1:3561(218) 2:3561(11) 3:1225(129) 4:1225(131) 5:1225(130) 199.219.128/19 NYSER-NETBLK C:US 1:1662 2:1239(218) 3:1239(147) 4:1239(144) 5:1800 199.219.160/20 NYSER-NETBLK C:US 1:1662 2:1239(218) 3:1239(147) 4:1239(144) 5:1800 199.219.176/22 NYSER-NETBLK C:US 1:1662 2:1239(218) 3:1239(147) 4:1239(144) 5:1800 199.249.140/23 NEXGEN C:US 1:2551(147) 2:1321 200.0.165/24 AQP C:PE 1:1800 2:1239(218) 3:1239(144) 200.2.72/21 IANSA-CL C:CL 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) 200.2.80/22 IANSA-CL C:CL 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) 200.2.82/23 IANSA-CL C:CL 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) 200.14.64/24 UCINF C:CL 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) 202.33.61/24 MMC-NET C:JP 1:2149 2:174 202.82.0/22 STARPAGING C:HK 1:701(147) 2:701(134) 202.244.32/24 INFOCITY-CUC-C-244-32 C:JP 1:3561(218) 2:3561(147) 3:3561(27) 4:3561(11) 5:3561(144) 6:97 202.244.33/24 INFOCITY-CUC-C-244-33 C:JP 1:3561(218) 2:3561(147) 3:3561(27) 4:3561(11) 5:3561(144) 6:97 202.244.34/24 INFOCITY-CUC-C-244-34 C:JP 1:3561(218) 2:3561(147) 3:3561(27) 4:3561(11) 5:3561(144) 6:97 202.244.35/24 INFOCITY-CUC-C-244-35 C:JP 1:3561(218) 2:3561(147) 3:3561(27) 4:3561(11) 5:3561(144) 6:97 202.244.36/24 INFOCITY-CUC-C-244-36 C:JP 1:3561(218) 2:3561(147) 3:3561(27) 4:3561(11) 5:3561(144) 6:97 202.244.37/24 INFOCITY-CUC-C-244-37 C:JP 1:3561(218) 2:3561(147) 3:3561(27) 4:3561(11) 5:3561(144) 6:97 202.244.38/24 INFOCITY-CUC-C-244-38 C:JP 1:3561(218) 2:3561(147) 3:3561(27) 4:3561(11) 5:3561(144) 6:97 202.244.39/24 INFOCITY-CUC-C-244-39 C:JP 1:3561(218) 2:3561(147) 3:3561(27) 4:3561(11) 5:3561(144) 6:97 203.65/16 NET-HINET C:TW 1:1239(147) 2:1239(218) 3:1239(144) 4:1800 5:1321 203.66/16 NET-HINET C:TW 1:1239(147) 2:1239(218) 3:1239(144) 4:1800 5:1321 203.67/16 NET-HINET C:TW 1:1239(147) 2:1239(218) 3:1239(144) 4:1800 5:1321 203.161.0/22 CESTINTS-VN C:VN 1:1321 204.6.91/24 PSINET-C4 C:US 1:2149 2:174 204.61.208/21 KENETECH-1 C:US 1:2551(147) 2:1321 204.61.216/23 KENETECH-1 C:US 1:2551(147) 2:1321 204.62.160/24 XINGNET C:US 1:3561(11) 2:3561(144) 3:3561(27) 4:3561(147) 5:3561(218) 204.75.174/24 CLARMONT C:US 1:1800 2:1239(144) 3:1239(218) 204.86.129/24 LESCORP-1 C:US 1:2386 2:1321 204.101.81/24 TRANSCOM2 C:CA 1:1239(218) 2:1239(147) 3:1239(144) 4:1800 204.101.83/24 TRANSDATA C:CA 1:1239(218) 2:1239(147) 3:1239(144) 4:1800 204.101.84/24 TELOS-NET84 C:CA 1:1239(218) 2:1239(147) 3:1239(144) 4:1800 204.101.85/24 IVIC-NET85 C:CA 1:1239(218) 2:1239(147) 3:1239(144) 4:1800 204.101.86/24 SOUTHAMTECH C:CA 1:1239(218) 2:1239(147) 3:1239(144) 4:1800 204.101.87/24 HCL C:CA 1:1239(218) 2:1239(147) 3:1239(144) 4:1800 204.101.88/24 CANADALIFE C:CA 1:1239(218) 2:1239(147) 3:1239(144) 4:1800 204.124.12/24 SLCCORP-1 C:US 1:1239(144) 2:1800 3:1239(218) 4:210 5:209 204.124.13/24 SLCCORP-1 C:US 1:1239(144) 2:1800 3:1239(218) 4:210 5:209 204.124.14/24 SLCCORP-1 C:US 1:1239(144) 2:1800 3:1239(218) 4:210 5:209 204.128.222/24 MOBILE-CHMBR C:US 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) 204.153.216/24 HBOC-WAN C:US 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) 204.166.64/24 HARVARD-64 C:US 1:3561(218) 2:3561(11) 3:560 4:701(147) 5:701(134) 204.166.65/24 HARVARD-65 C:US 1:3561(218) 2:3561(11) 3:560 4:701(147) 5:701(134) 204.166.66/24 HARVARD-66 C:US 1:3561(218) 2:3561(11) 3:560 4:701(147) 5:701(134) 204.166.67/24 HARVARD-67 C:US 1:3561(218) 2:3561(11) 3:560 4:701(147) 5:701(134) 204.166.68/24 HARVARD-68 C:US 1:3561(218) 2:3561(11) 3:560 4:701(147) 5:701(134) 204.166.69/24 HARVARD-69 C:US 1:3561(218) 2:3561(11) 3:560 4:701(147) 5:701(134) 204.166.70/24 HARVARD-70 C:US 1:3561(218) 2:3561(11) 3:560 4:701(147) 5:701(134) 204.166.71/24 HARVARD-71 C:US 1:3561(218) 2:3561(11) 3:560 4:701(147) 5:701(134) 204.166.88/24 HARVARD-88 C:US 1:3561(218) 2:3561(11) 3:560 4:701(147) 5:701(134) 204.166.89/24 HARVARD-89 C:US 1:3561(218) 2:3561(11) 3:560 4:701(147) 5:701(134) 204.166.90/24 HARVARD-90 C:US 1:3561(218) 2:3561(11) 3:560 4:701(147) 5:701(134) 204.166.91/24 HARVARD-91 C:US 1:3561(218) 2:3561(11) 3:560 4:701(147) 5:701(134) 204.166.92/24 HARVARD-92 C:US 1:3561(218) 2:3561(11) 3:560 4:701(147) 5:701(134) 204.166.93/24 HARVARD-93 C:US 1:3561(218) 2:3561(11) 3:560 4:701(147) 5:701(134) 204.166.94/24 HARVARD-94 C:US 1:3561(218) 2:3561(11) 3:560 4:701(147) 5:701(134) 204.166.95/24 HARVARD-95 C:US 1:3561(218) 2:3561(11) 3:560 4:701(147) 5:701(134) 204.181.91/24 NET-GSDM C:US 1:1239(147) 2:1239(144) 3:1239(218) 4:1800 204.194.8/21 SEMAPHORE-BLK C:US 1:4388 2:3830 3:1240 4:1800 5:1239 204.199.2/23 USVI-NET C:VI 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) 204.212.232/21 SIERRA-NET C:US 1:1239(144) 2:1239(147) 3:1239(218) 4:1800 204.214.129/24 NET-AYERS C:US 1:1239(147) 2:1239(144) 3:1239(218) 4:1800 204.214.130/24 NET-BDMG C:US 1:1239(147) 2:1239(144) 3:1239(218) 4:1800 204.246.0/20 TDS-TELECOM-DIAL-BLOC C:US 1:3561(27) 2:3561(218) 3:3561(147) 4:3561(11) 5:3561(144) 204.248.172/22 WWA-NET C:US 1:1239(218) 2:1239(147) 3:1239(144) 4:1800 204.248.182/23 NET-PARTYLINE C:US 1:1239(218) 2:1239(147) 3:1239(144) 4:1800 204.249.96/21 NET-ULTRANET C:US 1:1239(218) 2:1239(147) 3:1239(144) 4:1800 204.249.166/23 NET-SMCSYS C:US 1:1239(218) 2:1239(147) 3:1239(144) 4:1800 204.251.236/23 NET-GVI C:US 1:1239(147) 2:1239(144) 3:1239(218) 4:1800 205.129.0/21 OSCEOLA2-K12-FL-US C:US 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) 205.129.8/23 OSCEOLA2-K12-FL-US C:US 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) 205.159.83/24 LORNET C:US 1:1240 2:1800 3:1239 4:209 5:210 205.160.224/24 NET-CYBERIA C:US 1:1239(147) 2:1239(218) 3:1239(144) 4:1800 205.160.228/24 NET-SANCTUM C:US 1:1239(147) 2:1239(218) 3:1239(144) 4:1800 205.162.112/24 SPRINT-BLKE C:CA 1:1239(144) 2:1239(147) 3:1239(218) 4:1800 205.162.113/24 SPRINT-BLKE C:CA 1:1239(144) 2:1239(147) 3:1239(218) 4:1800 205.162.114/23 SPRINT-BLKE C:CA 1:1239(144) 2:1239(147) 3:1239(218) 4:1800 205.166.1/24 DE-LASCRUCES C:US 1:1334 2:1800 3:1240 4:209 5:210 205.166.76/24 NINTENDO-COM C:US 1:1321 2:2386 205.174.48/20 JSUNET3 C:US 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) 205.182.8/24 IMPERIALPRINT-NET8 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) 205.216.0/19 MCI-POP-AGG C:US 1:3561(27) 2:3561(218) 3:3561(147) 4:3561(11) 5:3561(144) 205.216.64/19 MCI-POP-AGG C:US 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) 205.216.96/19 MCI-POP-AGG C:US 1:3561(218) 2:3561(147) 3:3561(27) 4:3561(11) 5:3561(144) 205.216.128/19 MCI-POP-AGG C:US 1:3561(11) 2:3561(144) 3:3561(147) 4:3561(27) 5:3561(218) 205.216.160/19 MCI-POP-AGG C:US 1:3561(11) 2:3561(144) 3:3561(147) 4:3561(27) 5:3561(218) Deletions: --28/8 WIDEBAND C:US 1:2699(145) 2:2699(144) --134.203/16 TNO-HDO-LTD C:NL 1:2699(145) 2:2699(144) --137.8/13 DISN C:US 1:568(145) 2:568(144) --164.203/16 STDN4 C:US 1:2699(145) 2:2699(144) --165.37.203/24 BOFA7 C:US 1:1740(218) 2:1740(135) --192.12.203/24 NET-SRI-PSON-13 C:US 1:2699(145) 2:2699(144) --192.35.75/24 FOTLANMS C:US 1:2699(144) 2:2699(145) --192.35.94/24 RSRE-BOMLAN C:GB 1:2699(145) 2:2699(144) --192.44.222/24 VV-NET7 C:US 1:2699(145) 2:2699(144) --192.44.223/24 VV-NET8 C:US 1:2699(145) 2:2699(144) --192.44.233/24 VV-NET18 C:US 1:2699(145) 2:2699(144) --192.44.234/24 VV-NET19 C:US 1:2699(145) 2:2699(144) --192.44.235/24 VV-NET20 C:US 1:2699(145) 2:2699(144) --192.44.236/24 VV-NET21 C:US 1:2699(145) 2:2699(144) --192.44.237/24 VV-NET22 C:US 1:2699(145) 2:2699(144) --192.67.43/24 RSRE-OPEN-NET C:GB 1:2699(145) 2:2699(144) --192.70.248/24 WPC-STC-TRUNK C:NL 1:2699(145) 2:2699(144) --192.91.8/24 DWSNETBLOCK8 C:US 1:2699(145) 2:2699(144) --192.91.9/24 DWSNETBLOCK9 C:US 1:2699(145) 2:2699(144) --192.91.14/24 DWSNETBLOCK14 C:US 1:2699(145) 2:2699(144) --192.91.31/24 DWSNETBLOCK31 C:US 1:2699(145) 2:2699(144) --192.91.47/24 DWSNETBLOCK47 C:US 1:2699(145) 2:2699(144) --192.105.200/24 HP22 C:US 1:2699(145) 2:2699(144) --192.147.46/24 NET-MCS C:US 1:1239(218) 2:1800 3:1239(144) --192.245.15/24 NET-NTC C:US 1:2699(145) 2:2699(144) --192.253.39/24 DSI-NET39 C:US 1:2699(145) 2:2699(144) --192.253.160/24 DSI-NET160 C:US 1:2699(145) 2:2699(144) --192.253.161/24 DSI-NET161 C:US 1:2699(145) 2:2699(144) --192.253.163/24 DSI-NET163 C:US 1:2699(145) 2:2699(144) --198.98.133/24 STDN4-NET6 C:US 1:2699(145) 2:2699(144) --198.98.177/24 STDN4-NET50 C:US 1:2699(145) 2:2699(144) --198.201.156/24 TASDAC-29 C:US 1:2699(145) 2:2699(144) --199.10.48/20 DISN C:US 1:568(144) 2:568(145) --199.20.16/24 ASC-NET-C-20-16 C:US 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) --199.20.17/24 ASC-NET-C-20-17 C:US 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) --199.20.18/24 ASC-NET-C-20-18 C:US 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) --199.20.19/24 ASC-NET-C-20-19 C:US 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) --199.20.20/24 ASC-NET-C-20-20 C:US 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) --199.20.21/24 ASC-NET-C-20-21 C:US 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) --199.20.22/24 ASC-NET-C-20-22 C:US 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) --199.20.23/24 ASC-NET-C-20-23 C:US 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) --199.20.24/24 ASC-NET-C-20-24 C:US 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) --199.20.25/24 ASC-NET-C-20-25 C:US 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) --199.20.26/24 BJHS C:US 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) --199.20.27/24 ASC-NET-C-20-27 C:US 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) --199.20.28/23 NETBLK-AAMU C:US 1:3561(218) 2:3561(11) --199.20.30/24 ASC-NET-C-20-30 C:US 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) --199.20.31/24 ASC-NET-C-20-31 C:US 1:3561(147) 2:3561(218) 3:3561(27) 4:3561(11) 5:3561(144) --199.208/14 DISN C:US 1:568(144) 2:568(145) --199.249.141/24 NEXGEN C:US 1:2551(147) 2:1321 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 2883 - NAP-TWO - DNSS 27 Peer: 198.32.130.130 - Merit - rs1.aads.ra.net AS 2885 - NAP-FOUR - ENSS 147 Peer: 192.41.177.169 - Merit - rs2.mae-east.ra.net AS690 CIDR Squeezings Report: 11490 Nets, 189 ASs, 3455 Aggregates ------------------------------------------------------------------- 11490 (82%) of the ever-announced more-specific routes within aggregates have been withdrawn. 635 of those were withdrawn within the last week. 17 the week before that. 493 the week before that. 189 ASs have registered aggregates in the PRDB. 170 of those are announcing aggregates. 89 have withdrawn at least one more specific route. 3455 Aggregates are configured. 2254 of these were Top-Level Aggregates (not nested in another aggregate). 1769 of these are being announced to AS690. 1083 of those have at least one subnet configured (the other 686 may be saving the Internet future subnet announcements). 917 have stopped announcing at least one configured more specific route. 893 have stopped announcing half of their configured more specific routes. 843 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 Sean Doran 17 Apr '95

17 Apr '95

With respect, Marty, I think that experience should clearly indicate that keeping things quietis precisely the wrong thing to do. Sean.

1 0