- Test - lists.nanog.org

DRAFT NOTES ARE DONE!
by sob＠academ.com 26 Feb '95

26 Feb '95

I don't have all the slides plugged in yet, but all my notes are now on-line. Please review and comment! http://www.academ.com/nanog -- Stan | Academ Consulting Services |internet: sob(a)academ.com Olan | For more info on academ, see this |uucp: bcm!academ!sob Barber | URL- http://www.academ.com/academ |Opinions expressed are only mine.

2 1

Transition question (ENSS status)
by Eric.M.Aupperle＠um.cc.umich.edu 26 Feb '95

26 Feb '95

Sean, Several regionals have given their notice to NSF and Merit. To date it's only been possible for Merit to give ANS notice to terminate one ENSS. That was for ENSS 138 in Atlanta. Merit will soon, before the end of February, give notice to ANS to terminate all other ENSSs to meet the end of April deadline. Merit's termination notice will include ENSSs at the FIXs. Eric ------- Forwarded message Received: from home.merit.edu by um.cc.umich.edu via MTS-Net; Fri, 24 Feb 95 00:00:37 EST Received: from merit.edu (merit.edu [35.1.1.42]) by home.merit.edu (8.6.10/merit-2.0) with ESMTP id XAA08205; Thu, 23 Feb 1995 23:57:41 -0500 Received: from tiny.sprintlink.net (tiny.sprintlink.net [199.0.55.90]) by merit.edu (8.6.10/merit-2.0) with ESMTP id XAA23675 for <nanog(a)merit.edu>; Thu, 23 Feb 1995 23:48:21 -0500 Received: from tiny.sprintlink.net (localhost.sprintlink.net [127.0.0.1]) by tiny.sprintlink.net (8.6.9/8.6.9) with ESMTP id XAA25109 for <nanog(a)merit.edu>; Thu, 23 Feb 1995 23:48:20 -0500 Message-Id: <199502240448.XAA25109(a)tiny.sprintlink.net> From: Sean Doran <smd(a)sprint.net> Reply-To: smd(a)sprint.net To: nanog(a)merit.edu Subject: Transition question (ENSS status) Date: Thu, 23 Feb 1995 23:48:20 -0500 Sender: smd(a)sprint.net Out of curiosity, has any regional sent MERIT or has MERIT sent ANS a 60-day notice of termination yet? What happens if ANS doesn't get the 60-day termination notices 60 days in advance of the end of the cooperative agreement? Also, for the fednet crowd, once the cooperative agreement expires and ANS is no longer a federal network, and also has no IRC obligations, will they still be permitted to remain at the FIXes, or will that be considered less important given the plans to link the FIXes and the MAEs in various ways? WRT the FIXes, mostly I'm wondering about the fate of ENSS145, and pondering the fate of ICM AS 1800's external connectivity. Sean. (Just curious, and figuring someone here might know)

2 1

Re: Transition question (ENSS status)
by sob＠academ.com 24 Feb '95

24 Feb '95

1 0

Transition question (ENSS status)
by Sean Doran 24 Feb '95

24 Feb '95

Out of curiosity, has any regional sent MERIT or has MERIT sent ANS a 60-day notice of termination yet? What happens if ANS doesn't get the 60-day termination notices 60 days in advance of the end of the cooperative agreement? Also, for the fednet crowd, once the cooperative agreement expires and ANS is no longer a federal network, and also has no IRC obligations, will they still be permitted to remain at the FIXes, or will that be considered less important given the plans to link the FIXes and the MAEs in various ways? WRT the FIXes, mostly I'm wondering about the fate of ENSS145, and pondering the fate of ICM AS 1800's external connectivity. Sean. (Just curious, and figuring someone here might know)

1 0

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

23 Feb '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 47904 = 30 5295 39685 2894 Configured Networks 44956 = 30 5238 36858 2830 Added Networks 188 = 0 8 134 46 Deleted Networks 80 = 0 1 74 5 IP address Net name Country Priority:AS ---------- -------- ------- ----------- 138.104/16 MOTTMAC C:GB 1:701(136) 2:701(134) 3:1800 142.79/16 LAURALCO C:CA 1:1239 2:1800 3:1240 150.245/16 KODAKA1 C:US 1:1239 2:1800 3:1240 150.246/15 KODAKA2 C:US 1:1239 2:1800 3:1240 150.248/15 KODAKA4 C:US 1:1239 2:1800 3:1240 159.48/16 UIC C:US 1:701(136) 2:701(134) 160.2/15 KODAK C:US 1:2149 2:174 3:1239 4:1800 5:1240 164.102/16 ACB C:CA 1:1331 165.130/16 HOMEDEPOT C:US 1:1800 2:1239 3:1240 166.20/16 MMC-NET5 C:US 1:2149 2:174 167.223/16 KPCOLORADO-B C:US 1:1800 2:1240 3:1239 4:209 5:210 192.52.58/24 INTEL-FOLSOM C:US 1:701(136) 2:701(134) 192.55.32/22 NETBLK-CIS C:US 1:701(136) 2:701(134) 192.55.36/23 NETBLK-CIS C:US 1:701(136) 2:701(134) 192.55.38/24 NETBLK-CIS C:US 1:701(136) 2:701(134) 192.55.59/24 NETBLK-CIS C:US 1:701(136) 2:701(134) 192.64.44/23 DIBA C:ES 1:1800 2:1133 3:1674 4:1240 192.100.170/24 REDUTM C:MX 1:114 2:278 3:1328 4:3561(11) 5:3561(218) 192.102.187/24 LOCALNET6 C:US 1:701(136) 2:701(134) 192.133.244/24 READING-CS C:GB 1:1800 2:1133 3:1240 4:3561(218) 5:3561(11) 192.136.140/24 NET-VORTEX C:US 1:3561(218) 2:3561(11) 192.198.128/24 NETBLK-CIS C:US 1:701(136) 2:701(134) 192.198.148/23 NETBLK-CIS C:US 1:701(136) 2:701(134) 192.211.20/24 EVERGREEN1 C:US 1:3561(11) 2:3561(218) 3:685 4:73 5:101 192.219.130/24 NET-WELDWOOD11 C:CA 1:1240 2:1800 3:1239 192.219.135/24 NET-WELDWOOD16 C:CA 1:1240 2:1800 3:1239 192.219.136/24 NET-WELDWOOD17 C:CA 1:1240 2:1800 3:1239 192.219.138/24 NET-WELDWOOD19 C:CA 1:1240 2:1800 3:1239 192.231.197/24 NET-HUNTINGTON1 C:US 1:1800 2:1240 3:1239 192.232.64/18 NETBLK-KODAK-CSPACE C:US 1:2149 2:174 3:1239 4:1800 5:1240 192.251.169/24 CAM-CSCINDEX C:US 1:2551(136) 2:1321 192.251.170/23 SFO-CSCINDEX C:US 1:2551(136) 2:1321 192.251.172/23 SFPCGO-CSCINDEX C:US 1:2551(136) 2:1321 193.35.209/24 VN-UK C:GB 1:701(136) 2:701(134) 3:1800 193.122.132/24 NOVUK C:GB 1:701(136) 2:701(134) 3:1800 193.124.73/24 WILDWIND C:UA 1:701(136) 2:701(134) 3:1800 193.131.248/24 EASYNET C:GB 1:3561(218) 2:3561(11) 3:1800 4:1240 6:701(136) 7:1133 8:1674 193.166/15 FUNET-BLOCK C:FI 1:1800 2:1879 3:1133 4:1240 193.224.163/24 GALLUP C:HU 1:1800 2:1133 3:1240 193.248.174/24 FR-FTGCN C:FR 1:1800 2:1240 3:1133 4:1674 194.25.0/21 DTAG-BB1 C:DE 1:1800 2:1240 194.58.199/24 MATMEX C:RU 1:701(136) 2:701(134) 3:1800 194.115.17/24 PEU-TRANS-BI C:DE 1:701(136) 2:701(134) 3:1800 198.62.128/22 KPCOLORADO-1 C:US 1:1800 2:1240 3:1239 4:209 5:210 198.66.88/24 SESQUI-CIDR-C-66-88 C:US 1:3561(218) 2:3561(11) 3:114 198.66.98/24 SESQUI-CIDR-C-66-98 C:US 1:3561(218) 2:3561(11) 3:114 198.68.128/20 NETBLK-DNAI C:US 1:3561(11) 2:3561(218) 3:1240 4:1239 5:1800 198.68.164/22 NETBLK-ZOCALO C:US 1:3561(11) 2:3561(218) 3:1240 4:1239 5:1800 198.68.224/20 NETBLK-QUAKENET C:US 1:3561(11) 2:3561(218) 3:1240 4:1239 5:1800 198.83.27/24 FMC-NET C:US 1:1328 198.83.82/24 ANS-C-BLOCK C:US 1:1334 198.83.83/24 ANS-C-BLOCK C:US 1:1334 198.83.84/24 ANS-C-BLOCK C:US 1:1334 198.96.210/24 PORTAGE-CA C:CA 1:1240 2:1800 3:1239 198.99.4/22 KPCOLORADO-5 C:US 1:1800 2:1240 3:1239 4:209 5:210 198.138.93/24 NET-KOLACOM C:US 1:1800 2:1240 3:1239 198.140.8/21 KPCOLORADO-9 C:US 1:1800 2:1240 3:1239 4:209 5:210 198.167.161/24 NET-NET-PEI1 C:CA 1:701(136) 2:701(134) 198.176.186/23 NETBLK-CLACKAMAS C:US 1:3561(11) 2:3561(218) 3:685 4:73 5:101 198.200.32/24 NET-SWSPECTRUM1 C:US 1:1240 2:1800 3:1239 198.200.33/24 NET-SWSPECTRUM2 C:US 1:1240 2:1800 3:1239 198.200.34/24 NET-SWSPECTRUM3 C:US 1:1240 2:1800 3:1239 198.200.35/24 NET-SWSPECTRUM4 C:US 1:1240 2:1800 3:1239 198.200.36/24 NET-SWSPECTRUM5 C:US 1:1240 2:1800 3:1239 198.200.37/24 NET-SWSPECTRUM6 C:US 1:1240 2:1800 3:1239 198.200.38/24 NET-SWSPECTRUM7 C:US 1:1240 2:1800 3:1239 198.200.39/24 NET-SWSPECTRUM8 C:US 1:1240 2:1800 3:1239 198.200.40/24 NET-SWSPECTRUM9 C:US 1:1240 2:1800 3:1239 198.200.41/24 NET-SWSPECTRUM10 C:US 1:1240 2:1800 3:1239 198.200.43/24 NET-SWSPECTRUM1 C:US 1:1240 2:1800 3:1239 199.0.132/22 NETBLK-NPR C:US 1:701(136) 2:701(134) 199.1.185/24 NET-ATAWWW C:US 1:1240 2:1800 199.1.186/24 NET-DOWDELL C:US 1:1240 2:1800 199.29.96/19 REACH2 C:US 1:701(136) 2:701(134) 199.45.127/24 NET-UUNETCA-CBLK3 C:CA 1:701(136) 2:701(134) 199.166.39/24 NET-DKW1 C:CA 1:1240 2:1800 3:1239 199.171.23/24 NETBLK-ERINET-2 C:US 1:1800 2:1240 3:1239 199.171.88/22 INTERSERVE-NET C:US 1:701(136) 2:701(134) 199.173.149/24 HRW-NET C:US 1:701(136) 2:701(134) 199.173.176/20 IXL-NET C:US 1:701(136) 2:701(134) 199.185.138/24 NET-SHARECOM-CA C:CA 1:1240 2:1800 3:1239 199.190.250/24 CAMD-C-BLK C:US 1:3561(218) 2:3561(11) 3:279 4:86 199.190.251/24 CAMD-C-BLK C:US 1:3561(218) 2:3561(11) 3:279 4:86 199.221.107/24 NETBLK-ANS-C-BLOCK2 C:US 1:1693 199.246.215/24 TRIGRAPH C:CA 1:2493(35) 2:2493(91) 199.253.128/21 BCBSND-NET C:US 1:3561(11) 2:3561(218) 3:685 4:73 5:101 200.0.118/23 UPC-NET C:PE 1:1800 2:1239 3:1240 200.10.64/24 TELERED C:PE 1:1800 2:1239 3:1240 200.10.65/24 TELERED C:PE 1:1800 2:1239 3:1240 200.10.66/24 TELERED C:PE 1:1800 2:1239 3:1240 200.10.67/24 TELERED C:PE 1:1800 2:1239 3:1240 200.10.68/24 TELERED C:PE 1:1800 2:1239 3:1240 200.10.69/24 TELERED C:PE 1:1800 2:1239 3:1240 200.10.70/24 TELERED C:PE 1:1800 2:1239 3:1240 200.10.71/24 TELERED C:PE 1:1800 2:1239 3:1240 200.10.72/24 TELERED C:PE 1:1800 2:1239 3:1240 200.10.73/24 TELERED C:PE 1:1800 2:1239 3:1240 200.10.74/24 TELERED C:PE 1:1800 2:1239 3:1240 200.10.75/24 TELERED C:PE 1:1800 2:1239 3:1240 200.10.76/24 TELERED C:PE 1:1800 2:1239 3:1240 200.10.77/24 TELERED C:PE 1:1800 2:1239 3:1240 200.10.78/24 TELERED C:PE 1:1800 2:1239 3:1240 200.10.79/24 TELERED C:PE 1:1800 2:1239 3:1240 200.14.215/24 CTI-NET7 C:CL 1:3561(218) 2:3561(11) 3:86 4:279 200.14.242/24 CAMARA-NET C:CL 1:3561(218) 2:3561(11) 3:86 4:279 202.30/15 KREONET-SERI-AGAIN C:KR 1:1800 2:1239 3:1240 203.12.242/24 QUASARPROF-AU C:AU 1:297(144) 2:297(145) 203.12.243/24 MARENGO-AU C:AU 1:297(144) 2:297(145) 203.12.244/24 VISION-AU C:AU 1:297(144) 2:297(145) 203.12.245/24 VISION-AU C:AU 1:297(144) 2:297(145) 203.12.246/24 VISION-AU C:AU 1:297(144) 2:297(145) 203.12.247/24 VISION-AU C:AU 1:297(144) 2:297(145) 203.12.248/24 PICA-AU C:AU 1:297(144) 2:297(145) 203.12.249/24 NEUTRINO-AU C:AU 1:297(144) 2:297(145) 203.12.250/24 QUICKMODE-AU C:AU 1:297(144) 2:297(145) 203.12.251/24 INFOBAHN-AU C:AU 1:297(144) 2:297(145) 203.12.252/24 PEGASUS-AU C:AU 1:297(144) 2:297(145) 203.12.253/24 PEGASUS-AU C:AU 1:297(144) 2:297(145) 203.12.254/24 PEGASUS-AU C:AU 1:297(144) 2:297(145) 203.12.255/24 PEGASUS-AU C:AU 1:297(144) 2:297(145) 203.13.0/24 CIN-AU C:AU 1:297(144) 2:297(145) 203.13.1/24 CIN-AU C:AU 1:297(144) 2:297(145) 203.13.2/24 CIN-AU C:AU 1:297(144) 2:297(145) 203.13.3/24 CIN-AU C:AU 1:297(144) 2:297(145) 203.13.4/24 CIN-AU C:AU 1:297(144) 2:297(145) 203.13.5/24 CIN-AU C:AU 1:297(144) 2:297(145) 203.13.6/24 CIN-AU C:AU 1:297(144) 2:297(145) 203.13.7/24 CIN-AU C:AU 1:297(144) 2:297(145) 203.13.8/24 CIN-AU C:AU 1:297(144) 2:297(145) 203.13.9/24 CIN-AU C:AU 1:297(144) 2:297(145) 203.13.10/24 CIN-AU C:AU 1:297(144) 2:297(145) 203.13.11/24 CIN-AU C:AU 1:297(144) 2:297(145) 203.13.12/24 CIN-AU C:AU 1:297(144) 2:297(145) 203.13.13/24 CIN-AU C:AU 1:297(144) 2:297(145) 203.13.14/24 CIN-AU C:AU 1:297(144) 2:297(145) 203.13.15/24 CIN-AU C:AU 1:297(144) 2:297(145) 203.250.128/20 APNIC-CIDR-BLK C:KR 1:1800 2:1240 203.250.160/21 APNIC-CIDR-BLK C:KR 1:1800 2:1240 203.250.168/22 APNIC-CIDR-BLK C:KR 1:1800 2:1240 203.250.192/18 APNIC-CIDR-BLK C:KR 1:1800 2:1240 203.254/16 KREONET-SERI-YET-AGAI C:KR 1:1800 2:1239 3:1240 204.50.44/22 NET-NEWMEDIA C:CA 1:1240 2:1800 3:1239 204.50.51/24 NET-SONETIS C:CA 1:1240 2:1800 3:1239 204.50.52/22 NET-SOLECT C:CA 1:1240 2:1800 3:1239 204.72.176/20 HSII2 C:US 1:3561(218) 2:3561(11) 3:1225(130) 4:1225(129) 5:1225(131) 6:1239 7:1240 8:1800 204.73.59/24 SUFSYS3 C:US 1:3561(218) 2:3561(11) 3:1225(130) 4:1225(129) 5:1225(131) 6:1239 7:1240 8:1800 204.90.111/24 NET-WHC-NET C:US 1:3830 204.94.90/24 CTSNET-90BLK C:US 1:1240 2:1800 3:1239 204.101.51/24 WLDONLINE C:CA 1:1239 2:1800 3:1240 204.107.238/24 NET-VAMPIRE C:US 1:1800 2:1240 3:1239 204.117.183/24 NET-NIS C:US 1:1239 2:1800 3:1240 204.128.137/24 SIGNALSYSNET C:US 1:2149 2:174 3:3830 204.138.61/24 NET-CONBRIO-2 C:CA 1:1240 2:1800 3:1239 204.138.65/24 NET-SOFPAK C:CA 1:1240 2:1800 3:1239 204.165.56/24 DRAGON-56 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.57/24 DRAGON-57 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.58/24 DRAGON-58 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.59/24 DRAGON-59 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.60/24 DRAGON-60 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.61/24 DRAGON-61 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.62/24 DRAGON-62 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.165.63/24 DRAGON-63 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.174.103/24 DAO.NRC.CA C:CA 1:1331 204.174.222/24 AXION.COM C:CA 1:1331 204.176.20/23 SYNOPSYS2-NET C:US 1:701(136) 2:701(134) 204.176.20/24 SYNOPSYS2-NET C:US 1:701(136) 2:701(134) 204.176.21/24 SYNOPSYS2-NET C:US 1:701(136) 2:701(134) 204.176.224/19 INTERSERVE2 C:US 1:701(136) 2:701(134) 204.177.235/24 INTERSOURCE C:US 1:701(136) 2:701(134) 204.178.185/24 STARNET-NET C:US 1:701(136) 2:701(134) 204.178.222/23 NETBLK-WSNET-NET C:US 1:3830 204.181.88/24 KAMSTRA-AUSTIN C:US 1:1800 2:1239 3:1240 204.182.0/18 NETBLK-TLGNET-MCI C:US 1:3561(11) 2:3561(218) 3:1240 4:1239 5:1800 204.187.64/24 LAUNCHPAD-CA C:CA 1:2493(35) 2:2493(91) 204.187.86/24 SOUND-SOFT C:CA 1:2493(35) 2:2493(91) 204.188.128/18 NETBLK-TLGNET-MV-MCI C:US 1:3561(11) 2:3561(218) 3:1240 4:1239 5:1800 204.213.176/20 NETPLEX-NET C:US 1:1239 2:1800 3:1240 204.225.191/24 NET-EIS C:CA 1:1240 2:1800 3:1239 204.225.221/24 NET-INFOSHARE C:CA 1:1240 2:1800 3:1239 204.225.236/24 NET-OPCOM C:CA 1:1240 2:1800 3:1239 204.248.18/23 NET-ENS C:US 1:1239 2:1800 3:1240 204.249.0/22 NET-CUBED C:US 1:1239 2:1800 3:1240 204.252.66/23 FLAMINGO C:US 1:701(136) 2:701(134) 204.252.76/23 CYBERSERVE-NETBLK C:US 1:701(136) 2:701(134) 204.252.106/24 KILBO-NET C:US 1:701(136) 2:701(134) 204.252.108/23 I-LINK-NET C:US 1:701(136) 2:701(134) 205.118/15 NETBLK-WESTNETUT C:US 1:1240 2:1800 3:1239 4:210 5:209 205.120.0/24 NETBLK-WESTNETUT C:US 1:1240 2:1800 3:1239 4:210 5:209 Deletions: --163.135/16 DATA-NET C:JP 1:2149 2:174 --193.97.4/24 NOVELL-GMBH4 C:DE 1:210 2:209 --193.97.8/24 NOVELL-GMBH8 C:DE 1:210 2:209 --193.97.9/24 NOVELL-GMBH9 C:DE 1:210 2:209 --193.97.16/24 NOVELL-GMBH16 C:DE 1:210 2:209 --193.97.17/24 NOVELL-GMBH17 C:DE 1:210 2:209 --193.97.18/24 NOVELL-GMBH18 C:DE 1:210 2:209 --193.97.59/24 NOVELL-GMBH59 C:DE 1:210 2:209 --198.59.1/24 CSUDEN C:US 1:209 2:210 --198.59.7/24 NETBLK-WESTNET C:US 1:209 2:210 --198.59.8/24 NETBLK-WESTNET8 C:US 1:209 2:210 --198.59.10/24 CSN-SLIP-GREELY C:US 1:209 2:210 --198.59.11/24 KHAOS-NET C:US 1:209 2:210 --198.59.14/24 ADAPTEC-NET C:US 1:209 2:210 --198.59.15/24 NETBLK-WESTNET-59-15 C:US 1:209 2:210 --198.59.16/24 NETBLK-WESTNET-59-16 C:US 1:209 2:210 --198.59.22/24 TWARE-NET C:US 1:209 2:210 --198.59.23/24 NETBLK-WESTNET-59-23 C:US 1:209 2:210 --198.59.24/24 XVT-NET5 C:US 1:209 2:210 --198.59.25/24 NETBLK-WESTNET-59-25 C:US 1:209 2:210 --198.59.30/24 NETBLK-WESTNET-59-30 C:US 1:209 2:210 --198.59.31/24 NETBLK-WESTNET-59-31 C:US 1:209 2:210 --198.59.32/24 NETBLK-WESTNET-59-32 C:US 1:209 2:210 --198.59.33/24 SCICON-NET1 C:US 1:209 2:210 --198.59.53/24 NETBLK-WESTNET-53 C:US 1:209 2:210 --198.59.109/24 NETBLK-WESTNET C:US 1:1334 --198.59.113/24 NETBLK-WESTNET C:US 1:1334 --198.59.115/24 DBACYBER C:US 1:1334 --198.59.117/24 CINM2 C:US 1:1334 --198.59.129/24 NRCABQ C:US 1:1334 --198.59.135/24 NETBLK-WESTNET135 C:US 1:209 2:210 --198.59.165/24 NETBLK-WESTNET C:US 1:1334 --198.59.177/24 NETBLK-WESTNET C:US 1:1334 --198.59.180/24 NETBLK-WESTNET C:US 1:1334 --198.60.40/24(U) NETBLK-WESTNET-60-40 C:US 1:210 2:209 --198.60.121/24 NETBLK-WESTNET C:US 1:1800 2:1240 3:1239 4:210 5:209 --198.60.122/24 NETBLK-WESTNET C:US 1:1800 2:1240 3:1239 4:210 5:209 --198.60.123/24 NETBLK-WESTNET C:US 1:1240 2:1800 3:210 4:209 --198.60.124/24 NETBLK-WESTNET C:US 1:1240 2:1800 3:210 4:209 --198.60.125/24 NETBLK-WESTNET C:US 1:1240 2:1800 3:210 4:209 --198.60.126/24 NETBLK-WESTNET C:US 1:1240 2:1800 3:210 4:209 --198.60.127/24 NETBLK-WESTNET C:US 1:1240 2:1800 3:210 4:209 --198.60.128/24 NETBLK-WESTNET C:US 1:1800 2:1240 3:1239 4:210 5:209 --198.60.130/24 ASPIN C:US 1:1800 2:1240 3:1239 4:210 5:209 --198.60.132/24 ASPIN2 C:US 1:1800 2:1240 3:1239 4:210 5:209 --198.60.133/24 WESTNET-C-60-133 C:US 1:1800 2:1240 3:1239 4:210 5:209 --198.60.140/24 WESTNET-C-60-140 C:US 1:1240 2:1800 3:210 4:209 --198.60.141/24 WESTNET-C-60-141 C:US 1:1800 2:1240 3:1239 4:210 5:209 --198.60.142/24 WESTNET-C-60-142 C:US 1:1240 2:1800 3:210 4:209 --198.60.143/24 EVERGREEN C:US 1:1240 2:1800 3:1239 4:210 5:209 --198.60.144/24 WESTNET-C-60-144 C:US 1:1800 2:1240 3:1239 4:210 5:209 --198.60.145/24 WESTNET-C-60-145 C:US 1:1800 2:1240 3:1239 4:210 5:209 --198.60.146/24 TRGLINK C:US 1:1800 2:1240 3:1239 4:210 5:209 --198.60.149/24 USWCL C:US 1:1800 2:1240 3:1239 4:210 5:209 --198.60.150/24 IRONWOOD C:US 1:1800 2:1240 3:1239 4:210 5:209 --198.60.153/24 NET-WN-ID-FR C:US 1:1800 2:1240 3:1239 4:210 5:209 --198.60.184/24 WESTNET C:US 1:1800 2:1240 3:1239 4:210 5:209 --198.60.186/24 MOHAVE-CC C:US 1:1800 2:1240 3:1239 4:210 5:209 --198.60.189/24 WESTNET C:US 1:1800 2:1240 3:1239 4:210 5:209 --198.60.190/24 NETBLK-WESTNET C:US 1:1800 2:1240 3:1239 4:210 5:209 --199.171.88/24 INTERSERVE-NET C:US 1:701(136) 2:701(134) --199.171.89/24 INTERSERVE-NET C:US 1:701(136) 2:701(134) --199.171.90/24 INTERSERVE-NET C:US 1:701(136) 2:701(134) --199.171.91/24 INTERSERVE-NET C:US 1:701(136) 2:701(134) --199.173.176/23 IXL-NET C:US 1:701(136) 2:701(134) --202.33.24/24 RAPIDNET C:JP 1:2149 2:174 --202.33.61/24 TANDEM C:JP 1:2149 2:174 --203.250.0/19 APNIC-CIDR-BLK C:KR 1:1800 2:1240 --203.250.64/19 APNIC-CIDR-BLK C:KR 1:1800 2:1240 3:1239 --203.250.96/23 APNIC-CIDR-BLK C:KR 1:1800 2:1240 --203.250.98/23 APNIC-CIDR-BLK C:KR 1:1800 2:1240 --204.72.178/24 HSII2-3 C:US 1:3561(218) 2:3561(11) 3:1225(130) 4:1225(129) 5:1225(131) 6:1239 7:1240 8:1800 --204.72.180/24 HSII2-5 C:US 1:3561(218) 2:3561(11) 3:1225(130) 4:1225(129) 5:1225(131) 6:1239 7:1240 8:1800 --204.134.0/24 INNSOL C:US 1:1334 --204.134.1/24 NETBLK-CSN-BLOCK-6 C:US 1:1334 --204.134.2/24 DWF-DOM C:US 1:1334 --204.134.3/24 DECCS C:US 1:1334 --204.134.4/24 WACKO-NET C:US 1:1334 --204.134.77/24 CSN-BLOCK-6 C:US 1:1334 --204.134.78/24 CSN-BLOCK-6 C:US 1:1334 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 1321 - ANS San Francisco - DNSS 11 (US) - DNSS 11 Peer: 140.222.8.196 - ANS - cnss12.San-Francisco.t3.ans.net AS 1681 - ANS - Ann Arbor - ENSS 131 Peer: 140.222.131.4 - ANS - enss194.t3.ans.net AS 4388 - NET99-PACNAP-AS - DNSS 11 Peer: 198.32.128.16 - Net99 - pacnap.net99.net AS690 CIDR Squeezings Report: 9751 Nets, 180 ASs, 2859 Aggregates ------------------------------------------------------------------ 9751 (82%) of the ever-announced more-specific routes within aggregates have been withdrawn. 238 of those were withdrawn within the last week. 458 the week before that. 193 the week before that. 180 ASs have registered aggregates in the PRDB. 160 of those are announcing aggregates. 86 have withdrawn at least one more specific route. 2859 Aggregates are configured. 2104 of these were Top-Level Aggregates (not nested in another aggregate). 1618 of these are being announced to AS690. 1023 of those have at least one subnet configured (the other 595 may be saving the Internet future subnet announcements). 873 have stopped announcing at least one configured more specific route. 840 have stopped announcing half of their configured more specific routes. 809 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

IISP Congress (fwd)
by Elise Gerich 23 Feb '95

23 Feb '95

At the NANOG meeting in Boulder, we decided to discuss the date and location of the next meeting on line. Enclosed is the announcment of the IISP which has offered to host the next NANOG meeting in San Diego on April 10, 1995. Please send email to the list indicating whether this would be a good date for the next meeting, and if you would consider attending then. If this is not a good time/place, please make recommendations to the list or to me privately as to an alternate date/place. Thanks. --Elise > > ----- Begin Included Message ----- > > >From @snoopy.isoc.org:amr@linus.isoc.org Wed Feb 22 10:20:18 1995 > Date: Wed, 22 Feb 1995 13:11:23 -0500 > To: isoc-trustees(a)linus.isoc.org, isoc-advisory-council(a)linus.isoc.org > From: Tony Rutkowski <amr(a)linus.isoc.org> > Subject: IISP Congress > Cc: ops-exec(a)linus.isoc.org > > ======================================================================= > 22 Feb 1994 > > INTERNATIONAL CONGRESS OF INTERNET SERVICE PROVIDERS > San Diego CA USA 11-12 Apr 1995 > ANNOUNCEMENT > > This worldwide congress is being jointly hosted by the Internet Society, > the Commercial Internet Exchange (CIX), and FARNET, Inc., in cooperation > with other organizations to allow Internet Service Providers and Network > Information Center administrators to identify and explore shared problems > and a broad range of alternatives in Internet provisioning and administration. > For the purposes of this congress, a service provider is regarded as any > entity that itself has an Internet transport capability which it provides > to others. > > The objective of the congress is to promote a discussion framework for future > meetings and activities that may occur among the interested parties, as well > as some initial convergences on major issues. It is not intended to displace > existing operations engineering forums. > > The congress is proceeding via its programme committee to focus on key topic > areas, earmarking individuals to develop both an overview of the area, as well > as range of views on possible alternatives. Discussants and rapporteurs will > be named for each session, and conference report will be widely available. > This report is expected to constitute a continuing and growing set of materials > to assure the continued global scaling, universal connectivity, and effective > operation of the Internet. > > In light of the importance of this congress, the complexity of the issues, > and the need for a robust exchange of views, the aim is to strongly > encourage one key policy and one key technical attendee from each provider > or NIC organization. Space constraints may limit the number of participants. > > The congress co-chairs are Scott Bradner (Internet Society and Harvard), Bob > Collet (Commercial Internet Exchange and Sprint), and Jim Williams (FARNet). > > The congress home page is: http://www.isoc.org/iisp/iisp-home.html > and will provide continually updated information on the congress. > > ------------------------------------------------------------------------- > Registration Template > > Organization: ___________________________ > > > Internet Service Provider: __ Yes __ No > Network Administrative Center (e.g., NIC): __ Yes __ No > Other (type ______________): __ Yes __ No > > > Provider policy rep > --------------------- > > Family Name: ___________________________ > > First Name: ___________________________ > > Title: ___________________________ > > Street Address: ___________________________ > > ___________________________ > > City: ___________________________ > > State or Province: _________ > > Postal Code: _________ > > Country: ________________________ > > Email: ___________________________ > > Fax: ___________________________ > > Telephone: ___________________________ > > Preferred Badge Name: _______________________________ > > > Service provider technical rep > ------------------------ > > Family Name: ___________________________ > > First Name: ___________________________ > > Title: ___________________________ > > Street Address: ___________________________ > > ___________________________ > > City: ___________________________ > > State or Province: _________ > > Postal Code: _________ > > Country: ________________________ > > Email: ___________________________ > > Fax: ___________________________ > > Telephone: ___________________________ > > Preferred Badge Name: _______________________________ > > ----------------------------------------------------------------------- > > REGISTRATION FEES > > The registration fee for an organization is US$ 600. This fee covers two > attendees from the organization. The aim is to have one policy and one > technical attendee. > > The registration fee for additional person from an organization is > US$ 600 EACH. A registration form for an additional person will be sent > upon request. > > How would you like to pay? > > __ Credit card: > > __ Mastercard > __ Visa > __ American Express > > Credit Card Number: _____________________ > Expiration Date: _____________________ > Name on Card: _____________________ > > Do we have your authorization to charge the indicated total > against your card number? (Type YES or Sign) > > ____________________ > > __ Bank Transfer: > > Send to: Riggs Bank of Virginia Bank ABA no. 056001260 > 8315 Lee Highway Account: Internet Society 148-387-10 > Fairfax VA 22031 > USA > > Please indicate your family name, IIOC, and your organization > > __ Money Order or Personal Cheque. > > > ----------------------------------------------------------------------- > > SEND THIS COMPLETED TEMPLATE TO: <ops-register(a)linus.isoc.org> or > > FAX THIS COMPLETED TEMPLATE TO: +1 703 648 9887 > > POST THIS COMPLETED TEMPLATE TO: Internet Society > 12020 Sunrise Valley Dr. Suite 270 > Reston VA 22091 > USA > > ----------------------------------------------------------------------- > > Hotel Registration > ------------------ > Sheraton Harbor Island > 1380 Harbor Island Drive > San Diego CA 92101 > USA > > 1. Contact the hotel registration directly using their reservation line: > +1 619 692-2265 or fax: +1 619 692-2363 > 2. Indicate you are attending the Internet Society International Conference > on Internet Operations. > 3. Single or double occupancy rooms are $130 per night. > 4. Most popular forms of payment are accepted for reservations. > > Space is limited for this conference. Register soon. > > Thank you. > > ======================================================================= > > > > > ----- End Included Message ----- > >

4 3

Notes
by sob＠academ.com 23 Feb '95

23 Feb '95

I am trying to get the notes all wrapped up and available for merit by the end of this weekend. I still need machine readable versions of what was presented from the following folks: Jack Waters, Mitch Baltuch, Vince Fuller, Rolf Hahn & George Shenoda, Dennis Ferguson, and Mick Behringer. I have received word from Mitch and he should be uploading today. Rolf has contacted me, but I don't know the status of his slides. I have talked to Jack, but I don't know the status of his slides. -- Stan | Academ Consulting Services |internet: sob(a)academ.com Olan | For more info on academ, see this |uucp: bcm!academ!sob Barber | URL- http://www.academ.com/academ |Opinions expressed are only mine.

1 0

more updates to NANOG notes
by sob＠academ.com 23 Feb '95

23 Feb '95

I have added Guy Almes slides to the ANS transition page. I have added Matt Mathis' comments to the vBNS page. -- Stan | Academ Consulting Services |internet: sob(a)academ.com Olan | For more info on academ, see this |uucp: bcm!academ!sob Barber | URL- http://www.academ.com/academ |Opinions expressed are only mine.

1 0

Re: IISP Congress (fwd)
by salo＠msc.edu 23 Feb '95

23 Feb '95

> From: Elise Gerich <epg(a)merit.edu> > Subject: IISP Congress (fwd) > To: nanog(a)merit.edu > Date: Wed, 22 Feb 1995 18:00:21 -0500 (EST) > > At the NANOG meeting in Boulder, we decided to discuss the date and location > of the next meeting on line. > > Enclosed is the announcment of the IISP which has offered to host the next > NANOG meeting in San Diego on April 10, 1995. Please send email to the list > indicating whether this would be a good date for the next meeting, and if > you would consider attending then. > > If this is not a good time/place, please make recommendations to the list > or to me privately as to an alternate date/place. > [...] This is the week after IETF, as has been pointed out, and two weeks after Interop. -tjs

1 0

Re: IISP Congress (fwd)
by Sean Doran 23 Feb '95

23 Feb '95

| The $600 registration fee for this event also begs the question of what, if | any, value the ISOC brings to NANOG. I shall be extremely frank and state that in my humble personal opinion, the answer to Vince's question is: "Absolutely Nothing". Moreover, if you swap out NANOG and swap in IEPG, the answer is still "Absolutely Nothing", in spades. Sean. P.S.: I think ISOC's role in these operations forums should be limited to nil, or at most allowing them to offset the cost of coffee and donuts that the hosts of the NANOG or IEPG conferences usually provide, provided, of course, that ISOC well understands that neither body is beholden to it, or operates "under its auspices" or whatever.

1 0