From list-admin Fri Apr 1 05:07:34 1994 Received: from localhost (skw@localhost) by merit.edu (8.6.5/8.6.5) id FAA01041 for nwg; Fri, 1 Apr 1994 05:07:34 -0500 Date: Fri, 1 Apr 1994 05:07:34 -0500 From: "Steven K. Widmayer" Message-Id: <199404011007.FAA01041@merit.edu> To: nwg Subject: Additions to the NSFNET policy-based routing database ------------------------------------------------------------------------------ New format for Metric:AS lists coming later in this and all reports. See 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 Configured Networks 28748 = 28 4586 24075 59 Added Networks 175 = 0 14 149 12 Deleted Networks 5 = 0 0 4 1 *** Note: AS 1957 networks are configured for ANS CO+RE sites that use *** the ANSnet backbone for CIX transit. IP address Net name Country Priority:AS ---------- -------- ------- ----------- 133.251/16 MKCWAN C:JP 1:1957 137.69/16 LEGATO-NET C:US 1:1957 141.122/16 NESTNET C:CH 1:1133 2:1674 3:1800 141.160/16 MOODYS C:US 1:2149 2:174 145.0/9 SURFNET-B-AGGR-I C:NL 1:1800 2:1133 3:1674 4:1240 145.128/10 SURFNET-B-AGGR-II C:NL 1:1800 2:1133 3:1674 4:1240 145.192/11 SURFNET-B-AGGR-III C:NL 1:1800 2:1133 3:1674 4:1240 147.13/16 TELUB C:SE 1:1800 2:1879 3:1133 4:1240 147.202/16 LMT C:US 1:1225 2:267 3:266 4:555 157.147/16 TENSOR C:US 1:2149 2:174 158.164/16 NWMORTGAGE C:US 1:1225 2:267 3:266 4:555 160.16/16 NIC-NET C:JP 1:1957 160.69/16 PACCARNET C:US 1:1982 161.64/16 UMAC C:MO 1:372 2:297 161.161/16 PRIMERICACORP C:US 1:2149 2:174 165.220/16 PHILNET-B C:PH 1:1957 167.75/16 CITYOFTALLA-B C:US 1:279 2:86 192.5.160/24 PENN-STATE-10 C:US 1:1663 192.51.54/24 JAPAN-INET1 C:JP 1:1957 192.56.252/24 SPOKANECC C:US 1:1331 192.83.19/24 MMH-NET C:FI 1:701 2:702 192.87/16 SURFNET-C-AGGR C:NL 1:1800 2:1133 3:1674 4:1240 192.108.198/23 NET-STUPI-D C:SE 1:1800 2:1879 3:1133 4:1240 192.108.200/21 NET-STUPI-F C:SE 1:1800 2:1879 3:1133 4:1240 192.108.208/22 MUGGEN C:SE 1:1800 2:1879 3:1133 4:1240 192.108.212/23 SOVRUMMET C:SE 1:1800 2:1879 3:1133 4:1240 192.109.179/24 AUTONOM-HQ C:DE 1:701 2:1800 192.122.134/24 NCB-C-122-134 C:SG 1:97 192.122.135/24 NCB-C-122-135 C:SG 1:97 192.122.136/24 NCB-C-122-136 C:SG 1:97 192.122.137/24 NCB-C-122-137 C:SG 1:97 192.122.138/24 NCB-C-122-138 C:SG 1:97 192.122.139/24 NCB-C-122-139 C:SG 1:97 192.122.140/24 NCB-C-122-140 C:SG 1:97 192.124.171/24 MCST-SUNLAB C:RU 1:701 2:702 5:1800 6:1240 192.124.182/24 IPMCE-MOSCOW C:RU 1:701 2:702 5:1800 6:1240 192.152.82/24 NSC C:DE 1:1324 2:1800 3:1240 4:1133 192.153.174/24 ACONET-T2 C:AT 1:1800 2:1133 3:1240 192.159.95/24 NTAKPE C:DE 1:1324 2:1800 3:1240 4:1133 192.204.124/24 LSAS C:US 1:204 2:1206 192.215.178/24 CERFNET-178 C:US 1:1740 192.216.213/24 SOVAM C:RU 1:200 2:201 192.231.210/24 NET-LCCC C:US 1:97 192.239.235/24 LJL-NET C:US 1:279 2:86 193.10.36/24 SE-NRM C:SE 1:1800 2:1879 3:1133 4:1240 193.44.46/24 STFI-1 C:SE 1:1957 193.48.4/24 FR-MESR-00 C:FR 1:1800 2:1240 3:1133 4:1674 193.48.5/24 FR-MESR-01 C:FR 1:1800 2:1240 3:1133 4:1674 193.48.6/24 FR-MESR-02 C:FR 1:1800 2:1240 3:1133 4:1674 193.48.7/24 FR-MESR-03 C:FR 1:1800 2:1240 3:1133 4:1674 193.48.143/24 IEP-C C:FR 1:1800 2:1240 3:1133 4:1674 193.48.148/24 FR-MESR-04 C:FR 1:1800 2:1240 3:1133 4:1674 193.48.149/24 FR-MESR-05 C:FR 1:1800 2:1240 3:1133 4:1674 193.48.150/24 FR-MESR-06 C:FR 1:1800 2:1240 3:1133 4:1674 193.48.151/24 FR-MESR-07 C:FR 1:1800 2:1240 3:1133 4:1674 193.48.212/24 FR-CCAB1 C:FR 1:1800 2:1240 3:1133 4:1674 193.48.213/24 FR-CCAB2 C:FR 1:1800 2:1240 3:1133 4:1674 193.48.215/24 FR-BITI-02 C:FR 1:1800 2:1240 3:1133 4:1674 193.50.246/24 FR-OR-CRTTSN C:FR 1:1800 2:1240 3:1133 4:1674 193.50.247/24 FR-OR-GAVYSN C:FR 1:1800 2:1240 3:1133 4:1674 193.57.88/24 FRQSTL01 C:FR 1:1800 2:1240 3:1133 4:1674 193.64.171/24 MARTIS1 C:FI 1:701 2:1800 193.70.225/24 PHILIPS-CSA-NET C:IT 1:1957 193.88.49/24 NATIVE C:DK 1:1957 193.97.160/24 MAKS-NET C:DE 1:701 2:1800 193.97.161/24 MAKS-NET C:DE 1:701 2:1800 193.97.162/24 MAKS-NET C:DE 1:701 2:1800 193.97.163/24 MAKS-NET C:DE 1:701 2:1800 193.97.164/24 MAKS-NET C:DE 1:701 2:1800 193.97.165/24 MAKS-NET C:DE 1:701 2:1800 193.97.166/24 MAKS-NET C:DE 1:701 2:1800 193.97.167/24 MAKS-NET C:DE 1:701 2:1800 193.101.19/24 SMK C:DE 1:701 2:1800 193.117.112/24 FOREMOST-NET C:GB 1:1957 193.118.9/24 SCOTRAIL C:GB 1:1957 193.118.252/24 RUSSELL C:GB 1:1957 193.118.253/24 RUSSELL C:GB 1:1957 193.141.20/24 MARANET C:DE 1:1324 2:1800 3:1240 4:1133 193.141.27/24 SCHIELENET C:DE 1:1324 2:1800 3:1240 4:1133 193.141.98/24 HELIOSDE-C-141-98 C:DE 1:1324 2:1800 3:1240 4:1133 193.141.99/24 HELIOSDE-C-141-99 C:DE 1:1324 2:1800 3:1240 4:1133 193.172.160/24 PTT-POST-LT C:NL 1:1800 2:1133 3:1674 4:1240 193.210.8/24 DATANET C:FI 1:1957 193.210.9/24 DATANET C:FI 1:1957 193.210.10/24 DATANET C:FI 1:1957 193.210.11/24 DATANET C:FI 1:1957 193.210.12/24 DATANET C:FI 1:1957 193.210.13/24 DATANET C:FI 1:1957 193.210.14/24 DATANET C:FI 1:1957 193.210.15/24 DATANET C:FI 1:1957 193.210.16/24 DATANET C:FI 1:1957 193.210.17/24 DATANET C:FI 1:1957 193.233.19/24 GPI-LAN-1 C:RU 1:1800 2:1240 193.233.20/24 GPI-LAN-2 C:RU 1:1800 2:1240 193.233.21/24 GPI-LAN-3 C:RU 1:1800 2:1240 193.233.22/24 GPI-LAN-4 C:RU 1:1800 2:1240 193.233.23/24 GPI-LAN-5 C:RU 1:1800 2:1240 193.242.84/24 EUNET-AMS-DMZ C:NL 1:1957 194.2.72/24 FR-BUSOBJ C:FR 1:1957 194.2.73/24 FR-BUSOBJ C:FR 1:1957 194.11.243/24 GROPAR C:CH 1:701 2:1800 194.15.145/24 PFRM C:DE 1:1324 2:1800 3:1240 4:1133 194.22.127/24 UBN-194-22-127 C:SE 1:1957 194.47/16 LU-CBLOCK C:SE 1:1800 2:1879 3:1133 4:1240 198.5.255/24 NETBLK-UUNETCBLK5 C:US 1:1957 198.6.114/24 INTAC C:US 1:701 2:702 198.6.115/24 INTAC C:US 1:701 2:702 198.6.118/24 NET-GATEWAY C:US 1:1957 198.6.119/24 NETBLK-UUNETCBLK6 C:US 1:1957 198.6.195/24 LANSYSTEMS-DOM C:US 1:1957 198.60.27/24 WESTNET C:US 1:210 2:209 198.74.26/24 NORWEST C:US 1:1225 2:267 3:266 4:555 198.79.74/24 IBMLINK C:US 1:279 2:86 198.80.42/24 VISA-NET1 C:US 1:1321 198.108.5/24 MERIT-NET C:US 1:237 2:233 3:266 4:267 5:1225 198.108.132/24 NET-MSU-KMC C:US 1:237 2:233 3:266 4:267 5:1225 198.108.196/24 NORTHWESTERN-108-196 C:US 1:237 2:233 3:266 4:267 5:1225 198.108.197/24 NORTHWESTERN-108-197 C:US 1:237 2:233 3:266 4:267 5:1225 198.109.40/24 DETNET C:US 1:237 2:233 3:266 4:267 5:1225 198.111.17/24 NETBLK-OCC C:US 1:237 2:233 3:266 4:267 5:1225 198.111.18/24 NETBLK-OCC C:US 1:237 2:233 3:266 4:267 5:1225 198.111.19/24 NETBLK-OCC C:US 1:237 2:233 3:266 4:267 5:1225 198.111.20/24 NETBLK-OCC C:US 1:237 2:233 3:266 4:267 5:1225 198.111.21/24 NETBLK-OCC C:US 1:237 2:233 3:266 4:267 5:1225 198.111.22/24 NETBLK-OCC C:US 1:237 2:233 3:266 4:267 5:1225 198.111.23/24 NETBLK-OCC C:US 1:237 2:233 3:266 4:267 5:1225 198.111.24/24 NETBLK-OCC C:US 1:237 2:233 3:266 4:267 5:1225 198.111.25/24 NETBLK-OCC C:US 1:237 2:233 3:266 4:267 5:1225 198.111.26/24 NETBLK-OCC C:US 1:237 2:233 3:266 4:267 5:1225 198.111.27/24 NETBLK-OCC C:US 1:237 2:233 3:266 4:267 5:1225 198.111.28/24 NETBLK-OCC C:US 1:237 2:233 3:266 4:267 5:1225 198.111.29/24 NETBLK-OCC C:US 1:237 2:233 3:266 4:267 5:1225 198.111.30/24 NETBLK-OCC C:US 1:237 2:233 3:266 4:267 5:1225 198.111.31/24 NETBLK-OCC C:US 1:237 2:233 3:266 4:267 5:1225 198.114.190/24 NINE-NET1 C:US 1:560 198.115.157/24 EBC-NET C:US 1:560 2:701 198.137.146/24 NET-VILLAGE C:US 1:1240 2:1800 198.183.183/24 NETBLK-ADCGNET C:US 1:1957 198.186.151/24 TJLS C:US 1:1800 2:1240 198.189.18/24 CSUNET-NORTH C:US 1:2150 2:200 3:201 198.209.88/24 MORENET-C C:US 1:1800 2:1240 198.209.131/24 MORENET-C C:US 1:1800 2:1240 198.234/16 NETBLK-OHIO-NET C:US 1:600 2:1800 198.235.176/24 NET-ISOTRO C:CA 1:2493 199.71.182/24 WMSI-NET C:CA 1:701 2:702 199.71.183/24 WMSI-NET C:CA 1:701 2:702 199.74.172/24 REMOTE-DORSAI-CBLK C:US 1:1800 2:1240 199.79.199/24 NET-RIVA C:US 1:1800 2:1240 199.97.183/24 PSINET-C5 C:US 1:2149 2:174 199.98.33/24 NETBLK-PSINET-C5 C:US 1:1957 199.98.126/24 PSINET-C5-126 C:US 1:2149 2:174 199.98.127/24 PSINET-C5-127 C:US 1:2149 2:174 199.98.128/24 PSINET-C5-128 C:US 1:2149 2:174 199.98.129/24 PSINET-C5-129 C:US 1:2149 2:174 199.98.130/24 PSINET-C5-130 C:US 1:2149 2:174 199.98.131/24 PSINET-C5-131 C:US 1:2149 2:174 199.98.132/24 PSINET-C5 C:US 1:2149 2:174 199.98.133/24 PSINET-C5 C:US 1:2149 2:174 199.98.136/24 PSINET-C5 C:US 1:2149 2:174 199.98.137/24 PSINET-C5 C:US 1:2149 2:174 199.117.9/24 CSN-BLK3 C:US 1:209 2:210 199.120.162/24 DSD C:US 1:1240 2:1800 199.120.249/24 NET-TEAMQUEST C:US 1:1323 199.165.134/24 NET-PMNTRAC C:US 1:1240 2:1800 199.165.146/24 INRI C:US 1:1800 2:1240 199.165.147/24 INRI C:US 1:1800 2:1240 199.165.148/24 INRI C:US 1:1800 2:1240 199.165.221/24 CONJUNGI-NET C:US 1:1982 199.170.1/24 LANSYSTEMS C:US 1:1957 199.182/16 NETBLK-NETCOMCBLK-3 C:US 1:2551 199.183/16 NETBLK-NETCOMCBLK-3 C:US 1:2551 202.0.149/24 NET-ISEAS C:SG 1:97 202.42.140/24 CTRON-SG-C-42-140 C:SG 1:97 202.42.141/24 CTRON-SG-C-42-141 C:SG 1:97 202.42.142/24 NET-STERLING-SG C:SG 1:97 Deletions: --192.87.108/22 SIPLAN-AGGREGATE C:NL 1:1800 2:1133 3:1674 4:1240 --199.86.64/24 MNNET9 C:US 1:1225 2:267 3:266 --199.86.65/24 MNNET10 C:US 1:1225 2:267 3:266 --199.86.66/24 MNNET11 C:US 1:1225 2:267 3:266 --199.86.67/24 MNNET12 C:US 1:1225 2:267 3:266 Expanded listing, sorted by country, then by organization: ========================================================== Austria ------- Vienna University, Computer Center - ACOnet, Universitaetsstrasse 7, A-1010 Vienna, AUSTRIA 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific -------------- 192.153.174/24 ACONET-T2 (AT) Canada ------ ISOTRO Network Management Inc., Suite 200, 440 Laurier Ave W., Ottawa, Ontario, K1R 7X6, CANADA 1:2493 FONOROLA-EAST -------------- 198.235.176/24 NET-ISOTRO (CA) Waterloo Maple Software Inc., 450 Phillip Street, Waterloo, ON, N2L 5J2, CANADA 1:701 Alternet 2:702 Alternet ------------- 199.71.182/24 WMSI-NET (CA) 199.71.183/24 WMSI-NET (CA) Denmark ------- Native Communications, Amagerbrogade 156, 1. tv., DK-2300 Kbenhavn S, DENMARK 1:1957 ANSCIX-AS ------------ 193.88.49/24 NATIVE (DK) Finland ------- Martis Ltd, Sinikalliontie 7, Fi-02630 Espoo, FINLAND 1:701 Alternet 2:1800 ICM-Atlantic ------------- 193.64.171/24 MARTIS1 (FI) Telecom Finland Ltd, PL 228, 33101 TAMPERE, FINLAND 1:1957 ANSCIX-AS ------------ 193.210.8/24 DATANET (FI) 193.210.9/24 DATANET (FI) 193.210.10/24 DATANET (FI) 193.210.11/24 DATANET (FI) 193.210.12/24 DATANET (FI) 193.210.13/24 DATANET (FI) 193.210.14/24 DATANET (FI) 193.210.15/24 DATANET (FI) 193.210.16/24 DATANET (FI) 193.210.17/24 DATANET (FI) The National Land Survey of Finland, Opastinsilta 12 C (P.O.Box 84), Helsinki, 00520, FINLAND 1:701 Alternet 2:702 Alternet ------------ 192.83.19/24 MMH-NET (FI) France ------ Business Objects, 5 rue Chantecoq, Tour Chantecoq, 92808 Puteaux, FRANCE 1:1957 ANSCIX-AS ----------- 194.2.72/24 FR-BUSOBJ (FR) 194.2.73/24 FR-BUSOBJ (FR) Gavy Oceanis BP 152, 44603 Saint-Nazaire Cedex, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ------------- 193.50.246/24 FR-OR-CRTTSN (FR) 193.50.247/24 FR-OR-GAVYSN (FR) MRES - Ministere de l'Enseignement Superieur et de la Recherche, 1 rue Descartes BITI, 75005 Paris, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ------------- 193.48.212/24 FR-CCAB1 (FR) 193.48.213/24 FR-CCAB2 (FR) 193.48.215/24 FR-BITI-02 (FR) Ministere de l'Enseignement Superieur et de la Recherche, 61-65 Rue Dutot, 75015 Paris, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ----------- 193.48.4/24 FR-MESR-00 (FR) 193.48.5/24 FR-MESR-01 (FR) 193.48.6/24 FR-MESR-02 (FR) 193.48.7/24 FR-MESR-03 (FR) 193.48.148/24 FR-MESR-04 (FR) 193.48.149/24 FR-MESR-05 (FR) 193.48.150/24 FR-MESR-06 (FR) 193.48.151/24 FR-MESR-07 (FR) Questel, 930 route des Dollines, F-06560 Valbonne, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ------------ 193.57.88/24 FRQSTL01 (FR) Universite Lumiere Lyon2, 86 rue Pasteur, 69007 Lyon, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ------------- 193.48.143/24 IEP-C (FR) Germany ------- Autonom Computer GmbH, Robert-Bosch-Str. 35, D-W-5603 Wuelfrath, GERMANY 1:701 Alternet 2:1800 ICM-Atlantic -------------- 192.109.179/24 AUTONOM-HQ (DE) Helios Software GmbH, Lavesstr. 80, D-30159 Hannover, GERMANY 1:1324 ANS New York City - DNSS 35 2:1800 ICM-Atlantic 3:1240 ICM-Pacific 4:1133 CERN/DANTE ------------- 193.141.98/24 HELIOSDE-C-141-98 (DE) 193.141.99/24 HELIOSDE-C-141-99 (DE) Krankenhaus Mara gGmbH, Maraweg 21, D-33617 Bielefeld, GERMANY 1:1324 ANS New York City - DNSS 35 2:1800 ICM-Atlantic 3:1240 ICM-Pacific 4:1133 CERN/DANTE ------------- 193.141.20/24 MARANET (DE) MaK System GmbH, Falckensteiner Str. 2-4, D-24159 Kiel, GERMANY 1:701 Alternet 2:1800 ICM-Atlantic ------------- 193.97.160/24 MAKS-NET (DE) 193.97.161/24 MAKS-NET (DE) 193.97.162/24 MAKS-NET (DE) 193.97.163/24 MAKS-NET (DE) 193.97.164/24 MAKS-NET (DE) 193.97.165/24 MAKS-NET (DE) 193.97.166/24 MAKS-NET (DE) 193.97.167/24 MAKS-NET (DE) NCS Ntakpe Computer Systems, Geiselgasteigstr. 141, D-81545 Muenchen, GERMANY 1:1324 ANS New York City - DNSS 35 2:1800 ICM-Atlantic 3:1240 ICM-Pacific 4:1133 CERN/DANTE ------------- 192.152.82/24 NSC (DE) 192.159.95/24 NTAKPE (DE) Sauter Moller GmbH, Emil-Hoffmann-Str. 27, 50996 Koeln, GERMANY 1:701 Alternet 2:1800 ICM-Atlantic ------------- 193.101.19/24 SMK (DE) Schiele Computertechnik, Rechts der Alb 14, D-76199 Karlsruhe, GERMANY 1:1324 ANS New York City - DNSS 35 2:1800 ICM-Atlantic 3:1240 ICM-Pacific 4:1133 CERN/DANTE ------------- 193.141.27/24 SCHIELENET (DE) powerframe Datensysteme GmbH, Am Erlengraben 10, D-76275 Ettlingen, GERMANY 1:1324 ANS New York City - DNSS 35 2:1800 ICM-Atlantic 3:1240 ICM-Pacific 4:1133 CERN/DANTE ------------- 194.15.145/24 PFRM (DE) Italy ----- IUnet NOC, Via all' Opera Pia 11/a, I-16145 Genova, ITALY 1:1957 ANSCIX-AS ------------- 193.70.225/24 PHILIPS-CSA-NET (IT) Japan ----- Japan Inet, JAPAN 1:1957 ANSCIX-AS ------------ 192.51.54/24 JAPAN-INET1 (JP) Mitsubishi Kasei Corporation Research Center, 1000, Kamoshida-cho, Midori-ku, Yokohama 227, JAPAN 1:1957 ANSCIX-AS ---------- 133.251/16 MKCWAN (JP) Nissho Iwai Infocom Systems Co., Ltd., JAPAN 1:1957 ANSCIX-AS --------- 160.16/16 NIC-NET (JP) Macau ----- University of Macau, Computer Service Bureau, University Drive, Taipa, MACAU 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) --------- 161.64/16 UMAC (MO) Netherlands ----------- EUnet BVio, Kruislaan 409, NL-1098 SJ Amsterdam, NETHERLANDS 1:1957 ANSCIX-AS ------------- 193.242.84/24 EUNET-AMS-DMZ (NL) PTT post logistiek / EBT, NETHERLANDS 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1674 CERN/DANTE 4:1240 ICM-Pacific -------------- 193.172.160/24 PTT-POST-LT (NL) SURFnet, P.O. Box 19035, NL-3501 DA Utrecht, NETHERLANDS 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1674 CERN/DANTE 4:1240 ICM-Pacific ------- 145.0/9 SURFNET-B-AGGR-I (NL) 145.128/10 SURFNET-B-AGGR-II (NL) 145.192/11 SURFNET-B-AGGR-III (NL) 192.87/16 SURFNET-C-AGGR (NL) Philippines ----------- Department of Science and Technology, Republic of the Philippines, Computer Science Program, Ateneo de Manila University, Loyola Heights, Quezon City, Metro Manila, PHILIPPINES 1:1957 ANSCIX-AS ---------- 165.220/16 PHILNET-B (PH) Russian Federation ------------------ General Physics Institute RAS, Vavilov str., 38, Moscow, 117942, RUSSIAN FEDERATION 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ------------- 193.233.19/24 GPI-LAN-1 (RU) 193.233.20/24 GPI-LAN-2 (RU) 193.233.21/24 GPI-LAN-3 (RU) 193.233.22/24 GPI-LAN-4 (RU) 193.233.23/24 GPI-LAN-5 (RU) Moscow Centre of SPARC-technologies, 51 Leninsky Prospect, Moscow, 117914, RUSSIAN FEDERATION 1:701 Alternet 2:702 Alternet 5:1800 ICM-Atlantic 6:1240 ICM-Pacific -------------- 192.124.171/24 MCST-SUNLAB (RU) 192.124.182/24 IPMCE-MOSCOW (RU) Sovam Teleport, 2a, Nezhdanova St., Moscow, 103009, RUSSIAN FEDERATION 1:200 BARRNet 2:201 BARRNet -------------- 192.216.213/24 SOVAM (RU) Singapore --------- Cabletron System Pte Ltd, 85 Science Park Drive, #03-03/04, The Cavendish, SINGAPORE 1:97 JvNCnet Regional Network ------------- 202.42.140/24 CTRON-SG-C-42-140 (SG) 202.42.141/24 CTRON-SG-C-42-141 (SG) Institute of Southeast Asian Studies, Heng Mui Keng Terrace, Pasir Panjang, 0511, SINGAPORE 1:97 JvNCnet Regional Network ------------ 202.0.149/24 NET-ISEAS (SG) National Computer Board, 71 Science Park Drive, NCB Building 0511, SINGAPORE 1:97 JvNCnet Regional Network -------------- 192.122.134/24 NCB-C-122-134 (SG) 192.122.135/24 NCB-C-122-135 (SG) 192.122.136/24 NCB-C-122-136 (SG) 192.122.137/24 NCB-C-122-137 (SG) 192.122.138/24 NCB-C-122-138 (SG) 192.122.139/24 NCB-C-122-139 (SG) 192.122.140/24 NCB-C-122-140 (SG) Sterling Software Pte Ltd, 541 Orchard Road, SINGAPORE 1:97 JvNCnet Regional Network ------------- 202.42.142/24 NET-STERLING-SG (SG) Sweden ------ Lund University, Box 118, S-221 00 Lund, SWEDEN 1:1800 ICM-Atlantic 2:1879 EUROPE-RS 3:1133 CERN/DANTE 4:1240 ICM-Pacific --------- 194.47/16 LU-CBLOCK (SE) Naturhistoriska Riksmuseet, Box 50007, S-104 05 Stockholm, SWEDEN 1:1800 ICM-Atlantic 2:1879 EUROPE-RS 3:1133 CERN/DANTE 4:1240 ICM-Pacific ------------ 193.10.36/24 SE-NRM (SE) STUPI, Box 9129, S-102 72 Stockholm, SWEDEN 1:1800 ICM-Atlantic 2:1879 EUROPE-RS 3:1133 CERN/DANTE 4:1240 ICM-Pacific -------------- 192.108.198/23 NET-STUPI-D (SE) 192.108.200/21 NET-STUPI-F (SE) 192.108.208/22 MUGGEN (SE) 192.108.212/23 SOVRUMMET (SE) Telub AB, S-351 80 Vaxjo, SWEDEN 1:1800 ICM-Atlantic 2:1879 EUROPE-RS 3:1133 CERN/DANTE 4:1240 ICM-Pacific --------- 147.13/16 TELUB (SE) Unisource Business Networks Sverige, Kaserntorget 11, S-403 35 Goteborg, SWEDEN 1:1957 ANSCIX-AS ------------- 194.22.127/24 UBN-194-22-127 (SE) stfi, box 5604, s-11486 Stockholm, SWEDEN 1:1957 ANSCIX-AS ------------ 193.44.46/24 STFI-1 (SE) Switzerland ----------- Dr. J. Grob & Partner AG, Technikumstrasse 73, CH-8400 Winterthur, SWITZERLAND 1:701 Alternet 2:1800 ICM-Atlantic ------------- 194.11.243/24 GROPAR (CH) NESTEC Headquarters, En Bergere, CH-1800 Vevey, SWITZERLAND 1:1133 CERN/DANTE 2:1674 CERN/DANTE 3:1800 ICM-Atlantic ---------- 141.122/16 NESTNET (CH) United Kingdom -------------- Foremost Training, EAC Building, 141 St James road, Glasgow G4 0LT, ENGLAND, UNITED KINGDOM 1:1957 ANSCIX-AS -------------- 193.117.112/24 FOREMOST-NET (GB) Russell Consulting Ltd, 200 Derby Road, Nottingham NG7 1NJ, UNITED KINGDOM 1:1957 ANSCIX-AS -------------- 193.118.252/24 RUSSELL (GB) 193.118.253/24 RUSSELL (GB) Scotrail, Room 617, Caledonian Chambers, 87 Union Street, Glasgow G1 3TA, UNITED KINGDOM 1:1957 ANSCIX-AS ------------ 193.118.9/24 SCOTRAIL (GB) United States ------------- Advanced Technology Materials, Inc., 7 Commerce Drive, Danbury, CT 06810, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.128/24 PSINET-C5-128 (US) Allied Data Communications Group, Inc., 5375 Oakbrook Parkway, Norcross, GA 30093, USA 1:1957 ANSCIX-AS -------------- 198.183.183/24 NETBLK-ADCGNET (US) Ascent Solutions, Inc., 17 South St. Clair Street, Suite 300, Dayton, OH 45402, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.127/24 PSINET-C5-127 (US) Audre Inc., 11021 Via Forntera, San Diego, CA 92127, USA 1:1740 CERFnet -------------- 192.215.178/24 CERFNET-178 (US) City of Tallahassee, 300 S. Adams Stree, Tallahassee, FL 32301, USA 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) --------- 167.75/16 CITYOFTALLA-B (US) Colorado SuperNet, Inc., Colorado School of Mines, 1500 Illinois, Golden, CO 80401, USA 1:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 2:210 Westnet Regional Network (Utah Attachment) - ENSS 142 ------------ 199.117.9/24 CSN-BLK3 (US) Conjungi Corp., 5444 E. Mercer Way, Mercer Island, WA 98040-5118, USA 1:1982 Northwest Nexus -------------- 199.165.221/24 CONJUNGI-NET (US) DSD Corp., 2805 odell road NE, Duvall, WA 98019, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic -------------- 199.120.162/24 DSD (US) Data Highway, Inc., 256 Broad Avenue, Palisades Park, NJ 07650, USA 1:701 Alternet 2:702 Alternet ------------ 198.6.114/24 INTAC (US) 198.6.115/24 INTAC (US) Detroit Water & Sewerage Department, Computer Services, 303 S. Livernois, Detroit, MI 48209, USA 1:237 MichNet (MERIT) 2:233 UMnet (University of Michigan) 3:266 CICNET at MERIT 4:267 CICNET at UIUC 5:1225 CICNET at Argonne Labs ------------- 198.109.40/24 DETNET (US) Eastern Book Company, 131 Middle Street, Portland, ME 04112, USA 1:560 NEARnet Regional Network 2:701 Alternet -------------- 198.115.157/24 EBC-NET (US) Entire, Inc., 105 Despatch Drive, East Rochester, NY 14445, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.97.183/24 PSINET-C5 (US) Gateway To The World, Inc., 9200 South Dadeland Blvd., Suite 511, Miami, FL 33156-2703, USA 1:1957 ANSCIX-AS ------------ 198.6.118/24 NET-GATEWAY (US) GeoTel Communications Corp., 25 Porter Road, Littleton, MA 01460, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.126/24 PSINET-C5-126 (US) IBM, 3200 Windy Hill Rd., Marietta, GA 30067, USA 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) ------------ 198.79.74/24 IBMLINK (US) Image Business Systems, 417 Fifth Avenue, New York, NY 10016, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.130/24 PSINET-C5-130 (US) Inter-National Research Institute, 12350 Jefferson Ave., Suite 400, Newport News, VA 23602, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific -------------- 199.165.146/24 INRI (US) 199.165.147/24 INRI (US) 199.165.148/24 INRI (US) LANSYSTEMS-DOM, 300 Park Ave South, New York, NY 10010, USA 1:1957 ANSCIX-AS ------------ 198.6.195/24 LANSYSTEMS-DOM (US) LANSystems Inc., 300 Park Ave South, New York, NY 10010, USA 1:1957 ANSCIX-AS ------------ 199.170.1/24 LANSYSTEMS (US) LaserMaster Corporation, 71156 Shady Oak Road, Eden Prairie, MN 55344, USA 1:1225 CICNET at Argonne Labs 2:267 CICNET at UIUC 3:266 CICNET at MERIT 4:555 Minnesota Supercomputer Center Network (MSCNet) ---------- 147.202/16 LMT (US) Law School Admission Services, PO Box 40, Newton, PA 18940, USA 1:204 PSCNET Regional Network 2:1206 PSCNET Regional Network -------------- 192.204.124/24 LSAS (US) Legato Systems, Inc., 260 Sheridan Avenue, Palo Alto, CA 94306, USA 1:1957 ANSCIX-AS --------- 137.69/16 LEGATO-NET (US) Lehigh County Community College, 4524 Education Park Drive, Schnecksville, PA 18078, USA 1:97 JvNCnet Regional Network -------------- 192.231.210/24 NET-LCCC (US) MERRA, 2901 Hubbard Dr., Pod B, Ann Arbor, MI 48105, USA 1:237 MichNet (MERIT) 2:233 UMnet (University of Michigan) 3:266 CICNET at MERIT 4:267 CICNET at UIUC 5:1225 CICNET at Argonne Labs ------------ 198.108.5/24 MERIT-NET (US) Michigan State University, 220 Computer Center, East Lansing, MI 48824, USA 1:237 MichNet (MERIT) 2:233 UMnet (University of Michigan) 3:266 CICNET at MERIT 4:267 CICNET at UIUC 5:1225 CICNET at Argonne Labs -------------- 198.108.132/24 NET-MSU-KMC (US) Missouri Research and Education Network (MOREnet), University of Missouri-Columbia, Campus Computing, 200 Heinkel Bldg, Columbia, MO 65211, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ------------- 198.209.88/24 MORENET-C (US) 198.209.131/24 MORENET-C (US) Moody's Investors Service, 99 Church Street, New York, NY 10007, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ---------- 141.160/16 MOODYS (US) NETCOM Online Communications Services, Inc., 4000 Moorpark Ave, Suite 209, San Jose, CA 95117, USA 1:2551 NETCOM ---------- 199.182/16 NETBLK-NETCOMCBLK-3 (US) 199.183/16 NETBLK-NETCOMCBLK-3 (US) National Systems, Inc., 1129 20th Street NW, Suite 701, Washington, DC 20036, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.131/24 PSINET-C5-131 (US) Northwestern Michigan College, 1701 E. Front St., Traverse City, MI 49684, USA 1:237 MichNet (MERIT) 2:233 UMnet (University of Michigan) 3:266 CICNET at MERIT 4:267 CICNET at UIUC 5:1225 CICNET at Argonne Labs -------------- 198.108.196/24 NORTHWESTERN-108-196 (US) 198.108.197/24 NORTHWESTERN-108-197 (US) Norwest Mortgage, Inc., 801 Nicollet Mall, 1200 Midwest Plaza, Minneapolis, MN 55402, USA 1:1225 CICNET at Argonne Labs 2:267 CICNET at UIUC 3:266 CICNET at MERIT 4:555 Minnesota Supercomputer Center Network (MSCNet) ---------- 158.164/16 NWMORTGAGE (US) Norwest Technical Services, 255 Second Avenue South, Minneapolis, MN 55479-2011, USA 1:1225 CICNET at Argonne Labs 2:267 CICNET at UIUC 3:266 CICNET at MERIT 4:555 Minnesota Supercomputer Center Network (MSCNet) ------------ 198.74.26/24 NORWEST (US) Number Nine Computer Corp., 18 Hartwell Avenue, Lexington, MA 02173, USA 1:560 NEARnet Regional Network -------------- 198.114.190/24 NINE-NET1 (US) Oakland Community College, 2480 Opdyke Road, Bloomfield Hills, MI 48304, USA 1:237 MichNet (MERIT) 2:233 UMnet (University of Michigan) 3:266 CICNET at MERIT 4:267 CICNET at UIUC 5:1225 CICNET at Argonne Labs ------------- 198.111.17/24 NETBLK-OCC (US) 198.111.18/24 NETBLK-OCC (US) 198.111.19/24 NETBLK-OCC (US) 198.111.20/24 NETBLK-OCC (US) 198.111.21/24 NETBLK-OCC (US) 198.111.22/24 NETBLK-OCC (US) 198.111.23/24 NETBLK-OCC (US) 198.111.24/24 NETBLK-OCC (US) 198.111.25/24 NETBLK-OCC (US) 198.111.26/24 NETBLK-OCC (US) 198.111.27/24 NETBLK-OCC (US) 198.111.28/24 NETBLK-OCC (US) 198.111.29/24 NETBLK-OCC (US) 198.111.30/24 NETBLK-OCC (US) 198.111.31/24 NETBLK-OCC (US) Otsuka America Pharmaceutical, 2440 Research Blvd., Rockville, MD 20850, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.132/24 PSINET-C5 (US) PACCAR, Inc., 480 Houser Way North, Renton, WA 98055, USA 1:1982 Northwest Nexus --------- 160.69/16 PACCARNET (US) PMN TRAC, PO Box 65120, Tucson, AZ 85728, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic -------------- 199.165.134/24 NET-PMNTRAC (US) Pasha Publications, 1616 N. Fort Myer Dr., Suite 1000, Arlington, VA 22209, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.133/24 PSINET-C5 (US) Performance Systems International, Inc., 510 Huntmar Park Drive, Herndon, VA 22070, USA 1:1957 ANSCIX-AS ------------ 199.98.33/24 NETBLK-PSINET-C5 (US) Precision Seismic, Inc., 16010 Barker's Point Lane, Suite 300, Houston, TX 77079, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ---------- 157.147/16 TENSOR (US) Primerica Corp., 300 St. Paul Place, Baltimore, MD 21202, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ---------- 161.161/16 PRIMERICACORP (US) RevNet Systems, Inc., 4825 University Square, Suite 6, Huntsville, AL 35816, USA 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) -------------- 192.239.235/24 LJL-NET (US) Riva, 25 Lorraine Metcalf Dr., Rentham, MA 02093, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ------------- 199.79.199/24 NET-RIVA (US) San Joaquin Valley Library System, 2040 Mariposa Street., Fresno, CA 93702, USA 1:2150 CSUNET-SW 2:200 BARRNet 3:201 BARRNet ------------- 198.189.18/24 CSUNET-NORTH (US) Spokane Community College, N. 2000 Green Street, Spokane, WA 99207, USA 1:1331 ANS Seattle - DNSS 91 ------------- 192.56.252/24 SPOKANECC (US) State of Ohio Office of Telecommunications, 2151 Carmack Ave, Columbus, OH 43221, USA 1:600 OARNET, Cleveland, OH 2:1800 ICM-Atlantic ---------- 198.234/16 NETBLK-OHIO-NET (US) TJLS, 12 Elm Rock Road, Bronxville, NY 10708, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific -------------- 198.186.151/24 TJLS (US) TeamQuest Corp., 2410 3rd Ave. South, Clear Lake, IA 50428, USA 1:1323 ANS Chicago - DNSS 27 -------------- 199.120.249/24 NET-TEAMQUEST (US) The Dorsai Embassy, 38-62 11th Street, Long Island City, NY 11101, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ------------- 199.74.172/24 REMOTE-DORSAI-CBLK (US) The Fielding Institute, 2112 Santa Barbara St., Santa Barbara, CA 93105-3538, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.129/24 PSINET-C5-129 (US) The Pennsylvania State University, University Park, PA 16802, USA 1:1663 ANS-BLK1 ------------ 192.5.160/24 PENN-STATE-10 (US) U.S. Satellite Corp., 935 West Bullion, Murray, UT 84123, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.137/24 PSINET-C5 (US) UUNET Technologies, 3110 Fairview Park Drive, Suite 570, Falls Church, VA 22042, USA 1:1957 ANSCIX-AS ------------ 198.5.255/24 NETBLK-UUNETCBLK5 (US) 198.6.119/24 NETBLK-UUNETCBLK6 (US) Village Networking, 13 Curtis Pl, Longmont, CO 80501, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic -------------- 198.137.146/24 NET-VILLAGE (US) Visa International, 3000 Clearview Way, San Mateo, CA 94402, USA 1:1321 ANS San Francisco - DNSS 11 ------------ 198.80.42/24 VISA-NET1 (US) Westell, Inc., Sentry Bldg, 75 Executive Dr, Aurora, IL 60504, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.136/24 PSINET-C5 (US) Westnet, 3645 Marine Street, U. of Colorado, Boulder, CO 80309-0455, USA 1:210 Westnet Regional Network (Utah Attachment) - ENSS 142 2:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 ------------ 198.60.27/24 WESTNET (US) ========================================================== The following Midlevel/Regional peering sessions have also been added: AS 1663 - ANS-BLK1 - ENSS 200 Peer: 192.5.160.2 - Advanced Network & Services, 100 Clearbrook Road, Elmsford, NY 10523, USA - cisco.net94.psu.edu ========================================================== 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.t3p Information is also avaiable through the PRDB whois server. Type "whois -h prdb.merit.edu help" for details. -------------------------------------------------------------------------- REPORT CHANGES: (Updated March 24, 1994) Metric:AS(NSS) - Historically, peer networks with multiple connections to AS 690 could only select which of those connections their networks would take by creating "Fake" AS numbers, and using those in the PRDB Metric:AS announcement lists. Some time in the next few weeks we will begin supporting an expanded syntax, where the AS may be followed by an optional NSS peer number in parentheses. Eventually, this syntax will be used to replace most or all of the current Fake ASs. This change will affect *all* places that the announcement lists are reported: all whois queries, all network reports, this "NWG" report, and the Auto-NACR. If you have code which parses these announcement lists, please be aware that that code may need modifications soon. CIDR Reports: There is a new "whois" option to list aggregates in the PRDB: whois -h prdb.merit.edu listaggs will produce a listing of the currently registered aggregates. There is also a new report on "nestings" of PRDB-registered aggregates with their more specific routes: nets.non-classful. Anyone considering configuring an aggregate into the PRDB (and you all should be!) is encouraged to pre-check that aggregate by typing the command: whois -h prdb.merit.edu 'aggchk ' (where "" is the aggregate description). This command will list all of the other entries in the PRDB that are more specific routes of , as well as any aggregates all ready configured that contain . The output includes the AUP and announcement lists of each of the nets printed, with discrepancies flagged. This is the same program that we use for sanity-checking the NACRs that you submit. The archived discussion list "db-disc@merit.edu" exists for discussion of PRDB issues. Send a message to "db-disc-request@merit.edu" to subscribe. --Dale Johnson (dsj@merit.edu) -------------------------------------------------------------------------- Please send all requests for configuration changes to nsfnet-admin@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. ******************************* --Steve Widmayer Merit/NSFNET skw@merit.edu --Enke Chen Merit/NSFNET enke@merit.edu --Steven J. Richardson Merit/NSFNET sjr@merit.edu - - - - - - - - - - - - - - - - - From list-admin Mon Apr 4 19:52:41 1994 Received: from interlock.ans.net (interlock.ans.net [147.225.1.3]) by merit.edu (8.6.5/8.6.5) with SMTP id TAA29332 for ; Mon, 4 Apr 1994 19:52:40 -0400 Received: by interlock.ans.net id AA04698 (InterLock SMTP Gateway 1.1 for regional-techs@merit.edu); Mon, 4 Apr 1994 19:52:39 -0400 Received: by interlock.ans.net (Internal Mail Agent-2); Mon, 4 Apr 1994 19:52:39 -0400 Received: by interlock.ans.net (Internal Mail Agent-1); Mon, 4 Apr 1994 19:52:39 -0400 From: Curtis Villamizar Message-Id: <199404042349.AA94360@foo.ans.net> To: regional-techs@merit.edu Subject: Route Flap Reports Date: Mon, 04 Apr 94 19:49:43 -0500 Hi, At the IETF njm/netstat meeting it was suggested that the raw data for the "External Route Flap Reports" be released in it's entirety, excluding data only if specific providers objected. The were no objections to this raised at the meeting. The data consists of a daily count of the number of times unique BGP paths were declared unreachable. A full description of the data collection and the current reports can be found in: ftp.ans.net: /pub/info/routing-stats/ExternalRouteFlapReports If there are no objections, the 1993 data will be made available in about two weeks. If there are objections, data will be removed for those providers who do not wish to have their data reported and a note will be placed with the data to indicate the extent to which it is complete. The 1993 data is mostly complete with on the order of 10 days missing or incomplete due to disk space problems. Another topic that has come up is that since gated was fully deployed on ANSnet (data collection ended on Feb 27), this data has no longer been collected. Data collection should resume shortly. After data collection resumes, the Jan and Feb data and more recent data will be made available approximately monthly. Curtis - - - - - - - - - - - - - - - - - From list-admin Tue Apr 5 04:15:25 1994 Received: from localhost (skw@localhost) by merit.edu (8.6.5/8.6.5) id EAA02957 for nwg; Tue, 5 Apr 1994 04:15:25 -0400 Date: Tue, 5 Apr 1994 04:15:25 -0400 From: "Steven K. Widmayer" Message-Id: <199404050815.EAA02957@merit.edu> To: nwg Subject: Additions to the NSFNET policy-based routing database ------------------------------------------------------------------------------ New format for Metric:AS lists coming later in this and all reports. See 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 Configured Networks 29052 = 29 4595 24364 64 Added Networks 304 = 1 9 289 5 Deleted Networks 0 = 0 0 0 0 *** Note: AS 1957 networks are configured for ANS CO+RE sites that use *** the ANSnet backbone for CIX transit. IP address Net name Country Priority:AS ---------- -------- ------- ----------- 45/8 SHOWNETA C:US 1:200 2:201 133.127/16 NHK-STRL C:JP 1:1957 136.181/16 MICHTRANS-NET C:US 1:237 2:233 3:266 4:267 5:1225 144.18/16 YKTNPOE-GW1 C:US 1:19 2:568 144.142/16 TIMESNET C:US 1:1957 158.229/16 FLINS C:US 1:1800 2:1240 159.100/16 TRRLNET C:GB 1:1957 160.65/16 IDI2 C:US 1:1957 161.203/16 GAO C:US 1:1957 170.55/16 NAESCO C:US 1:560 2:701 192.69.116/24 HPS C:US 1:372 2:297 192.91.197/24 IBMNERBTV06 C:US 1:1326 192.96.139/24 SQLINT C:ZA 1:1957 192.108.196/23 NET-STUPI-B C:SE 1:1800 2:1879 3:1133 4:1240 192.135.227/24 BECPLNET C:US 1:93 192.187.65/24 LATIMES-2 C:US 1:1957 192.187.66/24 LATIMES-3 C:US 1:1957 192.187.67/24 LATIMES-4 C:US 1:1957 192.187.68/24 LATIMES-5 C:US 1:1957 192.187.69/24 LATIMES-6 C:US 1:1957 192.187.70/24 LATIMES-7 C:US 1:1957 192.187.71/24 LATIMES-8 C:US 1:1957 192.187.72/24 LATIMES-9 C:US 1:1957 192.187.73/24 LATIMES-10 C:US 1:1957 192.187.74/24 LATIMES-11 C:US 1:1957 192.187.75/24 LATIMES-12 C:US 1:1957 192.187.76/24 LATIMES-13 C:US 1:1957 192.187.77/24 LATIMES-14 C:US 1:1957 192.187.78/24 LATIMES-15 C:US 1:1957 192.187.79/24 LATIMES-16 C:US 1:1957 192.187.80/24 LATIMES-17 C:US 1:1957 192.187.81/24 LATIMES-18 C:US 1:1957 192.187.82/24 LATIMES-19 C:US 1:1957 192.187.83/24 LATIMES-20 C:US 1:1957 192.187.84/24 LATIMES-21 C:US 1:1957 192.187.85/24 LATIMES-22 C:US 1:1957 192.187.86/24 LATIMES-23 C:US 1:1957 192.187.87/24 LATIMES-24 C:US 1:1957 192.187.88/24 LATIMES-25 C:US 1:1957 192.187.89/24 LATIMES-26 C:US 1:1957 192.187.90/24 LATIMES-27 C:US 1:1957 192.187.91/24 LATIMES-28 C:US 1:1957 192.187.92/24 LATIMES-29 C:US 1:1957 192.187.93/24 LATIMES-30 C:US 1:1957 192.187.94/24 LATIMES-31 C:US 1:1957 192.187.95/24 LATIMES-32 C:US 1:1957 192.208.38/24 DEC-EXTERNAL C:US 1:209 2:210 192.215.64/21 NETBLK-CERFNET C:US 1:1740 193.39.141/24 BLACKNEST C:GB 1:1957 193.51.24/22 FR-UVSQ-CIDR-1 C:FR 1:1800 2:1240 3:1133 4:1674 193.55.240/23 RENATER-D-CIDR-1 C:FR 1:1800 2:1240 3:1133 4:1674 193.71.80/24 MULTIX C:NO 1:701 2:1800 193.97.141/24 MUK-ZENTRALE C:DE 1:1957 193.117.180/24 APOLLOADS C:GB 1:1957 193.118.14/24 BRE-UK-NET C:GB 1:1957 193.120.205/24 ALD C:IE 1:1957 193.120.241/24 IEUNET-ROUTE3 C:IE 1:1957 193.120.243/24 IEUNET-ROUTE2 C:IE 1:1957 193.124.76/24 IKO-NET C:UA 1:701 2:1800 193.124.248/24 MIAN C:RU 1:1957 193.128.72/24 CAMCONTROL C:GB 1:1957 193.130.91/24 MAID C:GB 1:1957 193.130.104/24 QSP C:GB 1:1957 193.130.105/24 BATH-COM C:GB 1:1957 193.130.114/24 MCB-NET C:GB 1:1957 193.130.152/24 BUSINESS-OBJECTS C:GB 1:1957 193.199.5/24 EDU-FI C:FI 1:1957 193.199.47/24 EDU-FI C:FI 1:1957 193.199.48/24 EDU-FI C:FI 1:1957 193.199.49/24 EDU-FI C:FI 1:1957 193.210.44/24 DATANET C:FI 1:1957 193.224.69/24 INGR-HU C:HU 1:1800 2:1133 3:1240 196.6.211/24 NETBLK-UNINET-C4 C:ZA 1:1957 196.7.3/24 NETLINE-SA C:ZA 1:1957 196.7.5/24 OIT-NET-C C:ZA 1:1957 198.6.197/24 NETBLK-UUNETCBLK6 C:US 1:1957 198.6.204/24 MURPHY-NET C:US 1:701 2:702 198.6.205/24 MURPHY-NET C:US 1:701 2:702 198.6.206/24 MURPHY-NET C:US 1:701 2:702 198.6.207/24 MURPHY-NET C:US 1:701 2:702 198.6.232/24 NETBLK-UUNETCBLK6 C:US 1:1957 198.6.233/24 NETBLK-UUNETCBLK6 C:US 1:1957 198.6.234/24 NETBLK-UUNETCBLK6 C:US 1:1957 198.6.235/24 NETBLK-UUNETCBLK6 C:US 1:1957 198.6.236/24 NETBLK-UUNETCBLK6 C:US 1:1957 198.6.237/24 NETBLK-UUNETCBLK6 C:US 1:1957 198.6.238/24 NETBLK-UUNETCBLK6 C:US 1:1957 198.6.239/24 NETBLK-UUNETCBLK6 C:US 1:1957 198.6.240/24 NETBLK-UUNETCBLK6 C:US 1:1957 198.6.241/24 NETBLK-UUNETCBLK6 C:US 1:1957 198.6.242/24 NETBLK-UUNETCBLK6 C:US 1:1957 198.6.243/24 NETBLK-UUNETCBLK6 C:US 1:1957 198.6.251/24 GEC C:US 1:1957 198.13.20/24 HYBRID-3-20 C:US 1:1957 198.60.189/24 WESTNET C:US 1:210 2:209 198.62.75/24 NET-CHRISTUSREX C:US 1:2149 2:174 198.76.40/24 CBEMA-NET1 C:US 1:279 2:86 198.76.128/24 NARA-NET3 C:US 1:86 2:279 198.76.129/24 NARA-NET4 C:US 1:86 2:279 198.76.130/24 NARA-NET5 C:US 1:86 2:279 198.76.131/24 NARA-NET6 C:US 1:86 2:279 198.76.132/24 NARA-NET7 C:US 1:86 2:279 198.76.133/24 NARA-NET8 C:US 1:86 2:279 198.76.134/24 NARA-NET9 C:US 1:86 2:279 198.76.135/24 NARA-NET10 C:US 1:86 2:279 198.76.136/24 NARA-NET11 C:US 1:86 2:279 198.76.137/24 NARA-NET12 C:US 1:86 2:279 198.76.138/24 NARA-NET13 C:US 1:86 2:279 198.76.139/24 NARA-NET14 C:US 1:86 2:279 198.76.140/24 NARA-NET15 C:US 1:86 2:279 198.76.141/24 NARA-NET16 C:US 1:86 2:279 198.76.142/24 NARA-NET17 C:US 1:86 2:279 198.76.143/24 NARA-NET18 C:US 1:86 2:279 198.76.144/24 NARA-NET19 C:US 1:86 2:279 198.76.145/24 NARA-NET20 C:US 1:86 2:279 198.76.146/24 NARA-NET21 C:US 1:86 2:279 198.76.147/24 NARA-NET22 C:US 1:86 2:279 198.76.148/24 NARA-NET23 C:US 1:86 2:279 198.76.149/24 NARA-NET24 C:US 1:86 2:279 198.76.150/24 NARA-NET25 C:US 1:86 2:279 198.76.151/24 NARA-NET26 C:US 1:86 2:279 198.76.152/24 NARA-NET27 C:US 1:86 2:279 198.76.153/24 NARA-NET28 C:US 1:86 2:279 198.76.154/24 NARA-NET29 C:US 1:86 2:279 198.76.155/24 NARA-NET30 C:US 1:86 2:279 198.76.156/24 NARA-NET31 C:US 1:86 2:279 198.76.157/24 NARA-NET32 C:US 1:86 2:279 198.76.158/24 NARA-NET33 C:US 1:86 2:279 198.76.159/24 NARA-NET34 C:US 1:86 2:279 198.78.43/24 CBMS-GSH-NET-1 C:US 1:279 2:86 198.81.1/24 AOL-NET2 C:US 1:1327 2:701 3:702 4:1329 198.81.200/24 ELRON-DMZ C:US 1:1324 198.81.213/24 ANS-C-BLOCK C:US 1:1323 198.84.4/22 WDC-PUBNIX1 C:US 1:701 2:702 198.85.113/24 IAT3-NET C:US 1:1329 198.85.114/24 WAHEC1-NET C:US 1:1329 198.85.220/24 PFEIFFER1 C:US 1:1329 198.85.221/24 PFEIFFER2 C:US 1:1329 198.85.222/24 PFEIFFER3 C:US 1:1329 198.85.223/24 PFEIFFER4 C:US 1:1329 198.85.224/24 PFEIFFER5 C:US 1:1329 198.85.225/24 PFEIFFER6 C:US 1:1329 198.85.226/24 PFEIFFER7 C:US 1:1329 198.85.227/24 PFEIFFER8 C:US 1:1329 198.85.228/24 PFEIFFER9 C:US 1:1329 198.85.229/24 PFEIFFER10 C:US 1:1329 198.85.230/24 PFEIFFER11 C:US 1:1329 198.85.231/24 PFEIFFER12 C:US 1:1329 198.85.232/24 PFEIFFER13 C:US 1:1329 198.85.233/24 PFEIFFER14 C:US 1:1329 198.85.234/24 PFEIFFER15 C:US 1:1329 198.85.235/24 PFEIFFER16 C:US 1:1329 198.85.236/24 CAPEFEAR1 C:US 1:1329 198.85.237/24 CAPEFEAR2 C:US 1:1329 198.85.238/24 CAPEFEAR3 C:US 1:1329 198.85.239/24 CAPEFEAR4 C:US 1:1329 198.85.240/24 CAPEFEAR5 C:US 1:1329 198.85.241/24 CAPEFEAR6 C:US 1:1329 198.85.242/24 CAPEFEAR7 C:US 1:1329 198.85.243/24 CAPEFEAR8 C:US 1:1329 198.85.244/24 CAPEFEAR9 C:US 1:1329 198.85.245/24 CAPEFEAR10 C:US 1:1329 198.85.246/24 CAPEFEAR11 C:US 1:1329 198.85.247/24 CAPEFEAR12 C:US 1:1329 198.85.248/24 LOUISBURG1 C:US 1:1329 198.85.249/24 LOUISBURG2 C:US 1:1329 198.85.250/24 LOUISBURG3 C:US 1:1329 198.85.251/24 LOUISBURG4 C:US 1:1329 198.85.252/24 LOUISBURG5 C:US 1:1329 198.85.253/24 LOUISBURG6 C:US 1:1329 198.85.255/24 LOUISBURG8 C:US 1:1329 198.86.104/24 GTCC1 C:US 1:1329 198.86.105/24 GTCC2 C:US 1:1329 198.86.106/24 GTCC3 C:US 1:1329 198.86.107/24 GTCC4 C:US 1:1329 198.86.108/24 GTCC5 C:US 1:1329 198.86.109/24 GTCC6 C:US 1:1329 198.86.110/24 GTCC7 C:US 1:1329 198.86.111/24 GTCC8 C:US 1:1329 198.86.112/24 FOR-TCC1 C:US 1:1329 198.86.113/24 FOR-TCC2 C:US 1:1329 198.86.114/24 FOR-TCC3 C:US 1:1329 198.86.115/24 FOR-TCC4 C:US 1:1329 198.86.116/24 FOR-TCC5 C:US 1:1329 198.86.117/24 FOR-TCC6 C:US 1:1329 198.86.118/24 FOR-TCC7 C:US 1:1329 198.86.119/24 FOR-TCC8 C:US 1:1329 198.86.120/24 CARTERETCC1 C:US 1:1329 198.86.121/24 CARTERETCC2 C:US 1:1329 198.86.122/24 CARTERETCC3 C:US 1:1329 198.86.123/24 CARTERETCC4 C:US 1:1329 198.86.124/24 CARTERETCC5 C:US 1:1329 198.86.125/24 CARTERETCC6 C:US 1:1329 198.86.126/24 CARTERETCC7 C:US 1:1329 198.86.127/24 CARTERETCC8 C:US 1:1329 198.96.240/24 GEAC-ONT C:CA 1:1957 198.104.68/24 CWU5 C:US 1:685 2:73 3:101 198.104.69/24 CWU6 C:US 1:685 2:73 3:101 198.104.110/24 CWU47 C:US 1:685 2:73 3:101 198.104.111/24 CWU48 C:US 1:685 2:73 3:101 198.104.120/24 CWU57 C:US 1:685 2:73 3:101 198.104.121/24 CWU58 C:US 1:685 2:73 3:101 198.115.158/24 WSICORP C:US 1:560 2:701 198.148.155/24 MTEL C:US 1:1957 198.154.8/24 AFIC-EMH-C-154-8 C:US 1:19 2:568 198.154.9/24 AFIC-EMH-C-154-9 C:US 1:19 2:568 198.154.10/24 AFIC-EMH-C-154-10 C:US 1:19 2:568 198.178.203/24 KAIWAN-1 C:US 1:1740 198.178.204/24 KAIWAN-NET C:US 1:1740 198.178.205/24 KAIWAN-NET C:US 1:1740 198.178.206/24 KAIWAN-NET C:US 1:1740 198.182.25/24 NASA-PSCNI-NET10 C:US 1:297 2:372 198.187.230/24 TMCNET-C C:US 1:1957 198.252.172/24 NTTC-NET C:US 1:86 2:279 198.252.173/24 NTTC-WASH C:US 1:86 2:279 198.254.11/24 NETBLK-ALC-FUJIKURA C:US 1:1957 198.254.12/24 NETBLK-ALC-FUJIKURA C:US 1:1957 198.254.14/24 NETBLK-ALC-FUJIKURA C:US 1:1957 199.5.238/24 HOPLINK C:US 1:1740 199.10.228/24 CNAP4 C:US 1:19 2:568 199.10.229/24 CNAP4 C:US 1:19 2:568 199.10.230/24 CNAP6 C:US 1:19 2:568 199.45.130/24 NETBLK-COOP-NET C:US 1:1957 199.88.183/24 CCRI C:US 1:701 2:702 199.88.184/24 JOHNSTONHS C:US 1:701 2:702 199.98.96/24 PSINET-C-98-96 C:US 1:2149 2:174 199.98.97/24 PSINET-C-98-97 C:US 1:2149 2:174 199.98.98/24 PSINET-C-98-98 C:US 1:2149 2:174 199.98.135/24 PSINET-C5 C:US 1:2149 2:174 199.98.138/24 PSINET-C5 C:US 1:2149 2:174 199.98.139/24 PSINET-C5 C:US 1:2149 2:174 199.98.140/24 NETBLK-PSINET-C5 C:US 1:1957 199.170.16/24 IIC-NET1 C:US 1:1957 199.199.0/24 ARMADILLO C:US 1:1225 2:267 3:266 4:555 199.225.0/24 CHCS-EGLIN-C-225-0 C:US 1:19 2:568 199.225.1/24 CHCS-EGLIN-C-225-1 C:US 1:19 2:568 199.225.2/24 CHCS-DAVIS-C-225-2 C:US 1:19 2:568 199.225.3/24 CHCS-DAVIS-C-225-3 C:US 1:19 2:568 199.225.4/24 CHCS-SCOTT-C-225-4 C:US 1:19 2:568 199.225.5/24 CHCS-SCOTT-C-225-5 C:US 1:19 2:568 199.225.6/24 CHCS-CORPUS-C-225-6 C:US 1:19 2:568 199.225.7/24 CHCS-CORPUS-C-225-7 C:US 1:19 2:568 199.225.8/24 CHCS-OFFUTT-C-225-8 C:US 1:19 2:568 199.225.9/24 CHCS-OFFUTT-C-225-9 C:US 1:19 2:568 199.225.10/24 CHCS-LEMOORE-C-225-10 C:US 1:19 2:568 199.225.11/24 CHCS-LEMOORE-C-225-11 C:US 1:19 2:568 202.20.16/24 BAE-OZ C:AU 1:372 2:297 202.20.17/24 BAE-OZ C:AU 1:372 2:297 202.20.18/24 BAE-OZ C:AU 1:372 2:297 202.20.19/24 BAE-OZ C:AU 1:372 2:297 202.20.20/24 BAE-OZ C:AU 1:372 2:297 202.20.21/24 BAE-OZ C:AU 1:372 2:297 202.20.22/24 BAE-OZ C:AU 1:372 2:297 202.20.23/24 BAE-OZ C:AU 1:372 2:297 202.20.24/24 BAE-OZ C:AU 1:372 2:297 202.20.25/24 BAE-OZ C:AU 1:372 2:297 202.20.26/24 BAE-OZ C:AU 1:372 2:297 202.20.27/24 BAE-OZ C:AU 1:372 2:297 202.20.28/24 BAE-OZ C:AU 1:372 2:297 202.20.29/24 BAE-OZ C:AU 1:372 2:297 202.20.30/24 BAE-OZ C:AU 1:372 2:297 202.20.31/24 BAE-OZ C:AU 1:372 2:297 202.20.99/24 MOKPO C:KR 1:372 2:297 202.21.8/24 CONNECTIONS-C C:AU 1:372 2:297 202.21.9/24 CONNECTIONS-C C:AU 1:372 2:297 202.21.10/24 CONNECTIONS-C C:AU 1:372 2:297 202.21.11/24 CONNECTIONS-C C:AU 1:372 2:297 202.21.12/24 CONNECTIONS-C C:AU 1:372 2:297 202.21.13/24 CONNECTIONS-C C:AU 1:372 2:297 202.21.14/24 CONNECTIONS-C C:AU 1:372 2:297 202.21.15/24 CONNECTIONS-C C:AU 1:372 2:297 202.30.60/24 NETBLK-KOREA-INET C:KR 1:1957 202.34.17/24 NETBLK-JP-SP-BLOCK C:JP 1:1957 202.48.250/24 SASAKINET C:JP 1:1240 2:1800 203.3.142/24 NEIS-AU C:AU 1:372 2:297 203.3.143/24 AUSHYDRO-AU C:AU 1:372 2:297 203.3.164/24 MHRINET-AU C:AU 1:372 2:297 203.3.165/24 MHRINET-AU C:AU 1:372 2:297 203.3.168/24 KELLOGG-AU C:AU 1:372 2:297 203.3.169/24 KELLOGG-AU C:AU 1:372 2:297 203.3.170/24 KELLOGG-AU C:AU 1:372 2:297 203.3.171/24 KELLOGG-AU C:AU 1:372 2:297 203.3.172/24 KELLOGG-AU C:AU 1:372 2:297 203.3.173/24 KELLOGG-AU C:AU 1:372 2:297 203.3.174/24 KELLOGG-AU C:AU 1:372 2:297 203.3.175/24 KELLOGG-AU C:AU 1:372 2:297 203.3.176/24 NSW-AU C:AU 1:372 2:297 203.3.177/24 NSW-AU C:AU 1:372 2:297 203.3.178/24 NSW-AU C:AU 1:372 2:297 203.3.179/24 NSW-AU C:AU 1:372 2:297 203.3.180/24 NSW-AU C:AU 1:372 2:297 203.3.181/24 NSW-AU C:AU 1:372 2:297 203.3.182/24 NSW-AU C:AU 1:372 2:297 203.3.183/24 NSW-AU C:AU 1:372 2:297 203.3.184/24 NSW-AU C:AU 1:372 2:297 203.3.185/24 NSW-AU C:AU 1:372 2:297 203.3.186/24 NSW-AU C:AU 1:372 2:297 203.3.187/24 NSW-AU C:AU 1:372 2:297 203.3.188/24 NSW-AU C:AU 1:372 2:297 203.3.189/24 NSW-AU C:AU 1:372 2:297 203.3.190/24 NSW-AU C:AU 1:372 2:297 203.3.191/24 NSW-AU C:AU 1:372 2:297 203.4.134/24 LANCORP-AU C:AU 1:372 2:297 203.4.135/24 DPD-VICGOV-AU C:AU 1:372 2:297 Deletions: Expanded listing, sorted by country, then by organization: ========================================================== Australia --------- Australian Hydrographic Office, PO Box 1332, North Sydney, NSW, 2059, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 203.3.143/24 AUSHYDRO-AU (AU) British Aerospace Australia, Technology Park, The Levels, Adelaide, SA, 5095, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 202.20.16/24 BAE-OZ (AU) 202.20.17/24 BAE-OZ (AU) 202.20.18/24 BAE-OZ (AU) 202.20.19/24 BAE-OZ (AU) 202.20.20/24 BAE-OZ (AU) 202.20.21/24 BAE-OZ (AU) 202.20.22/24 BAE-OZ (AU) 202.20.23/24 BAE-OZ (AU) 202.20.24/24 BAE-OZ (AU) 202.20.25/24 BAE-OZ (AU) 202.20.26/24 BAE-OZ (AU) 202.20.27/24 BAE-OZ (AU) 202.20.28/24 BAE-OZ (AU) 202.20.29/24 BAE-OZ (AU) 202.20.30/24 BAE-OZ (AU) 202.20.31/24 BAE-OZ (AU) CONNECT.COM.AU PTY LTD, 29 Fitzgibbon Crescent, Caulfield, VIC, 3161, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ----------- 202.21.8/24 CONNECTIONS-C (AU) 202.21.9/24 CONNECTIONS-C (AU) 202.21.10/24 CONNECTIONS-C (AU) 202.21.11/24 CONNECTIONS-C (AU) 202.21.12/24 CONNECTIONS-C (AU) 202.21.13/24 CONNECTIONS-C (AU) 202.21.14/24 CONNECTIONS-C (AU) 202.21.15/24 CONNECTIONS-C (AU) Department of Planning and Development, Level 3, 477 Collins Street, Melbourne, VIC, 3000, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 203.4.135/24 DPD-VICGOV-AU (AU) Kellogg (Aust.) Pty Ltd, 41-51 Wentworth Avenue, Pagewood, NSW, 2019, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 203.3.168/24 KELLOGG-AU (AU) 203.3.169/24 KELLOGG-AU (AU) 203.3.170/24 KELLOGG-AU (AU) 203.3.171/24 KELLOGG-AU (AU) 203.3.172/24 KELLOGG-AU (AU) 203.3.173/24 KELLOGG-AU (AU) 203.3.174/24 KELLOGG-AU (AU) 203.3.175/24 KELLOGG-AU (AU) Lancorp Pty Ltd, 33 Nott Street, Port Melbourne, VIC, 3207, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 203.4.134/24 LANCORP-AU (AU) Mental Health Research Institute of Victoria, Private Bag 3, Parkville, VIC, 3052, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 203.3.164/24 MHRINET-AU (AU) 203.3.165/24 MHRINET-AU (AU) NSW Department of Courts Administration, ITS Network Group, Level 11, 8-12 Chifley Square, Sydney, NSW, 2001, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 203.3.176/24 NSW-AU (AU) 203.3.177/24 NSW-AU (AU) 203.3.178/24 NSW-AU (AU) 203.3.179/24 NSW-AU (AU) 203.3.180/24 NSW-AU (AU) 203.3.181/24 NSW-AU (AU) 203.3.182/24 NSW-AU (AU) 203.3.183/24 NSW-AU (AU) 203.3.184/24 NSW-AU (AU) 203.3.185/24 NSW-AU (AU) 203.3.186/24 NSW-AU (AU) 203.3.187/24 NSW-AU (AU) 203.3.188/24 NSW-AU (AU) 203.3.189/24 NSW-AU (AU) 203.3.190/24 NSW-AU (AU) 203.3.191/24 NSW-AU (AU) National Electronic Interchange Services Pty Limited, PO Box 6064, North Sydney, NSW, 2060, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 203.3.142/24 NEIS-AU (AU) Canada ------ Geac Computer Corporation, Suite 300, 11 Allstate Parkway, Markham, Ontario L3R 9T8, CANADA 1:1957 ANSCIX-AS ------------- 198.96.240/24 GEAC-ONT (CA) Finland ------- Suomen Tietoverkkopalvelu Inc., P.O. Box 38, SF-00381 Helsinki, FINLAND 1:1957 ANSCIX-AS ------------ 193.199.5/24 EDU-FI (FI) 193.199.47/24 EDU-FI (FI) 193.199.48/24 EDU-FI (FI) 193.199.49/24 EDU-FI (FI) Telecom Finland Ltd, PL 228, 33101 TAMPERE, FINLAND 1:1957 ANSCIX-AS ------------- 193.210.44/24 DATANET (FI) France ------ RENATER GIP, Bat A 7eme etage Universite P. & M. Curie, 4 place Jussieu - 75252 Paris CEDEX, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ------------- 193.55.240/23 RENATER-D-CIDR-1 (FR) Universite de Versailles - Saint Quentin en Yvelines, 45 avenue des Etats-Unis - 78035 Versailles CEDEX, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ------------ 193.51.24/22 FR-UVSQ-CIDR-1 (FR) Germany ------- Markt- und Kuehlhallen AG, Joseph-Dollinger-Bogen 14, D-80807 Muenchen, GERMANY 1:1957 ANSCIX-AS ------------- 193.97.141/24 MUK-ZENTRALE (DE) Hungary ------- Intergraph Hungary Ltd., H-1149 Budapest, Bosnyak ter 5., HUNGARY 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific ------------- 193.224.69/24 INGR-HU (HU) Ireland ------- Murray Telecommunication Limited, 32 Upper Mount Street, Dublin 2, IRELAND 1:1957 ANSCIX-AS -------------- 193.120.205/24 ALD (IE) O'Reilly Institute, Trinity College, Dublin 2, IRELAND 1:1957 ANSCIX-AS -------------- 193.120.241/24 IEUNET-ROUTE3 (IE) 193.120.243/24 IEUNET-ROUTE2 (IE) Japan ----- Japan Network Information Center, c/o Computer Centre, University of Tokyo, Yayoi 2-11-16, Bunkyo-ku, Tokyo 113, JAPAN 1:1957 ANSCIX-AS ------------ 202.34.17/24 NETBLK-JP-SP-BLOCK (JP) NHK Science and Technical Research Laboratories, 1-10-11, Kinuta, Setagaya-ku, Tokyo 157, JAPAN 1:1957 ANSCIX-AS ---------- 133.127/16 NHK-STRL (JP) Sasaki Institute, 2-2 Kanda-Surugadai, Chiyoda-ku, Tokyo 101, JAPAN 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ------------- 202.48.250/24 SASAKINET (JP) Korea, South ------------ Korea Network Information Center, Dept. of Computer Science, Korea Advanced Institute of Science and Technology, 373-1, Yusong-gu, Kusong-dong, Taejon, 305-701, KOREA, REPUBLIC OF 1:1957 ANSCIX-AS ------------ 202.30.60/24 NETBLK-KOREA-INET (KR) Mokpo University, 61, Dorim-ri, Chunggye-myun, Mooan-gun, Chunranam-do, Chonnam, 534-729, KOREA, REPUBLIC OF 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 202.20.99/24 MOKPO (KR) Norway ------ Multix A/S, Lilleakerveien 31, N-0283 Oslo, NORWAY 1:701 Alternet 2:1800 ICM-Atlantic ------------ 193.71.80/24 MULTIX (NO) Russian Federation ------------------ Information and Publishing Dept., Math. Branch Russian Academy of Sciences, Leninsky prosp. 32a, room 2012, Moscow, RUSSIAN FEDERATION 1:1957 ANSCIX-AS -------------- 193.124.248/24 MIAN (RU) South Africa ------------ Netline Computers, P.O.Box 4472, Randburg, 2125, SOUTH AFRICA 1:1957 ANSCIX-AS ---------- 196.7.3/24 NETLINE-SA (ZA) Olivetti Information Technology, P.O.Box 31035, Braamfontein, SOUTH AFRICA 1:1957 ANSCIX-AS ---------- 196.7.5/24 OIT-NET-C (ZA) SQL Integrators (Pty) Ltd, PO Box 5209, Rivonia 2128, SOUTH AFRICA 1:1957 ANSCIX-AS ------------- 192.96.139/24 SQLINT (ZA) UNINET Project, PO Box 2600, Pretoria 0001, SOUTH AFRICA 1:1957 ANSCIX-AS ------------ 196.6.211/24 NETBLK-UNINET-C4 (ZA) Sweden ------ STUPI, Box 9129, S-102 72 Stockholm, SWEDEN 1:1800 ICM-Atlantic 2:1879 EUROPE-RS 3:1133 CERN/DANTE 4:1240 ICM-Pacific -------------- 192.108.196/23 NET-STUPI-B (SE) Ukraine ------- IKO, Ltd, 17a, Geroev Truda st., Kharkov, UKRAINE 1:701 Alternet 2:1800 ICM-Atlantic ------------- 193.124.76/24 IKO-NET (UA) United Kingdom -------------- AWE Eskdalemuir, Blacknest, Brimpton, Reading, RG7 4RS, England, UNITED KINGDOM 1:1957 ANSCIX-AS ------------- 193.39.141/24 BLACKNEST (GB) Apollo Advertising, 21 Macready House, 75 Crawford St,, London W1H 5FH, UNITED KINGDOM 1:1957 ANSCIX-AS -------------- 193.117.180/24 APOLLOADS (GB) Building Research Establishment, Bucknalls Lane, Garston, Watford, UNITED KINGDOM 1:1957 ANSCIX-AS ------------- 193.118.14/24 BRE-UK-NET (GB) Business Objects (UK) Limited, Objects House, Chapel Street, Marlow, Bucks, SL7 1DD, England, UNITED KINGDOM 1:1957 ANSCIX-AS -------------- 193.130.152/24 BUSINESS-OBJECTS (GB) Cambridge Control Ltd, Newton House, Cambridge Business Park, Cambridge, CB4 4WZ, England, UNITED KINGDOM 1:1957 ANSCIX-AS ------------- 193.128.72/24 CAMCONTROL (GB) MAID Systems Limited, 18 Dufferin Street, London, EC1Y 8PD, England, UNITED KINGDOM 1:1957 ANSCIX-AS ------------- 193.130.91/24 MAID (GB) MCB University Press Ltd, 60/62 Toller Lane, Bradford, West Yorks, BD8 9BY, England, UNITED KINGDOM 1:1957 ANSCIX-AS -------------- 193.130.114/24 MCB-NET (GB) Quality Software Products, Talipot House, 5th Avenue Business Park, Gateshead, Tyne & Wear, NE11 0XA, England, UNITED KINGDOM 1:1957 ANSCIX-AS -------------- 193.130.104/24 QSP (GB) Transport and Road Research Laboratory, Old Wokinham Rd., Crowthorne, Berkshire, UK RG11 6AU, UNITED KINGDOM 1:1957 ANSCIX-AS ---------- 159.100/16 TRRLNET (GB) University of Bath, Claverton Down, Bath, AVON, BA2 7AY, UNITED KINGDOM 1:1957 ANSCIX-AS -------------- 193.130.105/24 BATH-COM (GB) United States ------------- AFCSCNET, 102 Hall Blvd, suite 133, San Antonio, TX 78243-7012, USA 1:19 Milnet (FIX-East) 2:568 Milnet (FIX-West) ------------ 198.154.8/24 AFIC-EMH-C-154-8 (US) 198.154.9/24 AFIC-EMH-C-154-9 (US) 198.154.10/24 AFIC-EMH-C-154-10 (US) Advanced Network and Services, Inc., 100 Clearbrook Road, Elmsford, NY 10523, USA 1:1323 ANS Chicago - DNSS 27 ------------- 198.81.213/24 ANS-C-BLOCK (US) Alcoa - Fujikura, 105 Westpark Drive, Suite 200, Brentwood, TN 37027, USA 1:1957 ANSCIX-AS ------------- 198.254.11/24 NETBLK-ALC-FUJIKURA (US) 198.254.12/24 NETBLK-ALC-FUJIKURA (US) 198.254.14/24 NETBLK-ALC-FUJIKURA (US) America Online, 8619 Westwood Center Drive, Vienna, VA 22182, USA 1:1327 ANS Washington D.C. - DNSS 59 2:701 Alternet 3:702 Alternet 4:1329 ANS Greensboro - DNSS 75 ----------- 198.81.1/24 AOL-NET2 (US) American Institute of Physics, 500 Sunnyside Boulevard, Woodbury, NY 11797, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------ 199.98.96/24 PSINET-C-98-96 (US) 199.98.97/24 PSINET-C-98-97 (US) 199.98.98/24 PSINET-C-98-98 (US) Apple OnLine Services, 2600 Napa Valley Corporate Dr, Cupertino, CA 95014, USA 1:1740 CERFnet ------------- 192.215.64/21 NETBLK-CERFNET (US) Armadillo Zoo Software, 1016 Inglehart Ave, St Paul, MN 55104, USA 1:1225 CICNET at Argonne Labs 2:267 CICNET at UIUC 3:266 CICNET at MERIT 4:555 Minnesota Supercomputer Center Network (MSCNet) ------------ 199.199.0/24 ARMADILLO (US) Boeing Computer Support Services, P.O. Box 240010, Marshall Space Flight Center, AL 35812, USA 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) ------------- 198.182.25/24 NASA-PSCNI-NET10 (US) Buffalo & Erie County Public Library, Lafayette Square, Buffalo, NY 14203, USA 1:93 MIDnet -------------- 192.135.227/24 BECPLNET (US) Cape Fear Community College, 411 North Front St., Wilmington, NC 28401, USA 1:1329 ANS Greensboro - DNSS 75 ------------- 198.85.236/24 CAPEFEAR1 (US) 198.85.237/24 CAPEFEAR2 (US) 198.85.238/24 CAPEFEAR3 (US) 198.85.239/24 CAPEFEAR4 (US) 198.85.240/24 CAPEFEAR5 (US) 198.85.241/24 CAPEFEAR6 (US) 198.85.242/24 CAPEFEAR7 (US) 198.85.243/24 CAPEFEAR8 (US) 198.85.244/24 CAPEFEAR9 (US) 198.85.245/24 CAPEFEAR10 (US) 198.85.246/24 CAPEFEAR11 (US) 198.85.247/24 CAPEFEAR12 (US) Carteret Community College, 3505 Arendell Street, Morehead City, NC 28557-2989, USA 1:1329 ANS Greensboro - DNSS 75 ------------- 198.86.120/24 CARTERETCC1 (US) 198.86.121/24 CARTERETCC2 (US) 198.86.122/24 CARTERETCC3 (US) 198.86.123/24 CARTERETCC4 (US) 198.86.124/24 CARTERETCC5 (US) 198.86.125/24 CARTERETCC6 (US) 198.86.126/24 CARTERETCC7 (US) 198.86.127/24 CARTERETCC8 (US) Cedar Bluff Middle School, 707 Cedar Bluff Road, Knoxville, TN 37923, USA 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) ------------ 198.78.43/24 CBMS-GSH-NET-1 (US) Central Washington University, Information Resources, Ellensburg, WA 98926, USA 1:685 NorthWestNet Regional Network 2:73 NorthWestNet Regional Network 3:101 NorthWestNet Regional Network ------------- 198.104.68/24 CWU5 (US) 198.104.69/24 CWU6 (US) 198.104.110/24 CWU47 (US) 198.104.111/24 CWU48 (US) 198.104.120/24 CWU57 (US) 198.104.121/24 CWU58 (US) Christus Rex, Inc., 121 Roundhill Ct, Vallejo, CA 94591, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------ 198.62.75/24 NET-CHRISTUSREX (US) Colorado Internet Cooperative Association, 1495 Canyon Blvd, Suite 35, Boulder, CO 80302, USA 1:1957 ANSCIX-AS ------------- 199.45.130/24 NETBLK-COOP-NET (US) Commander Naval Air Force U.S. Pacific Fleet, BOX 357051, SAN DIEGO, CA 92135-7051, USA 1:19 Milnet (FIX-East) 2:568 Milnet (FIX-West) ------------- 199.10.228/24 CNAP4 (US) 199.10.229/24 CNAP4 (US) 199.10.230/24 CNAP6 (US) Community College of RI, 400 East Avenue, Warwick, RI 02886, USA 1:701 Alternet 2:702 Alternet ------------- 199.88.183/24 CCRI (US) Computer and Business Equipment Manufacturers Association, 1250 I Street, NW, Washington, DC 20005, USA 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) ------------ 198.76.40/24 CBEMA-NET1 (US) Continental Cablevision, 335 Main Street, Reading, MA 01867, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.135/24 PSINET-C5 (US) Davis Montham AFB, 4175 South ST Rd, Davis Montham AFB, AR 85707, USA 1:19 Milnet (FIX-East) 2:568 Milnet (FIX-West) ------------ 199.225.2/24 CHCS-DAVIS-C-225-2 (US) 199.225.3/24 CHCS-DAVIS-C-225-3 (US) Elron Technologies, 462 7th Ave, New York, NY 10018, USA 1:1324 ANS New York City - DNSS 35 ------------- 198.81.200/24 ELRON-DMZ (US) Florida Department of Insurance, 535 john Knox Rd., Tallahassee, FL 32303, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ---------- 158.229/16 FLINS (US) Forsyth Technical Community College, 2100 Silas Creek Parkway, Winston-Salem, NC 27103, USA 1:1329 ANS Greensboro - DNSS 75 ------------- 198.86.112/24 FOR-TCC1 (US) 198.86.113/24 FOR-TCC2 (US) 198.86.114/24 FOR-TCC3 (US) 198.86.115/24 FOR-TCC4 (US) 198.86.116/24 FOR-TCC5 (US) 198.86.117/24 FOR-TCC6 (US) 198.86.118/24 FOR-TCC7 (US) 198.86.119/24 FOR-TCC8 (US) GEC Systems, 150 Parish Drive, Wayne, NJ 07474, USA 1:1957 ANSCIX-AS ------------ 198.6.251/24 GEC (US) Guilford Technical Community College, Post Office Box 309, Jamestown, NC 27282, USA 1:1329 ANS Greensboro - DNSS 75 ------------- 198.86.104/24 GTCC1 (US) 198.86.105/24 GTCC2 (US) 198.86.106/24 GTCC3 (US) 198.86.107/24 GTCC4 (US) 198.86.108/24 GTCC5 (US) 198.86.109/24 GTCC6 (US) 198.86.110/24 GTCC7 (US) 198.86.111/24 GTCC8 (US) Hewlett Packard Company, 19420 Homestead Road, Cuptertino, CA 95014, USA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------- 192.69.116/24 HPS (US) HopLink, 7867 Rancho Fanita Drive, #E, Santee, CA 92071-3364, USA 1:1740 CERFnet ------------ 199.5.238/24 HOPLINK (US) Hybrid Networks, Inc., 20863 Stevens Creek Blvd, Suite 300, Cupertino, CA 95014-2116, USA 1:1957 ANSCIX-AS ------------ 198.13.20/24 HYBRID-3-20 (US) IBM Corporation, 1000 River Street, Essex Junction, VT 05452, USA 1:1326 ANS Hartford - DNSS 51 ------------- 192.91.197/24 IBMNERBTV06 (US) Indepth Data Inc., 20 N. Broadway, Suite 1000, Oklahoma City, OK 73102, USA 1:1957 ANSCIX-AS --------- 160.65/16 IDI2 (US) Indotronix International Corporation, 331 Main Mall, Suite 108, Poughkeepsie, NY 12601, USA 1:1957 ANSCIX-AS ------------- 199.170.16/24 IIC-NET1 (US) Information Management Consultants, 7915 Westpark Drive, McLean, VA 22102, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.139/24 PSINET-C5 (US) Institute for Academic Technology, 2525 Meridian Parkway, Durham, NC 27713, USA 1:1329 ANS Greensboro - DNSS 75 ------------- 198.85.113/24 IAT3-NET (US) Interop Show Network, Las Vegas Convention Center, 3150 S. Paradise Rd., Las Vegas, NV 89109, USA 1:200 BARRNet 2:201 BARRNet ---- 45/8 SHOWNETA (US) Johnston High School, 345 Cherry Hill Road, Johnston, RI 02919, USA 1:701 Alternet 2:702 Alternet ------------- 199.88.184/24 JOHNSTONHS (US) KAIWAN Corporation, 13442 Coast Street, Garden Grove, CA 92644, USA 1:1740 CERFnet -------------- 198.178.203/24 KAIWAN-1 (US) 198.178.204/24 KAIWAN-NET (US) 198.178.205/24 KAIWAN-NET (US) 198.178.206/24 KAIWAN-NET (US) Los Angeles Times, Publishing Systems Department, Times-Mirror Square, Los Angeles, CA 90053, USA 1:1957 ANSCIX-AS ---------- 144.142/16 TIMESNET (US) Los Angeles Times, Times-Mirror Square, Los Angeles, CA 90053, USA 1:1957 ANSCIX-AS ------------- 192.187.65/24 LATIMES-2 (US) 192.187.66/24 LATIMES-3 (US) 192.187.67/24 LATIMES-4 (US) 192.187.68/24 LATIMES-5 (US) 192.187.69/24 LATIMES-6 (US) 192.187.70/24 LATIMES-7 (US) 192.187.71/24 LATIMES-8 (US) 192.187.72/24 LATIMES-9 (US) 192.187.73/24 LATIMES-10 (US) 192.187.74/24 LATIMES-11 (US) 192.187.75/24 LATIMES-12 (US) 192.187.76/24 LATIMES-13 (US) 192.187.77/24 LATIMES-14 (US) 192.187.78/24 LATIMES-15 (US) 192.187.79/24 LATIMES-16 (US) 192.187.80/24 LATIMES-17 (US) 192.187.81/24 LATIMES-18 (US) 192.187.82/24 LATIMES-19 (US) 192.187.83/24 LATIMES-20 (US) 192.187.84/24 LATIMES-21 (US) 192.187.85/24 LATIMES-22 (US) 192.187.86/24 LATIMES-23 (US) 192.187.87/24 LATIMES-24 (US) 192.187.88/24 LATIMES-25 (US) 192.187.89/24 LATIMES-26 (US) 192.187.90/24 LATIMES-27 (US) 192.187.91/24 LATIMES-28 (US) 192.187.92/24 LATIMES-29 (US) 192.187.93/24 LATIMES-30 (US) 192.187.94/24 LATIMES-31 (US) 192.187.95/24 LATIMES-32 (US) Louisburg College, 502 North Main Street, Louisburg, NC 27549-7704, USA 1:1329 ANS Greensboro - DNSS 75 ------------- 198.85.248/24 LOUISBURG1 (US) 198.85.249/24 LOUISBURG2 (US) 198.85.250/24 LOUISBURG3 (US) 198.85.251/24 LOUISBURG4 (US) 198.85.252/24 LOUISBURG5 (US) 198.85.253/24 LOUISBURG6 (US) 198.85.255/24 LOUISBURG8 (US) Med Hospital Offutt AFB, 2501 Capehart Road - GI12, Offutt AFB, NE 68113-2160, USA 1:19 Milnet (FIX-East) 2:568 Milnet (FIX-West) ------------ 199.225.8/24 CHCS-OFFUTT-C-225-8 (US) 199.225.9/24 CHCS-OFFUTT-C-225-9 (US) Michigan Department of Transportation, 425 West Ottawa, Lansing, MI 48933, USA 1:237 MichNet (MERIT) 2:233 UMnet (University of Michigan) 3:266 CICNET at MERIT 4:267 CICNET at UIUC 5:1225 CICNET at Argonne Labs ---------- 136.181/16 MICHTRANS-NET (US) Mtel Technologies, Inc., 188 E. Capitol, Suite 1450, Jackson, MS 39201, USA 1:1957 ANSCIX-AS -------------- 198.148.155/24 MTEL (US) Murphy & Durieu Data Systems, 120 Broadway, 17th Floor, New York, NY 10271, USA 1:701 Alternet 2:702 Alternet ------------ 198.6.204/24 MURPHY-NET (US) 198.6.205/24 MURPHY-NET (US) 198.6.206/24 MURPHY-NET (US) 198.6.207/24 MURPHY-NET (US) National Archives and Records Administration, 8601 Adelphi Road, College Park, MD 20740-6001, USA 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) ------------- 198.76.128/24 NARA-NET3 (US) 198.76.129/24 NARA-NET4 (US) 198.76.130/24 NARA-NET5 (US) 198.76.131/24 NARA-NET6 (US) 198.76.132/24 NARA-NET7 (US) 198.76.133/24 NARA-NET8 (US) 198.76.134/24 NARA-NET9 (US) 198.76.135/24 NARA-NET10 (US) 198.76.136/24 NARA-NET11 (US) 198.76.137/24 NARA-NET12 (US) 198.76.138/24 NARA-NET13 (US) 198.76.139/24 NARA-NET14 (US) 198.76.140/24 NARA-NET15 (US) 198.76.141/24 NARA-NET16 (US) 198.76.142/24 NARA-NET17 (US) 198.76.143/24 NARA-NET18 (US) 198.76.144/24 NARA-NET19 (US) 198.76.145/24 NARA-NET20 (US) 198.76.146/24 NARA-NET21 (US) 198.76.147/24 NARA-NET22 (US) 198.76.148/24 NARA-NET23 (US) 198.76.149/24 NARA-NET24 (US) 198.76.150/24 NARA-NET25 (US) 198.76.151/24 NARA-NET26 (US) 198.76.152/24 NARA-NET27 (US) 198.76.153/24 NARA-NET28 (US) 198.76.154/24 NARA-NET29 (US) 198.76.155/24 NARA-NET30 (US) 198.76.156/24 NARA-NET31 (US) 198.76.157/24 NARA-NET32 (US) 198.76.158/24 NARA-NET33 (US) 198.76.159/24 NARA-NET34 (US) National Technology Transfer Center, Wheeling Jesuit College, 200 MT Dechantal Rd., Wheeling, WV 26003, USA 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) -------------- 198.252.172/24 NTTC-NET (US) 198.252.173/24 NTTC-WASH (US) Naval Hospital Corpus Christi, 10651 E. ST, Corpus Christi, TX 78419, USA 1:19 Milnet (FIX-East) 2:568 Milnet (FIX-West) ------------ 199.225.4/24 CHCS-SCOTT-C-225-4 (US) 199.225.5/24 CHCS-SCOTT-C-225-5 (US) 199.225.6/24 CHCS-CORPUS-C-225-6 (US) 199.225.7/24 CHCS-CORPUS-C-225-7 (US) Naval Hospital Lemoore, MD/CHCS Building # 930, Lemoore, CA 93246-5004, USA 1:19 Milnet (FIX-East) 2:568 Milnet (FIX-West) ------------- 199.225.10/24 CHCS-LEMOORE-C-225-10 (US) 199.225.11/24 CHCS-LEMOORE-C-225-11 (US) Naval Weapons Station, Code 032, Yorktown, VA 23691-5000, USA 1:19 Milnet (FIX-East) 2:568 Milnet (FIX-West) --------- 144.18/16 YKTNPOE-GW1 (US) Network Systems Laboratory Digital, 505 Hamilton Ave, Palo Alto, CA 94301, USA 1:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 2:210 Westnet Regional Network (Utah Attachment) - ENSS 142 ------------- 192.208.38/24 DEC-EXTERNAL (US) Northeast Utilities Service Company, Wethersfield, CT 06109-1698, USA 1:560 NEARnet Regional Network 2:701 Alternet --------- 170.55/16 NAESCO (US) PIX Technologies Corporation, 14703-E Baltimore Avenue, Suite 238, Laurel, MD 20707, USA 1:701 Alternet 2:702 Alternet ----------- 198.84.4/22 WDC-PUBNIX1 (US) Performance Systems International, Inc., 510 Huntmar Park Drive, Herndon, VA 22070, USA 1:1957 ANSCIX-AS ------------- 199.98.140/24 NETBLK-PSINET-C5 (US) Pfeiffer College, Post Office Box 3294, Misenheimer, NC 28109, USA 1:1329 ANS Greensboro - DNSS 75 ------------- 198.85.220/24 PFEIFFER1 (US) 198.85.221/24 PFEIFFER2 (US) 198.85.222/24 PFEIFFER3 (US) 198.85.223/24 PFEIFFER4 (US) 198.85.224/24 PFEIFFER5 (US) 198.85.225/24 PFEIFFER6 (US) 198.85.226/24 PFEIFFER7 (US) 198.85.227/24 PFEIFFER8 (US) 198.85.228/24 PFEIFFER9 (US) 198.85.229/24 PFEIFFER10 (US) 198.85.230/24 PFEIFFER11 (US) 198.85.231/24 PFEIFFER12 (US) 198.85.232/24 PFEIFFER13 (US) 198.85.233/24 PFEIFFER14 (US) 198.85.234/24 PFEIFFER15 (US) 198.85.235/24 PFEIFFER16 (US) Professional Examination Service, 475 Riverside Dr., 7th Floor, New York, NY 10115, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.138/24 PSINET-C5 (US) Times-Mirror Corporation, Times-Mirror Square, Los Angeles, CA 90053, USA 1:1957 ANSCIX-AS -------------- 198.187.230/24 TMCNET-C (US) U.S. General Accounting Office, 441 G Street NW, Room 2840-A, Washington, DC 20548, USA 1:1957 ANSCIX-AS ---------- 161.203/16 GAO (US) USAF Regional Hospital Eglin, Buliding 2833, Eglin AFB, FL 32542-4300, USA 1:19 Milnet (FIX-East) 2:568 Milnet (FIX-West) ------------ 199.225.0/24 CHCS-EGLIN-C-225-0 (US) 199.225.1/24 CHCS-EGLIN-C-225-1 (US) UUNET Technologies, 3110 Fairview Park Drive, Suite 570, Falls Church, VA 22042, USA 1:1957 ANSCIX-AS ------------ 198.6.197/24 NETBLK-UUNETCBLK6 (US) 198.6.232/24 NETBLK-UUNETCBLK6 (US) 198.6.233/24 NETBLK-UUNETCBLK6 (US) 198.6.234/24 NETBLK-UUNETCBLK6 (US) 198.6.235/24 NETBLK-UUNETCBLK6 (US) 198.6.236/24 NETBLK-UUNETCBLK6 (US) 198.6.237/24 NETBLK-UUNETCBLK6 (US) 198.6.238/24 NETBLK-UUNETCBLK6 (US) 198.6.239/24 NETBLK-UUNETCBLK6 (US) 198.6.240/24 NETBLK-UUNETCBLK6 (US) 198.6.241/24 NETBLK-UUNETCBLK6 (US) 198.6.242/24 NETBLK-UUNETCBLK6 (US) 198.6.243/24 NETBLK-UUNETCBLK6 (US) WSI Corporation, 4 Federal Street, Billerica, MA 01821, USA 1:560 NEARnet Regional Network 2:701 Alternet -------------- 198.115.158/24 WSICORP (US) Wake Area Health Education Center, 3000 Newburne Avenue, Raleigh, NC 27610, USA 1:1329 ANS Greensboro - DNSS 75 ------------- 198.85.114/24 WAHEC1-NET (US) Westnet, 3645 Marine Street, U. of Colorado, Boulder, CO 80309-0455, USA 1:210 Westnet Regional Network (Utah Attachment) - ENSS 142 2:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 ------------- 198.60.189/24 WESTNET (US) ========================================================== 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.t3p Information is also avaiable through the PRDB whois server. Type "whois -h prdb.merit.edu help" for details. -------------------------------------------------------------------------- REPORT CHANGES: (Updated March 24, 1994) Metric:AS(NSS) - Historically, peer networks with multiple connections to AS 690 could only select which of those connections their networks would take by creating "Fake" AS numbers, and using those in the PRDB Metric:AS announcement lists. Some time in the next few weeks we will begin supporting an expanded syntax, where the AS may be followed by an optional NSS peer number in parentheses. Eventually, this syntax will be used to replace most or all of the current Fake ASs. This change will affect *all* places that the announcement lists are reported: all whois queries, all network reports, this "NWG" report, and the Auto-NACR. If you have code which parses these announcement lists, please be aware that that code may need modifications soon. CIDR Reports: There is a new "whois" option to list aggregates in the PRDB: whois -h prdb.merit.edu listaggs will produce a listing of the currently registered aggregates. There is also a new report on "nestings" of PRDB-registered aggregates with their more specific routes: nets.non-classful. Anyone considering configuring an aggregate into the PRDB (and you all should be!) is encouraged to pre-check that aggregate by typing the command: whois -h prdb.merit.edu 'aggchk ' (where "" is the aggregate description). This command will list all of the other entries in the PRDB that are more specific routes of , as well as any aggregates all ready configured that contain . The output includes the AUP and announcement lists of each of the nets printed, with discrepancies flagged. This is the same program that we use for sanity-checking the NACRs that you submit. The archived discussion list "db-disc@merit.edu" exists for discussion of PRDB issues. Send a message to "db-disc-request@merit.edu" to subscribe. --Dale Johnson (dsj@merit.edu) -------------------------------------------------------------------------- Please send all requests for configuration changes to nsfnet-admin@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. ******************************* --Steve Widmayer Merit/NSFNET skw@merit.edu --Enke Chen Merit/NSFNET enke@merit.edu --Steven J. Richardson Merit/NSFNET sjr@merit.edu - - - - - - - - - - - - - - - - - From list-admin Wed Apr 6 13:01:03 1994 Received: from cert.org (cert.org [192.88.209.5]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id NAA03079 for ; Wed, 6 Apr 1994 13:00:44 -0400 Received: from clorets.cert.org by cert.org (4.1/cert-5.2) id AA00341; Wed, 6 Apr 94 12:53:21 EDT Received: by clorets.cert.org (5.65/2.5) id AA02442; Wed, 6 Apr 94 12:52:40 -0400 Message-Id: <9404061652.AA02442@clorets.cert.org> From: CERT Advisory Date: Wed, 6 Apr 94 12:51:16 EDT To: cert-advisory@cert.org Subject: CERT Advisory - wuarchive ftpd Trojan Horse Organization: Computer Emergency Response Team : 412-268-7090 ============================================================================= CA-94:07 CERT Advisory April 6, 1994 wuarchive ftpd Trojan Horse ----------------------------------------------------------------------------- The CERT Coordination Center has received confirmation that some copies of the source code for the wuarchive FTP daemon (ftpd) were modified by an intruder, and contain a Trojan horse. We strongly recommend that any site running the wuarchive ftpd take steps to immediately install version 2.3, or disable their FTP daemon. ----------------------------------------------------------------------------- I. Description Some copies of the source code for versions 2.2 and 2.1f of the wuarchive ftpd were modified by an intruder, and contain a Trojan horse. If your FTP daemon was compiled from the intruder-modified source code, you are vulnerable. It is possible that previous versions of the source code for the server were modified in a similar manner. If you are running the wuarchive ftpd, but not providing anonymous FTP access, you are still vulnerable to this Trojan horse. II. Impact An intruder can gain root access on a host running an FTP daemon that contains this Trojan horse. III. Solution We strongly recommend that any site running the wuarchive ftpd (version 2.2 or earlier) take steps to immediately install version 2.3. If you cannot install the new version in a timely manner, you should disable FTP service. It is not sufficient to disable anonymous FTP. You must disable the FTP daemon. Sites can obtain version 2.3 via anonymous FTP from ftp.uu.net, in the "/networking/ftp/wuarchive-ftpd" directory. We recommend that you turn off your FTP server until you have installed the new version. Be certain to verify the checksum information to confirm that you have retrieved a valid copy. BSD SVR4 File Checksum Checksum MD5 Digital Signature ----------------- -------- --------- -------------------------------- wu-ftpd-2.3.tar.Z 24416 181 30488 361 e58adc5ce0b6eae34f3f2389e9dc9197 --------------------------------------------------------------------------- The CERT Coordination Center wishes to thank Bryan O'Connor and Chris Myers of Washington University in St. Louis for their invaluable assistance in resolving this problem. CERT also gratefully acknowledges the help of Neil Woods and Karl Strickland. --------------------------------------------------------------------------- If you believe that your system has been compromised, contact the CERT Coordination Center or your representative in the Forum of Incident Response and Security Teams (FIRST). If you wish to send sensitive incident or vulnerability information to CERT via electronic mail, CERT strongly advises that the e-mail be encrypted. CERT can support a shared DES key, PGP (public key available via anonymous FTP on info.cert.org), or PEM (contact CERT for details). Internet E-mail: cert@cert.org Telephone: 412-268-7090 (24-hour hotline) CERT personnel answer 8:30 a.m.-5:00 p.m. EST(GMT-5)/EDT(GMT-4), and are on call for emergencies during other hours. CERT Coordination Center Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213-3890 Past advisories, information about FIRST representatives, and other information related to computer security are available via anonymous FTP from info.cert.org. - - - - - - - - - - - - - - - - - From list-admin Thu Apr 7 10:13:13 1994 Received: from interlock.ans.net (interlock.ans.net [147.225.1.3]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id KAA02385; Thu, 7 Apr 1994 10:13:12 -0400 Received: by interlock.ans.net id AA13703 (InterLock SMTP Gateway 1.1); Thu, 7 Apr 1994 10:13:11 -0400 Received: by interlock.ans.net (Internal Mail Agent-2); Thu, 7 Apr 1994 10:13:11 -0400 Received: by interlock.ans.net (Internal Mail Agent-1); Thu, 7 Apr 1994 10:13:11 -0400 Date: Thu, 7 Apr 94 10:10:13 EDT From: "John J. Hedderman (ANS Install Eng)" To: bgpd@merit.edu, regional-techs@merit.edu Subject: CIX-ANS path fully CIDR capable Message-Id: Hello, With the completion of the CIX-West router upgrade this Tuesday morning, the CIX is now speaking BGP4 with ANS (enss187.) Since enss187 is also speaking BGP4 with the ANSNET backbone, this entire path is now CIDR capable. At the moment, enss187 is hearing a number of aggregate routes from the CIX, but none from the ANSNET backbone. Those CIX-member regionals using ANS CO+RE as transit to the CIX may now pass aggregates on to the ANSNET backbone, and thereon to the CIX through enss187, if they require this. I do not see that any of these regionals, which include NEARNet, SURANet, WestNet and NorthWestNet, have begun announcing aggregates to ANSNET yet. In case this is of any importance, the current set of aggregates enss187 is hearing from the CIX numbers 31 routes, and is as follows: Network Next Hop Metric LocPrf Weight Path *> 192.36.32.0/22 149.20.5.1 0 1280 701 1729 2865 i *> 192.121.64.0/23 149.20.5.1 0 1280 701 1729 ? *> 192.135.240.0/21 149.20.5.1 0 1280 200 109 i *> 192.150.56.0/21 149.20.5.1 0 1280 701 1729 ? *> 192.150.64.0/20 149.20.5.1 0 1280 701 1729 ? *> 192.150.80.0/21 149.20.5.1 0 1280 701 1729 ? *> 192.165.148.0/22 149.20.5.1 0 1280 701 1729 2865 i *> 192.212.0.0/16 149.20.5.1 0 1280 1740 i *> 192.216.0.0/16 149.20.5.1 0 1280 200 i *> 192.244.176.0/20 149.20.5.1 0 1280 701 2509 2497 i *> 193.10.16.0/21 149.20.5.1 0 1280 701 1729 2865 i *> 193.10.24.0/22 149.20.5.1 0 1280 701 1729 2865 i *> 193.44.0.0/16 149.20.5.1 0 1280 701 1729 ? *> 193.44.76.0/22 149.20.5.1 0 1280 701 1729 2865 i *> 193.128.40.0/21 149.20.5.1 0 1280 701 1849 i *> 198.30.0.0/16 149.20.5.1 0 1280 1239 600 i *> 198.31.0.0/16 149.20.5.1 0 1280 200 i *> 198.84.4.0/22 149.20.5.1 0 1280 701 ? *> 198.92.0.0/17 149.20.5.1 0 1280 1740 109 i *> 198.93.160.0/19 149.20.5.1 0 1280 1740 109 i *> 198.234.0.0/16 149.20.5.1 0 1280 1239 600 i *> 199.0.0.0/16 149.20.5.1 0 1280 1239 i *> 199.1.0.0/16 149.20.5.1 0 1280 1239 i *> 199.2.0.0/16 149.20.5.1 0 1280 1239 i *> 199.3.0.0/16 149.20.5.1 0 1280 1239 i *> 199.18.0.0/16 149.20.5.1 0 1280 1239 600 i *> 199.108.0.0/16 149.20.5.1 0 1280 1740 i *> 199.182.0.0/16 149.20.5.1 0 1280 2551 i *> 202.24.208.0/20 149.20.5.1 0 1280 701 2509 2497 i *> 202.26.0.0/18 149.20.5.1 0 1280 701 2509 2497 i *> 202.32.0.0/16 149.20.5.1 0 1280 701 2509 2497 i I checked this yesterday as well, at which time the following additional 38 aggregates were being learned from CIX-West. I'm not sure where they disappeared to... Network Next Hop Metric LocPrf Weight Path *> 192.64.100.0/22 149.20.5.1 0 1280 701 286 1891 ? *> 192.78.186.0/23 149.20.5.1 0 1280 701 286 1891 ? *> 192.92.130.0/23 149.20.5.1 0 1280 701 286 1891 i *> 192.122.216.0/23 149.20.5.1 0 1280 701 286 2110 i *> 192.122.220.0/22 149.20.5.1 0 1280 701 286 2110 i *> 192.250.24.0/22 149.20.5.1 0 1280 701 286 1890 i *> 193.67.128.0/22 149.20.5.1 0 1280 701 286 1890 i *> 193.71.32.0/21 149.20.5.1 0 1280 701 286 2116 i *> 193.71.104.0/21 149.20.5.1 0 1280 701 286 2116 i *> 193.71.160.0/21 149.20.5.1 0 1280 701 286 2116 i *> 193.72.0.0/16 149.20.5.1 0 1280 701 286 1836 ? *> 193.74.160.0/20 149.20.5.1 0 1280 701 286 1891 ? *> 193.74.176.0/23 149.20.5.1 0 1280 701 286 1891 ? *> 193.74.192.0/22 149.20.5.1 0 1280 701 286 1891 i *> 193.74.200.0/23 149.20.5.1 0 1280 701 286 1891 i *> 193.74.232.0/21 149.20.5.1 0 1280 701 286 1891 i *> 193.74.240.0/20 149.20.5.1 0 1280 701 286 1891 ? *> 193.78.32.0/21 149.20.5.1 0 1280 701 286 1890 i *> 193.78.72.0/22 149.20.5.1 0 1280 701 286 1890 i *> 193.78.104.0/22 149.20.5.1 0 1280 701 286 1890 i *> 193.78.120.0/23 149.20.5.1 0 1280 701 286 1890 i *> 193.78.120.0/21 149.20.5.1 0 1280 701 286 1890 i *> 193.80.224.0/22 149.20.5.1 0 1280 701 286 1901 i *> 193.85.0.0/21 149.20.5.1 0 1280 701 286 2819 i *> 193.85.8.0/23 149.20.5.1 0 1280 701 286 2819 i *> 193.85.80.0/23 149.20.5.1 0 1280 701 286 2819 i *> 193.85.104.0/21 149.20.5.1 0 1280 701 286 2819 i *> 193.85.112.0/20 149.20.5.1 0 1280 701 286 2819 i *> 193.85.128.0/20 149.20.5.1 0 1280 701 286 2819 i *> 193.120.16.0/20 149.20.5.1 0 1280 701 286 2110 i *> 193.120.32.0/21 149.20.5.1 0 1280 701 286 2110 i *> 193.120.208.0/22 149.20.5.1 0 1280 701 286 2110 i *> 193.120.212.0/22 149.20.5.1 0 1280 701 286 2110 i *> 193.120.216.0/23 149.20.5.1 0 1280 701 286 2110 i *> 193.120.232.0/21 149.20.5.1 0 1280 701 286 2110 i *> 193.120.240.0/21 149.20.5.1 0 1280 701 286 2110 i *> 193.242.80.0/21 149.20.5.1 0 1280 701 286 i *> 199.0.192.0/20 149.20.5.1 0 1280 1239 ? - John - - - - - - - - - - - - - - - - - From list-admin Thu Apr 7 11:38:30 1994 Received: from nic.near.net (nic.near.net [192.52.71.4]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id LAA09651; Thu, 7 Apr 1994 11:38:28 -0400 Received: from fedney.near.net by nic.near.net id aa09167; 7 Apr 94 11:38 EDT To: "John J. Hedderman (ANS Install Eng)" cc: bgpd@merit.edu, regional-techs@merit.edu Subject: Re: CIX-ANS path fully CIDR capable In-reply-to: Your message of Thu, 07 Apr 1994 10:10:13 -0400. Date: Thu, 07 Apr 1994 11:38:24 -0400 Message-ID: <4895.765733104@nic.near.net> From: "L. Sean Kennedy" From: "John J. Hedderman (ANS Install Eng)" Subject: CIX-ANS path fully CIDR capable Date: Thu, 7 Apr 94 10:10:13 EDT > At the moment, enss187 is hearing a number of aggregate routes from the > CIX, but none from the ANSNET backbone. Those CIX-member regionals > using ANS CO+RE as transit to the CIX may now pass aggregates on to the > ANSNET backbone, and thereon to the CIX through enss187, if they require > this. I do not see that any of these regionals, which include NEARNet, > SURANet, WestNet and NorthWestNet, have begun announcing aggregates to > ANSNET yet. This is very good news! I am trying to get a NACR in for Noon for the block 192.32/16. This will only save about 53 routes currently, but if this is determined a success we will add more aggregates on Tuesday. (I need to double check on the AUP stuff, and next hop; since our assigned blocks try to, but do not necessarily follow AUP boundaries.) I don't think it is suprising that ANSNET has not heard aggregates. We certainly were not willing to send them while you couldn't pass them to the CIX, and blackhole our customers traffic. Tuesday was when this was corrected, and Friday is the next configuration window after that-- you should see some aggregates tomorrow. Perhaps since gated does dynamic configs, ANS/MERIT could offer special windows for block additions until the ball gets rolling. Sean - - - - - - - - - - - - - - - - - From list-admin Fri Apr 8 08:59:23 1994 Received: (skw@localhost) by merit.edu (8.6.8.1/merit-1.0) id IAA13061 for regional-techs; Fri, 8 Apr 1994 08:59:23 -0400 Date: Fri, 8 Apr 1994 08:59:23 -0400 From: "Steven K. Widmayer" Message-Id: <199404081259.IAA13061@merit.edu> To: regional-techs Subject: NSFNET/ANSnet routing configuration update delayed... Hi. Today's NSFNET/ANSnet routing configuration update has been delayed due to some problems in generating the new configuration files. We have decided to go ahead with the update later this morning. Since we have dynamic reconfig capability with gated, the updates will be non-disruptive. I expect the updates will be done by 11:00 EDT. --Steve Widmayer / Merit - - - - - - - - - - - - - - - - - From list-admin Fri Apr 8 10:53:40 1994 Received: (skw@localhost) by merit.edu (8.6.8.1/merit-1.0) id KAA23878 for nwg; Fri, 8 Apr 1994 10:53:40 -0400 Date: Fri, 8 Apr 1994 10:53:40 -0400 From: "Steven K. Widmayer" Message-Id: <199404081453.KAA23878@merit.edu> To: nwg Subject: Additions to the NSFNET policy-based routing database ------------------------------------------------------------------------------ New format for Metric:AS lists coming later in this and all reports. See 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 Configured Networks 29243 = 29 4605 24520 89 Added Networks 216 = 0 10 181 25 Deleted Networks 25 = 0 0 25 0 IP address Net name Country Priority:AS ---------- -------- ------- ----------- 142.98/16 DOEWAN2 C:CA 1:603 2:601 3:602 142.212/16 INACW C:CA 1:601 2:603 3:602 146.241/16 MAXUS C:US 1:2149 2:174 147.74/16 CAPE C:US 1:297 2:372 156.76/16 WEPCO C:US 1:2149 2:174 158.36/14 UNINETT1-CIDR C:NO 1:1800 2:1879 3:1133 4:1240 162.52/16 PETROINFO C:US 1:2551 163.205/16 NASA3 C:US 1:297 2:372 163.206/16 NASA4 C:US 1:297 2:372 168.84/16 GI-B C:US 1:2386 2:1321 168.119/16 GCTI-B C:US 1:560 2:701 192.4.139/24 BELLCORE-UNUSED C:US 1:1957 192.5.93/24 SRI-DEMO C:US 1:200 2:201 192.32/16 WELLFLEET-C-BLOCK C:US 1:560 2:701 192.36.32/24 UPPSALA-L1 C:SE 1:1957 192.50.189/24 TOSHIBA-NET1 C:JP 1:1240 2:1800 192.77.42/24 NASA-KSC16 C:US 1:297 2:372 192.77.60/24 CRIM-CNET12 C:CA 1:603 2:601 3:602 192.89.240/24 LINTURI1 C:FI 1:701 2:1800 192.89.241/24 LINTURI2 C:FI 1:701 2:1800 192.138.162/24 INFOSWITCH1 C:US 1:2149 2:174 192.147.160/20 NWNET10 C:US 1:685 2:73 3:101 192.148.157/24 TELECOM-C C:AU 1:372 2:297 192.150.52/22 SSW2-5 C:US 1:204 2:1206 192.157.67/24 ICMNET-4 C:CO 1:1800 2:1240 192.165.148/24 SE-AS-MED C:SE 1:1957 192.204/16 NETBLK-PREPNET-C C:US 1:204 2:1206 192.208.34/24 DEC-EXTERNAL C:US 1:701 2:702 192.220/16 NETBLK-NWNET C:US 1:685 2:73 3:101 192.245.136/24 WRLCNET C:US 1:86 2:279 192.253.70/24 DSI-NET70 C:US 1:274 2:60 193.8.2/24 BERNER-BLOCK-8 C:CH 1:1957 193.10.16/24 SE-AS-LAN C:SE 1:1957 193.10.24/24 SE-AS-LAN C:SE 1:1957 193.10.127/24 SE-AKADEM-MTA C:SE 1:1957 193.31.10/24 SOFTCON-MUC C:DE 1:701 2:1800 193.31.11/24 SOFTCON-MUC C:DE 1:701 2:1800 193.40.226/24 ENMB-NET-C-40-226 C:EE 1:1800 2:1879 3:1133 4:1240 193.40.227/24 ENMB-NET-C-40-227 C:EE 1:1800 2:1879 3:1133 4:1240 193.40.228/24 ENMB-NET-C-40-228 C:EE 1:1800 2:1879 3:1133 4:1240 193.44.76/24 UDAC-SERVER C:SE 1:1957 193.48.2/24 FR-OR-VETONA C:FR 1:1800 2:1240 3:1133 4:1674 193.48.172/24 FR-ENSAE01 C:FR 1:1800 2:1240 3:1133 4:1674 193.50.222/24 FR-PICTEL02 C:FR 1:1800 2:1240 3:1133 4:1674 193.50.223/24 FR-PICTEL03 C:FR 1:1800 2:1240 3:1133 4:1674 193.50.252/24 FR-PICTEL04 C:FR 1:1800 2:1240 3:1133 4:1674 193.50.253/24 FR-PICTEL05 C:FR 1:1800 2:1240 3:1133 4:1674 193.70.236/24 SODALIA-NET C:IT 1:1957 193.70.237/24 SODALIA-NET C:IT 1:1957 193.74.232/24 EUNET-BE C:BE 1:1957 193.74.240/24 COIBE C:BE 1:1957 193.80.234/24 PM-DATA C:AT 1:701 2:1800 193.120.232/24 FEXCO2 C:IE 1:1957 193.125.158/24 EXPO C:RU 1:701 2:1800 193.128.40/24 PIPEX-INTERAS C:GB 1:1957 193.128.77/24 HCS C:GB 1:1800 2:1240 193.136.48/24 INESCP-NET-SUPER C:PT 1:1800 2:1133 3:1240 193.136.49/24 INESCP-NET-SUPER C:PT 1:1800 2:1133 3:1240 193.136.50/24 INESCP-NET-SUPER C:PT 1:1800 2:1133 3:1240 193.136.52/24 INESCP-NET-SUPER C:PT 1:1800 2:1133 3:1240 193.136.144/24 ISEG-1 C:PT 1:1800 2:1133 3:1240 193.141.104/24 INDIVIDUAL-NET C:DE 1:1324 2:1800 3:1240 4:1133 193.141.230/24 THESYS-NET3 C:DE 1:1324 2:1800 3:1240 4:1133 193.141.231/24 THESYS-NET4 C:DE 1:1324 2:1800 3:1240 4:1133 193.142.16/24 NLWCNET C:FI 1:1957 193.156/15 UNITNET-CIDR C:NO 1:1800 2:1879 3:1133 4:1240 193.175.40/24 FH-WORMS-NET-C-175-40 C:DE 1:293 2:291 193.175.41/24 FH-WORMS-NET-C-175-41 C:DE 1:293 2:291 193.175.42/24 FH-WORMS-NET-C-175-42 C:DE 1:293 2:291 193.175.43/24 FH-WORMS-NET-C-175-43 C:DE 1:293 2:291 193.175.44/24 FH-WORMS-NET-C-175-44 C:DE 1:293 2:291 193.175.45/24 FH-WORMS-NET-C-175-45 C:DE 1:293 2:291 193.175.46/24 FH-WORMS-NET-C-175-46 C:DE 1:293 2:291 193.175.47/24 FH-WORMS-NET-C-175-47 C:DE 1:293 2:291 193.219.32/19 LITNET-CIDR C:LT 1:1800 2:1879 3:1133 4:1240 194.49.56/24 BREZING C:DE 1:1324 2:1800 3:1240 4:1133 194.49.57/24 BUOHLER C:DE 1:1324 2:1800 3:1240 4:1133 194.49.58/24 DARABOS C:DE 1:1324 2:1800 3:1240 4:1133 198.6.201/24 CCSI-NET C:US 1:701 2:702 198.6.226/24 SVCDUDES C:US 1:701 2:702 198.6.227/24 SVCDUDES C:US 1:701 2:702 198.55.8/21 MAGEE-NET1-8 C:US 1:204 2:1206 198.59/16 NETBLK-WESTNET C:US 1:209 2:210 198.59.192/18 NETBLK-WESTNET C:US 1:1800 2:1240 3:209 4:210 198.60/16 NETBLK-WESTNET C:US 1:210 2:209 198.60.200/24 WESTNET C:US 1:210 2:209 198.60.201/24 WESTNET C:US 1:210 2:209 198.60.202/24 WESTNET C:US 1:210 2:209 198.60.203/24 WESTNET C:US 1:210 2:209 198.60.204/24 WESTNET C:US 1:210 2:209 198.60.205/24 WESTNET C:US 1:210 2:209 198.60.206/24 WESTNET C:US 1:210 2:209 198.60.207/24 WESTNET C:US 1:210 2:209 198.78.246/24 KNXCOLL-NET C:US 1:279 2:86 198.79.76/24 REDGATE-NET C:US 1:279 2:86 198.85.254/24 LOUISBURG7 C:US 1:1329 198.95.32/24 CREAF-C-95-32 C:US 1:200 2:201 198.95.33/24 CREAF-C-95-33 C:US 1:200 2:201 198.95.34/24 CREAF-C-95-34 C:US 1:200 2:201 198.95.35/24 CREAF-C-95-35 C:US 1:200 2:201 198.95.36/24 CREAF-C-95-36 C:US 1:200 2:201 198.95.37/24 CREAF-C-95-37 C:US 1:200 2:201 198.95.38/24 CREAF-C-95-38 C:US 1:200 2:201 198.95.39/24 CREAF-C-95-39 C:US 1:200 2:201 198.95.40/24 CREAF-C-95-40 C:US 1:200 2:201 198.95.41/24 CREAF-C-95-41 C:US 1:200 2:201 198.95.42/24 CREAF-C-95-42 C:US 1:200 2:201 198.95.43/24 CREAF-C-95-43 C:US 1:200 2:201 198.95.44/24 CREAF-C-95-44 C:US 1:200 2:201 198.95.45/24 CREAF-C-95-45 C:US 1:200 2:201 198.95.46/24 CREAF-C-95-46 C:US 1:200 2:201 198.95.47/24 CREAF-C-95-47 C:US 1:200 2:201 198.101.16/24 GTE-SPACENET1 C:US 1:86 2:279 198.101.17/24 GTE-SPACENET2 C:US 1:86 2:279 198.101.24/24 GTE-SPACENET9 C:US 1:86 2:279 198.104/16 NWNET-BLK2 C:US 1:685 2:73 3:101 198.105.232/22 MSOFT-1 C:US 1:685 2:73 3:101 198.106/16 NWNET-BLK2 C:US 1:685 2:73 3:101 198.107/16 NWNET-BLK2 C:US 1:685 2:73 3:101 198.114.200/24 NHC-5 C:US 1:560 2:701 198.114.201/24 NHC-5 C:US 1:560 2:701 198.124.104/24 LAMONT-ARM C:US 1:293 2:291 198.136.8/21 MAGEE-NET9-16 C:US 1:204 2:1206 198.146.149/24 EXCEED-NET2 C:US 1:279 2:86 198.150.9/24 WISC-MERITER C:US 1:1225 2:267 3:266 198.150.38/24 PANVERA C:US 1:1225 2:267 3:266 198.151.231/24 NET-SILVERLINE2 C:US 1:1800 2:1240 198.161.118/24 DBCORP-AB C:CA 1:602 2:601 3:603 198.162.1/24 EKCCNET C:CA 1:602 2:601 3:603 198.164.3/24 NET-GFC-NB-CA C:CA 1:602 2:601 3:603 198.168.44/24 UQUEBEC-8 C:CA 1:603 2:601 3:602 198.168.45/24 UQUEBEC-9 C:CA 1:603 2:601 3:602 198.168.46/24 UQUEBEC-10 C:CA 1:603 2:601 3:602 198.168.47/24 UQUEBEC-11 C:CA 1:603 2:601 3:602 198.169.9/24 PSC-GOV-SK-CA C:CA 1:603 2:601 3:602 198.187.252/24 IEA-NET C:US 1:1982 198.202.66/24 SALKNET C:US 1:195 2:1740 198.206.162/24 FSR C:US 1:1982 198.236/15 OPEN-BLK1 C:US 1:685 2:73 3:101 198.238/15 NWNET-BLK3 C:US 1:685 2:73 3:101 198.243/16 NETBLK-NET-CSN-BLK2 C:US 1:209 2:210 198.247.241/24 DTNCOM C:US 1:93 198.247.243/24 SOAPNOTES C:US 1:93 198.252.228/24 TELOS-NET C:US 1:2149 2:174 199.2.28/24 BIGTREE-DOM C:US 1:1240 2:1800 199.4.218/24 NFBCAL C:US 1:1240 2:1800 199.35/16 NETBLK-NETCOMCBLK-2 C:US 1:2551 199.45.70/24 ONLINESYS C:CA 1:701 2:702 199.54/15 DSI-CIDR-BLK-INTERNAL C:US 1:274 2:60 199.60.30/24 BCSD42-N5 C:CA 1:602 2:601 3:603 199.60.31/24 BCSD42-N5 C:CA 1:602 2:601 3:603 199.71.69/24 OPC-ON-CA C:CA 1:601 2:603 3:602 199.71.80/24 OHI-NET C:CA 1:601 2:603 3:602 199.74.153/24 BAMS-C-74-153 C:US 1:97 199.74.154/24 BAMS-C-74-154 C:US 1:97 199.74.155/24 BAMS-C-74-155 C:US 1:97 199.74.156/24 BAMS-C-74-156 C:US 1:97 199.74.157/24 BAMS-C-74-157 C:US 1:97 199.74.158/24 BAMS-C-74-158 C:US 1:97 199.79.249/24 BOULDERCREEK C:US 1:1240 2:1800 199.86.16/24 STPAUL1 C:US 1:1225 2:267 3:266 4:555 199.86.17/24 STPAUL2 C:US 1:1225 2:267 3:266 4:555 199.86.18/24 STPAUL3 C:US 1:1225 2:267 3:266 4:555 199.86.19/24 STPAUL4 C:US 1:1225 2:267 3:266 4:555 199.86.66/24 MRNET-BLOCK3 C:US 1:1225 2:267 3:266 4:555 199.86.67/24 MRNET-BLOCK4 C:US 1:1225 2:267 3:266 4:555 199.86.88/24 MRNET-BLOCK3 C:US 1:1225 2:267 3:266 4:555 199.86.89/24 MRNET-BLOCK4 C:US 1:1225 2:267 3:266 4:555 199.86.90/24 MRNET-BLOCK5 C:US 1:1225 2:267 3:266 4:555 199.86.91/24 MRNET-BLOCK6 C:US 1:1225 2:267 3:266 4:555 199.86.92/24 MRNET-BLOCK7 C:US 1:1225 2:267 3:266 4:555 199.86.93/24 MRNET-BLOCK8 C:US 1:1225 2:267 3:266 4:555 199.86.94/24 MRNET-BLOCK9 C:US 1:1225 2:267 3:266 4:555 199.86.95/24 MRNET-BLOCK10 C:US 1:1225 2:267 3:266 4:555 199.89.187/24 SEI2 C:US 1:1240 2:1800 199.98.142/24 PSINET-C5 C:US 1:2149 2:174 199.98.143/24 PSINET-C5 C:US 1:2149 2:174 199.98.144/24 PSINET-C5 C:US 1:2149 2:174 199.98.145/24 PSINET-C5 C:US 1:2149 2:174 199.98.146/24 PSINET-C5 C:US 1:2149 2:174 199.98.147/24 PSINET-C5 C:US 1:2149 2:174 199.98.148/24 PSINET-C5 C:US 1:2149 2:174 199.104/16 NETBLK-WESTNET-W2 C:US 1:210 2:209 199.117/16 NETBLK-CSN-BLK3 C:US 1:209 2:210 199.117.16/24 CSN-BLK3 C:US 1:209 2:210 199.120.212/24 MYRI-NET C:US 1:1740 199.124.8/21 CPF-LAN C:US 1:22 199.164.137/24 ARCOM C:US 1:1740 199.164.166/24 ARMORY-SUB C:US 1:1240 2:1800 199.165.174/24 TRIPS C:US 1:1240 2:1800 199.174.5/24 NET-NLIC C:US 1:1240 2:1800 199.181.178/24 NET-SLCL C:US 1:1330 2:93 199.181.179/24 ZAK C:US 1:1982 199.181.180/24 ITRONIXNET-2 C:US 1:1982 199.181.197/24 STS-INC-NET C:US 1:1332 199.190.24/24 MHPCC C:US 1:3381 199.190.25/24 MPHCC C:US 1:3381 199.199.1/24 MRNET-C-BLOCK4 C:US 1:1225 2:267 3:266 4:555 199.201.8/24 CLARKNET2-CBLK3 C:US 1:1800 2:1240 199.201.9/24 CLARKNET2-CBLK3 C:US 1:1800 2:1240 199.201.10/24 CLARKNET2-CBLK3 C:US 1:1800 2:1240 199.201.11/24 CLARKNET2-CBLK3 C:US 1:1800 2:1240 199.201.12/24 CLARKNET2-CBLK3 C:US 1:1800 2:1240 199.201.13/24 CLARKNET2-CBLK3 C:US 1:1800 2:1240 199.201.14/24 CLARKNET2-CBLK3 C:US 1:1800 2:1240 199.201.15/24 CLARKNET2-CBLK3 C:US 1:1800 2:1240 200.9.107/24 UECE-ANCE C:BR 1:293 2:291 202.17.120/24 SGU C:JP 1:1240 2:1800 202.17.121/24 SGU C:JP 1:1240 2:1800 202.17.122/24 SGU C:JP 1:1240 2:1800 202.17.123/24 SGU C:JP 1:1240 2:1800 202.17.124/24 SGU C:JP 1:1240 2:1800 202.17.125/24 SGU C:JP 1:1240 2:1800 202.17.126/24 SGU C:JP 1:1240 2:1800 202.17.127/24 SGU C:JP 1:1240 2:1800 202.26.2/24 NETBLK-JAPAN-INET-C7 C:JP 1:1957 Deletions: --192.6.1/24 HP-NETS2 C:US 5:560 --192.245.1/24 FCR-IP-1 C:US 1:560 2:701 --192.245.2/24 FCR-IP-2 C:US 1:560 2:701 --198.49.178/24 LAHS-NET C:US 1:68 2:209 3:210 --198.84.4/24 WDC-PUBNIX1 C:US 1:1957 --198.84.5/24 WDC-PUBNIX2 C:US 1:1957 --198.84.6/24 WDC-PUBNIX3 C:US 1:1957 --198.84.7/24 WDC-PUBNIX4 C:US 1:1957 --198.133.171/24 LAMS-NET C:US 1:68 2:209 3:210 --202.35.80/24 KMSNET-C-35-80 C:JP 1:1240 2:1800 --202.35.81/24 KMSNET-C-35-81 C:JP 1:1240 2:1800 --202.35.82/24 KMSNET-C-35-82 C:JP 1:1240 2:1800 --202.35.83/24 KMSNET-C-35-83 C:JP 1:1240 2:1800 --202.35.84/24 KMSNET-C-35-84 C:JP 1:1240 2:1800 --202.35.85/24 KMSNET-C-35-85 C:JP 1:1240 2:1800 --202.35.86/24 KMSNET-C-35-86 C:JP 1:1240 2:1800 --202.35.87/24 KMSNET-C-35-87 C:JP 1:1240 2:1800 --202.35.88/24 KMSNET-C-35-88 C:JP 1:1240 2:1800 --202.35.89/24 KMSNET-C-35-89 C:JP 1:1240 2:1800 --202.35.90/24 KMSNET-C-35-90 C:JP 1:1240 2:1800 --202.35.91/24 KMSNET-C-35-91 C:JP 1:1240 2:1800 --202.35.92/24 KMSNET-C-35-92 C:JP 1:1240 2:1800 --202.35.93/24 KMSNET-C-35-93 C:JP 1:1240 2:1800 --202.35.94/24 KMSNET-C-35-94 C:JP 1:1240 2:1800 --202.35.95/24 KMSNET-C-35-95 C:JP 1:1240 2:1800 Expanded listing, sorted by country, then by organization: ========================================================== Australia --------- Telecom Australia, 32 Pirie Street, Adelaide, South Australia, 5000, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) -------------- 192.148.157/24 TELECOM-C (AU) Austria ------- PM-Data OEG, Entschendorf 45, A-8321 St. Margareten, AUSTRIA 1:701 Alternet 2:1800 ICM-Atlantic ------------- 193.80.234/24 PM-DATA (AT) Belgium ------- C.O.I. NV, Interleuvenlaan 16, B-3001 Leuven, BELGIUM 1:1957 ANSCIX-AS ------------- 193.74.240/24 COIBE (BE) EUnet Belgium nv/sa, Stapelhuisstraat 13, B-3000 Leuven, BELGIUM 1:1957 ANSCIX-AS ------------- 193.74.232/24 EUNET-BE (BE) Brazil ------ Universidade Estadual do Ceara / Departamento de Informatica, Av. Paranjana 1700. Campus do Itapery., Fortaleza, Ceara, 60740-000, BRAZIL 1:293 Energy Science Network (FIX-East) 2:291 Energy Science Network (FIX-West) ------------ 200.9.107/24 UECE-ANCE (BR) Canada ------ Atmospheric Environmental Service, 4905 Dufferin Ave., Downsview, ON, M3H5T4, CANADA 1:603 CA*net in Montreal 2:601 CA*net in Toronto 3:602 CA*net in Vancouver --------- 142.98/16 DOEWAN2 (CA) Centre de Recherche Informatique de Montreal, 1801, avenue Mcgill College, Montreal, Quebec, QC, H3A 2N4, CANADA 1:603 CA*net in Montreal 2:601 CA*net in Toronto 3:602 CA*net in Vancouver ------------ 192.77.60/24 CRIM-CNET12 (CA) DBCORP Information Systems Inc., 2060 Sunlife Plaza, 140 Fourth Avenue S.W., Calgary, AB, T2P 3N4, CANADA 1:602 CA*net in Vancouver 2:601 CA*net in Toronto 3:603 CA*net in Montreal -------------- 198.161.118/24 DBCORP-AB (CA) East Kootenay Community College, Box 8500, Cranbrook, BC, V1C 5L7, CANADA 1:602 CA*net in Vancouver 2:601 CA*net in Toronto 3:603 CA*net in Montreal ------------ 198.162.1/24 EKCCNET (CA) Gulf Fisheries Centre, 343 Archibald Street, Moncton, NB, E1C 9B6, CANADA 1:602 CA*net in Vancouver 2:601 CA*net in Toronto 3:603 CA*net in Montreal ------------ 198.164.3/24 NET-GFC-NB-CA (CA) Indian and Northern Affairs Canada, 10 Wellington Street, 7th Floor, North Tower, Hull, QC, K1A 0H4, CANADA 1:601 CA*net in Toronto 2:603 CA*net in Montreal 3:602 CA*net in Vancouver ---------- 142.212/16 INACW (CA) Online Systems of Canada, 1024 Hyde Park Road, London, ON, N6A 4B7, CANADA 1:701 Alternet 2:702 Alternet ------------ 199.45.70/24 ONLINESYS (CA) Ontario Prevention Clearinghouse, 415 Yonge Street, Suite 1200, Toronto, ON, M5B 2E7, CANADA 1:601 CA*net in Toronto 2:603 CA*net in Montreal 3:602 CA*net in Vancouver ------------ 199.71.69/24 OPC-ON-CA (CA) Ottawa Heart Institute, 1053 Carling Avenue, H2-231, Ottawa, ON, K1Y 4E9, CANADA 1:601 CA*net in Toronto 2:603 CA*net in Montreal 3:602 CA*net in Vancouver ------------ 199.71.80/24 OHI-NET (CA) Public Service Commission, 2103 11th Ave., Regina, SK, S4P 3V7, CANADA 1:603 CA*net in Montreal 2:601 CA*net in Toronto 3:602 CA*net in Vancouver ------------ 198.169.9/24 PSC-GOV-SK-CA (CA) School District #42 (Maple Ridge -- Pitt Meadows), 22225 Brown Avenue, Maple Ridge, BC, V2X 8N6, CANADA 1:602 CA*net in Vancouver 2:601 CA*net in Toronto 3:603 CA*net in Montreal ------------ 199.60.30/24 BCSD42-N5 (CA) 199.60.31/24 BCSD42-N5 (CA) Universite du Quebec, 2875 Bld.Laurier, Ste-Foy, QC, G1V2M3, CANADA 1:603 CA*net in Montreal 2:601 CA*net in Toronto 3:602 CA*net in Vancouver ------------- 198.168.44/24 UQUEBEC-8 (CA) 198.168.45/24 UQUEBEC-9 (CA) 198.168.46/24 UQUEBEC-10 (CA) 198.168.47/24 UQUEBEC-11 (CA) Colombia -------- Telecom Colombia, Transv 49 N 105-84, Bogota, COLOMBIA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ------------- 192.157.67/24 ICMNET-4 (CO) Estonia ------- Estonian National Maritime Board, Tartu mnt 13, EE0105 Tallinn, ESTONIA 1:1800 ICM-Atlantic 2:1879 EUROPE-RS 3:1133 CERN/DANTE 4:1240 ICM-Pacific ------------- 193.40.226/24 ENMB-NET-C-40-226 (EE) 193.40.227/24 ENMB-NET-C-40-227 (EE) 193.40.228/24 ENMB-NET-C-40-228 (EE) Finland ------- Nordic Lan & Wan Communication Oy, Sinikalliontie 14B, 02630 Espoo, FINLAND 1:1957 ANSCIX-AS ------------- 193.142.16/24 NLWCNET (FI) R. Linturi Ltd, Wihurinaukio 2, FI-00570 Helsinki, FINLAND 1:701 Alternet 2:1800 ICM-Atlantic ------------- 192.89.240/24 LINTURI1 (FI) 192.89.241/24 LINTURI2 (FI) France ------ CIMU Ecole veterinaire de Nantes, case postale 3013, 44087 Nantes CEDEX 03, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ----------- 193.48.2/24 FR-OR-VETONA (FR) ENSAE - Timbre J020, 3 avenue Pierre Larousse, 92241 Malakoff CEDEX, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ------------- 193.48.172/24 FR-ENSAE01 (FR) ENSAM, Porte de Paris, 71250 Cluny, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ------------- 193.50.222/24 FR-PICTEL02 (FR) 193.50.223/24 FR-PICTEL03 (FR) 193.50.252/24 FR-PICTEL04 (FR) 193.50.253/24 FR-PICTEL05 (FR) Germany ------- Fachhochschule - Rheinland Pfalz, Abt. Worms, Erenburgerstr. 19, Worms, D-67549, GERMANY 1:293 Energy Science Network (FIX-East) 2:291 Energy Science Network (FIX-West) ------------- 193.175.40/24 FH-WORMS-NET-C-175-40 (DE) 193.175.41/24 FH-WORMS-NET-C-175-41 (DE) 193.175.42/24 FH-WORMS-NET-C-175-42 (DE) 193.175.43/24 FH-WORMS-NET-C-175-43 (DE) 193.175.44/24 FH-WORMS-NET-C-175-44 (DE) 193.175.45/24 FH-WORMS-NET-C-175-45 (DE) 193.175.46/24 FH-WORMS-NET-C-175-46 (DE) 193.175.47/24 FH-WORMS-NET-C-175-47 (DE) Individual Network e. V., Linkstr. 15, D-65933 Frankfurt am Main, Frankfurt, GERMANY 1:1324 ANS New York City - DNSS 35 2:1800 ICM-Atlantic 3:1240 ICM-Pacific 4:1133 CERN/DANTE -------------- 193.141.104/24 INDIVIDUAL-NET (DE) SOFTCON Gesellschaft fuer Softwareentwicklung mbH, Gruenwalder Weg 28g, D-82041 Oberhaching, GERMANY 1:701 Alternet 2:1800 ICM-Atlantic ------------ 193.31.10/24 SOFTCON-MUC (DE) 193.31.11/24 SOFTCON-MUC (DE) Softwarebuero Buohler, Muehlenweg 10, D-88521 Erisdorf, GERMANY 1:1324 ANS New York City - DNSS 35 2:1800 ICM-Atlantic 3:1240 ICM-Pacific 4:1133 CERN/DANTE ------------ 194.49.57/24 BUOHLER (DE) THESYS GmbH, Haarbergstrasse 61, Postfach 194, D-99079 Erfurt, GERMANY 1:1324 ANS New York City - DNSS 35 2:1800 ICM-Atlantic 3:1240 ICM-Pacific 4:1133 CERN/DANTE -------------- 193.141.230/24 THESYS-NET3 (DE) 193.141.231/24 THESYS-NET4 (DE) UNIX Softwaredevelopment Brezing, Burgstrasse 24, D-72800 Eningen, GERMANY 1:1324 ANS New York City - DNSS 35 2:1800 ICM-Atlantic 3:1240 ICM-Pacific 4:1133 CERN/DANTE ------------ 194.49.56/24 BREZING (DE) UNIX Softwaredevelopment and DATABASE Maintenance Darabos, Baumgartenstrasse 6/2, D-73084 Salach, GERMANY 1:1324 ANS New York City - DNSS 35 2:1800 ICM-Atlantic 3:1240 ICM-Pacific 4:1133 CERN/DANTE ------------ 194.49.58/24 DARABOS (DE) Ireland ------- Foreign Exchange Co Ltd, Iveragh Road, Killorglin, CO KERRY, IRELAND 1:1957 ANSCIX-AS -------------- 193.120.232/24 FEXCO2 (IE) Italy ----- Sodalia S.p.A., Via Brennero 364, I-38100 Trento, ITALY 1:1957 ANSCIX-AS ------------- 193.70.236/24 SODALIA-NET (IT) 193.70.237/24 SODALIA-NET (IT) Japan ----- Japan Network Information Center, c/o Computer Centre, University of Tokyo, Yayoi 2-11-16, Bunkyo-ku, Tokyo 113, JAPAN 1:1957 ANSCIX-AS ----------- 202.26.2/24 NETBLK-JAPAN-INET-C7 (JP) Sapporo Gakuin University, 11, Bunkyoudai, Ebetsu-city, Hokkaido 069, JAPAN 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ------------- 202.17.120/24 SGU (JP) 202.17.121/24 SGU (JP) 202.17.122/24 SGU (JP) 202.17.123/24 SGU (JP) 202.17.124/24 SGU (JP) 202.17.125/24 SGU (JP) 202.17.126/24 SGU (JP) 202.17.127/24 SGU (JP) Toshiba Corporation, Research & Development Center,, Engneering Information System Dept., 1, Komukai Toshiba-cho, Saiwai-ku, Kawasaki 210, JAPAN 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ------------- 192.50.189/24 TOSHIBA-NET1 (JP) Lithuania --------- Institute of Mathematics and Informatics, A.Gostauto 12, LT-2600 Vilnius, LITHUANIA 1:1800 ICM-Atlantic 2:1879 EUROPE-RS 3:1133 CERN/DANTE 4:1240 ICM-Pacific ------------- 193.219.32/19 LITNET-CIDR (LT) Norway ------ SINTEF Runit, N-7034 Trondheim, NORWAY 1:1800 ICM-Atlantic 2:1879 EUROPE-RS 3:1133 CERN/DANTE 4:1240 ICM-Pacific --------- 158.36/14 UNINETT1-CIDR (NO) 193.156/15 UNITNET-CIDR (NO) Portugal -------- INESC-Porto, Lg. Mompilher, 22, P-4007 Porto CODEX, PORTUGAL 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific ------------- 193.136.48/24 INESCP-NET-SUPER (PT) 193.136.49/24 INESCP-NET-SUPER (PT) 193.136.50/24 INESCP-NET-SUPER (PT) 193.136.52/24 INESCP-NET-SUPER (PT) Universidade Tecnica de Lisboa, Instituto Superior de Economia e Gestao, Rua Miguel Lupi, 20, P-1200 LISBOA, PORTUGAL 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific -------------- 193.136.144/24 ISEG-1 (PT) Russian Federation ------------------ RELCOM Corp., 3, Raspletina st., Moscow, RUSSIAN FEDERATION 1:701 Alternet 2:1800 ICM-Atlantic -------------- 193.125.158/24 EXPO (RU) Sweden ------ Akademiska Sjukhuset Uppsala, Medicintekniska avd., S-751 85 Uppsala, SWEDEN 1:1957 ANSCIX-AS -------------- 192.165.148/24 SE-AS-MED (SE) Akademiska sjukhuset, MTA, S-751 85 Uppsala, SWEDEN 1:1957 ANSCIX-AS ------------ 193.10.16/24 SE-AS-LAN (SE) 193.10.24/24 SE-AS-LAN (SE) 193.10.127/24 SE-AKADEM-MTA (SE) Uppsala Lans Landsting, Box 602, S-751 25 Uppsala, SWEDEN 1:1957 ANSCIX-AS ------------ 192.36.32/24 UPPSALA-L1 (SE) Uppsala Universitet, UDAC, Box 174, S-751 04 Uppsala, SWEDEN 1:1957 ANSCIX-AS ------------ 193.44.76/24 UDAC-SERVER (SE) Switzerland ----------- Berner Versicherung, Abteilung ST, Sulgeneckstrasse 19, CH-3018 BERNE, SWITZERLAND 1:1957 ANSCIX-AS ---------- 193.8.2/24 BERNER-BLOCK-8 (CH) United Kingdom -------------- Harrier Computer Systems Ltd, Unit 1a, Falcon Business Park, Finchampstead, RG11 4QQ, UNITED KINGDOM 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ------------- 193.128.77/24 HCS (GB) PIPEX, 216 Cambridge Science Park, Milton Road, Cambridge, CB4 4WA, England, UNITED KINGDOM 1:1957 ANSCIX-AS ------------- 193.128.40/24 PIPEX-INTERAS (GB) United States ------------- Arcom Electronics, San Jose, CA, USA 1:1740 CERFnet -------------- 199.164.137/24 ARCOM (US) Battelle PNL, PO Box 999, Richland, WA 99352, USA 1:293 Energy Science Network (FIX-East) 2:291 Energy Science Network (FIX-West) -------------- 198.124.104/24 LAMONT-ARM (US) Bell Atlantic Mobil Systems, Route 202, Bedminster, NJ 19355, USA 1:97 JvNCnet Regional Network ------------- 199.74.153/24 BAMS-C-74-153 (US) 199.74.154/24 BAMS-C-74-154 (US) 199.74.155/24 BAMS-C-74-155 (US) 199.74.156/24 BAMS-C-74-156 (US) 199.74.157/24 BAMS-C-74-157 (US) 199.74.158/24 BAMS-C-74-158 (US) Bell Communications Research, Morris Research and Engineering Center, 445 South Street, Morristown, NJ 07960-6454, USA 1:1957 ANSCIX-AS ------------ 192.4.139/24 BELLCORE-UNUSED (US) Bolt Beranek and Newman, 10 Moulton Street, Cambridge, MA 02138, USA 1:274 DSI - Defense Simulation Internet (FIX-East) 2:60 DSI - Defense Simulation Internet (FIX-West) ------------- 192.253.70/24 DSI-NET70 (US) 199.54/15 DSI-CIDR-BLK-INTERNAL (US) Canter & Siegel, P.O.Box 13510, Scottsdale, AZ 85267, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.145/24 PSINET-C5 (US) Centocor, Inc., 200 Great Valley Parkway, Malvern, PA 19355, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.147/24 PSINET-C5 (US) Clark Internet Services, Inc., 10600 Route 108, Ellicott City, MD 21042, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ------------ 199.201.8/24 CLARKNET2-CBLK3 (US) 199.201.9/24 CLARKNET2-CBLK3 (US) 199.201.10/24 CLARKNET2-CBLK3 (US) 199.201.11/24 CLARKNET2-CBLK3 (US) 199.201.12/24 CLARKNET2-CBLK3 (US) 199.201.13/24 CLARKNET2-CBLK3 (US) 199.201.14/24 CLARKNET2-CBLK3 (US) 199.201.15/24 CLARKNET2-CBLK3 (US) Colorado SuperNet, Inc., Colorado School of Mines, 1500 Illinois, Golden, CO 80401, USA 1:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 2:210 Westnet Regional Network (Utah Attachment) - ENSS 142 ---------- 198.243/16 NETBLK-NET-CSN-BLK2 (US) 199.117/16 NETBLK-CSN-BLK3 (US) 199.117.16/24 CSN-BLK3 (US) Columbia Sportswear Company, 6600 North Baltimore, P.O. Box 83239, Portland, OR 97283, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.148/24 PSINET-C5 (US) Commander-In-Chief, Pacific Fleet, 250 Makalapa Drive, Parl Harbor, HI 96860-7000, USA 1:22 NOSC (Naval Ocean Systems Center) ------------ 199.124.8/21 CPF-LAN (US) Commuter Communications, 6201 Middle Fiskville Rd, Suite 1115, Austin, TX 78752, USA 1:701 Alternet 2:702 Alternet ------------ 198.6.201/24 CCSI-NET (US) CompuTech, West 1005 Ninth Ave. Suite 202, Spokane, WA 99204, USA 1:1982 Northwest Nexus -------------- 198.187.252/24 IEA-NET (US) Computer Services, Department of Public Works, City of St. Paul, 700 City Hall Annex, 25 West 4th Street, Saint Paul, MN 55102-1631, USA 1:1225 CICNET at Argonne Labs 2:267 CICNET at UIUC 3:266 CICNET at MERIT 4:555 Minnesota Supercomputer Center Network (MSCNet) ------------ 199.86.16/24 STPAUL1 (US) 199.86.17/24 STPAUL2 (US) 199.86.18/24 STPAUL3 (US) 199.86.19/24 STPAUL4 (US) Creative Labs, 1901 McCarthy Blvd, Milpitas, CA 95035, USA 1:200 BARRNet 2:201 BARRNet ------------ 198.95.32/24 CREAF-C-95-32 (US) 198.95.33/24 CREAF-C-95-33 (US) 198.95.34/24 CREAF-C-95-34 (US) 198.95.35/24 CREAF-C-95-35 (US) 198.95.36/24 CREAF-C-95-36 (US) 198.95.37/24 CREAF-C-95-37 (US) 198.95.38/24 CREAF-C-95-38 (US) 198.95.39/24 CREAF-C-95-39 (US) 198.95.40/24 CREAF-C-95-40 (US) 198.95.41/24 CREAF-C-95-41 (US) 198.95.42/24 CREAF-C-95-42 (US) 198.95.43/24 CREAF-C-95-43 (US) 198.95.44/24 CREAF-C-95-44 (US) 198.95.45/24 CREAF-C-95-45 (US) 198.95.46/24 CREAF-C-95-46 (US) 198.95.47/24 CREAF-C-95-47 (US) Data Transmission Network Corp, 9110 West Dodge Road, Suite 200, Omaha, NE 68114, USA 1:93 MIDnet -------------- 198.247.241/24 DTNCOM (US) Eastern Space and Missile Center, ESMC/SCPX, Patrick AFB, FL 32925, USA 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) --------- 147.74/16 CAPE (US) ExCEED, Inc, P.O. Box 70, Jamestown, TN 38556, USA 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) -------------- 198.146.149/24 EXCEED-NET2 (US) First Step Research, 1004 North Polk Ext., Moscow, ID 83843, USA 1:1982 Northwest Nexus -------------- 198.206.162/24 FSR (US) GTE Spacenet Corp., 1700 Old Meadow Road, McLean, VA 22102, USA 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) ------------- 198.101.16/24 GTE-SPACENET1 (US) 198.101.17/24 GTE-SPACENET2 (US) 198.101.24/24 GTE-SPACENET9 (US) General Cinema Theatres, 1300 Boylston Street, Chestnut Hill, MA 02167, USA 1:560 NEARnet Regional Network 2:701 Alternet ---------- 168.119/16 GCTI-B (US) General Instrument, 6262 Lusk Blvd, San Diego, CA 92121, USA 1:2386 INS-AS 2:1321 ANS San Francisco - DNSS 11 --------- 168.84/16 GI-B (US) HappMIS, Inc., 106 Garlish Drive, Elk Grove Village, IL 60007, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.143/24 PSINET-C5 (US) Itronix, Corporation, South 801 Steven's, Spokane, WA 99204, USA 1:1982 Northwest Nexus -------------- 199.181.180/24 ITRONIXNET-2 (US) Knoxville College, 205 McKee Hall, MIS Dept., 901 College Street, Knoxville, TN 37291, USA 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) ------------- 198.78.246/24 KNXCOLL-NET (US) Louisburg College, 502 North Main Street, Louisburg, NC 27549-7704, USA 1:1329 ANS Greensboro - DNSS 75 ------------- 198.85.254/24 LOUISBURG7 (US) MRNet, 511 11th ave s, Box 212, Minneapolis, MN 55415, USA 1:1225 CICNET at Argonne Labs 2:267 CICNET at UIUC 3:266 CICNET at MERIT 4:555 Minnesota Supercomputer Center Network (MSCNet) ------------ 199.199.1/24 MRNET-C-BLOCK4 (US) Magee-Womens Hospital, 300 Halket Street, Pittsburgh, PA 15213-3180, USA 1:204 PSCNET Regional Network 2:1206 PSCNET Regional Network ----------- 198.55.8/21 MAGEE-NET1-8 (US) 198.136.8/21 MAGEE-NET9-16 (US) Maui High Performance Computing Center, 535 Lipoa Parkway, Suite 201, Kihei, HI 96753, USA 1:3381 MHPCC-AS ------------- 199.190.24/24 MHPCC (US) 199.190.25/24 MPHCC (US) Maxus Energy Corporation, 717 North Harwood Street, Dallas, TX 75201, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ---------- 146.241/16 MAXUS (US) Microsoft, 3635 - 157th Ave. N.E., Redmond, WA 98052-6399, USA 1:685 NorthWestNet Regional Network 2:73 NorthWestNet Regional Network 3:101 NorthWestNet Regional Network -------------- 198.105.232/22 MSOFT-1 (US) Minnesota Regional Network, 511 11th Ave. S., Minneapolis, MN 55415, USA 1:1225 CICNET at Argonne Labs 2:267 CICNET at UIUC 3:266 CICNET at MERIT 4:555 Minnesota Supercomputer Center Network (MSCNet) ------------ 199.86.66/24 MRNET-BLOCK3 (US) 199.86.67/24 MRNET-BLOCK4 (US) 199.86.88/24 MRNET-BLOCK3 (US) 199.86.89/24 MRNET-BLOCK4 (US) 199.86.90/24 MRNET-BLOCK5 (US) 199.86.91/24 MRNET-BLOCK6 (US) 199.86.92/24 MRNET-BLOCK7 (US) 199.86.93/24 MRNET-BLOCK8 (US) 199.86.94/24 MRNET-BLOCK9 (US) 199.86.95/24 MRNET-BLOCK10 (US) Mount Bonnell, Inc., 1201 West 24th Street, Suite 103, Austin, TX 78705, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.142/24 PSINET-C5 (US) Myricom, Inc., 325 N. Santa Anita Ave., Arcadia, CA 91006, USA 1:1740 CERFnet -------------- 199.120.212/24 MYRI-NET (US) NASA Kennedy Space Center, Kennedy Space Center, FL 32899, USA 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) ---------- 163.205/16 NASA3 (US) 163.206/16 NASA4 (US) NASA Kennedy Space Center, Mail Stop DL-ESS-13, Kennedy Space Center, FL 32899, USA 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) ------------ 192.77.42/24 NASA-KSC16 (US) NETCOM On-line Communications Services, Inc., 4000 Moorpark Ave, Suite 209, San Jose, CA 95117, USA 1:2551 NETCOM --------- 199.35/16 NETBLK-NETCOMCBLK-2 (US) Network Systems Laboratory Digital, 505 Hamilton Ave, Palo ALto, CA 94301, USA 1:701 Alternet 2:702 Alternet ------------- 192.208.34/24 DEC-EXTERNAL (US) New Hampshire College, 2500 North River Road, Manchester, NH 03104, USA 1:560 NEARnet Regional Network 2:701 Alternet -------------- 198.114.200/24 NHC-5 (US) 198.114.201/24 NHC-5 (US) North Star Financial, 2-2600 East Cliff Drive, Santa Cruz, CA 95062, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ------------- 199.79.249/24 BOULDERCREEK (US) NorthWestNet, 15400 SE 30th Place, Suite 202, Bellevue, WA 98007, USA 1:685 NorthWestNet Regional Network 2:73 NorthWestNet Regional Network 3:101 NorthWestNet Regional Network ---------- 192.147.160/20 NWNET10 (US) 192.220/16 NETBLK-NWNET (US) 198.104/16 NWNET-BLK2 (US) 198.106/16 NWNET-BLK2 (US) 198.107/16 NWNET-BLK2 (US) 198.238/15 NWNET-BLK3 (US) Northern Life Insurance Company, PO Box 12530, Seattle, WA 98111, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ------------ 199.174.5/24 NET-NLIC (US) Oregon Department of Education, 700 Pringle Parkway SE, Salem, OR 97310-0290, USA 1:685 NorthWestNet Regional Network 2:73 NorthWestNet Regional Network 3:101 NorthWestNet Regional Network ---------- 198.236/15 OPEN-BLK1 (US) PREPnet, 305 S. Craig St., Pittsburgh, PA 15213, USA 1:204 PSCNET Regional Network 2:1206 PSCNET Regional Network ---------- 192.204/16 NETBLK-PREPNET-C (US) PanVera, 565 Science Drive, Madison, WI 53711, USA 1:1225 CICNET at Argonne Labs 2:267 CICNET at UIUC 3:266 CICNET at MERIT ------------- 198.150.38/24 PANVERA (US) Petroleum Information, 4100 E. Dry Creek Road, Littleton, CO 80122, USA 1:2551 NETCOM --------- 162.52/16 PETROINFO (US) Petroleum Science International, Inc., 3503 Cedar Knolls Dr., Ste. A, Kingwood, TX 77339, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.144/24 PSINET-C5 (US) Redgate Communications, 660 Beachland Blvd., Vero Beach, FL 32963, USA 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) ------------ 198.79.76/24 REDGATE-NET (US) S.O.A.P Notes, Inc, 3140 O Street, Lincoln, NE 68510, USA 1:93 MIDnet -------------- 198.247.243/24 SOAPNOTES (US) SRI International, 333 Ravenswood Avenue, Menlo Park, CA 94025, USA 1:200 BARRNet 2:201 BARRNet ----------- 192.5.93/24 SRI-DEMO (US) Sensimetrics Corp., 26 Landsdowne St., Cambridge, MA 02139, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.146/24 PSINET-C5 (US) Sequoia Technology Research, 28 Cortez Rd., Redwood City, CA 94062, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ----------- 199.2.28/24 BIGTREE-DOM (US) Silicon Engineering, 269 Mt Hermon Road, Suite #207, Scotts Valley, CA 95066, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ------------- 199.89.187/24 SEI2 (US) Silverline Industries, Inc, 2605W 22nd Street, Suite 38, Oakbrook, IL 60521, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific -------------- 198.151.231/24 NET-SILVERLINE2 (US) Soft Switch, Incorporated, 640 Lee Road, Wayne, PA 19087-5698, USA 1:204 PSCNET Regional Network 2:1206 PSCNET Regional Network ------------- 192.150.52/22 SSW2-5 (US) Software Ventures Corp., 2907 Claremont Ave., Berkeley, CA 94705, USA 1:701 Alternet 2:702 Alternet ------------ 198.6.226/24 SVCDUDES (US) 198.6.227/24 SVCDUDES (US) Solutions Through Software, 6851 South Holly Circle, Suite 135, Englewood, CO 80112, USA 1:1332 ANS Denver - DNSS 99 -------------- 199.181.197/24 STS-INC-NET (US) St. Louis County Library, 1640 South Lindbergh Blvd., St. Louis, MO 63131, USA 1:1330 ANS St. Louis - DNSS 83 2:93 MIDnet -------------- 199.181.178/24 NET-SLCL (US) THE ARMORY, 305 McMillan Dr, Santa Cruz, CA 95060, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic -------------- 199.164.166/24 ARMORY-SUB (US) TRIPS CENTRAL PARTNERSHIP, 325A River St, Santa Cruz, CA 95060, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic -------------- 199.165.174/24 TRIPS (US) Teknekron Infoswitch Corporation, 4425 Cambridge Road, Fort Worth, TX 76155, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI -------------- 192.138.162/24 INFOSWITCH1 (US) Telos Corporation, 460 Herndon Pkwy, Herndon, VA 22070, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI -------------- 198.252.228/24 TELOS-NET (US) The National Federation of the Blind of California, 317 Laurel St. #2, Santa Cruz, CA 95060, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ------------ 199.4.218/24 NFBCAL (US) The Salk Institute, 10010 North Torrey Pines Road, La Jolla, CA 92037, USA 1:195 SDSC Regional network 2:1740 CERFnet ------------- 198.202.66/24 SALKNET (US) University of Wisconsin - Madison, 1210 West Dayton Street, Madison, WI 53706, USA 1:1225 CICNET at Argonne Labs 2:267 CICNET at UIUC 3:266 CICNET at MERIT ------------ 198.150.9/24 WISC-MERITER (US) Washington Research Library Consortium, 4207 Forbes Boulevard, Lanham, MD 20706, USA 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) -------------- 192.245.136/24 WRLCNET (US) Wellfleet Communications Inc., 12 DeAngelo Drive, Bedford, MA 01730, USA 1:560 NEARnet Regional Network 2:701 Alternet --------- 192.32/16 WELLFLEET-C-BLOCK (US) Westnet, 3645 Marine Street, U. of Colorado, Boulder, CO 80309-0455, USA 1:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 2:210 Westnet Regional Network (Utah Attachment) - ENSS 142 --------- 198.59/16 NETBLK-WESTNET (US) Westnet, 3645 Marine Street, U. of Colorado, Boulder, CO 80309-0455, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 4:210 Westnet Regional Network (Utah Attachment) - ENSS 142 ------------- 198.59.192/18 NETBLK-WESTNET (US) Westnet, 3645 Marine Street, U. of Colorado, Boulder, CO 80309-0455, USA 1:210 Westnet Regional Network (Utah Attachment) - ENSS 142 2:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 --------- 198.60/16 NETBLK-WESTNET (US) 198.60.200/24 WESTNET (US) 198.60.201/24 WESTNET (US) 198.60.202/24 WESTNET (US) 198.60.203/24 WESTNET (US) 198.60.204/24 WESTNET (US) 198.60.205/24 WESTNET (US) 198.60.206/24 WESTNET (US) 198.60.207/24 WESTNET (US) 199.104/16 NETBLK-WESTNET-W2 (US) Wisconsin Electric Power Co., 231 West Michigan, Milwaukee, WI 53210, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI --------- 156.76/16 WEPCO (US) Zak Designs, Inc., South 1604 Garfield Rd., Spokane, WA 99204, USA 1:1982 Northwest Nexus -------------- 199.181.179/24 ZAK (US) ========================================================== The following Midlevel/Regional peering sessions have also been added: AS 22 - NOSC (Naval Ocean Systems Center) (US) - ENSS 135 Peer: 198.17.46.102 - Naval Ocean Systems Center, San Diego, CA 92152-5000, USA - gnop.nosc.mil ========================================================== 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.t3p Information is also avaiable through the PRDB whois server. Type "whois -h prdb.merit.edu help" for details. -------------------------------------------------------------------------- REPORT CHANGES: (Updated March 24, 1994) Metric:AS(NSS) - Historically, peer networks with multiple connections to AS 690 could only select which of those connections their networks would take by creating "Fake" AS numbers, and using those in the PRDB Metric:AS announcement lists. Some time in the next few weeks we will begin supporting an expanded syntax, where the AS may be followed by an optional NSS peer number in parentheses. Eventually, this syntax will be used to replace most or all of the current Fake ASs. This change will affect *all* places that the announcement lists are reported: all whois queries, all network reports, this "NWG" report, and the Auto-NACR. If you have code which parses these announcement lists, please be aware that that code may need modifications soon. CIDR Reports: There is a new "whois" option to list aggregates in the PRDB: whois -h prdb.merit.edu listaggs will produce a listing of the currently registered aggregates. There is also a new report on "nestings" of PRDB-registered aggregates with their more specific routes: nets.non-classful. Anyone considering configuring an aggregate into the PRDB (and you all should be!) is encouraged to pre-check that aggregate by typing the command: whois -h prdb.merit.edu 'aggchk ' (where "" is the aggregate description). This command will list all of the other entries in the PRDB that are more specific routes of , as well as any aggregates all ready configured that contain . The output includes the AUP and announcement lists of each of the nets printed, with discrepancies flagged. This is the same program that we use for sanity-checking the NACRs that you submit. The archived discussion list "db-disc@merit.edu" exists for discussion of PRDB issues. Send a message to "db-disc-request@merit.edu" to subscribe. --Dale Johnson (dsj@merit.edu) -------------------------------------------------------------------------- Please send all requests for configuration changes to nsfnet-admin@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. ******************************* --Steve Widmayer Merit/NSFNET skw@merit.edu --Enke Chen Merit/NSFNET enke@merit.edu --Steven J. Richardson Merit/NSFNET sjr@merit.edu - - - - - - - - - - - - - - - - - From list-admin Fri Apr 8 16:40:55 1994 Received: from barsoom.sura.net (aotearoa.sura.net [128.167.254.175]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id QAA26285 for ; Fri, 8 Apr 1994 16:40:44 -0400 Received: from localhost by barsoom.sura.net with SMTP (5.67b/($Id: sendmail.cf,v 1.17 1991/02/11 14:07:23 jmalcolm Exp $)) id AA06220; Fri, 8 Apr 1994 16:40:33 -0400 Message-Id: <199404082040.AA06220@barsoom.sura.net> To: regional-techs@merit.edu Subject: CIDR allocation question Date: Fri, 08 Apr 1994 16:40:32 -0400 From: Erik Sherk Hi, Given a site that has a need for a certain number of addresses, but probably will never need additional networks to fill out a power of two allocation. Should we allocate the larger block to the site anyway to reduce the size of the routing table, or should we allocate two CIDR blocks? For example, if a site will only realisticly need 6 class C's, should we allocate a block of 8, or a block of four and a block of two. Erik - - - - - - - - - - - - - - - - - From list-admin Fri Apr 8 18:25:43 1994 Received: from titan.sprintlink.net (titan.sprintlink.net [199.0.55.78]) by merit.edu (8.6.8.1/merit-1.0) with ESMTP id SAA05309 for ; Fri, 8 Apr 1994 18:25:42 -0400 Received: (from avg@localhost) by titan.sprintlink.net (8.6.8/8.6.8) id SAA03809; Fri, 8 Apr 1994 18:25:38 -0400 Date: Fri, 8 Apr 1994 18:25:38 -0400 From: Vadim Antonov Message-Id: <199404082225.SAA03809@titan.sprintlink.net> To: regional-techs@merit.edu, sherk@sura.net Subject: Re: CIDR allocation question > Given a site that has a need for a certain number of >addresses, but probably will never need additional networks to fill >out a power of two allocation. Should we allocate the larger block to >the site anyway to reduce the size of the routing table, or should we >allocate two CIDR blocks? > For example, if a site will only realisticly need 6 class C's, >should we allocate a block of 8, or a block of four and a block of two. Given that the immediate threat is the growth of routing tables, not IP address space exhaustion it's better to allocate powers of 2-sized blocks and announce only one route. The IP space overhead is about 30% but routing table savings are at least 50%. Actually, CIDR allocation helps to slow down IP address allocation by providing most of organizations an alternative to class B. We have sliced an eqivalent of 4 calss B to about 100 customers! So the 2008 doomsday estimate may be kind of pessimistic :-) --vadim - - - - - - - - - - - - - - - - - From list-admin Fri Apr 8 18:43:31 1994 Received: from Valinor.Stanford.EDU (Valinor.Stanford.EDU [131.119.246.200]) by merit.edu (8.6.8.1/merit-1.0) with ESMTP id SAA06451 for ; Fri, 8 Apr 1994 18:43:31 -0400 Received: (from vaf@localhost) by Valinor.Stanford.EDU (8.6.7/8.6.6) id PAA09109; Fri, 8 Apr 1994 15:44:43 -0700 Date: Fri, 8 Apr 94 15:44:42 PDT From: Vince Fuller To: Erik Sherk Cc: regional-techs@merit.edu Office: Spruce Hall F15, (415) 723-6860 USMail: Pine Hall 115, Stanford, CA, 94305-4122 Subject: Re: CIDR allocation question In-Reply-To: Your message of Fri, 08 Apr 1994 16:40:32 -0400 Message-ID: Given a site that has a need for a certain number of addresses, but probably will never need additional networks to fill out a power of two allocation. Should we allocate the larger block to the site anyway to reduce the size of the routing table, or should we allocate two CIDR blocks? For example, if a site will only realisticly need 6 class C's, should we allocate a block of 8, or a block of four and a block of two. The answer to this question depends on several factors. First, and probably most importantly: will all of the networks in question be aggregated into a larger block at the provider level or are there specific policy constraints that mean this site needs to be explicitly advertised beyond your network? If splitting them into two blocks means that both blocks are explicitly known to the global Internet, then the rest of the world would prefer that you give them a block of 8. If the rest of the world will only see a bigger aggregate that includes the block of 8 or the blocks of 2 + 4, then we probably don't care very much what you carry internally... Next, will you be aggregating the advertisement at the site level to propagate within your network? If you are not doing that or if there isn't any reason to do so (i.e. you have sufficiently few routes within your network that you can affort to carry all of the individual class-C's internally), then it probably doesn't make much difference to your internal routing whether the site is one block of two. In general, we allocate blocks in power-of-two chunks, though there have been some cases where our guesses about future growth were incorrect, resulting in some sites with more than one block. --Vince - - - - - - - - - - - - - - - - - From list-admin Sun Apr 10 20:07:51 1994 Received: from icm1.icp.net (icm1.icp.net [192.94.207.66]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id UAA05048 for ; Sun, 10 Apr 1994 20:07:51 -0400 Received: by icm1.icp.net (5.65/1.34) id AA22272; Sun, 10 Apr 94 20:08:58 -0400 Date: Sun, 10 Apr 94 20:08:58 -0400 From: ipasha@icm1.icp.net (Ismat Pasha) Message-Id: <9404110008.AA22272@icm1.icp.net> To: regional-techs@merit.edu, sherk@sura.net Subject: Re: CIDR allocation question I would allocate 2 blocks, considering the other option has the potential to waste lot of addresses. --Ismat Pasha (Sprintlink Engineer) - - - - - - - - - - - - - - - - - From list-admin Mon Apr 11 04:25:20 1994 Received: from ncc.ripe.net (ncc.ripe.net [192.87.45.2]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id EAA19507 for ; Mon, 11 Apr 1994 04:25:19 -0400 Received: from reif.ripe.net by ncc.ripe.net with SMTP id AA11540 (5.65a/NCC-1.12); Mon, 11 Apr 1994 10:25:15 +0200 Received: from localhost.ripe.net by reif.ripe.net with SMTP id AA01097 (5.65a/NCC-2.1); Mon, 11 Apr 1994 10:25:17 +0200 Message-Id: <9404110825.AA01097@reif.ripe.net> To: Vadim Antonov Cc: regional-techs@merit.edu Subject: Re: CIDR allocation question In-Reply-To: Your message of Fri, 08 Apr 1994 18:25:38 EDT. <199404082225.SAA03809@titan.sprintlink.net> From: Daniel Karrenberg X-Organization: RIPE Network Coordination Centre X-Phone: +31 20 592 5065 Date: Mon, 11 Apr 1994 10:25:15 +0200 Sender: Daniel.Karrenberg@ripe.net Folks, here is something I wrote some time ago on a very related subject. The last paragraph actually answers the question: To my mind it is quite OK to "reserve" a small amount of address space by rounding up. The emphasis here is on *small* in absolute terms. Enjoy Daniel CIDR Assignment Strategy Previously the RIPE NCC has recommended IRs to reserve some address space contiguous to assigned address space for future expansion. The reasoning was that this would further aggregation and keep the routing table sizes down in the long term, while being slightly inefficient on address space usage in the short term. However experience has shown that the address space usage problems created by those reservations outweigh the possible aggregation benefits. If a block of equal size to the one actually assigned is reserved, address space usage is halved at the expense of doubled routing table size. Relatively speaking this looks like a good tradeoff. In absolute terms however substantial amounts of address space are traded in for 1 (in words: one) additional CIDR route. If no reser- vation were made at all and more address space is needed then another non-contiguous block of appropriate size can always be assigned. Since there are now two blocks these can be aggregated into two routes instead of the one which would have resulted if a suitable reservation had been made. Note that this small absolute gain can only be realised if the reserved space indeed fits the need. The reserved space not only decreases address space usage but also creates fragmentation of the address space which makes it difficult to find block of appropriate size for new requests. Considering this it does not make sense to reserve anything but very small amounts of address space or unused parts of CIDR blocks. Thus the current recommendation is to reserve only address space that is needed to "round" the requested space to a suitable block boundary. - - - - - - - - - - - - - - - - - From list-admin Mon Apr 11 08:58:56 1994 Received: (pam@localhost) by merit.edu (8.6.8.1/merit-1.0) id IAA04664 for regional-techs; Mon, 11 Apr 1994 08:58:56 -0400 Date: Mon, 11 Apr 1994 08:58:56 -0400 From: Pam Ciesla Message-Id: <199404111258.IAA04664@merit.edu> To: regional-techs Subject: Meeting June 2 & 3 Due to the holiday, other meetings and meeting space accommodations the Regional Techs Meeting will be June 2 & 3. More info will be sent at a later date. To register for the meeting please send e-mail to "NSF-seminar@merit.edu. Thanks Pam Ciesla - - - - - - - - - - - - - - - - - From list-admin Mon Apr 11 09:48:13 1994 Received: (pam@localhost) by merit.edu (8.6.8.1/merit-1.0) id JAA08945 for regional-techs; Mon, 11 Apr 1994 09:48:13 -0400 Date: Mon, 11 Apr 1994 09:48:13 -0400 From: Pam Ciesla Message-Id: <199404111348.JAA08945@merit.edu> To: regional-techs Subject: June 2 & 3 Meeting The Regional Techs Meeting to be held June 2 & 3 will be in Ann Arbor, MI Pam - - - - - - - - - - - - - - - - - From list-admin Mon Apr 11 13:32:16 1994 Received: (dsj@localhost) by merit.edu (8.6.8.1/merit-1.0) id NAA29008; Mon, 11 Apr 1994 13:32:16 -0400 Date: Mon, 11 Apr 1994 13:32:16 -0400 From: "Dale S. Johnson" Message-Id: <199404111732.NAA29008@merit.edu> To: bgpd, regional-techs Subject: 493 Nets in 93 Aggregates FYI: CIDR Squeezings Report: 493 Nets in 93 Aggregates -------------------------------------------------- As of last night's Offnet data, AS690 had: 93 Total Aggregates configured. 78 of these were Top-Level Aggregates (not nested in another aggregate). 53 of these were announced to AS690 as of yesterday. 46 of those have at least one subnet configured (the other 7 may be saving. the Internet future subnet announcements). 21 have stopped announcing at least one configured more specific route. 13 have stopped announcing half of their configured more specific routes. 11 have stopped announcing most (80%) of their more specific routes. This produces a total CIDR removal of 493 more specific net announcements. 417 from top-level aggregates seen on AS690. 76 from top-level aggregates not seen on AS690 yesterday (though they may be routed by more-specific aggregates). -------------------------------------------------- Top-Level Configd Not Routed Orig AS690 Aggregate Nets=Routed+Now+Withdrawn AS Announcement List +129.240/15 2 0 0 2 100% 224 1:1800 2:1879 3:1133 4:1240 + +130.232/15 2 0 2 0 0% 1741 1:1800 2:1879 3:1133 4:1240 + +145.0/9 30 1 29 0 0% 1103 1:1800 2:1133 3:1674 4:1240 + 145.128/10 0 0 0 0 0% 1103 1:1800 2:1133 3:1674 4:1240 145.192/11 0 0 0 0 0% 1103 1:1800 2:1133 3:1674 4:1240 +158.36/14 4 0 0 4 100% 224 1:1800 2:1879 3:1133 4:1240 + 171.64/15 1 1 0 0 0% 200 1:200 2:201 192.32/16 52 4 48 0 0% 560 1:560 2:701 +192.87/16 60 11 47 2 4% 1103 1:1800 2:1133 3:1674 4:1240 + +192.108.196/23 2 0 2 0 0% 1882 1:1800 2:1879 3:1133 4:1240 + +192.108.198/23 2 1 1 0 0% 1880 1:1800 2:1879 3:1133 4:1240 + +192.108.200/21 8 3 2 3 60% 1880 1:1800 2:1879 3:1133 4:1240 + 192.108.208/22 4 4 0 0 0% 1880 1:1800 2:1879 3:1133 4:1240 +192.108.212/23 2 2 0 0 0% 1880 1:1800 2:1879 3:1133 4:1240 + +192.121.86/23 1 1 0 0 0% 2836 1:1800 2:1879 3:1133 4:1240 + 192.147.160/20 15 0 14 1 6% 685 1:685 2:73 3:101 +192.150.52/22 4 3 1 0 0% 204 1:204 2:1206 + +192.204/16 114 31 78 5 6% 204 1:204 2:1206 + +192.212/16 201 69 0 132 100% 1740 1:1740 + +192.215/16 122 51 70 1 1% 1740 1:1740 + +192.216/16 154 34 120 0 0% 200 1:200 2:201 + +192.220/16 93 12 76 5 6% 685 1:685 2:73 3:101 + +192.250.24/22 4 0 4 0 0% 1890 1:701 2:1800 + +193.4/16 29 1 0 28 100% 1850 1:1800 2:1879 3:1133 4:1240 + +193.10.6/23 0 0 0 0 0% 2836 1:1800 2:1879 3:1133 4:1240 + +193.44.24/22 1 1 0 0 0% 2836 1:1800 2:1879 3:1133 4:1240 + 193.51.24/22 4 0 4 0 0% 1717 1:1800 2:1240 3:1133 4:1674 193.55.240/23 2 1 0 1 100% 1717 1:1800 2:1240 3:1133 4:1674 +193.67.128/22 4 0 4 0 0% 1890 1:701 2:1800 + +193.72/16 91 35 56 0 0% 1836 1:701 2:1800 + +193.78.32/21 8 0 8 0 0% 1890 1:701 2:1800 + +193.78.72/22 3 0 3 0 0% 1890 1:701 2:1800 + +193.78.104/22 4 0 4 0 0% 1890 1:701 2:1800 + +193.78.120/21 4 0 4 0 0% 1890 1:701 2:1800 + +193.134.216/21 8 8 0 0 0% 559 1:1133 2:1674 3:1800 + 193.134.240/21 8 8 0 0 0% 559 1:1133 2:1674 3:1800 +193.156/15 45 12 0 33 100% 224 1:1800 2:1879 3:1133 4:1240 + +193.219.32/19 0 0 0 0 0% 2847 1:1800 2:1879 3:1133 4:1240 + +194.12.128/21 8 8 0 0 0% 513 1:1133 2:1674 3:1800 + +194.47/16 0 0 0 0 0% 2846 1:1800 2:1879 3:1133 4:1240 + 198.6.252/22 2 0 2 0 0% 701 1:701 2:702 +198.30/16 190 24 165 1 0% 600 1:600 2:1800 + +198.31/16 91 39 52 0 0% 200 1:200 2:201 + +198.55.8/21 8 0 8 0 0% 204 1:204 2:1206 + 198.59/16 96 15 73 8 9% 209 1:209 2:210 198.60/16 95 23 69 3 4% 210 1:210 2:209 198.63/16 0 0 0 0 0% 114 1:114 198.64/15 169 127 41 1 2% 114 1:114 +198.66/16 1 0 0 1 100% 114 1:114 + +198.84.4/22 0 0 0 0 0% 701 1:701 2:702 + 198.92/14 300 204 43 53 55% 200 1:200 2:201 +198.104/16 21 8 11 2 15% 685 1:685 2:73 3:101 + +198.105.232/22 4 3 1 0 0% 685 1:685 2:73 3:101 + +198.106/16 6 0 2 4 66% 685 1:685 2:73 3:101 + +198.107/16 20 15 5 0 0% 685 1:685 2:73 3:101 + +198.136.8/21 8 0 8 0 0% 204 1:204 2:1206 + +198.213/16 27 3 24 0 0% 3354 1:114 + 198.214/15 0 0 0 0 0% 3354 1:114 198.216/16 8 4 4 0 0% 3354 1:114 +198.234/16 70 17 53 0 0% 600 1:600 2:1800 + +198.236/15 117 73 42 2 4% 685 1:685 2:73 3:101 + 198.238/15 0 0 0 0 0% 685 1:685 2:73 3:101 198.243/16 37 6 31 0 0% 209 1:209 2:210 +198.253/16 34 4 0 30 100% 22 1:22 + +199.0/16 75 12 1 62 98% 1239 1:1800 2:1240 + +199.1/16 15 4 0 11 100% 1239 1:1240 2:1800 + +199.2/16 68 13 0 55 100% 1239 1:1240 2:1800 + +199.3/16 70 38 0 32 100% 1239 1:1800 2:1240 + +199.18/16 83 17 64 2 3% 600 1:600 2:1800 + 199.35/16 199 68 122 9 6% 2551 1:2551 199.44.0/17 0 0 0 0 0% 3447 1:1800 2:1240 199.54/15 0 0 0 0 0% 2699 1:274 2:60 199.104/16 2 2 0 0 0% 210 1:210 2:209 +199.108/16 0 0 0 0 0% 1740 1:1740 + 199.117/16 12 5 7 0 0% 209 1:209 2:210 +199.124.8/21 0 0 0 0 0% 22 1:22 + +199.182/16 0 0 0 0 0% 2551 1:2551 + 199.183/16 0 0 0 0 0% 2551 1:2551 Legend: Aggregates that were seen on AS690 yesterday are marked with "+" at the beginning and end of the line "Top-Level Aggregates" are those not included by another aggregate "Configured Nets" = # of more specific nets configured for that aggregate "Not Routed" = # of more specific nets for that aggregate which have not been announced to AS690 anytime after March 1 ("silent nets") "Routed Now" = # of more specific nets routed as of yesterday "Withdrawn" = # of more specific nets for that aggregate which have been announced after March 1, but were gone by yesterday "%" = (# Withdrawn) / (# Routed + # Withdrawn) "Orig AS" = "Home AS" according to the PRDB. Please have us update this via a NACR if we have a wrong value. "AS690 Announcement List" - Metrics and Announcers to AS 690 This report is published daily in merit.edu:pub/nsfnet/cidr/cidr_savings. See merit.edu:pub/nsfnet/cidr/nestings.announced for the full listings. - - - - - - - - - - - - - - - - - From list-admin Mon Apr 11 14:39:29 1994 Received: from bsd.stupi.se (Bsd.Stupi.SE [192.108.198.10]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id OAA05258; Mon, 11 Apr 1994 14:39:22 -0400 Received: by bsd.stupi.se (5.67/1.37) id AA07006; Mon, 11 Apr 94 20:39:11 +0200 Date: Mon, 11 Apr 94 20:39:08 MET DST From: Peter Lothberg To: yakov@watson.ibm.com Cc: dsj@merit.edu, bgpd@merit.edu, regional-techs@merit.edu Subject: Re: 493 Nets in 93 Aggregates In-Reply-To: Your message of Mon, 11 Apr 94 14:06:19 EDT Message-Id: > May I suggest that it would be quite useful if you'll agree........ > Yakov. May I suggest that we inherit some of the techniques from the phone-marketing people, and actively go after people that could reduce their routing announcements by using CDIR? ""BGP table version is 1239369, main routing table version 1239369 20244 network entries (51946 paths) using 3611880 bytes of memory 1357 BGP path attribute entries using 127396 bytes of memory "" -Peter - - - - - - - - - - - - - - - - - From list-admin Mon Apr 11 14:47:14 1994 Received: from watson.ibm.com (watson.ibm.com [129.34.139.4]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id OAA06168; Mon, 11 Apr 1994 14:47:13 -0400 From: yakov@watson.ibm.com Message-Id: <199404111847.OAA06168@merit.edu> Received: from YKTVMV by watson.ibm.com (IBM VM SMTP V2R3) with BSMTP id 6189; Mon, 11 Apr 94 14:47:14 EDT Date: Mon, 11 Apr 94 14:46:19 EDT To: roll@stupi.se cc: dsj@merit.edu, bgpd@merit.edu, regional-techs@merit.edu Subject: 493 Nets in 93 Aggregates Ref: Your note of Mon, 11 Apr 94 20:39:08 MET DST Peter, >May I suggest that we inherit some of the techniques from the >phone-marketing people, and actively go after people that >could reduce their routing announcements by using CIDR ? One useful step in this direction would be identify individual sites that have a large block of contiguous Class C networks, and then go after these sites first. This would allow us to maximize the "return on investment". Yakov. P.S. As a matter of fact, I wonder whether we can get a list of sites that have Class C networks sorted (in descreasing order) by the number of contiguous Class C networks assigned to a site. - - - - - - - - - - - - - - - - - From list-admin Mon Apr 11 14:06:48 1994 Received: from watson.ibm.com (watson.ibm.com [129.34.139.4]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id OAA02310; Mon, 11 Apr 1994 14:06:47 -0400 From: yakov@watson.ibm.com Message-Id: <199404111806.OAA02310@merit.edu> Received: from YKTVMV by watson.ibm.com (IBM VM SMTP V2R3) with BSMTP id 5249; Mon, 11 Apr 94 14:06:48 EDT Date: Mon, 11 Apr 94 14:06:19 EDT To: dsj@merit.edu, bgpd@merit.edu, regional-techs@merit.edu Subject: 493 Nets in 93 Aggregates Ref: Your note of Mon, 11 Apr 1994 13:32:16 -0400 Dale, >CIDR Squeezings Report: 493 Nets in 93 Aggregates >-------------------------------------------------- May I suggest that it would be quite useful if you'll agree to periodically (e.g. once a week or once every other week) to post a report summarizing the progress of CIDR-ization of the Internet. Yakov. - - - - - - - - - - - - - - - - - From list-admin Tue Apr 12 06:27:07 1994 Received: (skw@localhost) by merit.edu (8.6.8.1/merit-1.0) id GAA12095 for nwg; Tue, 12 Apr 1994 06:27:07 -0400 Date: Tue, 12 Apr 1994 06:27:07 -0400 From: "Steven K. Widmayer" Message-Id: <199404121027.GAA12095@merit.edu> To: nwg Subject: Additions to the NSFNET policy-based routing database ------------------------------------------------------------------------------ New format for Metric:AS lists coming later in this and all reports. See 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 Configured Networks 29538 = 29 4611 24800 98 Added Networks 303 = 0 8 285 10 Deleted Networks 8 = 0 2 5 1 IP address Net name Country Priority:AS ---------- -------- ------- ----------- 137.179/16 PGXPRESS C:US 1:600 2:1800 139.160/16 MGLAN C:FR 1:1957 145.232/16 ETAT-DE-VAUD C:CH 1:1133 2:1674 3:1800 157.80/16 IBARAKI-U C:JP 1:1240 2:1800 159.214/16 PECONET C:US 1:2149 2:174 161.136/16 ECMC C:US 1:1800 2:1240 164.71/16 FNET-B3 C:JP 1:2149 2:174 165.30/16 SUNAMERICA C:US 1:1240 2:1800 192.16.188/23 SARA-AGG-4 C:NL 1:1800 2:1133 3:1674 4:1240 192.31.126/23 TU-DELFT-AGG-1 C:NL 1:1800 2:1133 3:1674 4:1240 192.31.128/21 TU-DELFT-AGG-2 C:NL 1:1800 2:1133 3:1674 4:1240 192.42.114/23 SARA-AGG-1 C:NL 1:1800 2:1133 3:1674 4:1240 192.42.120/21 SARA-AGG-2 C:NL 1:1800 2:1133 3:1674 4:1240 192.42.128/23 SARA-AGG-3 C:NL 1:1800 2:1133 3:1674 4:1240 192.56.191/24 HP11 C:US 1:1957 192.70.218/24 MARATHON C:US 1:209 2:210 192.71.94/24 STIGBY-LAN C:SE 1:1800 2:1879 3:1133 4:1240 192.106.149/24 MATRICE C:IT 1:1957 192.109.44/24 IFADO-LAN1 C:DE 1:1957 192.109.45/24 IFADO-LAN2 C:DE 1:1957 192.114.141/24 ELRON-NET C:IL 1:2149 2:174 192.114.143/24 ORCKIT-NET C:IL 1:2149 2:174 192.121.175/24 SWNETX C:SE 1:1957 192.125.1/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.2/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.3/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.4/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.5/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.6/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.7/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.8/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.9/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.10/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.11/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.12/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.13/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.14/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.15/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.16/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.17/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.18/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.19/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.20/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.21/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.22/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.23/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.24/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.25/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.26/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.27/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.28/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.29/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.30/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.31/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.32/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.33/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.34/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.35/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.36/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.37/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.38/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.39/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.40/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.125.83/24 HARTMANN C:DE 1:1324 2:1800 3:1240 4:1133 192.157.169/24 INFOLAN47 C:US 1:2149 2:174 192.172.241/24 SII-INTERNET C:JP 1:2149 2:174 192.204.188/24 TRINET C:US 1:204 2:1206 192.204.189/24 TRINET-2 C:US 1:204 2:1206 192.217.86/24 CICNET-BLOCK C:US 1:1225 2:266 3:267 192.218.140/24 MELCO-IPNET4 C:JP 1:2149 2:174 192.244.21/24 NIJLNET2 C:JP 1:1240 2:1800 192.245.148/24 CERIST1 C:DZ 1:1800 2:1133 3:1674 4:1240 193.42.13/24 CNR-INTL-TEST C:IT 1:1800 2:1133 3:1674 4:1240 193.44.172/24 UDAC-NETC-2 C:SE 1:1957 193.56.37/24 FR-AERO-MU C:FR 1:1957 193.60.144/24 DERBY-NET-C-60-144 C:GB 1:1800 2:1133 3:1240 193.60.145/24 DERBY-NET-C-60-145 C:GB 1:1800 2:1133 3:1240 193.60.146/24 DERBY-NET-C-60-146 C:GB 1:1800 2:1133 3:1240 193.60.147/24 DERBY-NET-C-60-147 C:GB 1:1800 2:1133 3:1240 193.60.148/24 DERBY-NET-C-60-148 C:GB 1:1800 2:1133 3:1240 193.60.149/24 DERBY-NET-C-60-149 C:GB 1:1800 2:1133 3:1240 193.60.150/24 DERBY-NET-C-60-150 C:GB 1:1800 2:1133 3:1240 193.60.151/24 DERBY-NET-C-60-151 C:GB 1:1800 2:1133 3:1240 193.62.84/24 DERBY-NETC C:GB 1:1800 2:1133 3:1240 193.62.85/24 DERBY-NETD C:GB 1:1800 2:1133 3:1240 193.62.86/24 DERBY-NETE C:GB 1:1800 2:1133 3:1240 193.62.87/24 DERBY-NETF C:GB 1:1800 2:1133 3:1240 193.63.40/24 DERBY-NET9 C:GB 1:1800 2:1133 3:1240 193.63.41/24 DERBY-NET0 C:GB 1:1800 2:1133 3:1240 193.63.42/24 DERBY-NETA C:GB 1:1800 2:1133 3:1240 193.63.43/24 DERBY-NETB C:GB 1:1800 2:1133 3:1240 193.64.206/24 FIMNET1 C:FI 1:701 2:1800 193.70.125/24 ENIDATA-C-BLOCK C:IT 1:1957 193.73.218/24 NEXUS-AG C:CH 1:701 2:1800 193.80.185/24 TELEDATA C:AT 1:701 2:1800 193.88.72/24 NETMAN C:DK 1:1957 193.89.6/24 FOA-NET C:DK 1:1957 193.89.32/24 CAPSYS C:DK 1:1957 193.100.31/24 LEYKAM-HH C:FR 1:1957 193.104.1/24 FR-LAISSUS C:FR 1:1957 193.104.14/24 FR-AUSPEX C:FR 1:1957 193.112.232/24 CGI-NET C:GB 1:1957 193.120.208/24 BAKERRYAN-2 C:IE 1:1957 193.120.246/24 GALLIMAUFRY-NET C:IE 1:1957 193.124.228/24 UARNET-C-124-228 C:UA 1:1800 2:1133 3:1240 193.124.229/24 UARNET-C-124-229 C:UA 1:1800 2:1133 3:1240 193.141.50/24 BULLDE C:DE 1:1324 2:1800 3:1240 4:1133 193.141.246/24 CAPDEBISDA2 C:DE 1:1324 2:1800 3:1240 4:1133 193.141.247/24 CAPDEBISDA3 C:DE 1:1324 2:1800 3:1240 4:1133 193.175.27/24 RHEIN-NET2 C:DE 1:293 2:291 193.194.64/24 CERIST2-NET C:DZ 1:1800 2:1133 3:1674 4:1240 193.198.4/24 XNTNET-C-198-4 C:HR 1:1800 2:1133 3:1240 193.198.5/24 XNTNET-C-198-5 C:HR 1:1800 2:1133 3:1240 193.198.6/24 XNTNET-C-198-6 C:HR 1:1800 2:1133 3:1240 193.198.7/24 XNTNET-C-198-7 C:HR 1:1800 2:1133 3:1240 193.198.28/24 DINERS2-NET C:HR 1:1800 2:1133 3:1240 193.198.40/24 HCK-NET C:HR 1:1800 2:1133 3:1240 193.198.41/24 SKOK-NET C:HR 1:1800 2:1133 3:1240 193.198.55/24 DINERS-NET-C-198-55 C:HR 1:1800 2:1133 3:1240 193.198.56/24 DINERS-NET-C-198-56 C:HR 1:1800 2:1133 3:1240 193.212.48/24 ETHCINET-C-212-48 C:NO 1:1800 2:1879 3:1133 4:1240 193.212.49/24 ETHCINET-C-212-49 C:NO 1:1800 2:1879 3:1133 4:1240 193.212.50/24 ETHCINET-C-212-50 C:NO 1:1800 2:1879 3:1133 4:1240 193.212.51/24 ETHCINET-C-212-51 C:NO 1:1800 2:1879 3:1133 4:1240 193.212.52/24 ETHCINET-C-212-52 C:NO 1:1800 2:1879 3:1133 4:1240 193.212.53/24 ETHCINET-C-212-53 C:NO 1:1800 2:1879 3:1133 4:1240 193.212.54/24 ETHCINET-C-212-54 C:NO 1:1800 2:1879 3:1133 4:1240 193.212.55/24 ETHCINET-C-212-55 C:NO 1:1800 2:1879 3:1133 4:1240 193.235.128/24 SE-ELEKTA C:SE 1:1957 194.14.49/24 SE-ELEKTA C:SE 1:1957 194.15.144/24 CLS2-NET C:DE 1:1957 194.44.3/24 KCN-DIALUP-NET C:UA 1:701 2:1800 196.3.32/24 SYNTEX C:US 1:1957 198.6.200/24 IMATEK C:US 1:701 2:702 198.6.202/24 ICI-C C:US 1:1957 198.6.220/24 AKPHARMA C:US 1:1957 198.6.221/24 SCII-NET C:US 1:701 2:702 198.6.245/24 ERINET C:US 1:701 2:702 198.6.248/24 UUNETCBLK6 C:US 1:1957 198.6.249/24 UUNETCBLK6 C:US 1:1957 198.17.126/24 TSCNET C:US 1:2149 2:174 198.59.207/24 NETBLK-WESTNET C:US 1:1800 2:1240 3:209 4:210 198.59.208/24 NETBLK-WESTNET C:US 1:1800 2:1240 3:209 4:210 198.60.186/24 MOHAVE-CC C:US 1:210 2:209 198.81.204/24 GARTNER-DMZ C:US 1:1324 198.83.29/24 ANS-C-BLOCK C:US 1:1662 198.83.30/24 ANS-C-BLOCK C:US 1:1662 198.83.31/24 ANS-C-BLOCK C:US 1:1662 198.83.32/24 ANS-C-BLOCK C:US 1:1662 198.99.131/24 MUSTNET2 C:US 1:1957 198.99.132/24 MUSTNET3 C:US 1:1957 198.99.133/24 MUSTNET4 C:US 1:1957 198.102.26/24 GTE-SPACENET21 C:US 1:86 2:279 198.114.33/24 LOTUS-33 C:US 1:560 2:701 198.115.92/24 ARIESSYS C:US 1:560 2:701 198.137.176/24 CRSS C:US 1:1800 2:1240 198.137.177/24 CRSS C:US 1:1800 2:1240 198.137.178/24 CRSS C:US 1:1800 2:1240 198.138.212/24 JVNC-C1-NET213 C:US 1:1957 198.145.64/24 WDN-198 C:US 1:1957 198.176.8/21 SEGAOA-BLK C:US 1:1240 2:1800 198.176.194/24 SLCCORP2 C:US 1:210 2:209 198.176.195/24 SLCCORP2 C:US 1:210 2:209 198.176.196/24 SLCCORP2 C:US 1:210 2:209 198.176.197/24 SLCCORP2 C:US 1:210 2:209 198.177.146/24 ADINA-NET C:US 1:2149 2:174 198.189.22/24 CSUNET-NORTH C:US 1:2150 2:200 3:201 198.189.92/24 CRSS C:US 1:1800 2:1240 198.200.153/24 HUD-C C:US 1:86 2:279 198.202.128/24 SSA-C C:US 1:1225 2:267 3:266 198.209/16 MORENET-C C:US 1:1800 2:1240 198.234.0/24 NETBLK-OHIO-NET C:US 1:1957 198.234.2/24 NETBLK-OHIO-NET C:US 1:1957 198.234.15/24 NETBLK-OHIO-NET C:US 1:1957 199.0.208/24 NPR C:US 1:1800 2:1240 199.0.209/24 NPR C:US 1:1800 2:1240 199.0.210/24 NPR C:US 1:1800 2:1240 199.0.211/24 NPR C:US 1:1800 2:1240 199.0.212/24 NPR C:US 1:1800 2:1240 199.0.213/24 NPR C:US 1:1800 2:1240 199.0.214/24 NPR C:US 1:1800 2:1240 199.0.215/24 NPR C:US 1:1800 2:1240 199.4.64/18 NBN-NET-C-AGGR C:US 1:1240 2:1800 199.10.233/24 NET-ACSC C:US 1:19 2:568 199.26.183/24 TSCNET-C-26-183 C:US 1:2149 2:174 199.26.184/24 TSCNET-C-26-184 C:US 1:2149 2:174 199.33.167/24 WNYHSC C:US 1:1800 2:1240 199.33.168/24 BGH-C-33-168 C:US 1:1800 2:1240 199.33.169/24 BGH-C-33-169 C:US 1:1800 2:1240 199.33.170/24 BGH-C-33-170 C:US 1:1800 2:1240 199.33.171/24 BGH-C-33-171 C:US 1:1800 2:1240 199.33.172/24 BGH-C-33-172 C:US 1:1800 2:1240 199.33.173/24 BGH-C-33-173 C:US 1:1800 2:1240 199.45.140/24 COOP-NET C:US 1:1240 2:1800 199.45.141/24 COOP-NET C:US 1:1240 2:1800 199.45.142/24 COOP-NET C:US 1:1240 2:1800 199.45.143/24 COOP-NET C:US 1:1240 2:1800 199.45.144/24 COOP-NET C:US 1:1240 2:1800 199.45.145/24 COOP-NET C:US 1:1240 2:1800 199.45.146/24 COOP-NET C:US 1:1240 2:1800 199.45.147/24 COOP-NET C:US 1:1240 2:1800 199.45.148/24 COOP-NET C:US 1:1240 2:1800 199.45.149/24 COOP-NET C:US 1:1240 2:1800 199.79.146/24 FILESHOP-146 C:US 1:1740 199.79.239/24 INETONRAMP C:US 1:1240 2:1800 199.90.225/24 STATE-NC-US C:US 1:1329 199.98.141/24 PSINET-C5 C:US 1:2149 2:174 199.98.149/24 PSINET-C5 C:US 1:2149 2:174 199.125.128/17 DIGEX-BLK6 C:US 1:2548 199.165.135/24 NET-PD-NET C:US 1:1240 2:1800 199.170.20/24 UUCBLK170-173 C:US 1:1957 199.170.54/24 UUCBLK170-173 C:US 1:1957 199.170.68/24 SHAYSNET C:US 1:701 2:702 199.181.150/24 PANGEN C:US 1:1240 2:1800 199.225.12/24 CHCS-FTIRWIN-C-225-12 C:US 1:568 2:19 199.225.13/24 CHCS-FTIRWIN-C-225-13 C:US 1:568 2:19 202.12.8/24 WNI1 C:JP 1:2149 2:174 202.14.137/24 NET-MDAOZ C:AU 1:372 2:297 202.33.10/24 MLGNET C:JP 1:2149 2:174 202.33.13/24 KCLNET C:JP 1:2149 2:174 202.35.192/24 NCUNET C:JP 1:1240 2:1800 202.35.193/24 NCUNET C:JP 1:1240 2:1800 202.35.194/24 NCUNET C:JP 1:1240 2:1800 202.35.195/24 NCUNET C:JP 1:1240 2:1800 202.35.196/24 NCUNET C:JP 1:1240 2:1800 202.35.197/24 NCUNET C:JP 1:1240 2:1800 202.35.198/24 NCUNET C:JP 1:1240 2:1800 202.35.199/24 NCUNET C:JP 1:1240 2:1800 202.35.200/24 NCUNET C:JP 1:1240 2:1800 202.35.201/24 NCUNET C:JP 1:1240 2:1800 202.35.202/24 NCUNET C:JP 1:1240 2:1800 202.35.203/24 NCUNET C:JP 1:1240 2:1800 202.35.204/24 NCUNET C:JP 1:1240 2:1800 202.35.205/24 NCUNET C:JP 1:1240 2:1800 202.35.206/24 NCUNET C:JP 1:1240 2:1800 202.35.207/24 NCUNET C:JP 1:1240 2:1800 202.35.208/24 NCUNET C:JP 1:1240 2:1800 202.35.209/24 NCUNET C:JP 1:1240 2:1800 202.35.210/24 NCUNET C:JP 1:1240 2:1800 202.35.211/24 NCUNET C:JP 1:1240 2:1800 202.35.212/24 NCUNET C:JP 1:1240 2:1800 202.35.213/24 NCUNET C:JP 1:1240 2:1800 202.35.214/24 NCUNET C:JP 1:1240 2:1800 202.35.215/24 NCUNET C:JP 1:1240 2:1800 202.35.216/24 NCUNET C:JP 1:1240 2:1800 202.35.217/24 NCUNET C:JP 1:1240 2:1800 202.35.218/24 NCUNET C:JP 1:1240 2:1800 202.35.219/24 NCUNET C:JP 1:1240 2:1800 202.35.220/24 NCUNET C:JP 1:1240 2:1800 202.35.221/24 NCUNET C:JP 1:1240 2:1800 202.35.222/24 NCUNET C:JP 1:1240 2:1800 202.35.223/24 NCUNET C:JP 1:1240 2:1800 202.252.64/24 K-MSNET C:JP 1:1240 2:1800 202.252.65/24 K-MSNET C:JP 1:1240 2:1800 202.252.66/24 K-MSNET C:JP 1:1240 2:1800 202.252.67/24 K-MSNET C:JP 1:1240 2:1800 202.252.68/24 K-MSNET C:JP 1:1240 2:1800 202.252.69/24 K-MSNET C:JP 1:1240 2:1800 202.252.70/24 K-MSNET C:JP 1:1240 2:1800 202.252.71/24 K-MSNET C:JP 1:1240 2:1800 202.252.72/24 K-MSNET C:JP 1:1240 2:1800 202.252.73/24 K-MSNET C:JP 1:1240 2:1800 202.252.74/24 K-MSNET C:JP 1:1240 2:1800 202.252.75/24 K-MSNET C:JP 1:1240 2:1800 202.252.76/24 K-MSNET C:JP 1:1240 2:1800 202.252.77/24 K-MSNET C:JP 1:1240 2:1800 202.252.78/24 K-MSNET C:JP 1:1240 2:1800 202.252.79/24 K-MSNET C:JP 1:1240 2:1800 202.252.80/24 K-MSNET C:JP 1:1240 2:1800 202.252.81/24 K-MSNET C:JP 1:1240 2:1800 202.252.82/24 K-MSNET C:JP 1:1240 2:1800 202.252.83/24 K-MSNET C:JP 1:1240 2:1800 202.252.84/24 K-MSNET C:JP 1:1240 2:1800 202.252.85/24 K-MSNET C:JP 1:1240 2:1800 202.252.86/24 K-MSNET C:JP 1:1240 2:1800 202.252.87/24 K-MSNET C:JP 1:1240 2:1800 202.252.88/24 K-MSNET C:JP 1:1240 2:1800 202.252.89/24 K-MSNET C:JP 1:1240 2:1800 202.252.90/24 K-MSNET C:JP 1:1240 2:1800 202.252.91/24 K-MSNET C:JP 1:1240 2:1800 202.252.92/24 K-MSNET C:JP 1:1240 2:1800 202.252.93/24 K-MSNET C:JP 1:1240 2:1800 202.252.94/24 K-MSNET C:JP 1:1240 2:1800 202.252.95/24 K-MSNET C:JP 1:1240 2:1800 203.2.122/24 NET-POWERUP-AU C:AU 1:372 2:297 203.2.192/24 OZEMAIL-AU C:AU 1:372 2:297 203.2.193/24 OZEMAIL-AU C:AU 1:372 2:297 203.2.194/24 OZEMAIL-AU C:AU 1:372 2:297 203.2.195/24 OZEMAIL-AU C:AU 1:372 2:297 203.4.144/24 AFTRS-AU C:AU 1:372 2:297 203.4.145/24 CRCAMET-AU C:AU 1:372 2:297 203.4.146/24 MQ-DICT-AU C:AU 1:372 2:297 203.4.147/24 MQ-GSM-AU C:AU 1:372 2:297 203.4.148/24 BRISNET-AU C:AU 1:372 2:297 203.4.149/24 BRISNET-AU C:AU 1:372 2:297 203.4.150/24 TRIAD-AU C:AU 1:372 2:297 203.4.151/24 MUDLARK-AU C:AU 1:372 2:297 203.4.161/24 BALLBASEHOSP-AU C:AU 1:372 2:297 203.4.164/24 PETERMAC-AU C:AU 1:372 2:297 203.4.165/24 PETERMAC-AU C:AU 1:372 2:297 203.4.166/24 PETERMAC-AU C:AU 1:372 2:297 203.4.167/24 PETERMAC-AU C:AU 1:372 2:297 203.4.174/24 NINENET-AU C:AU 1:372 2:297 Deletions: --153.100/16 XLINKFAIR C:DE 1:1324 2:1800 3:1240 4:1133 --155.105/16 EINEV C:CH 1:1133 2:1674 3:1800 --192.204.248/22 PREPNET-C C:US 1:574 --192.204.248/24 PREPNET-C C:US 1:574 --192.204.249/24 PREPNET-C C:US 1:574 --192.204.250/24 PREPNET-C C:US 1:574 --192.204.251/24 PREPNET-C C:US 1:574 --198.87.2/24 MSU-MITN C:US 1:266 2:1225 3:267 Expanded listing, sorted by country, then by organization: ========================================================== Algeria ------- Research Center on Scientific and Technological Information, Rur des trois Freres Aissiou, Ben-Aknoun, BP-47 Hydra, Algiers, ALGERIA 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1674 CERN/DANTE 4:1240 ICM-Pacific -------------- 192.245.148/24 CERIST1 (DZ) 193.194.64/24 CERIST2-NET (DZ) Australia --------- Ballarat Base Hospital, Cnr Stuart/Drummond Street, Ballarat, VIC, 3353, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 203.4.161/24 BALLBASEHOSP-AU (AU) Brisbane Public Access Network Association Inc, 24 Thornlaw Street, Durack, QLD, 4077, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 203.4.148/24 BRISNET-AU (AU) 203.4.149/24 BRISNET-AU (AU) MacDonald Dettwiler, Level 7, 146 Arthur Street, North Sydney, NSW, 2060, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------- 202.14.137/24 NET-MDAOZ (AU) Macquarie University, Herring Road, North Ryde, NSW, 2109, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 203.4.144/24 AFTRS-AU (AU) Macquarie University, Office of Computing Services, Herring Road, North Ryde, NSW, 2109, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 203.4.145/24 CRCAMET-AU (AU) 203.4.146/24 MQ-DICT-AU (AU) 203.4.147/24 MQ-GSM-AU (AU) Nine Network Australia, 24 Artarmon Road, Willoughby, NSW, 2068, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 203.4.174/24 NINENET-AU (AU) OZ-E-MAIL Pty Ltd, Level One 39 Herbert Street, St Leonards, 2065, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 203.2.192/24 OZEMAIL-AU (AU) OZ-E-MAIL Pty Ltd, Level One 39 Herbert Street, St Leonards, NSW, 2065, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 203.2.193/24 OZEMAIL-AU (AU) 203.2.194/24 OZEMAIL-AU (AU) 203.2.195/24 OZEMAIL-AU (AU) Peter MacCallum Cancer Institute, 481 Lt. Lonsdale Street, Melbourne, VIC, 3000, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 203.4.164/24 PETERMAC-AU (AU) 203.4.165/24 PETERMAC-AU (AU) 203.4.166/24 PETERMAC-AU (AU) 203.4.167/24 PETERMAC-AU (AU) Peter Williams, 55/215 Bridge Road, Glebe, NSW, 2037, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 203.4.151/24 MUDLARK-AU (AU) Power Up, PO Box 295,Cannon Hill, Brisbane, QLD, 4170, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 203.2.122/24 NET-POWERUP-AU (AU) Triad Software Pty Ltd, Ground Floor, 41 McLaren Street, North Sydney, NSW, 2060, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 203.4.150/24 TRIAD-AU (AU) Austria ------- Teledata Consulting und Systemmanagement GesmbH, Vorarlberger Wirtschaftspark, A-6840 Goetzis, AUSTRIA 1:701 Alternet 2:1800 ICM-Atlantic ------------- 193.80.185/24 TELEDATA (AT) Croatia ------- Diners, Praska 5, Zagreb 41020, CROATIA 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific ------------- 193.198.28/24 DINERS2-NET (HR) 193.198.55/24 DINERS-NET-C-198-55 (HR) 193.198.56/24 DINERS-NET-C-198-56 (HR) Hrvatski Crveni Kriz, Crvenog kriza 14, Zagreb 41000, CROATIA 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific ------------- 193.198.40/24 HCK-NET (HR) Skolska knjiga d.d., Masarykova 28, 41001 Zagreb, p.p. 1039, CROATIA 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific ------------- 193.198.41/24 SKOK-NET (HR) Telecommunication Systems and Equipment Company, p.o., Nikola Tesla, Krapinska 45, 41000 Zagreb, CROATIA 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific ------------ 193.198.4/24 XNTNET-C-198-4 (HR) 193.198.5/24 XNTNET-C-198-5 (HR) 193.198.6/24 XNTNET-C-198-6 (HR) 193.198.7/24 XNTNET-C-198-7 (HR) Denmark ------- Capilex A/S - L'Oreal, Midtager 33, DK-2605 Broendby, DENMARK 1:1957 ANSCIX-AS ------------ 193.89.32/24 CAPSYS (DK) NetMan A/S, Aadalsvej 99, DK-2970 Hoersholm, DENMARK 1:1957 ANSCIX-AS ------------ 193.88.72/24 NETMAN (DK) Pen-Sam, Joergen Knudsensvej 2, DK-3520 Farum, DENMARK 1:1957 ANSCIX-AS ----------- 193.89.6/24 FOA-NET (DK) Finland ------- Finnish Medical Association, M{kel{nkatu 2, FI-00500 HELSINKI, FINLAND 1:701 Alternet 2:1800 ICM-Atlantic ------------- 193.64.206/24 FIMNET1 (FI) France ------ Aerospatiale, Aerodrome de Villacoublay, BP 59, F-78141 Velizy Villacoublay, FRANCE 1:1957 ANSCIX-AS ------------ 193.56.37/24 FR-AERO-MU (FR) Auspex Systems S.A, La Boursidiere RN 186 B.P.10, F-92357 Le Plessis Robinson CEDEX, FRANCE 1:1957 ANSCIX-AS ------------- 193.104.14/24 FR-AUSPEX (FR) Cabinet Francois Laissus, 24 rue Berthollet, F-75005 Paris, FRANCE 1:1957 ANSCIX-AS ------------ 193.104.1/24 FR-LAISSUS (FR) Leykam France, 44, Rue Saint Didier, F-75116 Paris, FRANCE 1:1957 ANSCIX-AS ------------- 193.100.31/24 LEYKAM-HH (FR) Merlin Gerin, Direction des Techniques de l'Information - Service Reseaux, Batiment C, 38050 Grenoble CEDEX 9, FRANCE 1:1957 ANSCIX-AS ---------- 139.160/16 MGLAN (FR) Germany ------- CAP debis GEI GmbH, Elisabetenstr. 35, D-64283 Darmstadt, GERMANY 1:1324 ANS New York City - DNSS 35 2:1800 ICM-Atlantic 3:1240 ICM-Pacific 4:1133 CERN/DANTE -------------- 193.141.246/24 CAPDEBISDA2 (DE) 193.141.247/24 CAPDEBISDA3 (DE) Hartmann & Braun AG, Graefstr. 97, D-60487 Frankfurt am Main, Frankfurt, GERMANY 1:1324 ANS New York City - DNSS 35 2:1800 ICM-Atlantic 3:1240 ICM-Pacific 4:1133 CERN/DANTE ------------ 192.125.1/24 HARTMANN (DE) 192.125.2/24 HARTMANN (DE) 192.125.3/24 HARTMANN (DE) 192.125.4/24 HARTMANN (DE) 192.125.5/24 HARTMANN (DE) 192.125.6/24 HARTMANN (DE) 192.125.7/24 HARTMANN (DE) 192.125.8/24 HARTMANN (DE) 192.125.9/24 HARTMANN (DE) 192.125.10/24 HARTMANN (DE) 192.125.11/24 HARTMANN (DE) 192.125.12/24 HARTMANN (DE) 192.125.13/24 HARTMANN (DE) 192.125.14/24 HARTMANN (DE) 192.125.15/24 HARTMANN (DE) 192.125.16/24 HARTMANN (DE) 192.125.17/24 HARTMANN (DE) 192.125.18/24 HARTMANN (DE) 192.125.19/24 HARTMANN (DE) 192.125.20/24 HARTMANN (DE) 192.125.21/24 HARTMANN (DE) 192.125.22/24 HARTMANN (DE) 192.125.23/24 HARTMANN (DE) 192.125.24/24 HARTMANN (DE) 192.125.25/24 HARTMANN (DE) 192.125.26/24 HARTMANN (DE) 192.125.27/24 HARTMANN (DE) 192.125.28/24 HARTMANN (DE) 192.125.29/24 HARTMANN (DE) 192.125.30/24 HARTMANN (DE) 192.125.31/24 HARTMANN (DE) 192.125.32/24 HARTMANN (DE) 192.125.33/24 HARTMANN (DE) 192.125.34/24 HARTMANN (DE) 192.125.35/24 HARTMANN (DE) 192.125.36/24 HARTMANN (DE) 192.125.37/24 HARTMANN (DE) 192.125.38/24 HARTMANN (DE) 192.125.39/24 HARTMANN (DE) 192.125.40/24 HARTMANN (DE) 192.125.83/24 HARTMANN (DE) Individual Network (Rhein Section), Hoehlenweg 7, Bonn, D-53125, GERMANY 1:293 Energy Science Network (FIX-East) 2:291 Energy Science Network (FIX-West) ------------- 193.175.27/24 RHEIN-NET2 (DE) Institut f. Arbeitsphysiologie an der Universitaet Dortmund, Ardeystrasse 67, D-W-4600 Dortmund 1, GERMANY 1:1957 ANSCIX-AS ------------- 192.109.44/24 IFADO-LAN1 (DE) 192.109.45/24 IFADO-LAN2 (DE) MAZ/CLS, Sternstr. 2, Kiel, Germany, D-24116, GERMANY 1:1957 ANSCIX-AS ------------- 194.15.144/24 CLS2-NET (DE) Softwarehaus BULL AG Langen, Robert-Bosch-Str. 52, D-63225 Langen, GERMANY 1:1324 ANS New York City - DNSS 35 2:1800 ICM-Atlantic 3:1240 ICM-Pacific 4:1133 CERN/DANTE ------------- 193.141.50/24 BULLDE (DE) Ireland ------- 60 Merrion Sqr., Dublin 2, IRELAND 1:1957 ANSCIX-AS -------------- 193.120.208/24 BAKERRYAN-2 (IE) Gallimaufry Ltd, 25 Gilford Park, Sandymount, Dublin 4, IRELAND 1:1957 ANSCIX-AS -------------- 193.120.246/24 GALLIMAUFRY-NET (IE) Israel ------ ELRON, 28,Hacharoshet str, Or-Yehuda, ISRAEL 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI -------------- 192.114.141/24 ELRON-NET (IL) ORCKIT Communications LTd., 38,Nahalat Yitzhak str., Tel-Aviv, 67448, ISRAEL 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI -------------- 192.114.143/24 ORCKIT-NET (IL) Italy ----- CNUCE Pisa, Via Santa Maria, 36, I-56126 Pisa, ITALY 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1674 CERN/DANTE 4:1240 ICM-Pacific ------------ 193.42.13/24 CNR-INTL-TEST (IT) MATRICE, Via Pierlombardo 9, I-20135 Milano, ITALY 1:1957 ANSCIX-AS -------------- 192.106.149/24 MATRICE (IT) Universita' di Genova, DIST, Via Opera Pia 11A, I-16145 Genova, ITALY 1:1957 ANSCIX-AS ------------- 193.70.125/24 ENIDATA-C-BLOCK (IT) Japan ----- Fujitsu Ltd., 1015 Kamikodanaka, Nakahara-ku, 211, JAPAN 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI --------- 164.71/16 FNET-B3 (JP) Ibarki University, 2-1-1 Bunkyo, Mito-shi, Ibaraki 310, JAPAN 1:1240 ICM-Pacific 2:1800 ICM-Atlantic --------- 157.80/16 IBARAKI-U (JP) KINOKUNIYA COMPANY LTD., 38-1, Sakuragaoka, 5-chome, Setagaya-ku, Tokyo, 156, JAPAN 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------ 202.33.13/24 KCLNET (JP) Kagawa Medical School, 1750-1 Ikenobe, Miki-cho, Kita-gun, Kagawa 761-07, JAPAN 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ------------- 202.252.64/24 K-MSNET (JP) 202.252.65/24 K-MSNET (JP) 202.252.66/24 K-MSNET (JP) 202.252.67/24 K-MSNET (JP) 202.252.68/24 K-MSNET (JP) 202.252.69/24 K-MSNET (JP) 202.252.70/24 K-MSNET (JP) 202.252.71/24 K-MSNET (JP) 202.252.72/24 K-MSNET (JP) 202.252.73/24 K-MSNET (JP) 202.252.74/24 K-MSNET (JP) 202.252.75/24 K-MSNET (JP) 202.252.76/24 K-MSNET (JP) 202.252.77/24 K-MSNET (JP) 202.252.78/24 K-MSNET (JP) 202.252.79/24 K-MSNET (JP) 202.252.80/24 K-MSNET (JP) 202.252.81/24 K-MSNET (JP) 202.252.82/24 K-MSNET (JP) 202.252.83/24 K-MSNET (JP) 202.252.84/24 K-MSNET (JP) 202.252.85/24 K-MSNET (JP) 202.252.86/24 K-MSNET (JP) 202.252.87/24 K-MSNET (JP) 202.252.88/24 K-MSNET (JP) 202.252.89/24 K-MSNET (JP) 202.252.90/24 K-MSNET (JP) 202.252.91/24 K-MSNET (JP) 202.252.92/24 K-MSNET (JP) 202.252.93/24 K-MSNET (JP) 202.252.94/24 K-MSNET (JP) 202.252.95/24 K-MSNET (JP) Mitsubishi Electric Corporation, 2-3-3 Marunouchi, Chiyoda-ku, Tokyo, 151, JAPAN 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI -------------- 192.218.140/24 MELCO-IPNET4 (JP) Nagoya City University, 1 Kawasumi, Mizuho-cho, Mizuho-ku, Nagoya-shi, Nagoya 467, JAPAN 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ------------- 202.35.192/24 NCUNET (JP) 202.35.193/24 NCUNET (JP) 202.35.194/24 NCUNET (JP) 202.35.195/24 NCUNET (JP) 202.35.196/24 NCUNET (JP) 202.35.197/24 NCUNET (JP) 202.35.198/24 NCUNET (JP) 202.35.199/24 NCUNET (JP) 202.35.200/24 NCUNET (JP) 202.35.201/24 NCUNET (JP) 202.35.202/24 NCUNET (JP) 202.35.203/24 NCUNET (JP) 202.35.204/24 NCUNET (JP) 202.35.205/24 NCUNET (JP) 202.35.206/24 NCUNET (JP) 202.35.207/24 NCUNET (JP) 202.35.208/24 NCUNET (JP) 202.35.209/24 NCUNET (JP) 202.35.210/24 NCUNET (JP) 202.35.211/24 NCUNET (JP) 202.35.212/24 NCUNET (JP) 202.35.213/24 NCUNET (JP) 202.35.214/24 NCUNET (JP) 202.35.215/24 NCUNET (JP) 202.35.216/24 NCUNET (JP) 202.35.217/24 NCUNET (JP) 202.35.218/24 NCUNET (JP) 202.35.219/24 NCUNET (JP) 202.35.220/24 NCUNET (JP) 202.35.221/24 NCUNET (JP) 202.35.222/24 NCUNET (JP) 202.35.223/24 NCUNET (JP) National Institute of Japanese Literature, 1-16-10 Yutaka-cho, Shinagawa-ku, Tokyo 142, JAPAN 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ------------- 192.244.21/24 NIJLNET2 (JP) Seiko Instrument Inc., 563, Takatsuka shinden, Matsudo-shi, Chiba, 271, JAPAN 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI -------------- 192.172.241/24 SII-INTERNET (JP) TEIJIN SYSTEMS TECHNOLOGY LTD., 10F URBAN-NET YOKOHAMA BLDG., KANAGAWA, 231, JAPAN 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------ 202.33.10/24 MLGNET (JP) Weathernews, Inc., D21, 1-3, Nakase, Mihama-ku, Chiba-shi, 261-01, JAPAN 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ----------- 202.12.8/24 WNI1 (JP) Netherlands ----------- SARA, Kruislaan 415, NL-1098 SJ Amsterdam, NETHERLANDS 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1674 CERN/DANTE 4:1240 ICM-Pacific ------------- 192.16.188/23 SARA-AGG-4 (NL) 192.42.114/23 SARA-AGG-1 (NL) 192.42.120/21 SARA-AGG-2 (NL) 192.42.128/23 SARA-AGG-3 (NL) Technische Universiteit Delft, P.O. Box 354, NL-2600 AJ Delft, NETHERLANDS 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1674 CERN/DANTE 4:1240 ICM-Pacific ------------- 192.31.126/23 TU-DELFT-AGG-1 (NL) 192.31.128/21 TU-DELFT-AGG-2 (NL) Norway ------ CINET AS, Rolf Wickstromsvei 15, P.B. 3 Grefsen, 0409 Oslo, NORWAY 1:1800 ICM-Atlantic 2:1879 EUROPE-RS 3:1133 CERN/DANTE 4:1240 ICM-Pacific ------------- 193.212.48/24 ETHCINET-C-212-48 (NO) 193.212.49/24 ETHCINET-C-212-49 (NO) 193.212.50/24 ETHCINET-C-212-50 (NO) 193.212.51/24 ETHCINET-C-212-51 (NO) 193.212.52/24 ETHCINET-C-212-52 (NO) 193.212.53/24 ETHCINET-C-212-53 (NO) 193.212.54/24 ETHCINET-C-212-54 (NO) 193.212.55/24 ETHCINET-C-212-55 (NO) Sweden ------ Elekta Instrument AB, Skeppargatan 8, S-114 52 Stockholm, SWEDEN 1:1957 ANSCIX-AS -------------- 193.235.128/24 SE-ELEKTA (SE) 194.14.49/24 SE-ELEKTA (SE) Jonkopings socialforvaltning, Sociallakarfunktionen, S-551 89 Jonkoping, SWEDEN 1:1800 ICM-Atlantic 2:1879 EUROPE-RS 3:1133 CERN/DANTE 4:1240 ICM-Pacific ------------ 192.71.94/24 STIGBY-LAN (SE) Swedish Network, ENEA Data Svenska AB, Box 232, S-183 23 Taeby, SWEDEN 1:1957 ANSCIX-AS -------------- 192.121.175/24 SWNETX (SE) Uppsala Universitet, UDAC, Box 174, S-751 04 Uppsala, SWEDEN 1:1957 ANSCIX-AS ------------- 193.44.172/24 UDAC-NETC-2 (SE) Switzerland ----------- Centre informatique de l'Etat de Vaud, Av. Recordon 1, CH-1014 Lausanne, SWITZERLAND 1:1133 CERN/DANTE 2:1674 CERN/DANTE 3:1800 ICM-Atlantic ---------- 145.232/16 ETAT-DE-VAUD (CH) Nexus Telecom AG, Feldbachstrasse, CH-8634 Hombrechtikon, SWITZERLAND 1:701 Alternet 2:1800 ICM-Atlantic ------------- 193.73.218/24 NEXUS-AG (CH) Ukraine ------- Institute for Condensed Matter Physics, 1 Svientsitskii Street, Lviv, 290011, UKRAINE 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific -------------- 193.124.228/24 UARNET-C-124-228 (UA) 193.124.229/24 UARNET-C-124-229 (UA) Institute for Low Temperature Physics and Engineering, pr. Lenina 47, SU-310164 Kharkov, UKRAINE 1:701 Alternet 2:1800 ICM-Atlantic ----------- 194.44.3/24 KCN-DIALUP-NET (UA) United Kingdom -------------- Eastfield Industrial Estate, Glenrothes,, Fife, KY7 4NT, UNITED KINGDOM 1:1957 ANSCIX-AS -------------- 193.112.232/24 CGI-NET (GB) University of Derby, Kedleston Road, Derby, Derbyshire, DE22 1GB, UNITED KINGDOM 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific ------------- 193.60.144/24 DERBY-NET-C-60-144 (GB) 193.60.145/24 DERBY-NET-C-60-145 (GB) 193.60.146/24 DERBY-NET-C-60-146 (GB) 193.60.147/24 DERBY-NET-C-60-147 (GB) 193.60.148/24 DERBY-NET-C-60-148 (GB) 193.60.149/24 DERBY-NET-C-60-149 (GB) 193.60.150/24 DERBY-NET-C-60-150 (GB) 193.60.151/24 DERBY-NET-C-60-151 (GB) 193.62.84/24 DERBY-NETC (GB) 193.62.85/24 DERBY-NETD (GB) 193.62.86/24 DERBY-NETE (GB) 193.62.87/24 DERBY-NETF (GB) 193.63.40/24 DERBY-NET9 (GB) 193.63.41/24 DERBY-NET0 (GB) 193.63.42/24 DERBY-NETA (GB) 193.63.43/24 DERBY-NETB (GB) United States ------------- AEGIS Combat Systems Center, Code 6900, Wallops Island, VA 23337-5000, USA 1:19 Milnet (FIX-East) 2:568 Milnet (FIX-West) ------------- 199.10.233/24 NET-ACSC (US) Adina R&D, Inc., 71 Elton Ave., Watertown, MA 02172, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI -------------- 198.177.146/24 ADINA-NET (US) AkPharma, INC, P.O.Box 111, Pleasantville, NJ 08232, USA 1:1957 ANSCIX-AS ------------ 198.6.220/24 AKPHARMA (US) Aries Systems Corporation, 200 Sutton Street, North Andover, MA 01845, USA 1:560 NEARnet Regional Network 2:701 Alternet ------------- 198.115.92/24 ARIESSYS (US) Buffalo General Hospital, 100 High St, Buffalo, NY 14125, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ------------- 199.33.168/24 BGH-C-33-168 (US) 199.33.169/24 BGH-C-33-169 (US) 199.33.170/24 BGH-C-33-170 (US) 199.33.171/24 BGH-C-33-171 (US) 199.33.172/24 BGH-C-33-172 (US) 199.33.173/24 BGH-C-33-173 (US) CICNet, Inc., 2901 Hubbard Ave, Ann Arbor, MI 48105, USA 1:1225 CICNET at Argonne Labs 2:266 CICNET at MERIT 3:267 CICNET at UIUC ------------- 192.217.86/24 CICNET-BLOCK (US) CRSS, 1177 West Loop South, Houston, TX 77027, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific -------------- 198.137.176/24 CRSS (US) 198.137.177/24 CRSS (US) 198.137.178/24 CRSS (US) 198.189.92/24 CRSS (US) Colorado Internet Cooperative Association, 1495 Canyon Blvd, Suite 35, Boulder, CO 80302, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ------------- 199.45.140/24 COOP-NET (US) 199.45.141/24 COOP-NET (US) 199.45.142/24 COOP-NET (US) 199.45.143/24 COOP-NET (US) 199.45.144/24 COOP-NET (US) 199.45.145/24 COOP-NET (US) 199.45.146/24 COOP-NET (US) 199.45.147/24 COOP-NET (US) 199.45.148/24 COOP-NET (US) 199.45.149/24 COOP-NET (US) Computer Labs, Inc., 1821 Summit Road, Suite 300, Cincinnati, OH 45237, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.149/24 PSINET-C5 (US) Department of Housing and Urban Development, 451 7th Street, SW, McLean, VA 22102, USA 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) -------------- 198.200.153/24 HUD-C (US) Digital Express Group Inc., 6006 Greenbelt Rd, Greenbelt, MD 20770, USA 1:2548 DIGEX-AS -------------- 199.125.128/17 DIGEX-BLK6 (US) ERI Computers, 5339 Far Hills Avenue, Dayton, OH 45429, USA 1:701 Alternet 2:702 Alternet ------------ 198.6.245/24 ERINET (US) Erie County Medical Center, Dept. of Hospital Information Systems, 462 Grider St., Buffalo, NY 14215, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ---------- 161.136/16 ECMC (US) GTE Spacenet Corp., 1700 Old Meadow Road, McLean, VA 22102, USA 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) ------------- 198.102.26/24 GTE-SPACENET21 (US) Gartner Group, 56 Top Gallant Road, Stamford, CT 06904, USA 1:1324 ANS New York City - DNSS 35 ------------- 198.81.204/24 GARTNER-DMZ (US) Global Enterprise Services INC. (JVNCnet), B6 Von Neuman Hall, Princeton, NJ 08514, USA 1:1957 ANSCIX-AS -------------- 198.138.212/24 JVNC-C1-NET213 (US) Hewlett-Packard Company, Information Networks Group, 19420 Homestead Road - MS/43UC, Cupertino, CA 95014, USA 1:1957 ANSCIX-AS ------------- 192.56.191/24 HP11 (US) Imatek, 1119 Timberpine Court, Sunnyvale, CA 94086, USA 1:701 Alternet 2:702 Alternet ------------ 198.6.200/24 IMATEK (US) Infonet, 2100 E. Grand Avenue, El Segundo, CA 90245, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI -------------- 192.157.169/24 INFOLAN47 (US) Internet On-Ramp (IOR-DOM), E. 4111 43'rd, Spokane, WA 99223, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ------------- 199.79.239/24 INETONRAMP (US) Internetworks, Inc., PO BOX 5127, Aloha, OR 97006, USA 1:1957 ANSCIX-AS ------------- 198.145.64/24 WDN-198 (US) John Jay College of Criminal Justice, CUNY, 445 West 59th Street, New York, NY 10019, USA 1:1662 CUNY, New York, New York ------------ 198.83.29/24 ANS-C-BLOCK (US) 198.83.30/24 ANS-C-BLOCK (US) 198.83.31/24 ANS-C-BLOCK (US) 198.83.32/24 ANS-C-BLOCK (US) Lotus Development Corporation, 55 Cambridge Parkway, Cambridge, MA 02142, USA 1:560 NEARnet Regional Network 2:701 Alternet ------------- 198.114.33/24 LOTUS-33 (US) Marathon Exploration, 5555 San Felipe, Houston, TX 77057, USA 1:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 2:210 Westnet Regional Network (Utah Attachment) - ENSS 142 ------------- 192.70.218/24 MARATHON (US) Missouri Research and Education Network (MOREnet), University of Missouri-Columbia, Campus Computing, 200 Heinkel Bldg, Columbia, MO 65211, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ---------- 198.209/16 MORENET-C (US) Mohave Community College, 1971 Jagerson Ave., Kingman, AZ 86401, USA 1:210 Westnet Regional Network (Utah Attachment) - ENSS 142 2:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 ------------- 198.60.186/24 MOHAVE-CC (US) Must Software International, 101 Merrit 7, 4th Floor, Norwalk, CT 06856, USA 1:1957 ANSCIX-AS ------------- 198.99.131/24 MUSTNET2 (US) 198.99.132/24 MUSTNET3 (US) 198.99.133/24 MUSTNET4 (US) NC State Telecommunications Services, 3700 Wake Forest Rd., Raleigh, NC 27609, USA 1:1329 ANS Greensboro - DNSS 75 ------------- 199.90.225/24 STATE-NC-US (US) National Public Radio, 635 Massachusetts Avenue, NW, Washington, DC 20001, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ------------ 199.0.208/24 NPR (US) 199.0.209/24 NPR (US) 199.0.210/24 NPR (US) 199.0.211/24 NPR (US) 199.0.212/24 NPR (US) 199.0.213/24 NPR (US) 199.0.214/24 NPR (US) 199.0.215/24 NPR (US) North Bay Network, Inc., 20 Minor Ct., San Rafael, CA 94903, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ----------- 199.4.64/18 NBN-NET-C-AGGR (US) Northwest Tri-County Intermediate Unit, 252 Waterford Street, Edinboro, PA 16412, USA 1:204 PSCNET Regional Network 2:1206 PSCNET Regional Network -------------- 192.204.188/24 TRINET (US) 192.204.189/24 TRINET-2 (US) PECO Energy Company, 2301 Market Street, Philadelphia, PA 19101, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ---------- 159.214/16 PECONET (US) Pantano Genesis, 2434 E. 3rd St., Tucson, AZ 85719, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic -------------- 199.181.150/24 PANGEN (US) Pixel Dust, Inc., 700 W. Prince Rd., Ste #170, Tucson, AZ 85705, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic -------------- 199.165.135/24 NET-PD-NET (US) Proctor & Gamble Co., 1 Proctor & Gamble Plaza, Cincinnati, OH 45202, USA 1:600 OARNET, Cleveland, OH 2:1800 ICM-Atlantic ---------- 137.179/16 PGXPRESS (US) RCG/Hagler Bailly, 1530 Wilson Blvd.#900, Arlington, VA 22209, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.141/24 PSINET-C5 (US) Salt Lake City Corporation, 72 East 400 South, Suite 400 Salt Lake City, UT 84111, USA 1:210 Westnet Regional Network (Utah Attachment) - ENSS 142 2:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 -------------- 198.176.194/24 SLCCORP2 (US) 198.176.195/24 SLCCORP2 (US) 198.176.196/24 SLCCORP2 (US) 198.176.197/24 SLCCORP2 (US) Sega of America, 275 Shoreline Drive, Redwood City, CA 94065, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ------------ 198.176.8/21 SEGAOA-BLK (US) ShaysNet.Com, 389 Adams Road, Greenfield, MA 01301-1361, USA 1:701 Alternet 2:702 Alternet ------------- 199.170.68/24 SHAYSNET (US) State Center Community College Dist., 1525 E. Weldon Ave., Fresno, CA 93704, USA 1:2150 CSUNET-SW 2:200 BARRNet 3:201 BARRNet ------------- 198.189.22/24 CSUNET-NORTH (US) State of Ohio, Department of Administrative Services, State of Ohio Office of Telecommunications, 2151 Carmack Ave., Columbus, OH 43221, USA 1:1957 ANSCIX-AS ------------ 198.234.0/24 NETBLK-OHIO-NET (US) 198.234.2/24 NETBLK-OHIO-NET (US) 198.234.15/24 NETBLK-OHIO-NET (US) Sun America Financial, 11 Executive Park, Atlanta, GA 30329, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic --------- 165.30/16 SUNAMERICA (US) Syntex USA Inc., 3401 Hillview Avenue, Palo Alto, CA 94303, USA 1:1957 ANSCIX-AS ----------- 196.3.32/24 SYNTEX (US) System Software Associates, Inc., 500 W. Madison Ave, Chicago, IL 60661, USA 1:1225 CICNET at Argonne Labs 2:267 CICNET at UIUC 3:266 CICNET at MERIT -------------- 198.202.128/24 SSA-C (US) Systems Consultants International, Inc., 10432 Nolan Avenue, Rockville, MD 20850, USA 1:701 Alternet 2:702 Alternet ------------ 198.6.221/24 SCII-NET (US) Tangram Systems Corporation, 5511 Capital Center Drive, Raleigh, NC 27606, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 198.17.126/24 TSCNET (US) 199.26.183/24 TSCNET-C-26-183 (US) 199.26.184/24 TSCNET-C-26-184 (US) The File Shop, 8160 N.W. Kirkwood, Kansas City, MO 64151, USA 1:1740 CERFnet ------------- 199.79.146/24 FILESHOP-146 (US) The Investment Company Institute, 1600 M St. NW, Suite 600 Washington, DC 20036, USA 1:1957 ANSCIX-AS ------------ 198.6.202/24 ICI-C (US) US Meddac Ft Irwin, Commander US Meddac, HFXK-IMF, Ft Irwin, CA 90310-5065, USA 1:568 Milnet (FIX-West) 2:19 Milnet (FIX-East) ------------- 199.225.12/24 CHCS-FTIRWIN-C-225-12 (US) 199.225.13/24 CHCS-FTIRWIN-C-225-13 (US) UUNET Technologies, Inc., 3110 Fairview Park Drive, Suite 570, Falls Church, VA 22042, USA 1:1957 ANSCIX-AS ------------- 198.6.248/24 UUNETCBLK6 (US) 198.6.249/24 UUNETCBLK6 (US) 199.170.20/24 UUCBLK170-173 (US) 199.170.54/24 UUCBLK170-173 (US) Western New York Health Science Consortium, University at Buffalo School of Medicine and Biomedical Sciences, 145 CFS Addition, 3435 Main St., Buffalo, NY 14214, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ------------- 199.33.167/24 WNYHSC (US) Westnet, 3645 Marine Street, U. of Colorado, Boulder, CO 80309-0455, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 4:210 Westnet Regional Network (Utah Attachment) - ENSS 142 ------------- 198.59.207/24 NETBLK-WESTNET (US) 198.59.208/24 NETBLK-WESTNET (US) ========================================================== 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.t3p Information is also avaiable through the PRDB whois server. Type "whois -h prdb.merit.edu help" for details. -------------------------------------------------------------------------- REPORT CHANGES: (Updated March 24, 1994) Metric:AS(NSS) - Historically, peer networks with multiple connections to AS 690 could only select which of those connections their networks would take by creating "Fake" AS numbers, and using those in the PRDB Metric:AS announcement lists. Some time in the next few weeks we will begin supporting an expanded syntax, where the AS may be followed by an optional NSS peer number in parentheses. Eventually, this syntax will be used to replace most or all of the current Fake ASs. This change will affect *all* places that the announcement lists are reported: all whois queries, all network reports, this "NWG" report, and the Auto-NACR. If you have code which parses these announcement lists, please be aware that that code may need modifications soon. CIDR Reports: There is a new "whois" option to list aggregates in the PRDB: whois -h prdb.merit.edu listaggs will produce a listing of the currently registered aggregates. There is also a new report on "nestings" of PRDB-registered aggregates with their more specific routes: nets.non-classful. Anyone considering configuring an aggregate into the PRDB (and you all should be!) is encouraged to pre-check that aggregate by typing the command: whois -h prdb.merit.edu 'aggchk ' (where "" is the aggregate description). This command will list all of the other entries in the PRDB that are more specific routes of , as well as any aggregates all ready configured that contain . The output includes the AUP and announcement lists of each of the nets printed, with discrepancies flagged. This is the same program that we use for sanity-checking the NACRs that you submit. The archived discussion list "db-disc@merit.edu" exists for discussion of PRDB issues. Send a message to "db-disc-request@merit.edu" to subscribe. --Dale Johnson (dsj@merit.edu) -------------------------------------------------------------------------- Please send all requests for configuration changes to nsfnet-admin@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. ******************************* --Steve Widmayer Merit/NSFNET skw@merit.edu --Enke Chen Merit/NSFNET enke@merit.edu --Steven J. Richardson Merit/NSFNET sjr@merit.edu - - - - - - - - - - - - - - - - - From list-admin Tue Apr 12 11:10:11 1994 Received: from interlock.ans.net (interlock.ans.net [147.225.1.3]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id LAA03202; Tue, 12 Apr 1994 11:10:09 -0400 Received: by interlock.ans.net id (InterLock SMTP Gateway 1.1); Tue, 12 Apr 1994 11:10:08 -0400 Received: by interlock.ans.net (Internal Mail Agent-2); Tue, 12 Apr 1994 11:10:08 -0400 Received: by interlock.ans.net (Internal Mail Agent-1); Tue, 12 Apr 1994 11:10:08 -0400 Received: by interlock.ans.net (Internal Mail Agent-0); Tue, 12 Apr 1994 11:10:08 -0400 Date: Tue, 12 Apr 94 10:35:11 EDT From: "John J. Hedderman (ANS Install Eng)" To: bgpd@merit.edu Cc: regional-techs@merit.edu Message-Id: FYI. This is a large step in getting ASes 1321-1333 fully CIDR-compliant. ANS will now be working on the aggregations themselves. - John --------------- Received: from interlock.ans.net by home.ans.net with SMTP id AA13587 (5.65c/IDA-1.4.4); Tue, 12 Apr 1994 10:06:28 -0400 Received: from knock.aa.ans.net by interlock.ans.net with SMTP id AA30279 (InterLock SMTP Gateway 1.1); Tue, 12 Apr 1994 10:10:55 -0400 Received: by knock.aa.ans.net id AA45218 (5.65c/IDA-1.4.4); Tue, 12 Apr 1994 14:11:10 GMT Date: Tue, 12 Apr 1994 14:11:10 GMT From: Serpil Bayraktar Message-Id: <199404121411.AA45218@knock.aa.ans.net> To: ans-neteng@ans.net, install-eng@ans.net, nnaf@ans.net All the core CISCOs have been upgraded to 9.21+bgp4.2.2 and they are running BGP4 with AS 690. Serpil - - - - - - - - - - - - - - - - - From list-admin Tue Apr 12 11:05:59 1994 Received: from ncc.ripe.net (ncc.ripe.net [192.87.45.2]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id LAA02838; Tue, 12 Apr 1994 11:05:58 -0400 Received: from mature.ripe.net by ncc.ripe.net with SMTP id AA08179 (5.65a/NCC-2.2); Tue, 12 Apr 1994 17:05:52 +0200 Received: from localhost.ripe.net by fs1.ripe.net with SMTP id AA27439 (5.65a/NCC-2.1); Tue, 12 Apr 1994 17:05:51 +0200 Message-Id: <9404121505.AA27439@fs1.ripe.net> To: yakov@watson.ibm.com Cc: roll@stupi.se, dsj@merit.edu, bgpd@merit.edu, regional-techs@merit.edu, ipv4-ale@ftp.com Subject: Re: 493 Nets in 93 Aggregates In-Reply-To: Your message of Mon, 11 Apr 1994 14:46:19 EDT. <199404111847.OAA06168@merit.edu> From: Tony Bates X-Phone: +31 20 592 5064 Date: Tue, 12 Apr 1994 17:05:50 +0200 Sender: Tony.Bates@ripe.net yakov@watson.ibm.com writes: * Yakov. * P.S. As a matter of fact, I wonder whether we can get a list * of sites that have Class C networks sorted (in descreasing order) * by the number of contiguous Class C networks assigned to a site. Whilst this is not exactly what you are asking as part of the cidr repository on ftp.ripe.net I am now producing the following stats (see below). --Tony. P.S. We can also do something like AS-agg but based on the RIPE database rather than using actual routing information to see where in Europe at least we can get good CIDR aggregation based on an SPs allocation. Here's the current README for ftp.ripe.net:cidr/stats/ Also, check ftp.ripe.net:cidr/data for daily routing dumps if anyone is interested is doing other stats. README for cidr/stats directory ------------------------------- The statistics kept in the CIDR statistics directory are as follows: 1) Table-History This shows the increase (or hopefully a decrease ;-)) of the routing table in the global Internet. It is taken from a router in Amsterdam (Amsterdam-EBS1.Ebone.Net) once a day and shows the actual number of routes and paths seen. 2) AS-agg.* This shows a daily analysis of the networks (classful) routed in the Internet per AS and the amount of networks after aggregation at the AS level. The aggregation assumed is without any holes whatsoever. Of course not every AS can aggregate at the AS level so for some ASes the "NetsCIDR" figure may be difficult to reach. It should also be noted that an AS where figures for NetsNow and NetsCIDR are the same may well mean the AS has already done as much aggregation as is possible (AS224 is a good example of this). These files will be archived from time to time. 3) Specific.* This shows a daily analysis of the current aggregates seen routed in the Internet. It also checks if more specific routes (only more specific classful routes at the moment) are being announced and how may. An explanation of the table is given with each files. These files will be archived from time to time. - - - - - - - - - - - - - - - - - From xladm@xlink.net Tue Apr 12 12:15:03 1994 Received: from relay.xlink.net (xlink5.xlink.net [193.141.40.5]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id JAA24595; Tue, 12 Apr 1994 09:37:40 -0400 From: xladm@xlink.net Received: from xlink1.xlink.net by relay.xlink.net id <13347-0@relay.xlink.net>; Tue, 12 Apr 1994 15:38:07 +0000 Subject: Problems with BARRNET network 131.119.250.119 To: bgpd@merit.edu, regional-techs@merit.edu, as1800@merit.edu Date: Tue, 12 Apr 1994 15:37:22 +0200 (MET DST) Cc: nipper@xlink.net Reply-To: nipper@xlink.net X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1401 Sender: xladm@xlink.net Message-ID: <"relay.xlin.354:12.03.94.13.38.22"@relay.xlink.net> Our mailer tries to deliver mail to 131.119.250.119 (bargate.silvaco.com, SILVACO.BARRNET.NET) and gets host unreachable. Routes for 131.119.0.0 are given as: gw3#sh ip ro 131.119.0.0 Routing entry for 131.119.0.0 (mask 255.255.255.0), 2 known subnets Redistributing via igrp 51771 B 131.119.246.0 [200/100] via 193.23.5.33, 16:10:55 B 131.119.253.0 [200/100] via 193.23.5.33, 16:11:51 gw3#sh ip bgp 131.119.246.0 BGP routing table entry for 131.119.246.0/255.255.255.0, version 2409868 Paths: (1 available, best #1) 1273 1755 1800 1239 1280 200 193.23.5.33 (metric 108166) from 192.54.104.130, localpref 100, weight 210 Origin IGP, valid, internal, best gw3#sh ip bgp 131.119.253.0 BGP routing table entry for 131.119.253.0/255.255.255.0, version 2409849 Paths: (1 available, best #1) 1273 1755 1800 1239 1280 200 193.23.5.33 (metric 108166) from 192.54.104.130, localpref 100, weight 210 Origin IGP, valid, internal, best Is it useful to add Class-B-Subnets to the routing table whilst we are trying to reduce Class-C entries? Regards, Arnold -- XLINK Hostmaster of the day / NTG Netzwerk und Telematic GmbH \/ phone: +49 721 9652 0 Geschaeftsbereich XLINK /\ LINK fax: +49 721 9652 210 Vincenz-Priessnitz-Str. 3 /_______ email: hostmaster@xlink.net D-76131 Karlsruhe, Germany - - - - - - - - - - - - - - - - - From list-admin Tue Apr 12 14:38:58 1994 Received: from Valinor.Stanford.EDU (Valinor.Stanford.EDU [131.119.246.200]) by merit.edu (8.6.8.1/merit-1.0) with ESMTP id OAA22781; Tue, 12 Apr 1994 14:38:56 -0400 Received: (from vaf@localhost) by Valinor.Stanford.EDU (8.6.7/8.6.6) id LAA18625; Tue, 12 Apr 1994 11:40:07 -0700 Sender: Vince Fuller Date: Tue, 12 Apr 94 11:40:07 PDT From: noc@barrnet.net To: nipper@xlink.net Cc: bgpd@merit.edu, regional-techs@merit.edu, as1800@merit.edu, nipper@xlink.net, noc@barrnet.net Office: Spruce Hall F15, (415) 723-6860 USMail: Pine Hall 115, Stanford, CA, 94305-4122 Subject: Re: Problems with BARRNET network 131.119.250.119 In-Reply-To: Your message of Tue, 12 Apr 1994 15:37:22 +0200 (MET DST) Reply-To: noc@barrnet.net Message-ID: Our mailer tries to deliver mail to 131.119.250.119 (bargate.silvaco.com, SILVACO.BARRNET.NET) and gets host unreachable. Routes for 131.119.0.0 are given as: gw3#sh ip ro 131.119.0.0 Routing entry for 131.119.0.0 (mask 255.255.255.0), 2 known subnets Redistributing via igrp 51771 B 131.119.246.0 [200/100] via 193.23.5.33, 16:10:55 B 131.119.253.0 [200/100] via 193.23.5.33, 16:11:51 This is odd. You should have a route to 131.119.0.0/255.255.0.0 which handles all subnets of 131.119. Is it useful to add Class-B-Subnets to the routing table whilst we are trying to reduce Class-C entries? This was an oversight. We are sending the subnet routes to ENSS128 in order to insure correct next-hop resolution across our DMZ network. These subnets should not have been sent to other external peers and no longer will be. Vince Fuller/BARRNet P.S. In the future, you will receive faster response if you send BARRNet problem reports directly to us, either to "noc@BARRNET.NET" or to the MERIT-maintained trouble list "as200-trouble@MERIT.EDU". - - - - - - - - - - - - - - - - - From list-admin Tue Apr 12 13:50:29 1994 Received: from Valinor.Stanford.EDU (Valinor.Stanford.EDU [131.119.246.200]) by merit.edu (8.6.8.1/merit-1.0) with ESMTP id NAA18040; Tue, 12 Apr 1994 13:50:24 -0400 Received: (from vaf@localhost) by Valinor.Stanford.EDU (8.6.7/8.6.6) id KAA18238; Tue, 12 Apr 1994 10:51:26 -0700 Date: Tue, 12 Apr 94 10:51:24 PDT From: Vince Fuller To: "Robert G. Moskowitz" <0003858921@mcimail.com> Cc: ipv4 ale , bgpd@merit.edu, regional-techs@merit.edu Office: Spruce Hall F15, (415) 723-6860 USMail: Pine Hall 115, Stanford, CA, 94305-4122 Subject: Re: Draft minutes ALE WG In-Reply-To: Your message of Tue, 12 Apr 94 06:42 EST Message-ID: BTW there will be a BOF at INTEROP Thursday night on RFC 1597. Out of curiosity, are there going to be other BOF or IETF-related meetings at Interop with technical substance sufficient to motivate one to go? The last couple of years have seen Interop become more and more of a marketing and sales (aka dog and pony) show and less of a technical conference. This year, since it isn't just up the road from here, some of us have much less incentive to go than in previous years. Opinions explicitly solicited - I will summarize if anyone cares. --Vince - - - - - - - - - - - - - - - - - From list-admin Tue Apr 12 15:08:03 1994 Received: from cider.cisco.com (cider.cisco.com [131.108.13.133]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id PAA25326; Tue, 12 Apr 1994 15:08:02 -0400 Received: from localhost.cisco.com by cider.cisco.com with SMTP id AA22631 (5.67a/IDA-1.5); Tue, 12 Apr 1994 12:06:57 -0700 Message-Id: <199404121906.AA22631@cider.cisco.com> To: noc@barrnet.net Cc: bgpd@merit.edu, regional-techs@merit.edu, rchandra@cisco.com Subject: Re: Problems with BARRNET network 131.119.250.119 In-Reply-To: Your message of "Tue, 12 Apr 1994 11:40:07 PDT." Date: Tue, 12 Apr 1994 12:06:57 -0700 From: Paul Traina From: noc@barrnet.net Subject: Re: Problems with BARRNET network 131.119.250.119 Our mailer tries to deliver mail to 131.119.250.119 (bargate.silvaco.com, SILVACO.BARRNET.NET) and gets host unreachable. Routes for 131.119.0.0 ar >>e given as: gw3#sh ip ro 131.119.0.0 Routing entry for 131.119.0.0 (mask 255.255.255.0), 2 known subnets Redistributing via igrp 51771 B 131.119.246.0 [200/100] via 193.23.5.33, 16:10:55 B 131.119.253.0 [200/100] via 193.23.5.33, 16:11:51 This is odd. You should have a route to 131.119.0.0/255.255.0.0 which handles all subnets of 131.119. Did you turn off auto-summary, or did you add explicit network commands? If you turned off auto-summary, you'll no longer generate a 131.119/16 route? FYI, this is just a general warning to everyone... no auto-summary does what you tell it to do. :-) (Vince, let's take this private and we can work out what went wrong...just in case.) Is it useful to add Class-B-Subnets to the routing table whilst we are trying to reduce Class-C entries? This was an oversight. We are sending the subnet routes to ENSS128 in order to insure correct next-hop resolution across our DMZ network. These subnets should not have been sent to other external peers and no longer will be. Vince Fuller/BARRNet P.S. In the future, you will receive faster response if you send BARRNet problem reports directly to us, either to "noc@BARRNET.NET" or to the MERIT-maintained trouble list "as200-trouble@MERIT.EDU". - - - - - - - - - - - - - - - - - From list-admin Tue Apr 12 18:02:25 1994 Received: from interlock.ans.net (interlock.ans.net [147.225.1.3]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id SAA09011; Tue, 12 Apr 1994 18:02:24 -0400 Received: by interlock.ans.net id AA27159 (InterLock SMTP Gateway 1.1); Tue, 12 Apr 1994 18:02:18 -0400 Received: by interlock.ans.net (Internal Mail Agent-2); Tue, 12 Apr 1994 18:02:18 -0400 Received: by interlock.ans.net (Internal Mail Agent-1); Tue, 12 Apr 1994 18:02:18 -0400 From: Curtis Villamizar Message-Id: <199404122159.AA27761@foo.ans.net> To: noc@barrnet.net Cc: nipper@xlink.net, bgpd@merit.edu, regional-techs@merit.edu, as1800@merit.edu, curtis@ans.net Subject: Re: Problems with BARRNET network 131.119.250.119 In-Reply-To: (Your message of Tue, 12 Apr 94 11:40:07 PDT.) Date: Tue, 12 Apr 94 17:59:19 -0500 > Is it useful to add Class-B-Subnets to the routing table whilst we are > trying to reduce Class-C entries? > > This was an oversight. We are sending the subnet routes to ENSS128 in order > to insure correct next-hop resolution across our DMZ network. These subnets > should not have been sent to other external peers and no longer will be. > > Vince Fuller/BARRNet These must be going through another AS path. AS 690 blocks further redistribution of your more specific routes. Does anyone have an AS path for these routes? Curtis - - - - - - - - - - - - - - - - - From list-admin Tue Apr 12 18:11:51 1994 Received: from Valinor.Stanford.EDU (Valinor.Stanford.EDU [131.119.246.200]) by merit.edu (8.6.8.1/merit-1.0) with ESMTP id SAA09828; Tue, 12 Apr 1994 18:11:50 -0400 Received: (from vaf@localhost) by Valinor.Stanford.EDU (8.6.7/8.6.6) id PAA19934; Tue, 12 Apr 1994 15:13:02 -0700 Sender: Vince Fuller Date: Tue, 12 Apr 94 15:13:02 PDT From: noc@barrnet.net To: Curtis Villamizar Cc: nipper@xlink.net, bgpd@merit.edu, regional-techs@merit.edu, as1800@merit.edu, curtis@ans.net, noc@barrnet.net Office: Spruce Hall F15, (415) 723-6860 USMail: Pine Hall 115, Stanford, CA, 94305-4122 Subject: Re: Problems with BARRNET network 131.119.250.119 In-Reply-To: Your message of Tue, 12 Apr 94 17:59:19 -0500 Reply-To: noc@barrnet.net Message-ID: These must be going through another AS path. AS 690 blocks further redistribution of your more specific routes. Does anyone have an AS path for these routes? Curtis- I believe the problem was at the CIX - we were not filtering-out the 131.119 subnets in our BGP advertisements to them. This has been fixed. --Vince - - - - - - - - - - - - - - - - - From list-admin Thu Apr 14 10:30:57 1994 Received: (dsj@localhost) by merit.edu (8.6.8.1/merit-1.0) id KAA18749 for regional-techs; Thu, 14 Apr 1994 10:30:57 -0400 Date: Thu, 14 Apr 1994 10:30:57 -0400 From: "Dale S. Johnson" Message-Id: <199404141430.KAA18749@merit.edu> To: regional-techs Subject: 722 Nets, 23 ASs, 98 Aggregates Good News from the CIDR Press!! AS690 CIDR Squeezings Report: 722 Nets, 23 ASs, 98 Aggregates -------------------------------------------------------------- 722 (35%) of the ever-announced more-specific routes within aggregates have been withdrawn. 442 of those were withdrawn within the last week. 155 the week before that. 122 the week before that. 23 ASs have registered aggregates in the PRDB. 20 of those are announcing aggregates. 11 have withdrawn at least one more specific route. 98 Aggregates are configured. 88 of these were Top-Level Aggregates (not nested in another aggregate). 69 of these were announced to AS690 as of yesterday. 58 of those have at least one subnet configured (the other 11 may be saving. the Internet future subnet announcements). 29 have stopped announcing at least one configured more specific route. 19 have stopped announcing half of their configured more specific routes. 16 have stopped announcing most (80%) of their more specific routes. See merit.edu:pub/nsfnet/cidr/cidr_savings for more detail. ----------------------------------------------------------- - - - - - - - - - - - - - - - - - From list-admin Thu Apr 14 10:49:27 1994 Received: from ncc.ripe.net (ncc.ripe.net [192.87.45.2]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id KAA20107; Thu, 14 Apr 1994 10:49:26 -0400 Received: from mature.ripe.net by ncc.ripe.net with SMTP id AA17614 (5.65a/NCC-2.2); Thu, 14 Apr 1994 16:49:24 +0200 Received: from localhost.ripe.net by fs1.ripe.net with SMTP id AA05119 (5.65a/NCC-2.1); Thu, 14 Apr 1994 16:49:23 +0200 Message-Id: <9404141449.AA05119@fs1.ripe.net> To: "Dale S. Johnson" Cc: regional-techs@merit.edu Subject: Re: 722 Nets, 23 ASs, 98 Aggregates In-Reply-To: Your message of Thu, 14 Apr 1994 10:30:57 EDT. <199404141430.KAA18749@merit.edu> From: Tony Bates X-Phone: +31 20 592 5064 Date: Thu, 14 Apr 1994 16:49:22 +0200 Sender: Tony.Bates@ripe.net Whilst this is good news - More routes move into the Internet every day. Here's just one weeks worth as seen in Europe from a full routing table. Date Routes Paths 080494 20136 53243 090494 20139 53225 100494 20044 53333 110494 20036 53183 120494 20294 53642 130494 20326 53849 140494 20374 53822 So whilst its good news from the CIDR press there's a definate dampening from the "Table Space" press. --Tony. "Dale S. Johnson" writes: * Good News from the CIDR Press!! * * AS690 CIDR Squeezings Report: 722 Nets, 23 ASs, 98 Aggregates * -------------------------------------------------------------- * * 722 (35%) of the ever-announced more-specific routes within aggregates hav * e * been withdrawn. 442 of those were withdrawn within the last week. * 155 the week before that. * 122 the week before that. * * 23 ASs have registered aggregates in the PRDB. * 20 of those are announcing aggregates. * 11 have withdrawn at least one more specific route. * * 98 Aggregates are configured. * 88 of these were Top-Level Aggregates (not nested in another aggregate). * 69 of these were announced to AS690 as of yesterday. * 58 of those have at least one subnet configured (the other 11 may be savi * ng. * the Internet future subnet announcements). * 29 have stopped announcing at least one configured more specific route. * 19 have stopped announcing half of their configured more specific routes. * 16 have stopped announcing most (80%) of their more specific routes. * * See merit.edu:pub/nsfnet/cidr/cidr_savings for more detail. * ----------------------------------------------------------- - - - - - - - - - - - - - - - - - From list-admin Thu Apr 14 11:17:03 1994 Received: from watson.ibm.com (watson.ibm.com [129.34.139.4]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id LAA23136; Thu, 14 Apr 1994 11:17:02 -0400 From: yakov@watson.ibm.com Message-Id: <199404141517.LAA23136@merit.edu> Received: from YKTVMV by watson.ibm.com (IBM VM SMTP V2R3) with BSMTP id 4025; Thu, 14 Apr 94 11:17:02 EDT Date: Thu, 14 Apr 94 11:14:18 EDT To: Tony.Bates@ripe.net, dsj@merit.edu cc: regional-techs@merit.edu Subject: 722 Nets, 23 ASs, 98 Aggregates Ref: Your note of Thu, 14 Apr 1994 16:49:22 +0200 It would be really nice if all the new destinations that can be CIDRized be announced ONLY via CIDR blocks without individual components. Is that the current practice ? And if not, then what can be done to put this in place ? Yakov. - - - - - - - - - - - - - - - - - From list-admin Thu Apr 14 11:50:57 1994 Received: from psi.com (psi.com [192.67.6.2]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id LAA25957; Thu, 14 Apr 1994 11:50:53 -0400 Received: from us.psi.com by psi.com (4.1/2.1-PSI/PSINet) id AA18853; Thu, 14 Apr 94 11:50:16 EDT Received: by us.psi.com (4.1/SMI-4.1.3-PSI-pop) id AA24521; Thu, 14 Apr 94 11:50:25 EDT Message-Id: <9404141550.AA24521@us.psi.com> To: yakov@watson.ibm.com Cc: Tony.Bates@ripe.net, dsj@merit.edu, regional-techs@merit.edu Subject: Re: 722 Nets, 23 ASs, 98 Aggregates In-Reply-To: Your message of "Thu, 14 Apr 1994 11:14:18 EDT." <199404141517.LAA23136@merit.edu> Date: Thu, 14 Apr 1994 11:50:18 -0400 From: "Martin Lee Schoffstall" Yakov, The way I read your message is that all new network numbers should be CIDRized and fundamentally not be portable between service providers. This is a bit rigid. Shouldn't there be another option that allows portability too? Marty > Ref: Your note of Thu, 14 Apr 1994 16:49:22 +0200 > > It would be really nice if all the new destinations that can be CIDRized > be announced ONLY via CIDR blocks without individual > components. Is that the current practice ? And if not, > then what can be done to put this in place ? > Yakov. - - - - - - - - - - - - - - - - - From list-admin Thu Apr 14 12:19:59 1994 Received: from watson.ibm.com (watson.ibm.com [129.34.139.4]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id MAA27985 for ; Thu, 14 Apr 1994 12:19:58 -0400 From: yakov@watson.ibm.com Message-Id: <199404141619.MAA27985@merit.edu> Received: from YKTVMV by watson.ibm.com (IBM VM SMTP V2R3) with BSMTP id 5331; Thu, 14 Apr 94 12:19:59 EDT Date: Thu, 14 Apr 94 12:19:15 EDT To: schoff@us.psi.com cc: regional-techs@merit.edu Subject: 722 Nets, 23 ASs, 98 Aggregates Ref: Your note of Thu, 14 Apr 1994 11:50:18 -0400 Marty, >The way I read your message is that all new network numbers should >be CIDRized You misread my message (but this is probably my fault as well, since I wasn't clear enough). So, let me try again. What I suggested is that if a site has a contiguous block of network numbers (such that this block could be reduced to a small number of IP address prefixes), then this site should be announced to the Internet as just the prefixes, rather than a set of individual network numbers. Yakov. - - - - - - - - - - - - - - - - - From list-admin Thu Apr 14 14:59:50 1994 Received: from interlock.ans.net (interlock.ans.net [147.225.1.3]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id OAA11147; Thu, 14 Apr 1994 14:59:48 -0400 Received: by interlock.ans.net id AA29118 (InterLock SMTP Gateway 1.1); Thu, 14 Apr 1994 14:59:12 -0400 Received: by interlock.ans.net (Internal Mail Agent-2); Thu, 14 Apr 1994 14:59:12 -0400 Received: by interlock.ans.net (Internal Mail Agent-1); Thu, 14 Apr 1994 14:59:12 -0400 From: Curtis Villamizar Message-Id: <199404141856.AA72963@foo.ans.net> To: "Martin Lee Schoffstall" Cc: yakov@watson.ibm.com, Tony.Bates@ripe.net, dsj@merit.edu, regional-techs@merit.edu, curtis@ans.net Subject: Re: 722 Nets, 23 ASs, 98 Aggregates In-Reply-To: (Your message of Thu, 14 Apr 94 11:50:18 D.) <9404141550.AA24521@us.psi.com> Date: Thu, 14 Apr 94 14:56:11 -0500 > Yakov, > > The way I read your message is that all new network numbers should > be CIDRized and fundamentally not be portable between service providers. > > This is a bit rigid. Shouldn't there be another option that allows > portability too? > > Marty If a component moves, and does not want to renumber, the old provider should announce an unreachable for the component (that is obviously more specific than the aggregate) and the new provider should announce the component that moved. You should ask the customer to renumber and explain why and strongly urge then to do so. I don't think anyone is advocating forced renumbering (are they)? Curtis - - - - - - - - - - - - - - - - - From list-admin Thu Apr 14 14:52:50 1994 Received: from cert.org (cert.org [192.88.209.5]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id OAA10735 for ; Thu, 14 Apr 1994 14:52:50 -0400 Received: from delphi.cert.org by cert.org (4.1/cert-5.2) id AA15965; Thu, 14 Apr 94 14:48:49 EDT Received: by delphi.cert.org (4.1/cert-5.3) id AA10634; Thu, 14 Apr 94 14:48:27 EDT Date: Thu, 14 Apr 94 14:48:27 EDT Message-Id: <9404141848.AA10634@delphi.cert.org> Subject: CERT Advisory /tmp/cert.org.ftp.files/CA-94:08.ftpd.vulnerabilities To: cert-advisory-request@cert.org From: cert-advisory@cert.org (CERT Advisory) Reply-To: cert-advisory@cert.org Organization: CERT Coordination Center Address: Software Engineering Institute Carnegie Mellon University Pittsburgh, Pennsylvania 15213-3890 Phone: +1 412 268-7090 Fax: +1 412 268-6989 ============================================================================= CA-94:08 CERT Advisory April 14, 1994 ftpd Vulnerabilities ----------------------------------------------------------------------------- The CERT Coordination Center has received information concerning two vulnerabilities in some ftpd implementations. The first is a vulnerability with the SITE EXEC command feature of the FTP daemon (ftpd) found in versions of ftpd that support the SITE EXEC feature. This vulnerability allows local or remote users to gain root access. The second vulnerability involves a race condition found in the ftpd implementations listed in Section I. below. This vulnerability allows local users to gain root access. Sites using these implementations are vulnerable even if they do not support anonymous FTP. As these vulnerabilities are widely known, we strongly recommend that any site running a version of ftpd listed below take steps to immediately upgrade or disable their FTP daemon. Also potentially at risk are sites whose ftpd is derived from the DECWRL or wuarchive ftpd code containing the SITE EXEC feature. For additional information or assistance, contact the developer or vendor of your ftpd implementation. If we receive additional information relating to this advisory, we will place it, along with any clarifications, in a README file available by anonymous FTP from info.cert.org (e.g., /pub/cert_advisories/CA-94:xx.README). We encourage you to check our README files regularly for updates on advisories that relate to your site. ----------------------------------------------------------------------------- I. Description There is a vulnerability in the SITE EXEC command feature of ftpd that allows any remote or local user to obtain root access. There is also a vulnerability due to a race condition in these implementations. Versions known to be vulnerable to these problems are: wuarchive ftpd versions 2.0-2.3 (version 2.2 patched the SITE EXEC problem, but not the race condition) DECWRL ftpd versions prior 5.93 BSDI ftpd version 1.1 prior to patch 5 The SITE EXEC vulnerability affects your ftpd only if the SITE EXEC command feature has been explicitly activated at your site. This functionality is not activated by default. Sites that have not enabled the SITE EXEC feature are not at risk from this vulnerability. However, since the race condition does not have an easily applied workaround, CERT recommends that you upgrade to one of the versions listed below. II. Impact Anyone (remote or local) can gain root access on a host running a vulnerable FTP daemon. Support for anonymous FTP is not required to exploit this vulnerability. III. Solution Affected sites can solve both of these problems by upgrading to the latest version of ftpd. These versions are listed below. Be certain to verify the checksum information to confirm that you have retrieved a valid copy. If you cannot install the new version in a timely manner, you should disable FTP service until you have corrected this problem. It is not sufficient to disable anonymous FTP. You must disable the FTP daemon. For wuarchive ftpd, you can obtain version 2.4 via anonymous FTP from wuarchive.wustl.edu, in the "/packages/wuarchive-ftpd" directory. If you are currently running version 2.3, a patch file is available. BSD SVR4 File Checksum Checksum MD5 Digital Signature ----------------- -------- --------- -------------------------------- wu-ftpd-2.4.tar.Z 38213 181 20337 362 cdcb237b71082fa23706429134d8c32e patch_2.3-2.4.Z 09291 8 51092 16 5558a04d9da7cdb1113b158aff89be8f For DECWRL ftpd, sites can obtain version 5.93 via anonymous FTP from gatekeeper.dec.com in the "/pub/misc/vixie" directory. BSD SVR4 File Checksum Checksum MD5 Digital Signature ----------------- -------- --------- -------------------------------- ftpd.tar.gz 38443 60 1710 119 ae624eb607b4ee90e318b857e6573500 For BSDI systems, patch 005 should be applied to version 1.1 of the BSD/386 software. You can obtain the patch file via anonymous FTP from ftp.bsdi.com in the "/bsdi/patches-1.1" directory. BSD SVR4 File Checksum Checksum MD5 Digital Signature ----------------- -------- --------- -------------------------------- BU110-005 35337 272 54935 543 1f454d4d9d3e1397d1eff0432bd383cf --------------------------------------------------------------------------- The CERT Coordination Center wishes to thank Neil Woods and Karl Strickland for finding and reporting the wustl FTP daemon bug. We also wish to thank Bryan O'Connor and Chris Myers of Washington University in St. Louis, Paul Vixie of Vixie Enterprises, and Tony Sanders of BSDI for their invaluable assistance in resolving this problem. --------------------------------------------------------------------------- If you believe that your system has been compromised, contact the CERT Coordination Center or your representative in the Forum of Incident Response and Security Teams (FIRST). If you wish to send sensitive incident or vulnerability information to CERT via electronic mail, CERT strongly advises that the e-mail be encrypted. CERT can support a shared DES key, PGP (public key available via anonymous FTP on info.cert.org), or PEM (contact CERT for details). Internet E-mail: cert@cert.org Telephone: 412-268-7090 (24-hour hotline) CERT personnel answer 8:30 a.m.-5:00 p.m. EST(GMT-5)/EDT(GMT-4), and are on call for emergencies during other hours. CERT Coordination Center Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213-3890 Past advisories, information about FIRST representatives, and other information related to computer security are available via anonymous FTP from info.cert.org. - - - - - - - - - - - - - - - - - From list-admin Thu Apr 14 15:54:49 1994 Received: from psi.com (psi.com [192.67.6.2]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id PAA16185; Thu, 14 Apr 1994 15:54:46 -0400 Received: from us.psi.com by psi.com (4.1/2.1-PSI/PSINet) id AA25933; Thu, 14 Apr 94 15:54:05 EDT Received: by us.psi.com (4.1/SMI-4.1.3-PSI-pop) id AA04612; Thu, 14 Apr 94 15:54:13 EDT Message-Id: <9404141954.AA04612@us.psi.com> To: Curtis Villamizar Cc: yakov@watson.ibm.com, Tony.Bates@ripe.net, dsj@merit.edu, regional-techs@merit.edu Subject: Re: 722 Nets, 23 ASs, 98 Aggregates In-Reply-To: Your message of "Thu, 14 Apr 1994 14:56:11 CDT." <199404141856.AA72963@foo.ans.net> Date: Thu, 14 Apr 1994 15:54:05 -0400 From: "Martin Lee Schoffstall" We've seen forced renumbering already being done. I'll defer my remarks on whether this is good or bad. Thinking of scaling in the future why does the old ISP want the administrative burden of configuring "unreachable" and then offer the computational burden to the entire Internet of a "unclean" CIDR block. And the new ISP putting a standalone network number which needs to be computed upon. CIDR seems like a future lose-lose situation unless the blocks are clean. And the larger the blocks the bigger win. These should be the goals for the future. "Strongly urge" seems like the cows are out of the barn already for us old dirt farmers. Marty > > If a component moves, and does not want to renumber, the old provider > should announce an unreachable for the component (that is obviously > more specific than the aggregate) and the new provider should announce > the component that moved. > > You should ask the customer to renumber and explain why and strongly > urge then to do so. I don't think anyone is advocating forced > renumbering (are they)? > > Curtis - - - - - - - - - - - - - - - - - From list-admin Thu Apr 14 18:10:36 1994 Received: from nic.near.net (nic.near.net [192.52.71.4]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id SAA28349; Thu, 14 Apr 1994 18:10:35 -0400 Received: from nic.near.net by nic.near.net id aa10057; 14 Apr 94 18:10 EDT To: Martin Lee Schoffstall cc: Curtis Villamizar , yakov@watson.ibm.com, Tony.Bates@ripe.net, dsj@merit.edu, regional-techs@merit.edu Subject: Re: 722 Nets, 23 ASs, 98 Aggregates In-reply-to: Your message of Thu, 14 Apr 1994 15:54:05 -0400. <9404141954.AA04612@us.psi.com> Date: Thu, 14 Apr 1994 18:10:32 -0400 From: John Curran Message-ID: <9404141810.aa10057@nic.near.net> -------- ] From: Martin Lee Schoffstall ] Subject: Re: 722 Nets, 23 ASs, 98 Aggregates ] Date: Thu, 14 Apr 1994 15:54:05 -0400 ] ] We've seen forced renumbering already being done. I'll defer my remarks ] on whether this is good or bad. ] ] Thinking of scaling in the future why does the old ISP want the administrative ] burden of configuring "unreachable" and then offer the computational ] burden to the entire Internet of a "unclean" CIDR block. And the new ] ISP putting a standalone network number which needs to be computed upon. ] ] CIDR seems like a future lose-lose situation unless the blocks are clean. ] And the larger the blocks the bigger win. A site which doesn't renumber will need to have his more specific route propogated to the far corners of the Internet. 1) Anyone care to estimate how much this route costs to the combined set of multiply-connected providers and sites? (Need to include router memory, forced introduction of new routers, update bandwidth, etc. for every affected network...) 2) Given the answer to #1, is there some way to recover these costs? /John p.s. (Yes, I can hear the booing and hissing starting already... :-) - - - - - - - - - - - - - - - - - From list-admin Thu Apr 14 19:39:44 1994 Received: from pepper.merit.edu (pepper.merit.edu [35.42.1.50]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id TAA03666; Thu, 14 Apr 1994 19:39:43 -0400 Received: by pepper.merit.edu (4.1/client-0.9) id AA06659; Thu, 14 Apr 94 19:39:42 EDT From: epg@merit.edu Message-Id: <9404142339.AA06659@pepper.merit.edu> Subject: Re: 20402 routing entries To: vaf@Valinor.Stanford.EDU (Vince Fuller) Date: Thu, 14 Apr 94 19:39:42 EDT Cc: bgpd@merit.edu, eowg@fnc.gov, regional-techs@merit.edu, epg@merit.edu (Elise Gerich) In-Reply-To: ; from "Vince Fuller" at Apr 14, 94 4:30 pm X-Mailer: ELM [version 2.3 PL11] Vince asks: > > Question to the MERIT folks: have you had any luck (and have you tried) using > the ASxxx@MERIT.EDU mailing lists to try and get in touch with those non-BGP4 > sites which might not be on the BGPD or Regional Techs mailing list? I'm likely > asking the obvious, but... > > --Vince > Yes, we have again started trying to get folks to move to BGP4 - heck we are still trying to get some folks to move to BGP. The results are slow in coming. --Elise - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 04:00:54 1994 Received: from ncc.ripe.net (ncc.ripe.net [192.87.45.2]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id EAA07033; Fri, 15 Apr 1994 04:00:50 -0400 Received: from reif.ripe.net by ncc.ripe.net with SMTP id AA24758 (5.65a/NCC-2.2); Fri, 15 Apr 1994 10:00:48 +0200 Received: from localhost.ripe.net by reif.ripe.net with SMTP id AA10684 (5.65a/NCC-2.1); Fri, 15 Apr 1994 10:00:47 +0200 Message-Id: <9404150800.AA10684@reif.ripe.net> To: Curtis Villamizar Cc: "Martin Lee Schoffstall" , yakov@watson.ibm.com, Tony.Bates@ripe.net, dsj@merit.edu, regional-techs@merit.edu Subject: Re: 722 Nets, 23 ASs, 98 Aggregates In-Reply-To: Your message of Thu, 14 Apr 1994 14:56:11 CDT. <199404141856.AA72963@foo.ans.net> From: Daniel Karrenberg X-Organization: RIPE Network Coordination Centre X-Phone: +31 20 592 5065 Date: Fri, 15 Apr 1994 10:00:46 +0200 Sender: Daniel.Karrenberg@ripe.net > Curtis Villamizar writes: > > You should ask the customer to renumber and explain why and strongly > urge then to do so. Exactly. > I don't think anyone is advocating forced > renumbering (are they)? There are people who do. I observe that none of them is dealing with customers as an ISP or Internet registry. Challenge? - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 06:48:09 1994 Received: from bsd.stupi.se (Bsd.Stupi.SE [192.108.198.10]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id GAA16743; Fri, 15 Apr 1994 06:48:00 -0400 Received: by bsd.stupi.se (5.67/1.37) id AA05326; Fri, 15 Apr 94 12:47:51 +0200 Date: Fri, 15 Apr 94 12:47:51 MET DST From: Peter Lothberg To: epg@merit.edu Cc: vaf@Valinor.Stanford.EDU (Vince Fuller), bgpd@merit.edu, eowg@fnc.gov, regional-techs@merit.edu, epg@merit.edu (Elise Gerich) Subject: Re: 20402 routing entries In-Reply-To: Your message of Thu, 14 Apr 94 19:39:42 EDT Message-Id: > Yes, we have again started trying to get folks to move to BGP4 - heck we > are still trying to get some folks to move to BGP. The results are slow > in coming. > --Elise I knew this sounds hard, but; Offer those who don't talk BGP4, to be disconnected by 15-MAY or so if they don't change. -peter - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 07:48:16 1994 Received: (skw@localhost) by merit.edu (8.6.8.1/merit-1.0) id HAA20568 for nwg; Fri, 15 Apr 1994 07:48:16 -0400 Date: Fri, 15 Apr 1994 07:48:16 -0400 From: "Steven K. Widmayer" Message-Id: <199404151148.HAA20568@merit.edu> To: nwg Subject: Additions to the NSFNET policy-based routing database ------------------------------------------------------------------------------ CIDR Progress Report: 722 Nets, 23 ASs, 98 Aggregates. Details below. New format for Metric:AS lists coming later in this and all reports. See 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 Configured Networks 29796 = 29 4630 25022 115 Added Networks 332 = 0 21 294 17 Deleted Networks 74 = 0 2 72 0 IP address Net name Country Priority:AS ---------- -------- ------- ----------- 132.172/16 HANDS C:US 1:291 2:293 136.174/16 PINELLAS C:US 1:279 2:86 136.209/16 VICENZA-NET2 C:US 1:19 2:568 149.252/16 DOE-NV3 C:US 1:291 2:293 151.106/16 EMS C:US 1:1225 2:267 3:266 152.229/16 DMC-DE-NET C:US 1:568 2:19 158.27/16 MOBILNET7 C:US 1:114 159.212/16 IHCNET C:US 1:210 2:209 159.226/16 NCFC C:CN 1:1240 2:1800 161.202/16 CSUISSE-USA C:US 1:2149 2:174 162.105/16 PUNET C:CN 1:1240 2:1800 162.113/16 DUKEPOWER2 C:US 1:1329 164.167/16 TIDEMEDNET C:US 1:19 2:568 165.242/16 HUNET C:JP 1:372 2:297 165.248/16 HAWAIIDOE C:US 1:372 2:297 166.31/16 MMC-NET16 C:US 1:1240 2:1800 166.92/16 SCHULLER-NET C:US 1:209 2:210 166.111/16 TUNET C:CN 1:1240 2:1800 166.122/16 HAWAIICC C:US 1:372 2:297 167.131/16 NET-OREDOT C:US 1:1240 2:1800 168.1/16 CSH-B-BLK3 C:US 1:2149 2:174 192.6.67/24 NETBLK-HP208 C:US 1:200 2:201 5:560 192.44.46/24 FNET-FRA-LD C:FR 1:701 2:1800 192.44.47/24 FNET-FRA-LY C:FR 1:701 2:1800 192.50.36/24 WIDE-EXP-NET C:JP 1:372 2:297 192.50.43/24 WIDE-EXP-NET2 C:JP 1:372 2:297 192.50.44/24 WIDE-MOBILE1 C:JP 1:372 2:297 192.50.45/24 WIDE-MOBILE2 C:JP 1:372 2:297 192.50.62/24 WIDE-ISDN C:JP 1:372 2:297 192.83.234/24 MICROTECH C:US 1:1240 2:1800 192.88.50/24 NET-HILLSIDE C:GB 1:701 2:1800 192.100.7/24 SLCCORP-ENG C:US 1:210 2:209 192.100.8/24 SLCCORP-UTIL C:US 1:210 2:209 192.100.150/23 INFOCOMM-NET-150 C:US 1:2551 192.102.197/24 LOCALNET16 C:US 3:210 4:209 192.109.251/24 ECRC-RBS C:DE 1:1800 2:1240 192.122.216/21 EUNET-IE-192.122.216- C:IE 1:701 2:1800 192.122.224/21 EUNET-IE-192.122.224- C:IE 1:701 2:1800 192.131.10/23 HMSI1 C:US 1:2551 192.136.62/24 NET-ORMALL C:US 1:1240 2:1800 192.157.37/24 SPRINTLINK9 C:US 1:1800 2:1240 192.164/16 EUNET-AT-192.164-AGG C:AT 1:701 2:1800 192.198.36/24 UNMC8 C:US 1:93 192.198.44/24 UNMC8 C:US 1:93 192.198.45/24 UNMC8 C:US 1:93 192.198.46/24 UNMC8 C:US 1:93 192.203.1/24 TDSCA-NET C:US 1:2149 2:174 192.204.4/24 NETAXS C:US 1:204 2:1206 192.204.122/24 TEXSCI-3 C:US 1:204 2:1206 192.204.123/24 TEXSCI-4 C:US 1:204 2:1206 192.218.228/24 WIDE-SAT-NET2 C:JP 1:372 2:297 192.225.82/24 GSFC23 C:US 1:297 2:372 192.225.83/24 GSFC24 C:US 1:297 2:372 192.239.247/24 STHRNCOL-NET C:US 1:279 2:86 193.23.5/24 ECRC-EBONE C:DE 1:1800 2:1240 193.48.186/24 FR-LIFL C:FR 1:1800 2:1240 3:1133 4:1674 193.54.39/24 FR-NCY-PN2 C:FR 1:1800 2:1240 3:1133 4:1674 193.54.187/24 FR-GRENET34 C:FR 1:1800 2:1240 3:1133 4:1674 193.54.188/24 FR-GRENET35 C:FR 1:1800 2:1240 3:1133 4:1674 193.54.189/24 FR-GRENET36 C:FR 1:1800 2:1240 3:1133 4:1674 193.55.107/24 FR-CNRS1234 C:FR 1:1800 2:1240 3:1133 4:1674 193.55.238/24 F-NCY-IUTA-G C:FR 1:1800 2:1240 3:1133 4:1674 193.55.239/24 F-NCY-IUTA-R C:FR 1:1800 2:1240 3:1133 4:1674 193.69/16 EUNET-NO-193.69-AGG C:NO 1:701 2:1800 193.71/16 EUNET-NO-193.71-AGG C:NO 1:701 2:1800 193.80/16 EUNET-AT-193.80-AGG C:AT 1:701 2:1800 193.84.188/24 STKNET-C-84-188 C:CZ 1:1800 2:1133 3:1240 193.84.189/24 STKNET-C-84-189 C:CZ 1:1800 2:1133 3:1240 193.87.100/24 CANET C:SK 1:1800 2:1133 3:1240 193.90/16 EUNET-NO-193.90-AGG C:NO 1:701 2:1800 193.97.189/24 HARRASSO-DE1 C:DE 1:701 2:1800 193.120/16 EUNET-IE-193.120-AGG C:IE 1:701 2:1800 193.136.104/24 LNEC-1 C:PT 1:1800 2:1133 3:1240 193.136.105/24 LNEC-2 C:PT 1:1800 2:1133 3:1240 193.136.106/24 LNEC-3 C:PT 1:1800 2:1133 3:1240 193.136.107/24 LNEC-4 C:PT 1:1800 2:1133 3:1240 193.136.108/24 LNEC-5 C:PT 1:1800 2:1133 3:1240 193.136.109/24 LNEC-6 C:PT 1:1800 2:1133 3:1240 193.136.112/24 UNL-FE-1 C:PT 1:1800 2:1133 3:1240 193.172.26/24 EMPB C:AT 1:1800 2:1133 3:1674 4:1240 193.198.42/24 GLOBTOUR-NET C:HR 1:1800 2:1133 3:1240 198.6.228/24 ISOCOR-NET1 C:US 1:701 2:702 198.6.229/24 ISOCOR-NET1 C:US 1:701 2:702 198.6.230/24 ISOCOR-NET1 C:US 1:701 2:702 198.6.231/24 ISOCOR-NET1 C:US 1:701 2:702 198.25.155/24 DLA-C156 C:US 1:19 2:568 198.59.12/23 TIME-WARNER C:US 1:2551 198.78.253/24 STHRNCOL-NET-C-78-253 C:US 1:279 2:86 198.78.254/24 STHRNCOL-NET-C-78-254 C:US 1:279 2:86 198.78.255/24 STHRNCOL-NET-C-78-255 C:US 1:279 2:86 198.79.80/24 NAS-S17 C:US 1:279 2:86 198.79.81/24 NAS-S18 C:US 1:279 2:86 198.79.82/24 NAS-S19 C:US 1:279 2:86 198.79.83/24 NAS-S20 C:US 1:279 2:86 198.81.209/24 LIGHT-DMZ C:US 1:1322 198.83.28/24 ANS-C-BLOCK C:US 1:1662 198.87.242/24 CICNET-2 C:US 1:266 2:1225 3:267 198.99.143/24 SLCCORP2 C:US 1:210 2:209 198.99.144/24 SLCCORP3 C:US 1:210 2:209 198.99.145/24 SLCCORP4 C:US 1:210 2:209 198.108.56/24 CAEN-BB C:US 1:233 2:237 3:266 4:267 5:1225 198.108.58/24 CICNET-HQ2 C:US 1:233 2:237 3:266 4:267 5:1225 198.112.68/24 YANKEE-198 C:US 1:560 2:701 198.133.187/24 MCMC1 C:US 1:1225 2:267 3:266 198.133.188/24 MCMC2 C:US 1:1225 2:267 3:266 198.133.189/24 MCMC3 C:US 1:1225 2:267 3:266 198.151.150/24 TXASHLTH-C3 C:US 1:114 198.176.229/24 NET-MHDDSD C:US 1:1240 2:1800 198.177.16/24 NET-ORECAP1 C:US 1:1240 2:1800 198.177.17/24 NET-ORECAP2 C:US 1:1240 2:1800 198.177.18/24 NET-ORECAP3 C:US 1:1240 2:1800 198.177.19/24 NET-ORECAP4 C:US 1:1240 2:1800 198.177.20/24 NET-ORECAP5 C:US 1:1240 2:1800 198.177.21/24 NET-ORECAP6 C:US 1:1240 2:1800 198.177.22/24 NET-ORECAP7 C:US 1:1240 2:1800 198.177.23/24 NET-ORECAP8 C:US 1:1240 2:1800 198.177.24/24 NET-ORECAP9 C:US 1:1240 2:1800 198.177.25/24 NET-ORECAP10 C:US 1:1240 2:1800 198.177.26/24 NET-ORECAP11 C:US 1:1240 2:1800 198.177.27/24 NET-ORECAP12 C:US 1:1240 2:1800 198.178.225/24 IFCMO C:US 1:1740 198.179.16/21 DIGEX1 C:US 1:2548 198.180.32/19 NETBLK-DIGEX-NET4 C:US 1:2548 198.185.173/24 SLCCORP5 C:US 1:210 2:209 198.185.174/24 SLCCORP5 C:US 1:210 2:209 198.185.175/24 SLCCORP5 C:US 1:210 2:209 198.185.176/24 SLCCORP5 C:US 1:210 2:209 198.185.177/24 SLCCORP5 C:US 1:210 2:209 198.187.32/19 DIGEX-NET5 C:US 1:2548 198.232.137/24 CSH-C-BLK3 C:US 1:2149 2:174 198.232.138/24 CSH-C-BLK3 C:US 1:2149 2:174 198.232.198/24 DCBS-C-232-198 C:US 1:1240 2:1800 198.232.199/24 DCBS-C-232-199 C:US 1:1240 2:1800 198.232.200/24 DCBS-C-232-200 C:US 1:1240 2:1800 198.232.201/24 DCBS-C-232-201 C:US 1:1240 2:1800 198.232.202/24 DCBS-C-232-202 C:US 1:1240 2:1800 198.232.203/24 DCBS-C-232-203 C:US 1:1240 2:1800 198.247.176/24 OKSTATE C:US 1:93 198.247.177/24 OKSTATE C:US 1:93 198.247.178/24 OKSTATE C:US 1:93 198.247.179/24 OKSTATE C:US 1:93 198.247.180/24 OKSTATE C:US 1:93 198.247.181/24 OKSTATE C:US 1:93 198.247.182/24 OKSTATE C:US 1:93 198.247.183/24 OKSTATE C:US 1:93 198.247.240/24 HESSTON-1 C:US 1:93 198.252.211/24 NET-ODOE2 C:US 1:1240 2:1800 198.252.231/24 NET-OPRD C:US 1:1240 2:1800 199.0.230/24 WNYHSC-VA-C-0-230 C:US 1:1800 2:1240 199.0.231/24 WNYHSC-VA-C-0-231 C:US 1:1800 2:1240 199.2.133/24 STATENET-DOM C:US 1:1240 2:1800 199.2.160/24 OR-GOV-C-2-160 C:US 1:1240 2:1800 199.2.161/24 OR-GOV-C-2-161 C:US 1:1240 2:1800 199.2.162/24 OR-GOV-C-2-162 C:US 1:1240 2:1800 199.2.163/24 OR-GOV-C-2-163 C:US 1:1240 2:1800 199.2.164/24 OR-GOV-C-2-164 C:US 1:1240 2:1800 199.2.165/24 OR-GOV-C-2-165 C:US 1:1240 2:1800 199.2.166/24 OR-GOV-C-2-166 C:US 1:1240 2:1800 199.2.167/24 OR-GOV-C-2-167 C:US 1:1240 2:1800 199.2.168/24 OR-GOV-C-2-168 C:US 1:1240 2:1800 199.2.169/24 OR-GOV-C-2-169 C:US 1:1240 2:1800 199.2.170/24 OR-GOV-C-2-170 C:US 1:1240 2:1800 199.2.171/24 OR-GOV-C-2-171 C:US 1:1240 2:1800 199.2.172/24 OR-GOV-C-2-172 C:US 1:1240 2:1800 199.2.173/24 OR-GOV-C-2-173 C:US 1:1240 2:1800 199.2.174/24 OR-GOV-C-2-174 C:US 1:1240 2:1800 199.2.175/24 OR-GOV-C-2-175 C:US 1:1240 2:1800 199.2.176/24 OR-GOV-C-2-176 C:US 1:1240 2:1800 199.2.177/24 OR-GOV-C-2-177 C:US 1:1240 2:1800 199.2.178/24 OR-GOV-C-2-178 C:US 1:1240 2:1800 199.2.179/24 OR-GOV-C-2-179 C:US 1:1240 2:1800 199.2.180/24 OR-GOV-C-2-180 C:US 1:1240 2:1800 199.2.181/24 OR-GOV-C-2-181 C:US 1:1240 2:1800 199.2.182/24 OR-GOV-C-2-182 C:US 1:1240 2:1800 199.2.183/24 OR-GOV-C-2-183 C:US 1:1240 2:1800 199.2.184/24 OR-GOV-C-2-184 C:US 1:1240 2:1800 199.2.185/24 OR-GOV-C-2-185 C:US 1:1240 2:1800 199.2.186/24 OR-GOV-C-2-186 C:US 1:1240 2:1800 199.2.187/24 OR-GOV-C-2-187 C:US 1:1240 2:1800 199.2.188/24 OR-GOV-C-2-188 C:US 1:1240 2:1800 199.2.189/24 OR-GOV-C-2-189 C:US 1:1240 2:1800 199.2.190/24 OR-GOV-C-2-190 C:US 1:1240 2:1800 199.2.191/24 OR-GOV-C-2-191 C:US 1:1240 2:1800 199.5.249/24 BADER C:US 1:1225 2:267 3:266 199.10.239/24 GUAMNET3 C:US 1:19 2:568 199.10.240/24 PENTAGON C:US 1:19 2:568 199.10.241/24 AURORA-NET C:US 1:19 2:568 199.34.32/19 DIGEX-NET4 C:US 1:2548 199.36.0/24 PLABMIL C:US 1:701 2:702 199.43.113/24 IO-NET2 C:CA 1:701 2:702 199.74.0/24 FOR-OR-C-74-0 C:US 1:1240 2:1800 199.74.1/24 FOR-OR-C-74-1 C:US 1:1240 2:1800 199.74.2/24 FOR-OR-C-74-2 C:US 1:1240 2:1800 199.74.3/24 FOR-OR-C-74-3 C:US 1:1240 2:1800 199.74.4/24 FOR-OR-C-74-4 C:US 1:1240 2:1800 199.74.5/24 FOR-OR-C-74-5 C:US 1:1240 2:1800 199.74.6/24 FOR-OR-C-74-6 C:US 1:1240 2:1800 199.74.7/24 FOR-OR-C-74-7 C:US 1:1240 2:1800 199.74.168/24 HAWAII-INC C:US 1:372 2:297 199.74.170/24 TEA5 C:US 1:114 199.88.199/24 WES C:US 1:2551 199.98.150/24 PSINET-C5 C:US 1:2149 2:174 199.98.151/24 PSINET-C5 C:US 1:2149 2:174 199.98.152/24 PSINET-C5 C:US 1:2149 2:174 199.98.153/24 PSINET-C5 C:US 1:2149 2:174 199.98.154/24 PSINET-C5 C:US 1:2149 2:174 199.98.155/24 PSINET-C5 C:US 1:2149 2:174 199.122.38/24 SATFA2 C:US 1:19 2:568 199.122.39/24 DMC-S C:US 1:19 2:568 199.122.40/24 EUSA-MANPWR2 C:US 1:19 2:568 199.164.165/24 RAYONTKOCO C:US 1:1332 199.165.133/24 CRUZCOM C:US 1:1240 2:1800 199.232/16 CENT-CIDR-01 C:US 1:1800 2:1240 200.9.32/24 CRNET C:CR 1:1800 2:1240 202.13.4/24 TUFSNET1 C:JP 1:372 2:297 202.13.5/24 TUFSNET2 C:JP 1:372 2:297 202.13.183/24 WIDE-JOIN C:JP 1:372 2:297 202.17.184/24 MICNET1 C:JP 1:372 2:297 202.17.185/24 MICNET2 C:JP 1:372 2:297 202.17.186/24 MICNET3 C:JP 1:372 2:297 202.17.187/24 MICNET4 C:JP 1:372 2:297 202.18.152/24 KCT-NET1 C:JP 1:372 2:297 202.18.153/24 KCT-NET2 C:JP 1:372 2:297 202.18.154/24 KCT-NET3 C:JP 1:372 2:297 202.18.155/24 KCT-NET4 C:JP 1:372 2:297 202.19.177/24 ANANTEC C:JP 1:372 2:297 202.23.116/24 FUJITAHUNET1 C:JP 1:372 2:297 202.23.117/24 FUJITAHUNET2 C:JP 1:372 2:297 202.24.140/24 KUNET1 C:JP 1:372 2:297 202.24.141/24 KUNET2 C:JP 1:372 2:297 202.24.142/24 KUNET3 C:JP 1:372 2:297 202.24.143/24 KUNET4 C:JP 1:372 2:297 202.25.99/24 MUSE C:JP 1:372 2:297 202.25.104/24 NCVCNET1 C:JP 1:372 2:297 202.25.105/24 NCVCNET2 C:JP 1:372 2:297 202.25.106/24 NCVCNET3 C:JP 1:372 2:297 202.25.107/24 NCVCNET4 C:JP 1:372 2:297 202.25.108/24 NCVCNET5 C:JP 1:372 2:297 202.25.109/24 NCVCNET6 C:JP 1:372 2:297 202.25.110/24 NCVCNET7 C:JP 1:372 2:297 202.25.111/24 NCVCNET8 C:JP 1:372 2:297 202.25.144/24 JAPAN-INET-C7 C:JP 1:97 202.25.145/24 JAPAN-INET-C8 C:JP 1:97 202.25.146/24 JAPAN-INET-C9 C:JP 1:97 202.25.147/24 JAPAN-INET-C10 C:JP 1:97 202.25.148/24 JAPAN-INET-C11 C:JP 1:97 202.25.149/24 JAPAN-INET-C12 C:JP 1:97 202.25.150/24 JAPAN-INET-C13 C:JP 1:97 202.25.151/24 JAPAN-INET-C14 C:JP 1:97 202.25.152/24 JAPAN-INET-C15 C:JP 1:97 202.25.153/24 JAPAN-INET-C16 C:JP 1:97 202.25.154/24 JAPAN-INET-C17 C:JP 1:97 202.25.155/24 JAPAN-INET-C18 C:JP 1:97 202.25.156/24 JAPAN-INET-C19 C:JP 1:97 202.25.157/24 JAPAN-INET-C20 C:JP 1:97 202.25.158/24 JAPAN-INET-C21 C:JP 1:97 202.25.159/24 JAPAN-INET-C22 C:JP 1:97 202.26.64/24 NALNET1 C:JP 1:372 2:297 202.26.65/24 NALNET2 C:JP 1:372 2:297 202.26.66/24 NALNET3 C:JP 1:372 2:297 202.26.67/24 NALNET4 C:JP 1:372 2:297 202.26.68/24 NALNET5 C:JP 1:372 2:297 202.26.69/24 NALNET6 C:JP 1:372 2:297 202.26.70/24 NALNET7 C:JP 1:372 2:297 202.26.71/24 NALNET8 C:JP 1:372 2:297 202.26.72/24 NALNET9 C:JP 1:372 2:297 202.26.73/24 NALNET10 C:JP 1:372 2:297 202.26.74/24 NALNET11 C:JP 1:372 2:297 202.26.75/24 NALNET12 C:JP 1:372 2:297 202.26.76/24 NALNET13 C:JP 1:372 2:297 202.26.77/24 NALNET14 C:JP 1:372 2:297 202.26.78/24 NALNET15 C:JP 1:372 2:297 202.26.79/24 NALNET16 C:JP 1:372 2:297 202.26.80/24 NALNET17 C:JP 1:372 2:297 202.26.81/24 NALNET18 C:JP 1:372 2:297 202.26.82/24 NALNET19 C:JP 1:372 2:297 202.26.83/24 NALNET20 C:JP 1:372 2:297 202.26.84/24 NALNET21 C:JP 1:372 2:297 202.26.85/24 NALNET22 C:JP 1:372 2:297 202.26.86/24 NALNET23 C:JP 1:372 2:297 202.26.87/24 NALNET24 C:JP 1:372 2:297 202.26.88/24 NALNET25 C:JP 1:372 2:297 202.26.89/24 NALNET26 C:JP 1:372 2:297 202.26.90/24 NALNET27 C:JP 1:372 2:297 202.26.91/24 NALNET28 C:JP 1:372 2:297 202.26.92/24 NALNET29 C:JP 1:372 2:297 202.26.93/24 NALNET30 C:JP 1:372 2:297 202.26.94/24 NALNET31 C:JP 1:372 2:297 202.26.95/24 NALNET32 C:JP 1:372 2:297 202.26.140/24 OSAKA-GU-NET1 C:JP 1:372 2:297 202.26.141/24 OSAKA-GU-NET2 C:JP 1:372 2:297 202.26.142/24 OSAKA-GU-NET3 C:JP 1:372 2:297 202.26.143/24 OSAKA-GU-NET4 C:JP 1:372 2:297 202.26.208/24 KIDNET1 C:JP 1:372 2:297 202.26.209/24 KIDNET2 C:JP 1:372 2:297 202.26.210/24 KIDNET3 C:JP 1:372 2:297 202.26.211/24 KIDNET4 C:JP 1:372 2:297 202.26.212/24 KIDNET5 C:JP 1:372 2:297 202.26.213/24 KIDNET6 C:JP 1:372 2:297 202.26.214/24 KIDNET7 C:JP 1:372 2:297 202.26.215/24 KIDNET8 C:JP 1:372 2:297 202.26.216/24 KIDNET9 C:JP 1:372 2:297 202.26.217/24 KIDNET10 C:JP 1:372 2:297 202.26.218/24 KIDNET11 C:JP 1:372 2:297 202.26.219/24 KIDNET12 C:JP 1:372 2:297 202.26.220/24 KIDNET13 C:JP 1:372 2:297 202.26.221/24 KIDNET14 C:JP 1:372 2:297 202.26.222/24 KIDNET15 C:JP 1:372 2:297 202.26.223/24 KIDNET16 C:JP 1:372 2:297 202.26.254/24 HLANET C:JP 1:372 2:297 202.34.16/24 ASTEC-NET1 C:JP 1:372 2:297 202.34.248/24 ATNET1 C:JP 1:372 2:297 202.34.249/24 ATNET2 C:JP 1:372 2:297 202.34.250/24 ATNET3 C:JP 1:372 2:297 202.34.251/24 ATNET4 C:JP 1:372 2:297 202.35.192/19 NCUNET C:JP 1:1240 2:1800 202.35.240/24 YMU-NET1 C:JP 1:372 2:297 202.35.241/24 YMU-NET2 C:JP 1:372 2:297 202.35.242/24 YMU-NET3 C:JP 1:372 2:297 202.35.243/24 YMU-NET4 C:JP 1:372 2:297 202.35.244/24 YMU-NET5 C:JP 1:372 2:297 202.35.245/24 YMU-NET6 C:JP 1:372 2:297 202.35.246/24 YMU-NET7 C:JP 1:372 2:297 202.35.247/24 YMU-NET8 C:JP 1:372 2:297 202.48.228/24 TIKNET1 C:JP 1:372 2:297 202.48.229/24 TIKNET2 C:JP 1:372 2:297 202.48.230/24 TIKNET3 C:JP 1:372 2:297 202.48.231/24 TIKNET4 C:JP 1:372 2:297 202.252.104/24 JAPAN-INET-C10 C:JP 1:97 202.252.105/24 JAPAN-INET-C11 C:JP 1:97 202.252.106/24 JAPAN-INET-C12 C:JP 1:97 202.252.107/24 JAPAN-INET-C13 C:JP 1:97 Deletions: --133.130/16 TRAD-NET C:JP 1:372 2:297 --133.233/16 STRATEGIC C:JP 1:372 2:297 --192.5.160/24 PENN-STATE-10 C:US 1:1663 --192.12.97/24 MCRC C:US 1:560 2:701 --192.58.109/24 TAMU1 C:US 1:114 --192.58.115/24 NET-TAMU7 C:US 1:114 --192.58.116/24 TAMU8 C:US 1:114 --192.58.117/24 NET-TAMU9 C:US 1:114 --192.58.118/24 NET-TAMU10 C:US 1:114 --192.122.227/24 IEUNET2 C:IE 1:1957 --192.138.239/24 TAMU-2 C:US 1:114 --192.164.40/24 KPMG-NET C:AT 1:1957 --192.164.132/24 DELACHER5 C:AT 1:1957 --193.69.56/24 INFOKOMP C:NO 1:1957 --193.69.96/24 IK-NET C:NO 1:1957 --193.71.2/24 EUNET-NO-2 C:NO 1:1957 --193.71.3/24 EUNET-NO-3 C:NO 1:1957 --193.71.4/24 EUNET-NO-X25 C:NO 1:1957 --193.71.136/24 FALCON-NO C:NO 1:1957 --193.71.168/24 DND-NET C:NO 1:1957 --193.71.176/24 NFT-NET C:NO 1:1957 --193.71.216/24 LANDBRUKSDATA-C-71-21 C:NO 1:1957 --193.71.217/24 LANDBRUKSDATA-C-71-21 C:NO 1:1957 --193.71.218/24 LANDBRUKSDATA-C-71-21 C:NO 1:1957 --193.71.219/24 LANDBRUKSDATA-C-71-21 C:NO 1:1957 --193.71.248/24 UPNET C:NO 1:1957 --193.80.11/24 KPMG-NET4 C:AT 1:1957 --193.80.28/24 EDVG-NET C:AT 1:1957 --193.80.29/24 EDVG-NET C:AT 1:1957 --193.80.30/24 EDVG-NET C:AT 1:1957 --193.80.31/24 EDVG-NET C:AT 1:1957 --193.80.64/24 EUNET-AT2-C-80-64 C:AT 1:1957 --193.80.65/24 EUNET-AT2-C-80-65 C:AT 1:1957 --193.80.66/24 EUNET-AT2-C-80-66 C:AT 1:1957 --193.80.67/24 EUNET-AT2-C-80-67 C:AT 1:1957 --193.80.116/24 LEYKAM-NET C:FR 1:1957 --193.80.117/24 LEYKAM-NET C:AT 1:1957 --193.80.118/24 LEYKAM-NET C:AT 1:1957 --193.80.119/24 LEYKAM-NET C:AT 1:1957 --193.80.120/24 LEYKAM-NET C:AT 1:1957 --193.80.121/24 LEYKAM-NET C:AT 1:1957 --193.80.122/24 LEYKAM-NET C:AT 1:1957 --193.80.123/24 LEYKAM-NET C:AT 1:1957 --193.80.124/24 LEYKAM-NET C:AT 1:1957 --193.80.125/24 LEYKAM-NET C:AT 1:1957 --193.80.126/24 LEYKAM-NET C:AT 1:1957 --193.80.127/24 LEYKAM-NET C:AT 1:1957 --193.80.128/24 LEYKAM-NET C:AT 1:1957 --193.80.129/24 LEYKAM-NET C:AT 1:1957 --193.80.224/24 EUNET-AT-BGP4-TESTNET C:AT 1:1957 --193.80.225/24 EUNET-AT-BGP4-TESTNET C:AT 1:1957 --193.90.20/24 STERLING-SW-OSL C:NO 1:1957 --193.120.205/24 ALD C:IE 1:1957 --193.120.206/24 IEUNET-LOGIN-SERVICES C:IE 1:1957 --193.120.208/24 BAKERRYAN-2 C:IE 1:1957 --193.120.232/24 FEXCO2 C:IE 1:1957 --193.120.241/24 IEUNET-ROUTE3 C:IE 1:1957 --193.120.242/24 IEUNET-ROUTE C:IE 1:1957 --193.120.243/24 IEUNET-ROUTE2 C:IE 1:1957 --193.120.246/24 GALLIMAUFRY-NET C:IE 1:1957 --198.80.13/24 AMPHI-NET C:US 1:1324 --198.80.80/24 ANS-C-80-80 C:US 1:1324 --198.80.81/24 ANS-C-80-81 C:US 1:1324 --198.80.82/24 ANS-C-80-82 C:US 1:1324 --198.80.83/24 ANS-C-80-83 C:US 1:1324 --198.80.84/24 ANS-C-80-84 C:US 1:1324 --198.80.85/24 ANS-C-80-85 C:US 1:1324 --198.80.86/24 ANS-C-80-86 C:US 1:1324 --198.80.87/24 ANS-C-80-87 C:US 1:1324 --198.83.32/24 ANS-C-BLOCK C:US 1:1662 --198.114.180/24 CSCC C:US 1:560 2:701 --198.234.0/24 NETBLK-OHIO-NET C:US 1:1957 --198.234.2/24 NETBLK-OHIO-NET C:US 1:1957 --198.234.15/24 NETBLK-OHIO-NET C:US 1:1957 Expanded listing, sorted by country, then by organization: ========================================================== Austria ------- EUnet EDV Dienstleistungs GmbH, Thurngasse 8/16, A-1090 Wien, AUSTRIA 1:701 Alternet 2:1800 ICM-Atlantic ---------- 192.164/16 EUNET-AT-192.164-AGG (AT) 193.80/16 EUNET-AT-193.80-AGG (AT) Unisource Business Networks, P.O. Box 90934, NL-2509 LX The Hague, NETHERLANDS 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1674 CERN/DANTE 4:1240 ICM-Pacific ------------- 193.172.26/24 EMPB (AT) Canada ------ Internex Online Inc., 1 Yonge St., Suite 1801, Toronto, ON, M4E 1W7, CANADA 1:701 Alternet 2:702 Alternet ------------- 199.43.113/24 IO-NET2 (CA) China ----- Institute of Computing Technology Chinese Academy of Sciences, P.O. Box 2704-10, Beijing, 100080, CHINA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ---------- 159.226/16 NCFC (CN) Institute of Integrated Information Network Technology, Tsinghua University, Beijing, 100084, CHINA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ---------- 166.111/16 TUNET (CN) Peking University, Computer Center, Beijing, 100871, CHINA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ---------- 162.105/16 PUNET (CN) Costa Rica ---------- Red Nacional de Investigacion, Universidad de Costa Rica, San Jose, COSTA RICA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ----------- 200.9.32/24 CRNET (CR) Croatia ------- Globtour, Trg N.S.Zrinskog 1/1, 41000 Zagreb, CROATIA 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific ------------- 193.198.42/24 GLOBTOUR-NET (HR) Czech Republic -------------- State Technical Library, Marianske nam. 5, Prague 1, 113 07, CZECH REPUBLIC 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific ------------- 193.84.188/24 STKNET-C-84-188 (CZ) 193.84.189/24 STKNET-C-84-189 (CZ) France ------ CNRS Universite Paris1, 13 rue du Four, 75006 Paris, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ------------- 193.55.107/24 FR-CNRS1234 (FR) Centre Inter-universitaire de Calcul de Grenoble, BP 53X, F-38041 Grenoble CEDEX, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ------------- 193.54.187/24 FR-GRENET34 (FR) 193.54.188/24 FR-GRENET35 (FR) 193.54.189/24 FR-GRENET36 (FR) FRAMATOME, 10, rue Juliette Recamier, B.P. 3083, F-69398 Lyon CEDEX 03, FRANCE 1:701 Alternet 2:1800 ICM-Atlantic ------------ 192.44.46/24 FNET-FRA-LD (FR) 192.44.47/24 FNET-FRA-LY (FR) IUT universite de Nancy II, Departement Informatique, 2 Ter,Boulevard Charlemagne, 54000 Nancy, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ------------- 193.55.238/24 F-NCY-IUTA-G (FR) 193.55.239/24 F-NCY-IUTA-R (FR) Presidence de l'Universite de Nancy II, 25 Rue Baron Louis, BP 454, 54001 Nancy CEDEX, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ------------ 193.54.39/24 FR-NCY-PN2 (FR) USTL cite scientifique bat M3, 59655 Villeneuve d'Ascq CEDEX, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ------------- 193.48.186/24 FR-LIFL (FR) Germany ------- ECRC, Arabellastr. 17, Munich, Bavaria, 81925, GERMANY 1:1800 ICM-Atlantic 2:1240 ICM-Pacific -------------- 192.109.251/24 ECRC-RBS (DE) 193.23.5/24 ECRC-EBONE (DE) Otto Harrassowitz, Taunusstr. 5, Postfach 2929, D-65019 Wiesbaden, GERMANY 1:701 Alternet 2:1800 ICM-Atlantic ------------- 193.97.189/24 HARRASSO-DE1 (DE) Ireland ------- IEUnet Ltd, O'Reilly Institute, Trinity College, Dublin 2, IRELAND 1:701 Alternet 2:1800 ICM-Atlantic -------------- 192.122.216/21 EUNET-IE-192.122.216- (IE) 192.122.224/21 EUNET-IE-192.122.224- (IE) 193.120/16 EUNET-IE-193.120-AGG (IE) Japan ----- ASTEC, Inc., BR Ichigaya, 6 Minami, Shinjuku, Tokyo, 162, JAPAN 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 202.34.16/24 ASTEC-NET1 (JP) Anan College of Technology, Aoki 265 Minobayashi, Anan, Tokushima, 774, JAPAN 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------- 202.19.177/24 ANANTEC (JP) Fujita Health University, Kutsukake, Tokyoake, Aichi, 477-11, JAPAN 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------- 202.23.116/24 FUJITAHUNET1 (JP) 202.23.117/24 FUJITAHUNET2 (JP) Hiroshima City University, 151-5 Otsuka Numata, Asaminami, Hiroshima, 731-31, JAPAN 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ---------- 165.242/16 HUNET (JP) Japan Network Information Center, Yayoi 2-11-16, Bunkyo-ku, Tokyo, 113, JAPAN 1:97 JvNCnet Regional Network ------------- 202.25.144/24 JAPAN-INET-C7 (JP) 202.25.145/24 JAPAN-INET-C8 (JP) 202.25.146/24 JAPAN-INET-C9 (JP) 202.25.147/24 JAPAN-INET-C10 (JP) 202.25.148/24 JAPAN-INET-C11 (JP) 202.25.149/24 JAPAN-INET-C12 (JP) 202.25.150/24 JAPAN-INET-C13 (JP) 202.25.151/24 JAPAN-INET-C14 (JP) 202.25.152/24 JAPAN-INET-C15 (JP) 202.25.153/24 JAPAN-INET-C16 (JP) 202.25.154/24 JAPAN-INET-C17 (JP) 202.25.155/24 JAPAN-INET-C18 (JP) 202.25.156/24 JAPAN-INET-C19 (JP) 202.25.157/24 JAPAN-INET-C20 (JP) 202.25.158/24 JAPAN-INET-C21 (JP) 202.25.159/24 JAPAN-INET-C22 (JP) 202.252.104/24 JAPAN-INET-C10 (JP) 202.252.105/24 JAPAN-INET-C11 (JP) 202.252.106/24 JAPAN-INET-C12 (JP) 202.252.107/24 JAPAN-INET-C13 (JP) Joint Research Center for Atom Technology, 1-1-4 Higashi, Tsukuba, Ibaraki, 305, JAPAN 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------- 202.34.248/24 ATNET1 (JP) 202.34.249/24 ATNET2 (JP) 202.34.250/24 ATNET3 (JP) 202.34.251/24 ATNET4 (JP) Kitasato University, 1-15-1 Kitasato, Sagamihara, Kanagawa, 228, JAPAN 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------- 202.24.140/24 KUNET1 (JP) 202.24.141/24 KUNET2 (JP) 202.24.142/24 KUNET3 (JP) 202.24.143/24 KUNET4 (JP) Kochi National College of Technology, Monobe Otu 200-1, Nankoku, Kochi, 783, JAPAN 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------- 202.18.152/24 KCT-NET1 (JP) 202.18.153/24 KCT-NET2 (JP) 202.18.154/24 KCT-NET3 (JP) 202.18.155/24 KCT-NET4 (JP) Koto College of Economics, Higashinaga-cho 3-1, OOe, Nishikyo-ku, Kyoto, 610-11, JAPAN 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------- 202.48.228/24 TIKNET1 (JP) 202.48.229/24 TIKNET2 (JP) 202.48.230/24 TIKNET3 (JP) 202.48.231/24 TIKNET4 (JP) Kyushu Institute of Design, 4-9-1 Shiobaru, Minami, Fukuoka, Fukuoka, 815, JAPAN 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------- 202.26.208/24 KIDNET1 (JP) 202.26.209/24 KIDNET2 (JP) 202.26.210/24 KIDNET3 (JP) 202.26.211/24 KIDNET4 (JP) 202.26.212/24 KIDNET5 (JP) 202.26.213/24 KIDNET6 (JP) 202.26.214/24 KIDNET7 (JP) 202.26.215/24 KIDNET8 (JP) 202.26.216/24 KIDNET9 (JP) 202.26.217/24 KIDNET10 (JP) 202.26.218/24 KIDNET11 (JP) 202.26.219/24 KIDNET12 (JP) 202.26.220/24 KIDNET13 (JP) 202.26.221/24 KIDNET14 (JP) 202.26.222/24 KIDNET15 (JP) 202.26.223/24 KIDNET16 (JP) Miyazaki International College, 1415 Kanoh, Kiyotake-cho, Miyazaki-gun, Miyazaki, 889-16, JAPAN 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------- 202.17.184/24 MICNET1 (JP) 202.17.185/24 MICNET2 (JP) 202.17.186/24 MICNET3 (JP) 202.17.187/24 MICNET4 (JP) Miyazaki Municipal University, 1-1-2 Funatsuka, Miyazaki, Miyazaki, 880, JAPAN 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 202.25.99/24 MUSE (JP) Nagoya City University, 1 Kawasumi, Mizuho-cho, Mizuho-ku, Nagoya 467, JAPAN 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ------------- 202.35.192/19 NCUNET (JP) National Aerospace Laboratory, 7-44-1 Jindaiji-Higashi, Chofu, Tokyo, 182, JAPAN 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 202.26.64/24 NALNET1 (JP) 202.26.65/24 NALNET2 (JP) 202.26.66/24 NALNET3 (JP) 202.26.67/24 NALNET4 (JP) 202.26.68/24 NALNET5 (JP) 202.26.69/24 NALNET6 (JP) 202.26.70/24 NALNET7 (JP) 202.26.71/24 NALNET8 (JP) 202.26.72/24 NALNET9 (JP) 202.26.73/24 NALNET10 (JP) 202.26.74/24 NALNET11 (JP) 202.26.75/24 NALNET12 (JP) 202.26.76/24 NALNET13 (JP) 202.26.77/24 NALNET14 (JP) 202.26.78/24 NALNET15 (JP) 202.26.79/24 NALNET16 (JP) 202.26.80/24 NALNET17 (JP) 202.26.81/24 NALNET18 (JP) 202.26.82/24 NALNET19 (JP) 202.26.83/24 NALNET20 (JP) 202.26.84/24 NALNET21 (JP) 202.26.85/24 NALNET22 (JP) 202.26.86/24 NALNET23 (JP) 202.26.87/24 NALNET24 (JP) 202.26.88/24 NALNET25 (JP) 202.26.89/24 NALNET26 (JP) 202.26.90/24 NALNET27 (JP) 202.26.91/24 NALNET28 (JP) 202.26.92/24 NALNET29 (JP) 202.26.93/24 NALNET30 (JP) 202.26.94/24 NALNET31 (JP) 202.26.95/24 NALNET32 (JP) National Cardiovascular Center Research Institute, 5-7-1 Fujishirodai, Suita, Osaka, 565, JAPAN 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------- 202.25.104/24 NCVCNET1 (JP) 202.25.105/24 NCVCNET2 (JP) 202.25.106/24 NCVCNET3 (JP) 202.25.107/24 NCVCNET4 (JP) 202.25.108/24 NCVCNET5 (JP) 202.25.109/24 NCVCNET6 (JP) 202.25.110/24 NCVCNET7 (JP) 202.25.111/24 NCVCNET8 (JP) Osaka Gakuin University, 2-26-1 Kishibe-Minami, Suita, Osaka, 564, JAPAN 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------- 202.26.140/24 OSAKA-GU-NET1 (JP) 202.26.141/24 OSAKA-GU-NET2 (JP) 202.26.142/24 OSAKA-GU-NET3 (JP) 202.26.143/24 OSAKA-GU-NET4 (JP) The Japanese Red Cross Central Blood Center, 4-1-31 Hiroo, Shibuya-ku, Tokyo, 160, JAPAN 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------- 202.26.254/24 HLANET (JP) Tokyo University of Foreign Studies, Nishigahara 4-51-21, Kita-ku, Tokyo, 114, JAPAN 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ----------- 202.13.4/24 TUFSNET1 (JP) 202.13.5/24 TUFSNET2 (JP) WIDE Project, Keio Univ. 5322 Endo, Fujisawa, Kanagawa, 252, JAPAN 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 192.50.36/24 WIDE-EXP-NET (JP) 192.50.43/24 WIDE-EXP-NET2 (JP) 192.50.44/24 WIDE-MOBILE1 (JP) 192.50.45/24 WIDE-MOBILE2 (JP) 192.50.62/24 WIDE-ISDN (JP) 192.218.228/24 WIDE-SAT-NET2 (JP) 202.13.183/24 WIDE-JOIN (JP) Yamanashi Medical University, Shimokato 1110, Tamaho-cho, Nakakoma-gun, Yamanashi, 409-38, JAPAN 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------- 202.35.240/24 YMU-NET1 (JP) 202.35.241/24 YMU-NET2 (JP) 202.35.242/24 YMU-NET3 (JP) 202.35.243/24 YMU-NET4 (JP) 202.35.244/24 YMU-NET5 (JP) 202.35.245/24 YMU-NET6 (JP) 202.35.246/24 YMU-NET7 (JP) 202.35.247/24 YMU-NET8 (JP) Norway ------ EUnet Norway, Forskningsparken, Gaustadallen 21, N-0371 Oslo, NORWAY 1:701 Alternet 2:1800 ICM-Atlantic --------- 193.69/16 EUNET-NO-193.69-AGG (NO) 193.71/16 EUNET-NO-193.71-AGG (NO) 193.90/16 EUNET-NO-193.90-AGG (NO) Portugal -------- Instituto Superior de Estatistica e Gestao de Informacao, Universidade Nova de Lisboa, Travessa Estevao Pinto, 1000 Lisboa, PORTUGAL 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific -------------- 193.136.112/24 UNL-FE-1 (PT) LNEC - CI, 1799 Lisboa CODEX, PORTUGAL 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific -------------- 193.136.104/24 LNEC-1 (PT) 193.136.105/24 LNEC-2 (PT) 193.136.106/24 LNEC-3 (PT) 193.136.107/24 LNEC-4 (PT) 193.136.108/24 LNEC-5 (PT) 193.136.109/24 LNEC-6 (PT) Slovakia -------- Institute of Computer Technology, Technical University in Kosice, B. Nemcovej 3, Kosice, 042 00, SLOVAKIA 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific ------------- 193.87.100/24 CANET (SK) United Kingdom -------------- Hillside Systems, 61 Hillside Avenue, Canterbury, Kent, CT2 8HA, Great Britain, UNITED KINGDOM 1:701 Alternet 2:1800 ICM-Atlantic ------------ 192.88.50/24 NET-HILLSIDE (GB) United States ------------- Air Force Information Warfare Center, 230 Hall Blvd, Ste 371, San Antonio, TX 78243-7063, USA 1:19 Milnet (FIX-East) 2:568 Milnet (FIX-West) ------------- 199.10.241/24 AURORA-NET (US) Assistant Chief of Staff, Resource, HQ USFK/EUSA, UNIT #15236, APO, AP 96205-0009, USA 1:19 Milnet (FIX-East) 2:568 Milnet (FIX-West) ------------- 199.122.40/24 EUSA-MANPWR2 (US) Bureau of Medicine and Surgery, Naval Medical Center, N. Effingham. St., Portsmouth, VA 23708-5100, USA 1:19 Milnet (FIX-East) 2:568 Milnet (FIX-West) ---------- 164.167/16 TIDEMEDNET (US) Bureau of Medicine and Surgery, PSC 490, Box 7606, MID Code 202, FPO, AP 96538-1600, USA 1:19 Milnet (FIX-East) 2:568 Milnet (FIX-West) ------------- 199.10.239/24 GUAMNET3 (US) Bureau of Medicine and Surgery, Room 4C469, The Pentagon, Washington, DC 20350-2000, USA 1:19 Milnet (FIX-East) 2:568 Milnet (FIX-West) ------------- 199.10.240/24 PENTAGON (US) CICNet Inc., 2901 Hubbard Ave., Ann Arbor, MI 48105, USA 1:233 UMnet (University of Michigan) 2:237 MichNet (MERIT) 3:266 CICNET at MERIT 4:267 CICNET at UIUC 5:1225 CICNET at Argonne Labs ------------- 198.108.58/24 CICNET-HQ2 (US) CICNet, Inc., 2901 Hubbard Ave., Ann Arbor, MI 48105, USA 1:266 CICNET at MERIT 2:1225 CICNET at Argonne Labs 3:267 CICNET at UIUC ------------- 198.87.242/24 CICNET-2 (US) CentNet, Inc., 90 Sherman St., Cambridge, MA 02140-3233, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ---------- 199.232/16 CENT-CIDR-01 (US) Computer Aided Engineering Network (CAEN), University of Michigan, Ann Arbor, MI 48109-2092, USA 1:233 UMnet (University of Michigan) 2:237 MichNet (MERIT) 3:266 CICNET at MERIT 4:267 CICNET at UIUC 5:1225 CICNET at Argonne Labs ------------- 198.108.56/24 CAEN-BB (US) Credit Suisse, 1 Liberty Plaza, 165 Broadway, 3rd Floor, New York, NY 10006, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ---------- 161.202/16 CSUISSE-USA (US) 168.1/16 CSH-B-BLK3 (US) 198.232.137/24 CSH-C-BLK3 (US) 198.232.138/24 CSH-C-BLK3 (US) Cruz Communications, 258 Waugh Ave., Santa Cruz, CA 95065, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic -------------- 199.165.133/24 CRUZCOM (US) DLA Systems Automation Center, 3990 E. Broad St., Columbus, OH 43216, USA 1:19 Milnet (FIX-East) 2:568 Milnet (FIX-West) ------------- 198.25.155/24 DLA-C156 (US) DOIM, 54th TACOM, Caserma Ederle, USASETAF, 54th TACOM, APO, AE 09630, USA 1:19 Milnet (FIX-East) 2:568 Milnet (FIX-West) ---------- 136.209/16 VICENZA-NET2 (US) Defense Finance Accounting Service - Denver Center, DFAS-DE/SCC, Lowry Air Force Base, CO 80279-5000, USA 1:568 Milnet (FIX-West) 2:19 Milnet (FIX-East) ---------- 152.229/16 DMC-DE-NET (US) Defense MegaCenter-St Louis, 4300 Goodfellow Blvd, St Louis, MO 63120-1798, USA 1:19 Milnet (FIX-East) 2:568 Milnet (FIX-West) ------------- 199.122.39/24 DMC-S (US) Department of Energy, Nevada Field Office, PO Box 95487, Las Vegas, NV 89193-5487, USA 1:291 Energy Science Network (FIX-West) 2:293 Energy Science Network (FIX-East) ---------- 132.172/16 HANDS (US) 149.252/16 DOE-NV3 (US) Digital Express Group Inc., 6006 Greenbelt Rd, Greenbelt, MD 20770, USA 1:2548 DIGEX-AS ------------- 198.179.16/21 DIGEX1 (US) 198.180.32/19 NETBLK-DIGEX-NET4 (US) 198.187.32/19 DIGEX-NET5 (US) 199.34.32/19 DIGEX-NET4 (US) Duke Power Company, P. O. Box 1008, Charlotte, NC 28201-1008, USA 1:1329 ANS Greensboro - DNSS 75 ---------- 162.113/16 DUKEPOWER2 (US) Effective Management Systems, Inc., 12000 West Park Place, Milwaukee, WI 53224, USA 1:1225 CICNET at Argonne Labs 2:267 CICNET at UIUC 3:266 CICNET at MERIT ---------- 151.106/16 EMS (US) GageTalker, 13680 NE 16th St, Belleue, WA 98005, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.153/24 PSINET-C5 (US) General DataComm, Inc., Park Road Extension, PO Box 1299, Middlebury, CT 06762-1299, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.150/24 PSINET-C5 (US) HESSTON COLLEGE, Box 3000, Hesston, KS 67062, USA 1:93 MIDnet -------------- 198.247.240/24 HESSTON-1 (US) Hawaii Dept. of Education, 2565 The Mall, Honolulu, HI 96822, USA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ---------- 165.248/16 HAWAIIDOE (US) Hawaii Information Network Corp., City Financial Tower, 201 Merchant, Suite 1500, Honolulu, HI 96813, USA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------- 199.74.168/24 HAWAII-INC (US) Helen Bader Foundation, 777 East Wisconsin Avenue, Suite 3275, Milwaukee, WI 53202, USA 1:1225 CICNET at Argonne Labs 2:267 CICNET at UIUC 3:266 CICNET at MERIT ------------ 199.5.249/24 BADER (US) Hewlett-Packard Company, 19420 Homestead Road, Cupertino, CA 95014, USA 1:200 BARRNet 2:201 BARRNet 5:560 NEARnet Regional Network ----------- 192.6.67/24 NETBLK-HP208 (US) Hitachi Micro Systems, Inc., 180 Rose Orchard Way, San Jose, CA 95134, USA 1:2551 NETCOM ------------- 192.131.10/23 HMSI1 (US) IFC Communications, 23715 W. Malibu Rd., Suite 318, Malibu, CA 90265, USA 1:1740 CERFnet -------------- 198.178.225/24 IFCMO (US) ISOCOR, 12011 San Vicente Blvd Suite 500, Los Angeles, CA 90049, USA 1:701 Alternet 2:702 Alternet ------------ 198.6.228/24 ISOCOR-NET1 (US) 198.6.229/24 ISOCOR-NET1 (US) 198.6.230/24 ISOCOR-NET1 (US) 198.6.231/24 ISOCOR-NET1 (US) Info Comm, 1558 Fernside Street, Redwood City, CA 94061, USA 1:2551 NETCOM -------------- 192.100.150/23 INFOCOMM-NET-150 (US) Information Resources, Inc., 1925 N. Lynn Street, Suite 1000, Arlington, VA 22209, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.155/24 PSINET-C5 (US) Intel Corporation, Corporate Information Services, 1900 Prairie City Road, FM1-56, Folsom, CA 95670, USA 3:210 Westnet Regional Network (Utah Attachment) - ENSS 142 4:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 -------------- 192.102.197/24 LOCALNET16 (US) Intermountain Health Care, 36 South State, 8th Floor, Salt Lake City, UT 84111, USA 1:210 Westnet Regional Network (Utah Attachment) - ENSS 142 2:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 ---------- 159.212/16 IHCNET (US) John Jay College of Criminal Justice, CUNY, 445 West 59th Street, Brooklyn, NY 10019, USA 1:1662 CUNY, New York, New York ------------ 198.83.28/24 ANS-C-BLOCK (US) KPMG Peat Marwick, 2001 M St. NW, Washington, DC 20036, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.154/24 PSINET-C5 (US) Lightside, Inc., 101 N. Citrus, #4A, Covina, CA 91723, USA 1:1322 ANS Los Angeles - DNSS 19 ------------- 198.81.209/24 LIGHT-DMZ (US) Martin Marietta Astronautics Group, 12257 State Highway 121, Littleton, CO 80127, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic --------- 166.31/16 MMC-NET16 (US) Mental Health Div. of Dept. of Human Resources, 2575 Bittern St. NE, Salem, OR 97310, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic -------------- 198.176.229/24 NET-MHDDSD (US) MicroTech Conversion Systems, 940 Industrial Av., Palo Alto, CA 94303, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ------------- 192.83.234/24 MICROTECH (US) Milwaukee County Medical Complex, 8700 W. Wisconsin Avenue, Milwaukee, WI 53226, USA 1:1225 CICNET at Argonne Labs 2:267 CICNET at UIUC 3:266 CICNET at MERIT -------------- 198.133.187/24 MCMC1 (US) 198.133.188/24 MCMC2 (US) 198.133.189/24 MCMC3 (US) Mobil Administrative Services Company Inc., P.O. Box 650232, Dallas, TX 75265-023, USA 1:114 SESQUINET Regional Network --------- 158.27/16 MOBILNET7 (US) NASA Goddard Space Flight Center, Greenbelt, MD 20771, USA 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) ------------- 192.225.82/24 GSFC23 (US) 192.225.83/24 GSFC24 (US) Net Access, P.O. Box 502, Glenside, PA 19038, USA 1:204 PSCNET Regional Network 2:1206 PSCNET Regional Network ------------ 192.204.4/24 NETAXS (US) Oklahoma State University, MSB Room, Stillwater, OK 74075, USA 1:93 MIDnet -------------- 198.247.176/24 OKSTATE (US) 198.247.177/24 OKSTATE (US) 198.247.178/24 OKSTATE (US) 198.247.179/24 OKSTATE (US) 198.247.180/24 OKSTATE (US) 198.247.181/24 OKSTATE (US) 198.247.182/24 OKSTATE (US) 198.247.183/24 OKSTATE (US) Oregon Dept. of Consumer and Business Services, Labor & Industries Bldg., Salem, OR 97310, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic -------------- 198.232.198/24 DCBS-C-232-198 (US) 198.232.199/24 DCBS-C-232-199 (US) 198.232.200/24 DCBS-C-232-200 (US) 198.232.201/24 DCBS-C-232-201 (US) 198.232.202/24 DCBS-C-232-202 (US) 198.232.203/24 DCBS-C-232-203 (US) Oregon Dept. of Energy, 625 Marion St NE, Salem, OR 97310, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic -------------- 198.252.211/24 NET-ODOE2 (US) Oregon Dept. of Forestry, 2600 State St, Salem, OR 97310, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ----------- 199.74.0/24 FOR-OR-C-74-0 (US) 199.74.1/24 FOR-OR-C-74-1 (US) 199.74.2/24 FOR-OR-C-74-2 (US) 199.74.3/24 FOR-OR-C-74-3 (US) 199.74.4/24 FOR-OR-C-74-4 (US) 199.74.5/24 FOR-OR-C-74-5 (US) 199.74.6/24 FOR-OR-C-74-6 (US) 199.74.7/24 FOR-OR-C-74-7 (US) Oregon Dept. of Transportation, 135 Transportation Bldg, Salem, OR 97310, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ---------- 167.131/16 NET-OREDOT (US) Oregon Parks & Recreation Department, Vicks Bldg 525 Trade St SE, Salem, OR 97310, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic -------------- 198.252.231/24 NET-OPRD (US) Oregon State Library, State Library Building, Salem, OR 97310, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ------------- 192.136.62/24 NET-ORMALL (US) Philadelphia College of Textiles and Science, School House Lane and Henry Ave, Philadelphia, PA 19144, USA 1:204 PSCNET Regional Network 2:1206 PSCNET Regional Network -------------- 192.204.122/24 TEXSCI-3 (US) 192.204.123/24 TEXSCI-4 (US) Photronics Inc., 1913 Tarob Court, Milpitas, CA 95035, USA 1:701 Alternet 2:702 Alternet ----------- 199.36.0/24 PLABMIL (US) Pinellas County Government, 400 South Fort Harrison Avenue, Clearwater, FL 34616, USA 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) ---------- 136.174/16 PINELLAS (US) Public Utility Commission, 550 Capital St. NE, Salem, OR 97310, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ------------- 198.177.16/24 NET-ORECAP1 (US) 198.177.17/24 NET-ORECAP2 (US) 198.177.18/24 NET-ORECAP3 (US) 198.177.19/24 NET-ORECAP4 (US) 198.177.20/24 NET-ORECAP5 (US) 198.177.21/24 NET-ORECAP6 (US) 198.177.22/24 NET-ORECAP7 (US) 198.177.23/24 NET-ORECAP8 (US) 198.177.24/24 NET-ORECAP9 (US) 198.177.25/24 NET-ORECAP10 (US) 198.177.26/24 NET-ORECAP11 (US) 198.177.27/24 NET-ORECAP12 (US) Ray Ontko & Co., P.O. Box 9, Richmond, IN 47375, USA 1:1332 ANS Denver - DNSS 99 -------------- 199.164.165/24 RAYONTKOCO (US) SECURITY ASSISTANCE TRAINING FIELD ACTIVITY, 2017 CUNNINGHAM DR., HAMPTON, VA 23666, USA 1:19 Milnet (FIX-East) 2:568 Milnet (FIX-West) ------------- 199.122.38/24 SATFA2 (US) Salt Lake City Corp., 72 East 400 South, Suite 400 Salt Lake City, UT 84111, USA 1:210 Westnet Regional Network (Utah Attachment) - ENSS 142 2:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 -------------- 192.100.7/24 SLCCORP-ENG (US) 192.100.8/24 SLCCORP-UTIL (US) 198.185.173/24 SLCCORP5 (US) 198.185.174/24 SLCCORP5 (US) 198.185.175/24 SLCCORP5 (US) 198.185.176/24 SLCCORP5 (US) 198.185.177/24 SLCCORP5 (US) 198.99.143/24 SLCCORP2 (US) 198.99.144/24 SLCCORP3 (US) 198.99.145/24 SLCCORP4 (US) Schuller International, Inc, P.O. Box 5108, Denver, CO 80217, USA 1:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 2:210 Westnet Regional Network (Utah Attachment) - ENSS 142 --------- 166.92/16 SCHULLER-NET (US) Southern College, P.O. Box 370, Collegedale, TN 37315-0370, USA 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) -------------- 192.239.247/24 STHRNCOL-NET (US) 198.78.253/24 STHRNCOL-NET-C-78-253 (US) 198.78.254/24 STHRNCOL-NET-C-78-254 (US) 198.78.255/24 STHRNCOL-NET-C-78-255 (US) Sprint, 13221 Woodland Park Road, Herndon, VA 22071, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ------------- 192.157.37/24 SPRINTLINK9 (US) State of Oregon, 1225 Ferry St SE, Salem, OR 97310, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ------------ 199.2.160/24 OR-GOV-C-2-160 (US) 199.2.161/24 OR-GOV-C-2-161 (US) 199.2.162/24 OR-GOV-C-2-162 (US) 199.2.163/24 OR-GOV-C-2-163 (US) 199.2.164/24 OR-GOV-C-2-164 (US) 199.2.165/24 OR-GOV-C-2-165 (US) 199.2.166/24 OR-GOV-C-2-166 (US) 199.2.167/24 OR-GOV-C-2-167 (US) 199.2.168/24 OR-GOV-C-2-168 (US) 199.2.169/24 OR-GOV-C-2-169 (US) 199.2.170/24 OR-GOV-C-2-170 (US) 199.2.171/24 OR-GOV-C-2-171 (US) 199.2.172/24 OR-GOV-C-2-172 (US) 199.2.173/24 OR-GOV-C-2-173 (US) 199.2.174/24 OR-GOV-C-2-174 (US) 199.2.175/24 OR-GOV-C-2-175 (US) 199.2.176/24 OR-GOV-C-2-176 (US) 199.2.177/24 OR-GOV-C-2-177 (US) 199.2.178/24 OR-GOV-C-2-178 (US) 199.2.179/24 OR-GOV-C-2-179 (US) 199.2.180/24 OR-GOV-C-2-180 (US) 199.2.181/24 OR-GOV-C-2-181 (US) 199.2.182/24 OR-GOV-C-2-182 (US) 199.2.183/24 OR-GOV-C-2-183 (US) 199.2.184/24 OR-GOV-C-2-184 (US) 199.2.185/24 OR-GOV-C-2-185 (US) 199.2.186/24 OR-GOV-C-2-186 (US) 199.2.187/24 OR-GOV-C-2-187 (US) 199.2.188/24 OR-GOV-C-2-188 (US) 199.2.189/24 OR-GOV-C-2-189 (US) 199.2.190/24 OR-GOV-C-2-190 (US) 199.2.191/24 OR-GOV-C-2-191 (US) State of Tennessee Office for Information Resources, 598 James Robertson Parkway, Third Floor, Nashville, TN 37243-0560, USA 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) ------------ 198.79.80/24 NAS-S17 (US) 198.79.81/24 NAS-S18 (US) 198.79.82/24 NAS-S19 (US) 198.79.83/24 NAS-S20 (US) Statenet (STATENET-DOM), 2101 K. Street, Sacremento, CA 95814, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ------------ 199.2.133/24 STATENET-DOM (US) Texas Department of Health, 211 NW 1st St, Andrews, TX 79714, USA 1:114 SESQUINET Regional Network -------------- 198.151.150/24 TXASHLTH-C3 (US) Texas Education Agency, 1701 Congress Ave, Austin, TX 78701, USA 1:114 SESQUINET Regional Network ------------- 199.74.170/24 TEA5 (US) The Future Now, 76 9th Avenue, 5th Fl., New York, NY 10011, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.152/24 PSINET-C5 (US) Time Warner Cable, 160 Inverness Dr. W., Englewood, CO 80112, USA 1:2551 NETCOM ------------ 198.59.12/23 TIME-WARNER (US) Trident Data Systems, 5933 w. Century Blvd., Los Angeles, CA 90045, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------ 192.203.1/24 TDSCA-NET (US) University of Hawaii Community College System, 2565 The Mall, Honolulu, HI 96822, USA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ---------- 166.122/16 HAWAIICC (US) University of Nebraska Med Center, 600 S 42nd Street, Omaha, NE 68198, USA 1:93 MIDnet ------------- 192.198.36/24 UNMC8 (US) 192.198.44/24 UNMC8 (US) 192.198.45/24 UNMC8 (US) 192.198.46/24 UNMC8 (US) WNYHSC-Veteran's Administration Medical Center, 3495 Bailey Avenue, Buffalo, NY 14125, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ------------ 199.0.230/24 WNYHSC-VA-C-0-230 (US) 199.0.231/24 WNYHSC-VA-C-0-231 (US) Whittaker Electronic Systems, 1785 Voyager Avenue, Simi Valley, CA 93063, USA 1:2551 NETCOM ------------- 199.88.199/24 WES (US) Wiley, Rein & Fielding, 1776 K Street, N.W., Washington, DC 20006, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.151/24 PSINET-C5 (US) Yankee Atomic Electric Company, 580 Main Street, Bolton, MA 01740, USA 1:560 NEARnet Regional Network 2:701 Alternet ------------- 198.112.68/24 YANKEE-198 (US) ========================================================== The following Midlevel/Regional peering sessions have also been added: AS 689 - AS-NSFNET-T3-BB-AS - ENSS 160 Peer: 147.225.1.191 - NSFNET/ANSnet Research Network - tweedledee.ans.net ========================================================== AS690 CIDR Squeezings Report: 722 Nets, 23 ASs, 98 Aggregates -------------------------------------------------------------- 722 (35%) of the ever-announced more-specific routes within aggregates have been withdrawn. 442 of those were withdrawn within the last week. 155 the week before that. 122 the week before that. 23 ASs have registered aggregates in the PRDB. 20 of those are announcing aggregates. 11 have withdrawn at least one more specific route. 98 Aggregates are configured. 88 of these were Top-Level Aggregates (not nested in another aggregate). 69 of these were announced to AS690 as of yesterday. 58 of those have at least one subnet configured (the other 11 may be saving. the Internet future subnet announcements). 29 have stopped announcing at least one configured more specific route. 19 have stopped announcing half of their configured more specific routes. 16 have stopped announcing most (80%) of their more specific routes. See 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.t3p Information is also avaiable through the PRDB whois server. Type "whois -h prdb.merit.edu help" for details. -------------------------------------------------------------------------- REPORT CHANGES: (Updated March 24, 1994) Metric:AS(NSS) - Historically, peer networks with multiple connections to AS 690 could only select which of those connections their networks would take by creating "Fake" AS numbers, and using those in the PRDB Metric:AS announcement lists. Some time in the next few weeks we will begin supporting an expanded syntax, where the AS may be followed by an optional NSS peer number in parentheses. Eventually, this syntax will be used to replace most or all of the current Fake ASs. This change will affect *all* places that the announcement lists are reported: all whois queries, all network reports, this "NWG" report, and the Auto-NACR. If you have code which parses these announcement lists, please be aware that that code may need modifications soon. CIDR Reports: There is a new "whois" option to list aggregates in the PRDB: whois -h prdb.merit.edu listaggs will produce a listing of the currently registered aggregates. There is also a new report on "nestings" of PRDB-registered aggregates with their more specific routes: nets.non-classful. Anyone considering configuring an aggregate into the PRDB (and you all should be!) is encouraged to pre-check that aggregate by typing the command: whois -h prdb.merit.edu 'aggchk ' (where "" is the aggregate description). This command will list all of the other entries in the PRDB that are more specific routes of , as well as any aggregates all ready configured that contain . The output includes the AUP and announcement lists of each of the nets printed, with discrepancies flagged. This is the same program that we use for sanity-checking the NACRs that you submit. The archived discussion list "db-disc@merit.edu" exists for discussion of PRDB issues. Send a message to "db-disc-request@merit.edu" to subscribe. --Dale Johnson (dsj@merit.edu) -------------------------------------------------------------------------- Please send all requests for configuration changes to nsfnet-admin@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. ******************************* --Steve Widmayer Merit/NSFNET skw@merit.edu --Enke Chen Merit/NSFNET enke@merit.edu --Steven J. Richardson Merit/NSFNET sjr@merit.edu - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 09:09:46 1994 Received: from pepper.merit.edu (pepper.merit.edu [35.42.1.50]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id JAA27168; Fri, 15 Apr 1994 09:09:44 -0400 Received: by pepper.merit.edu (4.1/client-0.9) id AA06771; Fri, 15 Apr 94 09:09:44 EDT From: epg@merit.edu Message-Id: <9404151309.AA06771@pepper.merit.edu> Subject: Re: 20402 routing entries To: roll@Stupi.SE (Peter Lothberg) Date: Fri, 15 Apr 94 9:09:43 EDT Cc: eowg@fnc.gov, regional-techs@merit.edu, bgpd@merit.edu In-Reply-To: ; from "Peter Lothberg" at Apr 15, 94 12:47 pm X-Mailer: ELM [version 2.3 PL11] > > I knew this sounds hard, but; > > Offer those who don't talk BGP4, to be disconnected by 15-MAY or so if > they don't change. > > -peter > Not hard, just unrealistic. --Elise - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 10:10:16 1994 Received: from psi.com (psi.com [192.67.6.2]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id KAA04254; Fri, 15 Apr 1994 10:09:59 -0400 Received: from us.psi.com by psi.com (4.1/2.1-PSI/PSINet) id AA11014; Fri, 15 Apr 94 10:08:56 EDT Received: by us.psi.com (4.1/SMI-4.1.3-PSI-pop) id AA00916; Fri, 15 Apr 94 10:09:04 EDT Message-Id: <9404151409.AA00916@us.psi.com> To: Peter Lothberg Cc: epg@merit.edu, vaf@valinor.stanford.edu (Vince Fuller), bgpd@merit.edu, eowg@fnc.gov, regional-techs@merit.edu Subject: Re: 20402 routing entries In-Reply-To: Your message of "Fri, 15 Apr 1994 12:47:51 +0700." Date: Fri, 15 Apr 1994 10:09:04 -0400 From: "Martin Lee Schoffstall" it would have been a reasonable approach had cisco and/or other vendors had a standard release support BGP4 without bugs 12 months ago and had you given 12 months notice marty > > Yes, we have again started trying to get folks to move to BGP4 - heck we > > are still trying to get some folks to move to BGP. The results are slow > > in coming. > > --Elise > > I knew this sounds hard, but; > > Offer those who don't talk BGP4, to be disconnected by 15-MAY or so if > they don't change. > > -peter - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 09:59:28 1994 Received: from watson.ibm.com (watson.ibm.com [129.34.139.4]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id JAA02717; Fri, 15 Apr 1994 09:59:28 -0400 From: yakov@watson.ibm.com Message-Id: <199404151359.JAA02717@merit.edu> Received: from YKTVMV by watson.ibm.com (IBM VM SMTP V2R3) with BSMTP id 9753; Fri, 15 Apr 94 09:59:27 EDT Date: Fri, 15 Apr 94 09:57:42 EDT To: epg@merit.edu cc: bgpd@merit.edu, eowg@fnc.gov, regional-techs@merit.edu Subject: 20402 routing entries Ref: Your note of Thu, 14 Apr 94 19:39:42 EDT Elise, >Yes, we have again started trying to get folks to move to BGP4 -- heck >we are still trying to get some folks to move to BGP. Trying to get folks to move to BGP4 is a good thing to do and it should be encouraged, but given the time constraints this is unlikely to be a feasible solution to the problem in the near future. >The results are slow in coming... It seems that some folks PERSISENTLY missed the point. The clock is ticking. The only way to slow down the clock is by reducing the volume of routing information (via CIDR). Nothing else is going to stop or slow down the clock. The clock cares less whether "the results are slow in coming" or why they are "slow in coming". And, by the way, when the clock handle hits the mark there is going to be a massive crash. Forgive me my bluntness, but given where we are today I just don't see any feasible alternatives to a medium-large scale proxy aggregation within a next month or so. So, given the finite amount of human resources we have, let me suggest that the CIDR efforts should be strongly focused on the following two FEASIBLE choices: (a) make sites who have BGP-4 TODAY to withdraw individual components asap (b) make sites who don't have BGP-4 TODAY to arrange proxy aggregation by their providers (who assumed to have BGP-4) asap (or the providers will arrange it for them). Yakov. - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 10:21:42 1994 Received: from loki.oar.net (loki.oar.net [131.187.1.133]) by merit.edu (8.6.8.1/merit-1.0) with ESMTP id KAA05575; Fri, 15 Apr 1994 10:21:41 -0400 From: henryc@oar.net Received: for henryc@oar.net by loki.oar.net (PIPE/8.6.8.1/940327) id KAA07327; Fri, 15 Apr 1994 10:21:39 -0400 Date: Fri, 15 Apr 1994 10:21:39 -0400 Message-Id: <199404151421.KAA07327@loki.oar.net> To: yakov@watson.ibm.com Subject: Re: 20402 routing entries Cc: bgpd@merit.edu, regional-techs@merit.edu >It seems that some folks PERSISENTLY missed the point. The clock is >ticking. The only way to slow down the clock is by reducing the volume >of routing information (via CIDR). Nothing else is going to stop or >slow down the clock. The clock cares less whether "the results are slow >in coming" or why they are "slow in coming". And, by the way, when the >clock handle hits the mark there is going to be a massive crash. But even in the best of circumstances, all CIDR does is slow the RPM of the clock from 10 to 2, and over time it goes to 10 again. Hey Tony, what about that 1024MB cpu :-)? henry - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 10:34:07 1994 Received: from watson.ibm.com (watson.ibm.com [129.34.139.4]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id KAA06845; Fri, 15 Apr 1994 10:34:06 -0400 From: yakov@watson.ibm.com Message-Id: <199404151434.KAA06845@merit.edu> Received: from YKTVMV by watson.ibm.com (IBM VM SMTP V2R3) with BSMTP id 0431; Fri, 15 Apr 94 10:34:06 EDT Date: Fri, 15 Apr 94 10:32:00 EDT To: henryc@oar.net cc: bgpd@merit.edu, regional-techs@merit.edu Subject: 20402 routing entries Ref: Your note of Fri, 15 Apr 1994 10:21:39 -0400 Henry, >But even in the best of circumstances, all CIDR does is slow the >RPM of the clock from 10 to 2, an over time it goes to 10 again. In the best of circumstances CIDR reduces the growth of routing information to roughly log(#sites). So, yes, in theory over time it could go "to 10 again", but that would require the number of sites that may be well beyond IPv4 (or even any IPng) addressing capabilities. It may also be well beyond any practical requirements for a max size of an internet. Yakov. - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 11:31:05 1994 Received: from pepper.merit.edu (pepper.merit.edu [35.42.1.50]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id LAA12087; Fri, 15 Apr 1994 11:31:05 -0400 Received: by pepper.merit.edu (4.1/client-0.9) id AA06843; Fri, 15 Apr 94 11:31:04 EDT From: epg@merit.edu Message-Id: <9404151531.AA06843@pepper.merit.edu> Subject: Re: 20402 routing entries To: yakov@watson.ibm.com Date: Fri, 15 Apr 94 11:31:04 EDT Cc: epg@merit.edu, bgpd@merit.edu, eowg@fnc.gov, regional-techs@merit.edu In-Reply-To: <199404151359.JAA02717@merit.edu>; from "yakov@watson.ibm.com" at Apr 15, 94 9:57 am X-Mailer: ELM [version 2.3 PL11] Yakov, > > Ref: Your note of Thu, 14 Apr 94 19:39:42 EDT > > > Elise, > > >Yes, we have again started trying to get folks to move to BGP4 -- heck > >we are still trying to get some folks to move to BGP. > > Trying to get folks to move to BGP4 is a good thing to do and it > should be encouraged, but given the time constraints this is unlikely > to be a feasible solution to the problem in the near future. > > >The results are slow in coming... > > It seems that some folks PERSISENTLY missed the point. The clock is > ticking. The only way to slow down the clock is by reducing the volume > of routing information (via CIDR). Nothing else is going to stop or > slow down the clock. The clock cares less whether "the results are slow > in coming" or why they are "slow in coming". And, by the way, when the > clock handle hits the mark there is going to be a massive crash. > > Forgive me my bluntness, but given where we are today I just don't see > any feasible alternatives to a medium-large scale proxy aggregation > within a next month or so. > > So, given the finite amount of human resources we have, let me suggest > that the CIDR efforts should be strongly focused on the following two > FEASIBLE choices: > > (a) make sites who have BGP-4 TODAY to withdraw individual components asap > > (b) make sites who don't have BGP-4 TODAY to arrange proxy aggregation > by their providers (who assumed to have BGP-4) asap (or > the providers will arrange it for them). > > Yakov. > If you refer to the list of the top ten ASs, you can see that large gains can be attained without being heavy handed. If the top 10, several of which are BGP4 capable, cidrize the savings would be substantial. --Elise - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 10:52:16 1994 Received: from loki.oar.net (loki.oar.net [131.187.1.133]) by merit.edu (8.6.8.1/merit-1.0) with ESMTP id KAA08455; Fri, 15 Apr 1994 10:52:15 -0400 From: henryc@oar.net Received: for henryc@oar.net by loki.oar.net (PIPE/8.6.8.1/940327) id KAA16444; Fri, 15 Apr 1994 10:52:00 -0400 Date: Fri, 15 Apr 1994 10:52:00 -0400 Message-Id: <199404151452.KAA16444@loki.oar.net> To: yakov@watson.ibm.com Subject: Re: 20402 routing entries Cc: bgpd@merit.edu, regional-techs@merit.edu >In the best of circumstances CIDR reduces the growth of routing >information to roughly log(#sites). So, yes, in theory over time >it could go "to 10 again", but that would require the number of >sites that may be well beyond IPv4 (or even any IPng) addressing >capabilities. Your first 5 words say alot. This assumes alot, including customers that don't switch providers and inject more specific routes (this is happening already). You're also assuming that we have a mechanism for aggregating routes for folks who choose not to (or can't, for some reason). CIDR only buys us a *little* time. Pigs still can't fly :-). henry - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 11:05:18 1994 Received: from watson.ibm.com (watson.ibm.com [129.34.139.4]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id LAA09532; Fri, 15 Apr 1994 11:05:17 -0400 From: yakov@watson.ibm.com Message-Id: <199404151505.LAA09532@merit.edu> Received: from YKTVMV by watson.ibm.com (IBM VM SMTP V2R3) with BSMTP id 1045; Fri, 15 Apr 94 11:05:18 EDT Date: Fri, 15 Apr 94 11:03:38 EDT To: henryc@oar.net cc: bgpd@merit.edu, regional-techs@merit.edu Subject: 20402 routing entries Ref: Your note of Fri, 15 Apr 1994 10:52:00 -0400 Henry, >This assumes alot, including customers that don't switch providers >and inject more specific routes (this is happening already). No, I assumed that most (but NOT all) of the customers who switch providers would renumber. I can further weaken this assumption by allowing aggregation above the immediate provider level (you can do this with CIDR). >You're also assuming that we have a mechanism for aggregating >routes for folks who choose not to (or can't, for some reason). That is not so far-fetched assumption. Proxy aggregation is likely to happen, whether some folks like it or not. >CIDR only buys us a *little* time.. Remember there is "CIDR movie", but there is also "CIDR book". You need to consider both... Yakov. - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 12:08:40 1994 Received: from mon.cise.nsf.gov (mon.cise.nsf.gov [128.150.55.14]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id MAA14993; Fri, 15 Apr 1994 12:08:39 -0400 Received: by mon.cise.nsf.gov (920330.SGI/920502.SGI) for bgpd@merit.edu id AA12629; Fri, 15 Apr 94 12:09:46 -0500 Date: Fri, 15 Apr 1994 12:09:45 -0500 (EDT) From: Stephen Wolff To: bgpd@merit.edu, regional-techs@merit.edu Cc: pwg@nsipo.arc.nasa.gov, fepg@nsipo.arc.nasa.gov Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII If NSF were to waive the NSFNET Backbone Service AUP **for the sole purpose of assisting providers in effective CIDRization/aggregation to avoid Internet collapse**, would that be of any help? I have alerted the NSF Counsel to this possibility, and they are of course concerned that everyone will cancel their current commercial contracts, switch their traffic to NSFNET, and hurl all the private providers into bankruptcy. I should welcome your comments; if you support the idea (the waiver, not hurtling into ruin), I may also enlist your help convincing Counsel and the IG. -s - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 12:28:48 1994 Received: from cider.cisco.com (cider.cisco.com [131.108.13.133]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id MAA16919; Fri, 15 Apr 1994 12:28:47 -0400 Received: from localhost.cisco.com by cider.cisco.com with SMTP id AA19324 (5.67a/IDA-1.5); Fri, 15 Apr 1994 09:28:15 -0700 Message-Id: <199404151628.AA19324@cider.cisco.com> To: epg@merit.edu Cc: roll@stupi.se (Peter Lothberg), eowg@fnc.gov, regional-techs@merit.edu, bgpd@merit.edu Subject: Re: 20402 routing entries In-Reply-To: Your message of "Fri, 15 Apr 1994 09:09:43 EDT." <9404151309.AA06771@pepper.merit.edu> Date: Fri, 15 Apr 1994 09:28:15 -0700 From: Paul Traina From: epg@merit.edu Subject: Re: 20402 routing entries > > I knew this sounds hard, but; > > Offer those who don't talk BGP4, to be disconnected by 15-MAY or so if > they don't change. > > -peter > Not hard, just unrealistic. --Elise Not even necessary, their NSPs can proxy for them (and should force proxy down their throat). Yes, it's impolite, but causing the internet to thrash is impolite. - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 11:52:55 1994 Received: from upeksa.sdsc.edu (upeksa.sdsc.edu [132.249.22.107]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id LAA13801; Fri, 15 Apr 1994 11:52:54 -0400 Received: by upeksa.sdsc.edu (AIX 3.2/UCB 5.64/4.03) id AA18283; Fri, 15 Apr 1994 08:52:48 -0700 From: hwb@upeksa.sdsc.edu (Hans-Werner Braun) Message-Id: <9404151552.AA18283@upeksa.sdsc.edu> Subject: Re: 20402 routing entries To: epg@merit.edu Date: Fri, 15 Apr 94 8:52:48 PDT Cc: yakov@watson.ibm.com, bgpd@merit.edu, eowg@fnc.gov, regional-techs@merit.edu In-Reply-To: <9404151531.AA06843@pepper.merit.edu>; from "epg@merit.edu" at Apr 15, 94 11:31 am Elise: >If you refer to the list of the top ten ASs, you can see that large >gains can be attained without being heavy handed. If the top 10, >several of which are BGP4 capable, cidrize the savings would be >substantial. Probably true. While Peter L.'s comment is of course stretching it way too much in terms of "where's a whip there is a way," I believe that in the interest of the survival of the network, having to hurt people's feelings may be the lesser evil. As such, there should be a rather strong encouragement towards making progress here. Also, I believe it would be good for someone to take a very strong lead on renumbering ("I want my net 35 back; I fought so hard with Jon for it! It's MINE!"). Are you and/or Jon as the RAs taking the lead there? What is your implementation plan? If you don't have one, what are your current projections of when and how things will become critical? What is your model to define criticality? Hans-Werner - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 12:13:27 1994 Received: from localhost (jyy@localhost) by merit.edu (8.6.8.1/merit-1.0) with SMTP id MAA15561; Fri, 15 Apr 1994 12:13:27 -0400 Message-Id: <199404151613.MAA15561@merit.edu> To: yakov@watson.ibm.com cc: epg@merit.edu, bgpd@merit.edu, eowg@fnc.gov, regional-techs@merit.edu, jyy@merit.edu Subject: Re: 20402 routing entries In-reply-to: Your message of "Fri, 15 Apr 1994 09:57:42 EDT." <199404151359.JAA02717@merit.edu> Date: Fri, 15 Apr 1994 12:13:26 -0400 From: Jessica Yu According to NSF/ANSNET data, 23 aggregates ALONG with its covered 898 specific routes are co-exist in the routing table now. If the ASs withdraws all these more specific routes, the routing table could be reduced by 898. Given the urgent need of reduce the routing table size, would these ASs withdraw those specific routes as soon as possible? --Jessica - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 13:03:29 1994 Received: from psi.com (psi.com [192.67.6.2]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id NAA20708; Fri, 15 Apr 1994 13:03:27 -0400 Received: from us.psi.com by psi.com (4.1/2.1-PSI/PSINet) id AA15217; Fri, 15 Apr 94 13:02:55 EDT Received: by us.psi.com (4.1/SMI-4.1.3-PSI-pop) id AA04458; Fri, 15 Apr 94 13:03:02 EDT Message-Id: <9404151703.AA04458@us.psi.com> To: henryc@oar.net Cc: yakov@watson.ibm.com, bgpd@merit.edu, regional-techs@merit.edu Subject: Re: 20402 routing entries In-Reply-To: Your message of "Fri, 15 Apr 1994 10:52:00 EDT." <199404151452.KAA16444@loki.oar.net> Date: Fri, 15 Apr 1994 13:03:01 -0400 From: "Martin Lee Schoffstall" I agree with Henry. Marty ----- > >In the best of circumstances CIDR reduces the growth of routing > >information to roughly log(#sites). So, yes, in theory over time > >it could go "to 10 again", but that would require the number of > >sites that may be well beyond IPv4 (or even any IPng) addressing > >capabilities. > > Your first 5 words say alot. This assumes alot, including customers > that don't switch providers and inject more specific routes (this is > happening already). You're also assuming that we have a mechanism > for aggregating routes for folks who choose not to (or can't, for > some reason). > > CIDR only buys us a *little* time. Pigs still can't fly :-). > > henry - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 13:08:08 1994 Received: from psi.com (psi.com [192.67.6.2]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id NAA20919; Fri, 15 Apr 1994 13:08:06 -0400 Received: from us.psi.com by psi.com (4.1/2.1-PSI/PSINet) id AA15323; Fri, 15 Apr 94 13:07:34 EDT Received: by us.psi.com (4.1/SMI-4.1.3-PSI-pop) id AA04531; Fri, 15 Apr 94 13:07:41 EDT Message-Id: <9404151707.AA04531@us.psi.com> To: yakov@watson.ibm.com Cc: henryc@oar.net, bgpd@merit.edu, regional-techs@merit.edu Subject: Re: 20402 routing entries In-Reply-To: Your message of "Fri, 15 Apr 1994 11:03:38 EDT." <199404151505.LAA09532@merit.edu> Date: Fri, 15 Apr 1994 13:07:40 -0400 From: "Martin Lee Schoffstall" a bit less than 28,000 currently configured "Internet" network numbers believe they have permanently gained their class B's and C's and will NEVER give them up and renumber. Or at least the ones in the US believe that. a bit less than all assigned network numbers total believe that they have gained their class B's and C's and will never give up and renumber. You have provided no incentive (carrot) for individual companies to do the right thing. CIDR is a perfectly engineered suspension bridge unconnected to either bank of the river. Marty > Ref: Your note of Fri, 15 Apr 1994 10:52:00 -0400 > > > Henry, > > >This assumes alot, including customers that don't switch providers > >and inject more specific routes (this is happening already). > > No, I assumed that most (but NOT all) of the customers who switch > providers would renumber. I can further weaken this assumption > by allowing aggregation above the immediate provider level > (you can do this with CIDR). > > >You're also assuming that we have a mechanism for aggregating > >routes for folks who choose not to (or can't, for some reason). > > That is not so far-fetched assumption. Proxy aggregation is > likely to happen, whether some folks like it or not. > > >CIDR only buys us a *little* time.. > > Remember there is "CIDR movie", but there is also "CIDR book". > You need to consider both... > > Yakov. - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 12:38:50 1994 Received: from Valinor.Stanford.EDU (Valinor.Stanford.EDU [131.119.246.200]) by merit.edu (8.6.8.1/merit-1.0) with ESMTP id MAA18083; Fri, 15 Apr 1994 12:38:49 -0400 Received: (from vaf@localhost) by Valinor.Stanford.EDU (8.6.7/8.6.6) id JAA29947; Fri, 15 Apr 1994 09:40:02 -0700 Date: Fri, 15 Apr 94 9:40:01 PDT From: Vince Fuller To: "Martin Lee Schoffstall" Cc: Peter Lothberg , epg@merit.edu, bgpd@merit.edu, eowg@fnc.gov, regional-techs@merit.edu Office: Spruce Hall F15, (415) 723-6860 USMail: Pine Hall 115, Stanford, CA, 94305-4122 Subject: Re: 20402 routing entries In-Reply-To: Your message of Fri, 15 Apr 1994 10:09:04 -0400 Message-ID: it would have been a reasonable approach had cisco and/or other vendors had a standard release support BGP4 without bugs 12 months ago and had you given 12 months notice C'mon Marty, wake up and smell the kimchi. The writing has been on the wall since RFC 1338 (Supernetting) was published almost two years ago, since shortly after that is when the CIDR addressing plan first started being implemented. cisco and the other router vendors have gone out of their way to support the CIDR effort, having integrated CIDR support into the earliest possible release of their code. CIDR, default, or die - it may not be the law, but it is reality. --Vince - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 13:34:45 1994 Received: from relay2.UU.NET (relay2.UU.NET [192.48.96.7]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id NAA23468; Fri, 15 Apr 1994 13:34:42 -0400 Received: from chsun.eunet.ch by relay2.UU.NET with SMTP (5.61/UUNET-internet-primary) id AAwltm03965; Fri, 15 Apr 94 13:34:39 -0400 Received: from localhost by chsun.eunet.ch (8.6.4/1.34) id TAA07027; Fri, 15 Apr 1994 19:37:57 +0200 From: poole@eunet.ch (Simon Poole) Message-Id: <199404151737.TAA07027@chsun.eunet.ch> Subject: Re: your mail To: steve@nsf.gov (Stephen Wolff) Date: Fri, 15 Apr 1994 19:37:54 +0200 (MET DST) Cc: bgpd@merit.edu, regional-techs@merit.edu, pwg@nsipo.arc.nasa.gov, fepg@nsipo.arc.nasa.gov In-Reply-To: from "Stephen Wolff" at Apr 15, 94 12:09:45 pm X-Mailer: ELM [version 2.4 PL23alpha] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1244 > > If NSF were to waive the NSFNET Backbone Service AUP **for the sole > purpose of assisting providers in effective CIDRization/aggregation to > avoid Internet collapse**, would that be of any help? > > I have alerted the NSF Counsel to this possibility, and they are of > course concerned that everyone will cancel their current commercial > contracts, switch their traffic to NSFNET, and hurl all the private > providers into bankruptcy. > > I should welcome your comments; if you support the idea (the waiver, not > hurtling into ruin), I may also enlist your help convincing Counsel and > the IG. I see no reason to waiver the AUP. Essentially adherence to the AUP has been based on an honor system up to now, and I don't see any reason why this should change. What would make sense is to: - have all interested service providers sign a (formal?) agreement that they will inform their customers of the restrictions on usage of the NSFnet backbone service (possibly adding an explicit pointer to the AUP in their contracts). - do away with the PRDB / NACR's. I really don't see how this would significantly change the current situation (expect that we would all have less work). Simon Poole - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 12:40:13 1994 Received: from upeksa.sdsc.edu (upeksa.sdsc.edu [132.249.22.107]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id MAA18248; Fri, 15 Apr 1994 12:40:12 -0400 Received: by upeksa.sdsc.edu (AIX 3.2/UCB 5.64/4.03) id AA10902; Fri, 15 Apr 1994 09:40:03 -0700 From: hwb@upeksa.sdsc.edu (Hans-Werner Braun) Message-Id: <9404151640.AA10902@upeksa.sdsc.edu> Subject: Re: your mail To: steve@nsf.gov (Stephen Wolff) Date: Fri, 15 Apr 94 9:40:03 PDT Cc: bgpd@merit.edu, regional-techs@merit.edu, pwg@nsipo.arc.nasa.gov, fepg@nsipo.arc.nasa.gov In-Reply-To: ; from "Stephen Wolff" at Apr 15, 94 12:09 pm Steve: Sounds like a fine idea to me. Aren't we also just talking about a few remaining months of the NSFNET Backbone, after which the issue would become irrelevant anyway? So doing what you are saying seems to also help with the transition? Hans-Werner >If NSF were to waive the NSFNET Backbone Service AUP **for the sole >purpose of assisting providers in effective CIDRization/aggregation to >avoid Internet collapse**, would that be of any help? > >I have alerted the NSF Counsel to this possibility, and they are of >course concerned that everyone will cancel their current commercial >contracts, switch their traffic to NSFNET, and hurl all the private >providers into bankruptcy. > >I should welcome your comments; if you support the idea (the waiver, not >hurtling into ruin), I may also enlist your help convincing Counsel and >the IG. > >-s - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 13:35:18 1994 Received: from psi.com (psi.com [192.67.6.2]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id NAA23518; Fri, 15 Apr 1994 13:35:15 -0400 Received: from us.psi.com by psi.com (4.1/2.1-PSI/PSINet) id AA16126; Fri, 15 Apr 94 13:33:52 EDT Received: by us.psi.com (4.1/SMI-4.1.3-PSI-pop) id AA04708; Fri, 15 Apr 94 13:12:30 EDT Message-Id: <9404151712.AA04708@us.psi.com> To: Stephen Wolff Cc: bgpd@merit.edu, regional-techs@merit.edu, pwg@nsipo.arc.nasa.gov, fepg@nsipo.arc.nasa.gov, wls@us.psi.com In-Reply-To: Your message of "Fri, 15 Apr 1994 12:09:45 CDT." Date: Fri, 15 Apr 1994 13:11:59 -0400 From: "Martin Lee Schoffstall" continuing my bridge analogy you are now providing glider service from the river bank to the bridge not very useful for that Teamster driven truck m > If NSF were to waive the NSFNET Backbone Service AUP **for the sole > purpose of assisting providers in effective CIDRization/aggregation to > avoid Internet collapse**, would that be of any help? > > I have alerted the NSF Counsel to this possibility, and they are of > course concerned that everyone will cancel their current commercial > contracts, switch their traffic to NSFNET, and hurl all the private > providers into bankruptcy. > > I should welcome your comments; if you support the idea (the waiver, not > hurtling into ruin), I may also enlist your help convincing Counsel and > the IG. > > -s > - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 13:44:46 1994 Received: from mon.cise.nsf.gov (mon.cise.nsf.gov [128.150.55.14]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id NAA24317; Fri, 15 Apr 1994 13:44:44 -0400 Received: by mon.cise.nsf.gov (920330.SGI/920502.SGI) for bgpd@merit.edu id AA13204; Fri, 15 Apr 94 13:45:49 -0500 Date: Fri, 15 Apr 1994 13:45:48 -0500 (EDT) From: Stephen Wolff Subject: Re: your mail To: Matt Mathis Cc: bgpd@merit.edu, regional-techs@merit.edu In-Reply-To: <9404151715.AA15935@pele.psc.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > ... A further > refinement: allow the case where commercial traffic traverses the NSFnet > becasue routing technology is not sufficient to support an existing entirely > commercial path between subscribers, as long as there are contracts and > sufficient facilitys in place to support the path. Matt - Good point. In fact I had to make a qualification like that just to get Counsel off the ceiling and start talking to me. Tnx, -s - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 13:15:47 1994 Received: from pele.psc.edu (pele.psc.edu [128.182.61.222]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id NAA21562; Fri, 15 Apr 1994 13:15:47 -0400 Received: from localhost by pele.psc.edu (5.65/Ultrix3.0-C 11/12/92 nydick) id AA15935; Fri, 15 Apr 1994 13:15:44 -0400 Message-Id: <9404151715.AA15935@pele.psc.edu> To: Stephen Wolff Cc: bgpd@merit.edu, regional-techs@merit.edu In-Reply-To: Your message of "Fri, 15 Apr 94 12:09:45 CDT." Date: Fri, 15 Apr 94 13:15:43 -0400 From: "Matt Mathis" X-Mts: smtp A safer position, which would be easier for many people to swallow, would be to retain the AUP as a legal entropy, but lift the requirement to use routing to enforce it. (Oops I mean entity. Talk about Freud!). A further refinement: allow the case where commercial traffic traverses the NSFnet becasue routing technology is not sufficient to support an existing entirely commercial path between subscribers, as long as there are contracts and sufficient facilitys in place to support the path. --MM-- - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 13:57:43 1994 Received: from mon.cise.nsf.gov (mon.cise.nsf.gov [128.150.55.14]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id NAA25378; Fri, 15 Apr 1994 13:57:42 -0400 Received: by mon.cise.nsf.gov (920330.SGI/920502.SGI) for bgpd@merit.edu id AA13254; Fri, 15 Apr 94 13:57:24 -0500 Date: Fri, 15 Apr 1994 13:57:24 -0500 (EDT) From: Stephen Wolff Subject: Re: your mail To: Martin Lee Schoffstall Cc: bgpd@merit.edu, regional-techs@merit.edu, pwg@nsipo.arc.nasa.gov, fepg@nsipo.arc.nasa.gov, wls@us.psi.com In-Reply-To: <9404151712.AA04708@us.psi.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > continuing my bridge analogy > > you are now providing glider service from the river bank to the bridge > > not very useful for that Teamster driven truck > > m Marty - Sorry, but that's now TWO bridge analogies I don't understand. Could you please be a little more explicit? Tnx, -s - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 13:27:40 1994 Received: from psi.com (psi.com [192.67.6.2]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id NAA22656; Fri, 15 Apr 1994 13:27:35 -0400 Received: from us.psi.com by psi.com (4.1/2.1-PSI/PSINet) id AA15808; Fri, 15 Apr 94 13:24:21 EDT Received: by us.psi.com (4.1/SMI-4.1.3-PSI-pop) id AA05259; Fri, 15 Apr 94 13:24:29 EDT Message-Id: <9404151724.AA05259@us.psi.com> To: Vince Fuller Cc: Peter Lothberg , epg@merit.edu, bgpd@merit.edu, eowg@fnc.gov, regional-techs@merit.edu Subject: Re: 20402 routing entries In-Reply-To: Your message of "Fri, 15 Apr 1994 09:40:01 PDT." Date: Fri, 15 Apr 1994 13:24:29 -0400 From: "Martin Lee Schoffstall" again, this has nothing to do with cisco this has to do with cutting people off the Internet - other people. don't worry about PSI meeting "the Swedish deadline" - no problemo Marty > it would have been a reasonable approach > > had cisco and/or other vendors had a standard release support BGP4 withou t > bugs 12 months ago > > and had you given 12 months notice > > C'mon Marty, wake up and smell the kimchi. > > The writing has been on the wall since RFC 1338 (Supernetting) was published > almost two years ago, since shortly after that is when the CIDR addressing > plan first started being implemented. > > cisco and the other router vendors have gone out of their way to support the > CIDR effort, having integrated CIDR support into the earliest possible releas e > of their code. > > CIDR, default, or die - it may not be the law, but it is reality. > > --Vince - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 13:43:47 1994 Received: from hsdndev.harvard.edu (hsdndev.harvard.edu [128.103.202.40]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id NAA24260; Fri, 15 Apr 1994 13:43:45 -0400 Date: Fri, 15 Apr 94 13:43:35 -0400 From: sob@hsdndev.harvard.edu (Scott Bradner) Message-Id: <9404151743.AA19252@hsdndev.harvard.edu> To: schoff@us.psi.com, yakov@watson.ibm.com Subject: Re: 20402 routing entries Cc: bgpd@merit.edu, henryc@oar.net, regional-techs@merit.edu Marty, You don't seem to like the state all that much. What is your suggestion to get the bridge long enough? (or the river narrow enough) Scott - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 13:38:24 1994 Received: from mystic.cerf.net (mystic.cerf.net [192.153.156.11]) by merit.edu (8.6.8.1/merit-1.0) with ESMTP id NAA23708; Fri, 15 Apr 1994 13:38:23 -0400 Received: from localhost (pushp@localhost) by mystic.cerf.net (8.6.4/8.6.4) id KAA21381; Fri, 15 Apr 1994 10:38:07 -0700 From: Pushpendra Mohta Message-Id: <199404151738.KAA21381@mystic.cerf.net> Subject: Waiving the AUP for CIDRization To: steve@nsf.gov (Stephen Wolff) Date: Fri, 15 Apr 1994 10:38:06 -0700 (PDT) Cc: bgpd@merit.edu, regional-techs@merit.edu, pwg@nsipo.arc.nasa.gov, fepg@nsipo.arc.nasa.gov In-Reply-To: from "Stephen Wolff" at Apr 15, 94 12:09:45 pm X-USMAIL: CERFnet, P.O. BOX 85608, San Diego, CA 92186-9784 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1082 I cant speak for everyone else, but I welcome the waiving of the AUP for this purpose. And no, I wont yank my CIX connection till the dust settles on the new architecture. This will however open up a whole bunch of routing asymetry and related trouble shooting problems. --pushpendra Pushpendra Mohta pushp@cerf.net +1 619 455 3908 Director of Engineering pushp@sdsc.bitnet +1 800 876 2373 CERFNet Stephen Wolff writes: > > If NSF were to waive the NSFNET Backbone Service AUP **for the sole > purpose of assisting providers in effective CIDRization/aggregation to > avoid Internet collapse**, would that be of any help? > > I have alerted the NSF Counsel to this possibility, and they are of > course concerned that everyone will cancel their current commercial > contracts, switch their traffic to NSFNET, and hurl all the private > providers into bankruptcy. > > I should welcome your comments; if you support the idea (the waiver, not > hurtling into ruin), I may also enlist your help convincing Counsel and > the IG. > > -s > > - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 13:56:17 1994 Received: from netcom13.netcom.com (netcom13.netcom.com [192.100.81.125]) by merit.edu (8.6.8.1/merit-1.0) with ESMTP id NAA25313; Fri, 15 Apr 1994 13:56:16 -0400 Received: from localhost by netcom13.netcom.com (8.6.4/SMI-4.1/Netcom) id KAA26990; Fri, 15 Apr 1994 10:57:25 -0700 Message-Id: <199404151757.KAA26990@netcom13.netcom.com> From: hoodr@netcom.com (Robert Hood) Date: Fri, 15 Apr 1994 10:57:25 PDT In-Reply-To: Jessica Yu "Re: 20402 routing entries" (Apr 15, 12:13pm) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Jessica Yu Subject: Re: 20402 routing entries Cc: epg@merit.edu, bgpd@merit.edu, regional-techs@merit.edu >According to NSF/ANSNET data, 23 aggregates ALONG with its covered 898 specific >routes are co-exist in the routing table now. If the ASs withdraws all these more >specific routes, the routing table could be reduced by 898. Given the urgent >need of reduce the routing table size, would these ASs withdraw those specific >routes as soon as possible? I tried. They told me that the forms and policy for removing more specific routes were not in place yet, and that there would be an announcement about it in a week or so. (I tried to remove 150 routes). I've got a few hundred more to do next week. -- Robert Hood hoodr@netcom.com 1-408-983-1510 System/Network Administrator for NETCOM On-line Communications Services, Inc. - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 14:07:03 1994 Received: from goshawk.lanl.gov (goshawk.lanl.gov [128.165.96.145]) by merit.edu (8.6.8.1/merit-1.0) with ESMTP id OAA26485; Fri, 15 Apr 1994 14:07:02 -0400 Received: from localhost.lanl.gov (localhost.lanl.gov [127.0.0.1]) by goshawk.lanl.gov (8.6.7/8.6.4) with SMTP id MAA22720; Fri, 15 Apr 1994 12:05:14 -0600 From: "Peter S. Ford" Message-Id: <199404151805.MAA22720@goshawk.lanl.gov> X-Authentication-Warning: goshawk.lanl.gov: Host localhost.lanl.gov didn't use HELO protocol To: poole@eunet.ch (Simon Poole) cc: steve@nsf.gov (Stephen Wolff), bgpd@merit.edu, regional-techs@merit.edu, pwg@nsipo.arc.nasa.gov, fepg@nsipo.arc.nasa.gov Subject: Re: your mail In-reply-to: Your message of Fri, 15 Apr 94 19:37:54 +0200. <199404151737.TAA07027@chsun.eunet.ch> Date: Fri, 15 Apr 94 12:05:13 MST >>> - do away with the PRDB / NACR's. I would not want to see these go away, rather they should and need to be reshaped. NSFNET policy was hardly the sole reason for setting NACRs up in the first place. An important goal was to establish sound routing in the NSFNET and for the networks attached to the NSFNET. By recasting the process to reflect the global and multi-provider nature of the Internet into "routing registries" the sound routing goal can be met in a distributed manner. My understanding is that this is already in progress due to the efforts of Merit, RIPE and the APNIC. peter - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 14:36:24 1994 Received: from watson.ibm.com (watson.ibm.com [129.34.139.4]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id OAA29110; Fri, 15 Apr 1994 14:36:23 -0400 From: yakov@watson.ibm.com Message-Id: <199404151836.OAA29110@merit.edu> Received: from YKTVMV by watson.ibm.com (IBM VM SMTP V2R3) with BSMTP id 5017; Fri, 15 Apr 94 14:36:23 EDT Date: Fri, 15 Apr 94 14:34:02 EDT To: Havard.Eidnes@runit.sintef.no cc: bgpd@merit.edu, regional-techs@merit.edu Subject: CIDR testing Ref: Your note of Fri, 15 Apr 1994 20:26:47 +0200 Havard, >What this means is that I think it's fairly safe to say that there >will be no connectivity problems when you pull the specific routes. I guess we can declare the as of April 15, 1994 the Internet "guts" have been adequately CIDRized :-) Yakov. - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 14:58:36 1994 Received: from localhost (jyy@localhost) by merit.edu (8.6.8.1/merit-1.0) with SMTP id OAA01409; Fri, 15 Apr 1994 14:58:35 -0400 Message-Id: <199404151858.OAA01409@merit.edu> To: hoodr@netcom.com (Robert Hood) cc: Jessica Yu , epg@merit.edu, bgpd@merit.edu, regional-techs@merit.edu Subject: Re: 20402 routing entries In-reply-to: Your message of "Fri, 15 Apr 1994 10:57:25 PDT." <199404151757.KAA26990@netcom13.netcom.com> Date: Fri, 15 Apr 1994 14:58:34 -0400 From: Jessica Yu >>According to NSF/ANSNET data, 23 aggregates ALONG with its covered 898 specific >>routes are co-exist in the routing table now. If the ASs withdraws all these more >>specific routes, the routing table could be reduced by 898. Given the urgent >>need of reduce the routing table size, would these ASs withdraw those specific >>routes as soon as possible? >I tried. They told me that the forms and policy for removing more >specific routes were not in place yet, and that there would be an announcement >about it in a week or so. (I tried to remove 150 routes). I've got >a few hundred more to do next week. Bob, You just need to stop advertising those more specific routes if you have already advertised the aggregate that covers them. It will do the job of reducing the routing table. --jessica - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 15:19:35 1994 Received: from goshawk.lanl.gov (goshawk.lanl.gov [128.165.96.145]) by merit.edu (8.6.8.1/merit-1.0) with ESMTP id PAA03641; Fri, 15 Apr 1994 15:19:33 -0400 Received: from localhost.lanl.gov (localhost.lanl.gov [127.0.0.1]) by goshawk.lanl.gov (8.6.7/8.6.4) with SMTP id NAA24007; Fri, 15 Apr 1994 13:18:11 -0600 From: "Peter S. Ford" Message-Id: <199404151918.NAA24007@goshawk.lanl.gov> X-Authentication-Warning: goshawk.lanl.gov: Host localhost.lanl.gov didn't use HELO protocol To: "Martin Lee Schoffstall" cc: yakov@watson.ibm.com, bgpd@merit.edu, regional-techs@merit.edu Subject: Re: 20402 routing entries In-reply-to: Your message of Fri, 15 Apr 94 13:07:40 -0400. <9404151707.AA04531@us.psi.com> Date: Fri, 15 Apr 94 13:18:10 MST Marty, >a bit less than 28,000 currently configured "Internet" network >numbres believe they have permanently gained their class B's and >C's. Or at least the ones in the US believe that. > >a bit less than all assigned network numbers total believe that >they have gained their class B's and C's and will never give up >and renumber > >You have provided no incentive (carrot) for individual companies >to do the right thing. Let us try to answer your question with another question: Do you want a routable large scale global Internet ? It is hard to imagine supporting a truly huge Internet without relying on hierarchical routing (CIDR is simply a realization of hierarchical routing). And if you do plan to rely on hierarchical routing, then you need to understand how to deal with the issue of containing address entropy (due to switching among providers) without renumbering. It seems naive and perhaps irresponsible to think about flat routing (based on network numbers). It should be a goal to make this renumbering simple. We'd like to suggest that folks with alternative proposals to CIDR should put their alternative proposals on a table and explain, among other things, how their proposals would be deployed and used and how these proposals would be better than CIDR. Hitting the right time frame turns out to count! When people got network numbers in the past they were getting addresses for the research Internet. It is important to understand that the research Internet was a great thing, but we are now working on the global public Internet and we desperately needed new routing and addressing systems. We should establish that we are in a transition from the research Internet to the global public Internet and we subsequently can not just use uncoordinated IP addresses and still have a workable system. This is not dissimilar to what happened when local phone exchanges started to get interconnected during the advent of long distance telephone services. There needs to be a globally coordinated address space to make this work. Reasoning by analogy with the phone system is a powerful argument. People change phone numbers all the time, they don't absolutely revolt because the phone system is so valuable. Some elect to get 700 numbers, but they *PAY* for this service. We suggest the following subjects be carefully considered: The old addresses of the research Internet need to be reorganized into the global public Internet addressing plan which is based on CIDR. Those addresses not currently globally routed will not be routed. These new customers of the Internet should get their addresses from their immediate providers. (This could be softened if there is a commitment by the customer to enter into the transition ASAP). This also would cover the case of provider switching under CIDR. Those addresses that are currently routed will *eventually* be migrated to CIDR allocations. This may take some time, on the order of years (2-5). We could look for the simple cases first (small/tiny sites). It is not fair to get people to renumber when they attach to the Internet when they see that people already attached are just sitting pretty. We need to be consistent in the application of standards and rules. Marty has brought up the subject of a carrot: The carrot is getting global Internet routing. The stick is not getting global Internet routing. It is a dull and boring argument, but it is the core of the debate. There is extreme value in what we are trying to build with the global public Internet, and we need to impress on the customer base that we need their help to make it possible to achieve our goals. We are not saying this is going to be easy, but it is rare that something worth having comes for free. Peter & Yakov P.S. The number of uncoordinated IP addresses is higher than 30K. - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 15:40:16 1994 Received: from mystic.cerf.net (mystic.cerf.net [192.153.156.11]) by merit.edu (8.6.8.1/merit-1.0) with ESMTP id PAA05920; Fri, 15 Apr 1994 15:40:14 -0400 Received: from localhost (pushp@localhost) by mystic.cerf.net (8.6.4/8.6.4) id MAA23450; Fri, 15 Apr 1994 12:40:10 -0700 From: Pushpendra Mohta Message-Id: <199404151940.MAA23450@mystic.cerf.net> Subject: Re: 20402 routing entries To: hoodr@netcom.com (Robert Hood) Date: Fri, 15 Apr 1994 12:40:09 -0700 (PDT) Cc: jyy@merit.edu, epg@merit.edu, bgpd@merit.edu, regional-techs@merit.edu In-Reply-To: <199404151757.KAA26990@netcom13.netcom.com> from "Robert Hood" at Apr 15, 94 10:57:25 am X-USMAIL: CERFnet, P.O. BOX 85608, San Diego, CA 92186-9784 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1030 Robert Hood writes: > > >According to NSF/ANSNET data, 23 aggregates ALONG with its covered 898 specific > >routes are co-exist in the routing table now. If the ASs withdraws all these more > >specific routes, the routing table could be reduced by 898. Given the urgent > >need of reduce the routing table size, would these ASs withdraw those specific > >routes as soon as possible? > > I tried. They told me that the forms and policy for removing more > specific routes were not in place yet, and that there would be an announcement > about it in a week or so. (I tried to remove 150 routes). I've got > a few hundred more to do next week. > > > -- > Robert Hood hoodr@netcom.com 1-408-983-1510 > System/Network Administrator for NETCOM On-line Communications Services, Inc. > Why dont you just stop announcing them ? --pushpendra Pushpendra Mohta pushp@cerf.net +1 619 455 3908 Director of Engineering pushp@sdsc.bitnet +1 800 876 2373 CERFNet - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 16:40:47 1994 Received: from psi.com (psi.com [192.67.6.2]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id QAA12024; Fri, 15 Apr 1994 16:40:40 -0400 Received: from us.psi.com by psi.com (4.1/2.1-PSI/PSINet) id AA21771; Fri, 15 Apr 94 16:39:54 EDT Received: by us.psi.com (4.1/SMI-4.1.3-PSI-pop) id AA14510; Fri, 15 Apr 94 16:39:56 EDT Message-Id: <9404152039.AA14510@us.psi.com> To: "Peter S. Ford" Cc: yakov@watson.ibm.com, bgpd@merit.edu, regional-techs@merit.edu, fedor@us.psi.com Subject: Re: 20402 routing entries In-Reply-To: Your message of "Fri, 15 Apr 1994 13:18:10 MST." <199404151918.NAA24007@goshawk.lanl.gov> Date: Fri, 15 Apr 1994 16:39:45 -0400 From: "Martin Lee Schoffstall" No. I do not want a routable large scale global Internet. I want a mixed mode Information SuperHighway which is a mixture of routing and layer-two switching. In fact I have that right now extensively internally, and increasingly externally. I believe that the the routed form will have some hierarchy, but it will NOT be exclusively hierarchial. PSI did hierarchial routing in 1992 internally and transparently to everyone. In fact at the current scale of the routed form there is no need for hierarchy architecturally. You have an IMPLEMENTATION problem in the NSFNet backbone and some other "key" places which will not accept any larger routing tables. What if you used cisco's with 64Megs of memory or 128Megs? Would we be playing "henny penny" right now if that was true? Should we really be considering a routing architecture imposition at 100,000 routes or 200,000 routes? The implications of CIDR are extensive and have not been "sold" to the world, there is no carrot and thinking that you can impose all hierarchial routing on everyone is niave. I think your metaphor of phone numbers is wrong, I think the metaphor is portable 1.800 imposed by the FCC and embraced by everyone who used it. You are going in the opposite direction and are imposing non-portable 1800 implicitly with CIDR, it will not play in Peoria. Sign up for temporary compression of the routing table and then growth beyond the current volume some number of months later. Forget renumbering, you are a party theorist and your cadre does not represent the entire soviet. You REPRESENT the research Internet taking a position on the way the global public Internet is going to growing up is absurd. You've no experience on what is happening in the real world of providing the service to end customers. There are lots of issues you have not given any creedance to even if you have given them limited consideration. But nothing in your messages leads me to believe that you have given them consideration. I'll bet we could have flat routing if less than 100 places did some upgrades, and then we could keep some of the benefits of flat routing. PSI is doing CIDR, but we are NOT signed up for some of the draconian theories you and others are espousing. so Forget - renumbering (ready to deal with Solomon's or GE's lawyers?) - not accepting individual network numbers (or Columbia's?) - continued growth (you will compress, and you will slow, you will not stop) We will have to incent (carrot) people to do the right thing, you have no plan (predictable government style), we need to come up with one, and it will then take 12 to 18 months to have material affect. Marty > > Let us try to answer your question with another question: > > Do you want a routable large scale global Internet ? > > It is hard to imagine supporting a truly huge Internet without relying > on hierarchical routing (CIDR is simply a realization of > hierarchical routing). > > And if you do plan to rely on hierarchical routing, then you need to > understand how to deal with the issue of containing address entropy > (due to switching among providers) without renumbering. It seems naive > and perhaps irresponsible to think about flat routing (based on network > numbers). It should be a goal to make this renumbering simple. > > We'd like to suggest that folks with alternative proposals to CIDR > should put their alternative proposals on a table and explain, among > other things, how their proposals would be deployed and used and how > these proposals would be better than CIDR. Hitting the right time > frame turns out to count! > > > When people got network numbers in the past they were getting addresses > for the research Internet. It is important to understand that the > research Internet was a great thing, but we are now working on the > global public Internet and we desperately needed new routing and addressing > systems. We should establish that we are in a transition from the > research Internet to the global public Internet and we subsequently > can not just use uncoordinated IP addresses and still have a workable > system. This is not dissimilar to what happened when local phone > exchanges started to get interconnected during the advent of long > distance telephone services. There needs to be a globally coordinated > address space to make this work. Reasoning by analogy with the phone system > is a powerful argument. People change phone numbers all the time, they > don't absolutely revolt because the phone system is so valuable. > Some elect to get 700 numbers, but they *PAY* for this service. > > We suggest the following subjects be carefully considered: > > The old addresses of the research Internet need to be reorganized > into the global public Internet addressing plan which is based > on CIDR. > > Those addresses not currently globally routed will not be > routed. These new customers of the Internet should get > their addresses from their immediate providers. > (This could be softened if there is a commitment by the > customer to enter into the transition ASAP). This also > would cover the case of provider switching under CIDR. > > Those addresses that are currently routed will *eventually* > be migrated to CIDR allocations. This may take some time, > on the order of years (2-5). We could look for the > simple cases first (small/tiny sites). > > It is not fair to get people to renumber when they attach to > the Internet when they see that people already attached > are just sitting pretty. We need to be consistent in the > application of standards and rules. > > Marty has brought up the subject of a carrot: > > The carrot is getting global Internet routing. > > The stick is not getting global Internet routing. > > It is a dull and boring argument, but it is the core of the debate. > There is extreme value in what we are trying to build with the global public > Internet, and we need to impress on the customer base that we need > their help to make it possible to achieve our goals. > > We are not saying this is going to be easy, but it is rare that something > worth having comes for free. > > Peter & Yakov > > P.S. The number of uncoordinated IP addresses is higher than 30K. > - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 16:14:17 1994 Received: from localhost (sjr@localhost) by merit.edu (8.6.8.1/merit-1.0) with SMTP id QAA09310; Fri, 15 Apr 1994 16:14:16 -0400 Message-Id: <199404152014.QAA09310@merit.edu> To: hoodr@netcom.com (Robert Hood) cc: Jessica Yu , epg@merit.edu, bgpd@merit.edu, regional-techs@merit.edu Subject: Re: 20402 routing entries In-reply-to: Your message of Fri, 15 Apr 1994 10:57:25 PDT. <199404151757.KAA26990@netcom13.netcom.com> Date: Fri, 15 Apr 1994 16:14:15 -0400 From: "Steven J. Richardson" Robert: > Date: Fri, 15 Apr 1994 10:57:25 PDT > From: hoodr@netcom.com (Robert Hood) > To: Jessica Yu > CC: epg@merit.edu, bgpd@merit.edu, regional-techs@merit.edu > >According to NSF/ANSNET data, 23 aggregates ALONG with its covered 898 spe cific > >routes are co-exist in the routing table now. If the ASs withdraws all th ese more > >specific routes, the routing table could be reduced by 898. Given the urg ent > >need of reduce the routing table size, would these ASs withdraw those spec ific > >routes as soon as possible? > > I tried. They told me that the forms and policy for removing more > specific routes were not in place yet, and that there would be an announcem ent > about it in a week or so. (I tried to remove 150 routes). I've got > a few hundred more to do next week. Well... Regionals/mid-levels have always been able to delete net announcements, but the CIDR deployment raised the same sort of issue which had been raised previously when "silent nets" had been discussed: how about a way of deleting nets from the routing configuration files without removing the information from the PRDB, since we might reconfigure more-specific information soon? A normal delete is fine, and we are [read: "I am" ;-) ] finishing the implementation of the use of a "no configure" flag in the file generation (it'll be done for next Mon/Tues's config run). If you'd like to have your original 150 nets removed by hand before Tues. AM, please send them and I'll take care of it; looking at the current situation, it's probably a good thing to do. > -- > Robert Hood hoodr@netcom.com 1-408-983-1510 > System/Network Administrator for NETCOM On-line Communications Services, I nc. Steve Richardson/Merit - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 16:41:39 1994 Received: from netcom13.netcom.com (netcom13.netcom.com [192.100.81.125]) by merit.edu (8.6.8.1/merit-1.0) with ESMTP id QAA12077; Fri, 15 Apr 1994 16:41:38 -0400 Received: from localhost by netcom13.netcom.com (8.6.4/SMI-4.1/Netcom) id NAA18766; Fri, 15 Apr 1994 13:42:37 -0700 Message-Id: <199404152042.NAA18766@netcom13.netcom.com> From: hoodr@netcom.com (Robert Hood) Date: Fri, 15 Apr 1994 13:42:37 PDT In-Reply-To: Pushpendra Mohta "Re: 20402 routing entries" (Apr 15, 12:40pm) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Pushpendra Mohta Subject: Re: 20402 routing entries Cc: epg@merit.edu, bgpd@merit.edu, regional-techs@merit.edu >Robert Hood writes: >> I tried. They told me that the forms and policy for removing more >> specific routes were not in place yet, and that there would be an announcement >> about it in a week or so. (I tried to remove 150 routes). I've got >> a few hundred more to do next week. >> >Why dont you just stop announcing them ? I did, but BGP didn't want to let them go (the other end never recieved a network unreachable event). I tried finding a way to remove the routes without reseting the BGP link, but couldn't, so I just reset the links. I hate doing that. Can we change the subject to 20252 routes now? :) BTW: I just sent another set of CIDR NACRs to Merit. I hope to remove another ~350 routes by the end of next week. -- Robert Hood hoodr@netcom.com 1-408-983-1510 System/Network Administrator for NETCOM On-line Communications Services, Inc. - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 16:30:54 1994 Received: from psi.com (psi.com [192.67.6.2]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id QAA11007; Fri, 15 Apr 1994 16:30:52 -0400 Received: from us.psi.com by psi.com (4.1/2.1-PSI/PSINet) id AA21579; Fri, 15 Apr 94 16:30:07 EDT Received: by us.psi.com (4.1/SMI-4.1.3-PSI-pop) id AA12641; Fri, 15 Apr 94 16:03:08 EDT Message-Id: <9404152003.AA12641@us.psi.com> To: Jessica Yu Cc: hoodr@netcom.com (Robert Hood), epg@merit.edu, bgpd@merit.edu, regional-techs@merit.edu Subject: Re: 20402 routing entries In-Reply-To: Your message of "Fri, 15 Apr 1994 14:58:34 EDT." <199404151858.OAA01409@merit.edu> Date: Fri, 15 Apr 1994 16:02:57 -0400 From: "Martin Lee Schoffstall" And is only downside is that anyone not doing BGP4 he won't be able to talk to at all. Maybe you could help him a little bit and tell him who that might be. Marty > You just need to stop advertising those more specific routes if > you have already advertised the aggregate that covers them. It > will do the job of reducing the routing table. > > --jessica > > - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 17:38:50 1994 Received: from psi.com (psi.com [192.67.6.2]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id RAA17163; Fri, 15 Apr 1994 17:38:42 -0400 Received: from us.psi.com by psi.com (4.1/2.1-PSI/PSINet) id AA23699; Fri, 15 Apr 94 17:38:09 EDT Received: by us.psi.com (4.1/SMI-4.1.3-PSI-pop) id AA17510; Fri, 15 Apr 94 17:38:17 EDT Message-Id: <9404152138.AA17510@us.psi.com> To: "Peter S. Ford" Cc: yakov@watson.ibm.com, bgpd@merit.edu, regional-techs@merit.edu, fedor@us.psi.com Subject: Re: 20402 routing entries In-Reply-To: Your message of "Fri, 15 Apr 1994 15:23:27 MST." <199404152123.PAA27696@goshawk.lanl.gov> Date: Fri, 15 Apr 1994 17:38:16 -0400 From: "Martin Lee Schoffstall" In YOUR Internet you believe in name based portability. That is NOT what the people who have those numbers believe. You are confusing the technology vs the reality of the marketplace. That is not to say that you can't turn on your propaganda machine and make everyone believe that Comrade Peter is a friend of all Internet children. CIDR with masks defeats the substantial purpose's that you are selling CIDR to solve, I can't wait to see the processing impact of the increasingly sparse matrix's you are pushing. Not that I have heard anyone buy into it yet though. Marty PS: He was a red head. I think i'm casting myself as Medevev in this context. --------- > Marty, > > In the Internet we believe the issue will be name based portability, not > address portability. This level of decoupling will permit the > functionality of portable 800 numbers. +1 800 I-LIKE-IP is simply a name > which the telephone company maps to something which which they in > turn route to. > > It is important not to confuse naming with routing and packet forwarding. > > It is also important to note that CIDR is based on mask and match so > it is not exclusively hierarchical as you imply. It allows > for a mixture of flat and hierarchical routing, as the need arises. > This must be true since today the Internet exhibits both flat uncoordinated > addresses and hierarchically assigned addresses. We seem to be able to > route them in together. > > CIDR allows you to dial in the level of hierarchy you need. This seems to > be sound architecturally. > > cheers, Comrades Peter and Yakov > > P.S. I always like the way you color our debates in ideological terms, I > really enjoy picturing you in a Jeffersonian Wig. -- pf - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 17:32:49 1994 Received: from psi.com (psi.com [192.67.6.2]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id RAA16666; Fri, 15 Apr 1994 17:32:47 -0400 Received: from us.psi.com by psi.com (4.1/2.1-PSI/PSINet) id AA23462; Fri, 15 Apr 94 17:28:51 EDT Received: by us.psi.com (4.1/SMI-4.1.3-PSI-pop) id AA17044; Fri, 15 Apr 94 17:28:59 EDT Message-Id: <9404152128.AA17044@us.psi.com> To: hwb@upeksa.sdsc.edu (Hans-Werner Braun) Cc: peter@goshawk.lanl.gov, yakov@watson.ibm.com, bgpd@merit.edu, regional-techs@merit.edu, fedor@us.psi.com Subject: Re: 20402 routing entries In-Reply-To: Your message of "Fri, 15 Apr 1994 13:59:43 PDT." <9404152059.AA05680@upeksa.sdsc.edu> Date: Fri, 15 Apr 1994 17:28:57 -0400 From: "Martin Lee Schoffstall" PSI is easy (when compared to the below) I can't imagine going back to 5000 seperate companies and say "Give me your network number, by such and such a date, or I turn you off" I'll be glad to refer their lawyers to Peter, LLNL, the FNC or anyone who has a big wallet/purse/money-bag-under-bed to settle the issue. That is a non-deterministic path, it will not be ruled by fiat. A clean slate as below (tounge in cheek or not) is the chance to create the perfect information state (make sure all transactions are checkpointed through the FinCen etc). And of course there are other possabilities for clean slates. (Possabilities not probabilities btw). Marty > I tell ya, fellas, Marty is right. Renumbering is a looser. People will > give us more trouble than its worth it. E.g., PSI would never go for > giving up their Class A, as it means too much to them. Must help them > milking the cows. Lets just bandaid the current addressing structure > and protocols as best we can for a little longer, and under the premise > that we have to jettison the IP address space anyway and completely and > each and every bit a little while down the road. We should have gone > for CLNP years ago (didn't Clark suggest that in, uh, '86 or so > already)? If only for the sole benefit of a forced renumbering by means > of a brand new and hierarchical addressing space called NSAPs. Who > cares about petty details like the protocols chosen, and some > bells'n'whistles nonsense in each packet. The address is what counts. > Color and size of the envelope doesn't matter. Right on, Marty! - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 17:43:41 1994 Received: from psi.com (psi.com [192.67.6.2]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id RAA17675; Fri, 15 Apr 1994 17:43:39 -0400 Received: from us.psi.com by psi.com (4.1/2.1-PSI/PSINet) id AA23864; Fri, 15 Apr 94 17:43:01 EDT Received: by us.psi.com (4.1/SMI-4.1.3-PSI-pop) id AA17581; Fri, 15 Apr 94 17:43:08 EDT Message-Id: <9404152143.AA17581@us.psi.com> To: yakov@watson.ibm.com Cc: bgpd@merit.edu, regional-techs@merit.edu Subject: Re: 20402 routing entries In-Reply-To: Your message of "Fri, 15 Apr 1994 17:20:08 EDT." <9404152125.AA23410@psi.com> Date: Fri, 15 Apr 1994 17:43:07 -0400 From: "Martin Lee Schoffstall" You've been selling the CIDR drugs, your responsibility was to have come up with one. I think the community needs to have a solution, i can't come up with a unilateral one, and it will take a LONG time to sell a multilateral one. But we've been working on them for some number of months. Hint, think about buying back network numbers. General principal of the US Constitution is that if you take something you give some relief. (I'm not saying this is uniuque to the US btw). Marty > Ref: Your note of Fri, 15 Apr 1994 16:39:45 -0400 > > > Marty, > > >We will have to incent (carrot) people to do the right thing... > > Would you be so kind as to share with the rest of us what > that "right thing" is. > > >you have no plan... > > Would you be so kind as to tell us whether you have a plan ? > > Comrades Yakov&Peter > - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 17:20:42 1994 Received: from watson.ibm.com (watson.ibm.com [129.34.139.4]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id RAA15682; Fri, 15 Apr 1994 17:20:42 -0400 From: yakov@watson.ibm.com Message-Id: <199404152120.RAA15682@merit.edu> Received: from YKTVMV by watson.ibm.com (IBM VM SMTP V2R3) with BSMTP id 8081; Fri, 15 Apr 94 17:20:42 EDT Date: Fri, 15 Apr 94 17:20:08 EDT To: schoff@us.psi.com cc: bgpd@merit.edu, regional-techs@merit.edu Subject: 20402 routing entries Ref: Your note of Fri, 15 Apr 1994 16:39:45 -0400 Marty, >We will have to incent (carrot) people to do the right thing... Would you be so kind as to share with the rest of us what that "right thing" is. >you have no plan... Would you be so kind as to tell us whether you have a plan ? Comrades Yakov&Peter - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 16:57:06 1994 Received: from msf.psi.net (msf.psi.net [149.127.3.181]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id QAA13485; Fri, 15 Apr 1994 16:57:05 -0400 Received: by msf.psi.net (4.1/SMI-4.1.2-PSI) id AA01717; Fri, 15 Apr 94 16:57:04 EDT Date: Fri, 15 Apr 94 16:57:04 EDT From: fedor@msf.psi.net (Mark S. Fedor) Message-Id: <9404152057.AA01717@msf.psi.net> To: peter@goshawk.lanl.gov, schoff@us.psi.com Subject: Re: 20402 routing entries Cc: bgpd@merit.edu, fedor@us.psi.com, regional-techs@merit.edu, yakov@watson.ibm.com I'm sure that we will all eventually do CIDR/BGP4 and maybe even slow the growth of routing tables to a managable level. By this time we will all have 500MB routers..... Now with talk of global renumbering and a Utopian world of CIDR, what do we lose? I was never optimistic of how CIDR would work in a real operational redundant topology like the current internet. In this scenario, it is a big win to be able to have fine grain control of routing down to the organizational level. What does this mean? Well you can develop a routing strategies which take into account many diverse exit points from your AS. You can develop routing strategies based on high end users, low-end users, route the east coast here, the west coast there. You name it. You can't do this by routing large blocks of networks around. Pure CIDR'ists will say that you should divy up your blocks and assign addresses accordingly. Well... how many people who run networks have stayed with the exact same routing strategy with zero changes for more than 6 months? New connections and connectivity happen. The internet is an ever changing place. My CIDR allocation today will not be good for my routing strategy 2 months from now. As Andrew said, we are not fortune tellers... So, In a totally static topology, CIDR "the movie" and global renumbering will work. I wouldn't bet on static topology... Mark - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 17:02:18 1994 Received: from upeksa.sdsc.edu (upeksa.sdsc.edu [132.249.22.107]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id RAA14181; Fri, 15 Apr 1994 17:02:17 -0400 Received: by upeksa.sdsc.edu (AIX 3.2/UCB 5.64/4.03) id AA05680; Fri, 15 Apr 1994 13:59:43 -0700 From: hwb@upeksa.sdsc.edu (Hans-Werner Braun) Message-Id: <9404152059.AA05680@upeksa.sdsc.edu> Subject: Re: 20402 routing entries To: schoff@us.psi.com (Martin Lee Schoffstall) Date: Fri, 15 Apr 94 13:59:43 PDT Cc: peter@goshawk.lanl.gov, yakov@watson.ibm.com, bgpd@merit.edu, regional-techs@merit.edu, fedor@us.psi.com In-Reply-To: <9404152039.AA14510@us.psi.com>; from "Martin Lee Schoffstall" at Apr 15, 94 4:39 pm I tell ya, fellas, Marty is right. Renumbering is a looser. People will give us more trouble than its worth it. E.g., PSI would never go for giving up their Class A, as it means too much to them. Must help them milking the cows. Lets just bandaid the current addressing structure and protocols as best we can for a little longer, and under the premise that we have to jettison the IP address space anyway and completely and each and every bit a little while down the road. We should have gone for CLNP years ago (didn't Clark suggest that in, uh, '86 or so already)? If only for the sole benefit of a forced renumbering by means of a brand new and hierarchical addressing space called NSAPs. Who cares about petty details like the protocols chosen, and some bells'n'whistles nonsense in each packet. The address is what counts. Color and size of the envelope doesn't matter. Right on, Marty! - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 17:24:50 1994 Received: from goshawk.lanl.gov (goshawk.lanl.gov [128.165.96.145]) by merit.edu (8.6.8.1/merit-1.0) with ESMTP id RAA15879; Fri, 15 Apr 1994 17:24:49 -0400 Received: from localhost.lanl.gov (localhost.lanl.gov [127.0.0.1]) by goshawk.lanl.gov (8.6.7/8.6.4) with SMTP id PAA27696; Fri, 15 Apr 1994 15:23:28 -0600 From: "Peter S. Ford" Message-Id: <199404152123.PAA27696@goshawk.lanl.gov> X-Authentication-Warning: goshawk.lanl.gov: Host localhost.lanl.gov didn't use HELO protocol To: "Martin Lee Schoffstall" cc: yakov@watson.ibm.com, bgpd@merit.edu, regional-techs@merit.edu, fedor@us.psi.com Subject: Re: 20402 routing entries In-reply-to: Your message of Fri, 15 Apr 94 16:39:45 -0400. <9404152039.AA14510@us.psi.com> Date: Fri, 15 Apr 94 15:23:27 MST Marty, In the Internet we believe the issue will be name based portability, not address portability. This level of decoupling will permit the functionality of portable 800 numbers. +1 800 I-LIKE-IP is simply a name which the telephone company maps to something which which they in turn route to. It is important not to confuse naming with routing and packet forwarding. It is also important to note that CIDR is based on mask and match so it is not exclusively hierarchical as you imply. It allows for a mixture of flat and hierarchical routing, as the need arises. This must be true since today the Internet exhibits both flat uncoordinated addresses and hierarchically assigned addresses. We seem to be able to route them in together. CIDR allows you to dial in the level of hierarchy you need. This seems to be sound architecturally. cheers, Comrades Peter and Yakov P.S. I always like the way you color our debates in ideological terms, I really enjoy picturing you in a Jeffersonian Wig. -- pf - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 18:24:27 1994 Received: from psi.com (psi.com [192.67.6.2]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id SAA20473; Fri, 15 Apr 1994 18:24:26 -0400 Received: from us.psi.com by psi.com (4.1/2.1-PSI/PSINet) id AA25148; Fri, 15 Apr 94 18:23:53 EDT Received: by us.psi.com (4.1/SMI-4.1.3-PSI-pop) id AA19153; Fri, 15 Apr 94 18:24:01 EDT Message-Id: <9404152224.AA19153@us.psi.com> To: Dennis Ferguson Cc: "Peter S. Ford" , yakov@watson.ibm.com, bgpd@merit.edu, regional-techs@merit.edu, fedor@us.psi.com Subject: Re: 20402 routing entries In-Reply-To: Your message of "Fri, 15 Apr 1994 17:57:02 EDT." <199404152157.AA75919@foo.ans.net> Date: Fri, 15 Apr 1994 18:24:00 -0400 From: "Martin Lee Schoffstall" CIDR is a technology similiar to a Meat Cleaver It can be used for good or for ill. We've watched CIDR for a long time, and perceived it as having "stealth" implications in how it would be used. We are now seeing how it will be used, and how it is intended to be used. Some of them sound pretty bad (we are not surprised). We want to see CIDR used for good. Not for secret or not-so-secret agendas which we do not agree with. We want both hierachial and non-hierachial routing to proceed in parallel. Marty > > You have an IMPLEMENTATION problem in the NSFNet backbone and some other > > "key" places which will not accept any larger routing tables. > > Just to be clear, you are in fact mistaken. The RS/6000 routers are not > having problems with the current routing load. They no doubt will have > problems some day, you can't keep hardware forever if the task it needs > to do is continually growing, but the current problems are with 16M ciscos > in environments with relatively rich connectivity. > > You keep complaining about what is being done wrong, but have said very > little about what should be done instead. I'd be much more interested > in hearing the latter. > > Dennis Ferguson - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 18:00:25 1994 Received: from interlock.ans.net (interlock.ans.net [147.225.1.3]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id SAA18634; Fri, 15 Apr 1994 18:00:16 -0400 Received: by interlock.ans.net id AA33249 (InterLock SMTP Gateway 1.1); Fri, 15 Apr 1994 18:00:04 -0400 Received: by interlock.ans.net (Internal Mail Agent-2); Fri, 15 Apr 1994 18:00:04 -0400 Received: by interlock.ans.net (Internal Mail Agent-1); Fri, 15 Apr 1994 18:00:04 -0400 Message-Id: <199404152157.AA75919@foo.ans.net> To: "Martin Lee Schoffstall" Cc: "Peter S. Ford" , yakov@watson.ibm.com, bgpd@merit.edu, regional-techs@merit.edu, fedor@us.psi.com Subject: Re: 20402 routing entries In-Reply-To: Your message of "Fri, 15 Apr 1994 16:39:45 EDT." <9404152039.AA14510@us.psi.com> Date: Fri, 15 Apr 1994 17:57:02 -0400 From: Dennis Ferguson > You have an IMPLEMENTATION problem in the NSFNet backbone and some other > "key" places which will not accept any larger routing tables. Just to be clear, you are in fact mistaken. The RS/6000 routers are not having problems with the current routing load. They no doubt will have problems some day, you can't keep hardware forever if the task it needs to do is continually growing, but the current problems are with 16M ciscos in environments with relatively rich connectivity. You keep complaining about what is being done wrong, but have said very little about what should be done instead. I'd be much more interested in hearing the latter. Dennis Ferguson - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 18:40:56 1994 Received: from ski.utah.edu (ski.utah.edu [128.110.124.10]) by merit.edu (8.6.8.1/merit-1.0) with ESMTP id SAA21646; Fri, 15 Apr 1994 18:40:55 -0400 Received: (from haas@localhost) by ski.utah.edu (8.6.8/8.6.8.UUCC-C) id QAA11758; Fri, 15 Apr 1994 16:50:26 -0600 From: Walt Haas Message-Id: <199404152250.QAA11758@ski.utah.edu> Date: Fri, 15 Apr 94 16:50:26 MDT Subject: Re: 20402 routing entries To: "Martin Lee Schoffstall" , Dennis Ferguson , "Peter S. Ford" , yakov@watson.ibm.com, bgpd@merit.edu, regional-techs@merit.edu, fedor@us.psi.com In-Reply-To: "Martin Lee Schoffstall" , Fri, 15 Apr 1994 18:24:00 -0400 It seems to me that this entire discussion is based on the premise that renumbering is extremely slow, difficult, expensive and disruptive. This belief is probably justified given current technology. Our Chemistry department reported that they renumbered 20 workstations, and it was a week before anybody involved got any useful work done. One shudders to think what this means if extrapolated to the global Internet. However, if we could develop a technology which could make renumbering of a network (ie. a company, university or similar-sized unit) fast and efficient, this premise would break down and it would no longer be unreasonable to consider renumbering the organization when switching providers. Suppose, for example that Domain Names were sacred but a daemon could somehow touch every machine in a certain domain simultaneously and give it a new number, while simultaneously updating the routing tables that pointed into that domain? No, I don't have an RFC written, sorry, it's just an idea. -- Walt ------- - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 18:13:57 1994 Received: from goshawk.lanl.gov (goshawk.lanl.gov [128.165.96.145]) by merit.edu (8.6.8.1/merit-1.0) with ESMTP id SAA19811; Fri, 15 Apr 1994 18:13:56 -0400 Received: from localhost.lanl.gov (localhost.lanl.gov [127.0.0.1]) by goshawk.lanl.gov (8.6.7/8.6.4) with SMTP id QAA28449; Fri, 15 Apr 1994 16:12:33 -0600 From: "Peter S. Ford" Message-Id: <199404152212.QAA28449@goshawk.lanl.gov> X-Authentication-Warning: goshawk.lanl.gov: Host localhost.lanl.gov didn't use HELO protocol To: "Martin Lee Schoffstall" cc: hwb@upeksa.sdsc.edu (Hans-Werner Braun), yakov@watson.ibm.com, bgpd@merit.edu, regional-techs@merit.edu, fedor@us.psi.com Subject: Re: 20402 routing entries In-reply-to: Your message of Fri, 15 Apr 94 17:28:57 -0400. <9404152128.AA17044@us.psi.com> Date: Fri, 15 Apr 94 16:12:32 MST marty, If the return on routing entry (RORE) is large enough no one is going to particularly upset if mega-corp sends in a routing entry. The place to get gain is at the tiny places (my home for example with a subnet with a tiny number of hosts). >>> "Give me your network number, by such and such a date, or I turn you off" As I suggested in my note this is too strict a position to take. I suspect that PSI like most providers work with their customers, and could facilitate this kind of transition over time. The issue is to get from the current state to a better state. I am not unwilling to consider larger routers, hierarchy prudently applied, renumbering, etc. Why limit yourself when you have real problems to solve. The implication that I am gratuitously suggesting renumbering without solving a real problem is incorrect. If everything was going just right, the topic would not come up. If we figure out how to do this without any hierarchy as you seem to imply would be desirable, then I hope the vendors build routers big enough to hold routes to all the telephone outlets in China. We need some abstraction, and CIDR simply carries the IP subnetting model out to its logical conclusion. The thought that we can eliminate all hierarchy is as silly as demanding a strictly hierarchical system. Let's not confuse CIDR with renumbering. CIDR is to get reasonable routing handles on "places" in the Internet. In some cases this will be a 30 bit long prefix identifying a single host on a LAN and in some cases it will be the prefix to all the IP systems in Mozambique. Appropriate prefixes to meet routing requirements. I think this fits your notion of a non-deterministic path. cheers, peter - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 18:35:14 1994 Received: from psi.com (psi.com [192.67.6.2]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id SAA21219; Fri, 15 Apr 1994 18:35:09 -0400 Received: from us.psi.com by psi.com (4.1/2.1-PSI/PSINet) id AA25295; Fri, 15 Apr 94 18:34:08 EDT Received: by us.psi.com (4.1/SMI-4.1.3-PSI-pop) id AA19489; Fri, 15 Apr 94 18:34:16 EDT Message-Id: <9404152234.AA19489@us.psi.com> To: "Peter S. Ford" Cc: hwb@upeksa.sdsc.edu (Hans-Werner Braun), yakov@watson.ibm.com, bgpd@merit.edu, regional-techs@merit.edu, fedor@us.psi.com Subject: Re: 20402 routing entries In-Reply-To: Your message of "Fri, 15 Apr 1994 16:12:32 MST." <199404152212.QAA28449@goshawk.lanl.gov> Date: Fri, 15 Apr 1994 18:34:15 -0400 From: "Martin Lee Schoffstall" > > If the return on routing entry (RORE) is large enough no one is going to > particularly upset if mega-corp sends in a routing entry. The place > to get gain is at the tiny places (my home for example with a subnet with > a tiny number of hosts). We have a solution for that, we call it an InternetRelay, they are part and parcel of what we are deploying on cable. Surprise! > > >>> "Give me your network number, by such and such a date, or I turn you off" > > As I suggested in my note this is too strict a position to take. I > suspect that PSI like most providers work with their customers, and > could facilitate this kind of transition over time. The issue is to > get from the current state to a better state. I am not unwilling to > consider larger routers, hierarchy prudently applied, renumbering, > etc. Why limit yourself when you have real problems to solve. > The implication that I am gratuitously suggesting renumbering without > solving a real problem is incorrect. If everything was going just > right, the topic would not come up. And while your fording the stream with your tanks to liberate those shackled by RevisionistDemocrats you accidently crush ten civilians and your 120mm gun goes off and you take out the town Hospital. "I'm sorry, I'm from the government, I'm here to help". Basically you can cause more problems than you are solving with your current tac. > > If we figure out how to do this without any hierarchy as you seem to imply > would be desirable, then I hope the vendors build routers big enough to > hold routes to all the telephone outlets in China. We need some abstraction > and CIDR simply carries the IP subnetting model out to its logical > conclusion. The thought that we can eliminate all hierarchy is as silly > as demanding a strictly hierarchical system. I'm not eliminating all hierarchy, I'm arguing (at least) mixed mode, and of course no renumbering. > > Let's not confuse CIDR with renumbering. CIDR is to get reasonable > routing handles on "places" in the Internet. In some cases this will > be a 30 bit long prefix identifying a single host on a LAN and in some > cases it will be the prefix to all the IP systems in Mozambique. > Appropriate prefixes to meet routing requirements. I think this fits your > notion of a non-deterministic path. > If you think the current IP is going to deal with China then you have lost sight of what are reasonable design goals. Start again with new white paper. Don't saddle the current IP with totalitarian-administered CIDR to reach that goal. Marty - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 18:43:52 1994 Received: from lager.cisco.com (lager.cisco.com [131.108.11.55]) by merit.edu (8.6.8.1/merit-1.0) with ESMTP id SAA21722; Fri, 15 Apr 1994 18:43:52 -0400 Received: (tli@localhost) by lager.cisco.com (8.6.8+c/CISCO.SERVER.1.1) id PAA11886; Fri, 15 Apr 1994 15:42:00 -0700 Date: Fri, 15 Apr 1994 15:42:00 -0700 From: Tony Li Message-Id: <199404152242.PAA11886@lager.cisco.com> To: schoff@us.psi.com Cc: dennis@ans.net, peter@goshawk.lanl.gov, yakov@watson.ibm.com, bgpd@merit.edu, regional-techs@merit.edu, fedor@us.psi.com In-Reply-To: "Martin Lee Schoffstall"'s message of Fri, 15 Apr 1994 18:24:00 -0400 <9404152224.AA19153@us.psi.com> Subject: 20402 routing entries We want to see CIDR used for good. Not for secret or not-so-secret agendas which we do not agree with. We want both hierachial and non-hierachial routing to proceed in parallel. I believe that we have unanimous consent on these items. So, I'll play Suzanne Vega and ask "what's the matter here"? Tony - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 19:06:19 1994 Received: from ski.utah.edu (ski.utah.edu [128.110.124.10]) by merit.edu (8.6.8.1/merit-1.0) with ESMTP id TAA23177; Fri, 15 Apr 1994 19:06:18 -0400 Received: (from haas@localhost) by ski.utah.edu (8.6.8/8.6.8.UUCC-C) id RAA11881; Fri, 15 Apr 1994 17:15:47 -0600 From: Walt Haas Message-Id: <199404152315.RAA11881@ski.utah.edu> Date: Fri, 15 Apr 94 17:15:46 MDT Subject: Re: 20402 routing entries To: hwb@upeksa.sdsc.edu (Hans-Werner Braun) Cc: schoff@us.psi.com, dennis@ans.net, peter@goshawk.lanl.gov, yakov@watson.ibm.com, bgpd@merit.edu, regional-techs@merit.edu, fedor@us.psi.com In-Reply-To: hwb@upeksa.sdsc.edu (Hans-Werner Braun), Fri, 15 Apr 94 15:54:49 PDT >The problem is that there are many things that can be easily >overlooked. I believe if done right, renumbering 20 workstations in a >single department is a no-brainer. However, what it would require is >some cheat sheet of things that can be easily overlooked. Some recipe >of how to do it right. Exactly my point, the recipe could be defined in an RFC and implemented in code, so that the execution cost would be very low. This might be an easier problem to solve than the problem we are trying to address with CIDRizing. -- Walt ------- - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 18:37:40 1994 Received: from goshawk.lanl.gov (goshawk.lanl.gov [128.165.96.145]) by merit.edu (8.6.8.1/merit-1.0) with ESMTP id SAA21289; Fri, 15 Apr 1994 18:37:39 -0400 Received: from localhost.lanl.gov (localhost.lanl.gov [127.0.0.1]) by goshawk.lanl.gov (8.6.7/8.6.4) with SMTP id QAA28747; Fri, 15 Apr 1994 16:36:19 -0600 From: "Peter S. Ford" Message-Id: <199404152236.QAA28747@goshawk.lanl.gov> X-Authentication-Warning: goshawk.lanl.gov: Host localhost.lanl.gov didn't use HELO protocol To: "Martin Lee Schoffstall" cc: yakov@watson.ibm.com, bgpd@merit.edu, regional-techs@merit.edu, fedor@us.psi.com Subject: Re: 20402 routing entries In-reply-to: Your message of Fri, 15 Apr 94 17:38:16 -0400. <9404152138.AA17510@us.psi.com> Date: Fri, 15 Apr 94 16:36:19 MST >>> In YOUR Internet you believe in name based portability. What fraction of Internet users know their DNS names better than they know their IP addresses? What number of people know my email address vrs the number who know my IP address? I bet more users know more URLs than IP addresses. >>> That is NOT what the people who have those numbers believe. >>>> You are confusing the technology vs the reality of the marketplace. No, I am considering what the users really want, which is Internet services, and THEY are the ones who don't care about address space, technology, etc. >>> That is not to say that you can't turn on your propaganda machine and >>> make everyone believe that Comrade Peter is a friend of all Internet children. I will plead guilty to selling ice cream on a hot day. Sort of a market driven thing. You can scream all you want about how it is going to cool off tonight, I've got to go back to taking care of that line of customers. >>> CIDR with masks defeats the substantial purpose's that you are selling >>> CIDR to solve, I can't wait to see the processing impact of the >>> increasingly sparse matrix's you are pushing. Not that I have heard >>> anyone buy into it yet though. CIDR always has masks, by defn. CIDR without masks is like a black russian without Kahlua. If you are refering to the notion that through hierarchical abstraction you lose information, you are certainly correct. However, most networks don't want to know *all* of the gory details of networks halfway across the globe, or even in the next state. >>> Marty petrov >>> PS: He was a red head. I think i'm casting myself as Medevev in this context. Harder to image, but I'll work on it. Long live the revolution! - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 18:47:07 1994 Received: from goshawk.lanl.gov (goshawk.lanl.gov [128.165.96.145]) by merit.edu (8.6.8.1/merit-1.0) with ESMTP id SAA21768; Fri, 15 Apr 1994 18:47:06 -0400 Received: from localhost.lanl.gov (localhost.lanl.gov [127.0.0.1]) by goshawk.lanl.gov (8.6.7/8.6.4) with SMTP id QAA28974; Fri, 15 Apr 1994 16:45:44 -0600 From: "Peter S. Ford" Message-Id: <199404152245.QAA28974@goshawk.lanl.gov> X-Authentication-Warning: goshawk.lanl.gov: Host localhost.lanl.gov didn't use HELO protocol To: "Martin Lee Schoffstall" cc: yakov@watson.ibm.com, bgpd@merit.edu, regional-techs@merit.edu Subject: Re: 20402 routing entries In-reply-to: Your message of Fri, 15 Apr 94 17:43:07 -0400. <9404152143.AA17581@us.psi.com> Date: Fri, 15 Apr 94 16:45:43 MST >>> Hint, think about buying back network numbers. >>> General principal of the US Constitution is that if you take something >>> you give some relief. (I'm not saying this is uniuque to the US btw). Now I think we are getting in synch. I don't think this is completely unreasonable. And if you charge enough it will help drive an IPng solution thereby voiding the original value. Question? What is the value of something that the govt. granted you at no cost? And do you really "own" it or do you simply own the mineral rights? These are serious issues. And the notions of rents etc. all play into it, especially when you consider things like DHCP leases. cheers, peter P.S. Perhaps this solution will lead to the same checkerboard quilt of land ownership you see between railroads and the U.S. Forest Service? Land grants in cyberspace? - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 18:59:20 1994 Received: from brazos.is.rice.edu (bmanning@brazos.is.rice.edu [128.42.42.2]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id SAA22464; Fri, 15 Apr 1994 18:59:19 -0400 Received: by brazos.is.rice.edu (AA02367); Fri, 15 Apr 94 17:57:59 CDT From: bmanning@is.rice.edu (William Manning) Message-Id: <9404152257.AA02367@brazos.is.rice.edu> Subject: Re: 20402 routing entries To: schoff@us.psi.com (Martin Lee Schoffstall) Date: Fri, 15 Apr 1994 17:57:58 -0500 (CDT) Cc: yakov@watson.ibm.com, bgpd@merit.edu, regional-techs@merit.edu In-Reply-To: <9404152143.AA17581@us.psi.com> from "Martin Lee Schoffstall" at Apr 15, 94 05:43:07 pm X-Mailer: ELM [version 2.4 PL22] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 268 Martin Lee Schoffstall sez: > > Hint, think about buying back network numbers. > Just how much did you pay for -your- network numbers? How much are they worth to you? I just might be willing to take you up on your most generous offer. -- Regards, Bill Manning - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 18:56:20 1994 Received: from upeksa.sdsc.edu (upeksa.sdsc.edu [132.249.22.107]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id SAA22355; Fri, 15 Apr 1994 18:56:20 -0400 Received: by upeksa.sdsc.edu (AIX 3.2/UCB 5.64/4.03) id AA16210; Fri, 15 Apr 1994 15:54:49 -0700 From: hwb@upeksa.sdsc.edu (Hans-Werner Braun) Message-Id: <9404152254.AA16210@upeksa.sdsc.edu> Subject: Re: 20402 routing entries To: haas@ski.utah.edu (Walt Haas) Date: Fri, 15 Apr 94 15:54:49 PDT Cc: schoff@us.psi.com, dennis@ans.net, peter@goshawk.lanl.gov, yakov@watson.ibm.com, bgpd@merit.edu, regional-techs@merit.edu, fedor@us.psi.com In-Reply-To: <199404152250.QAA11758@ski.utah.edu>; from "Walt Haas" at Apr 15, 94 4:50 pm >This belief is probably justified given current technology. Our Chemistry >department reported that they renumbered 20 workstations, and it was a >week before anybody involved got any useful work done. One shudders to >think what this means if extrapolated to the global Internet. The problem is that there are many things that can be easily overlooked. I believe if done right, renumbering 20 workstations in a single department is a no-brainer. However, what it would require is some cheat sheet of things that can be easily overlooked. Some recipe of how to do it right. I still believe renumbering what we reasonably can is well worth it and people should be encouraged to do so. But we *will* hit the kind of attitudes that Marty is pointing out, no doubt. Have seen my share of it already (e.g., net 35). I guess the question is whether we will try to make the best of it, expecting that while people prefer to be lazy, but even more prefer to be good citizens, whether we cut our losses and move to NSAPs or so, or whether we are just gonna let the network just go to hell. Hans-Werner - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 19:35:02 1994 Received: from lager.cisco.com (lager.cisco.com [131.108.11.55]) by merit.edu (8.6.8.1/merit-1.0) with ESMTP id TAA24902; Fri, 15 Apr 1994 19:35:01 -0400 Received: (tli@localhost) by lager.cisco.com (8.6.8+c/CISCO.SERVER.1.1) id QAA14873; Fri, 15 Apr 1994 16:32:30 -0700 Date: Fri, 15 Apr 1994 16:32:30 -0700 From: Tony Li Message-Id: <199404152332.QAA14873@lager.cisco.com> To: haas@ski.utah.edu Cc: hwb@upeksa.sdsc.edu, schoff@us.psi.com, dennis@ans.net, peter@goshawk.lanl.gov, yakov@watson.ibm.com, bgpd@merit.edu, regional-techs@merit.edu, fedor@us.psi.com In-Reply-To: Walt Haas's message of Fri, 15 Apr 94 17:15:46 MDT <199404152315.RAA11881@ski.utah.edu> Subject: 20402 routing entries Exactly my point, the recipe could be defined in an RFC and implemented in code, so that the execution cost would be very low. This might be an easier problem to solve than the problem we are trying to address with CIDRizing. I think folks are missing the point. The primary goal of CIDR is to slow the growth of the routing table. Renumbering without CIDR is a pointless waste. It buys you nothing. Renumbering _with_ CIDR allows the addressing to more closely match the topological hierarchy, and thus allows routing to eliminate some noise from the routing system, thus allowing it to scale better. So renumbering helps. However, folks should recall that CIDR _requests_ and _recommends_ that people renumber. However, no one is trying to or has a mechanism to force people to renumber. It's just a matter of being a good citizen. Folks who don't want to be good citizens will exist. So be it. Now, if the extremist parties on all sides could take a deep breath and start being rational, we could get back to work. Tony - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 19:05:34 1994 Received: from sprintlink.net (tiny.sprintlink.net [199.0.55.90]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id TAA23154; Fri, 15 Apr 1994 19:05:33 -0400 Received: from flagstone-ether.keepe.intercon.com by sprintlink.net (5.65/1.34) id AA10033; Fri, 15 Apr 94 19:05:33 -0500 X-Mailer: InterCon TCP/Connect II 1.2 Message-Id: <9404151905.AA07840@srobseas.sprint.dialup.net> Date: Fri, 15 Apr 1994 19:05:07 -0500 From: "Robert E. Seastrom" To: bgpd@merit.edu, regional-techs@merit.edu Subject: egregious waste of bandwidth... Hmmm, the regional-techs and bgpd lists are looking a lot like com-priv these days... ---Rob - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 19:42:20 1994 Received: from Hearts.ACES.COM (Hearts.ACES.COM [192.195.240.4]) by merit.edu (8.6.8.1/merit-1.0) with ESMTP id TAA25358; Fri, 15 Apr 1994 19:42:18 -0400 Received: from ACES.COM by ACES.COM (PMDF V4.2-10 #4107) id <01HB78IUHRMO0009H3@ACES.COM>; Fri, 15 Apr 1994 16:41:48 MST Date: Fri, 15 Apr 1994 16:37:58 -0700 (MST) From: Ehud Gavron Subject: RE: 20402 routing entries In-reply-to: Your message dated "Fri, 15 Apr 1994 17:57:58 -0500 (CDT)" <9404152257.AA02367@brazos.is.rice.edu> To: bmanning@is.rice.edu Cc: schoff@us.psi.com, yakov@watson.ibm.com, bgpd@merit.edu, regional-techs@merit.edu, Ehud Gavron Message-id: <01HB7LOBP1S20009H3@ACES.COM> Organization: ACES Research Inc. MIME-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Date Sent: 15-APR-1994 16:37:59 >Just how much did you pay for -your- network numbers? >How much are they worth to you? I just might be willing >to take you up on your most generous offer. Getting something for free doesn't make it worthless, as any of my married friends keep telling me. However, the US Government is in no position to take IP numbers back [or away] from the worldwide users of the IP protocol. While "IP IS THE REAL THING", let's not screw it up. I'd tend to take Marty's comments seriously. While we use IP, upgrade the 16Mb Ciscos. After that, work a solution into it and let people keep their numbers foever ala 1-800 numbers. Ehud -- Ehud Gavron (EG76) gavron@Hearts.ACES.COM - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 19:42:16 1994 Received: from brazos.is.rice.edu (bmanning@brazos.is.rice.edu [128.42.42.2]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id TAA25354; Fri, 15 Apr 1994 19:42:15 -0400 Received: by brazos.is.rice.edu (AA03054); Fri, 15 Apr 94 18:42:14 CDT From: bmanning@is.rice.edu (William Manning) Message-Id: <9404152342.AA03054@brazos.is.rice.edu> Subject: Dups To: bgpd@merit.edu, regional-techs@merit.edu Date: Fri, 15 Apr 1994 18:42:13 -0500 (CDT) X-Mailer: ELM [version 2.4 PL22] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 112 I am getting a lot of these.... Perhaps this is the carrot to dump an AS or two. :) -- Regards, Bill Manning - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 20:20:36 1994 Received: from lager.cisco.com (lager.cisco.com [131.108.11.55]) by merit.edu (8.6.8.1/merit-1.0) with ESMTP id UAA27453; Fri, 15 Apr 1994 20:20:36 -0400 Received: (tli@localhost) by lager.cisco.com (8.6.8+c/CISCO.SERVER.1.1) id RAA18199; Fri, 15 Apr 1994 17:18:39 -0700 Date: Fri, 15 Apr 1994 17:18:39 -0700 From: Tony Li Message-Id: <199404160018.RAA18199@lager.cisco.com> To: t.c.streater@dante.org.uk Cc: hwb@upeksa.sdsc.edu, haas@ski.utah.edu, schoff@us.psi.com, dennis@ans.net, peter@goshawk.lanl.gov, yakov@watson.ibm.com, bgpd@merit.edu, regional-techs@merit.edu, fedor@us.psi.com In-Reply-To: Tim Streater's message of Sat, 16 Apr 1994 01:01:38 +0000 <9404160001.AA02297@dante.org.uk> Subject: 20402 routing entries (renumbering) They expect the network to be like the phone or power outlets; you just plug in where you happen to be. If we expect renumbering and provider-based addressing to be feasible, it seems to me that w/s vendors need to provide powerful tools to enable *transparent* *on-the-fly* renumbering - else it won't happen. And even if they do (and where's the carrot for *them*?), it will be quite a while before such tools are ubiquitous enough to make the process always easy. Should we be working with vendors in this area? I'm told that numerous host vendors are working on developing DHCP. Of course, this does not fix legacy systems, but it does mean that renumbering may get easier than it is today. The carrot for them is that it makes it easier to renumber. ;-) This makes life easier for the network manager, who has to deal with Sally and George moving their department to the third floor problems. Tony - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 19:57:43 1994 Received: from titan.sprintlink.net (titan.sprintlink.net [199.0.55.78]) by merit.edu (8.6.8.1/merit-1.0) with ESMTP id TAA25964; Fri, 15 Apr 1994 19:57:40 -0400 Received: (from avg@localhost) by titan.sprintlink.net (8.6.8/8.6.8) id TAA12304; Fri, 15 Apr 1994 19:57:40 -0400 Date: Fri, 15 Apr 1994 19:57:40 -0400 From: Vadim Antonov Message-Id: <199404152357.TAA12304@titan.sprintlink.net> To: peter@goshawk.lanl.gov, schoff@us.psi.com Subject: Re: 20402 routing entries Cc: bgpd@merit.edu, fedor@us.psi.com, regional-techs@merit.edu, yakov@watson.ibm.com Not, Marty; the "market reality" is that you do CIDR or people will stop getting PSI's routes. By not doing it you already got screwed routing; the next step is loss of global connectivity, i guess. God bless your customers. Your analogy with 800 portability and IP renumbering is more than artificial. The whole debate about 800 portability rotated around retracting published numbers and loss of investments in advertisements. So far i didn't hear anyone publishing IP numbers in their ads. Changing providers *always* involves some expenses and probably disruption of service. Also, nobody was really interested in renumbering technology in pre-CIDR times; now market will force software vendors to provide network number discovery as a standard feature. The host portability problem is not new -- the mobile communications folks worked on it for quite a time; but it wasn't anywhere near the interest field of regular TCP/IP community. Now it is -- as well as IPNG, video and security. New times, new problems. --vadim - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 20:05:52 1994 Received: from titan.sprintlink.net (titan.sprintlink.net [199.0.55.78]) by merit.edu (8.6.8.1/merit-1.0) with ESMTP id UAA26570; Fri, 15 Apr 1994 20:05:51 -0400 Received: (from avg@localhost) by titan.sprintlink.net (8.6.8/8.6.8) id UAA12349; Fri, 15 Apr 1994 20:05:51 -0400 Date: Fri, 15 Apr 1994 20:05:51 -0400 From: Vadim Antonov Message-Id: <199404160005.UAA12349@titan.sprintlink.net> To: bgpd@merit.edu, regional-techs@merit.edu Subject: Re: 20402 routing entries >>you have no plan... >Would you be so kind as to tell us whether you have a plan ? "Mister Fiks, do you have a plan?" "Do I have a plan? Do I have a plan? I have two sacks of plan!" :-) --vadim - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 20:09:20 1994 Received: from dante.org.uk (sun.dante.org.uk [193.63.211.1]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id UAA26635; Fri, 15 Apr 1994 20:09:18 -0400 Received: from [193.63.211.8] (mac-tim.dante.org.uk) by dante.org.uk (5.0/SMI-SVR4) id AA02297; Sat, 16 Apr 94 01:01:28 BST Message-Id: <9404160001.AA02297@dante.org.uk> X-Sender: tim@omega Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 16 Apr 1994 01:01:38 +0000 To: hwb@upeksa.sdsc.edu (Hans-Werner Braun), haas@ski.utah.edu (Walt Haas) From: t.c.streater@dante.org.uk (Tim Streater) Subject: Re: 20402 routing entries (renumbering) Cc: schoff@us.psi.com, dennis@ans.net, peter@goshawk.lanl.gov, yakov@watson.ibm.com, bgpd@merit.edu, regional-techs@merit.edu, fedor@us.psi.com content-length: 2393 Renumbering workstations in principle *is* a no-brainer. But there are always wrinkles. And if those workstations are running a particle accelerator (as when a year or so ago I coordinated some renumbering at SLAC), you better have a damn good reason for doing it. A $20M facility running 7*24 expects good reasons for you to possibly screw it up, and their operational philosophy is to assume you will. I was able to renumber two largish groups of machines (200 or so in each), with quite a bit of coordination needed, and because of the various overlapping schedules it took a while before I could even start. Then, for each group I had to assemble numerous experts (Macs, Amigas, PCs, Next, RS/6000, Sun, Ultrix, VAX, Cisco). Luckily we had a good database of workstations so that I could tell the platform experts which machines were going to be involved. In some cases changes had to be backed out a couple of times because of something the platform experts forgot (or didn't know about). Now, can you imagine the conversation I might have had if still working there and SLAC agrees to exchange its class B (with about 1k out of 64k addresses assigned) for some number of class C: Me: SLAC has to renumber! Users: Again? OK Tim - but why? And what's in it for us? Me: (explanation of routing overload deleted) Users: So you are saying that of the 20k or so addresses in routers, SLAC renumbering saves just one entry? Me: Err, yes. Users: Don't ring us, we'll ring you! As Marty says, there is (unfortunately) no carrot - and users resent the stick. You apply the stick too often and you are out the door, either as an external provider or internal expert. Users barely (in some instances) know what an IP address is. They expect the network to be like the phone or power outlets; you just plug in where you happen to be. If we expect renumbering and provider-based addressing to be feasible, it seems to me that w/s vendors need to provide powerful tools to enable *transparent* *on-the-fly* renumbering - else it won't happen. And even if they do (and where's the carrot for *them*?), it will be quite a while before such tools are ubiquitous enough to make the process always easy. Should we be working with vendors in this area? Now will you all *go* *home* - it's the weekend, damnit! Tim Streater, DANTE. t.c.streater@dante.org.uk +44 223 302992 - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 21:03:34 1994 Received: from nic.near.net (nic.near.net [192.52.71.4]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id VAA29695; Fri, 15 Apr 1994 21:03:33 -0400 Received: from platinum.near.net by nic.near.net id aa25053; 15 Apr 94 21:03 EDT To: Tim Streater cc: bgpd@merit.edu, regional-techs@merit.edu Subject: Re: 20402 routing entries (renumbering) In-reply-to: Your message of Sat, 16 Apr 1994 01:01:38 -0000. <9404160001.AA02297@dante.org.uk> Date: Fri, 15 Apr 1994 21:02:36 -0400 From: John Curran Message-ID: <9404152103.aa25053@nic.near.net> -------- ] From: Tim Streater ] Subject: Re: 20402 routing entries (renumbering) ] Date: Sat, 16 Apr 1994 01:01:38 +0000 ] ... ] Now, can you imagine the conversation I might have had if still working ] there and SLAC agrees to exchange its class B (with about 1k out of 64k ] addresses assigned) for some number of class C: ] ] Me: SLAC has to renumber! ] Users: Again? OK Tim - but why? And what's in it for us? ] Me: (explanation of routing overload deleted) ] Users: So you are saying that of the 20k or so addresses in routers, ] SLAC renumbering saves just one entry? ] Me: Err, yes. ] Users: Don't ring us, we'll ring you! ] ] As Marty says, there is (unfortunately) no carrot - and users resent the ] stick. ] ... Tim, I agree that there is no motivation for renumbering. I also agreement that convenient renumbering technology would be very valuable in pursuit of CIDR renumbering. I don't believe that renumbering technology will be sufficient, because (as Marty notes): there's still no carrot. The fact of the matter is that there is going to be a carrot soon... it may not be a very big carrot, but there will be one. At some point or another, the cost of route entry propagation will be identified and some enterprising soul will turn a "problem" into a business opportunity by actually recovering these costs seperately. Yes, it will be messy, and providers will begin handling routing (not traffic) settlements, but if the cost component of routing gets high enough, then it's quite likely to emerge as a separate item. Of course, most folks will be forgiven for entering a single route into the Internet (and it will be absorbed in service costs as it is today), but folks with random collections of network numbers will feel some impact. Will a fortune 500 company be concerned about the extra [wild estimate] $250/month to keep their dozen distinct CIDR entries? Perhaps not, they may even consider it a good investment compared to renumbering when they change providers. Would the local bookstore renumber both their hosts (when changing providers) in order to avoid $20/month? Maybe. Look, if the real cost of a routing entry in the global Internet is low, then people will pay it and not worry about CIDR. If it turns out that it's quite costly to enter a global route, then some people will invest the effort to avoid the cost. No, it's not going to have an impact on most businesses, because the financials will almost work out to paying for the routing service. I also expect that SLAC would pay to have their entry maintained in the situation above. /John - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 20:24:28 1994 Received: from upeksa.sdsc.edu (upeksa.sdsc.edu [132.249.22.107]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id UAA27535; Fri, 15 Apr 1994 20:24:27 -0400 Received: by upeksa.sdsc.edu (AIX 3.2/UCB 5.64/4.03) id AA11083; Fri, 15 Apr 1994 17:22:26 -0700 From: hwb@upeksa.sdsc.edu (Hans-Werner Braun) Message-Id: <9404160022.AA11083@upeksa.sdsc.edu> Subject: Re: 20402 routing entries (renumbering) To: t.c.streater@dante.org.uk (Tim Streater) Date: Fri, 15 Apr 94 17:22:25 PDT Cc: haas@ski.utah.edu, schoff@us.psi.com, dennis@ans.net, peter@goshawk.lanl.gov, yakov@watson.ibm.com, bgpd@merit.edu, regional-techs@merit.edu, fedor@us.psi.com In-Reply-To: <9404160001.AA02297@dante.org.uk>; from "Tim Streater" at Apr 16, 94 1:01 am Sounds like the same kind of mentality that lets people in LA drive cars with a 20 miles/gallon mileage. Me: You have to use cars with better mileage! Users: Again? OK - but why? And what's in it for me? Me: (explanation of air overload of pullutants deleted) Users: So you are saying that of the 200 tons (or whatever) of the total pollution in LA's air due to the usage of gas in cars, that my buying a 60 miles/gallon car saves just a few pounds? Me: Err, yes. Users: Don't ring us, we'll ring you! .... later ... Users: Uuuuhhhh, this cancer is KILLing me ... .... much later (Users: are dead by now) ... Quiz: Should Users: have saved 2 gallons/day or moved to Alaska? >Renumbering workstations in principle *is* a no-brainer. But there are >always wrinkles. And if those workstations are running a particle >accelerator (as when a year or so ago I coordinated some renumbering at >SLAC), you better have a damn good reason for doing it. A $20M facility >running 7*24 expects good reasons for you to possibly screw it up, and >their operational philosophy is to assume you will. > >I was able to renumber two largish groups of machines (200 or so in each), >with quite a bit of coordination needed, and because of the various >overlapping schedules it took a while before I could even start. Then, for >each group I had to assemble numerous experts (Macs, Amigas, PCs, Next, >RS/6000, Sun, Ultrix, VAX, Cisco). Luckily we had a good database of >workstations so that I could tell the platform experts which machines were >going to be involved. In some cases changes had to be backed out a couple >of times because of something the platform experts forgot (or didn't know >about). > >Now, can you imagine the conversation I might have had if still working >there and SLAC agrees to exchange its class B (with about 1k out of 64k >addresses assigned) for some number of class C: > >Me: SLAC has to renumber! >Users: Again? OK Tim - but why? And what's in it for us? >Me: (explanation of routing overload deleted) >Users: So you are saying that of the 20k or so addresses in routers, > SLAC renumbering saves just one entry? >Me: Err, yes. >Users: Don't ring us, we'll ring you! > >As Marty says, there is (unfortunately) no carrot - and users resent the >stick. You apply the stick too often and you are out the door, either as an >external provider or internal expert. Users barely (in some instances) know >what an IP address is. They expect the network to be like the phone or >power outlets; you just plug in where you happen to be. If we expect >renumbering and provider-based addressing to be feasible, it seems to me >that w/s vendors need to provide powerful tools to enable *transparent* >*on-the-fly* renumbering - else it won't happen. And even if they do (and >where's the carrot for *them*?), it will be quite a while before such tools >are ubiquitous enough to make the process always easy. Should we be working >with vendors in this area? > >Now will you all *go* *home* - it's the weekend, damnit! > >Tim Streater, DANTE. t.c.streater@dante.org.uk +44 223 302992 > > > - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 20:34:03 1994 Received: from goshawk.lanl.gov (goshawk.lanl.gov [128.165.96.145]) by merit.edu (8.6.8.1/merit-1.0) with ESMTP id UAA28070; Fri, 15 Apr 1994 20:34:02 -0400 Received: from localhost.lanl.gov (localhost.lanl.gov [127.0.0.1]) by goshawk.lanl.gov (8.6.7/8.6.4) with SMTP id SAA29978; Fri, 15 Apr 1994 18:33:52 -0600 From: "Peter S. Ford" Message-Id: <199404160033.SAA29978@goshawk.lanl.gov> X-Authentication-Warning: goshawk.lanl.gov: Host localhost.lanl.gov didn't use HELO protocol To: t.c.streater@dante.org.uk (Tim Streater) cc: bgpd@merit.edu, regional-techs@merit.edu Subject: Re: 20402 routing entries (renumbering) In-reply-to: Your message of Sat, 16 Apr 94 01:01:38 -0000. <9404160001.AA02297@dante.org.uk> Date: Fri, 15 Apr 94 18:33:51 MST Tim, Many vendors have recently implemented DHCP and I know a few vendors who are very interested in going beyond simple DHCP. The goal is to get to the point that you get your system, and it can simply plug into the Internet and most things you want, DNS and addresses (host, router, other servers, etc.) are all auto-configured over the wire. In the case of dialup or ISDN this could be done up to the point of providing the "phone number" and one could imagine a system where the initial phone number would not be necessary. With set top box being the current rage in the telecom industry it is very important to have a viable strategy for autoconfiguring/registering into the Internet for simple devices (PCs on modems/ISDN, set top box, etc.). cheers, peter - - - - - - - - - - - - - - - - - From list-admin Fri Apr 15 20:54:44 1994 Received: from upeksa.sdsc.edu (upeksa.sdsc.edu [132.249.22.107]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id UAA29094; Fri, 15 Apr 1994 20:54:43 -0400 Received: by upeksa.sdsc.edu (AIX 3.2/UCB 5.64/4.03) id AA16133; Fri, 15 Apr 1994 17:53:16 -0700 From: hwb@upeksa.sdsc.edu (Hans-Werner Braun) Message-Id: <9404160053.AA16133@upeksa.sdsc.edu> Subject: Re: 20402 routing entries (renumbering) To: t.c.streater@dante.org.uk (Tim Streater) Date: Fri, 15 Apr 94 17:53:15 PDT Cc: haas@ski.utah.edu, schoff@us.psi.com, dennis@ans.net, peter@goshawk.lanl.gov, yakov@watson.ibm.com, bgpd@merit.edu, regional-techs@merit.edu, fedor@us.psi.com In-Reply-To: <9404160001.AA02297@dante.org.uk>; from "Tim Streater" at Apr 16, 94 1:01 am Look, guys, get real. CIDR is a big kluge and it was predictable as such. But as a second or third best "solution" it is necessary to use it, as the powers of anarchy screwed the Internet royally two years ago when the Internet community should have elected NSAPs. Remember the IESG solicitation for IPv7, to then be all done and settled by November 1992 (or was it 1991?). CIDR is just a bandaid because the community does not have its act together, and varieties of things are not driven by operational requirements. I don't particularly like CIDR, as compared to cleaner choices, but believe we have no choice but to use it as much and as best we can. Until the IETF/IESG/IAB/whoever get their stuff in gear and define and follow through on a process that pragmatically looks at requirements, defines a reasonable subset as strategic direction and people go off implementing and deploying it. From what I have seen so far, despite them I**3 claims, there seems to be a neverending target with really no end in sight. Like it or not, as several have pointed out already, router still, as already for the last ten years or so, get blown away by the routing table sizes. If you have a well defined funding stream you may be able to upgrade, otherwise you may be screwed. There is no routing plan on a global level that also goes down to the capillaries and their interconnectivity, and people naively believe that arbitrary interconnections have to work for generations to come. And if I create a 2400 bps dial up link to London, it has to be possible for the whole US to use it as a fallback, as a solid requirement, right? You have no choice, gang, reality says there are too many routes, routers break, and arbitrariness doesn't scale. Amplifying this will be the dismantling of the NSFNET, resulting in much more of an interconnection weave than a backbone or core. As much as I dislike CIDR by itself, I see no choice at this point of time to move ahead with it as much as we can, even if it causes some pain, or problems will continue, until we find a long term sulution and quit this bickering about the IPng protocol details. Hans-Werner PS: May be Microsoft *should* make the choice for us. Then even Marty gets his clean slate. - - - - - - - - - - - - - - - - - From list-admin Sat Apr 16 08:41:15 1994 Received: from ncc.ripe.net (ncc.ripe.net [192.87.45.2]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id IAA05516; Sat, 16 Apr 1994 08:41:14 -0400 Received: from mellow.ripe.net by ncc.ripe.net with SMTP id AA07432 (5.65a/NCC-2.2); Sat, 16 Apr 1994 14:41:13 +0200 Received: from localhost.ripe.net by mellow.ripe.net with SMTP id AA05156 (5.65a/NCC-2.1); Sat, 16 Apr 1994 14:41:12 +0200 Message-Id: <9404161241.AA05156@mellow.ripe.net> To: "Peter S. Ford" Cc: "Martin Lee Schoffstall" , yakov@watson.ibm.com, bgpd@merit.edu, regional-techs@merit.edu Subject: Re: 20402 routing entries In-Reply-To: Your message of Fri, 15 Apr 1994 13:18:10 MST. <199404151918.NAA24007@goshawk.lanl.gov> From: Daniel Karrenberg X-Organization: RIPE Network Coordination Centre X-Phone: +31 20 592 5065 Date: Sat, 16 Apr 1994 14:41:11 +0200 Sender: Daniel.Karrenberg@ripe.net Peter & Yakov, the only carrot/stick combination that is going to work is to charge for announcements - period. Make a charging scheme that punishes many small announcements out-of provider block announcements Convince the big transit providers to implement it and it will percolate downwards. This has some problems too but is the only carrot/stick combination that will work better than just convincing people to be good citizens. Daniel Speaking for myself only > "Peter S. Ford" writes: > > > Marty, > > >a bit less than 28,000 currently configured "Internet" network > >numbres believe they have permanently gained their class B's and > >C's. Or at least the ones in the US believe that. > > > >a bit less than all assigned network numbers total believe that > >they have gained their class B's and C's and will never give up > >and renumber > > > >You have provided no incentive (carrot) for individual companies > >to do the right thing. > > Let us try to answer your question with another question: > > Do you want a routable large scale global Internet ? > > It is hard to imagine supporting a truly huge Internet without relying > on hierarchical routing (CIDR is simply a realization of > hierarchical routing). > > And if you do plan to rely on hierarchical routing, then you need to > understand how to deal with the issue of containing address entropy > (due to switching among providers) without renumbering. It seems naive > and perhaps irresponsible to think about flat routing (based on network > numbers). It should be a goal to make this renumbering simple. > > We'd like to suggest that folks with alternative proposals to CIDR > should put their alternative proposals on a table and explain, among > other things, how their proposals would be deployed and used and how > these proposals would be better than CIDR. Hitting the right time > frame turns out to count! > > > When people got network numbers in the past they were getting addresses > for the research Internet. It is important to understand that the > research Internet was a great thing, but we are now working on the > global public Internet and we desperately needed new routing and addressing > > systems. We should establish that we are in a transition from the > research Internet to the global public Internet and we subsequently > can not just use uncoordinated IP addresses and still have a workable > system. This is not dissimilar to what happened when local phone > exchanges started to get interconnected during the advent of long > distance telephone services. There needs to be a globally coordinated > address space to make this work. Reasoning by analogy with the phone syste > m > is a powerful argument. People change phone numbers all the time, they > don't absolutely revolt because the phone system is so valuable. > Some elect to get 700 numbers, but they *PAY* for this service. > > We suggest the following subjects be carefully considered: > > The old addresses of the research Internet need to be reorganized > into the global public Internet addressing plan which is based > on CIDR. > > Those addresses not currently globally routed will not be > routed. These new customers of the Internet should get > their addresses from their immediate providers. > (This could be softened if there is a commitment by the > customer to enter into the transition ASAP). This also > would cover the case of provider switching under CIDR. > > Those addresses that are currently routed will *eventually* > be migrated to CIDR allocations. This may take some time, > on the order of years (2-5). We could look for the > simple cases first (small/tiny sites). > > It is not fair to get people to renumber when they attach to > the Internet when they see that people already attached > are just sitting pretty. We need to be consistent in the > application of standards and rules. > > Marty has brought up the subject of a carrot: > > The carrot is getting global Internet routing. > > The stick is not getting global Internet routing. > > It is a dull and boring argument, but it is the core of the debate. > There is extreme value in what we are trying to build with the global publi > c > Internet, and we need to impress on the customer base that we need > their help to make it possible to achieve our goals. > > We are not saying this is going to be easy, but it is rare that something > worth having comes for free. > > Peter & Yakov > > P.S. The number of uncoordinated IP addresses is higher than 30K. > - - - - - - - - - - - - - - - - - From list-admin Sat Apr 16 09:02:02 1994 Received: from ncc.ripe.net (ncc.ripe.net [192.87.45.2]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id JAA06585; Sat, 16 Apr 1994 09:02:01 -0400 Received: from mellow.ripe.net by ncc.ripe.net with SMTP id AA07514 (5.65a/NCC-2.2); Sat, 16 Apr 1994 15:02:00 +0200 Received: from localhost.ripe.net by mellow.ripe.net with SMTP id AA05242 (5.65a/NCC-2.1); Sat, 16 Apr 1994 15:01:59 +0200 Message-Id: <9404161301.AA05242@mellow.ripe.net> To: John Curran Cc: bgpd@merit.edu, regional-techs@merit.edu Subject: Re: 20402 routing entries (renumbering) In-Reply-To: Your message of Fri, 15 Apr 1994 21:02:36 EDT. <9404152103.aa25053@nic.near.net> From: Daniel Karrenberg X-Organization: RIPE Network Coordination Centre X-Phone: +31 20 592 5065 Date: Sat, 16 Apr 1994 15:01:59 +0200 Sender: Daniel.Karrenberg@ripe.net > John Curran writes: > ... At some point > or another, the cost of route entry propagation will be identified and > some enterprising soul will turn a "problem" into a business opportunity > by actually recovering these costs seperately. Yes, it will be messy, > and providers will begin handling routing (not traffic) settlements, > but if the cost component of routing gets high enough, then it's quite > likely to emerge as a separate item. > > ... Will a fortune 500 company be concerned about the extra > [wild estimate] $250/month to keep their dozen distinct CIDR entries? > Perhaps not, they may even consider it a good investment compared to > renumbering when they change providers. Would the local bookstore > renumber both their hosts (when changing providers) in order to avoid > $20/month? Maybe. > ... RIGHT ON ! - - - - - - - - - - - - - - - - - From list-admin Sat Apr 16 11:37:15 1994 Received: from ncc.ripe.net (ncc.ripe.net [192.87.45.2]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id LAA13647; Sat, 16 Apr 1994 11:37:14 -0400 Received: from belegen.ripe.net by ncc.ripe.net with SMTP id AA08066 (5.65a/NCC-2.2); Sat, 16 Apr 1994 17:35:55 +0200 Received: from localhost.ripe.net by belegen.ripe.net with SMTP id AA27899 (5.65a/NCC-2.2); Sat, 16 Apr 1994 17:35:54 +0200 Message-Id: <9404161535.AA27899@belegen.ripe.net> To: Walt Haas Cc: "Martin Lee Schoffstall" , Dennis Ferguson , "Peter S. Ford" , yakov@watson.ibm.com, bgpd@merit.edu, regional-techs@merit.edu, fedor@us.psi.com From: Geert Jan de Groot X-Organization: RIPE Network Coordination Centre X-Phone: +31 20 592 5065 Subject: Re: 20402 routing entries In-Reply-To: Your message of "Fri, 15 Apr 1994 16:50:26 MDT." <199404152250.QAA11758@ski.utah.edu> Date: Sat, 16 Apr 1994 17:35:51 +0200 Sender: GeertJan.deGroot@ripe.net On Fri, 15 Apr 94 16:50:26 MDT Walt Haas wrote: > It seems to me that this entire discussion is based on the premise that > renumbering is extremely slow, difficult, expensive and disruptive. > > This belief is probably justified given current technology. Our Chemistry > department reported that they renumbered 20 workstations, and it was a > week before anybody involved got any useful work done. One shudders to > think what this means if extrapolated to the global Internet. > > However, if we could develop a technology which could make renumbering > of a network (ie. a company, university or similar-sized unit) fast and > efficient, this premise would break down and it would no longer be unreasonab le > to consider renumbering the organization when switching providers. I don't believe that renumbering should be this painful, *if done right*. In a previous occupation, I managed a network of about 150 machines of various types and kinds. It was intentionally set up in such a way that network configuration information (IP addresses, netmasks, default routes etc) was concentrated on one machine and other config info was built from that automagically (using machine-built config files, RARP, bootp, rdist and the like). I have done a number of splits, moves, merges and the like and found that, if the network is managed this way, renumbering doesn't have to be painful at all. The last big action (merging three parts that were split one year beforehand), took only two hours. The key to this is realizing that this might happen one day and planning for it. Basically, preparing new master config files and typing 'make' should do 90% of the work. It also does involve doing things *different* than most manufacturers want: instead of typing in the (fixed) IP address the first time a shiny new box boots, think how you can make (re-)configuration automatic. As an added bonus, you can use the same mechanism to distribute patches, new security measures and the like. I know of similar mechanisms at some other places. Like me, they have done some re-designs of their network over time. It can be done. Geert Jan - - - - - - - - - - - - - - - - - From list-admin Sat Apr 16 14:38:03 1994 Received: from ski.utah.edu (ski.utah.edu [128.110.124.10]) by merit.edu (8.6.8.1/merit-1.0) with ESMTP id OAA22757; Sat, 16 Apr 1994 14:38:02 -0400 Received: (from haas@localhost) by ski.utah.edu (8.6.8/8.6.8.UUCC-C) id MAA00382; Sat, 16 Apr 1994 12:48:52 -0600 From: Walt Haas Message-Id: <199404161848.MAA00382@ski.utah.edu> Date: Sat, 16 Apr 94 12:48:51 MDT Subject: a modest proposal To: bgpd@merit.edu, regional-techs@merit.edu The idea below seemed to make sense last night after a couple of margaritas at the Rio Grande Cafe, let's see if anybody else thinks it will fly. If this isn't the right place to discuss it let me know, I will forward it appropriately. -- Walt ======= PROPOSAL FOR A NEW NAME/ADDRESS PARADIGM FOR THE INTERNET April 16, 1994 Walter O. Haas University of Utah Salt Lake City, UT 84112 1. Internet names are the property of the user, not the network service provider. An Internet name has much the same legal status as a registered trademark, and is suited to appear in advertising and other literature completely independently of the Internet service provider currently employed by the user. Internet names will be issued by a central authority directly to the user. Optionally, a network service provider may handle the necessary paperwork for a user to obtain a name, but this does not give the said provider any right or interest in the name issued and the provider must not attempt to mislead the user to the effect that it has such a right. 2. Internet addresses consist of a and a . The belongs to the Internet service provider, and is used by Internet routers to switch traffic to agreed points of that service provider's network. The belongs to the customer. A complete Internet address is of the form .. If the customer decides to obtain services from a different provider, the customer shall adopt addresses using the of the desired provider. It shall be possible for a customer host to be multi-homed to two addresses with different , either temporarily or permanently. The consists of two areas: a which identifies the organization providing service, followed by a part which tells that provider's network how to route to the customer network. Thus a complete Internet address can be specified as .. Providers are assigned a by a global authority, but may choose their part according to their internal criteria, which may include (but are not limited to) technology, geography, business plan, and perceived customer desires. All providers are required to forward traffic to any of the globally-defined values, but are not required to process any portion of the Internet address beyond that (except their own). There shall however be a defined upper limit on the size of the and . 3. Each user host shall be configured with its Internet name. Upon booting, the host shall send a Name-to-Address Request (NARQ) packet to a defined broadcast address. The NARQ packet will contain the host's name. A server will respond with a Name-to-Address Reply (NARP) packet containing the Internet address of that host. 4. If the customer decides to change Internet service providers, it will need to assign a new corresponding to the new Internet address of the new service provider to each host. This will be done by giving the new to the customer's nameserver, which will then send appropriate NARP packets to the relevant network hosts which will then each have two Internet addresses. This operation obviously needs appropriate security. When the customer's network has acquired the new set of addresses and the old service provider is no longer in use, then the customer's nameserver can send an appropriate Name-to-Address Invalid (NANA) packet to each host to invalidate that address from its configuration. This operation also needs to be secure. ------- - - - - - - - - - - - - - - - - - From list-admin Sat Apr 16 16:45:14 1994 Received: from localhost (jyy@localhost) by merit.edu (8.6.8.1/merit-1.0) with SMTP id QAA29496; Sat, 16 Apr 1994 16:45:13 -0400 Message-Id: <199404162045.QAA29496@merit.edu> To: schoff@us.psi.com cc: bgpd@merit.edu, regional-techs@merit.edu, hoodr@netcom.com, jyy@merit.edu Subject: Re: 20402 routing entries Date: Sat, 16 Apr 1994 16:45:13 -0400 From: Jessica Yu Date: Fri, 15 Apr 1994 16:02:57 -0400 From: "Martin Lee Schoffstall" And is only downside is that anyone not doing BGP4 he won't be able to talk to at all. If an AS does not do BGP4 but defaults to a CIDR capable AS, he can still reach it. Only the ASs which does neigher BGP4 nor default will have problem. Maybe you could help him a little bit and tell him who that might be. About 1000 more specific routes have been withdrawn from the Internet during the past two weeks. Have not heard any complain yet. If you know anyone who does neigher CIDR nor default and therefore will have reachability problem when specific routes withdrawn,please let us know. --Jessica - - - - - - - - - - - - - - - - - From list-admin Sun Apr 17 19:20:52 1994 Received: from totalrecall.rs.itd.umich.edu (totalrecall.rs.itd.umich.edu [35.1.1.91]) by merit.edu (8.6.8.1/merit-1.0) with ESMTP id TAA15830; Sun, 17 Apr 1994 19:20:51 -0400 From: Jeff.Ogden@um.cc.umich.edu Received: from um.cc.umich.edu by totalrecall.rs.itd.umich.edu (8.6.7/2.2) with SMTP id TAA07393; Sun, 17 Apr 1994 19:20:46 -0400 Date: Sun, 17 Apr 94 19:20:50 EDT To: haas@ski.utah.edu, GeertJan.deGroot@ripe.net Cc: schoff@us.psi.com, dennis@ans.net, peter@goshawk.lanl.gov, yakov@watson.ibm.com, bgpd@merit.edu, regional-techs@merit.edu, fedor@us.psi.com Message-ID: <34269271@um.cc.umich.edu> X-MTS-Userid: W163 Subject: Re: 20402 routing entries About three years ago we renumbered all of the state Universities in Michigan (except Michigan State U). It was a lot of work and I wouldn't want to do it very often, but the whole business went much better than I expected. The key is good planning. Another key is getting people to use domain names rather than IP addresses whenever possible. We had signs up saying "Names good, numbers bad!". -Jeff Ogden Merit/MichNet - - - - - - - - - - - - - - - - - From list-admin Sun Apr 17 22:22:35 1994 Received: from Sun.COM (Sun.COM [192.9.9.1]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id WAA24382; Sun, 17 Apr 1994 22:22:35 -0400 Received: from Eng.Sun.COM (zigzag.Eng.Sun.COM) by Sun.COM (sun-barr.Sun.COM) id AA17768; Sun, 17 Apr 94 19:22:31 PDT Received: from jurassic.Eng.Sun.COM (jurassic-248) by Eng.Sun.COM (4.1/SMI-4.1) id AA00978; Sun, 17 Apr 94 19:21:44 PDT Received: by jurassic.Eng.Sun.COM (5.x/SMI-SVR4) id AA28040; Sun, 17 Apr 1994 19:22:24 -0700 Date: Sun, 17 Apr 1994 19:22:24 -0700 From: Bob.Hinden@Eng.Sun.COM (Bob Hinden) Message-Id: <9404180222.AA28040@jurassic.Eng.Sun.COM> To: "Peter S. Ford" Cc: "Martin Lee Schoffstall" , bgpd@merit.edu, regional-techs@merit.edu In-Reply-To: <199404151918.NAA24007@goshawk.lanl.gov> Subject: Re: 20402 routing entries Peter, > When people got network numbers in the past they were getting addresses > for the research Internet. It is important to understand that the > research Internet was a great thing, but we are now working on the > global public Internet and we desperately needed new routing and addressing > systems. We should establish that we are in a transition from the > research Internet to the global public Internet and we subsequently I don't think this will fly. I was around when we had a "research internet". I even had two class A addresses assigned to me [yes, I know I should have kept them :-) ]. I think that was quite a while ago and does not apply to the majority of internet sites today. Certainly not for all of the sites labeled as commercial under the AUP. > address space to make this work. Reasoning by analogy with the phone system > is a powerful argument. People change phone numbers all the time, they > don't absolutely revolt because the phone system is so valuable. The phone number analogy does not apply here. When you phone number changes (and in most cases today it is only the area code, not the local number) the telephone still works. This is not the case for computers and routers. They break. Some hosts may not even boot. When the phone number changes and someone dials the old number the user gets a recording with the new number to dial. We have not built the current internet to do anything like this. Bob - - - - - - - - - - - - - - - - - From list-admin Mon Apr 18 09:31:25 1994 Received: from vax3.sara.nl (vax3.sara.nl [192.16.188.187]) by merit.edu (8.6.8.1/merit-1.0) with ESMTP id JAA16045; Mon, 18 Apr 1994 09:31:24 -0400 Received: from horus.sara.nl by SARA.NL (PMDF V4.2-15 #2498) id <01HBBQ3J7CUO8Y8AN3@SARA.NL>; Mon, 18 Apr 1994 15:31:00 +0200 (MET-DST) Received: from localhost.sara.nl by horus.sara.nl (AIX 3.2/UCB 5.64/4.03) id AA28458; Mon, 18 Apr 1994 15:30:54 +0200 Date: Mon, 18 Apr 1994 15:30:53 +0200 From: Willem van der Scheun Subject: Re: CIDR testing In-reply-to: Your message of Fri, 15 Apr 1994 14:34:02 MET DST. <199404151836.OAA29110@merit.edu> To: yakov@watson.ibm.com Cc: Havard.Eidnes@runit.sintef.no, bgpd@merit.edu, regional-techs@merit.edu Message-id: <9404181330.AA28458@horus.sara.nl> X-Envelope-to: bgpd@merit.edu, regional-techs@merit.edu Content-transfer-encoding: 7BIT > > >What this means is that I think it's fairly safe to say that there > >will be no connectivity problems when you pull the specific routes. > > I guess we can declare the as of April 15, 1994 the Internet "guts" have > been adequately CIDRized :-) > Meaning there is no reason whatsoever to not advertize big blocks and remove the explicit ones. Since SURFnet withdrew all explicit routes possible and started announcing as big blocks as possible (i.e including black holes) we did not get any complaint. So: DO IT NOW! -- Willem - - - - - - - - - - - - - - - - - From list-admin Mon Apr 18 11:09:49 1994 Received: from interlock.ans.net (interlock.ans.net [147.225.1.3]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id LAA23199; Mon, 18 Apr 1994 11:09:47 -0400 Received: by interlock.ans.net id AA33112 (InterLock SMTP Gateway 1.1); Mon, 18 Apr 1994 11:04:45 -0400 Received: by interlock.ans.net (Internal Mail Agent-2); Mon, 18 Apr 1994 11:04:45 -0400 Received: by interlock.ans.net (Internal Mail Agent-1); Mon, 18 Apr 1994 11:04:45 -0400 From: Curtis Villamizar Message-Id: <199404181501.AA59610@foo.ans.net> To: Walt Haas Cc: bgpd@merit.edu, regional-techs@merit.edu, curtis@ans.net Subject: Re: a modest proposal In-Reply-To: (Your message of Sat, 16 Apr 94 12:48:51 MST.) <199404161848.MAA00382@ski.utah.edu> Date: Mon, 18 Apr 94 11:01:41 -0500 > PROPOSAL FOR A NEW NAME/ADDRESS PARADIGM FOR THE INTERNET This sort of idea has been proposed. In essence, the NIC would inform the customer that they don't own their address. Efforts to do so by individual providers have been legally challenged. > A complete Internet address is of the form .. > If the customer decides to obtain services from a different provider, > the customer shall adopt addresses using the of the > desired provider. It shall be possible for a customer host to be > multi-homed to two addresses with different , either > temporarily or permanently. You don't need a second set of addresses to have a backup provider and you don't want them. If your primary provider loses connectivity to you, the DNS mapping is still to the same set of numbers, it just gets routed a different way. A second set of numbers doesn't help. > name. A server will respond with a Name-to-Address Reply (NARP) > packet containing the Internet address of that host. Acronym overload: NARP is NBMA Address Resolution Protocol. NBMA is Non-Broadcast Multiple Access. The mechanisms you describe for acquiring and disposing of address mappings differ from DHCP (Dynamic Host Configuration Protocol). The cutover can be executed by configuring the hosts with aliases (two sets of addresses for their interfaces) changing the DNS mappings while both addresses are available and then quitely removing the first set of addresses. (Except I don't think DHCP can do aliases). Nice ideas. Needs a few more margaritas. ;-) Curtis - - - - - - - - - - - - - - - - - From list-admin Mon Apr 18 12:29:43 1994 Received: from psi.com (psi.com [192.67.6.2]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id MAA29438; Mon, 18 Apr 1994 12:29:36 -0400 Received: from us.psi.com by psi.com (4.1/2.1-PSI/PSINet) id AA07174; Mon, 18 Apr 94 12:29:03 EDT Received: by us.psi.com (4.1/SMI-4.1.3-PSI-pop) id AA11750; Mon, 18 Apr 94 12:29:09 EDT Message-Id: <9404181629.AA11750@us.psi.com> To: "Peter S. Ford" Cc: yakov@watson.ibm.com, bgpd@merit.edu, regional-techs@merit.edu, fedor@us.psi.com Subject: Re: 20402 routing entries In-Reply-To: Your message of "Fri, 15 Apr 1994 16:36:19 MST." <199404152236.QAA28747@goshawk.lanl.gov> Date: Mon, 18 Apr 1994 12:29:02 -0400 From: "Martin Lee Schoffstall" > What fraction of Internet users know their DNS names better than they > know their IP addresses? What number of people know my email > address vrs the number who know my IP address? I bet more users > know more URLs than IP addresses. I didn't make my point clear. You are talking about individual users. I'm talking about the decision makers and operators of the networks at individual institutions. They are not going to be easily sold on renumbering or non-portable network numbers. They are going to have to be incented. Marty - - - - - - - - - - - - - - - - - From list-admin Mon Apr 18 12:35:28 1994 Received: from psi.com (psi.com [192.67.6.2]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id MAA00203; Mon, 18 Apr 1994 12:35:26 -0400 Received: from us.psi.com by psi.com (4.1/2.1-PSI/PSINet) id AA07314; Mon, 18 Apr 94 12:34:46 EDT Received: by us.psi.com (4.1/SMI-4.1.3-PSI-pop) id AA11994; Mon, 18 Apr 94 12:34:52 EDT Message-Id: <9404181634.AA11994@us.psi.com> To: bmanning@is.rice.edu (William Manning) Cc: yakov@watson.ibm.com, bgpd@merit.edu, regional-techs@merit.edu Subject: Re: 20402 routing entries In-Reply-To: Your message of "Fri, 15 Apr 1994 17:57:58 CDT." <9404152257.AA02367@brazos.is.rice.edu> Date: Mon, 18 Apr 1994 12:34:51 -0400 From: "Martin Lee Schoffstall" think land patents People bought them for $5, and mined $12Billion worth of gold out of them. I can't remember who the person was that bought all the US oil lands in the 19th century for next to nothing because while the oil was known to exist (there) technology did not exist for pumping it from 150 feet. Four years later they had the technology. What you paid vs what they are worth (especially in the future) are not necessarily closely bound. Marty > Martin Lee Schoffstall sez: > > > > Hint, think about buying back network numbers. > > > > Just how much did you pay for -your- network numbers? > How much are they worth to you? I just might be willing > to take you up on your most generous offer. > > -- > Regards, > Bill Manning - - - - - - - - - - - - - - - - - From list-admin Mon Apr 18 11:47:38 1994 Received: from office.EU.net (office.EU.net [192.16.202.23]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id LAA26339; Mon, 18 Apr 1994 11:47:37 -0400 Received: from smakelijk.EU.net by office.EU.net with SMTP id AA23618 (5.67a/IDA-1.5); Mon, 18 Apr 1994 17:47:14 +0200 Received: by smakelijk.EU.net id AA10666 (930416.SGI/IDA-1.5); Mon, 18 Apr 94 17:49:08 +0200 Date: Mon, 18 Apr 94 17:49:08 +0200 Message-Id: <9404181549.AA10666@smakelijk.EU.net> From: Petri Ojala To: Willem van der Scheun Cc: bgpd@merit.edu, regional-techs@merit.edu Subject: Re: CIDR testing In-Reply-To: <9404181330.AA28458@horus.sara.nl> References: <199404151836.OAA29110@merit.edu> <9404181330.AA28458@horus.sara.nl> > Meaning there is no reason whatsoever to not advertize big blocks and > remove the explicit ones. Since SURFnet withdrew all explicit routes > possible and started announcing as big blocks as possible (i.e including > black holes) we did not get any complaint. So: DO IT NOW! I back this up with EUnet's favourite slogan, "it works for EUnet, just do it!" EUnet has been announcing several /16 or other aggregates for sometime now and there hasn't been a single complaint, and yet we are talking about several hundreds of networks and practically the commercial internet in a few European countries. Petri - - - - - - - - - - - - - - - - - From list-admin Mon Apr 18 16:26:32 1994 Received: from pepper.merit.edu (pepper.merit.edu [35.42.1.50]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id QAA21741; Mon, 18 Apr 1994 16:26:31 -0400 Received: by pepper.merit.edu (4.1/client-0.9) id AA07074; Mon, 18 Apr 94 16:26:30 EDT Date: Mon, 18 Apr 94 16:26:30 EDT From: epg@merit.edu Message-Id: <9404182026.AA07074@pepper.merit.edu> To: bgpd@merit.edu, db-wg@ripe.net, regional-techs@merit.edu, routing-wg@ripe.net Subject: Merit Routing Registry Merit is happy to announce the Merit Routing Registry. Whereas Merit designed and manages the PRDB (Policy Routing Data Base) for the NSFNET service, RIPE pioneered a policy routing registry for the European community. The RIPE Routing Registry is based on the document, RIPE-81. With RIPE's collaboration, Merit installed RIPE-81 software and then extended the policy descriptions in order to realize more complex policies. The Merit Routing Registry will be a companion registry to the RIPE Routing Registry and is intended to serve the community that is not served by RIPE. This is a new service and we consider ourselves still in the beta phase. Registrations may be basic policy descriptions defined in RIPE-81 or complex routing policy descriptions defined in the Extended Policy Syntax document by Chen, Gerich, Joncheray, and Yu. The Extended Policy Syntax document may be found on rrdb.merit.edu:pub/meritrr/policy_syntax.txt. Documentation for using the MeritRR can be found on rrdb.merit.edu:pub/meritrr. Merit and RIPE anticipate that the combined registries will provide a more comprehensive picture of the routing interactions in the Internet. We are working together to allow the two registries to appear like one virtual registry to the various tools that are developed. We welcome your comments on all aspects of this project. For more information, please respond to rradmin@rrdb.merit.edu. Elise Gerich, Merit Network, Inc. Daniel Karrenberg, RIPE NCC - - - - - - - - - - - - - - - - - From list-admin Tue Apr 19 05:58:41 1994 Received: (skw@localhost) by merit.edu (8.6.8.1/merit-1.0) id FAA18726 for nwg; Tue, 19 Apr 1994 05:58:41 -0400 Date: Tue, 19 Apr 1994 05:58:41 -0400 From: "Steven K. Widmayer" Message-Id: <199404190958.FAA18726@merit.edu> To: nwg Subject: Additions to the NSFNET policy-based routing database ------------------------------------------------------------------------------ CIDR Progress Report: 1044 Nets, 24 ASs, 115 Aggregates. Details below. New format for Metric:AS lists coming later in this and all reports. See 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 Configured Networks 29856 = 29 4635 25020 172 Added Networks 212 = 0 6 149 57 Deleted Networks 152 = 0 1 151 0 IP address Net name Country Priority:AS ---------- -------- ------- ----------- 128.178/15 EPNET C:CH 1:1133 2:1674 3:1800 129.194/15 SWITCH-AGGR.1 C:CH 1:1133 2:1674 3:1800 131.89/16 PGE-BNET C:US 1:2149 2:174 142.111/16 SSCNET-CA C:CA 1:601 2:603 3:602 142.129/16 SSCNET1-CA C:CA 1:601 2:603 3:602 147.86/15 SWITCH-AGGR.2 C:CH 1:1133 2:1674 3:1800 149.143/16 NET-MVNC C:US 1:600 2:1800 158.223/16 GOLD C:GB 1:1800 2:1133 3:1240 165.215/16 BH-COM C:US 1:1325 192.16.124/22 IMIKTH-CIDR C:SE 1:1800 2:1879 3:1133 4:1240 192.33.216/22 C-216 C:CH 1:1133 2:1674 3:1800 192.50.66/24 MARINE2 C:JP 1:1240 2:1800 192.50.67/24 MARINE2 C:JP 1:1240 2:1800 192.50.68/24 MARINE2 C:JP 1:1240 2:1800 192.91.242/23 CERN-CNET29 C:CH 1:1133 2:1800 3:1240 192.132.235/24 MCHV-235 C:US 1:560 2:701 192.132.236/24 MCHV-236 C:US 1:560 2:701 192.132.237/24 MCHV-237 C:US 1:560 2:701 192.135.240/21 CISCO-FLD2 C:US 1:200 2:201 192.153.42/23 NETCOM1 C:US 1:2551 192.153.44/22 NET-FCS C:US 1:2551 192.153.48/21 NETCOM7 C:US 1:2551 192.187.128/17 NETCOM31 C:US 1:2551 192.197.251/24 MSHRI-NET1 C:CA 1:601 2:603 3:602 192.206.82/23 DESKTOPDATA C:US 1:2551 192.206.84/23 DESKTOPDATA3 C:US 1:2551 192.215.126/23 NATUNIV27 C:US 1:2551 192.215.128/22 NATUNIV29 C:US 1:2551 192.217.209/24 CICNET-C-217-209 C:US 1:1225 2:267 3:266 192.217.210/24 CICNET-C-217-210 C:US 1:1225 2:267 3:266 192.217.211/24 CICNET-C-217-211 C:US 1:1225 2:267 3:266 192.217.215/24 CICNET-C-217-215 C:US 1:1225 2:267 3:266 192.217.216/24 CICNET-C-217-216 C:US 1:1225 2:267 3:266 192.217.217/24 CICNET-C-217-217 C:US 1:1225 2:267 3:266 192.235.32/20 AXIL1 C:US 1:2551 192.235.48/22 AXIL17 C:US 1:2551 192.240.32/24 MCHV-32 C:US 1:560 2:701 192.240.33/24 MCHV-33 C:US 1:560 2:701 192.240.34/24 MCHV-34 C:US 1:560 2:701 192.240.35/24 MCHV-35 C:US 1:560 2:701 192.240.36/24 MCHV-36 C:US 1:560 2:701 192.240.37/24 MCHV-37 C:US 1:560 2:701 192.240.38/24 MCHV-38 C:US 1:560 2:701 192.240.39/24 MCHV-39 C:US 1:560 2:701 192.240.40/24 MCHV-40 C:US 1:560 2:701 192.240.41/24 MCHV-41 C:US 1:560 2:701 192.240.42/24 MCHV-42 C:US 1:560 2:701 192.240.43/24 MCHV-43 C:US 1:560 2:701 192.240.44/24 MCHV-44 C:US 1:560 2:701 192.240.45/24 MCHV-45 C:US 1:560 2:701 192.240.46/24 MCHV-46 C:US 1:560 2:701 192.245.82/23 AGAMES-1 C:US 1:2551 192.245.84/23 AGAMES-3 C:US 1:2551 192.247.16/21 RWBECK-16 C:US 1:2551 192.247.24/22 RWBECK-24 C:US 1:2551 193.5/16 SWITCH-AGGR.3 C:CH 1:1133 2:1674 3:1800 193.5.26/23 LIS-VADUZ C:LI 1:1133 2:1674 3:1800 193.5.44/23 CERBERUS C:CH 1:1133 2:1674 3:1800 193.5.70/23 CNCS C:CH 1:1133 2:1674 3:1800 193.5.80/21 ISBE-SWS-NET1 C:CH 1:1133 2:1674 3:1800 193.5.152/22 STS C:CH 1:1133 2:1674 3:1800 193.5.156/22 XMIT2 C:CH 1:1133 2:1674 3:1800 193.5.160/21 CIMNET C:CH 1:1133 2:1674 3:1800 193.5.168/22 ISBURG2 C:CH 1:1133 2:1674 3:1800 193.5.224/20 VPTT C:CH 1:1133 2:1674 3:1800 193.22.64/24 BIB-LAN-C-22-64 C:DE 1:1324 2:1800 3:1240 4:1133 193.22.65/24 BIB-LAN-C-22-65 C:DE 1:1324 2:1800 3:1240 4:1133 193.22.66/24 BIB-LAN-C-22-66 C:DE 1:1324 2:1800 3:1240 4:1133 193.22.67/24 BIB-LAN-C-22-67 C:DE 1:1324 2:1800 3:1240 4:1133 193.22.68/24 BIB-LAN-C-22-68 C:DE 1:1324 2:1800 3:1240 4:1133 193.22.69/24 BIB-LAN-C-22-69 C:DE 1:1324 2:1800 3:1240 4:1133 193.22.70/24 BIB-LAN-C-22-70 C:DE 1:1324 2:1800 3:1240 4:1133 193.22.71/24 BIB-LAN-C-22-71 C:DE 1:1324 2:1800 3:1240 4:1133 193.22.72/24 BIB-LAN-C-22-72 C:DE 1:1324 2:1800 3:1240 4:1133 193.22.73/24 BIB-LAN-C-22-73 C:DE 1:1324 2:1800 3:1240 4:1133 193.22.74/24 BIB-LAN-C-22-74 C:DE 1:1324 2:1800 3:1240 4:1133 193.22.75/24 BIB-LAN-C-22-75 C:DE 1:1324 2:1800 3:1240 4:1133 193.22.76/24 BIB-LAN-C-22-76 C:DE 1:1324 2:1800 3:1240 4:1133 193.22.77/24 BIB-LAN-C-22-77 C:DE 1:1324 2:1800 3:1240 4:1133 193.22.78/24 BIB-LAN-C-22-78 C:DE 1:1324 2:1800 3:1240 4:1133 193.22.79/24 BIB-LAN-C-22-79 C:DE 1:1324 2:1800 3:1240 4:1133 193.88/15 EUNET-DK-193.88-AGG C:DK 1:701 2:1800 193.104.15/24 FR-BRIDGEWAY C:FR 1:701 2:1800 193.120.202/24 ALD-CONNECT C:IE 1:701 2:1800 193.120.205/24 ALD C:IE 1:701 2:1800 193.134/16 SWITCH-AGGR.4 C:CH 1:1133 2:1674 3:1800 193.134.200/21 WSLNET C:CH 1:1133 2:1674 3:1800 193.134.208/21 SERONET C:CH 1:1133 2:1674 3:1800 193.141/16 XLINK_BLOCK_193.141.0 C:DE 1:1324 2:1800 3:1240 4:1133 193.141.139/24 ROKANET4 C:DE 1:1324 2:1800 3:1240 4:1133 193.144/15 REDIRIS-PROVIDER C:ES 1:1800 2:1133 3:1674 4:1240 193.172.2/23 EMPB C:NL 1:1800 2:1133 3:1674 4:1240 193.204.118/24 CRES-IPNET-2 C:IT 1:293 2:291 3:1133 4:1674 5:1800 193.208.149/24 SGO-NET C:FI 1:1800 2:1879 3:1133 4:1240 193.232.22/24 BABAKIN-LAN C:RU 1:297 2:372 193.232.24/24 NPOE-LAN C:RU 1:297 2:372 198.6.198/24 FC1 C:US 1:701 2:702 198.60.72/24 WESTNET C:US 1:210 2:209 198.60.73/24 WESTNET C:US 1:210 2:209 198.62.156/23 CFER-NET1 C:US 1:2551 198.67.0/17 SL-EAST-AGGR C:US 1:1800 2:1240 198.67.128/17 ICM-EAST-AGGR C:US 1:1800 198.68/16 SPRINT-WEST2 C:US 1:1240 2:1800 198.71.16/21 MFI C:US 1:2551 198.71.24/22 MFI9 C:US 1:2551 198.77.88/24 VA-MCI-NET-C-77-88 C:US 1:86 2:279 198.77.89/24 VA-MCI-NET-C-77-89 C:US 1:86 2:279 198.77.90/24 VA-MCI-NET-C-77-90 C:US 1:86 2:279 198.77.91/24 VA-MCI-NET-C-77-91 C:US 1:86 2:279 198.77.92/24 VA-MCI-NET-C-77-92 C:US 1:86 2:279 198.77.93/24 VA-MCI-NET-C-77-93 C:US 1:86 2:279 198.77.94/24 VA-MCI-NET-C-77-94 C:US 1:86 2:279 198.77.95/24 VA-MCI-NET-C-77-95 C:US 1:86 2:279 198.78.247/24 KNXCOLL-NET C:US 1:279 2:86 198.81.224/24 MK-SHARED C:US 1:1331 198.85.108/24 FHI C:US 1:1329 198.85.109/24 QESOFT-NET C:US 1:1329 198.86.76/24 LENOIRCC1 C:US 1:1329 198.87.250/24 CICNET-2 C:US 1:266 2:267 3:1225 198.108/14 NETBLK-MICHNET198 C:US 1:237 2:233 3:266 4:267 5:1225 198.108.0/22 NETBLK-MICHNET198 C:US 1:237 2:233 3:266 4:267 5:1225 198.108.80/24 NETBLK-ADRIAN C:US 1:237 2:233 3:266 4:267 5:1225 198.108.81/24 NETBLK-ADRIAN C:US 1:237 2:233 3:266 4:267 5:1225 198.108.82/24 NETBLK-ADRIAN C:US 1:237 2:233 3:266 4:267 5:1225 198.108.83/24 NETBLK-ADRIAN C:US 1:237 2:233 3:266 4:267 5:1225 198.108.84/24 NETBLK-ADRIAN C:US 1:237 2:233 3:266 4:267 5:1225 198.108.85/24 NETBLK-ADRIAN C:US 1:237 2:233 3:266 4:267 5:1225 198.108.86/24 NETBLK-ADRIAN C:US 1:237 2:233 3:266 4:267 5:1225 198.108.87/24 NETBLK-ADRIAN C:US 1:237 2:233 3:266 4:267 5:1225 198.116.18/24 NSI C:US 1:297 2:372 198.116.19/24 NSI C:US 1:297 2:372 198.162.87/24 SEAWEST-SEACHG-COM C:CA 1:602 2:601 3:603 198.182.250/24 CTIMAGENET C:US 1:1800 2:1240 198.183.206/23 LAMBDA-C-183-206 C:US 1:2551 198.183.208/23 LAMBDA-C-183-208 C:US 1:2551 198.185.168/24 MABON6 C:US 1:2149 2:174 198.185.169/24 MABON7 C:US 1:2149 2:174 198.185.170/24 MABON8 C:US 1:2149 2:174 198.185.171/24 MABON9 C:US 1:2149 2:174 198.185.172/24 MABON10 C:US 1:2149 2:174 198.188.246/24 CSUNET-SOUTH-C-188-24 C:US 1:2150 2:200 3:201 198.188.247/24 CSUNET-SOUTH-C-188-24 C:US 1:2150 2:200 3:201 198.211/16 NETBLK-NETCOM-CBLK C:US 1:2551 198.247.236/24 BOYSTOWN C:US 1:93 198.247.237/24 BOYSTOWN C:US 1:93 198.247.238/24 BOYSTOWN C:US 1:93 198.247.239/24 BOYSTOWN C:US 1:93 199.3.26/24 SPRINTGSD C:US 1:1240 2:1800 199.6.32/20 IAC-CBLK1 C:US 1:2548 199.10.243/24 MED-NET-1 C:US 1:19 2:568 199.11/16 MRN-BLK1 C:US 1:1800 2:1240 199.14/16 MRN-BLK4 C:US 1:1800 2:1240 199.45.128/17 NETBLK-COOP-NET C:US 1:1240 2:1800 199.60.1/24 SFUCSS C:CA 1:602 2:601 3:603 199.60.2/24 SFUCSS C:CA 1:602 2:601 3:603 199.60.3/24 SFUCSS C:CA 1:602 2:601 3:603 199.60.4/24 SFUCSS C:CA 1:602 2:601 3:603 199.60.5/24 SFUCSS C:CA 1:602 2:601 3:603 199.60.6/24 SFUCSS C:CA 1:602 2:601 3:603 199.60.7/24 SFUCSS C:CA 1:602 2:601 3:603 199.60.8/24 SFUCSS C:CA 1:602 2:601 3:603 199.60.9/24 SFUCSS C:CA 1:602 2:601 3:603 199.60.10/24 SFUCSS C:CA 1:602 2:601 3:603 199.60.11/24 SFUCSS C:CA 1:602 2:601 3:603 199.60.12/24 SFUCSS C:CA 1:602 2:601 3:603 199.60.13/24 SFUCSS C:CA 1:602 2:601 3:603 199.60.14/24 SFUCSS C:CA 1:602 2:601 3:603 199.60.15/24 SFUCSS C:CA 1:602 2:601 3:603 199.60.16/24 SFUCSS C:CA 1:602 2:601 3:603 199.60.17/24 SFUCSS C:CA 1:602 2:601 3:603 199.60.18/24 SFUCSS C:CA 1:602 2:601 3:603 199.67.10/23 ABEKAS-10 C:US 1:2551 199.67.12/22 ABEKAS-12 C:US 1:2551 199.72/16 INTERPATH-AGG C:US 1:1800 2:1240 199.88.64/18 MARIN-COUNTY C:US 1:1240 2:1800 199.88.179/24 SENSE-NET C:US 1:210 2:209 199.89.221/24 BEDGE C:US 1:1740 199.98.116/24 DSA C:US 1:2149 2:174 199.98.156/24 PSINET-C5 C:US 1:2149 2:174 199.98.157/24 PSINET-C5 C:US 1:2149 2:174 199.104.70/24 WESTNET-W2 C:US 1:210 2:209 199.117.22/24 CSN-BLK3 C:US 1:209 2:210 199.165.172/24 DSA C:US 1:2149 2:174 199.165.192/24 STEAM C:US 1:1800 199.170.56/24 NACM-NET C:US 1:701 2:702 199.170.57/24 NACM-NET C:US 1:701 2:702 199.170.58/24 NACM-NET C:US 1:701 2:702 199.170.59/24 NACM-NET C:US 1:701 2:702 199.170.60/24 NACM-NET C:US 1:701 2:702 199.170.61/24 NACM-NET C:US 1:701 2:702 199.170.62/24 NACM-NET C:US 1:701 2:702 199.170.63/24 NACM-NET C:US 1:701 2:702 199.170.71/24 JAXNET-NET C:US 1:701 2:702 199.170.77/24 UNIPALM-TS C:GB 1:701 2:702 199.175.7/24 MINDLINK3 C:CA 1:602 2:601 3:603 199.181.200/24 TELMAR-NET C:US 1:1800 2:1240 199.212.4/24 WHRI C:CA 1:601 2:603 3:602 202.25.112/24 NCT-NET C:JP 1:1240 2:1800 202.252.214/24 OKINAWA-NET C:JP 1:1240 2:1800 202.252.216/24 BCASJNET C:JP 1:1240 2:1800 202.252.217/24 BCASJNET C:JP 1:1240 2:1800 202.252.218/24 BCASJNET C:JP 1:1240 2:1800 202.252.219/24 BCASJNET C:JP 1:1240 2:1800 202.252.220/24 BCASJNET C:JP 1:1240 2:1800 202.252.221/24 BCASJNET C:JP 1:1240 2:1800 202.252.222/24 BCASJNET C:JP 1:1240 2:1800 202.252.223/24 BCASJNET C:JP 1:1240 2:1800 202.252.246/24 YACHIYONET C:JP 1:1240 2:1800 203.3.121/24 NET-UNIXPAC-AU C:AU 1:372 2:297 203.4.175/24 PIONEER-AU C:AU 1:372 2:297 203.4.181/24 FMSC-NET-AU C:AU 1:372 2:297 203.4.184/24 FERRO-MAG-NET-AU C:AU 1:372 2:297 Deletions: --145.13/16 GNS-MAIL C:NL 1:1957 --192.26.129/24 TAC-NET1 C:FI 1:701 2:1800 --192.26.130/24 TAC-NET2 C:FI 1:701 2:1800 --192.26.131/24 TAC-NET3 C:FI 1:701 2:1800 --192.26.132/24 TAC-NET4 C:FI 1:701 2:1800 --192.98.4/24 APUNET1 C:FI 1:701 2:1800 --192.98.5/24 APUNET2 C:FI 1:701 2:1800 --192.98.34/24 APUNET3 C:FI 1:701 2:1800 --192.129.50/24 CLS-NET C:DE 1:1324 2:1800 3:1240 4:1133 --192.138.240/24 TAMU-3 C:US 1:114 --192.138.241/24 TAMU-4 C:US 1:114 --192.138.244/24 TAMU-7 C:US 1:114 --192.195.86/24 TAMU-19 C:US 1:114 --192.195.87/24 TAMU-20 C:US 1:114 --192.195.88/24 TAMU-21 C:US 1:114 --192.195.90/24 TAMU-23 C:US 1:114 --192.195.91/24 TAMU-24 C:US 1:114 --192.195.92/24 TAMU-25 C:US 1:114 --192.195.95/24 TAMU-28 C:US 1:114 --192.215.72/24 CERFNET C:US 1:1957 --192.215.73/24 CERFNET C:US 1:1957 --192.215.74/24 CERFNET C:US 1:1957 --192.215.75/24 CERFNET C:US 1:1957 --192.215.76/24 CERFNET C:US 1:1957 --192.215.77/24 CERFNET C:US 1:1957 --192.215.78/24 CERFNET C:US 1:1957 --192.215.154/24 CERFNET C:US 1:1957 --192.215.155/24 CERFNET C:US 1:1957 --192.215.156/24 CERFNET C:US 1:1957 --192.215.157/24 CERFNET C:US 1:1957 --192.215.158/24 CERFNET C:US 1:1957 --192.215.253/24 CERFNET-C-215-253 C:US 1:1957 --192.215.254/24 CERFNET-C-215-254 C:US 1:1957 --192.216.0/24 NETBLK-BARRNET C:US 1:1957 --192.216.183/24 NETBLK-BARRNET C:US 1:1957 --193.64.184/24 APU5 C:FI 1:701 2:1800 --193.72.16/24 IFRC-C1 C:CH 1:1957 --193.72.48/24 UNICC-C1 C:CH 1:1957 --193.72.65/24 WAG-NET2 C:CH 1:1957 --193.72.66/24 WAG-NET3 C:CH 1:1957 --193.72.67/24 WAG-NET4 C:CH 1:1957 --193.72.81/24 OLSEN-C2 C:CH 1:1957 --193.72.82/24 OLSEN-C3 C:CH 1:1957 --193.72.83/24 OLSEN-C4 C:CH 1:1957 --193.72.84/24 OLSEN-C5 C:CH 1:1957 --193.72.85/24 OLSEN-C6 C:CH 1:1957 --193.72.86/24 OLSEN-C7 C:CH 1:1957 --193.72.87/24 OLSEN-C8 C:CH 1:1957 --193.72.128/24 VARNMR-CS C:CH 1:1957 --193.72.132/24 EM-1 C:CH 1:1957 --193.72.136/24 EUNET-CH-C4 C:CH 1:1957 --193.72.144/24 OLSEN-C1 C:CH 1:1957 --193.72.145/24 OLSEN-C2 C:CH 1:1957 --193.72.146/24 MATRIX-C-72-146 C:CH 1:1957 --193.72.147/24 MATRIX-C-72-147 C:CH 1:1957 --193.72.148/24 NEXOS-NET C:CH 1:1957 --193.72.152/24 RAG-C1 C:CH 1:1957 --193.72.153/24 RAG-C2 C:CH 1:1957 --193.72.156/24 ASPA-C1 C:CH 1:1957 --193.72.160/24 UNIP-C1 C:CH 1:1957 --193.72.161/24 UNIP-C2 C:CH 1:1957 --193.72.165/24 PROMINTEL-C2 C:CH 1:1957 --193.72.168/24 MZMZ-C1 C:CH 1:1957 --193.72.169/24 MZMZ-C2 C:CH 1:1957 --193.72.172/24 P3SYS-C1 C:CH 1:1957 --193.72.174/24 PANOP-BLOCK-2 C:CH 1:1957 --193.72.186/24 ALPHANET C:CH 1:1957 --193.72.193/24 EUNET-CH-C3 C:CH 1:1957 --193.72.204/24 METROPOLIS-C1 C:CH 1:1957 --193.72.208/24 FWE-TF-C1 C:CH 1:1957 --193.72.210/24 SGS-DEV C:CH 1:1957 --193.72.212/24 ADNZH C:CH 1:1957 --193.72.216/24 PEGASUS-NET C:CH 1:1957 --193.72.220/24 SEMAFOR C:CH 1:1957 --193.72.222/24 BSB C:CH 1:1957 --193.72.226/24 ERGON3 C:CH 1:1957 --193.72.230/24 RDM C:CH 1:1957 --193.72.236/24 VABA C:CH 1:1957 --193.72.238/24 CCI-C1 C:CH 1:1957 --193.72.242/24 MECATI C:CH 1:1957 --193.72.250/24 ELEX C:CH 1:1957 --193.88.33/24 DHINET-C-88-33 C:DK 1:1957 --193.88.34/24 DHINET-C-88-34 C:DK 1:1957 --193.88.35/24 DHINET-C-88-35 C:DK 1:1957 --193.88.40/24 RHHNET-C-88-40 C:DK 1:1957 --193.88.41/24 RHHNET-C-88-41 C:DK 1:1957 --193.88.42/24 RHHNET-C-88-42 C:DK 1:1957 --193.88.43/24 RHHNET-C-88-43 C:DK 1:1957 --193.88.49/24 NATIVE C:DK 1:1957 --193.88.50/24 DANOSI-OEST C:DK 1:1957 --193.88.62/24 METRIC C:DK 1:1957 --193.88.63/24 METRIC C:DK 1:1957 --193.88.64/24 DKNET-DIALIP1 C:DK 1:1957 --193.88.72/24 NETMAN C:DK 1:1957 --193.88.73/24 ACTIV C:DK 1:1957 --193.88.74/24 RHHNET-C-88-74 C:DK 1:1957 --193.88.75/24 RHHNET-C-88-75 C:DK 1:1957 --193.88.77/24 DUPLIKA C:DK 1:1957 --193.88.88/24 TV2 C:DK 1:1957 --193.88.89/24 TV2 C:DK 1:1957 --193.88.176/24 WHOEUR-C-88-176 C:DK 1:1957 --193.88.177/24 WHOEUR-C-88-177 C:DK 1:1957 --193.88.178/24 WHOEUR-C-88-178 C:DK 1:1957 --193.88.179/24 WHOEUR-C-88-179 C:DK 1:1957 --193.88.180/24 WHOEUR-C-88-180 C:DK 1:1957 --193.88.181/24 WHOEUR-C-88-181 C:DK 1:1957 --193.88.248/24 GNFILE C:DK 1:1957 --193.89.6/24 FOA-NET C:DK 1:1957 --193.89.16/24 COMPEL C:DK 1:1957 --193.89.20/24 DPI C:DK 1:1957 --193.89.32/24 CAPSYS C:DK 1:1957 --193.89.34/24 NORDNET C:DK 1:1957 --193.89.35/24 NORDNET C:DK 1:1957 --193.89.36/24 CMC-CPH-C-89-36 C:DK 1:1957 --193.89.37/24 CMC-CPH-C-89-37 C:DK 1:1957 --193.89.44/24 RHHNET-C-89-44 C:DK 1:1957 --193.89.45/24 RHHNET-C-89-45 C:DK 1:1957 --193.89.46/24 RHHNET-C-89-46 C:DK 1:1957 --193.89.96/24 Q8 C:DK 1:1957 --193.89.103/24 DDRE C:DK 1:1957 --193.89.105/24 PROMAX C:DK 1:1957 --193.89.106/24 BLT-COM C:DK 1:1957 --193.89.120/24 HILLKOMM C:DK 1:1957 --193.89.130/24 FDB C:DK 1:1957 --193.89.131/24 DIMATRIX C:DK 1:1957 --193.89.254/24 DKNET-TEST C:DK 1:1957 --193.141.74/24 A-LAB-NET C:DE 1:1324 2:1800 3:1240 4:1133 --198.67.2/24 POWERTREE C:US 1:1957 --198.67.20/24 FALCONBLK5 C:US 1:1957 --198.67.21/24 FALCONBLK6 C:US 1:1957 --198.67.22/24 FALCONBLK7 C:US 1:1957 --198.67.23/24 FALCONBLK8 C:US 1:1957 --198.67.24/24 FALCONBLK9 C:US 1:1957 --198.67.25/24 FALCONBLK10 C:US 1:1957 --198.67.39/24 SPRINT-C-67-39 C:US 1:1957 --198.67.41/24 SPRINT-C-67-41 C:US 1:1957 --198.93.16/24 BARRNET198-273 C:US 1:1957 --198.94.35/24 BARRNET198-548 C:US 1:1957 --198.94.37/24 CHABOT C:US 1:1957 --199.0.153/24 SPRINT-BLKA C:US 1:1957 --199.3.16/24 STERLINGSOFT1 C:US 1:1957 --199.14.11/24 SPRINT-MRN C:US 1:1957 --199.14.12/24 SPRINT-MRN C:US 1:1957 --199.35.10/24 NETBLK-NETCOMCBLK-2 C:US 1:1957 --199.35.11/24 NETBLK-NETCOMCBLK-2 C:US 1:1957 --199.35.12/24 NETBLK-NETCOMCBLK-2 C:US 1:1957 --199.35.13/24 NETBLK-NETCOMCBLK-2 C:US 1:1957 --199.35.14/24 NETBLK-NETCOMCBLK-2 C:US 1:1957 --199.35.75/24 NETBLK-NETCOMCBLK-2 C:US 1:1957 --199.35.129/24 NETBLK-NETCOMCBLK-2 C:US 1:1957 --199.45.130/24 NETBLK-COOP-NET C:US 1:1957 --199.72.5/24 NETBLK-INTERPATH C:US 1:1957 Expanded listing, sorted by country, then by organization: ========================================================== Australia --------- Australian Data Security Organization, PO Box 2031, BARKER, VIC, 3122, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 203.4.184/24 FERRO-MAG-NET-AU (AU) Financial Market Software Consultants, PO Box 836, ARTARMON, NSW, 2064, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 203.4.181/24 FMSC-NET-AU (AU) Pioneer Concrete, 63 Grove Street, St Peters, NSW, 2044, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 203.4.175/24 PIONEER-AU (AU) Unixpac Pty Limited, Level 3,339 Military Road, Cremorne, NSW, 2090, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 203.3.121/24 NET-UNIXPAC-AU (AU) Canada ------ MIND LINK! Communications Corp., Suite 105 - 20381 62nd Avenue, Langley, BC, V3A 5E6, CANADA 1:602 CA*net in Vancouver 2:601 CA*net in Toronto 3:603 CA*net in Montreal ------------ 199.175.7/24 MINDLINK3 (CA) Samuel Lunenfeld Institute of Mount Sinai Hospital, 600 University Avenue, Room 975A, Toronto, ON, M5G 1X5, CANADA 1:601 CA*net in Toronto 2:603 CA*net in Montreal 3:602 CA*net in Vancouver -------------- 192.197.251/24 MSHRI-NET1 (CA) Sea Change Corporation, 5159 Beckton Road, Victoria, BC, V8Y 2C2, CANADA 1:602 CA*net in Vancouver 2:601 CA*net in Toronto 3:603 CA*net in Montreal ------------- 198.162.87/24 SEAWEST-SEACHG-COM (CA) Simon Fraser University, Center for Systems Science, Burnaby, BC, V5A 1S6, CANADA 1:602 CA*net in Vancouver 2:601 CA*net in Toronto 3:603 CA*net in Montreal ----------- 199.60.1/24 SFUCSS (CA) 199.60.2/24 SFUCSS (CA) 199.60.3/24 SFUCSS (CA) 199.60.4/24 SFUCSS (CA) 199.60.5/24 SFUCSS (CA) 199.60.6/24 SFUCSS (CA) 199.60.7/24 SFUCSS (CA) 199.60.8/24 SFUCSS (CA) 199.60.9/24 SFUCSS (CA) 199.60.10/24 SFUCSS (CA) 199.60.11/24 SFUCSS (CA) 199.60.12/24 SFUCSS (CA) 199.60.13/24 SFUCSS (CA) 199.60.14/24 SFUCSS (CA) 199.60.15/24 SFUCSS (CA) 199.60.16/24 SFUCSS (CA) 199.60.17/24 SFUCSS (CA) 199.60.18/24 SFUCSS (CA) Supply and Services Canada, 11 Daumier Street, 2A1 Phase III, Hull, QC, K1A 0S5, CANADA 1:601 CA*net in Toronto 2:603 CA*net in Montreal 3:602 CA*net in Vancouver ---------- 142.111/16 SSCNET-CA (CA) 142.129/16 SSCNET1-CA (CA) Wellesley Hospital Research Institute, 65 Wellesley Street East, 428 Churwell Bldg, Toronto, ON, M4Y 1G7, CANADA 1:601 CA*net in Toronto 2:603 CA*net in Montreal 3:602 CA*net in Vancouver ------------ 199.212.4/24 WHRI (CA) Denmark ------- DKnet, Science Park Symbion, Fruebjergvej 3, DK-2100 Copenhagen O/, DENMARK 1:701 Alternet 2:1800 ICM-Atlantic --------- 193.88/15 EUNET-DK-193.88-AGG (DK) Finland ------- EISCAT Scientific Association, FIN-99600 Sodankyla, FINLAND 1:1800 ICM-Atlantic 2:1879 EUROPE-RS 3:1133 CERN/DANTE 4:1240 ICM-Pacific -------------- 193.208.149/24 SGO-NET (FI) France ------ Bridgeway Europe, 217 Quai de Stalingrad, 92130 Issy les moulineaux, FRANCE 1:701 Alternet 2:1800 ICM-Atlantic ------------- 193.104.15/24 FR-BRIDGEWAY (FR) Germany ------- Bildungszentrum fuer informationsverarbeitende Berufe e.V., Hauptstrasse 2, D-50935 Bergisch Gladbach, Bergisch, D-50935, GERMANY 1:1324 ANS New York City - DNSS 35 2:1800 ICM-Atlantic 3:1240 ICM-Pacific 4:1133 CERN/DANTE ------------ 193.22.64/24 BIB-LAN-C-22-64 (DE) 193.22.65/24 BIB-LAN-C-22-65 (DE) 193.22.66/24 BIB-LAN-C-22-66 (DE) 193.22.67/24 BIB-LAN-C-22-67 (DE) 193.22.68/24 BIB-LAN-C-22-68 (DE) 193.22.69/24 BIB-LAN-C-22-69 (DE) 193.22.70/24 BIB-LAN-C-22-70 (DE) 193.22.71/24 BIB-LAN-C-22-71 (DE) 193.22.72/24 BIB-LAN-C-22-72 (DE) 193.22.73/24 BIB-LAN-C-22-73 (DE) 193.22.74/24 BIB-LAN-C-22-74 (DE) 193.22.75/24 BIB-LAN-C-22-75 (DE) 193.22.76/24 BIB-LAN-C-22-76 (DE) 193.22.77/24 BIB-LAN-C-22-77 (DE) 193.22.78/24 BIB-LAN-C-22-78 (DE) 193.22.79/24 BIB-LAN-C-22-79 (DE) NTG Netzwerk und Telematic GmbH, Geschaeftsbereich XLINK, Vincenz-Priessnitz-Str. 3, D-76131 Karlsruhe, GERMANY 1:1324 ANS New York City - DNSS 35 2:1800 ICM-Atlantic 3:1240 ICM-Pacific 4:1133 CERN/DANTE ---------- 193.141/16 XLINK_BLOCK_193.141.0 (DE) roka EDV und Datenkommunikationsberatung GmbH, Elbestr. 25, D-47800 Krefeld, GERMANY 1:1324 ANS New York City - DNSS 35 2:1800 ICM-Atlantic 3:1240 ICM-Pacific 4:1133 CERN/DANTE -------------- 193.141.139/24 ROKANET4 (DE) Ireland ------- Murray Telecommunication Limited, 32 Upper Mount Street, Dublin 2, IRELAND 1:701 Alternet 2:1800 ICM-Atlantic -------------- 193.120.202/24 ALD-CONNECT (IE) 193.120.205/24 ALD (IE) Italy ----- Comsorzio Catania Ricerche, Viale Andrea Doria 6, Catania, I-95125, ITALY 1:293 Energy Science Network (FIX-East) 2:291 Energy Science Network (FIX-West) 3:1133 CERN/DANTE 4:1674 CERN/DANTE 5:1800 ICM-Atlantic -------------- 193.204.118/24 CRES-IPNET-2 (IT) Japan ----- Business Center for Academic Societies Japan, Gakkai-Center Building C, 21, 5-16-9 Honkomagome, Bunkyo-ku, Tokyo 133, JAPAN 1:1240 ICM-Pacific 2:1800 ICM-Atlantic -------------- 202.252.216/24 BCASJNET (JP) 202.252.217/24 BCASJNET (JP) 202.252.218/24 BCASJNET (JP) 202.252.219/24 BCASJNET (JP) 202.252.220/24 BCASJNET (JP) 202.252.221/24 BCASJNET (JP) 202.252.222/24 BCASJNET (JP) 202.252.223/24 BCASJNET (JP) Mie University, 1515 Kamihama, Tsu-shi, Mie 514, JAPAN 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ------------ 192.50.66/24 MARINE2 (JP) 192.50.67/24 MARINE2 (JP) 192.50.68/24 MARINE2 (JP) Nagaoka College of Technology, 888 Nishikatakai, Nagaoka-shi, Niigata 940, JAPAN 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ------------- 202.25.112/24 NCT-NET (JP) Okinawa University, 555 Kokuba, Naha-shi, Okinawa 902, JAPAN 1:1240 ICM-Pacific 2:1800 ICM-Atlantic -------------- 202.252.214/24 OKINAWA-NET (JP) Yachiyo International University, Daigaku-cho 1-1, Yachiyo-shi, Chiba 276, JAPAN 1:1240 ICM-Pacific 2:1800 ICM-Atlantic -------------- 202.252.246/24 YACHIYONET (JP) Liechtenstein ------------- Liechtensteinische Ingenieurschule - Fachhochschule, Marianumstrasse 45, FL-9490 Vaduz, LIECHTENSTEIN 1:1133 CERN/DANTE 2:1674 CERN/DANTE 3:1800 ICM-Atlantic ----------- 193.5.26/23 LIS-VADUZ (LI) Netherlands ----------- Unisource Business Networks, P.O. Box 90934, NL-2509 LX The Hague, NETHERLANDS 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1674 CERN/DANTE 4:1240 ICM-Pacific ------------ 193.172.2/23 EMPB (NL) Russian Federation ------------------ Babakin Institute, Leningradskoye Sh. 22-101, Moscow Region, Khimki, 141400, RUSSIAN FEDERATION 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) ------------- 193.232.22/24 BABAKIN-LAN (RU) Izmiran, Experimental Bldg., Moscow Region, Troitsk, 142092, RUSSIAN FEDERATION 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) ------------- 193.232.24/24 NPOE-LAN (RU) Spain ----- RedIRIS, Serrano 142, Madrid, E-28006, SPAIN 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1674 CERN/DANTE 4:1240 ICM-Pacific ---------- 193.144/15 REDIRIS-PROVIDER (ES) Sweden ------ Swedish Institute of Microelectronics (IM), PO Box 1084, S-164 21 Kista, SWEDEN 1:1800 ICM-Atlantic 2:1879 EUROPE-RS 3:1133 CERN/DANTE 4:1240 ICM-Pacific ------------- 192.16.124/22 IMIKTH-CIDR (SE) Switzerland ----------- Ares Services S.A., 15bis, ch. des Mines, CH-1202 Geneva, SWITZERLAND 1:1133 CERN/DANTE 2:1674 CERN/DANTE 3:1800 ICM-Atlantic -------------- 193.134.208/21 SERONET (CH) CERN, European Laboratory for, Particle Physics, CN division, CH-1211 Geneva 23, SWITZERLAND 1:1133 CERN/DANTE 2:1800 ICM-Atlantic 3:1240 ICM-Pacific ------------- 192.91.242/23 CERN-CNET29 (CH) CNCS Computer Network Consulting Services AG, Froebelstrasse 10, CH-8032 Zuerich, SWITZERLAND 1:1133 CERN/DANTE 2:1674 CERN/DANTE 3:1800 ICM-Atlantic ----------- 193.5.70/23 CNCS (CH) Centre CIM de Suisse Occidental, Rte Mont-Carmel 1, CH-1762 Givisiez (FR), SWITZERLAND 1:1133 CERN/DANTE 2:1674 CERN/DANTE 3:1800 ICM-Atlantic ------------ 193.5.160/21 CIMNET (CH) Cerberus AG, alte Landstr. 411, CH-8708 Maennedorf, SWITZERLAND 1:1133 CERN/DANTE 2:1674 CERN/DANTE 3:1800 ICM-Atlantic ----------- 193.5.44/23 CERBERUS (CH) EPFL, Swiss Federal Institute of Technology Lausanne, EPFL-SIG, CH-1015 Lausanne, SWITZERLAND 1:1133 CERN/DANTE 2:1674 CERN/DANTE 3:1800 ICM-Atlantic ---------- 128.178/15 EPNET (CH) Ingenieurschule Bern HTL, Morgartenstrasse 2c, CH-3014 Berne, SWITZERLAND 1:1133 CERN/DANTE 2:1674 CERN/DANTE 3:1800 ICM-Atlantic ----------- 193.5.80/21 ISBE-SWS-NET1 (CH) Ingenieurschule Burgdorf, Pestalozzistrasse 20, CH-3400 Burgdorf, SWITZERLAND 1:1133 CERN/DANTE 2:1674 CERN/DANTE 3:1800 ICM-Atlantic ------------ 193.5.168/22 ISBURG2 (CH) SWITCH Geschaeftsstelle, Limmatquai 138, CH-8001 Zuerich, SWITZERLAND 1:1133 CERN/DANTE 2:1674 CERN/DANTE 3:1800 ICM-Atlantic ---------- 129.194/15 SWITCH-AGGR.1 (CH) 147.86/15 SWITCH-AGGR.2 (CH) 193.5/16 SWITCH-AGGR.3 (CH) 193.134/16 SWITCH-AGGR.4 (CH) Scuola Tecnica Superiore Lugano, CH-6952 Canobbio, SWITZERLAND 1:1133 CERN/DANTE 2:1674 CERN/DANTE 3:1800 ICM-Atlantic ------------ 193.5.152/22 STS (CH) Swiss Federal Institute for Forest, Snow and Landscape Research, Zuercherstrasse 111, CH-8903 Birmensdorf, SWITZERLAND 1:1133 CERN/DANTE 2:1674 CERN/DANTE 3:1800 ICM-Atlantic -------------- 193.134.200/21 WSLNET (CH) Swiss PTT, Research & Development, Technical Center, CH-3000 Bern 29, SWITZERLAND 1:1133 CERN/DANTE 2:1674 CERN/DANTE 3:1800 ICM-Atlantic ------------ 193.5.224/20 VPTT (CH) University of Geneva, Rue du General Dufour, 24, CH-1211 Geneva 4, SWITZERLAND 1:1133 CERN/DANTE 2:1674 CERN/DANTE 3:1800 ICM-Atlantic ------------- 192.33.216/22 C-216 (CH) XMIT AG, Bernstrasse 388, CH-8953 Dietikon, SWITZERLAND 1:1133 CERN/DANTE 2:1674 CERN/DANTE 3:1800 ICM-Atlantic ------------ 193.5.156/22 XMIT2 (CH) United Kingdom -------------- Goldsmith's College, New Cross, London, Greater London, SE14 6NW, UNITED KINGDOM 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific ---------- 158.223/16 GOLD (GB) Unipalm, Ltd., 216 Cambridge Science Park, Milton Road, Cambridge, CB4 4WA, UNITED KINGDOM 1:701 Alternet 2:702 Alternet ------------- 199.170.77/24 UNIPALM-TS (GB) United States ------------- Adrian College, 110 S. Madison, Adrian, MI 49221, USA 1:237 MichNet (MERIT) 2:233 UMnet (University of Michigan) 3:266 CICNET at MERIT 4:267 CICNET at UIUC 5:1225 CICNET at Argonne Labs ------------- 198.108.80/24 NETBLK-ADRIAN (US) 198.108.81/24 NETBLK-ADRIAN (US) 198.108.82/24 NETBLK-ADRIAN (US) 198.108.83/24 NETBLK-ADRIAN (US) 198.108.84/24 NETBLK-ADRIAN (US) 198.108.85/24 NETBLK-ADRIAN (US) 198.108.86/24 NETBLK-ADRIAN (US) 198.108.87/24 NETBLK-ADRIAN (US) Anaheim Union High School District, 501 Cresent Way, Anaheim, CA 92803-3520, USA 1:2150 CSUNET-SW 2:200 BARRNet 3:201 BARRNet -------------- 198.188.246/24 CSUNET-SOUTH-C-188-24 (US) 198.188.247/24 CSUNET-SOUTH-C-188-24 (US) Bedge Inc., 14382 Crestwood Avenue, Poway, CA 92064, USA 1:1740 CERFnet ------------- 199.89.221/24 BEDGE (US) Bell & Howell Company,, 300 N. Zeeb Rd., Ann Arbor, MI 48106, USA 1:1325 ANS Cleveland - DNSS 43 ---------- 165.215/16 BH-COM (US) Blueshift, Inc., 6825 Jimmy Carter Boulevard, Suite #1220, Norcross, GA 30202, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.156/24 PSINET-C5 (US) Boystown National Research Hospital, 555 N. 30th St, Omaha, NE 68131, USA 1:93 MIDnet -------------- 198.247.236/24 BOYSTOWN (US) 198.247.237/24 BOYSTOWN (US) 198.247.238/24 BOYSTOWN (US) 198.247.239/24 BOYSTOWN (US) CICNet, Inc., 2901 Hubbard, Ann Arbor, MI 48105, USA 1:1225 CICNET at Argonne Labs 2:267 CICNET at UIUC 3:266 CICNET at MERIT -------------- 192.217.209/24 CICNET-C-217-209 (US) 192.217.210/24 CICNET-C-217-210 (US) 192.217.211/24 CICNET-C-217-211 (US) 192.217.215/24 CICNET-C-217-215 (US) 192.217.216/24 CICNET-C-217-216 (US) 192.217.217/24 CICNET-C-217-217 (US) CICNet, Inc., 2901 Hubbard, Ann Arbor, MI 48105, USA 1:266 CICNET at MERIT 2:267 CICNET at UIUC 3:1225 CICNET at Argonne Labs ------------- 198.87.250/24 CICNET-2 (US) Chicago Title & Trust Company, 171 N. Clark, 7th Floor, Chicago, IL 60601, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific -------------- 198.182.250/24 CTIMAGENET (US) Cisco Systems, 1525 O'Brien Drive, Menlo Park, CA 94025, USA 1:200 BARRNet 2:201 BARRNet -------------- 192.135.240/21 CISCO-FLD2 (US) Colorado Internet Cooperative Association, 1495 Canyon Blvd, Suite 35, Boulder, CO 80302, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ------------- 199.45.128/17 NETBLK-COOP-NET (US) Colorado SuperNet, Inc., Colorado School of Mines, 1500 Illinois, Golden, CO 80401, USA 1:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 2:210 Westnet Regional Network (Utah Attachment) - ENSS 142 ------------- 199.117.22/24 CSN-BLK3 (US) County of Marin, 371 Bel Marin Keys, Novato, CA 94947, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ------------ 199.88.64/18 MARIN-COUNTY (US) Decision Science Applications, 1110 N. Glebe Road, Suite 400, Arlington, VA 22201, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.116/24 DSA (US) 199.165.172/24 DSA (US) Economists Inc., 1233 20th St. NW, Suite 600, Washington, DC 20036, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.157/24 PSINET-C5 (US) Family Health International, Post Office Box 13950, Research Triangle Park, NC 27709, USA 1:1329 ANS Greensboro - DNSS 75 ------------- 198.85.108/24 FHI (US) Freeside Communications, Inc., 2120 Denton Drive, Suite 104, Austin, TX 78758, USA 1:701 Alternet 2:702 Alternet ------------ 198.6.198/24 FC1 (US) Internet Access Cincinnati, 210 S. Monument Ave., Hamilton, OH 45011, USA 1:2548 DIGEX-AS ----------- 199.6.32/20 IAC-CBLK1 (US) Interpath, 711 Hillsborough Street, Raleigh, NC 27603, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific --------- 199.72/16 INTERPATH-AGG (US) Knoxville College, 205 McKee Hall, MIS Dept., 901 College, Knoxville, TN 37291, USA 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) ------------- 198.78.247/24 KNXCOLL-NET (US) Lenoir Community College, PO Box 188, Kinston, NC 28501, USA 1:1329 ANS Greensboro - DNSS 75 ------------ 198.86.76/24 LENOIRCC1 (US) MCI Telecommunications, 2100 Reston Parkway, Reston, VA 22091, USA 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) ------------ 198.77.88/24 VA-MCI-NET-C-77-88 (US) 198.77.89/24 VA-MCI-NET-C-77-89 (US) 198.77.90/24 VA-MCI-NET-C-77-90 (US) 198.77.91/24 VA-MCI-NET-C-77-91 (US) 198.77.92/24 VA-MCI-NET-C-77-92 (US) 198.77.93/24 VA-MCI-NET-C-77-93 (US) 198.77.94/24 VA-MCI-NET-C-77-94 (US) 198.77.95/24 VA-MCI-NET-C-77-95 (US) Mabon Securities, One Liberty Plaza, New York, NY 10006, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI -------------- 198.185.168/24 MABON6 (US) 198.185.169/24 MABON7 (US) 198.185.170/24 MABON8 (US) 198.185.171/24 MABON9 (US) 198.185.172/24 MABON10 (US) Medical Center Hospital of Vermont, 111 Colchester Avenue, Burlington, VT 05401, USA 1:560 NEARnet Regional Network 2:701 Alternet -------------- 192.132.235/24 MCHV-235 (US) 192.132.236/24 MCHV-236 (US) 192.132.237/24 MCHV-237 (US) 192.240.32/24 MCHV-32 (US) 192.240.33/24 MCHV-33 (US) 192.240.34/24 MCHV-34 (US) 192.240.35/24 MCHV-35 (US) 192.240.36/24 MCHV-36 (US) 192.240.37/24 MCHV-37 (US) 192.240.38/24 MCHV-38 (US) 192.240.39/24 MCHV-39 (US) 192.240.40/24 MCHV-40 (US) 192.240.41/24 MCHV-41 (US) 192.240.42/24 MCHV-42 (US) 192.240.43/24 MCHV-43 (US) 192.240.44/24 MCHV-44 (US) 192.240.45/24 MCHV-45 (US) 192.240.46/24 MCHV-46 (US) Merit Network, Inc., University of Michigan, 1071 Beal Ave., Ann Arbor, MI 48109, USA 1:237 MichNet (MERIT) 2:233 UMnet (University of Michigan) 3:266 CICNET at MERIT 4:267 CICNET at UIUC 5:1225 CICNET at Argonne Labs ---------- 198.108/14 NETBLK-MICHNET198 (US) 198.108.0/22 NETBLK-MICHNET198 (US) Morrison Knudsen Corporation, 720 Park Boulevard, Boise, ID 83712, USA 1:1331 ANS Seattle - DNSS 91 ------------- 198.81.224/24 MK-SHARED (US) Mt Vernon Nazarene College, 800 Martinsburg Rd, Mt Vernon, OH 43050, USA 1:600 OARNET, Cleveland, OH 2:1800 ICM-Atlantic ---------- 149.143/16 NET-MVNC (US) NASA Ames Research Center, MS 233-8, Moffett Field, CA 95014, USA 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) ------------- 198.116.18/24 NSI (US) 198.116.19/24 NSI (US) NAVAL COMPUTER AND TELECOMM. AREA MASTER STATION, PSC 822 BOX 1000, FPO, AE 09621-7000, USA 1:19 Milnet (FIX-East) 2:568 Milnet (FIX-West) ------------- 199.10.243/24 MED-NET-1 (US) Netcom On-line Communications Services, Inc., 4000 Moorpark Ave, Suite 209, San Jose, CA 95117, USA 1:2551 NETCOM ------------- 192.153.42/23 NETCOM1 (US) 192.153.44/22 NET-FCS (US) 192.153.48/21 NETCOM7 (US) 192.187.128/17 NETCOM31 (US) 192.206.82/23 DESKTOPDATA (US) 192.206.84/23 DESKTOPDATA3 (US) 192.215.126/23 NATUNIV27 (US) 192.215.128/22 NATUNIV29 (US) 192.235.32/20 AXIL1 (US) 192.235.48/22 AXIL17 (US) 192.245.82/23 AGAMES-1 (US) 192.245.84/23 AGAMES-3 (US) 192.247.16/21 RWBECK-16 (US) 192.247.24/22 RWBECK-24 (US) 198.62.156/23 CFER-NET1 (US) 198.71.16/21 MFI (US) 198.71.24/22 MFI9 (US) 198.183.206/23 LAMBDA-C-183-206 (US) 198.183.208/23 LAMBDA-C-183-208 (US) 198.211/16 NETBLK-NETCOM-CBLK (US) 199.67.10/23 ABEKAS-10 (US) 199.67.12/22 ABEKAS-12 (US) Nicholas-Applegate Capital Management, 600 West Broadway, 29th Floor, San Diego, CA 92101, USA 1:701 Alternet 2:702 Alternet ------------- 199.170.56/24 NACM-NET (US) 199.170.57/24 NACM-NET (US) 199.170.58/24 NACM-NET (US) 199.170.59/24 NACM-NET (US) 199.170.60/24 NACM-NET (US) 199.170.61/24 NACM-NET (US) 199.170.62/24 NACM-NET (US) 199.170.63/24 NACM-NET (US) PWAC, Inc, 145 Munroe St. Suite 400, Lynn, MA 01904, USA 1:1800 ICM-Atlantic -------------- 199.165.192/24 STEAM (US) Pacific Gas and Electric Company, 77 Beale Street, San Francisco, CA 94106, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI --------- 131.89/16 PGE-BNET (US) Q+E Software, 5540 Centerview Drive, Suite 324, Raleigh, NC 27606, USA 1:1329 ANS Greensboro - DNSS 75 ------------- 198.85.109/24 QESOFT-NET (US) Sense/Net, 553 1st Ave, #4, Salt Lake City, UT 84111, USA 1:210 Westnet Regional Network (Utah Attachment) - ENSS 142 2:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 ------------- 199.88.179/24 SENSE-NET (US) Southeast Network Services, PO Box 56946, Jacksonville, FL 32241-6946, USA 1:701 Alternet 2:702 Alternet ------------- 199.170.71/24 JAXNET-NET (US) Sprint Government Systems Division, 8330 Ward Parkway, Kansas City, MO 64114, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ----------- 199.3.26/24 SPRINTGSD (US) US Sprint, BSG, 13221 Woodland Rd, Herndon, VA 22071, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ----------- 198.67.0/17 SL-EAST-AGGR (US) 199.11/16 MRN-BLK1 (US) 199.14/16 MRN-BLK4 (US) US Sprint, BSG, 13221 Woodland Rd, Herndon, VA 22071, USA 1:1800 ICM-Atlantic ------------- 198.67.128/17 ICM-EAST-AGGR (US) US Sprint, BSG, 13221 Woodland Rd, Herndon, VA 22071, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic --------- 198.68/16 SPRINT-WEST2 (US) Westnet Regional Network, University of Colorado, 3645 Marine Street, Boulder, CO 80309-0455, USA 1:210 Westnet Regional Network (Utah Attachment) - ENSS 142 2:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 ------------- 198.60.72/24 WESTNET (US) 198.60.73/24 WESTNET (US) 199.104.70/24 WESTNET-W2 (US) hfl Consulting, 92 Evans Road, Brookline, MA 02146-2118, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific -------------- 199.181.200/24 TELMAR-NET (US) ========================================================== The following Midlevel/Regional peering sessions have also been added: AS 3354 - THENET-AS-1 - ENSS 139 Peer: 192.67.14.93 - The University of Texas System, Office of Telecommunication Services, SER 319 - 62900, Austin, TX 78712, USA - Router domain name unknown ========================================================== AS690 CIDR Squeezings Report: 1044 Nets, 24 ASs, 115 Aggregates ---------------------------------------------------------------- 1044 (46%) of the ever-announced more-specific routes within aggregates have been withdrawn. 552 of those were withdrawn within the last week. 220 the week before that. 152 the week before that. 24 ASs have registered aggregates in the PRDB. 21 of those are announcing aggregates. 12 have withdrawn at least one more specific route. 115 Aggregates are configured. 104 of these were Top-Level Aggregates (not nested in another aggregate). 81 of these were announced to AS690 as of yesterday. 70 of those have at least one subnet configured (the other 11 may be saving. the Internet future subnet announcements). 46 have stopped announcing at least one configured more specific route. 34 have stopped announcing half of their configured more specific routes. 29 have stopped announcing most (80%) of their more specific routes. See 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.t3p Information is also avaiable through the PRDB whois server. Type "whois -h prdb.merit.edu help" for details. -------------------------------------------------------------------------- REPORT CHANGES: (Updated March 24, 1994) Metric:AS(NSS) - Historically, peer networks with multiple connections to AS 690 could only select which of those connections their networks would take by creating "Fake" AS numbers, and using those in the PRDB Metric:AS announcement lists. Some time in the next few weeks we will begin supporting an expanded syntax, where the AS may be followed by an optional NSS peer number in parentheses. Eventually, this syntax will be used to replace most or all of the current Fake ASs. This change will affect *all* places that the announcement lists are reported: all whois queries, all network reports, this "NWG" report, and the Auto-NACR. If you have code which parses these announcement lists, please be aware that that code may need modifications soon. CIDR Reports: There is a new "whois" option to list aggregates in the PRDB: whois -h prdb.merit.edu listaggs will produce a listing of the currently registered aggregates. There is also a new report on "nestings" of PRDB-registered aggregates with their more specific routes: nets.non-classful. Anyone considering configuring an aggregate into the PRDB (and you all should be!) is encouraged to pre-check that aggregate by typing the command: whois -h prdb.merit.edu 'aggchk ' (where "" is the aggregate description). This command will list all of the other entries in the PRDB that are more specific routes of , as well as any aggregates all ready configured that contain . The output includes the AUP and announcement lists of each of the nets printed, with discrepancies flagged. This is the same program that we use for sanity-checking the NACRs that you submit. The archived discussion list "db-disc@merit.edu" exists for discussion of PRDB issues. Send a message to "db-disc-request@merit.edu" to subscribe. --Dale Johnson (dsj@merit.edu) -------------------------------------------------------------------------- Please send all requests for configuration changes to nsfnet-admin@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. ******************************* --Steve Widmayer Merit/NSFNET skw@merit.edu --Enke Chen Merit/NSFNET enke@merit.edu --Steven J. Richardson Merit/NSFNET sjr@merit.edu - - - - - - - - - - - - - - - - - From list-admin Thu Apr 21 09:26:04 1994 Received: from localhost (skh@localhost) by merit.edu (8.6.8.1/merit-1.0) with SMTP id JAA25316; Thu, 21 Apr 1994 09:25:58 -0400 Message-Id: <199404211325.JAA25316@merit.edu> To: fedor@msf.psi.net (Mark S. Fedor) cc: peter@goshawk.lanl.gov, schoff@us.psi.com, bgpd@merit.edu, fedor@us.psi.com, regional-techs@merit.edu, yakov@watson.ibm.com, skh@merit.edu Subject: Re: 20402 routing entries In-reply-to: Your message of "Fri, 15 Apr 1994 16:57:04 EDT." <9404152057.AA01717@msf.psi.net> Date: Thu, 21 Apr 1994 09:06:51 -0400 From: Susan Hares Mark: Just catching up on mail, so I apologize if this is out of sequence. >What does this mean? Well you can develop a routing strategies which >take into account many diverse exit points from your AS. You can >develop routing strategies based on high end users, low-end users, >route the east coast here, the west coast there. You name it. It sounds like long-range you want a IPng protocol that allows flexible auto-assignment of network numbers? Perhaps someone should mention this to the IPng folks? I know of autoconfiguration work in some of the protocols for IPng. ;-) Sue Hares - - - - - - - - - - - - - - - - - From list-admin Thu Apr 21 13:34:04 1994 Received: from watson.ibm.com (watson.ibm.com [129.34.139.4]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id NAA22586 for ; Thu, 21 Apr 1994 13:34:04 -0400 From: yakov@watson.ibm.com Message-Id: <199404211734.NAA22586@merit.edu> Received: from YKTVMV by watson.ibm.com (IBM VM SMTP V2R3) with BSMTP id 9473; Thu, 21 Apr 94 13:33:59 EDT Date: Thu, 21 Apr 94 13:33:36 EDT To: regional-techs@merit.edu Subject: CIDRizing the Internet fyi Yakov. ****** The following is a COPY ***************************** Received: from merit.edu by watson.ibm.com (IBM VM SMTP V2R3) with TCP; Thu, 21 Apr 94 12:17:01 EDT Received: from localhost (jyy@localhost) by merit.edu (8.6.8.1/merit-1.0) with SMTP id MAA14094; Thu, 21 Apr 1994 12:13:50 -0400 Message-Id: <199404211613.MAA14094@merit.edu> To: bgpd@merit.edu cc: jyy@merit.edu Subject: CIDR, proxy-aggr or Die? Date: Thu, 21 Apr 1994 12:13:49 -0400 From: Jessica Yu Hi, Below is the NSF/ANSNET routing table size growth history data which Merit has been collecting. It shows that, on average, every two weeks there are ~500 more routes added to the routing table between 4/93 - 3/94 and the average growth is 4%. Note, this is prior to people start to withdraw more specific routes. It also shows that during the first half of month 4/94, the routing table increased by 333 routes instead of 857 during the previous two-week period. This shows the effect of CIDR. So what's the point? 1. Since we start to withdraw more specific routes around Apr. 1st.'94, it helped reduce the growth of the routing table by more than a half (4.1% vs 1.7%) 2. The routing table grows faster since the beginning of this year than last year, the average increase of two-week period since 1/94 - 3/94 is 776 routes or 4.57%. Everyone can do a calculation and figure out when his/her routers will run out of memory. 3. It still adds 333 more routes during the two-week period when we start to withdraw more specific routes. We need to do more CIDR. If we withdraw more or the same amount of routes added, we win. That requires us - When advertise new routes, advertise aggregates not aggregatable specific routes. Do more aggregation on existing specific routes and withdraw them. So again: ASs who do BGP4 already, please advertise aggregates and remove your more specific routes. ASs who do not do BGP4 yet, please either run BGP4 and do aggregation or delegate your neighbor ASs to proxy aggregate your routes. It used to be: CIDR, default or die! It is now: CIDR, proxy-aggr or die! --jessica P.S. The reason this set of data is shown in bi-weekly format is that we want to see the effect of CIDR since 4/94. Since 4/15, there are a lot more withdrawn happened so it should be interesting to see the data at the end of this month. (Enke:thanks for collecting the data). # 2 week # max r_tab # 2wk growth(%) #2wk rts increase # =============================================================== 93/04/15 7972 2.64 205 93/04/30 8239 3.35 267 93/05/15 8538 3.63 299 93/05/30 8961 4.95 423 93/06/15 9244 3.16 283 93/06/30 9534 3.14 290 93/07/15 9739 2.15 205 93/07/30 10113 3.84 374 93/08/15 10484 3.67 371 93/08/30 10879 3.77 395 93/09/15 11244 3.36 365 93/09/30 11621 3.35 377 93/10/15 12150 4.55 529 93/10/30 12703 4.55 553 93/11/15 13409 5.56 706 93/11/30 13886 3.56 477 93/12/15 14649 5.49 763 93/12/30 14802 1.04 153 94/01/15 15509 4.78 707 94/01/30 16281 4.98 772 94/02/15 16890 3.74 609 94/02/30 17713 4.87 823 94/03/15 18531 4.62 818 94/03/30 19388 4.62 857 avg: 4.06% 496 94/04/15 19721 1.72 333 - - - - - - - - - - - - - - - - - From list-admin Thu Apr 21 16:35:02 1994 Received: (dsj@localhost) by merit.edu (8.6.8.1/merit-1.0) id QAA10259; Thu, 21 Apr 1994 16:35:02 -0400 Date: Thu, 21 Apr 1994 16:35:02 -0400 From: "Dale S. Johnson" Message-Id: <199404212035.QAA10259@merit.edu> To: db-disc, regional-techs Subject: PRDB Report Changes FYI: Reports from the Policy Routing DataBase (PRDB) will be changing in the next days to reflect new PRDB funcitonality. The most visible new feature today is the "UNCONFIGURE" flag. This is a flag that can be turned on for any network. It has the effect of removing that network from the AS690 configuration files, while keeping it in the PRDB for registry and analysis purposes. (Information about *all* nets is also copied over to the new Merit Routing Registry every config run). whois - has been updated to include a new "flags:" field. Currently, the field is either empty or contains a message that the net "is not to be configured." This syntax will become more elaborate later, as new features evolve. nets.unl.now - has just been updated to include four more fields. These fields have been added at the end of the current records, so, hopefully, current applications that use nets.unl.now will not break. The definitions of the contents of these fields has not been finalized, but they will be used to present information about UNCONFIGURE status, Proxy Aggregation status, and Offnet information. For now, field #14 contains an "N" for all nets that have the UNCONFIGURE bit set. nets.tag.now - will also have these new fields added. other reports (ans_core.now, corenets, and country.now) will not change, except that "UNCONFIGUREd" networks will no longer appear in them. Metric:AS(NSS) - The long-awaited demise of "Fake ASs" is also soon to happen. As soon as next week you may the new "Metric:AS(NSS)" syntax in all PRDB reports that include AS announcement lists. --Dale - - - - - - - - - - - - - - - - - From list-admin Thu Apr 21 16:41:48 1994 Received: from igi.prep.net (root@BOONE.SLIP.ANDREW.CMU.EDU [128.2.115.8]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id QAA11090; Thu, 21 Apr 1994 16:41:41 -0400 Received: from boone.slip.andrew.cmu.edu by igi.prep.net with smtp (Smail3.1.28.1 #1) id m0pu5Rc-0004nUC; Thu, 21 Apr 94 16:33 EDT Date: Thu, 21 Apr 1994 16:33:56 +0100 From: "Jon 'Iain' Boone" Subject: Re: 20402 routing entries To: Walt Haas cc: Martin Lee Schoffstall , Dennis Ferguson , "Peter S. Ford" , yakov@watson.ibm.com, bgpd@MERIT.EDU, regional-techs@MERIT.EDU, fedor@us.psi.com In-Reply-To: <199404152250.QAA11758@ski.utah.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII You mean assert network numbers like Appletalk allows for?!? On Fri, 15 Apr 1994, Walt Haas wrote: > However, if we could develop a technology which could make renumbering > of a network (ie. a company, university or similar-sized unit) fast and > efficient, this premise would break down and it would no longer be unreasonable > to consider renumbering the organization when switching providers. > > Suppose, for example that Domain Names were sacred but a daemon could > somehow touch every machine in a certain domain simultaneously and give > it a new number, while simultaneously updating the routing tables that > pointed into that domain? > > No, I don't have an RFC written, sorry, it's just an idea. /***********************************************************/ /* Jon 'Iain' Boone Production Engineer boone@prep.net */ /* (412) 268-7874 PREPnet iain+@cmu.edu */ /* The opinions expressed above are just that: opinions. */ /* They belong to me and me alone. */ /***********************************************************/ - - - - - - - - - - - - - - - - - From list-admin Fri Apr 22 05:51:11 1994 Received: (skw@localhost) by merit.edu (8.6.8.1/merit-1.0) id FAA04198 for nwg; Fri, 22 Apr 1994 05:51:11 -0400 Date: Fri, 22 Apr 1994 05:51:11 -0400 From: "Steven K. Widmayer" Message-Id: <199404220951.FAA04198@merit.edu> To: nwg Subject: Additions to the NSFNET policy-based routing database ------------------------------------------------------------------------------ New format for Metric:AS lists coming later in this and all reports. See 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 Configured Networks 30279 = 29 4645 25279 326 Added Networks 460 = 0 10 296 154 Deleted Networks 37 = 0 0 37 0 IP address Net name Country Priority:AS ---------- -------- ------- ----------- 134.54/16 CAMEX C:US 1:2551 141.23/16 CSTUB C:DE 1:701 2:1800 145.237/16 POLFIN C:PL 1:1800 2:1133 3:1240 146.74/16 SCCONET C:US 1:200 2:201 146.172/16 TBKINTERNET C:NO 1:1800 2:1879 3:1133 4:1240 148.231/16 UABC C:MX 1:2150 2:200 3:201 150.221/16 KODAKB C:US 1:2149 2:174 164.73/16 RAU C:UY 1:1800 2:1240 165.22/16 CELTECH1 C:US 1:1982 170.9/16 KII C:US 1:2149 2:174 192.6.3/24 HP-NETS4 C:US 1:560 2:200 3:201 192.18.78/23 IDE-1 C:US 1:701 2:702 192.18.80/23 IDE-3 C:US 1:701 2:702 192.43.154/23 NCD-CNETS154 C:US 1:701 2:702 192.43.156/22 NCD-CNETS156 C:US 1:701 2:702 192.58.98/23 NTTDATA-02 C:JP 1:1957 192.58.100/23 NTTDATA-04 C:JP 1:1957 192.58.248/24 IMATRON C:US 1:2551 192.64.100/22 EUNET-BE-192.64.100-A C:BE 1:701 2:1800 192.68.141/24 NET-SD-SYSTEMS C:US 1:600 2:1800 192.78.186/23 EUNET-BE-192.78.186-A C:BE 1:701 2:1800 192.92.130/23 EUNET-BE-192.92.130-A C:BE 1:701 2:1800 192.93.181/24 FNET-INPL C:FR 1:1800 2:1240 3:1133 4:1674 192.100.203/24 PIXEL C:MX 1:1800 2:1240 3:1328 192.103.16/22 NOKIA-US-1 C:US 1:701 2:702 192.107.242/23 QUINTUS-NET2 C:US 1:701 2:702 192.107.244/23 QUINTUS-NET4 C:US 1:701 2:702 192.108.252/23 FRAME-C1 C:US 1:701 2:702 192.124.146/23 TRUEVISION-NET C:US 1:701 2:702 192.125.2/23 HARTMANN-1-40 C:DE 1:1324 2:1800 3:1240 4:1133 192.125.4/22 HARTMANN-1-40 C:DE 1:1324 2:1800 3:1240 4:1133 192.125.8/21 HARTMANN-1-40 C:DE 1:1324 2:1800 3:1240 4:1133 192.125.16/20 HARTMANN-1-40 C:DE 1:1324 2:1800 3:1240 4:1133 192.125.32/21 HARTMANN-1-40 C:DE 1:1324 2:1800 3:1240 4:1133 192.132.217/24 COLGATE4 C:US 1:1957 192.138.128/23 SCOTOR1 C:CA 1:701 2:702 192.154.10/23 DP7UP3 C:US 1:701 2:702 192.156.132/24 CEC-JRC-IRMM C:BE 1:293 2:291 192.158.32/23 CUMMINS-FS1 C:US 1:701 2:702 192.159.78/23 LARSE1-NET C:US 1:701 2:702 192.167.96/20 MESSINA-NET C:IT 1:293 2:291 3:1133 4:1674 192.187.66/23 LATIMES-3 C:US 1:1957 192.187.68/22 LATIMES-5 C:US 1:1957 192.187.72/21 LATIMES-9 C:US 1:1957 192.187.80/20 LATIMES-17 C:US 1:1957 192.195.208/23 ITM1 C:US 1:701 2:702 192.203.2/24 TDSCA-NET-C-203-2 C:US 1:2149 2:174 192.203.3/24 TDSCA-NET-C-203-3 C:US 1:2149 2:174 192.203.4/24 TDSCA-NET-C-203-4 C:US 1:2149 2:174 192.203.5/24 TDSCA-NET-C-203-5 C:US 1:2149 2:174 192.203.6/23 INTERVAL-NET1 C:US 1:701 2:702 192.203.46/23 VERITAS-1 C:US 1:1957 192.203.56/21 CSI-NET1 C:US 1:701 2:702 192.203.66/23 PROTOOLS-C1 C:US 1:701 2:702 192.203.72/23 FET-C-004 C:US 1:701 2:702 192.203.128/23 LARSE2-NET C:US 1:701 2:702 192.206.185/24 NET-IAI C:US 1:1800 2:1240 192.206.205/24 GMACM-CORP C:US 1:1957 192.206.206/23 GMACM-CORP2 C:US 1:1957 192.206.206/24 GMACM-CORP2 C:US 1:1957 192.206.207/24 GMACM-CORP3 C:US 1:1957 192.206.208/23 GMACM-CORP4 C:US 1:1957 192.206.208/24 GMACM-CORP4 C:US 1:1957 192.206.209/24 GMACM-CORP5 C:US 1:1957 192.206.210/24 GMACM-CORP6 C:US 1:1957 192.217.10/24 CHRYSYS2 C:US 1:1225 2:267 3:266 192.217.37/24 JALNET C:US 1:1225 2:267 3:266 192.221/16 NETBLK-SURA-SUB-PRJ C:US 1:86 2:279 192.228.32/19 KENTROX C:US 1:701 2:702 192.229.32/23 VERDIX C:US 1:701 2:702 192.231.173/24 EMPRESSUSNET C:US 1:2548 192.231.174/24 NET-EMPRESSUSRD C:US 1:2548 192.241.16/20 GMACM-CORP C:US 1:1957 192.241.16/24 NETBLK-GMACM-CORP C:US 1:1957 192.241.17/24 NETBLK-GMACM-CORP C:US 1:1957 192.241.18/24 NETBLK-GMACM-CORP C:US 1:1957 192.241.19/24 NETBLK-GMACM-CORP C:US 1:1957 192.241.20/24 NETBLK-GMACM-CORP C:US 1:1957 192.241.21/24 NETBLK-GMACM-CORP C:US 1:1957 192.241.22/24 NETBLK-GMACM-CORP C:US 1:1957 192.241.23/24 NETBLK-GMACM-CORP C:US 1:1957 192.241.24/24 NETBLK-GMACM-CORP C:US 1:1957 192.241.25/24 NETBLK-GMACM-CORP C:US 1:1957 192.241.26/24 NETBLK-GMACM-CORP C:US 1:1957 192.241.27/24 NETBLK-GMACM-CORP C:US 1:1957 192.241.28/24 NETBLK-GMACM-CORP C:US 1:1957 192.241.29/24 NETBLK-GMACM-CORP C:US 1:1957 192.241.30/24 NETBLK-GMACM-CORP C:US 1:1957 192.241.31/24 NETBLK-GMACM-CORP C:US 1:1957 192.243.179/24 TIPS179 C:US 1:209 2:210 192.243.180/24 TIPS180 C:US 1:209 2:210 192.243.184/24 TIPS184 C:US 1:209 2:210 192.243.186/24 TIPS186 C:US 1:209 2:210 192.243.187/24 TIPS187 C:US 1:209 2:210 192.245.122/23 ARRIS1 C:US 1:1957 192.245.124/23 ARRIS3 C:US 1:1957 192.251.132/22 PRENTICE2 C:US 1:701 2:702 192.254.16/20 GTSI16 C:US 1:701 2:702 193.1/16 HEANET-193-AGGR-1 C:IE 1:1133 2:1674 3:1800 193.17.8/22 EUMETSAT-C00 C:DE 1:1324 2:1800 3:1240 4:1133 193.22.64/20 BIB-LAN C:DE 1:1324 2:1800 3:1240 4:1133 193.26.136/21 PC-PLUS-NET C:DE 1:1324 2:1800 3:1240 4:1133 193.28.52/23 SYSPART-NET C:DE 1:1324 2:1800 3:1240 4:1133 193.48.205/24 REGION-PACA1 C:FR 1:1800 2:1240 3:1133 4:1674 193.52.115/24 FR-OR-NASAS1 C:FR 1:1800 2:1240 3:1133 4:1674 193.54.0/24 FR-NCY-CRRI C:FR 1:1800 2:1240 3:1133 4:1674 193.54.38/24 FR-NCY-GPLG C:FR 1:1800 2:1240 3:1133 4:1674 193.54.141/24 FR-TSINTERC2 C:FR 1:1800 2:1240 3:1133 4:1674 193.55.237/24 FR-CNRS-NCY C:FR 1:1800 2:1240 3:1133 4:1674 193.55.255/24 FR-NCY-VIDEO C:FR 1:1800 2:1240 3:1133 4:1674 193.59.66/24 CHEM-TUNIV-SZCZECIN-P C:PL 1:1800 2:1133 3:1240 193.59.67/24 MALOKA-BBS C:PL 1:1800 2:1133 3:1240 193.59.69/24 THESAR-LAN C:PL 1:1800 2:1133 3:1240 193.59.80/24 WSIZG-C-59-80 C:PL 1:1800 2:1133 3:1240 193.59.81/24 WSIZG-C-59-81 C:PL 1:1800 2:1133 3:1240 193.59.82/24 WSIZG-C-59-82 C:PL 1:1800 2:1133 3:1240 193.59.83/24 WSIZG-C-59-83 C:PL 1:1800 2:1133 3:1240 193.59.84/24 WSIZG-C-59-84 C:PL 1:1800 2:1133 3:1240 193.59.85/24 WSPZG-C-59-85 C:PL 1:1800 2:1133 3:1240 193.59.86/24 WSPZG-C-59-86 C:PL 1:1800 2:1133 3:1240 193.59.87/24 WSPZG-C-59-87 C:PL 1:1800 2:1133 3:1240 193.59.110/24 TUNET-C-59-110 C:PL 1:1800 2:1133 3:1240 193.59.111/24 TUNET-C-59-111 C:PL 1:1800 2:1133 3:1240 193.59.112/24 TUNET-C-59-112 C:PL 1:1800 2:1133 3:1240 193.59.113/24 TUNET-C-59-113 C:PL 1:1800 2:1133 3:1240 193.59.114/24 TUNET-C-59-114 C:PL 1:1800 2:1133 3:1240 193.59.115/24 TUNET-C-59-115 C:PL 1:1800 2:1133 3:1240 193.59.116/24 TUNET-C-59-116 C:PL 1:1800 2:1133 3:1240 193.59.117/24 TUNET-C-59-117 C:PL 1:1800 2:1133 3:1240 193.59.118/24 TUNET-C-59-118 C:PL 1:1800 2:1133 3:1240 193.59.119/24 TUNET-C-59-119 C:PL 1:1800 2:1133 3:1240 193.59.176/24 WIMAL-X25IP-NET C:PL 1:1800 2:1133 3:1240 193.74/16 EUNET-BE-193.74-AGG C:BE 1:701 2:1800 193.88.58/24 DECUSDK-NET C:DK 1:701 193.88.59/24 DECUSDK-NET C:DK 1:701 193.92.208/24 DUTHNET-1 C:GR 1:1800 2:1133 3:1240 193.92.209/24 DUTHNET-2 C:GR 1:1800 2:1133 3:1240 193.92.210/24 DUTHNET-3 C:GR 1:1800 2:1133 3:1240 193.92.211/24 DUTHNET-4 C:GR 1:1800 2:1133 3:1240 193.99.128/20 GUP-NET C:DE 1:1324 2:1800 3:1240 4:1133 193.125.147/24 KFRCNB C:RU 1:701 2:1800 193.166/16 FUNET-CIDR C:FI 1:1800 2:1879 3:1133 4:1240 193.204.114/23 IEN-NET C:IT 1:293 2:291 3:1133 4:1674 193.204.168/21 ARNO-MAN C:IT 1:293 2:291 3:1133 4:1674 193.204.216/21 GARR-P-P C:IT 1:293 2:291 3:1133 4:1674 193.204.224/20 ESRIN-IPNET C:IT 1:293 2:291 3:1133 4:1674 193.210.33/24 WIDER C:FI 1:1800 2:1879 3:1133 4:1240 193.233.7/24 INR-LAN C:RU 1:1800 2:1240 194.13.0/17 SURFNET-C-AGGR-2 C:NL 1:1800 2:1133 3:1674 4:1240 198.3.2/23 FNET-C-002 C:US 1:701 2:702 198.3.8/21 FILENET-C-001 C:US 1:1957 198.3.16/21 ODI-NET-16 C:US 1:701 2:702 198.3.24/22 ODI-NET-24 C:US 1:701 2:702 198.3.30/23 ODI-NET-30 C:US 1:701 2:702 198.3.32/22 NET-VICORP-1 C:US 1:701 2:702 198.3.38/23 DIGICON-HOU-2 C:US 1:1957 198.3.42/23 TELERATE-C-001 C:US 1:701 2:702 198.3.44/22 NCMSNET1 C:US 1:701 2:702 198.3.48/20 AWNET-2 C:US 1:701 2:702 198.3.64/20 DIGICON-HOU-4 C:US 1:1957 198.3.96/22 CSCINET1 C:US 1:701 2:702 198.3.104/21 AGILENET1 C:US 1:701 2:702 198.3.136/21 OEC-NET-1 C:US 1:701 2:702 198.3.144/22 NY-SHL-NET1 C:US 1:701 2:702 198.3.152/22 CPDSC-NET1 C:US 1:1957 198.3.160/23 EPR-NET1 C:US 1:701 2:702 198.3.176/20 SYLVEST-NET1 C:US 1:701 2:702 198.3.200/22 PENCOM-001 C:US 1:701 2:702 198.3.204/22 SHL-DC-204 C:US 1:701 2:702 198.3.212/22 ARTECON-NET1 C:US 1:701 2:702 198.3.216/22 ADRA-NET1 C:US 1:701 2:702 198.3.236/23 INSIGNIA1 C:US 1:701 2:702 198.3.248/22 PANVERSAL1 C:US 1:1957 198.4.4/22 COMPUSERVE-NET1 C:US 1:701 2:702 198.4.8/22 COMPUSERVE-NET5 C:US 1:701 2:702 198.4.32/20 RELL-NET1 C:US 1:1957 198.4.48/23 XYVISION-NET1 C:US 1:701 2:702 198.4.60/23 SJG-001 C:US 1:701 2:702 198.4.62/23 DEPUY-NET1 C:US 1:701 2:702 198.4.64/20 ICM-1 C:US 1:701 2:702 198.4.86/23 COGNISEIS-NET3 C:US 1:701 2:702 198.4.96/21 ESYSTEMS-001 C:US 1:701 2:702 198.4.104/22 POWERHOUSE1 C:US 1:701 2:702 198.4.108/22 MAGNA1 C:US 1:1957 198.4.118/23 PAE-NET-L1 C:US 1:701 2:702 198.4.124/22 WSC-001 C:US 1:701 2:702 198.4.166/23 IMCNET1 C:US 1:701 2:702 198.4.168/21 CSC-OIS-18 C:US 1:701 2:702 198.4.176/22 CURSCI-NET1 C:US 1:701 2:702 198.4.190/23 ARIELNET1 C:US 1:1957 198.4.192/22 SMSNET-001 C:US 1:1957 198.4.200/23 XOPEN1 C:GB 1:701 2:702 198.4.202/23 XOPEN3 C:GB 1:701 2:702 198.4.222/23 SEIKOTSI-NET15 C:US 1:701 2:702 198.4.224/20 PAGENET1 C:US 1:701 2:702 198.4.242/23 AERODYNE-1 C:US 1:701 2:702 198.5.6/23 BA-NET1 C:US 1:701 2:702 198.5.8/21 CCG-001 C:US 1:701 2:702 198.5.128/24 MITRE-01 C:US 1:701 2:702 198.5.129/24 MITRE-02 C:US 1:701 2:702 198.5.130/24 MITRE-03 C:US 1:701 2:702 198.5.131/24 MITRE-04 C:US 1:701 2:702 198.5.132/24 MITRE-05 C:US 1:701 2:702 198.5.133/24 MITRE-06 C:US 1:701 2:702 198.5.134/24 MITRE-07 C:US 1:701 2:702 198.5.135/24 MITRE-08 C:US 1:701 2:702 198.5.136/24 MITRE-09 C:US 1:701 2:702 198.5.137/24 MITRE-10 C:US 1:701 2:702 198.5.138/24 MITRE-11 C:US 1:701 2:702 198.5.139/24 MITRE-12 C:US 1:701 2:702 198.5.140/24 MITRE-13 C:US 1:701 2:702 198.5.141/24 MITRE-14 C:US 1:701 2:702 198.5.142/24 MITRE-15 C:US 1:701 2:702 198.5.143/24 MITRE-16 C:US 1:701 2:702 198.5.144/24 MITRE-17 C:US 1:701 2:702 198.5.145/24 MITRE-18 C:US 1:701 2:702 198.5.146/24 MITRE-19 C:US 1:701 2:702 198.5.147/24 MITRE-20 C:US 1:701 2:702 198.5.148/24 MITRE-21 C:US 1:701 2:702 198.5.149/24 MITRE-22 C:US 1:701 2:702 198.5.150/24 MITRE-23 C:US 1:701 2:702 198.5.151/24 MITRE-24 C:US 1:701 2:702 198.5.152/24 MITRE-25 C:US 1:701 2:702 198.5.153/24 MITRE-26 C:US 1:701 2:702 198.5.154/24 MITRE-27 C:US 1:701 2:702 198.5.155/24 MITRE-28 C:US 1:701 2:702 198.5.156/24 MITRE-29 C:US 1:701 2:702 198.5.157/24 MITRE-30 C:US 1:701 2:702 198.5.176/22 ORANGE-001 C:US 1:701 2:702 198.5.188/23 INTERET-NET C:US 1:1957 198.5.208/22 INFOSEEK1 C:US 1:701 2:702 198.5.212/22 ELECTRICITI-001 C:US 1:701 2:702 198.5.216/22 GWEMED-001 C:US 1:701 2:702 198.5.248/22 ASCEND2 C:US 1:701 2:702 198.6.4/22 AICHE-1 C:US 1:701 2:702 198.6.32/19 CPOINT1 C:US 1:701 2:702 198.6.64/23 NETMGRS-NET C:US 1:1957 198.6.80/20 UCG01 C:US 1:701 2:702 198.6.100/22 CAMPBELL1 C:US 1:1957 198.6.104/21 FCR-CBLK C:US 1:1957 198.6.114/23 INTAC C:US 1:701 2:702 198.6.116/23 PRPA-2 C:US 1:701 2:702 198.6.120/21 GKI-DOM C:US 1:701 2:702 198.6.193/24 DLBSYS-NET3 C:US 1:1957 198.6.199/24 NECX C:US 1:1957 198.6.226/23 SVCDUDES C:US 1:701 2:702 198.6.228/22 ISOCOR-NET1 C:US 1:701 2:702 198.6.232/21 METRO-OR C:US 1:701 2:702 198.6.240/22 METRO-OR C:US 1:701 2:702 198.6.248/23 ETAK C:US 1:1957 198.14.1/24 NET-HYBRID-2-1 C:US 1:2548 198.17.99/24 GRCNET2 C:US 1:1800 2:1240 198.37.32/21 RASTEROPS1 C:US 1:701 2:702 198.37.40/22 RASTEROPS9 C:US 1:701 2:702 198.37.44/23 RASTEROPS13 C:US 1:701 2:702 198.60.3/24 WESTNET C:US 1:210 2:209 198.60.235/24 WESTNET C:US 1:210 2:209 198.62.174/24 NET-DTIX C:US 1:1800 2:1240 198.76/16 NETBLK-CIDR-BLK-1 C:US 1:86 2:279 198.77/16 NETBLK-CIDR-BLK-2 C:US 1:86 2:279 198.77.84/24 NET-CAMSCI-C-77-84 C:US 1:86 2:279 198.77.85/24 NET-CAMSCI-C-77-85 C:US 1:86 2:279 198.77.96/24 VA-MCI-NET-C-77-96 C:US 1:86 2:279 198.77.97/24 VA-MCI-NET-C-77-97 C:US 1:86 2:279 198.77.98/24 VA-MCI-NET-C-77-98 C:US 1:86 2:279 198.77.99/24 VA-MCI-NET-C-77-99 C:US 1:86 2:279 198.77.100/24 VA-MCI-NET-C-77-100 C:US 1:86 2:279 198.77.101/24 VA-MCI-NET-C-77-101 C:US 1:86 2:279 198.77.102/24 VA-MCI-NET-C-77-102 C:US 1:86 2:279 198.77.103/24 VA-MCI-NET-C-77-103 C:US 1:86 2:279 198.77.112/24 ASPENSYS-C-77-112 C:US 1:86 2:279 198.77.113/24 ASPENSYS-C-77-113 C:US 1:86 2:279 198.77.114/24 ASPENSYS-C-77-114 C:US 1:86 2:279 198.77.115/24 ASPENSYS-C-77-115 C:US 1:86 2:279 198.78/16 NETBLK-CIDR-BLK-3 C:US 1:86 2:279 198.79/16 NETBLK-CIDR-BLK C:US 1:86 2:279 198.84.0/22 PROCASE1 C:US 1:701 2:702 198.99.239/24 PRESCISIONINT C:US 1:2551 198.102.72/24 TLH-MAN C:US 1:279 2:86 198.116.48/24 NSI-C-116-48 C:US 1:297 2:372 198.116.49/24 NSI-C-116-49 C:US 1:297 2:372 198.116.50/24 NSI-C-116-50 C:US 1:297 2:372 198.116.51/24 NSI-C-116-51 C:US 1:297 2:372 198.120.17/24 NSI C:US 1:372 2:297 198.138.213/24 JVNC-C1-NET214 C:US 1:97 198.147.128/24 SPEAKEZ C:US 1:1240 2:1800 198.147.130/23 HFM-NET2 C:US 1:1957 198.147.132/23 HFM-NET4 C:US 1:1957 198.160.154/24 CHRYSYS C:US 1:1225 2:267 3:266 198.161.2/24 CHILD-HOSP-AB-C-161-2 C:CA 1:602 2:601 3:603 198.161.3/24 CHILD-HOSP-AB-C-161-3 C:CA 1:602 2:601 3:603 198.161.4/24 CHILD-HOSP-AB-C-161-4 C:CA 1:602 2:601 3:603 198.162.68/24 STPAULS1 C:CA 1:602 2:601 3:603 198.182.210/23 SYKES C:US 1:701 2:702 198.182.221/24 NET-AZTECH C:US 1:1240 2:1800 198.186.8/21 KALEIDA-CNET-1 C:US 1:200 2:201 3:1740 198.188.134/24 CSUNET-SOUTH C:US 1:2150 2:200 3:201 198.206.244/24 CEI C:US 1:1329 198.217.64/19 ALTABATES C:US 1:701 2:702 198.217.96/20 ALTABATES C:US 1:701 2:702 198.217.112/23 ALTABATES C:US 1:701 2:702 198.247.242/24 ACTON C:US 1:93 198.252.137/24 NET-JCK-NET C:US 1:1800 2:1240 199.0.160/24 GHS.ORG-C-0-160 C:US 1:1800 2:1240 199.0.161/24 GHS.ORG-C-0-161 C:US 1:1800 2:1240 199.0.162/24 GHS.ORG-C-0-162 C:US 1:1800 2:1240 199.0.163/24 GHS.ORG-C-0-163 C:US 1:1800 2:1240 199.0.164/24 GHS.ORG-C-0-164 C:US 1:1800 2:1240 199.0.165/24 GHS.ORG-C-0-165 C:US 1:1800 2:1240 199.0.166/24 GHS.ORG-C-0-166 C:US 1:1800 2:1240 199.0.167/24 GHS.ORG-C-0-167 C:US 1:1800 2:1240 199.0.168/24 GHS.ORG-C-0-168 C:US 1:1800 2:1240 199.0.169/24 GHS.ORG-C-0-169 C:US 1:1800 2:1240 199.0.170/24 GHS.ORG-C-0-170 C:US 1:1800 2:1240 199.0.171/24 GHS.ORG-C-0-171 C:US 1:1800 2:1240 199.0.172/24 GHS.ORG-C-0-172 C:US 1:1800 2:1240 199.0.173/24 GHS.ORG-C-0-173 C:US 1:1800 2:1240 199.0.174/24 GHS.ORG-C-0-174 C:US 1:1800 2:1240 199.0.175/24 GHS.ORG-C-0-175 C:US 1:1800 2:1240 199.1.36/24 MEDIUM-DOM C:US 1:1240 2:1800 199.10.245/24 NAMRL-SUSOPS C:US 1:19 2:568 199.10.246/24 NAMRL-VISION C:US 1:19 2:568 199.10.247/24 NAMRL-OA C:US 1:19 2:568 199.10.252/24 FFSDMC-SD C:US 1:19 2:568 199.43.117/24 EMPRESSDIAL1 C:CA 1:701 2:702 199.60.99/24 INFOMATCH C:CA 1:602 2:601 3:603 199.68.64/24 NETBLK-GMACM C:US 1:1957 199.68.66/23 GMACM C:US 1:1957 199.68.66/24 NETBLK-GMACM C:US 1:1957 199.68.67/24 NETBLK-GMACM C:US 1:1957 199.68.68/22 GMACM C:US 1:1957 199.68.68/24 NETBLK-GMACM C:US 1:1957 199.68.69/24 NETBLK-GMACM C:US 1:1957 199.68.70/24 NETBLK-GMACM C:US 1:1957 199.68.71/24 NETBLK-GMACM C:US 1:1957 199.68.72/21 GMACM C:US 1:1957 199.68.72/24 NETBLK-GMACM C:US 1:1957 199.68.73/24 NETBLK-GMACM C:US 1:1957 199.68.74/24 NETBLK-GMACM C:US 1:1957 199.68.75/24 NETBLK-GMACM C:US 1:1957 199.68.76/24 NETBLK-GMACM C:US 1:1957 199.68.77/24 NETBLK-GMACM C:US 1:1957 199.68.78/24 NETBLK-GMACM C:US 1:1957 199.68.79/24 NETBLK-GMACM C:US 1:1957 199.68.80/20 GMACM C:US 1:1957 199.68.80/24 NETBLK-GMACM C:US 1:1957 199.68.81/24 NETBLK-GMACM C:US 1:1957 199.68.82/24 NETBLK-GMACM C:US 1:1957 199.68.83/24 NETBLK-GMACM C:US 1:1957 199.68.84/24 NETBLK-GMACM C:US 1:1957 199.68.85/24 NETBLK-GMACM C:US 1:1957 199.68.86/24 NETBLK-GMACM C:US 1:1957 199.68.87/24 NETBLK-GMACM C:US 1:1957 199.68.88/24 NETBLK-GMACM C:US 1:1957 199.68.89/24 NETBLK-GMACM C:US 1:1957 199.68.90/24 NETBLK-GMACM C:US 1:1957 199.68.91/24 NETBLK-GMACM C:US 1:1957 199.68.92/24 NETBLK-GMACM C:US 1:1957 199.68.93/24 NETBLK-GMACM C:US 1:1957 199.68.94/24 NETBLK-GMACM C:US 1:1957 199.68.95/24 NETBLK-GMACM C:US 1:1957 199.68.96/22 GMACM C:US 1:1957 199.68.96/24 NETBLK-GMACM C:US 1:1957 199.68.97/24 NETBLK-GMACM C:US 1:1957 199.68.98/24 NETBLK-GMACM C:US 1:1957 199.68.99/24 NETBLK-GMACM C:US 1:1957 199.68.100/23 GMACM C:US 1:1957 199.68.100/24 NETBLK-GMACM C:US 1:1957 199.68.101/24 NETBLK-GMACM C:US 1:1957 199.73.36/24 CLARKNET-BLK1 C:US 1:1800 2:1240 199.74.222/24 NET-GRIFFIN C:US 1:1800 2:1240 199.76/16 NETBLK-SURA-CIDR-PRJ C:US 1:86 2:279 199.76.208/24 SJCSD-C-76-208 C:US 1:279 2:86 199.76.209/24 SJCSD-C-76-209 C:US 1:279 2:86 199.76.210/24 SJCSD-C-76-210 C:US 1:279 2:86 199.76.211/24 SJCSD-C-76-211 C:US 1:279 2:86 199.76.212/24 SJCSD-C-76-212 C:US 1:279 2:86 199.76.213/24 SJCSD-C-76-213 C:US 1:279 2:86 199.76.214/24 SJCSD-C-76-214 C:US 1:279 2:86 199.76.215/24 SJCSD-C-76-215 C:US 1:279 2:86 199.76.216/24 SJCSD-C-76-216 C:US 1:279 2:86 199.76.217/24 SJCSD-C-76-217 C:US 1:279 2:86 199.76.218/24 SJCSD-C-76-218 C:US 1:279 2:86 199.76.219/24 SJCSD-C-76-219 C:US 1:279 2:86 199.76.220/24 SJCSD-C-76-220 C:US 1:279 2:86 199.76.221/24 SJCSD-C-76-221 C:US 1:279 2:86 199.76.222/24 SJCSD-C-76-222 C:US 1:279 2:86 199.76.223/24 SJCSD-C-76-223 C:US 1:279 2:86 199.76.224/24 SJCSD-C-76-224 C:US 1:279 2:86 199.76.225/24 SJCSD-C-76-225 C:US 1:279 2:86 199.76.226/24 SJCSD-C-76-226 C:US 1:279 2:86 199.76.227/24 SJCSD-C-76-227 C:US 1:279 2:86 199.76.228/24 SJCSD-C-76-228 C:US 1:279 2:86 199.76.229/24 SJCSD-C-76-229 C:US 1:279 2:86 199.76.230/24 SJCSD-C-76-230 C:US 1:279 2:86 199.76.231/24 SJCSD-C-76-231 C:US 1:279 2:86 199.76.232/24 SJCSD-C-76-232 C:US 1:279 2:86 199.76.233/24 SJCSD-C-76-233 C:US 1:279 2:86 199.76.234/24 SJCSD-C-76-234 C:US 1:279 2:86 199.76.235/24 SJCSD-C-76-235 C:US 1:279 2:86 199.76.236/24 SJCSD-C-76-236 C:US 1:279 2:86 199.76.237/24 SJCSD-C-76-237 C:US 1:279 2:86 199.76.238/24 SJCSD-C-76-238 C:US 1:279 2:86 199.76.239/24 SJCSD-C-76-239 C:US 1:279 2:86 199.79.128/24 BASENET C:US 1:1240 2:1800 199.98.63/24 PSINET-C5-63 C:US 1:2149 2:174 199.98.159/24 PSINET-C5 C:KW 1:2149 2:174 199.98.160/24 TC-CATS-NET C:US 1:2149 2:174 199.98.161/24 PSINET-C5 C:US 1:2149 2:174 199.98.162/24 PSINET-C5 C:US 1:2149 2:174 199.98.163/24 PSINET-C5 C:US 1:2149 2:174 199.98.164/24 PSINET-C5 C:US 1:2149 2:174 199.98.166/24 PSINET-C5 C:US 1:2149 2:174 199.98.167/24 ARIEL-SDO-NET C:US 1:2149 2:174 199.98.168/24 MICROMASK-NET C:US 1:2149 2:174 199.98.169/24 VETERAN-AFFAIRS-NET C:US 1:2149 2:174 199.98.170/24 PSINET-C5 C:US 1:2149 2:174 199.98.171/24 PSINET-C5 C:US 1:2149 2:174 199.98.172/24 ADDENA-NET C:US 1:2149 2:174 199.98.173/24 OPNSYS-NET C:US 1:2149 2:174 199.100.0/24 PSINET-C5 C:US 1:2149 2:174 199.100.1/24 PSINET-C6 C:US 1:2149 2:174 199.100.2/24 PSINET-C7 C:US 1:2149 2:174 199.100.3/24 PSINET-C8 C:US 1:2149 2:174 199.100.4/24 PSINET-C9 C:US 1:2149 2:174 199.100.5/24 PSINET-C10 C:US 1:2149 2:174 199.114.16/20 CBCPH C:US 1:22 199.117.220/24 CSN-BLK3 C:US 1:209 2:210 199.117.221/24 CSN-BLK3 C:US 1:209 2:210 199.117.222/24 CSN-BLK3 C:US 1:209 2:210 199.164.129/24 EMPRESSDIAL2 C:US 1:2548 199.164.139/24 SYN-NET C:US 1:1800 2:1240 199.164.151/24 CONSTSF C:US 1:2551 199.164.213/24 INETSVCS C:US 1:1800 2:1240 199.165.245/24 NET-GREEN-DIAMOND-C1 C:US 1:1800 2:1240 199.170.8/21 NETEDGE C:US 1:1957 199.170.8/24 NETBLK-NETEDGE C:US 1:1957 199.170.9/24 NETBLK-NETEDGE C:US 1:1957 199.170.10/24 NETBLK-NETEDGE C:US 1:1957 199.170.11/24 NETBLK-NETEDGE C:US 1:1957 199.170.12/24 NETBLK-NETEDGE C:US 1:1957 199.170.13/24 NETBLK-NETEDGE C:US 1:1957 199.170.14/24 NETBLK-NETEDGE C:US 1:1957 199.170.15/24 NETBLK-NETEDGE C:US 1:1957 199.170.17/24 ICONS C:US 1:1957 199.170.21/24 VDOSPK-NET C:US 1:1957 199.170.56/21 NACM-NET C:US 1:701 2:702 199.170.74/23 POWERHOUSE5 C:US 1:701 2:702 199.170.74/24 POWERHOUSE5 C:US 1:701 2:702 199.170.75/24 POWERHOUSE6 C:US 1:701 2:702 199.170.103/24 NET-PSMFCNET C:US 1:701 2:702 199.175.64/24 STPAULSNET C:CA 1:602 2:601 3:603 199.175.80/24 STPAULSNET C:CA 1:602 2:601 3:603 199.175.95/24 STPAULSNET C:CA 1:602 2:601 3:603 199.181.234/24 MEDIMPACT-NET C:US 1:1240 2:1800 199.184.16/24 WADSWORTH C:US 1:1324 199.186.16/24 NETBLOCK-ATT C:US 1:2386 2:1321 199.186.17/24 NETBLOCK-ATT C:US 1:2386 2:1321 199.236/14 NWNET-BLK4 C:US 1:685 2:73 3:101 200.9.127/24 PRODEMG-ANMG C:BR 1:293 2:291 Deletions: --192.244.224/24 KITNET1 C:JP 1:97 --192.244.225/24 KITNET2 C:JP 1:97 --192.244.226/24 KITNET3 C:JP 1:97 --192.244.227/24 KITNET4 C:JP 1:97 --193.74.1/24 EUNET-BE C:BE 1:1957 --193.74.168/24 BKRT-C-74-168 C:BE 1:1957 --193.74.169/24 BKRT-C-74-169 C:BE 1:1957 --193.74.170/24 BKRT-C-74-170 C:BE 1:1957 --193.74.171/24 BKRT-C-74-171 C:BE 1:1957 --193.74.172/24 BKRT-C-74-172 C:BE 1:1957 --193.74.173/24 BKRT-C-74-173 C:BE 1:1957 --193.74.174/24 BKRT-C-74-174 C:BE 1:1957 --193.74.175/24 BKRT-C-74-175 C:BE 1:1957 --193.74.176/24 TWGEUR-C-74-176 C:BE 1:1957 --193.74.177/24 TWGEUR-C-74-177 C:BE 1:1957 --193.74.192/24 ACSET C:BE 1:1957 --193.74.193/24 ACSET C:BE 1:1957 --193.74.194/24 ACSET C:BE 1:1957 --193.74.195/24 ACSET C:BE 1:1957 --193.74.200/24 LHS-BE-C-74-200 C:BE 1:1957 --193.74.201/24 LHS-BE-C-74-201 C:BE 1:1957 --193.74.232/24 EUNET-BE C:BE 1:1957 --193.74.234/24 MAXON-INT C:BE 1:1957 --193.74.235/24 MAXON-INT C:BE 1:1957 --193.74.236/24 FERRANTI C:BE 1:1957 --193.74.237/24 FERRANTI C:BE 1:1957 --193.74.238/24 ABCOMP C:BE 1:1957 --193.74.239/24 ABCOMP C:BE 1:1957 --193.74.240/24 COIBE C:BE 1:1957 --193.74.242/24 ALPHABIT-BE C:BE 1:1957 --193.74.249/24 STERLBRU C:BE 1:1957 --193.74.251/24 EUNET-BE C:BE 1:1957 --193.74.252/24 CIMINKO C:BE 1:1957 --193.74.254/24 EUNET-BE C:BE 1:1957 --198.211.55/24 NETCOM-C-211-55 C:US 1:1957 --198.211.76/24 WALKER3 C:US 1:1957 --198.211.194/24 PRCPSI-C-211-194 C:US 1:1957 Expanded listing, sorted by country, then by organization: ========================================================== Belgium ------- Commission of the European Communities, Joint Research Centre, Institute for Reference Materials and Measurements, Retieseweg, Geel, B-2440, BELGIUM 1:293 Energy Science Network (FIX-East) 2:291 Energy Science Network (FIX-West) -------------- 192.156.132/24 CEC-JRC-IRMM (BE) EUnet Belgium NV/SA, Stapelhuisstraat 13, B-3000 Leuven, BELGIUM 1:701 Alternet 2:1800 ICM-Atlantic ------------- 192.64.100/22 EUNET-BE-192.64.100-A (BE) 192.78.186/23 EUNET-BE-192.78.186-A (BE) 192.92.130/23 EUNET-BE-192.92.130-A (BE) 193.74/16 EUNET-BE-193.74-AGG (BE) Brazil ------ Cia de Processamento de dados do estado de Minas Gerais, Rua da Bahia, 2277 - Bairro Lourdes, Belo Horizonte, Minas Gerais (MG), 30160-012, BRAZIL 1:293 Energy Science Network (FIX-East) 2:291 Energy Science Network (FIX-West) ------------ 200.9.127/24 PRODEMG-ANMG (BR) Canada ------ Alberta General Provincial Children's Hospital, 1820 Richmond Road SW, Calgary, AB, T2T 5C7, CANADA 1:602 CA*net in Vancouver 2:601 CA*net in Toronto 3:603 CA*net in Montreal ------------ 198.161.2/24 CHILD-HOSP-AB-C-161-2 (CA) 198.161.3/24 CHILD-HOSP-AB-C-161-3 (CA) 198.161.4/24 CHILD-HOSP-AB-C-161-4 (CA) Empress Software Inc., 3100 Steeles Ave. E. Suite 300, Markham, ON, L3R 4T3, CANADA 1:701 Alternet 2:702 Alternet ------------- 199.43.117/24 EMPRESSDIAL1 (CA) InfoMatch Communications Inc., 1922 Ashley Grove, Burnaby, BC, V5A 4A2, CANADA 1:602 CA*net in Vancouver 2:601 CA*net in Toronto 3:603 CA*net in Montreal ------------ 199.60.99/24 INFOMATCH (CA) SCO Canada, Inc., 130 Bloor St. West, Ste. 1001, Toronto, ON, M5S 1N5, CANADA 1:701 Alternet 2:702 Alternet -------------- 192.138.128/23 SCOTOR1 (CA) St. Paul's Hospital, 1081 Burrard Street, Vancouver, BC, V6Z 1Y6, CANADA 1:602 CA*net in Vancouver 2:601 CA*net in Toronto 3:603 CA*net in Montreal ------------- 198.162.68/24 STPAULS1 (CA) 199.175.64/24 STPAULSNET (CA) 199.175.80/24 STPAULSNET (CA) 199.175.95/24 STPAULSNET (CA) Denmark ------- DECUS (Digital Equipment Computer Users Society), erik mainz a/s, Dortheavej 7, DK-2400 Koebenhavn NV, DENMARK 1:701 Alternet ------------ 193.88.58/24 DECUSDK-NET (DK) 193.88.59/24 DECUSDK-NET (DK) Finland ------- FUNET c/o VTKK, P.O. BOX 405, FIN-02101 ESPOO, FINLAND 1:1800 ICM-Atlantic 2:1879 EUROPE-RS 3:1133 CERN/DANTE 4:1240 ICM-Pacific ---------- 193.166/16 FUNET-CIDR (FI) UNU/WIDER, Katajanokanlaituri 6 B, FIN-00160 Helsinki, FINLAND 1:1800 ICM-Atlantic 2:1879 EUROPE-RS 3:1133 CERN/DANTE 4:1240 ICM-Pacific ------------- 193.210.33/24 WIDER (FI) France ------ CRRI/Centre Regional de Recherche Image, 9, rue Michel Ney - BP 3329, 54014 Nancy CEDEX, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ----------- 193.54.0/24 FR-NCY-CRRI (FR) Conseil Regional Provence Alpes Cote d'Azur, 27 Place Jules Guesde, 13481 Marseille CEDEX 20, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ------------- 193.48.205/24 REGION-PACA1 (FR) Delegation Regionale du CNRS du Nord-Est, 8 rue baron Louis BP 30, 54002 Nancy, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ------------- 193.55.237/24 FR-CNRS-NCY (FR) France Telecom, 9 Rue de Nanteuil, 75015 Paris, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ------------- 193.54.141/24 FR-TSINTERC2 (FR) INPL, 2, Avenue de la Foret de Haye, BP 3, 54501 Vandoeuvre-les-Nancy CEDEX, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ------------- 192.93.181/24 FNET-INPL (FR) Pole Lorrain De Gestion - Universite de NANCY II, 13 Rue Michel NEY, 54037 NANCY Cedex, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ------------ 193.54.38/24 FR-NCY-GPLG (FR) UFR Medecine Hotel-Dieu, 1 Rue Gaston Veil, 44035 Nantes CEDEX 01, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ------------- 193.52.115/24 FR-OR-NASAS1 (FR) Videoscop - Universite NANCY 2, 9, rue Michel Ney , BP 722, 54064 Nancy CEDEX, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ------------- 193.55.255/24 FR-NCY-VIDEO (FR) Germany ------- Bildungszentrum fuer informationsverarbeitende Berufe e.V., Hauptstrasse 2, D-50935 Bergisch Gladbach, Bergisch, GERMANY 1:1324 ANS New York City - DNSS 35 2:1800 ICM-Atlantic 3:1240 ICM-Pacific 4:1133 CERN/DANTE ------------ 193.22.64/20 BIB-LAN (DE) EUMETSAT, Am Elfengrund 45, D-64297 Darmstadt, GERMANY 1:1324 ANS New York City - DNSS 35 2:1800 ICM-Atlantic 3:1240 ICM-Pacific 4:1133 CERN/DANTE ----------- 193.17.8/22 EUMETSAT-C00 (DE) Garmhausen und Partner GmbH, Endenicher Str. 81, D-53115 Bonn, GERMANY 1:1324 ANS New York City - DNSS 35 2:1800 ICM-Atlantic 3:1240 ICM-Pacific 4:1133 CERN/DANTE ------------- 193.99.128/20 GUP-NET (DE) Hartmann & Braun AG, Graefstr. 97, D-60487 Frankfurt am Main, Frankfurt, GERMANY 1:1324 ANS New York City - DNSS 35 2:1800 ICM-Atlantic 3:1240 ICM-Pacific 4:1133 CERN/DANTE ------------ 192.125.2/23 HARTMANN-1-40 (DE) 192.125.4/22 HARTMANN-1-40 (DE) 192.125.8/21 HARTMANN-1-40 (DE) 192.125.16/20 HARTMANN-1-40 (DE) 192.125.32/21 HARTMANN-1-40 (DE) SystemPartner Moeller u. Hellwig, Suederstrasse 345b, D-20537 Hamburg, GERMANY 1:1324 ANS New York City - DNSS 35 2:1800 ICM-Atlantic 3:1240 ICM-Pacific 4:1133 CERN/DANTE ------------ 193.28.52/23 SYSPART-NET (DE) TU Berlin, Franklinstr. 28/29, D-W-1000 Berlin 10, GERMANY 1:701 Alternet 2:1800 ICM-Atlantic --------- 141.23/16 CSTUB (DE) pc-plus GmbH, Schlierseestrasse 73, D-81539 Muenchen, GERMANY 1:1324 ANS New York City - DNSS 35 2:1800 ICM-Atlantic 3:1240 ICM-Pacific 4:1133 CERN/DANTE ------------- 193.26.136/21 PC-PLUS-NET (DE) Greece ------ Democritus University of Thraki, Electrical Engineering Dept., Xanthi, 67100, GREECE 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific ------------- 193.92.208/24 DUTHNET-1 (GR) 193.92.209/24 DUTHNET-2 (GR) 193.92.210/24 DUTHNET-3 (GR) 193.92.211/24 DUTHNET-4 (GR) Ireland ------- HEAnet, 21 Fitzwilliam Square, Dublin 2, IRELAND 1:1133 CERN/DANTE 2:1674 CERN/DANTE 3:1800 ICM-Atlantic -------- 193.1/16 HEANET-193-AGGR-1 (IE) Italy ----- Consiglio Nazionale delle ricerche-CNUCE, Via S.Maria, 32, Pisa, I-00044, ITALY 1:293 Energy Science Network (FIX-East) 2:291 Energy Science Network (FIX-West) 3:1133 CERN/DANTE 4:1674 CERN/DANTE -------------- 193.204.168/21 ARNO-MAN (IT) ESA-ESRIN, Via Galileo Galilei, Frascati, I-00044, ITALY 1:293 Energy Science Network (FIX-East) 2:291 Energy Science Network (FIX-West) 3:1133 CERN/DANTE 4:1674 CERN/DANTE -------------- 193.204.224/20 ESRIN-IPNET (IT) GARR-CNUCE, Via Santa Maria, 36, Pisa, I-56126, ITALY 1:293 Energy Science Network (FIX-East) 2:291 Energy Science Network (FIX-West) 3:1133 CERN/DANTE 4:1674 CERN/DANTE -------------- 193.204.216/21 GARR-P-P (IT) Istituto Elettrotecnico Nazionale Galileo Ferraris, Strada delle cacce, 91, Torino, I-10135, ITALY 1:293 Energy Science Network (FIX-East) 2:291 Energy Science Network (FIX-West) 3:1133 CERN/DANTE 4:1674 CERN/DANTE -------------- 193.204.114/23 IEN-NET (IT) Universita' di Messina, P.za Pugliatti, Messina, I-98100, ITALY 1:293 Energy Science Network (FIX-East) 2:291 Energy Science Network (FIX-West) 3:1133 CERN/DANTE 4:1674 CERN/DANTE ------------- 192.167.96/20 MESSINA-NET (IT) Japan ----- NTT Data Communications Systems Corporation, Kowa Kawasaki Nishi-guchi Building, 66-2, Horikawa-cho, Saiwai-ku, Kawasaki-shi, Kanagawa 210, JAPAN 1:1957 ANSCIX-AS ------------ 192.58.98/23 NTTDATA-02 (JP) 192.58.100/23 NTTDATA-04 (JP) Kuwait ------ International Turnkey Systems, P.O. Box 26729 Safat, 13128, KUWAIT 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.159/24 PSINET-C5 (KW) Mexico ------ Pixel Internacional, Rio Amazonas 331, Monterrey, Nuevo Leon, MEXICO 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1328 ANS Houston - DNSS 67 -------------- 192.100.203/24 PIXEL (MX) UNIVERSIDAD AUTONOMA DE BAJA CALIFORNIA, Av. Alvaro Obregon y J Julian, Carrillo S/N, Mexicali, BC, MEXICO 1:2150 CSUNET-SW 2:200 BARRNet 3:201 BARRNet ---------- 148.231/16 UABC (MX) Netherlands ----------- SURFnet, P.O. Box 19035, NL-3501 DA Utrecht, NETHERLANDS 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1674 CERN/DANTE 4:1240 ICM-Pacific ----------- 194.13.0/17 SURFNET-C-AGGR-2 (NL) Norway ------ TBK A/S, Ilderveien 10, Box 1206 Oterveien, N-2201 Kongsvinger, NORWAY 1:1800 ICM-Atlantic 2:1879 EUROPE-RS 3:1133 CERN/DANTE 4:1240 ICM-Pacific ---------- 146.172/16 TBKINTERNET (NO) Poland ------ Maloka BBS, Lesna 14, 05-806 Komorow, POLAND 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific ------------ 193.59.67/24 MALOKA-BBS (PL) Ministry of Finance, Department of Informatics, Swietokrzyska 12, 00-916 Warszawa, POLAND 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific ---------- 145.237/16 POLFIN (PL) Technical University of Szczecin, Polymer Institute, Pulaskiego 10, 70-322 Szczecin, POLAND 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific ------------ 193.59.66/24 CHEM-TUNIV-SZCZECIN-P (PL) 193.59.110/24 TUNET-C-59-110 (PL) 193.59.111/24 TUNET-C-59-111 (PL) 193.59.112/24 TUNET-C-59-112 (PL) 193.59.113/24 TUNET-C-59-113 (PL) 193.59.114/24 TUNET-C-59-114 (PL) 193.59.115/24 TUNET-C-59-115 (PL) 193.59.116/24 TUNET-C-59-116 (PL) 193.59.117/24 TUNET-C-59-117 (PL) 193.59.118/24 TUNET-C-59-118 (PL) 193.59.119/24 TUNET-C-59-119 (PL) Technical University of Zielona Gora, Podgorna 50, 65-246 Zielona Gora, POLAND 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific ------------ 193.59.80/24 WSIZG-C-59-80 (PL) 193.59.81/24 WSIZG-C-59-81 (PL) 193.59.82/24 WSIZG-C-59-82 (PL) 193.59.83/24 WSIZG-C-59-83 (PL) 193.59.84/24 WSIZG-C-59-84 (PL) 193.59.85/24 WSPZG-C-59-85 (PL) 193.59.86/24 WSPZG-C-59-86 (PL) 193.59.87/24 WSPZG-C-59-87 (PL) Thesar LTD., 00-355 Warszawa, ul. Tamka 49, XIVp., POLAND 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific ------------ 193.59.69/24 THESAR-LAN (PL) Wimal Int., Sniadeckich 17, 00-654 Warszawa, POLAND 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific ------------- 193.59.176/24 WIMAL-X25IP-NET (PL) Russian Federation ------------------ Institute for Nuclear Research RAS, 60th October Anniversary prospect 7a, Moscow, 117312, RUSSIAN FEDERATION 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ------------ 193.233.7/24 INR-LAN (RU) Kamchatsky Filial of Russian Commercial Bank, Leninskaya 18, Petropavlovsk-Kamchatsky, RUSSIAN FEDERATION 1:701 Alternet 2:1800 ICM-Atlantic -------------- 193.125.147/24 KFRCNB (RU) United Kingdom -------------- The X/Open Company Limited, Apex Plaza, Forbury Road, Reading, Berkshire, UNITED KINGDOM 1:701 Alternet 2:702 Alternet ------------ 198.4.200/23 XOPEN1 (GB) 198.4.202/23 XOPEN3 (GB) United States ------------- ARRIS Pharmaceutical Corporation, 385 Oyster Point Blvd., Suite 12, South San Francisco, CA 94080, USA 1:1957 ANSCIX-AS -------------- 192.245.122/23 ARRIS1 (US) 192.245.124/23 ARRIS3 (US) AT&T Data Communication Services, 5000 Hadley Rd, South Plainfield, NJ 07080, USA 1:2386 INS-AS 2:1321 ANS San Francisco - DNSS 11 ------------- 199.186.16/24 NETBLOCK-ATT (US) 199.186.17/24 NETBLOCK-ATT (US) AZTech Consultants, 737 E. 10th St., Tucson, AZ 85719, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic -------------- 198.182.221/24 NET-AZTECH (US) Acton LTD, 4900 Highway 77 North, Lincoln, NE 68505, USA 1:93 MIDnet -------------- 198.247.242/24 ACTON (US) Addena Corp., 1725 Jeff Davis Highway, Suite 1010, Arlington, VA 22202, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.172/24 ADDENA-NET (US) Addison-Wesley Publishing Company, 7 Jacob Way, Reading, MA 01867, USA 1:701 Alternet 2:702 Alternet ----------- 198.3.48/20 AWNET-2 (US) Adra Systems, Inc., 59 Technology Drive, Lowell, MA 01851, USA 1:701 Alternet 2:702 Alternet ------------ 198.3.216/22 ADRA-NET1 (US) Aerodyne Research, Inc., 45 Manning Road, Billerica, MA 01821, USA 1:701 Alternet 2:702 Alternet ------------ 198.4.242/23 AERODYNE-1 (US) Agile Networks, Inc., 200 Baker Avenue, Concord, MA 01742, USA 1:701 Alternet 2:702 Alternet ------------ 198.3.104/21 AGILENET1 (US) Alta Bates Medical Center, 2850 Telegraph Avenue, Third Floor, Berkeley, CA 94705, USA 1:701 Alternet 2:702 Alternet ------------- 198.217.64/19 ALTABATES (US) 198.217.96/20 ALTABATES (US) 198.217.112/23 ALTABATES (US) Aluminum Extrusion Consultant Inc., 1216 Fair Oaks Drive, Irving, TX 75060, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ----------- 199.1.36/24 MEDIUM-DOM (US) American Institure of Chemical Engineers, 345 East 47th Street, Second Floor, New York, NY 10017, USA 1:701 Alternet 2:702 Alternet ---------- 198.6.4/22 AICHE-1 (US) Ariel Corporation, 1140 West Bernardo Ct., Suite 290, San Diego, CA 92127-1643, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.167/24 ARIEL-SDO-NET (US) Ariel Corporation, 433 River Road, Highland Park, NJ 08904, USA 1:1957 ANSCIX-AS ------------ 198.4.190/23 ARIELNET1 (US) Artecon, Inc., 6305 El Camino Real, Carlsbad, CA 92008, USA 1:701 Alternet 2:702 Alternet ------------ 198.3.212/22 ARTECON-NET1 (US) Ascend Communications Inc., 1275 Harbor Bay Parkway, Alameda, CA 94501, USA 1:701 Alternet 2:702 Alternet ------------ 198.5.248/22 ASCEND2 (US) Aspen Systems Corp, 1600 Research Blvd, Rockville, MD 20850, USA 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) ------------- 198.77.112/24 ASPENSYS-C-77-112 (US) 198.77.113/24 ASPENSYS-C-77-113 (US) 198.77.114/24 ASPENSYS-C-77-114 (US) 198.77.115/24 ASPENSYS-C-77-115 (US) Basenet, 2260 Rock Street #G, Mountain View, CA 94043, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ------------- 199.79.128/24 BASENET (US) CSC-Intelicom Inc., 500 Helendale Road, Rochester, NY 14609, USA 1:701 Alternet 2:702 Alternet ----------- 198.3.96/22 CSCINET1 (US) Cambridge Scientific Abstracts, 7200 Wisconsin Ave, Suite 601, Bethesda, MD 20814, USA 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) ------------ 198.77.84/24 NET-CAMSCI-C-77-84 (US) 198.77.85/24 NET-CAMSCI-C-77-85 (US) Camex, 75 Kneeland St., Boston, MA 02111, USA 1:2551 NETCOM --------- 134.54/16 CAMEX (US) Campbell & Co., Court Towers Building, 210 West Pennsylvania Avenue, Baltimore, MD 21204, USA 1:1957 ANSCIX-AS ------------ 198.6.100/22 CAMPBELL1 (US) Capital Area Internet Service, Pimmit Run Research, 6701 Lumsden Street, Suite 450, McLean, VA 22101, USA 1:701 Alternet 2:702 Alternet ---------- 198.5.6/23 BA-NET1 (US) Cellular Technical Services Company, 2401 Fourth Avenue; Suite #808, Seattle, WA 98121, USA 1:1982 Northwest Nexus --------- 165.22/16 CELTECH1 (US) Central Point Software, 15220 Northwest Greenbrier Parkway, Suite 150, Beaverton, OR 97006, USA 1:701 Alternet 2:702 Alternet ----------- 198.6.32/19 CPOINT1 (US) Chrysler Systems, 1 Tower Lane #2000, Oakbrook Terrace, IL 60181, USA 1:1225 CICNET at Argonne Labs 2:267 CICNET at UIUC 3:266 CICNET at MERIT ------------- 192.217.10/24 CHRYSYS2 (US) 198.160.154/24 CHRYSYS (US) CogniSeis Development, 2401 Portsmouth, Houston, TX 77098, USA 1:701 Alternet 2:702 Alternet ----------- 198.4.86/23 COGNISEIS-NET3 (US) Colgate-Palmolive Company, 909 River Road, PO Box 1343, Piscataway, NJ 08855-1343, USA 1:1957 ANSCIX-AS -------------- 192.132.217/24 COLGATE4 (US) Colorado SuperNet, Inc., Colorado School of Mines, 1500 Illinois, Golden, CO 80401, USA 1:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 2:210 Westnet Regional Network (Utah Attachment) - ENSS 142 -------------- 199.117.220/24 CSN-BLK3 (US) 199.117.221/24 CSN-BLK3 (US) 199.117.222/24 CSN-BLK3 (US) Comdisco Systems, Inc., 919 E. Hillsdale Blvd., Suite 300, Foster City, CA 94404, USA 1:701 Alternet 2:702 Alternet ------------- 192.203.56/21 CSI-NET1 (US) Compton Community College, 1111 E. Artesia, Compton, CA 90221, USA 1:2150 CSUNET-SW 2:200 BARRNet 3:201 BARRNet -------------- 198.188.134/24 CSUNET-SOUTH (US) CompuServe Incorporated, 5000 Arlington Centre Blvd, Columbus, OH 43220, USA 1:701 Alternet 2:702 Alternet ---------- 198.4.4/22 COMPUSERVE-NET1 (US) 198.4.8/22 COMPUSERVE-NET5 (US) Computational Engineering International, PO Box 14306, Research Triangle Park, NC 27709, USA 1:1329 ANS Greensboro - DNSS 75 -------------- 198.206.244/24 CEI (US) Computer Sciences Corporation, 3160 Fairview Park Drive, Falls Church, VA 22042, USA 1:701 Alternet 2:702 Alternet ------------ 198.4.168/21 CSC-OIS-18 (US) Computer Task Group, 800 Delaware Avenue, Buffalo, NY 14202, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------ 199.100.0/24 PSINET-C5 (US) 199.100.1/24 PSINET-C6 (US) 199.100.2/24 PSINET-C7 (US) 199.100.3/24 PSINET-C8 (US) 199.100.4/24 PSINET-C9 (US) 199.100.5/24 PSINET-C10 (US) Construction Market Data, 1550 Bryant St. #639, San Francisco, CA 94103, USA 1:2551 NETCOM -------------- 199.164.151/24 CONSTSF (US) Conway Computer Group, 6360 I-55 North, Jackson, MS 39211, USA 1:701 Alternet 2:702 Alternet ---------- 198.5.8/21 CCG-001 (US) Cummins Engine Company, Inc., 500 Jackson Street, Columbus, IN 47201, USA 1:701 Alternet 2:702 Alternet ------------- 192.158.32/23 CUMMINS-FS1 (US) Current Science, 20 North 3rd Street, 7th Floor, Philadelphia, PA 19106, USA 1:701 Alternet 2:702 Alternet ------------ 198.4.176/22 CURSCI-NET1 (US) DISO-UMF, 6760 East Irvington Place, Denver, CO 80279-1000, USA 1:19 Milnet (FIX-East) 2:568 Milnet (FIX-West) ------------- 199.10.252/24 FFSDMC-SD (US) DLB Systems, Inc., 110 Allen Road, Liberty Corner, NJ 07938, USA 1:1957 ANSCIX-AS ------------ 198.6.193/24 DLBSYS-NET3 (US) DSC Communications, 640 International Parkway, Richardson, TX 75081, USA 1:1957 ANSCIX-AS ------------ 198.3.152/22 CPDSC-NET1 (US) Data Highway, Inc., 256 Broad Avenue, Palisades Park, NJ 07650, USA 1:701 Alternet 2:702 Alternet ------------ 198.6.114/23 INTAC (US) DePuy Inc., 700 Orthopedic Drive, Warsaw, IN 46581-0988, USA 1:701 Alternet 2:702 Alternet ----------- 198.4.62/23 DEPUY-NET1 (US) Department of Veteran Affairs, 1670 Clairmont Rd., Decatur, GA 30033, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.169/24 VETERAN-AFFAIRS-NET (US) Digicon Geophysical, 3701 Kirby Drive, Houston, TX 77098, USA 1:1957 ANSCIX-AS ----------- 198.3.38/23 DIGICON-HOU-2 (US) 198.3.64/20 DIGICON-HOU-4 (US) Digital Technology, 43 Third Avenue, North West Park, Burlington, MA 01803, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ------------- 198.62.174/24 NET-DTIX (US) Dow Jones-Telerate, 2 Harborside Plaza, Jersey City, NJ 07311, USA 1:701 Alternet 2:702 Alternet ----------- 198.3.42/23 TELERATE-C-001 (US) Dr. Pepper/The Seven Up Co., 8144 Walnut Hill Lane, Dallas, TX 75231-8144, USA 1:701 Alternet 2:702 Alternet ------------- 192.154.10/23 DP7UP3 (US) E-Systems, Melpar Division, 7700 Arlington Blvd., Falls Church, VA 22046, USA 1:701 Alternet 2:702 Alternet ----------- 198.4.96/21 ESYSTEMS-001 (US) ETAK, Inc., 1430 O'Brien Drive, Menlo Park, CA 94025, USA 1:1957 ANSCIX-AS ------------ 198.6.248/23 ETAK (US) Eastman Kodak Co., Computational Science Lab, 1669 Lake Avenue, Rochester, NY 14650, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ---------- 150.221/16 KODAKB (US) ElectriCiti, 2171 India Street, Suite C, San Diego, CA 92101, USA 1:701 Alternet 2:702 Alternet ------------ 198.5.212/22 ELECTRICITI-001 (US) Electronic Publishing Resources, Inc., 2 Wisconsin Circle, Suite 700, Chevy Chase, MD 20814, USA 1:701 Alternet 2:702 Alternet ------------ 198.3.160/23 EPR-NET1 (US) Empress Software, Inc., 6401 Golden Triangle Drive, Greenbelt, MD 20770, USA 1:2548 DIGEX-AS -------------- 192.231.173/24 EMPRESSUSNET (US) 192.231.174/24 NET-EMPRESSUSRD (US) 199.164.129/24 EMPRESSDIAL2 (US) FCR Software, Inc., 398 Columbus Avenue, Suite 201, Boston, MA 02118, USA 1:1957 ANSCIX-AS ------------ 198.6.104/21 FCR-CBLK (US) FileNet Corporation, 3565 Harbor Blvd., Costa Mesa, CA 92626, USA 1:1957 ANSCIX-AS ---------- 198.3.8/21 FILENET-C-001 (US) First Quadrant, 800 East Colorado Ave, Suite 900, Pasadena, CA 91101, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.161/24 PSINET-C5 (US) Florida State University, 2035 E. Paul Dirac Dr., Tallahassee, FL 32310, USA 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) ------------- 198.102.72/24 TLH-MAN (US) Frame Technologies, 1010 Rincon Circle, San Jose, CA 95131, USA 1:701 Alternet 2:702 Alternet -------------- 192.108.252/23 FRAME-C1 (US) Furukawa Electric Technologies, Inc., 900 Lafayette St., Suite 401, Santa Clara, CA 95050, USA 1:701 Alternet 2:702 Alternet ------------- 192.203.72/23 FET-C-004 (US) 198.3.2/23 FNET-C-002 (US) GMAC Mortgage Corp., 8360 Old York Road, Elkins Park, PA 19117-1590, USA 1:1957 ANSCIX-AS -------------- 192.206.205/24 GMACM-CORP (US) 192.206.206/23 GMACM-CORP2 (US) 192.206.206/24 GMACM-CORP2 (US) 192.206.207/24 GMACM-CORP3 (US) 192.206.208/23 GMACM-CORP4 (US) 192.206.208/24 GMACM-CORP4 (US) 192.206.209/24 GMACM-CORP5 (US) 192.206.210/24 GMACM-CORP6 (US) 192.241.16/20 GMACM-CORP (US) 192.241.16/24 NETBLK-GMACM-CORP (US) 192.241.17/24 NETBLK-GMACM-CORP (US) 192.241.18/24 NETBLK-GMACM-CORP (US) 192.241.19/24 NETBLK-GMACM-CORP (US) 192.241.20/24 NETBLK-GMACM-CORP (US) 192.241.21/24 NETBLK-GMACM-CORP (US) 192.241.22/24 NETBLK-GMACM-CORP (US) 192.241.23/24 NETBLK-GMACM-CORP (US) 192.241.24/24 NETBLK-GMACM-CORP (US) 192.241.25/24 NETBLK-GMACM-CORP (US) 192.241.26/24 NETBLK-GMACM-CORP (US) 192.241.27/24 NETBLK-GMACM-CORP (US) 192.241.28/24 NETBLK-GMACM-CORP (US) 192.241.29/24 NETBLK-GMACM-CORP (US) 192.241.30/24 NETBLK-GMACM-CORP (US) 192.241.31/24 NETBLK-GMACM-CORP (US) 199.68.64/24 NETBLK-GMACM (US) 199.68.66/23 GMACM (US) 199.68.66/24 NETBLK-GMACM (US) 199.68.67/24 NETBLK-GMACM (US) 199.68.68/22 GMACM (US) 199.68.68/24 NETBLK-GMACM (US) 199.68.69/24 NETBLK-GMACM (US) 199.68.70/24 NETBLK-GMACM (US) 199.68.71/24 NETBLK-GMACM (US) 199.68.72/21 GMACM (US) 199.68.72/24 NETBLK-GMACM (US) 199.68.73/24 NETBLK-GMACM (US) 199.68.74/24 NETBLK-GMACM (US) 199.68.75/24 NETBLK-GMACM (US) 199.68.76/24 NETBLK-GMACM (US) 199.68.77/24 NETBLK-GMACM (US) 199.68.78/24 NETBLK-GMACM (US) 199.68.79/24 NETBLK-GMACM (US) 199.68.80/20 GMACM (US) 199.68.80/24 NETBLK-GMACM (US) 199.68.81/24 NETBLK-GMACM (US) 199.68.82/24 NETBLK-GMACM (US) 199.68.83/24 NETBLK-GMACM (US) 199.68.84/24 NETBLK-GMACM (US) 199.68.85/24 NETBLK-GMACM (US) 199.68.86/24 NETBLK-GMACM (US) 199.68.87/24 NETBLK-GMACM (US) 199.68.88/24 NETBLK-GMACM (US) 199.68.89/24 NETBLK-GMACM (US) 199.68.90/24 NETBLK-GMACM (US) 199.68.91/24 NETBLK-GMACM (US) 199.68.92/24 NETBLK-GMACM (US) 199.68.93/24 NETBLK-GMACM (US) 199.68.94/24 NETBLK-GMACM (US) 199.68.95/24 NETBLK-GMACM (US) 199.68.96/22 GMACM (US) 199.68.96/24 NETBLK-GMACM (US) 199.68.97/24 NETBLK-GMACM (US) 199.68.98/24 NETBLK-GMACM (US) 199.68.99/24 NETBLK-GMACM (US) 199.68.100/23 GMACM (US) 199.68.100/24 NETBLK-GMACM (US) 199.68.101/24 NETBLK-GMACM (US) GWU, Department of Emergency Medicine, 2140 Pennsylvania Ave., NW, Washington, DC 20037, USA 1:701 Alternet 2:702 Alternet ------------ 198.5.216/22 GWEMED-001 (US) General Kinetics Inc, 14130C Sully Field Circle, Chantilly, VA 22021, USA 1:701 Alternet 2:702 Alternet ------------ 198.6.120/21 GKI-DOM (US) General Research Corporation, 5383 Hollister Ave, Santa Barbara, CA 93111, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ------------ 198.17.99/24 GRCNET2 (US) Global Enterprise Services, Inc., 3 Independence Way, Princeton, NJ 08540, USA 1:97 JvNCnet Regional Network -------------- 198.138.213/24 JVNC-C1-NET214 (US) Government Technology Services, Inc, 4100 LaFayette Center Drive, Chantilly, VA 22021, USA 1:701 Alternet 2:702 Alternet ------------- 192.254.16/20 GTSI16 (US) Green Diamond Data, 11 Lincoln St, Natick, MA 01760, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific -------------- 199.165.245/24 NET-GREEN-DIAMOND-C1 (US) Greenville Hospital System, 701 Grove Road, Greenville, SC 29605, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ------------ 199.0.160/24 GHS.ORG-C-0-160 (US) 199.0.161/24 GHS.ORG-C-0-161 (US) 199.0.162/24 GHS.ORG-C-0-162 (US) 199.0.163/24 GHS.ORG-C-0-163 (US) 199.0.164/24 GHS.ORG-C-0-164 (US) 199.0.165/24 GHS.ORG-C-0-165 (US) 199.0.166/24 GHS.ORG-C-0-166 (US) 199.0.167/24 GHS.ORG-C-0-167 (US) 199.0.168/24 GHS.ORG-C-0-168 (US) 199.0.169/24 GHS.ORG-C-0-169 (US) 199.0.170/24 GHS.ORG-C-0-170 (US) 199.0.171/24 GHS.ORG-C-0-171 (US) 199.0.172/24 GHS.ORG-C-0-172 (US) 199.0.173/24 GHS.ORG-C-0-173 (US) 199.0.174/24 GHS.ORG-C-0-174 (US) 199.0.175/24 GHS.ORG-C-0-175 (US) Griffin Manufacturing, 37 Harvard St., Arlington, MA 02174-6017, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ------------- 199.74.222/24 NET-GRIFFIN (US) Harry's Farmers Market, 1180 Upper Hembree Road, Roswell, GA 30076, USA 1:1957 ANSCIX-AS -------------- 198.147.130/23 HFM-NET2 (US) 198.147.132/23 HFM-NET4 (US) Hewlett Packard, 3000 Minuteman Rd., Andover, MA 01810, USA 1:560 NEARnet Regional Network 2:200 BARRNet 3:201 BARRNet ---------- 192.6.3/24 HP-NETS4 (US) Hoya Micro Mask, Inc., 695 Vaqueros Avenue, Sunnyvale, CA 94086, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.168/24 MICROMASK-NET (US) Hybrid Networks, Inc., 20863 Stevens Creek Blvd, Suite 300, Cupertino, CA 95014, USA 1:2548 DIGEX-AS ----------- 198.14.1/24 NET-HYBRID-2-1 (US) Imatron Medical Imaging Network, 389 Oyster Point Boulevard, South San Franciso, CA 94080, USA 1:2551 NETCOM ------------- 192.58.248/24 IMATRON (US) InfoSeek, 2620 Augustine Drive, Suite 350, Santa Clara, CA 95050, USA 1:701 Alternet 2:702 Alternet ------------ 198.5.208/22 INFOSEEK1 (US) Information Management Company, 256 Campus Drive, P.O. Box 6446, Edison, NJ 08818-6446, USA 1:701 Alternet 2:702 Alternet ------------ 198.4.166/23 IMCNET1 (US) Insignia Solutions Inc, 1300 Charleston Avenue, Mountain View, CA 94043, USA 1:701 Alternet 2:702 Alternet ------------ 198.3.236/23 INSIGNIA1 (US) Integrated Architectures, Inc., 300 East Main Street Suite 207, Milford, MA 01757, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific -------------- 192.206.185/24 NET-IAI (US) Intellicom, 30 South First Avenue, Highland Park, NJ 08904, USA 1:701 Alternet 2:702 Alternet ----------- 198.4.64/20 ICM-1 (US) Interactive Development Environments, 595 Market Street, 12th Floor, San Francisco, CA 94105, USA 1:701 Alternet 2:702 Alternet ------------ 192.18.78/23 IDE-1 (US) 192.18.80/23 IDE-3 (US) Interactive MIS, 5001-4 Green Mountain Circle, Columbia, MD 21044, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ------------ 199.73.36/24 CLARKNET-BLK1 (US) Interet, Inc., 374 Millburn Avenue, Millburn, NJ 07041, USA 1:1957 ANSCIX-AS ------------ 198.5.188/23 INTERET-NET (US) Internet Consulting Corp., 92 Central Ave., New Brunswick, NJ 08901, USA 1:1957 ANSCIX-AS ------------- 199.170.17/24 ICONS (US) Internet Information Services, 13912 Saddleview Drive, North Potomac, MD 20879, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific -------------- 199.164.213/24 INETSVCS (US) Interval Research Corporation, 1801 Page Mill Road, Bldg. C, Palo Alto, CA 94304, USA 1:701 Alternet 2:702 Alternet ------------ 192.203.6/23 INTERVAL-NET1 (US) Isocor, 12011 San Vicente Blvd, Suite 500, Los Angeles, CA 90049, USA 1:701 Alternet 2:702 Alternet ------------ 198.6.228/22 ISOCOR-NET1 (US) John A. Logan Community College, Greenbriar Road, Carterville, IL 62918, USA 1:1225 CICNET at Argonne Labs 2:267 CICNET at UIUC 3:266 CICNET at MERIT ------------- 192.217.37/24 JALNET (US) John C. Klensin and Associates, PO Box 197, Cambridge, MA 02140, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific -------------- 198.252.137/24 NET-JCK-NET (US) Kaleida Labs, Inc., 1945 Charleston Road, Mountain View, CA 94041, USA 1:200 BARRNet 2:201 BARRNet 3:1740 CERFnet ------------ 198.186.8/21 KALEIDA-CNET-1 (US) Kentrox, 14375 NW Science Park Dr., Portland, OR 97229, USA 1:701 Alternet 2:702 Alternet ------------- 192.228.32/19 KENTROX (US) Keystone International, Inc., 9600 West Gulf Bank Road, Houston, TX 77240, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI -------- 170.9/16 KII (US) Larse Corporation, 4600 Patrick Henry Drive, Santa Clara, CA 95052-8138, USA 1:701 Alternet 2:702 Alternet ------------- 192.159.78/23 LARSE1-NET (US) 192.203.128/23 LARSE2-NET (US) Los Angeles Times, Times-Mirror Square, Los Angeles, CA 90053, USA 1:1957 ANSCIX-AS ------------- 192.187.66/23 LATIMES-3 (US) 192.187.68/22 LATIMES-5 (US) 192.187.72/21 LATIMES-9 (US) 192.187.80/20 LATIMES-17 (US) MAXM Systems Corporation, 1600 Spring Hill Road, Suite 400, Vienna, VA 22182, USA 1:701 Alternet 2:702 Alternet -------------- 192.195.208/23 ITM1 (US) MCI Telecommunications, 2100 Reston Parkway, Reston, VA 22091, USA 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) ------------ 198.77.96/24 VA-MCI-NET-C-77-96 (US) 198.77.97/24 VA-MCI-NET-C-77-97 (US) 198.77.98/24 VA-MCI-NET-C-77-98 (US) 198.77.99/24 VA-MCI-NET-C-77-99 (US) 198.77.100/24 VA-MCI-NET-C-77-100 (US) 198.77.101/24 VA-MCI-NET-C-77-101 (US) 198.77.102/24 VA-MCI-NET-C-77-102 (US) 198.77.103/24 VA-MCI-NET-C-77-103 (US) Magna Software Corporation, 12450 Fair Lakes Circle, Suite 315, Fairfax, VA 22033, USA 1:1957 ANSCIX-AS ------------ 198.4.108/22 MAGNA1 (US) Medimetrix Group, 1001 Lakeside Avenue, Suite 1500, Cleveland, OH 44114, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.162/24 PSINET-C5 (US) Medimpact, 10660 Scripps Ranch Blvd. Suite 100, San Diego, CA 92131, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic -------------- 199.181.234/24 MEDIMPACT-NET (US) Metro, 600 N.E. Grand Ave, Portland, OR 97232, USA 1:701 Alternet 2:702 Alternet ------------ 198.6.232/21 METRO-OR (US) 198.6.240/22 METRO-OR (US) NASA Ames Research Center, MS 233-8, Moffett Field, CA 95014, USA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------- 198.120.17/24 NSI (US) NASA Ames Research Center, Moffett Field, CA 95014, USA 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) ------------- 198.116.48/24 NSI-C-116-48 (US) 198.116.49/24 NSI-C-116-49 (US) 198.116.50/24 NSI-C-116-50 (US) 198.116.51/24 NSI-C-116-51 (US) NAVAL AEROSPACE MEDICAL RESEARCH LABRATORY, 51 HOVEY ROAD, PENSACOLA, FL 32508, USA 1:19 Milnet (FIX-East) 2:568 Milnet (FIX-West) ------------- 199.10.245/24 NAMRL-SUSOPS (US) 199.10.246/24 NAMRL-VISION (US) 199.10.247/24 NAMRL-OA (US) NECX, 4 Technology Drive, Peabody, OH 01960, USA 1:1957 ANSCIX-AS ------------ 198.6.199/24 NECX (US) National Center for Manufacturing Sciences, 900 Victors Way, Suite 310, Ann Arbor, MI 48108, USA 1:701 Alternet 2:702 Alternet ----------- 198.3.44/22 NCMSNET1 (US) Naval Construction Battalion Center, 1000 23rd St., Port Hueneme, CA 93043-4103, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.166/24 PSINET-C5 (US) NetEdge Systems, Inc., PO Box 14993, Research Triangle Park, NC 27709-4993, USA 1:1957 ANSCIX-AS ------------ 199.170.8/21 NETEDGE (US) 199.170.8/24 NETBLK-NETEDGE (US) 199.170.9/24 NETBLK-NETEDGE (US) 199.170.10/24 NETBLK-NETEDGE (US) 199.170.11/24 NETBLK-NETEDGE (US) 199.170.12/24 NETBLK-NETEDGE (US) 199.170.13/24 NETBLK-NETEDGE (US) 199.170.14/24 NETBLK-NETEDGE (US) 199.170.15/24 NETBLK-NETEDGE (US) Network Computing Devices, Inc., 350 North Bernado Avenue, Mountain View, CA 94043, USA 1:701 Alternet 2:702 Alternet ------------- 192.43.154/23 NCD-CNETS154 (US) 192.43.156/22 NCD-CNETS156 (US) Network Managers, 73 Princeton Street, Suite 305, North Chelmsford, MA 01863, USA 1:1957 ANSCIX-AS ----------- 198.6.64/23 NETMGRS-NET (US) Nicholas-Applegate Capital Management, 600 West Broadway, 29th Floor, San Diego, CA 92101, USA 1:701 Alternet 2:702 Alternet ------------- 199.170.56/21 NACM-NET (US) NorthWestNet, 15400 SE 30th Place Suite 202, Bellevue, WA 98007, USA 1:685 NorthWestNet Regional Network 2:73 NorthWestNet Regional Network 3:101 NorthWestNet Regional Network ---------- 199.236/14 NWNET-BLK4 (US) Object Design, Inc., 1 New England Executive Park, Burlington, MA 01803, USA 1:701 Alternet 2:702 Alternet ----------- 198.3.16/21 ODI-NET-16 (US) 198.3.24/22 ODI-NET-24 (US) 198.3.30/23 ODI-NET-30 (US) Open Environment Corporation, 219 Vassar St., Cambridge, MA 02139, USA 1:701 Alternet 2:702 Alternet ------------ 198.3.136/21 OEC-NET-1 (US) Open Systems Associates, Inc., 1801 Robert Fulton Drive, Suite 400, Reston, VA 22091, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.173/24 OPNSYS-NET (US) Orange Systems, 13 Firstfield Road, Gaithersburg, MD 20878, USA 1:701 Alternet 2:702 Alternet ------------ 198.5.176/22 ORANGE-001 (US) PAE Associates, 9056 Arlington Blvd., Fairfax, VA 22031, USA 1:701 Alternet 2:702 Alternet ------------ 198.4.118/23 PAE-NET-L1 (US) PROCASE Corporation, 2694 Orchard Parkway, San Jose, CA 95134, USA 1:701 Alternet 2:702 Alternet ----------- 198.84.0/22 PROCASE1 (US) Pacific States Marine Fisheries Commission, 45 S.E. 82nd Drive, Gladstone, OR 97027, USA 1:701 Alternet 2:702 Alternet -------------- 199.170.103/24 NET-PSMFCNET (US) PageMart, Inc., 6688 North Central Expressway, Suite 900, Dallas, TX 75206, USA 1:701 Alternet 2:702 Alternet ------------ 198.4.224/20 PAGENET1 (US) Panversal, P.O. Box 2184, Washington, DC 20013, USA 1:1957 ANSCIX-AS ------------ 198.3.248/22 PANVERSAL1 (US) Pencom Systems, Inc., 9050 Capital of Texas Highway North, Austin, TX 78759, USA 1:701 Alternet 2:702 Alternet ------------ 198.3.200/22 PENCOM-001 (US) Philips Research Palo Alto, 4005 Miranda Avenue, Suite 175, Palo Alto, CA 94306, USA 1:701 Alternet 2:702 Alternet ------------ 198.6.116/23 PRPA-2 (US) PowerHouse Systems, Inc., 123 Saginaw Drive, Redwood City, CA 94063, USA 1:701 Alternet 2:702 Alternet ------------ 198.4.104/22 POWERHOUSE1 (US) 199.170.74/23 POWERHOUSE5 (US) 199.170.74/24 POWERHOUSE5 (US) 199.170.75/24 POWERHOUSE6 (US) Precision Interconnect Corp., 16640 SW 72nd Avenue, Portland, OR 97224, USA 1:2551 NETCOM ------------- 198.99.239/24 PRESCISIONINT (US) Protools, 14976 N.W. Greenbrier Parkway, Beaverton, OR 97006, USA 1:701 Alternet 2:702 Alternet ------------- 192.203.66/23 PROTOOLS-C1 (US) Quintus Computer Systems, Inc, 2100 Geng Road, Suite 101, Palo Alto, CA 94303, USA 1:701 Alternet 2:702 Alternet -------------- 192.107.242/23 QUINTUS-NET2 (US) 192.107.244/23 QUINTUS-NET4 (US) RasterOps Corporation, 2500 Walsh Avenue, Santa Clara, CA 95051, USA 1:701 Alternet 2:702 Alternet ------------ 198.37.32/21 RASTEROPS1 (US) 198.37.40/22 RASTEROPS9 (US) 198.37.44/23 RASTEROPS13 (US) Richardson Electronics, Ltd., 40W267 Keslinger Road, LaFox, IL 60147, USA 1:1957 ANSCIX-AS ----------- 198.4.32/20 RELL-NET1 (US) SURAnet, 8400 Baltimore Blvd., College Park, MD 20740, USA 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) ---------- 192.221/16 NETBLK-SURA-SUB-PRJ (US) 198.76/16 NETBLK-CIDR-BLK-1 (US) 198.77/16 NETBLK-CIDR-BLK-2 (US) 198.78/16 NETBLK-CIDR-BLK-3 (US) 198.79/16 NETBLK-CIDR-BLK (US) 199.76/16 NETBLK-SURA-CIDR-PRJ (US) Santa Clara County, Office of the County Executive, Center for Urban Analysis, 70 West Hedding Street, 11th Floor, San Jose, CA 95110, USA 1:200 BARRNet 2:201 BARRNet --------- 146.74/16 SCCONET (US) Seiko Telecommunication Systems, Inc., 9205 SW Gemini Drive, Building 14A, Beaverton, OR 97005, USA 1:701 Alternet 2:702 Alternet ------------ 198.4.222/23 SEIKOTSI-NET15 (US) Select Technology, Inc., 246 First Street, Suite 401, San Francisco, CA 94105, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------ 199.98.63/24 PSINET-C5-63 (US) Simon & Schuster, 270 Sylvan Avenue, Englewood Cliffs, NJ 07632, USA 1:701 Alternet 2:702 Alternet -------------- 192.251.132/22 PRENTICE2 (US) Software Maintenance Specialists, Inc., 16680 Valley View Drive, La Miranda, CA 90638, USA 1:1957 ANSCIX-AS ------------ 198.4.192/22 SMSNET-001 (US) Software Ventures Corp., 2907 Claremont Ave., Berkeley, CA 94705, USA 1:701 Alternet 2:702 Alternet ------------ 198.6.226/23 SVCDUDES (US) SpeakEasy Software, 8947-A Complex Drive, San Diego, CA 92123, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic -------------- 198.147.128/24 SPEAKEZ (US) St. John's County School District, 40 Orange St., St. Augustine, FL 32084, USA 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) ------------- 199.76.208/24 SJCSD-C-76-208 (US) 199.76.209/24 SJCSD-C-76-209 (US) 199.76.210/24 SJCSD-C-76-210 (US) 199.76.211/24 SJCSD-C-76-211 (US) 199.76.212/24 SJCSD-C-76-212 (US) 199.76.213/24 SJCSD-C-76-213 (US) 199.76.214/24 SJCSD-C-76-214 (US) 199.76.215/24 SJCSD-C-76-215 (US) 199.76.216/24 SJCSD-C-76-216 (US) 199.76.217/24 SJCSD-C-76-217 (US) 199.76.218/24 SJCSD-C-76-218 (US) 199.76.219/24 SJCSD-C-76-219 (US) 199.76.220/24 SJCSD-C-76-220 (US) 199.76.221/24 SJCSD-C-76-221 (US) 199.76.222/24 SJCSD-C-76-222 (US) 199.76.223/24 SJCSD-C-76-223 (US) 199.76.224/24 SJCSD-C-76-224 (US) 199.76.225/24 SJCSD-C-76-225 (US) 199.76.226/24 SJCSD-C-76-226 (US) 199.76.227/24 SJCSD-C-76-227 (US) 199.76.228/24 SJCSD-C-76-228 (US) 199.76.229/24 SJCSD-C-76-229 (US) 199.76.230/24 SJCSD-C-76-230 (US) 199.76.231/24 SJCSD-C-76-231 (US) 199.76.232/24 SJCSD-C-76-232 (US) 199.76.233/24 SJCSD-C-76-233 (US) 199.76.234/24 SJCSD-C-76-234 (US) 199.76.235/24 SJCSD-C-76-235 (US) 199.76.236/24 SJCSD-C-76-236 (US) 199.76.237/24 SJCSD-C-76-237 (US) 199.76.238/24 SJCSD-C-76-238 (US) 199.76.239/24 SJCSD-C-76-239 (US) Steve Jackson Games, PO Box 18957, Austin, TX 78760, USA 1:701 Alternet 2:702 Alternet ----------- 198.4.60/23 SJG-001 (US) Superior Dairy, Inc, 4719 Navarre Rd, SW, Canton, OH 44718, USA 1:600 OARNET, Cleveland, OH 2:1800 ICM-Atlantic ------------- 192.68.141/24 NET-SD-SYSTEMS (US) Sybus Corporation, 2300 Tall Pines Drive, Suite 100, Largo, FL 34641, USA 1:701 Alternet 2:702 Alternet ------------- 192.103.16/22 NOKIA-US-1 (US) Sykes Enterprises, Inc., 510 Glenora Street, Sterling, CO 80751, USA 1:701 Alternet 2:702 Alternet -------------- 198.182.210/23 SYKES (US) Sylvest Management Systems, 1001 Derekwood Lane, Lanham, MD 20706, USA 1:701 Alternet 2:702 Alternet ------------ 198.3.176/20 SYLVEST-NET1 (US) SynErgo, 21515 Ridgetop Circle, Suite 300, Sterling, VA 20166, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.164/24 PSINET-C5 (US) Synergistics, Inc., 9 Tech Circle, Natick, MA 01760, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific -------------- 199.164.139/24 SYN-NET (US) Systemhouse, 25th Floor, 885 Third Avenue, New York, NY 10022, USA 1:701 Alternet 2:702 Alternet ------------ 198.3.144/22 NY-SHL-NET1 (US) Systemhouse, Inc., 1010 North Glebe Road, Arlington, VA 22201, USA 1:701 Alternet 2:702 Alternet ------------ 198.3.204/22 SHL-DC-204 (US) The MITRE Corporation, 7525 Colshire Drive, McLean, VA 22103, USA 1:701 Alternet 2:702 Alternet ------------ 198.5.128/24 MITRE-01 (US) 198.5.129/24 MITRE-02 (US) 198.5.130/24 MITRE-03 (US) 198.5.131/24 MITRE-04 (US) 198.5.132/24 MITRE-05 (US) 198.5.133/24 MITRE-06 (US) 198.5.134/24 MITRE-07 (US) 198.5.135/24 MITRE-08 (US) 198.5.136/24 MITRE-09 (US) 198.5.137/24 MITRE-10 (US) 198.5.138/24 MITRE-11 (US) 198.5.139/24 MITRE-12 (US) 198.5.140/24 MITRE-13 (US) 198.5.141/24 MITRE-14 (US) 198.5.142/24 MITRE-15 (US) 198.5.143/24 MITRE-16 (US) 198.5.144/24 MITRE-17 (US) 198.5.145/24 MITRE-18 (US) 198.5.146/24 MITRE-19 (US) 198.5.147/24 MITRE-20 (US) 198.5.148/24 MITRE-21 (US) 198.5.149/24 MITRE-22 (US) 198.5.150/24 MITRE-23 (US) 198.5.151/24 MITRE-24 (US) 198.5.152/24 MITRE-25 (US) 198.5.153/24 MITRE-26 (US) 198.5.154/24 MITRE-27 (US) 198.5.155/24 MITRE-28 (US) 198.5.156/24 MITRE-29 (US) 198.5.157/24 MITRE-30 (US) The Sage Colleges, 45 Ferry Street, Troy, NY 12180-4115, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.171/24 PSINET-C5 (US) Thompson Network Software, 15 Hamby Road, Marietta, GA 30066, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.163/24 PSINET-C5 (US) Transcription Enterprises, 101 Albright Way, Los Gatos, CA 95030, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.160/24 TC-CATS-NET (US) Trident Data Systems, 5933 w. Century Blvd., Suite 700, Los Angeles, CA 90045, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------ 192.203.2/24 TDSCA-NET-C-203-2 (US) 192.203.3/24 TDSCA-NET-C-203-3 (US) 192.203.4/24 TDSCA-NET-C-203-4 (US) 192.203.5/24 TDSCA-NET-C-203-5 (US) Truevision Inc., 7340 Shadeland Station, Indianapolis, IN 46256, USA 1:701 Alternet 2:702 Alternet -------------- 192.124.146/23 TRUEVISION-NET (US) U.S. Naval Construction Battalion Center, Port Hueneme, 1000 23rd Ave., Port Hueneme, CA 93043-4300, USA 1:22 NOSC (Naval Ocean Systems Center) ------------- 199.114.16/20 CBCPH (US) US Office of Surface Mining, 1020 15th Street, Denver, CO 80202, USA 1:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 2:210 Westnet Regional Network (Utah Attachment) - ENSS 142 -------------- 192.243.179/24 TIPS179 (US) 192.243.180/24 TIPS180 (US) 192.243.184/24 TIPS184 (US) 192.243.186/24 TIPS186 (US) 192.243.187/24 TIPS187 (US) United Communications Group, 11300 Rockville Pike, Suite 1100, Rockville, MD 20352-3030, USA 1:701 Alternet 2:702 Alternet ----------- 198.6.80/20 UCG01 (US) V. I. Corporation, 47 Pleasant Street, Northhampton, MA 01060, USA 1:701 Alternet 2:702 Alternet ----------- 198.3.32/22 NET-VICORP-1 (US) VERITAS Software, 4800 Great America Parkway, Suite 420, Santa Clara, CA 95054, USA 1:1957 ANSCIX-AS ------------- 192.203.46/23 VERITAS-1 (US) Verdix Corporation, 205 Van Buren St, Herndon, VA 22070, USA 1:701 Alternet 2:702 Alternet ------------- 192.229.32/23 VERDIX (US) Videospeak Systems, Inc., 250 South Cooper Street, Memphis, TN 38104, USA 1:1957 ANSCIX-AS ------------- 199.170.21/24 VDOSPK-NET (US) WSC Investment Services, Inc., 90 Broad Street 15th Floor, New York, NY 10004, USA 1:701 Alternet 2:702 Alternet ------------ 198.4.124/22 WSC-001 (US) Wadsworth Center, Empire State Plaza, Albany, NY 12201, USA 1:1324 ANS New York City - DNSS 35 ------------- 199.184.16/24 WADSWORTH (US) Westnet, 3645 Marine Street, U. of Colorado, Boulder, CO 80309-0455, USA 1:210 Westnet Regional Network (Utah Attachment) - ENSS 142 2:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 ----------- 198.60.3/24 WESTNET (US) 198.60.235/24 WESTNET (US) XYVision, Inc., 101 Edgewater Drive, Wakefield, MA 10880-1290, USA 1:701 Alternet 2:702 Alternet ----------- 198.4.48/23 XYVISION-NET1 (US) dcVAST Inc., 1327 Butterfield Road, Suite 610, Downers Grove, IL 60515, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.170/24 PSINET-C5 (US) Uruguay ------- Servicio Central de Informatica, Colonia 2066, Montevideo 11200, URUGUAY 1:1800 ICM-Atlantic 2:1240 ICM-Pacific --------- 164.73/16 RAU (UY) ========================================================== The following Midlevel/Regional peering sessions have also been added: AS 267 - CICNET at UIUC (US) - ENSS 129 Peer: 192.17.2.10 - ENSS 129 - CICnet, Champaign, Illinois - uiuc-lan1.cic.net AS 2493 - FONOROLA-EAST (CA) - DNSS 36 Peer: 192.103.63.2 - fONOROLA, 250 Albert St., Suite 205, Ottawa, Ontario, K1P-6M1, CANADA - fono-east ========================================================== 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.t3p Information is also avaiable through the PRDB whois server. Type "whois -h prdb.merit.edu help" for details. -------------------------------------------------------------------------- REPORT CHANGES: (Updated March 24, 1994) Metric:AS(NSS) - Historically, peer networks with multiple connections to AS 690 could only select which of those connections their networks would take by creating "Fake" AS numbers, and using those in the PRDB Metric:AS announcement lists. Some time in the next few weeks we will begin supporting an expanded syntax, where the AS may be followed by an optional NSS peer number in parentheses. Eventually, this syntax will be used to replace most or all of the current Fake ASs. This change will affect *all* places that the announcement lists are reported: all whois queries, all network reports, this "NWG" report, and the Auto-NACR. If you have code which parses these announcement lists, please be aware that that code may need modifications soon. CIDR Reports: There is a new "whois" option to list aggregates in the PRDB: whois -h prdb.merit.edu listaggs will produce a listing of the currently registered aggregates. There is also a new report on "nestings" of PRDB-registered aggregates with their more specific routes: nets.non-classful. Anyone considering configuring an aggregate into the PRDB (and you all should be!) is encouraged to pre-check that aggregate by typing the command: whois -h prdb.merit.edu 'aggchk ' (where "" is the aggregate description). This command will list all of the other entries in the PRDB that are more specific routes of , as well as any aggregates all ready configured that contain . The output includes the AUP and announcement lists of each of the nets printed, with discrepancies flagged. This is the same program that we use for sanity-checking the NACRs that you submit. The archived discussion list "db-disc@merit.edu" exists for discussion of PRDB issues. Send a message to "db-disc-request@merit.edu" to subscribe. --Dale Johnson (dsj@merit.edu) -------------------------------------------------------------------------- Please send all requests for configuration changes to nsfnet-admin@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. ******************************* --Steve Widmayer Merit/NSFNET skw@merit.edu --Enke Chen Merit/NSFNET enke@merit.edu --Steven J. Richardson Merit/NSFNET sjr@merit.edu - - - - - - - - - - - - - - - - - From list-admin Fri Apr 22 13:00:54 1994 Received: from localhost (jyy@localhost) by merit.edu (8.6.8.1/merit-1.0) with SMTP id NAA08483; Fri, 22 Apr 1994 13:00:43 -0400 Message-Id: <199404221700.NAA08483@merit.edu> To: bgpd@merit.edu, regional-techs@merit.edu cc: jyy@merit.edu Subject: this week's CIDR progress report Date: Fri, 22 Apr 1994 13:00:40 -0400 From: Jessica Yu Hi, Between 4/15 - 4/22, NSF/ANSNet routing table growth is as follows: 04/15/94 19688 04/16/94 na 04/17/94 na 04/18/94 19496 04/19/94 19467 04/20/94 18740 04/21/94 18729 04/22/94 18596 Note it actually has negative growth. (Also, note: 4/22's table size is counted as of 11:00 am today.) The routes withdrawn during 4/15-4/22 is 1487. The following ASs have withdrawn more specific routes from the NSFNET/ANSNet routing table during this period of time: 2551 NETCOMM 440 200 BARRnet 212 600 OARNet 195 685 NorthWestNet 137 1800 ICM-Atlantic 117 701 AlertNet 112 2548 DIGEX 87 204 PSCNET 86 1133 CERN/DANTE 52 114 SESQUINET 29 1324 ANS-NewYork Connection 15 1240 ICM-Pacific 5 Note: this is based on data gathered before 11:00 am today. Routes withdrawn afterwards are not counted here. New challenges: There are 565 routes co-existing with its aggregate in the routing table currently, that is they can be withdrawn as we speak. ASs who advertise these nets PLEASE withdrawn them. --Jessica - - - - - - - - - - - - - - - - - From list-admin Fri Apr 22 14:26:58 1994 Received: from localhost (jyy@localhost) by merit.edu (8.6.8.1/merit-1.0) with SMTP id OAA15893; Fri, 22 Apr 1994 14:26:57 -0400 Message-Id: <199404221826.OAA15893@merit.edu> To: bgpd@merit.edu, regional-techs@merit.edu cc: jyy@merit.edu Subject: new bgp4 runners Date: Fri, 22 Apr 1994 14:26:56 -0400 From: Jessica Yu Hi, The following ASs coverted to BGP4 with NSF/ANSnet during the past two weeks: 237: MichNet 266: CICNET at MERIT 267: CICnet at UIUC 279: SURANET Regional Network (Georgia Tech) 1206: PSCNET Regional Network 1225: CICNET at Argonne Labs 2149: PSINET-2 3354: THENET-AS-1 --Jessica - - - - - - - - - - - - - - - - - From list-admin Fri Apr 22 15:18:27 1994 Received: (pam@localhost) by merit.edu (8.6.8.1/merit-1.0) id PAA20625 for regional-techs; Fri, 22 Apr 1994 15:18:27 -0400 Date: Fri, 22 Apr 1994 15:18:27 -0400 From: Pam Ciesla Message-Id: <199404221918.PAA20625@merit.edu> To: regional-techs Subject: Meeting Info I have blocked rooms at the following hotel: Holiday Inn (313)769-9800 3800 Plymouth Rd Ann Arbor, MI $61.00 single or double The block is available for June 1, 2, 3, & 4. Rooms must be reserved by May 20. Please mention Merit Network when registering. The Michigan League and the *Campus Inn (*might have rooms to release at the end of next week) are book for the meeting dates. DIRECTIONS to the Holiday Inn: From Detroit Metro take I 94 west to US 23 north. Exit at Plymouth Road. Turn left onto Plymouth Road cross over the expressway and turn left into the hotel parking lot. To the Chysler Center Continue on Plymouth Road to Murfin (4th traffic light) turn left, pass 2 stop signs, just befor you get to the 3rd stop sign turn left into the parking lot. This puts you behind the North Campus Commons. You must go through this building to get to the Chrysler Center where the meeting is being held. Oh yea :*) did I mention construction?? We are missing the parking lot that use to be next to the Chrysler Ctr. The Holiday Inn has offered to run a shuttle between the hotel and the meeting depending on the how many people and the time. I would like to suggest 8:30am drop-off 5:15pm pickup for 6/2 and 8:30 drop-off 3pm(?) pickup for 6/3. If you will be staying at the Holiday Inn let me know if this is something you want. ANYONE WITH SPECIAL DIET LET ME KNOW AND PLEASE REGISTER SOON. Thanks Pam Ciesla - - - - - - - - - - - - - - - - - From list-admin Fri Apr 22 15:18:36 1994 Received: from rodan.UU.NET (49@rodan.UU.NET [153.39.128.10]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id PAA20635; Fri, 22 Apr 1994 15:18:35 -0400 Received: by rodan.UU.NET (5.61/UUNET-mail-drop) id AA10279; Fri, 22 Apr 94 15:18:33 -0400 From: asp@uunet.uu.net (Andrew Partan) Message-Id: <9404221918.AA10279@rodan.UU.NET> Subject: Re: this week's CIDR progress report To: jyy@merit.edu (Jessica Yu) Date: Fri, 22 Apr 1994 15:18:31 -0400 (EDT) Cc: bgpd@merit.edu, regional-techs@merit.edu, jyy@merit.edu In-Reply-To: <199404221700.NAA08483@merit.edu> from "Jessica Yu" at Apr 22, 94 01:00:40 pm X-Mailer: ELM [version 2.4 PL17] Content-Type: text Content-Length: 617 > 04/22/94 18596 AlterNet is currently seeing 19583 routes - looks like ANS is seeing about 1K fewer routes. Interesting data point. Not quite sure what it means. > The following ASs have withdrawn more specific routes from the > NSFNET/ANSNet routing table during this period of time: > 701 AlterNet 112 I think that you really mean that the following peers of NSFNET/ANSnet (& all of the ASs behind them) have withdrawn more specific routes. If you could identify the home-ASs of the withdrawn nets, that would probably be more helpful & more accurate. --asp@uunet.uu.net (Andrew Partan) - - - - - - - - - - - - - - - - - From list-admin Fri Apr 22 16:05:01 1994 Received: from ncc.ripe.net (ncc.ripe.net [192.87.45.2]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id QAA25232; Fri, 22 Apr 1994 16:04:59 -0400 Received: from mature.ripe.net by ncc.ripe.net with SMTP id AA12027 (5.65a/NCC-2.2); Fri, 22 Apr 1994 22:04:57 +0200 Received: from localhost.ripe.net by mature.ripe.net with SMTP id AA06421 (5.65a/NCC-2.1); Fri, 22 Apr 1994 22:04:57 +0200 Message-Id: <9404222004.AA06421@mature.ripe.net> To: asp@uunet.uu.net (Andrew Partan) Cc: jyy@merit.edu (Jessica Yu), bgpd@merit.edu, regional-techs@merit.edu Subject: Re: this week's CIDR progress report In-Reply-To: Your message of Fri, 22 Apr 1994 15:18:31 EDT. <9404221918.AA10279@rodan.UU.NET> From: Tony Bates X-Phone: +31 20 592 5064 Date: Fri, 22 Apr 1994 22:04:56 +0200 Sender: Tony.Bates@ripe.net asp@uunet.uu.net (Andrew Partan) writes: * > 04/22/94 18596 * * AlterNet is currently seeing 19583 routes - looks like ANS is seeing * about 1K fewer routes. Interesting data point. Not quite sure what it * means. * Hmm. to confirm - this is the data I see from the Table-History file I am generatiing. It does seem ANS is a 1000 low ? Date Routes Paths 080494 20136 53243 090494 20139 53225 100494 20044 53333 110494 20036 53183 120494 20294 53642 130494 20326 53849 140494 20374 53822 150494 20246 53541 150494 20384 53776 160494 20099 53167 170494 19949 52708 180494 19858 52489 190494 20238 53577 200494 19327 51054 210494 19463 51341 220494 19486 51544 --Tony. - - - - - - - - - - - - - - - - - From list-admin Fri Apr 22 17:18:13 1994 Received: from localhost (jyy@localhost) by merit.edu (8.6.8.1/merit-1.0) with SMTP id RAA01238; Fri, 22 Apr 1994 17:18:12 -0400 Message-Id: <199404222118.RAA01238@merit.edu> To: asp@uunet.uu.net (Andrew Partan) cc: jyy@merit.edu (Jessica Yu), bgpd@merit.edu, regional-techs@merit.edu Subject: Re: this week's CIDR progress report In-reply-to: Your message of "Fri, 22 Apr 1994 15:18:31 EDT." <9404221918.AA10279@rodan.UU.NET> Date: Fri, 22 Apr 1994 17:18:12 -0400 From: Jessica Yu Andrew: > 04/22/94 18596 AlterNet is currently seeing 19583 routes - looks like ANS is seeing about 1K fewer routes. Interesting data point. Not quite sure what it means. The following things may contribute to the table size difference: 1. ASs may sent aggregates to NSF/ANSnet and withdrawn more specific routes from it while still sending more specific routes to other neighbors. So the route reduced in the NSFNET but not other places. This is interesting to verify. 2. There are routes has not made it to NSFnet yet. e.g. routes advertised to CIX usually has a delay to make it to ANSNET. 3. Also, the number 18596 was as of 11:00 am this morning as I indicated in my previous message. The routing table may grow by the time you gathered your data. Friday is configuration morning, this behavior is not unusually. > The following ASs have withdrawn more specific routes from the > NSFNET/ANSNet routing table during this period of time: > 701 AlterNet 112 I think that you really mean that the following peers of NSFNET/ANSnet (& all of the ASs behind them) have withdrawn more specific routes. Yes. If you could identify the home-ASs of the withdrawn nets, that would probably be more helpful & more accurate. Actually, I still like to mention NSF/ANSNet neighbor ASs who withdrawn routes because if they do not do CIDR, AS690 would not be able to see aggregates from the ASs behind those ASs. So it is important that a transit AS do CIDR and got recognized. I will try to do home-AS in addition. --Jessica - - - - - - - - - - - - - - - - - From list-admin Fri Apr 22 18:18:37 1994 Received: from localhost (jyy@localhost) by merit.edu (8.6.8.1/merit-1.0) with SMTP id SAA05907; Fri, 22 Apr 1994 18:18:37 -0400 Message-Id: <199404222218.SAA05907@merit.edu> To: asp@uunet.uu.net (Andrew Partan) cc: jyy@merit.edu (Jessica Yu), bgpd@merit.edu, regional-techs@merit.edu Subject: Re: this week's CIDR progress report In-reply-to: Your message of "Fri, 22 Apr 1994 15:18:31 EDT." <9404221918.AA10279@rodan.UU.NET> Date: Fri, 22 Apr 1994 18:18:36 -0400 From: Jessica Yu Got a list of routes which are not in the NSFnet table but some other places. Spot that one incident that the aggregate is advertised to both routing tables, but there are few specific routes within the aggregate has been advertised to the NSFNET. So in terms of connectivity, both can reach all the specific routes destination, but the path would be different. However, that cause the difference in size of the routing table. This is just the one I happen to see but there could be more such cases. This indicates reason #1 in my previous message. I also saw a lot of routes in the diff list looks like testnets but not quite sure. I do not have time to do more poking today, I will do it on Monday. --Jessica - - - - - - - - - - - - - - - - - From list-admin Sun Apr 24 15:07:35 1994 Received: (skw@localhost) by merit.edu (8.6.8.1/merit-1.0) id PAA20204; Sun, 24 Apr 1994 15:07:35 -0400 Date: Sun, 24 Apr 1994 15:07:35 -0400 From: "Steven K. Widmayer" Message-Id: <199404241907.PAA20204@merit.edu> To: asp@uunet.uu.net, jyy@merit.edu Subject: Re: this week's CIDR progress report Cc: bgpd, regional-techs >From list-admin Fri Apr 22 18:19:27 1994 > >Got a list of routes which are not in the NSFnet table but some other places. >Spot that one incident that the aggregate is advertised to both routing >tables, but there are few specific routes within the aggregate has been >advertised to the NSFNET. So in terms of connectivity, both can reach all the >specific routes destination, but the path would be different. However, that >cause the difference in size of the routing table. This is just the one I >happen to see but there could be more such cases. This indicates >reason #1 in my previous message. I also saw a lot of routes in the diff list >looks like testnets but not quite sure. I do not have time to do more poking >today, I will do it on Monday. > > --Jessica > I would agree that the difference in table size is most likely due to CIX issues. I used to see table size differences of a few hundred routes, which I mostly attributed to the few days of lag time in getting new CIX routes registered in the PRDB. ANS-CIX (AS 1957) has a new policy for the past week or two which is to stop automatically registering the CIX-only routes (routes known to the CIX which are not registered by another AS 690 service provider) in the PRDB. I understand they are working out a new policy for getting these CIX-only routes registed in the PRDB. This could account for some of the table size discrepency. Also, as service providers register aggregates in the PRDB, AS 1957 component routes are removed, unless for policy purposes the service provider requests and ANS agrees to leave the AS 1957 component networks configured. This could account for several hundred CIX-only component routes that have recently disappeared from the AS 690 routing tables, but which may still be announced to the CIX. Also, there always seem to be a handful of routes (maybe about 20 ?) which are known to the CIX but which are not registered in the PRDB because they cannot be verified as having been assigned from address space delegated to the InterNIC or RIPE. --Steve Widmayer - - - - - - - - - - - - - - - - - From list-admin Mon Apr 25 13:06:12 1994 Received: from pepper.merit.edu (pepper.merit.edu [35.42.1.50]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id NAA27547; Mon, 25 Apr 1994 13:06:11 -0400 Received: by pepper.merit.edu (4.1/client-0.9) id AA00527; Mon, 25 Apr 94 13:06:10 EDT From: epg@merit.edu Message-Id: <9404251706.AA00527@pepper.merit.edu> Subject: classless nets and home ASs To: asp@uunet.uu.net (Andrew Partan) Date: Mon, 25 Apr 94 13:06:10 EDT Cc: jyy@merit.edu, bgpd@merit.edu, regional-techs@merit.edu, epg@merit.edu (Elise Gerich) In-Reply-To: <9404221918.AA10279@rodan.UU.NET>; from "Andrew Partan" at Apr 22, 94 3:18 pm X-Mailer: ELM [version 2.3 PL11] Andrew, > (& all of the ASs behind them) have withdrawn more specific routes. If > you could identify the home-ASs of the withdrawn nets, that would > probably be more helpful & more accurate. > --asp@uunet.uu.net (Andrew Partan) > During this tranisition from the classful world to the classless, home ASs still have meaning. It does not seem clear that home ASs will be relevant when we treat all routes as classless entities, because most assignments can be further subdivided. There will be no base unit such as class A, B or C on which to hang the home AS tag. We may want to move from "one net/one home AS" to "prefix and length/ announcing AS" - since an AS downstream or upstream may aggregate a subset or superset. I'm not commenting directly on your suggestion on how to express meaningful information about the specific nets that AS 701 has withdrawn from its announcment to AS 690, but trying to explore how we should look at keeping information about classless entities. These lists (regional-techs and bgpd) seem like the right place to discuss what information the operators need in a classless routing world. --Elise - - - - - - - - - - - - - - - - - From list-admin Mon Apr 25 14:17:56 1994 Received: from localhost (jyy@localhost) by merit.edu (8.6.8.1/merit-1.0) with SMTP id OAA03917; Mon, 25 Apr 1994 14:17:55 -0400 Message-Id: <199404251817.OAA03917@merit.edu> To: bgpd@merit.edu, regional-techs@merit.edu cc: jyy@merit.edu Date: Mon, 25 Apr 1994 14:17:54 -0400 From: Jessica Yu Hi, For those who already run BGP4, would you please provide the following information: Vendor routers (e.g. Cisco, Proteon ...etc) Hardward platform (e.g. Cisco 7000, 4000 .. etc) Software version other info which you think is valuable for new users We have been asked about these kinds of questions from people who are working on deploying BGP4. Please help. Please send your information to me. I will summerize it and post it to the list. Thanks! --jessica - - - - - - - - - - - - - - - - - From list-admin Mon Apr 25 13:37:43 1994 Received: from barsoom.sura.net (aotearoa.sura.net [128.167.254.175]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id NAA00487; Mon, 25 Apr 1994 13:37:42 -0400 Received: from localhost by barsoom.sura.net with SMTP (5.67b/($Id: sendmail.cf,v 1.17 1991/02/11 14:07:23 jmalcolm Exp $)) id AA20626; Mon, 25 Apr 1994 13:37:40 -0400 Message-Id: <199404251737.AA20626@barsoom.sura.net> To: epg@merit.edu Cc: asp@uunet.uu.net (Andrew Partan), jyy@merit.edu, bgpd@merit.edu, regional-techs@merit.edu Subject: Re: classless nets and home ASs In-Reply-To: Your message of "Mon, 25 Apr 1994 13:06:10 EDT." <9404251706.AA00527@pepper.merit.edu> Date: Mon, 25 Apr 1994 13:37:39 -0400 From: Erik Sherk Elise, My feeling is that there is some level of atomic aggregation, below which, you will be using igp routes. This goes back to the original definition of Autonomous System. I would like to see the home AS represent that transition from igp routing to egp routing. That is, if you inject a route into the global routing table, then you have some level of responsibility for that route and this should be documented somewhere. Don't think of it as no more A,B,C networks, but rather as 30 different sizes. Erik P.S. Would routing within a AS be sub-atomic routing? :-) > During this tranisition from the classful world to the classless, > home ASs still have meaning. It does not seem clear that home ASs > will be relevant when we treat all routes as classless entities, > because most assignments can be further subdivided. There will be > no base unit such as class A, B or C on which to hang the home AS > tag. We may want to move from "one net/one home AS" to "prefix and length/ > announcing AS" - since an AS downstream or upstream may aggregate > a subset or superset. > > I'm not commenting directly on your suggestion on how to express > meaningful information about the specific nets that AS 701 has > withdrawn from its announcment to AS 690, but trying to explore > how we should look at keeping information about classless entities. > These lists (regional-techs and bgpd) seem like the right place to > discuss what information the operators need in a classless routing > world. > --Elise > - - - - - - - - - - - - - - - - - From list-admin Mon Apr 25 14:13:40 1994 Received: from rodan.UU.NET (49@rodan.UU.NET [153.39.128.10]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id OAA03687; Mon, 25 Apr 1994 14:13:39 -0400 Received: by rodan.UU.NET (5.61/UUNET-mail-drop) id AA28119; Mon, 25 Apr 94 14:13:32 -0400 From: asp@uunet.uu.net (Andrew Partan) Message-Id: <9404251813.AA28119@rodan.UU.NET> Subject: Re: classless nets and home ASs To: epg@merit.edu Date: Mon, 25 Apr 1994 14:13:32 -0400 (EDT) Cc: jyy@merit.edu, bgpd@merit.edu, regional-techs@merit.edu In-Reply-To: <9404251706.AA00527@pepper.merit.edu> from "epg@merit.edu" at Apr 25, 94 01:06:10 pm X-Mailer: ELM [version 2.4 PL17] Content-Type: text Content-Length: 263 Home-AS still has meansing for a classless net; just as it does for a classfull one. Routing table entries should have some idea of the 'creator' of that entry. Home-AS or aggregator or some such seems to be the most useful. --asp@uunet.uu.net (Andrew Partan) - - - - - - - - - - - - - - - - - From list-admin Mon Apr 25 14:09:02 1994 Received: from localhost (jyy@localhost) by merit.edu (8.6.8.1/merit-1.0) with SMTP id OAA03176; Mon, 25 Apr 1994 14:09:01 -0400 Message-Id: <199404251809.OAA03176@merit.edu> To: asp@uunet.uu.net (Andrew Partan) cc: jyy@merit.edu (Jessica Yu), bgpd@merit.edu, regional-techs@merit.edu Subject: Re: this week's CIDR progress report In-reply-to: Your message of "Fri, 22 Apr 1994 15:18:31 EDT." <9404221918.AA10279@rodan.UU.NET> Date: Mon, 25 Apr 1994 14:09:01 -0400 From: Jessica Yu >I think that you really mean that the following peers of NSFNET/ANSnet >(& all of the ASs behind them) have withdrawn more specific routes. If >you could identify the home-ASs of the withdrawn nets, that would >probably be more helpful & more accurate. Thought about this a bit more. If we really want to mention the ASs which have withdrawn specific routes, homeAS may not give accurate information either. Think about the case of proxy aggregation, the AS which withdrew specific routes is the one who does the proxy aggr not the homeAS itself. --jessica - - - - - - - - - - - - - - - - - From list-admin Mon Apr 25 15:29:09 1994 Received: from cider.cisco.com (cider.cisco.com [131.108.13.133]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id PAA11676; Mon, 25 Apr 1994 15:29:08 -0400 Received: from localhost.cisco.com by cider.cisco.com with SMTP id AA12121 (5.67a/IDA-1.5); Mon, 25 Apr 1994 12:28:41 -0700 Message-Id: <199404251928.AA12121@cider.cisco.com> To: Jessica Yu Cc: bgpd@merit.edu, regional-techs@merit.edu In-Reply-To: Your message of "Mon, 25 Apr 1994 14:17:54 EDT." <199404251817.OAA03917@merit.edu> Date: Mon, 25 Apr 1994 12:28:40 -0700 From: Paul Traina > To: bgpd@merit.edu, regional-techs@merit.edu > Cc: jyy@merit.edu > Date: Mon, 25 Apr 1994 14:17:54 -0400 > From: Jessica Yu > > Hi, > > For those who already run BGP4, would you please provide the following information: > > Vendor routers (e.g. Cisco, Proteon ...etc) > Hardward platform (e.g. Cisco 7000, 4000 .. etc) > Software version > other info which you think is valuable for new users > > We have been asked about these kinds of questions from people who are working on > deploying BGP4. Please help. > > Please send your information to me. I will summerize it and post it to the list. > Thanks! > > --jessica Just as a side note, 10.0 has left beta, and we are suggesting that everyone who is migrating to BGP4 run 10.0, instead of 9.21+BGP4, since 10.0 receives better support (9.21+BGP4 is on the way out). - - - - - - - - - - - - - - - - - From list-admin Mon Apr 25 18:24:37 1994 Received: from pepper.merit.edu (pepper.merit.edu [35.42.1.50]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id SAA28921; Mon, 25 Apr 1994 18:24:36 -0400 Received: by pepper.merit.edu (4.1/client-0.9) id AA00806; Mon, 25 Apr 94 18:24:36 EDT From: epg@merit.edu Message-Id: <9404252224.AA00806@pepper.merit.edu> Subject: Re: classless nets and home ASs To: asp@uunet.uu.net (Andrew Partan) Date: Mon, 25 Apr 94 18:24:36 EDT Cc: epg@merit.edu, jyy@merit.edu, bgpd@merit.edu, regional-techs@merit.edu In-Reply-To: <9404251813.AA28119@rodan.UU.NET>; from "Andrew Partan" at Apr 25, 94 2:13 pm X-Mailer: ELM [version 2.3 PL11] Andrew, Is your definition of home-as the RIPE definition? > > Home-AS still has meansing for a classless net; just as it does for a > classfull one. > How do you designate home-as for 194.16/16 from 194.16.16/24? 194.16/16 was assigned to organizationX and indicated that the home-as was 701. Then organizationX gave 194.16.16/24 to companyY who has their own AS 702. Now the assignment registry can be updated to show these changes in home-AS. > Routing table entries should have some idea of the 'creator' of that > entry. Home-AS or aggregator or some such seems to be the most > useful. > --asp@uunet.uu.net (Andrew Partan) But when the classless thingy is routed, home-AS and aggregator-AS can be inconsistent or there can even be multiple creators of aggregation. So I am not sure that home-AS means the same thing for classless entities - or perhaps we need another concept which acknowledges a classless entity may be included in several supersets all of which have different aggregator-ASs. If your definition permits multiple home-as tags per classless net, then you have answered my question. Thanks. --Elise - - - - - - - - - - - - - - - - - From list-admin Mon Apr 25 23:21:58 1994 Received: (enke@localhost) by merit.edu (8.6.8.1/merit-1.0) id XAA17914 for nwg; Mon, 25 Apr 1994 23:21:58 -0400 Date: Mon, 25 Apr 1994 23:21:58 -0400 From: merit Message-Id: <199404260321.XAA17914@merit.edu> To: nwg Subject: Additions to the NSFNET policy-based database ------------------------------------------------------------------------------ CIDR Progress Report: 2421 Nets, 39 ASs, 326 Aggregates. Details below. New format for Metric:AS lists coming later in this and all reports. See 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 30444 = 29 4650 25387 378 Configured Networks 29390 = 29 4650 24333 378 Added Networks 166 = 0 5 109 52 Deleted Networks 1 = 0 0 1 0 IP address Net name Country Priority:AS ---------- -------- ------- ----------- 138.200/16 AEG-SW-FFM C:DE 1:701 2:1800 138.250/15 JANET-AGGR-2 C:GB 1:1800 2:1133 3:1240 143.52/15 JANET-AGGR-3 C:GB 1:1800 2:1133 3:1240 147.48/16 DFAS-C C:US 1:19 2:568 147.185/16 NET-TIMKEN C:US 1:600 2:1800 162.27/16 RRD C:US 1:2149 2:174 164.40/16 RIPE-TMP-SHOWNET C:NL 1:1800 2:1133 3:1240 192.41.102/23 EDUNI-AGGR-1 C:GB 1:1800 2:1133 3:1240 192.41.104/23 EDUNI-AGGR-2 C:GB 1:1800 2:1133 3:1240 192.41.108/23 EDUNI-AGGR-3 C:GB 1:1800 2:1133 3:1240 192.41.112/22 EDUNI-AGGR-4 C:GB 1:1800 2:1133 3:1240 192.76.6/23 OXUNI-AGGR-1 C:GB 1:1800 2:1133 3:1240 192.76.8/23 OXUNI-AGGR-2 C:GB 1:1800 2:1133 3:1240 192.76.12/22 OXUNI-AGGR-3 C:GB 1:1800 2:1133 3:1240 192.76.16/23 OXUNI-AGGR-4 C:GB 1:1800 2:1133 3:1240 192.76.20/23 OXUNI-AGGR-5 C:GB 1:1800 2:1133 3:1240 192.76.26/23 OXUNI-AGGR-6 C:GB 1:1800 2:1133 3:1240 192.76.28/22 OXUNI-AGGR-7 C:GB 1:1800 2:1133 3:1240 192.82.242/23 KEELEUNI-AGGR-1 C:GB 1:1800 2:1133 3:1240 192.84.76/22 MANUNI-AGGR-1 C:GB 1:1800 2:1133 3:1240 192.84.80/22 MANUNI-AGGR-2 C:GB 1:1800 2:1133 3:1240 192.93.59/24 FNET-SYNERGIE C:FR 1:701 2:1800 192.108.6/24 LONGBEACHNET C:US 1:19 2:568 192.135.232/23 QMW-AGGR-1 C:GB 1:1800 2:1133 3:1240 192.150.178/23 MANUNI-AGGR-3 C:GB 1:1800 2:1133 3:1240 192.150.180/23 MANUNI-AGGR-4 C:GB 1:1800 2:1133 3:1240 192.160.178/23 RFHSM-AGGR-1 C:GB 1:1800 2:1133 3:1240 192.167.160/19 CNR-BOLOGNA3 C:IT 1:293 2:291 3:1133 4:1674 192.171.130/23 NERC-AGGR-1 C:GB 1:1800 2:1133 3:1240 192.171.134/23 NERC-AGGR-2 C:GB 1:1800 2:1133 3:1240 192.171.136/23 NERC-AGGR-3 C:GB 1:1800 2:1133 3:1240 192.171.142/23 NERC-AGGR-4 C:GB 1:1800 2:1133 3:1240 192.171.144/22 NERC-AGGR-5 C:GB 1:1800 2:1133 3:1240 192.171.148/23 NERC-AGGR-6 C:GB 1:1800 2:1133 3:1240 192.171.154/23 NERC-AGGR-7 C:GB 1:1800 2:1133 3:1240 192.171.156/22 NERC-AGGR-8 C:GB 1:1800 2:1133 3:1240 192.171.160/22 NERC-AGGR-9 C:GB 1:1800 2:1133 3:1240 192.171.164/23 NERC-AGGR-10 C:GB 1:1800 2:1133 3:1240 192.171.168/21 NERC-AGGR-11 C:GB 1:1800 2:1133 3:1240 192.171.176/23 NERC-AGGR-12 C:GB 1:1800 2:1133 3:1240 192.171.180/22 NERC-AGGR-13 C:GB 1:1800 2:1133 3:1240 192.171.184/23 NERC-AGGR-14 C:GB 1:1800 2:1133 3:1240 192.171.190/23 NERC-AGGR-15 C:GB 1:1800 2:1133 3:1240 192.171.192/22 NERC-AGGR-16 C:GB 1:1800 2:1133 3:1240 192.171.196/23 NERC-AGGR-17 C:GB 1:1800 2:1133 3:1240 192.173.2/23 UNN-AGGR-1 C:GB 1:1800 2:1133 3:1240 192.173.128/21 BTONUNI-AGGR-1 C:GB 1:1800 2:1133 3:1240 192.195.42/23 ULSTUNI-AGGR-1 C:GB 1:1800 2:1133 3:1240 192.195.247/24 WORKGROUP C:US 1:2149 2:174 192.221.52/24 NETBLK-SURA-SUB-PRJ C:US 1:279 2:86 193.10.48/24 SE-HHS C:SE 1:1800 2:1879 3:1133 4:1240 193.56.159/24 FR-DEEMED C:FR 1:701 2:1800 193.60/14 JANET-AGGR-1 C:GB 1:1800 2:1133 3:1240 193.63.82/24 GWENT-NET C:GB 1:1800 2:1133 3:1240 193.64.208/24 JYTOL1 C:FI 1:701 2:1800 193.64.209/24 JYTOL2 C:FI 1:701 2:1800 193.64.210/24 JYTOL3 C:FI 1:701 2:1800 193.64.211/24 JYTOL4 C:FI 1:701 2:1800 193.64.212/24 JYTOL5 C:FI 1:701 2:1800 193.64.213/24 JYTOL6 C:FI 1:701 2:1800 193.64.214/24 JYTOL7 C:FI 1:701 2:1800 193.64.215/24 JYTOL8 C:FI 1:701 2:1800 193.77.3/24 NILNET-1 C:SI 1:701 2:1800 193.77.8/24 SINET-SLIP-INET C:SI 1:701 2:1800 193.78.98/24 BAUSCH C:NL 1:701 2:1800 193.78.180/24 DUPACO C:NL 1:701 2:1800 193.78.181/24 DUPACO C:NL 1:701 2:1800 193.78.245/24 NLNET C:NL 1:701 2:1800 193.78.246/24 NLNET C:NL 1:701 2:1800 193.78.247/24 NLNET-CONF C:NL 1:701 2:1800 193.78.248/24 NLNET-CONF C:NL 1:701 2:1800 193.80.238/24 IBMVIE C:AT 1:701 2:1800 193.104.38/24 FR-OST C:FR 1:701 2:1800 193.104.60/24 FR-APIC C:FR 1:701 2:1800 193.125.172/24 RELCOM-EXPO C:RU 1:701 2:1800 193.125.173/24 RELCOM-EXPO C:RU 1:701 2:1800 193.125.174/24 RELCOM-EXPO C:RU 1:701 2:1800 193.125.175/24 RELCOM-EXPO C:RU 1:701 2:1800 193.172.11/24 EMPB C:NL 1:1800 2:1133 3:1674 4:1240 193.174/15 DFN-AGG-1 C:DE 1:293 2:291 193.196/15 BELWUE-AGG-1 C:DE 1:293 2:291 193.212.6/24 TPC6NET C:NO 1:1800 2:1879 3:1133 4:1240 193.216.3/24 NO-OCEANOR1 C:NO 1:1800 2:1879 3:1133 4:1240 194.4.144/24 FR-OCP-01 C:FR 1:701 2:1800 194.8.8/24 VERNET C:LV 1:701 2:1800 194.66/16 JANET-AGGR-4 C:GB 1:1800 2:1133 3:1240 198.56.0/21 MYXA C:US 1:204 2:1206 198.81.216/24 SHERWIN-DMZ C:US 1:1325 198.96.127/24 NET-CALIAN C:CA 1:701 2:702 198.146.12/24 CPS-NET-C-146-12 C:US 1:279 2:86 198.146.13/24 CPS-NET-C-146-13 C:US 1:279 2:86 198.147.191/24 BMCPRODNET C:US 1:114 198.147.192/22 BMCAUSTIN C:US 1:114 198.170/15 SESQUINET-CIDR-02 C:US 1:114 198.172/15 SESQUINET-CIDR-02 C:US 1:114 198.175.15/24 PAGESAT-C8 C:US 1:1740 198.175.229/24 BMCAUSTR-C-175-229 C:US 1:114 198.175.230/24 BMCAUSTR-C-175-230 C:US 1:114 198.199.133/24 LACOLLEGE C:US 1:279 2:86 198.206.223/24 NET-SNL C:US 1:377 198.207.141/24 NETBLK-MAGIC-C-C-207- C:US 1:555 2:1225 3:267 4:266 198.207.142/24 NETBLK-MAGIC-C-C-207- C:US 1:555 2:1225 3:267 4:266 198.207.143/24 NETBLK-MAGIC-C-C-207- C:US 1:555 2:1225 3:267 4:266 198.207.144/24 NETBLK-MAGIC-C-C-207- C:US 1:555 2:1225 3:267 4:266 198.207.223/24 BMCENET C:US 1:114 198.232.212/23 NETBLK-CCUBE-NET C:US 1:2551 199.1.23/24 NETBLK-SPRINT-BLKA C:US 1:1240 2:1800 199.1.48/24 NETBLK-USIT-C-1-48 C:US 1:1240 2:1800 199.1.49/24 NETBLK-USIT-C-1-49 C:US 1:1240 2:1800 199.1.50/24 NETBLK-USIT-C-1-50 C:US 1:1240 2:1800 199.1.51/24 NETBLK-USIT-C-1-51 C:US 1:1240 2:1800 199.1.52/24 NETBLK-USIT-C-1-52 C:US 1:1240 2:1800 199.1.53/24 NETBLK-USIT-C-1-53 C:US 1:1240 2:1800 199.1.54/24 NETBLK-USIT-C-1-54 C:US 1:1240 2:1800 199.1.55/24 NETBLK-USIT-C-1-55 C:US 1:1240 2:1800 199.1.56/24 NETBLK-USIT-C-1-56 C:US 1:1240 2:1800 199.1.57/24 NETBLK-USIT-C-1-57 C:US 1:1240 2:1800 199.1.58/24 NETBLK-USIT-C-1-58 C:US 1:1240 2:1800 199.1.59/24 NETBLK-USIT-C-1-59 C:US 1:1240 2:1800 199.1.60/24 NETBLK-USIT-C-1-60 C:US 1:1240 2:1800 199.1.61/24 NETBLK-USIT-C-1-61 C:US 1:1240 2:1800 199.1.62/24 NETBLK-USIT-C-1-62 C:US 1:1240 2:1800 199.1.63/24 NETBLK-USIT-C-1-63 C:US 1:1240 2:1800 199.33.92/24 NETBLK-ROCKWELL C:US 1:114 199.43.112/24 MICROSL-1 C:CA 1:701 2:702 199.76.57/24 NETBLK-UMSMEDCTR10 C:US 1:279 2:86 199.88.23/24 LIVINGSTON-NET C:US 1:279 2:86 199.88.30/24 JVILLE-NET C:US 1:279 2:86 199.98.174/24 PSINET-C5 C:US 1:2149 2:174 199.98.175/24 PSINET-C5 C:US 1:2149 2:174 199.98.176/24 PSINET-C5 C:US 1:2149 2:174 199.98.177/24 PSINET-C5 C:US 1:2149 2:174 199.98.178/24 PSINET-C5 C:US 1:2149 2:174 199.98.179/24 PSINET-C5 C:US 1:2149 2:174 199.98.180/24 PSINET-C5 C:US 1:2149 2:174 199.98.181/24 PSINET-C5 C:US 1:2149 2:174 199.100/16 PSINET-NETBLK-C5 C:US 1:2149 2:174 199.181.232/24 ARIEL C:US 1:279 2:86 199.234/16 NETBLK-PREPNET-C2 C:US 1:204 2:1206 203.4.185/24 ZIRCON-AU C:AU 1:372 2:297 203.4.188/24 AAP-AU C:AU 1:372 2:297 203.4.189/24 AAP-AU C:AU 1:372 2:297 203.4.190/24 AAP-AU C:AU 1:372 2:297 203.4.191/24 AAP-AU C:AU 1:372 2:297 203.4.200/24 NLA-AU C:AU 1:372 2:297 203.4.201/24 NLA-AU C:AU 1:372 2:297 203.4.202/24 NLA-AU C:AU 1:372 2:297 203.4.203/24 NLA-AU C:AU 1:372 2:297 203.4.204/24 ASPECT-AU C:AU 1:372 2:297 203.4.205/24 MAQ-AU C:AU 1:372 2:297 203.4.206/24 TRIPLE-G-AU C:AU 1:372 2:297 203.4.207/24 DATAPLEX-AU C:AU 1:372 2:297 203.4.212/24 MAGNADATA-AU C:AU 1:372 2:297 203.4.213/24 MAGNADATA-AU C:AU 1:372 2:297 203.4.214/24 MAGNADATA-AU C:AU 1:372 2:297 203.4.215/24 MAGNADATA-AU C:AU 1:372 2:297 203.4.216/24 STVMELB-AU C:AU 1:372 2:297 203.4.217/24 STVMELB-AU C:AU 1:372 2:297 203.4.218/24 STVMELB-AU C:AU 1:372 2:297 203.4.219/24 STVMELB-AU C:AU 1:372 2:297 203.4.220/24 STVMELB-AU C:AU 1:372 2:297 203.4.221/24 STVMELB-AU C:AU 1:372 2:297 203.4.222/24 STVMELB-AU C:AU 1:372 2:297 203.4.223/24 STVMELB-AU C:AU 1:372 2:297 203.4.224/24 MGGSNETWORK-AU C:AU 1:372 2:297 203.4.225/24 MGGSNETWORK-AU C:AU 1:372 2:297 Deletions: --192.217.96/24 CICNET-7 C:US 1:267 2:1225 3:266 Expanded listing, sorted by country, then by organization: ========================================================== Australia --------- AAP Communications Services Pty Ltd, 22-24 Junction Street, Glebe, NSW, 2037, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 203.4.188/24 AAP-AU (AU) 203.4.189/24 AAP-AU (AU) 203.4.190/24 AAP-AU (AU) 203.4.191/24 AAP-AU (AU) Aspect Computing Pty Ltd, Suite 1101, 122 Arthur Street, North Sydney, NSW, 2060, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 203.4.204/24 ASPECT-AU (AU) Dataplex Pty Ltd, 234 Whitehorse Road, Blackburn, VIC, 3130, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 203.4.207/24 DATAPLEX-AU (AU) Macquarie Textiles Group, PO Box 319, Bridge Street, Albury, NSW, 2640, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 203.4.205/24 MAQ-AU (AU) Magnadata, PO Box A770, Sydney, NSW, 2000, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 203.4.212/24 MAGNADATA-AU (AU) 203.4.213/24 MAGNADATA-AU (AU) 203.4.214/24 MAGNADATA-AU (AU) 203.4.215/24 MAGNADATA-AU (AU) Melbourne Girls Grammar School, 82 Anderson Street, South Yarra, VIC, 3141, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 203.4.224/24 MGGSNETWORK-AU (AU) 203.4.225/24 MGGSNETWORK-AU (AU) National Library of Australia, Parkes Place, Canberra, ACT, 2600, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 203.4.200/24 NLA-AU (AU) 203.4.201/24 NLA-AU (AU) 203.4.202/24 NLA-AU (AU) 203.4.203/24 NLA-AU (AU) St Vincent's Public Hospital, 41 Victoria Parade, Melbourne, VIC, 3000, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 203.4.216/24 STVMELB-AU (AU) 203.4.217/24 STVMELB-AU (AU) 203.4.218/24 STVMELB-AU (AU) 203.4.219/24 STVMELB-AU (AU) 203.4.220/24 STVMELB-AU (AU) 203.4.221/24 STVMELB-AU (AU) 203.4.222/24 STVMELB-AU (AU) 203.4.223/24 STVMELB-AU (AU) Triple G Corporation, PO Box 130W, Ballarat West, VIC, 3350, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 203.4.206/24 TRIPLE-G-AU (AU) Zircon Systems Pty Ltd, PO Box 265, Rosebery, NSW, 2018, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 203.4.185/24 ZIRCON-AU (AU) Austria ------- IBM Oesterreich, Obere Donaustrasse 95, A-1020 Wien, AUSTRIA 1:701 Alternet 2:1800 ICM-Atlantic ------------- 193.80.238/24 IBMVIE (AT) Canada ------ Calian Communications Systems Ltd., 300 Legget Drive, Kanata, ON, K2K 1Y5, CANADA 1:701 Alternet 2:702 Alternet ------------- 198.96.127/24 NET-CALIAN (CA) Microstar Software Limited, 100-34 Colonnade Rd. N., Nepean, ON, K2E 7J6, CANADA 1:701 Alternet 2:702 Alternet ------------- 199.43.112/24 MICROSL-1 (CA) Finland ------- Jyvaskylan Teknillinen Oppilaitos, Viitaniementie 1, FI-40720 JYVASKYLA, FINLAND 1:701 Alternet 2:1800 ICM-Atlantic ------------- 193.64.208/24 JYTOL1 (FI) 193.64.209/24 JYTOL2 (FI) 193.64.210/24 JYTOL3 (FI) 193.64.211/24 JYTOL4 (FI) 193.64.212/24 JYTOL5 (FI) 193.64.213/24 JYTOL6 (FI) 193.64.214/24 JYTOL7 (FI) 193.64.215/24 JYTOL8 (FI) France ------ Apic Systemes SA, Immeuble Le Baudran, 25 rue de Stalingrad, F-94110 Arcueil, FRANCE 1:701 Alternet 2:1800 ICM-Atlantic ------------- 193.104.60/24 FR-APIC (FR) Deemed International, 2 avenue de Vignate , Centre Equation, 38610 Gieres, FRANCE 1:701 Alternet 2:1800 ICM-Atlantic ------------- 193.56.159/24 FR-DEEMED (FR) OCP Repartition, Service Reseau, 24 Rue des Ardennes, F-75019 Paris, FRANCE 1:701 Alternet 2:1800 ICM-Atlantic ------------ 194.4.144/24 FR-OCP-01 (FR) OST SA, Rue du bas Village BP 158, F-35515 Cesson Sevigne CEDEX, FRANCE 1:701 Alternet 2:1800 ICM-Atlantic ------------- 193.104.38/24 FR-OST (FR) Synergie Telesystemes, 12bis, rue des Pavillons, BP 133, F-92804 Puteaux CEDEX, FRANCE 1:701 Alternet 2:1800 ICM-Atlantic ------------ 192.93.59/24 FNET-SYNERGIE (FR) Germany ------- AEG Softwaretechnik, Lyoner Strasse 9, D-60528 Frankfurt, GERMANY 1:701 Alternet 2:1800 ICM-Atlantic ---------- 138.200/16 AEG-SW-FFM (DE) BelWue, Baden Wuerttembergs extended LAN, Rechenzentrum der Universitaet Stuttgart, Allmandring 30, Stuttgart, D-70550, GERMANY 1:293 Energy Science Network (FIX-East) 2:291 Energy Science Network (FIX-West) ---------- 193.196/15 BELWUE-AGG-1 (DE) Deutsches Forschungsnetz e.V., Pariser Str. 44, Berlin, D-10707, GERMANY 1:293 Energy Science Network (FIX-East) 2:291 Energy Science Network (FIX-West) ---------- 193.174/15 DFN-AGG-1 (DE) Italy ----- Consiglio Nazionale delle Ricerche, AREA di Bologna, V. Gobetti 101, BOLOGNA, I-40129, ITALY 1:293 Energy Science Network (FIX-East) 2:291 Energy Science Network (FIX-West) 3:1133 CERN/DANTE 4:1674 CERN/DANTE -------------- 192.167.160/19 CNR-BOLOGNA3 (IT) Latvia ------ VERSIA LTD, 5 Kleistu st., LV-1067 Riga, Latvia, LATVIA 1:701 Alternet 2:1800 ICM-Atlantic ---------- 194.8.8/24 VERNET (LV) Netherlands ----------- Bausch Datacom B.V., Veldweg 33, NL-6075 NL Herkenbosch, NETHERLANDS 1:701 Alternet 2:1800 ICM-Atlantic ------------ 193.78.98/24 BAUSCH (NL) Dupaco B.V., 't Koendert 8, 3831 RB Leusden, NETHERLANDS 1:701 Alternet 2:1800 ICM-Atlantic ------------- 193.78.180/24 DUPACO (NL) 193.78.181/24 DUPACO (NL) RIPE Network Coordination Centre (NCC), PRIDE Project, Kruislaan 409, NL-1098 SJ Amsterdam, Netherlands, NETHERLANDS 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific --------- 164.40/16 RIPE-TMP-SHOWNET (NL) Stichting NLnet, Kruislaan 419, NL-1098 VA Amsterdam, NETHERLANDS 1:701 Alternet 2:1800 ICM-Atlantic ------------- 193.78.245/24 NLNET (NL) 193.78.246/24 NLNET (NL) 193.78.247/24 NLNET-CONF (NL) 193.78.248/24 NLNET-CONF (NL) Unisource Business Networks, P.O. Box 90934, NL-2509 LX The Hague, NETHERLANDS 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1674 CERN/DANTE 4:1240 ICM-Pacific ------------- 193.172.11/24 EMPB (NL) Norway ------ Oceanor A/S, Pircentret, N-7005 Trondheim, NORWAY 1:1800 ICM-Atlantic 2:1879 EUROPE-RS 3:1133 CERN/DANTE 4:1240 ICM-Pacific ------------ 193.216.3/24 NO-OCEANOR1 (NO) TelePost Communication AS, P.O.Box 335, Skoyen, N-0212 Oslo, NORWAY 1:1800 ICM-Atlantic 2:1879 EUROPE-RS 3:1133 CERN/DANTE 4:1240 ICM-Pacific ------------ 193.212.6/24 TPC6NET (NO) Russian Federation ------------------ RELCOM Corp., 3, Raspletina st., Moscow, RUSSIAN FEDERATION 1:701 Alternet 2:1800 ICM-Atlantic -------------- 193.125.172/24 RELCOM-EXPO (RU) 193.125.173/24 RELCOM-EXPO (RU) 193.125.174/24 RELCOM-EXPO (RU) 193.125.175/24 RELCOM-EXPO (RU) Slovenia -------- NIL Systems Integration & Consulting Ltd., Leskoskova 4, 61000 Ljubljana, SLOVENIA 1:701 Alternet 2:1800 ICM-Atlantic ----------- 193.77.3/24 NILNET-1 (SI) 193.77.8/24 SINET-SLIP-INET (SI) Sweden ------ Handelshogskolan, Box 6501, S-113 83 Stockholm, SWEDEN 1:1800 ICM-Atlantic 2:1879 EUROPE-RS 3:1133 CERN/DANTE 4:1240 ICM-Pacific ------------ 193.10.48/24 SE-HHS (SE) United Kingdom -------------- Gwent Collge of Higher Education, Allt-Yr-Yn Avenue, Newport, Gwent, NP9 5XA, UNITED KINGDOM 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific ------------ 193.63.82/24 GWENT-NET (GB) JANET, c/o ULCC, 20 Guilford Street, London, WC1N 1DZ, UNITED KINGDOM 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific ---------- 138.250/15 JANET-AGGR-2 (GB) 143.52/15 JANET-AGGR-3 (GB) 193.60/14 JANET-AGGR-1 (GB) 194.66/16 JANET-AGGR-4 (GB) Manchester University, MCC, Oxford Road, Manchester, M13 9PL, UNITED KINGDOM 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific ------------ 192.84.76/22 MANUNI-AGGR-1 (GB) 192.84.80/22 MANUNI-AGGR-2 (GB) 192.150.178/23 MANUNI-AGGR-3 (GB) 192.150.180/23 MANUNI-AGGR-4 (GB) Natural Environment Research Council, 4th Floor, Holbrook House, Swindon, Wiltshire, SN1 1DE, UNITED KINGDOM 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific -------------- 192.171.130/23 NERC-AGGR-1 (GB) 192.171.134/23 NERC-AGGR-2 (GB) 192.171.136/23 NERC-AGGR-3 (GB) 192.171.142/23 NERC-AGGR-4 (GB) 192.171.144/22 NERC-AGGR-5 (GB) 192.171.148/23 NERC-AGGR-6 (GB) 192.171.154/23 NERC-AGGR-7 (GB) 192.171.156/22 NERC-AGGR-8 (GB) 192.171.160/22 NERC-AGGR-9 (GB) 192.171.164/23 NERC-AGGR-10 (GB) 192.171.168/21 NERC-AGGR-11 (GB) 192.171.176/23 NERC-AGGR-12 (GB) 192.171.180/22 NERC-AGGR-13 (GB) 192.171.184/23 NERC-AGGR-14 (GB) 192.171.190/23 NERC-AGGR-15 (GB) 192.171.192/22 NERC-AGGR-16 (GB) 192.171.196/23 NERC-AGGR-17 (GB) Oxford University, Computing Services, 13 Banbury Road, Oxford, Oxfordshire, OX2 6NN, UNITED KINGDOM 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific ----------- 192.76.6/23 OXUNI-AGGR-1 (GB) 192.76.8/23 OXUNI-AGGR-2 (GB) 192.76.12/22 OXUNI-AGGR-3 (GB) 192.76.16/23 OXUNI-AGGR-4 (GB) 192.76.20/23 OXUNI-AGGR-5 (GB) 192.76.26/23 OXUNI-AGGR-6 (GB) 192.76.28/22 OXUNI-AGGR-7 (GB) 192.82.242/23 KEELEUNI-AGGR-1 (GB) Queen Mary and Westfield College, Computer Science Dept, Mile End Road, London, E1 4NS, UNITED KINGDOM 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific -------------- 192.135.232/23 QMW-AGGR-1 (GB) Royal Free Hospital School of Medicine, Rowland Hill Street, London, NW3 2PF, UNITED KINGDOM 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific -------------- 192.160.178/23 RFHSM-AGGR-1 (GB) University of Brighton, Watts Building, Lewes Road, Mouselecoomb, Brighton, BN2 4GJ, UNITED KINGDOM 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific -------------- 192.173.128/21 BTONUNI-AGGR-1 (GB) University of Edinburgh, Computing Service, Kings Buildings, Edinburgh, Scotland, EH9 3JZ, UNITED KINGDOM 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific ------------- 192.41.102/23 EDUNI-AGGR-1 (GB) 192.41.104/23 EDUNI-AGGR-2 (GB) 192.41.108/23 EDUNI-AGGR-3 (GB) 192.41.112/22 EDUNI-AGGR-4 (GB) University of Northumbria at Newcastle, Computer Unit, Northumberland Building, Newcastle-upon-Tyne, NE1 8ST, UNITED KINGDOM 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific ------------ 192.173.2/23 UNN-AGGR-1 (GB) University of Ulster, Cromore Road, Coleraine, Co Londonderry, Northern Ireland, BT52 1SA, UNITED KINGDOM 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific ------------- 192.195.42/23 ULSTUNI-AGGR-1 (GB) United States ------------- Associate Business Publications, 41 East 42nd St., Suite 921, New York, NY 10017, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.181/24 PSINET-C5 (US) BMC Software, Inc., BMC Software, Inc. P.O. Box 2002 Sugar Land, TX 77487-2002, USA 1:114 SESQUINET Regional Network -------------- 198.147.191/24 BMCPRODNET (US) 198.147.192/22 BMCAUSTIN (US) BMC Software, Inc., PO Box 2002, Sugarland, TX 77487-2002, USA 1:114 SESQUINET Regional Network -------------- 198.175.229/24 BMCAUSTR-C-175-229 (US) 198.175.230/24 BMCAUSTR-C-175-230 (US) BMC Software, Inc., po box 2002, Sugarland, TX 77487-2002, USA 1:114 SESQUINET Regional Network -------------- 198.207.223/24 BMCENET (US) C-CUBE, 1778 McCarthy Blvd., Milpitas, CA 95035, USA 1:2551 NETCOM -------------- 198.232.212/23 NETBLK-CCUBE-NET (US) CAD Solutions, Inc., 2841 Junction Ave. #200, San Jose, CA 95134, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.175/24 PSINET-C5 (US) Chattanooga Public Schools, 1161 West 40th Street, Chattanooga, TN 47409, USA 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) ------------- 198.146.12/24 CPS-NET-C-146-12 (US) 198.146.13/24 CPS-NET-C-146-13 (US) DLA Systems Automation Center, 3990 East Broad Street, Columbus, OH 43216, USA 1:19 Milnet (FIX-East) 2:568 Milnet (FIX-West) --------- 147.48/16 DFAS-C (US) Data Switch Corp., 1 Enterprise Drive, Shelton, CT 06484, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.178/24 PSINET-C5 (US) House Ear Institute, 2100 West 3rd Street, Los Angeles, CA 90057, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.177/24 PSINET-C5 (US) Innovative Emergency Management, Lakeside Plaza I, 5215 W. Wiley Post Way, Ste 100, Salt Lake City, UT 84116, USA 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) -------------- 199.181.232/24 ARIEL (US) Jacksonville State University, Computer Center Bldg., Trustee Circle, Jacksonville, AL 36265, USA 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) ------------ 199.88.30/24 JVILLE-NET (US) Livingston University, Station #15, Livingston, AL 35470, USA 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) ------------ 199.88.23/24 LIVINGSTON-NET (US) Louisiana College, 1140 College Dr., Pineville, LA 71359, USA 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) -------------- 198.199.133/24 LACOLLEGE (US) MSCI MAGIC Gigabit Testbed (NETBLK-MAGIC-C), 1200 Washington Avenue South, Minneapolis, MN 55415, USA 1:555 Minnesota Supercomputer Center Network (MSCNet) 2:1225 CICNET at Argonne Labs 3:267 CICNET at UIUC 4:266 CICNET at MERIT -------------- 198.207.141/24 NETBLK-MAGIC-C-C-207- (US) 198.207.142/24 NETBLK-MAGIC-C-C-207- (US) 198.207.143/24 NETBLK-MAGIC-C-C-207- (US) 198.207.144/24 NETBLK-MAGIC-C-C-207- (US) Myxa Corporation, 3837 Byron Road, Huntingdon, PA 19006-2320, USA 1:204 PSCNET Regional Network 2:1206 PSCNET Regional Network ----------- 198.56.0/21 MYXA (US) Naval Facilities Engineering, 200 Stovall Street, Alexandria, VA 22332, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.174/24 PSINET-C5 (US) Naval Hospital, Bureau of Medicine and Surgery, Long Beach, CA 90801, USA 1:19 Milnet (FIX-East) 2:568 Milnet (FIX-West) ------------ 192.108.6/24 LONGBEACHNET (US) PREPnet, 305 S. Craig Street, Pittsburgh, PA 15213, USA 1:204 PSCNET Regional Network 2:1206 PSCNET Regional Network ---------- 199.234/16 NETBLK-PREPNET-C2 (US) Pagesat Inc., 992 San Antonio Rd., Palo Alto, CA 94303, USA 1:1740 CERFnet ------------- 198.175.15/24 PAGESAT-C8 (US) Performance Systems Int'l, Inc, 510 Huntmar Park Drive, Herndon, VA 22070, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ---------- 199.100/16 PSINET-NETBLK-C5 (US) R. R. Donnelley & Sons, 750 Warrenville Road, Lisle, IL 60532, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI --------- 162.27/16 RRD (US) Rice University-Sesquinet, 6100 South Main, Houston, TX 77251, USA 1:114 SESQUINET Regional Network ---------- 198.170/15 SESQUINET-CIDR-02 (US) 198.172/15 SESQUINET-CIDR-02 (US) Rockwell Internationl Corporation, 2201 Seal Beach Boulevard, PO Box 2515, Seal Beach, CA 90740-1515, USA 1:114 SESQUINET Regional Network ------------ 199.33.92/24 NETBLK-ROCKWELL (US) SURAnet, 8400 Baltimore Blvd., College Park, MD 20740, USA 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) ------------- 192.221.52/24 NETBLK-SURA-SUB-PRJ (US) Sandia National Laboratories, PO Box 5800, Org 1954, Albuquerque, NM 87185, USA 1:377 SNLA (Sandia National Laboratories) -------------- 198.206.223/24 NET-SNL (US) Sherwin Williams Company, 101 Prospect Ave, Cleveland, OH 44115, USA 1:1325 ANS Cleveland - DNSS 43 ------------- 198.81.216/24 SHERWIN-DMZ (US) Sprint, 13221 Woodland Park Road, Herndon, VA 22071, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ----------- 199.1.23/24 NETBLK-SPRINT-BLKA (US) Sumitomo Bank Capital Markets, 1 World Trade Center, Suite 9651, New York, NY 10048, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.179/24 PSINET-C5 (US) The Timken Co., 4500 Mt. Pleasant Rd, North Canton, OH 44720, USA 1:600 OARNET, Cleveland, OH 2:1800 ICM-Atlantic ---------- 147.185/16 NET-TIMKEN (US) United States Department of State, 22nd and D St., NW, Washington, DC 20520, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.180/24 PSINET-C5 (US) United States Internet Inc., 5016 Mountain Crest Drive, Knoxville, TN 37918, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ----------- 199.1.48/24 NETBLK-USIT-C-1-48 (US) 199.1.49/24 NETBLK-USIT-C-1-49 (US) 199.1.50/24 NETBLK-USIT-C-1-50 (US) 199.1.51/24 NETBLK-USIT-C-1-51 (US) 199.1.52/24 NETBLK-USIT-C-1-52 (US) 199.1.53/24 NETBLK-USIT-C-1-53 (US) 199.1.54/24 NETBLK-USIT-C-1-54 (US) 199.1.55/24 NETBLK-USIT-C-1-55 (US) 199.1.56/24 NETBLK-USIT-C-1-56 (US) 199.1.57/24 NETBLK-USIT-C-1-57 (US) 199.1.58/24 NETBLK-USIT-C-1-58 (US) 199.1.59/24 NETBLK-USIT-C-1-59 (US) 199.1.60/24 NETBLK-USIT-C-1-60 (US) 199.1.61/24 NETBLK-USIT-C-1-61 (US) 199.1.62/24 NETBLK-USIT-C-1-62 (US) 199.1.63/24 NETBLK-USIT-C-1-63 (US) Univ. of Miss. Medical Center, 2500 N. State ST., Jackson, MS 39216, USA 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) ------------ 199.76.57/24 NETBLK-UMSMEDCTR10 (US) Vision Associates Inc., 300 Burr Street, Fairfield, CT 06430, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.176/24 PSINET-C5 (US) Workgroup Technology Corp., 81 Hartwell Avenue, Lexington, MA 02173, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI -------------- 192.195.247/24 WORKGROUP (US) ========================================================== The following Midlevel/Regional peering sessions have also been added: AS 3388 - UNM-AS - ENSS 191 Peer: 198.83.5.3 - Advanced Network and Services, Inc., 100 Clearbrook Road, Elmsford, NY 10523, USA - Router-name unknown AS690 CIDR Squeezings Report: 2421 Nets, 39 ASs, 326 Aggregates ---------------------------------------------------------------- 2421 (58%) of the ever-announced more-specific routes within aggregates have been withdrawn. 1391 of those were withdrawn within the last week. 523 the week before that. 221 the week before that. 39 ASs have registered aggregates in the PRDB. 31 of those are announcing aggregates. 20 have withdrawn at least one more specific route. 326 Aggregates are configured. 299 of these were Top-Level Aggregates (not nested in another aggregate). 144 of these are being announced to AS690. 126 of those have at least one subnet configured (the other 18 may be saving. the Internet future subnet announcements). 97 have stopped announcing at least one configured more specific route. 92 have stopped announcing half of their configured more specific routes. 74 have stopped announcing most (80%) of their more specific routes. See 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.t3p Information is also avaiable through the PRDB whois server. Type "whois -h prdb.merit.edu help" for details. -------------------------------------------------------------------------- REPORT CHANGES: (Updated March 24, 1994) Metric:AS(NSS) - Historically, peer networks with multiple connections to AS 690 could only select which of those connections their networks would take by creating "Fake" AS numbers, and using those in the PRDB Metric:AS announcement lists. Some time in the next few weeks we will begin supporting an expanded syntax, where the AS may be followed by an optional NSS peer number in parentheses. Eventually, this syntax will be used to replace most or all of the current Fake ASs. This change will affect *all* places that the announcement lists are reported: all whois queries, all network reports, this "NWG" report, and the Auto-NACR. If you have code which parses these announcement lists, please be aware that that code may need modifications soon. CIDR Reports: There is a new "whois" option to list aggregates in the PRDB: whois -h prdb.merit.edu listaggs will produce a listing of the currently registered aggregates. There is also a new report on "nestings" of PRDB-registered aggregates with their more specific routes: nets.non-classful. Anyone considering configuring an aggregate into the PRDB (and you all should be!) is encouraged to pre-check that aggregate by typing the command: whois -h prdb.merit.edu 'aggchk ' (where "" is the aggregate description). This command will list all of the other entries in the PRDB that are more specific routes of , as well as any aggregates all ready configured that contain . The output includes the AUP and announcement lists of each of the nets printed, with discrepancies flagged. This is the same program that we use for sanity-checking the NACRs that you submit. The archived discussion list "db-disc@merit.edu" exists for discussion of PRDB issues. Send a message to "db-disc-request@merit.edu" to subscribe. --Dale Johnson (dsj@merit.edu) -------------------------------------------------------------------------- Please send all requests for configuration changes to nsfnet-admin@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. ******************************* --Steve Widmayer Merit/NSFNET skw@merit.edu --Enke Chen Merit/NSFNET enke@merit.edu --Steven J. Richardson Merit/NSFNET sjr@merit.edu - - - - - - - - - - - - - - - - - From list-admin Tue Apr 26 11:38:21 1994 Received: from pepper.merit.edu (pepper.merit.edu [35.42.1.50]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id LAA05739 for ; Tue, 26 Apr 1994 11:38:21 -0400 Received: by pepper.merit.edu (4.1/client-0.9) id AA00980; Tue, 26 Apr 94 11:38:20 EDT From: epg@merit.edu Message-Id: <9404261538.AA00980@pepper.merit.edu> Subject: A new tool to expand aggregate (fwd) To: regional-techs@merit.edu Date: Tue, 26 Apr 94 11:38:19 EDT X-Mailer: ELM [version 2.3 PL11] Just in case some folks are not on the other two lists. --Elise Forwarded message: > From lpj@merit.edu Tue Apr 26 10:02:43 1994 > From: Laurent Joncheray > Message-Id: <199404261357.JAA25563@merit.edu> > Subject: A new tool to expand aggregate > To: bgpd@merit.edu, routing-wg@ripe.net > Date: Tue, 26 Apr 94 9:57:02 EDT > X-Mailer: ELM [version 2.3 PL11] > > A new tool ("aggrwalk") to expand an aggregate into known compoments > is available on rrdb.merit.edu:pub/meritrr/aggrwalk.tar.Z > This tool gets all the info from the RIPE database, Merit Routing > Registry DB, and NSF DB. It also adds usefull info like home AS, network > name or NSF announcement list. Here is an example: > > % aggrwalk.pl -a -A cntry 193.74.240/20 > Connected to ALC server > > Aggregate Database(s) homeas cntry > > <193.74.240/24> RIPE-DB BE > <193.74.241/24> RIPE-DB BE > <193.74.242/24> RIPE-DB AS1891 BE > <193.74.243/24> RIPE-DB BE > <193.74.244/24> RIPE-DB BE > <193.74.245/24> RIPE-DB BE > <193.74.247/24> RIPE-DB BE > <193.74.248/24> RIPE-DB BE > <193.74.249/24> RIPE-DB AS1891 BE > <193.74.250/24> RIPE-DB:NSF_DB AS1891 BE > <193.74.251/24> RIPE-DB AS1891 BE > <193.74.252/24> RIPE-DB AS1891 BE > <193.74.254/24> RIPE-DB AS1891 BE > > > > -- > Laurent Joncheray, E-Mail: lpj@merit.edu > Merit Network Inc, 1071 Beal Avenue, Phone: +1 (313) 936 2065 > Ann Arbor, MI 48109, USA Fax: +1 (313) 747 3745 > "This is the end, Beautiful friend. This is the end, My only friend, the end" JM > - - - - - - - - - - - - - - - - - From list-admin Tue Apr 26 15:13:26 1994 Received: from localhost (jyy@localhost) by merit.edu (8.6.8.1/merit-1.0) with SMTP id PAA26656; Tue, 26 Apr 1994 15:13:26 -0400 Message-Id: <199404261913.PAA26656@merit.edu> To: bgpd@merit.edu, regional-techs@merit.edu cc: jyy@merit.edu Subject: BGP4 software info Date: Tue, 26 Apr 1994 15:13:25 -0400 From: Jessica Yu Hi, I received 17 responses since I sent my message yesterday. Thanks to those who responded quickly and provide the information. Below is a summary of the responses. It shows the kind of software version people are using on the hardware platform they have and the network protocols they are supporting. Hope this gives those who are planning on or in the process of deploying BGP4 some idea of what software version to use. --Jessica Vendor Platform Software Version Prots in addition to IP ====== ======== ================ ======================= 1.Cisco AGS+ 10.0(0.11) 2.Cisco AGS+,3000 10.0 CLNP,DECNet 3.3Com NETBuilder II SW/NBII-HS, 6.2.2 4.Cisco AGS+ 10.0(4879) 5.Cisco 4000 10.0(0.14) 6.Cisco AGS+ 9.21+BGP4(2.2) 7.Cisco AGS+ 10.0(0.5) 8.Cisco 4000 9.21(5192) 9.Cisco AGS+ 9.21+bgp4(2.5) 10.Cisco AGS+ 9.21(5362) 11.Telebit RC5000 SWIP version 4.2 Communications 12.Cisco CGS,AGS,AGS+,4000,7000 10.0(0.14) CLNP 13.Cisco 4000 9.21+BGP4(2.1) Cisco AGS+ 10.0(4879) 14.Cisco AGS+,7000 9.21+BGP4(2.2) 15.DEC DS5000/200 Ultrix 4.2, & Cornell gated R3.5A3 16.Cisco AGS+,3000,7000 9.21+BGP4(2.2) 17.Cisco AGS+,7000 10(0.14) Other information: one has to have at least 16MB momery in order to load BGP4 software on cisco routers. Also, see Paul's notes on version selection on cisco routers. Date: Mon, 25 Apr 1994 12:28:40 PDT To: Jessica Yu cc: bgpd@merit.edu, regional-techs@merit.edu From: Paul Traina Return-Path: list-admin In-Reply-To: Your message of "Mon, 25 Apr 1994 14:17:54 EDT." <199404251817.OAA03917@merit.edu> > To: bgpd@merit.edu, regional-techs@merit.edu > Cc: jyy@merit.edu > Date: Mon, 25 Apr 1994 14:17:54 -0400 > From: Jessica Yu > > Hi, > > For those who already run BGP4, would you please provide the following information : > > Vendor routers (e.g. Cisco, Proteon ...etc) > Hardward platform (e.g. Cisco 7000, 4000 .. etc) > Software version > other info which you think is valuable for new users > > We have been asked about these kinds of questions from people who are working on > deploying BGP4. Please help. > > Please send your information to me. I will summerize it and post it to the list. > Thanks! > > --jessica Just as a side note, 10.0 has left beta, and we are suggesting that everyone who is migrating to BGP4 run 10.0, instead of 9.21+BGP4, since 10.0 receives better support (9.21+BGP4 is on the way out). - - - - - - - - - - - - - - - - - From list-admin Wed Apr 27 18:11:26 1994 Received: from is.rice.edu (root@is.rice.edu [128.42.42.24]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id SAA21533; Wed, 27 Apr 1994 18:11:25 -0400 Received: from sabine.is.rice.edu by is.rice.edu (AA05065); Wed, 27 Apr 94 17:11:22 CDT Received: by sabine.is.rice.edu (AA25544); Wed, 27 Apr 94 17:09:18 CDT From: bmanning@is.rice.edu (William Manning) Message-Id: <9404272209.AA25544@sabine.is.rice.edu> Subject: innocent remark To: bgpd@merit.edu Date: Wed, 27 Apr 94 17:09:17 CDT Cc: regional-techs@merit.edu X-Mailer: ELM [version 2.3 PL11] From another list... given that a BSD/386 or NetBSD system can be put together quite cheaply and does a fine job at handling PPP and SLIP and multiple ethernets, this seems like a fine alternative to dedicated routers like Cisco for T1/E1-speed internet gateways. especially considering the power of GateD 3.5, and that a 16MB cisco can't handle a "full internet route table" while a 16MB i486 machine can do it easily. ... Comments from the gated crowd? The cisco crowd? -- Regards, Bill Manning - - - - - - - - - - - - - - - - - From list-admin Wed Apr 27 18:44:05 1994 Received: from titan.sprintlink.net (titan.sprintlink.net [199.0.55.78]) by merit.edu (8.6.8.1/merit-1.0) with ESMTP id SAA23420; Wed, 27 Apr 1994 18:44:05 -0400 Received: (from avg@localhost) by titan.sprintlink.net (8.6.8/8.6.8) id SAA02940; Wed, 27 Apr 1994 18:44:04 -0400 Date: Wed, 27 Apr 1994 18:44:04 -0400 From: Vadim Antonov Message-Id: <199404272244.SAA02940@titan.sprintlink.net> To: bgpd@merit.edu, bmanning@is.rice.edu Subject: Re: innocent remark Cc: regional-techs@merit.edu BSD/386 can handle full routing table with some amount of tweaking. Also, gated becomes essentially useless as soon as system starts to do paging; so it's better 64Mb or more :-) Reliability of 486 platforms... closer to non-existant. ciscos do not cost $$$s for nothing. Also, ciscos are much more manageable. There are several real-life E-1 BSD/386 routers in the Internet, though owners want to replace them with ciscos (capacity problems). --vadim - - - - - - - - - - - - - - - - - From list-admin Wed Apr 27 19:46:24 1994 Received: from interlock.ans.net (interlock.ans.net [147.225.1.3]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id TAA26877; Wed, 27 Apr 1994 19:46:23 -0400 Received: by interlock.ans.net id AA38333 (InterLock SMTP Gateway 1.1); Wed, 27 Apr 1994 19:46:13 -0400 Received: by interlock.ans.net (Internal Mail Agent-2); Wed, 27 Apr 1994 19:46:13 -0400 Received: by interlock.ans.net (Internal Mail Agent-1); Wed, 27 Apr 1994 19:46:13 -0400 From: Curtis Villamizar Message-Id: <199404272343.AA104908@foo.ans.net> To: Vadim Antonov Cc: bgpd@merit.edu, bmanning@is.rice.edu, regional-techs@merit.edu, curtis@ans.net Subject: Re: innocent remark In-Reply-To: (Your message of Wed, 27 Apr 94 18:44:04 D.) <199404272244.SAA02940@titan.sprintlink.net> Date: Wed, 27 Apr 94 19:43:08 -0500 Bill, Vadim, This discussion doesn't really belong on this list, but since Vadim has told some untruths about gated needing more than 64MB of memory... > BSD/386 can handle full routing table with some amount of tweaking. > Also, gated becomes essentially useless as soon as system starts > to do paging; so it's better 64Mb or more :-) Most of the ANS routers run 32 MB and run gated. A few have 64 MB. If we didn't have the scram utility holding it's own routing table (used to load routes into smart cards), we could probably get away with 32 MB almost everywhere. Yes - we do take full routing. The SGI I am typing on has 32 MB and runs gated and takes full routing and does full logging and I do compiles and other stuff with no problem. > Reliability of 486 platforms... closer to non-existant. ciscos > do not cost $$$s for nothing. Also, ciscos are much more > manageable. The reliability of a Cisco is better, but PCs are not as bad as you say. The manageability issue, I disagree with. I'd take the BSDI box any day on that count. Just try expressing the policy on one of our major ENSS routers on a Cisco. A BSDI box doesn't need a host to tftp boot images and configs from (on the odd chance that you ever update your Cisco software or have a config that doesn't fit into NVRAM) and doesn't need a host to tftp logs to (on the odd chance that anything ever goes wrong in a network and you need logging or tracing). > There are several real-life E-1 BSD/386 routers in the Internet, > though owners want to replace them with ciscos (capacity problems). > > --vadim I don't think a PC today can realistically handle even one T1 at full capacity. Also PC ethernet cards are sufficiently miserable that you can only put one in a PC and get it to use the full ethernet bandwidth. Makes a fine 56k router or a low end dial in PPP or SLIP server if you can live with one ethernet. Beyond that, the PC hardware just isn't there yet. Cisco doesn't make a laptop. :-) Curtis - - - - - - - - - - - - - - - - - From list-admin Wed Apr 27 19:41:36 1994 Received: from cider.cisco.com (cider.cisco.com [131.108.13.133]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id TAA26832; Wed, 27 Apr 1994 19:41:35 -0400 Received: from localhost.cisco.com by cider.cisco.com with SMTP id AA05269 (5.67a/IDA-1.5); Wed, 27 Apr 1994 16:41:02 -0700 Message-Id: <199404272341.AA05269@cider.cisco.com> To: bmanning@is.rice.edu (William Manning) Cc: bgpd@merit.edu, regional-techs@merit.edu From: pst@shockwave.com (Paul Traina) Subject: Re: innocent remark In-Reply-To: Your message of "Wed, 27 Apr 1994 17:09:17 CDT." <9404272209.AA25544@sabine.is.rice.edu> Date: Wed, 27 Apr 1994 16:41:01 -0700 Sender: pst@cisco.com From: bmanning@is.rice.edu (William Manning) Subject: innocent remark >From another list... given that a BSD/386 or NetBSD system can be put together quite cheaply and does a fine job at handling PPP and SLIP and multiple ethernets, this seems like a fine alternative to dedicated routers like Cisco for T1/E1-speed internet gateways. especially considering the power of GateD 3.5, and that a 16MB cisco can't handle a "full internet route table" while a 16MB i486 machine can do it easily. ... Comments from the gated crowd? The cisco crowd? Go for it, have a party. I've got 2 BSD boxes myself, and I prefer them over clunky cisco routers. Besides, have you ever been able to play DOOM on an AGS? -- Regards, Bill Manning - - - - - - - - - - - - - - - - - From list-admin Wed Apr 27 20:38:20 1994 Received: from interlock.ans.net (interlock.ans.net [147.225.1.3]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id UAA00591; Wed, 27 Apr 1994 20:38:19 -0400 Received: by interlock.ans.net id AA02899 (InterLock SMTP Gateway 1.1); Wed, 27 Apr 1994 20:38:16 -0400 Received: by interlock.ans.net (Internal Mail Agent-2); Wed, 27 Apr 1994 20:38:16 -0400 Received: by interlock.ans.net (Internal Mail Agent-1); Wed, 27 Apr 1994 20:38:16 -0400 Message-Id: <199404280035.AA115158@foo.ans.net> To: bmanning@is.rice.edu (William Manning) Cc: bgpd@merit.edu, regional-techs@merit.edu Subject: Re: innocent remark In-Reply-To: Your message of "Wed, 27 Apr 1994 17:09:17 CDT." <9404272209.AA25544@sabine.is.rice.edu> Date: Wed, 27 Apr 1994 20:35:10 -0400 From: Dennis Ferguson > given that a BSD/386 or NetBSD system can be put together quite cheaply and > does a fine job at handling PPP and SLIP and multiple ethernets, this seems > like a fine alternative to dedicated routers like Cisco for T1/E1-speed > internet gateways. especially considering the power of GateD 3.5, and that > a 16MB cisco can't handle a "full internet route table" while a 16MB i486 > machine can do it easily. The end of the last sentence is wrong (the start of the last sentence might be too, though I'm biased enough to maybe believe it). I know for a fact that, while gated's memory usage is not unreasonable, gated code does tend to resolve memory/CPU tradeoffs in favour of spending memory and saving CPU. And the per-route memory consumption in the Net/II kernel forwarding table is way out of line with what a decent router implementation should do. If you want your 486 box to compete with a 16MB cisco you really need to buy it a couple of extra rows of SIMMs. By the time you get enough neighbours and alternate paths in there to overwhelm a 16MB Cisco the 16MB 486 box will be spending most of its time trying to get large chunks of gated into and out of the page space, though a 32MB 486 box should still be pretty chipper. My (somewhat dated) observation is that i486 machines also seem to do a whole lot of work to get quite mediocre packet-per-second forwarding rates. On the other hand, if you buy it a good screen and interface card, the graphics are much better than even a 64MB Cisco. Dennis Ferguson - - - - - - - - - - - - - - - - - From list-admin Wed Apr 27 20:52:09 1994 Received: from hawksbill.sprintmrn.com ([199.11.1.3]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id UAA01695; Wed, 27 Apr 1994 20:52:00 -0400 Received: by hawksbill.sprintmrn.com (5.65/1.34) id AA15209; Wed, 27 Apr 94 20:53:52 -0500 From: paul@hawksbill.sprintmrn.com (Paul Ferguson) Message-Id: <9404280153.AA15209@hawksbill.sprintmrn.com> Subject: Re: innocent remark To: pst@shockwave.com (Paul Traina) Date: Wed, 27 Apr 1994 20:53:52 -0500 (EST) Cc: bgpd@merit.edu, regional-techs@merit.edu In-Reply-To: <199404272341.AA05269@cider.cisco.com> from "Paul Traina" at Apr 27, 94 04:41:01 pm X-Mailer: ELM [version 2.4 PL22] Content-Type: text Content-Length: 646 >> Comments from the gated crowd? The cisco crowd? > > Go for it, have a party. I've got 2 BSD boxes myself, and I prefer them > over clunky cisco routers. Besides, have you ever been able to play > DOOM on an AGS? > > -- > Regards, > Bill Manning > OBoff-topic: You can have 'em, Bill. I think I've got better uses for my Unix boxes anyway. _______________________________________________________________________________ Paul Ferguson US Sprint Enterprise Internet Engineering tel: 703.904.2437 Herndon, Virginia USA internet: paul@hawk.sprintmrn.com - - - - - - - - - - - - - - - - - From list-admin Wed Apr 27 22:27:41 1994 Received: from ns.iij.ad.jp (root@ns.iij.ad.jp [192.244.176.33]) by merit.edu (8.6.8.1/merit-1.0) with ESMTP id WAA07380; Wed, 27 Apr 1994 22:27:39 -0400 Received: from terminus.iij.ad.jp (terminus.iij.ad.jp [192.244.191.56]) by ns.iij.ad.jp (8.6.9+2.4Wb/3.3Wb-NS) with ESMTP id LAA22317; Thu, 28 Apr 1994 11:27:36 +0900 Received: from terminus.iij.ad.jp by terminus.iij.ad.jp (8.6.5/iij-slave) id LAA02611; Thu, 28 Apr 1994 11:27:36 +0900 Message-Id: <199404280227.LAA02611@terminus.iij.ad.jp> To: bmanning@is.rice.edu (William Manning), bgpd@merit.edu, regional-techs@merit.edu Subject: Re: innocent remark In-reply-to: Your message of "Wed, 27 Apr 1994 20:35:10 -0400." <199404280035.AA115158@foo.ans.net> Date: Thu, 28 Apr 1994 11:27:35 +0900 From: David R Conrad >> a 16MB cisco can't handle a "full internet route table" while a 16MB i486 >> machine can do it easily. SL-IIJ-1>show ip b s BGP table version is 9430997, main routing table version 9430997 19216 network entries (32713 paths) using 2945880 bytes of memory 917 BGP path attribute entries using 73740 bytes of memory ... SL-IIJ-1>show mem free Head FreeList Total(b) Used(b) Free(b) Largest(b) Processor 310824 2E96D0 13315724 7699588 5616136 5131068 I/O 6000000 2F04B4 1047544 370708 676836 676836 SRAM 1000 2F11E8 65412 34760 30652 30652 SL-IIJ-1> show ver ... cisco 4000 (68030) processor (revision 0xA0) with 16384K/1024K bytes of memory. ... Cheers, -drc - - - - - - - - - - - - - - - - - From list-admin Wed Apr 27 22:39:25 1994 Received: from psi.com (psi.com [192.67.6.2]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id WAA08188; Wed, 27 Apr 1994 22:39:25 -0400 Received: from us.psi.com by psi.com (4.1/2.1-PSI/PSINet) id AA10201; Wed, 27 Apr 94 22:38:52 EDT Received: by us.psi.com (4.1/SMI-4.1.3-PSI-pop) id AA06724; Wed, 27 Apr 94 22:38:52 EDT Message-Id: <9404280238.AA06724@us.psi.com> To: Dennis Ferguson Cc: bmanning@is.rice.edu (William Manning), bgpd@merit.edu, regional-techs@merit.edu Subject: Re: innocent remark In-Reply-To: Your message of "Wed, 27 Apr 1994 20:35:10 EDT." <199404280035.AA115158@foo.ans.net> Date: Wed, 27 Apr 1994 22:38:11 -0400 From: "Martin Lee Schoffstall" there are a number of companies that have made modest enhancements (some of which you have mentioned) to NetBSD and are or will be deploying routers based on the code using PC or other SBC "platforms". I consider these people to be the "cloners" like a gateway or a dell. They make wonderful 1e1T, 1e1B (BRI), and 1e1V (v.32bis) "edge" routers, but like the PC cloners they will set their sights higher and higher. Marty > > given that a BSD/386 or NetBSD system can be put together quite cheaply and > > does a fine job at handling PPP and SLIP and multiple ethernets, this seems > > like a fine alternative to dedicated routers like Cisco for T1/E1-speed > > internet gateways. especially considering the power of GateD 3.5, and that > > a 16MB cisco can't handle a "full internet route table" while a 16MB i486 > > machine can do it easily. > > The end of the last sentence is wrong (the start of the last sentence > might be too, though I'm biased enough to maybe believe it). I know > for a fact that, while gated's memory usage is not unreasonable, gated > code does tend to resolve memory/CPU tradeoffs in favour of spending > memory and saving CPU. And the per-route memory consumption in the > Net/II kernel forwarding table is way out of line with what a decent > router implementation should do. If you want your 486 box to compete > with a 16MB cisco you really need to buy it a couple of extra rows of > SIMMs. By the time you get enough neighbours and alternate paths in > there to overwhelm a 16MB Cisco the 16MB 486 box will be spending most > of its time trying to get large chunks of gated into and out of the > page space, though a 32MB 486 box should still be pretty chipper. > > My (somewhat dated) observation is that i486 machines also seem to do > a whole lot of work to get quite mediocre packet-per-second forwarding > rates. On the other hand, if you buy it a good screen and interface card, > the graphics are much better than even a 64MB Cisco. > > Dennis Ferguson - - - - - - - - - - - - - - - - - From list-admin Wed Apr 27 21:58:33 1994 Received: from hsdndev.harvard.edu (hsdndev.harvard.edu [128.103.202.40]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id VAA05855; Wed, 27 Apr 1994 21:58:33 -0400 Date: Wed, 27 Apr 94 21:58:28 -0400 From: sob@hsdndev.harvard.edu (Scott Bradner) Message-Id: <9404280158.AA21475@hsdndev.harvard.edu> To: avg@sprint.net, curtis@ans.net Subject: Re: innocent remark Cc: bgpd@merit.edu, bmanning@is.rice.edu, regional-techs@merit.edu Some real data, these are test results for throughput (max zero loss rate) for the Novell multiprotocol router running on a 486 box. these results are for ethernet to ethernet through a T1 line, the limiting factor is the T1. There are more sults on hsdndev.harvard.edu in pub/ndtl. Small packets run at about a half T1, large packets at about 75%. The limit is not in the PC it is in the serial line interface. (the same PC can run at more than 50Mb/sec fddi to fddi.) Scott 0064 byte packets total: 043891 duration: 000028 total rate: 001567 pps packet 020: 043891 (001567 pps) 0128 byte packets total: 029089 duration: 000028 total rate: 001038 pps packet 020: 029089 (001038 pps) 0256 byte packets total: 017951 duration: 000029 total rate: 000619 pps packet 020: 017951 (000619 pps) 0512 byte packets total: 009585 duration: 000028 total rate: 000342 pps packet 020: 009585 (000342 pps) 0768 byte packets total: 006483 duration: 000028 total rate: 000231 pps packet 020: 006483 (000231 pps) 1024 byte packets total: 004172 duration: 000028 total rate: 000149 pps packet 020: 004172 (000149 pps) 1280 byte packets total: 003509 duration: 000029 total rate: 000121 pps packet 020: 003509 (000121 pps) 1518 byte packets total: 002958 duration: 000029 total rate: 000102 pps packet 020: 002958 (000102 pps) - - - - - - - - - - - - - - - - - From list-admin Thu Apr 28 02:22:41 1994 Received: from lager.cisco.com (lager.cisco.com [131.108.11.55]) by merit.edu (8.6.8.1/merit-1.0) with ESMTP id CAA21214; Thu, 28 Apr 1994 02:22:40 -0400 Received: (tli@localhost) by lager.cisco.com (8.6.8+c/CISCO.SERVER.1.1) id XAA26017; Wed, 27 Apr 1994 23:21:36 -0700 Date: Wed, 27 Apr 1994 23:21:36 -0700 From: Tony Li Message-Id: <199404280621.XAA26017@lager.cisco.com> To: davidc@terminus.iij.ad.jp Cc: bmanning@is.rice.edu, bgpd@merit.edu, regional-techs@merit.edu In-Reply-To: David R Conrad's message of Thu, 28 Apr 1994 11:27:35 +0900 <199404280227.LAA02611@terminus.iij.ad.jp> Subject: innocent remark 19216 network entries (32713 paths) using 2945880 bytes of memory Head FreeList Total(b) Used(b) Free(b) Processor 310824 2E96D0 13315724 7699588 5616136 I think that it's time for folks on these mailing lists (and on the BGP list) to stop discussing the number of routes. It's really a bogus metric. Memory (at least in our implementation) is consumed for multiple reasons: paths, the AS path table, the routing table, etc. I would suggest that a much better characterization of BGP memory usage is in terms of both number of routes AND number of paths. A router with 20k routes and 20k paths uses a lot less memory than 20k routes and 100k paths. Admittedly this isn't perfect, but it's a lot better than just one dimension. We now return you to your normally scheduled confusion... Tony - - - - - - - - - - - - - - - - - From list-admin Thu Apr 28 10:21:03 1994 Received: from interlock.ans.net (interlock.ans.net [147.225.1.3]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id KAA20007 for ; Thu, 28 Apr 1994 10:21:01 -0400 Received: by interlock.ans.net id AA18843 (InterLock SMTP Gateway 1.1 for regional-techs@merit.edu); Thu, 28 Apr 1994 10:20:49 -0400 Received: by interlock.ans.net (Internal Mail Agent-2); Thu, 28 Apr 1994 10:20:49 -0400 Received: by interlock.ans.net (Internal Mail Agent-1); Thu, 28 Apr 1994 10:20:49 -0400 From: Curtis Villamizar Message-Id: <199404281417.AA33001@foo.ans.net> To: davidg@root.com Cc: regional-techs@merit.edu Subject: Re: More on PC Routers from BGPD In-Reply-To: (Your message of Wed, 27 Apr 94 18:55:51 MST.) <199404280155.SAB01335@corbin.Root.COM> Date: Thu, 28 Apr 94 10:17:44 -0500 > >I don't think a PC today can realistically handle even one T1 at full > >capacity. Also PC ethernet cards are sufficiently miserable that you > >can only put one in a PC and get it to use the full ethernet > >bandwidth. > > I'd be happy to prove this statement wrong. A 66Mhz 486 with the right > ethernet boards (16bit WD/SMC type), and running a recent version of 'FreeBSD', > can easily fully saturate 2 ethers and possibly 3...and this is all the way > to/from a client application. With bus mastering EISA adapters, the same PC > should be capable of routing traffic between two T3's at full T3 speeds (this > assertion is unproven, however). > > -DG > > David Greenman > FreeBSD development group David, My comment was incorrect on T1/E1. We were trying to do full DES encryption of a T1 stream and couldn't saturate the link using a modified BSDI kernel and a 486/66. Full T1/E1 is possible using existing cards if you don't try to encrypt. Wrt ethernet - I was under the impression that the fastest EISA card was the 3C579 and the fastest ISA the TN-1500. I'd be surprised to hear that a WD/SMC EISA card can saturate 2-3 ethernets at small packet sizes (typical traffic seen by a router). This is more a reflection of my opinion of PC card technology, not FreeBSD or BSDI. If anyone has measured troughput under small packet load, I'd be interested in hearing the result. Wrt DS3 - I didn't think a HSSI card for EISA existed. Does one exist? Also, keep in mind that routers see an average packet size on the order of 200 bytes. Do you really think an EISA bus can handle the small packet throughput? Big packets are easy, too bad real traffic isn't all big packets. Curtis BTW - I've corrected my own untruths by way of Cc. Thanks for the note and the good work that you are doing on FreeBSD. - - - - - - - - - - - - - - - - - From list-admin Thu Apr 28 14:11:44 1994 Received: from titan.sprintlink.net (titan.sprintlink.net [199.0.55.78]) by merit.edu (8.6.8.1/merit-1.0) with ESMTP id OAA13028; Thu, 28 Apr 1994 14:11:43 -0400 Received: (from avg@localhost) by titan.sprintlink.net (8.6.8/8.6.8) id OAA05486; Thu, 28 Apr 1994 14:11:39 -0400 Date: Thu, 28 Apr 1994 14:11:39 -0400 From: Vadim Antonov Message-Id: <199404281811.OAA05486@titan.sprintlink.net> To: avg@sprint.net, curtis@ans.net Subject: Re: innocent remark Cc: bgpd@merit.edu, bmanning@is.rice.edu, regional-techs@merit.edu >This discussion doesn't really belong on this list, but since Vadim >has told some untruths about gated needing more than 64MB of memory... I told that 16Mb is not enough. Memory for PCs is cheap and it's better to be safe than sorry. >The reliability of a Cisco is better, but PCs are not as bad as you >say. If you're lucky. I've seen a lot of burned PCs but only few ciscos with problems. An average PC from Pretzelz'N'Computerz simply won't work with Unix without massive tweaking. >The manageability issue, I disagree with. I'd take the BSDI box >any day on that count. Yeah. Sorry, how do i do "show ip bgp summary" on BSD/386? >Just try expressing the policy on one of our >major ENSS routers on a Cisco. That's the problem of the policy (though it's entirely different kettle of fish). Sure, cisco can't handle real big access lists. >A BSDI box doesn't need a host to tftp >boot images and configs from What is the average failure rate of cheap PC HD drives as compared to flash ROM? What do you do if after power failure fsck clears /etc? Sure, you can find an industrial-design PC but it'll cost not less than a cisco. >(on the odd chance that you ever update >your Cisco software or have a config that doesn't fit into NVRAM) and >doesn't need a host to tftp logs to (on the odd chance that anything >ever goes wrong in a network and you need logging or tracing). Never saw a configuration which does not fit into NVRAM. KISS. > There are several real-life E-1 BSD/386 routers in the Internet, > though owners want to replace them with ciscos (capacity problems). >I don't think a PC today can realistically handle even one T1 at full >capacity. I only wanted to point our that there *are* such BSDI-based routers. If you do traceroute to sovcom.kiae.su you'll see three of them. >Also PC ethernet cards are sufficiently miserable that you >can only put one in a PC and get it to use the full ethernet >bandwidth. Take a look at 3c509. It starts giving you data while the rest of a packet is still in the wire. Or, better yet, EISA model. >Makes a fine 56k router or a low end dial in PPP or SLIP server if you >can live with one ethernet. Beyond that, the PC hardware just isn't >there yet. Hey, i wrote most Ethernet drivers, all sync serial drivers and PPP stuff when i worked for BSD Inc. IMHO, you *can* do 2-3 port T-1 on a PC. >Cisco doesn't make a laptop. :-) Yeah, it also doesn't have joystick and soundblaster :-) :-) :-) --vadim - - - - - - - - - - - - - - - - - From list-admin Thu Apr 28 15:16:24 1994 Received: from interlock.ans.net (interlock.ans.net [147.225.1.3]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id PAA19864; Thu, 28 Apr 1994 15:16:22 -0400 Received: by interlock.ans.net id AA23962 (InterLock SMTP Gateway 1.1); Thu, 28 Apr 1994 15:16:18 -0400 Received: by interlock.ans.net (Internal Mail Agent-2); Thu, 28 Apr 1994 15:16:18 -0400 Received: by interlock.ans.net (Internal Mail Agent-1); Thu, 28 Apr 1994 15:16:18 -0400 Message-Id: <199404281913.AA110937@foo.ans.net> To: Vadim Antonov Cc: curtis@ans.net, bgpd@merit.edu, bmanning@is.rice.edu, regional-techs@merit.edu Subject: Re: innocent remark In-Reply-To: Your message of "Thu, 28 Apr 1994 14:11:39 EDT." <199404281811.OAA05486@titan.sprintlink.net> Date: Thu, 28 Apr 1994 15:13:12 -0400 From: Dennis Ferguson > Yeah. Sorry, how do i do "show ip bgp summary" on BSD/386? I agree this is a big defect. The traditional way of getting information from gated has long been outgrown and SNMP mostly sucks for anything other than turning something on a network monitor red. Being able to type things and see specific interesting and entirely implementation-dependent bits of internal state in response is neat, so this defect is being fixed. Dennis Ferguson - - - - - - - - - - - - - - - - - From list-admin Fri Apr 29 06:15:51 1994 Received: (sjr@localhost) by merit.edu (8.6.8.1/merit-1.0) id GAA27858 for nwg; Fri, 29 Apr 1994 06:15:51 -0400 Date: Fri, 29 Apr 1994 06:15:51 -0400 From: "Steven J. Richardson" Message-Id: <199404291015.GAA27858@merit.edu> To: nwg Subject: Additions to the NSFNET policy-based routing database ------------------------------------------------------------------------------ CIDR Progress Report: 2660 Nets, 40 ASs, 378 Aggregates. Details below. New format for Metric:AS lists coming later in this and all reports. See 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 30620 = 29 4653 25503 435 Configured Networks 29540 = 29 4653 24423 435 Added Networks 198 = 0 3 138 57 Deleted Networks 22 = 0 0 22 0 IP address Net name Country Priority:AS ---------- -------- ------- ----------- 130.226/15 DENET-CIDR C:DK 1:1800 2:1879 3:1133 4:1240 138.187/16 INFNET-PTT1 C:CH 1:1133 2:1674 3:1800 152.2/15 NCREN-AGG-002 C:US 1:1329 152.4/14 NCREN-AGG-003 C:US 1:1329 152.8/13 NCREN-AGG-004 C:US 1:1329 152.16/12 NCREN-AGG-005 C:US 1:1329 152.32/12 NCREN-AGG-006 C:US 1:1329 152.48/14 NCREN-AGG-007 C:US 1:1329 156.134/16 FRITZ C:US 1:2149 2:174 168.151/16 INTNET2-B1 C:US 1:2386 2:1321 192.35.236/23 NCREN-AGG-116 C:US 1:1329 192.47.24/24 NIFTY-SERVE C:JP 1:701 2:702 192.58.204/23 NCREN-AGG-023 C:US 1:1329 192.101.22/23 NCREN-AGG-001 C:US 1:1329 192.146.151/24 JRIVER C:US 1:1240 2:1800 192.154.36/22 NCREN-AGG-008 C:US 1:1329 192.154.40/22 NCREN-AGG-009 C:US 1:1329 192.154.46/23 NCREN-AGG-010 C:US 1:1329 192.154.48/23 NCREN-AGG-101 C:US 1:1329 192.154.50/23 NCREN-AGG-011 C:US 1:1329 192.154.52/23 NCREN-AGG-012 C:US 1:1329 192.154.56/23 NCREN-AGG-103 C:US 1:1329 192.154.60/22 NCREN-AGG-013 C:US 1:1329 192.154.64/23 NCREN-AGG-014 C:US 1:1329 192.154.68/22 NCREN-AGG-104 C:US 1:1329 192.154.76/23 NCREN-AGG-105 C:US 1:1329 192.154.78/23 NCREN-AGG-015 C:US 1:1329 192.154.82/23 NCREN-AGG-106 C:US 1:1329 192.154.84/22 NCREN-AGG-107 C:US 1:1329 192.154.88/23 NCREN-AGG-108 C:US 1:1329 192.154.92/22 NCREN-AGG-016 C:US 1:1329 192.156.209/24 ODS-HOFF-NET C:US 1:701 2:702 192.204.190/24 MCIU C:US 1:204 2:1206 192.204.252/24 ART-NET C:US 1:204 2:1206 192.217/16 NETBLK-CICNET-BLOCK C:US 1:1225 2:267 3:266 192.222.32/19 SEATTLEU-BLK C:US 1:685 2:73 3:101 192.244.176/20 IIJNET C:JP 1:701 2:702 192.247.16/20 NETBLK-RWBECK C:US 1:2551 192.251.73/24 GOLDGATE C:US 1:1740 192.251.74/24 GOLDGATE3 C:US 1:1740 193.5.56/23 ARINET C:CH 1:1133 2:1674 3:1800 193.5.57/24 ARINET C:CH 1:1133 2:1674 3:1800 193.10/16 SUNET-CIDR10 C:SE 1:1800 2:1879 3:1133 4:1240 193.10.46/24 SE-SBGOV C:SE 1:1800 2:1879 3:1133 4:1240 193.48.25/24 FR-THOMNET C:FR 1:1800 2:1240 3:1133 4:1674 193.48.34/24 CSJF-ADMIN C:FR 1:1800 2:1240 3:1133 4:1674 193.48.35/24 CSJF-ENS C:FR 1:1800 2:1240 3:1133 4:1674 193.48.210/24 NCY-DROIT-R C:FR 1:1800 2:1240 3:1133 4:1674 193.48.211/24 NCY-DROIT-A C:FR 1:1800 2:1240 3:1133 4:1674 193.49.68/24 FR-BITI-03 C:FR 1:1800 2:1240 3:1133 4:1674 193.49.69/24 FR-BITI-04 C:FR 1:1800 2:1240 3:1133 4:1674 193.49.70/24 FR-BITI-05 C:FR 1:1800 2:1240 3:1133 4:1674 193.49.71/24 FR-BITI-06 C:FR 1:1800 2:1240 3:1133 4:1674 193.49.142/24 NCY-LETTRE-R C:FR 1:1800 2:1240 3:1133 4:1674 193.54.1/24 FR-NCY-LET-G C:FR 1:1800 2:1240 3:1133 4:1674 193.55.5/24 FR-KBU292 C:FR 1:1800 2:1240 3:1133 4:1674 193.55.156/24 FR-NORD-LI1 C:FR 1:1800 2:1240 3:1133 4:1674 193.55.157/24 FR-ALSA-ST1 C:FR 1:1800 2:1240 3:1133 4:1674 193.55.158/24 FR-POIT-P1 C:FR 1:1800 2:1240 3:1133 4:1674 193.55.159/24 FR-RHONEALP C:FR 1:1800 2:1240 3:1133 4:1674 193.64.202/24 PENET1 C:FI 1:701 2:1800 193.70.238/24 BIESSE-NET C:IT 1:701 2:1800 193.85/16 EUNET-CZ-193.85-AGG C:CZ 1:701 2:1800 193.92.80/20 UOFCYPRUSNET80-CIDR C:CY 1:1800 2:1133 3:1240 193.100.166/24 ATM-NET C:DE 1:701 2:1800 193.101.222/24 EUNET-PPP C:DE 1:701 2:1800 193.104.212/24 FR-EPSHOM-GB C:FR 1:701 2:1800 193.104.213/24 FR-EPSHOM-NB1 C:FR 1:701 2:1800 193.104.214/24 FR-EPSHOM-NB2 C:FR 1:701 2:1800 193.104.215/24 FR-EPSHOM-NB3 C:FR 1:701 2:1800 193.105.81/24 FR-UNIV-EVE2 C:FR 1:1800 2:1240 3:1133 4:1674 193.105.82/24 FR-UNIV-EVE3 C:FR 1:1800 2:1240 3:1133 4:1674 193.117.190/24 ALGORITHMICS C:GB 1:1800 2:1240 193.142.17/24 NLWC2 C:FI 1:701 2:1800 193.185.26/24 TEKES-PUB-NET C:FI 1:1800 2:1879 3:1133 4:1240 193.202.28/24 INFBRKM C:DE 1:1324 2:1800 3:1240 4:1133 193.209.180/24 KOKPOLY1 C:FI 1:701 2:1800 193.209.182/24 KOKPOLY3 C:FI 1:701 2:1800 194.45.11/24 TREFZ C:DE 1:1324 2:1800 3:1240 4:1133 194.55.6/24 ECRCTRAN2 C:DE 1:1800 2:1240 3:701 198.6.208/24 SONALYSTS-NET C:US 1:701 2:702 198.6.209/24 SONALYSTS-NET C:US 1:701 2:702 198.6.210/24 SONALYSTS-NET C:US 1:701 2:702 198.6.211/24 SONALYSTS-NET C:US 1:701 2:702 198.6.212/24 SONALYSTS-NET C:US 1:701 2:702 198.6.213/24 SONALYSTS-NET C:US 1:701 2:702 198.6.214/24 SONALYSTS-NET C:US 1:701 2:702 198.6.215/24 SONALYSTS-NET C:US 1:701 2:702 198.6.216/24 SONALYSTS-NET C:US 1:701 2:702 198.6.217/24 SONALYSTS-NET C:US 1:701 2:702 198.6.222/24 ODEDODEA C:US 1:701 2:702 198.6.223/24 ODEDODEA C:US 1:701 2:702 198.7.0/21 NETBLK-ACCESS-NET1 C:US 1:1800 2:1240 198.7.64/19 WA-DEPT-LIC-BLK C:US 1:685 2:73 3:101 198.22.152/24 BLK-GRCNET5 C:US 1:1800 2:1240 198.55.35/24 DEC-SHOWNET C:US 1:279 2:86 198.55.41/24 DEC-SHOWNET-C-55-41 C:US 1:279 2:86 198.60.8/24 NETBLK-WESTNET C:US 1:210 2:209 198.60.121/24 NETBLK-WESTNET C:US 1:210 2:209 198.60.122/24 NETBLK-WESTNET C:US 1:210 2:209 198.60.123/24 NETBLK-WESTNET C:US 1:210 2:209 198.60.124/24 NETBLK-WESTNET C:US 1:210 2:209 198.60.125/24 NETBLK-WESTNET C:US 1:210 2:209 198.60.126/24 NETBLK-WESTNET C:US 1:210 2:209 198.60.127/24 NETBLK-WESTNET C:US 1:210 2:209 198.60.128/24 NETBLK-WESTNET C:US 1:210 2:209 198.85.0/21 NCREN-AGG-109 C:US 1:1329 198.85.16/20 NCREN-AGG-017 C:US 1:1329 198.85.32/20 NCREN-AGG-110 C:US 1:1329 198.85.48/20 NCREN-AGG-018 C:US 1:1329 198.85.64/20 NCREN-AGG-111 C:US 1:1329 198.85.80/23 NCREN-AGG-112 C:US 1:1329 198.85.84/23 NCREN-AGG-113 C:US 1:1329 198.85.102/23 NCREN-AGG-114 C:US 1:1329 198.85.104/22 NCREN-AGG-115 C:US 1:1329 198.85.114/23 NCREN-AGG-019 C:US 1:1329 198.85.220/22 NCREN-AGG-020 C:US 1:1329 198.85.224/19 NCREN-AGG-021 C:US 1:1329 198.86/16 NCREN-AGG-022 C:US 1:1329 198.104/14 NWNET-BLK2 C:US 1:685 2:73 3:101 198.135.74/24 WCJC C:US 1:3354 2:114 198.152.92/24 NETBLK-ATT-CBLOCK C:US 1:1321 2:2386 198.152.93/24 NETBLK-ATT-CBLOCK C:US 1:1321 2:2386 198.152.94/24 NETBLK-ATT-CBLOCK C:US 1:1321 2:2386 198.152.95/24 NETBLK-ATT-CBLOCK C:US 1:1321 2:2386 198.152.96/24 NETBLK-ATT-CBLOCK C:US 1:1321 2:2386 198.179.128/24 NET-SAU-2 C:US 1:1800 2:1240 3:1323 198.187.178/23 NCREN-AGG-117 C:US 1:1329 198.187.180/22 NCREN-AGG-118 C:US 1:1329 198.187.184/22 NCREN-AGG-119 C:US 1:1329 198.236/14 NWNET-BLK3 C:US 1:685 2:73 3:101 198.247.6/24 PUEBLO C:US 1:93 198.247.7/24 LMN C:US 1:93 198.252.33/24 NETBLK-INTNET C:US 1:2386 2:1321 198.252.34/24 NETBLK-INTNET C:US 1:2386 2:1321 198.252.159/24 W8HDNET C:US 1:2149 2:174 198.252.200/24 ATLANTIC-C C:US 1:2149 2:174 199.2.31/24 BTW-DOM C:US 1:1240 2:1800 199.10.231/24 SEACOSD-NET C:US 1:568 2:19 199.26.150/24 GISD-NET C:US 1:2149 2:174 199.72.12/24 NETBLK-INTERPATH C:US 1:1800 2:1240 199.73.37/24 MCCABE-NET C:US 1:1800 2:1240 199.74.244/24 GRCNET3 C:US 1:1800 2:1240 199.79.216/24 GRCNET4 C:US 1:1800 2:1240 199.86.65/24 MRNET-BLOCK3 C:US 1:1225 2:267 3:266 4:555 199.88.171/24 XCALIBER C:US 1:2551 199.89.132/24 GRC C:US 1:1800 2:1240 199.89.133/24 NETBLK-GRCNET6 C:US 1:1800 2:1240 199.89.158/24 GRCI-VIENNA-C-89-158 C:US 1:1800 2:1240 199.89.159/24 GRCI-VIENNA-C-89-159 C:US 1:1800 2:1240 199.89.160/24 GRCI-VIENNA-C-89-160 C:US 1:1800 2:1240 199.97.187/24 NETBLK-PSINET-C5 C:US 1:2149 2:174 199.98.125/24 PSINET-C5 C:US 1:2149 2:174 199.98.182/24 PULSE-NET C:US 1:2149 2:174 199.98.183/24 PSINET-C5 C:US 1:2149 2:174 199.98.184/24 PSINET-C5 C:US 1:2149 2:174 199.98.185/24 PSINET-C5 C:US 1:2149 2:174 199.98.186/24 PSINET-C5 C:US 1:2149 2:174 199.98.187/24 NETBLK-PSINET-C5 C:US 1:2149 2:174 199.120.185/24 INFOCOM C:US 1:1332 199.164.227/24 DEATECH.COM C:US 1:1240 2:1800 199.170.24/24 CADMUS-NET C:US 1:701 2:702 199.170.25/24 CADMUS-NET C:US 1:701 2:702 199.170.26/24 CADMUS-NET C:US 1:701 2:702 199.170.27/24 CADMUS-NET C:US 1:701 2:702 199.170.28/24 CADMUS-NET C:US 1:701 2:702 199.170.29/24 CADMUS-NET C:US 1:701 2:702 199.170.30/24 CADMUS-NET C:US 1:701 2:702 199.170.31/24 CADMUS-NET C:US 1:701 2:702 199.170.78/24 FCW-NET C:US 1:701 2:702 199.170.79/24 FCW-NET C:US 1:701 2:702 199.181.144/24 EDI-NET C:US 1:1225 2:267 3:266 4:555 199.184.171/24 W8HDNET-C-184-171 C:US 1:2149 2:174 199.184.172/24 W8HDNET-C-184-172 C:US 1:2149 2:174 199.184.186/24 ARISCORP-NET C:US 1:1982 199.184.216/24 EPAN.COM C:US 1:1240 2:1800 199.190.131/24 CSCNS-NET4 C:US 1:1332 199.190.133/24 CSCNS-NET3 C:US 1:1332 199.190.172/24 RELAXNET C:US 1:1332 199.199.2/24 POWERCERV1 C:US 1:1225 2:267 3:266 4:555 199.199.3/24 MRNET-C-BLOCK4 C:US 1:1225 2:267 3:266 4:555 199.199.4/24 MCCCARE1 C:US 1:1225 2:267 3:266 199.199.5/24 MCCCARE2 C:US 1:1225 2:267 3:266 199.199.6/24 MCCCARE3 C:US 1:1225 2:267 3:266 199.199.7/24 MCCCARE4 C:US 1:1225 2:267 3:266 199.245.16/24 CLARKNET-CBLK2 C:US 1:1800 2:1240 200.7.9/24 UFPR-ANPR9 C:BR 1:293 2:291 200.10.141/24 UNISC C:BR 1:293 2:291 202.17.236/22 NETBLK-MOCHIDANET C:JP 1:701 2:702 202.23.80/24 BRINET C:JP 1:1240 2:1800 202.23.81/24 BRINET C:JP 1:1240 2:1800 202.23.82/24 BRINET C:JP 1:1240 2:1800 202.23.83/24 BRINET C:JP 1:1240 2:1800 202.32/16 NETBLK-JP-SP-BLOCK C:JP 1:701 2:702 202.40.141/24 NETBLK-TCHK-C-40-141 C:HK 1:1321 202.40.142/24 NETBLK-TCHK-C-40-142 C:HK 1:1321 202.40.147/24 DEAL C:HK 1:1321 202.64/16 HKSUPER-BLK C:HK 1:2149 2:174 Deletions: --193.10.16/24 SE-AS-LAN C:SE 1:1957 --193.10.24/24 SE-AS-LAN C:SE 1:1957 --193.10.127/24 SE-AKADEM-MTA C:SE 1:1957 --199.100.0/24 PSINET-C5 C:US 1:2149 2:174 --199.100.1/24 PSINET-C6 C:US 1:2149 2:174 --199.100.2/24 PSINET-C7 C:US 1:2149 2:174 --199.100.3/24 PSINET-C8 C:US 1:2149 2:174 --199.100.4/24 PSINET-C9 C:US 1:2149 2:174 --199.100.5/24 PSINET-C10 C:US 1:2149 2:174 --202.17.236/24 NETBLK-MOCHIDANET C:JP 1:1957 --202.32.0/24 JP-SP-BLOCK C:JP 1:1957 --202.32.2/24 JP-SP-BLOCK C:JP 1:1957 --202.32.4/24 JP-SP-BLOCK C:JP 1:1957 --202.32.5/24 JP-SP-BLOCK C:JP 1:1957 --202.32.6/24 JP-SP-BLOCK C:JP 1:1957 --202.32.7/24 JP-SP-BLOCK C:JP 1:1957 --202.32.8/24 JP-SP-BLOCK C:JP 1:1957 --202.32.9/24 JP-SP-BLOCK C:JP 1:1957 --202.32.10/24 JP-SP-BLOCK C:JP 1:1957 --202.32.12/24 JP-SP-BLOCK C:JP 1:1957 --202.32.14/24 JP-SP-BLOCK C:JP 1:1957 --202.32.16/24 NETBLK-JP-SP-BLOCK C:JP 1:1957 Expanded listing, sorted by country, then by organization: ========================================================== Brazil ------ Universidade Federal do Parana', Caixa Postal 19081 - Centro Politecnico - Jardim das Americas, Curitiba, PR, 81531-990, BRAZIL 1:293 Energy Science Network (FIX-East) 2:291 Energy Science Network (FIX-West) ---------- 200.7.9/24 UFPR-ANPR9 (BR) Universidade de Santa Cruz do Sul, Av. Independencia, 2293, Santa Cruz do Sul, RS, 96815-900, BRAZIL 1:293 Energy Science Network (FIX-East) 2:291 Energy Science Network (FIX-West) ------------- 200.10.141/24 UNISC (BR) Cyprus ------ University of Cyprus, 75 Kallipoleos str, Nicosia, CYPRUS 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific ------------ 193.92.80/20 UOFCYPRUSNET80-CIDR (CY) Czech Republic -------------- COnet, Technicka 5, 166 28 Prague 6, Czechia, CZECH REPUBLIC 1:701 Alternet 2:1800 ICM-Atlantic --------- 193.85/16 EUNET-CZ-193.85-AGG (CZ) Denmark ------- UNI-C - Danish Computing Centre for Research and Education, DTH, Building 305, DK-2800 Lyngby, DENMARK 1:1800 ICM-Atlantic 2:1879 EUROPE-RS 3:1133 CERN/DANTE 4:1240 ICM-Pacific ---------- 130.226/15 DENET-CIDR (DK) Finland ------- EUnet Finland, Punavuorenkatu 1, FI-00120 HELSINKI, FINLAND 1:701 Alternet 2:1800 ICM-Atlantic ------------- 193.64.202/24 PENET1 (FI) Kokkolan kaupunki, 67100 KOKKOLA, FINLAND, Finland, FINLAND 1:701 Alternet 2:1800 ICM-Atlantic -------------- 193.209.180/24 KOKPOLY1 (FI) 193.209.182/24 KOKPOLY3 (FI) Nordic LAN & WAN Communications Oy, Sinikalliontie 14 B, FI-02630 Espoo, Finland, Finland, FINLAND 1:701 Alternet 2:1800 ICM-Atlantic ------------- 193.142.17/24 NLWC2 (FI) Teknologian kehittamiskeskus TEKES, Malminkatu 34, FI-00100 Helsinki, FINLAND 1:1800 ICM-Atlantic 2:1879 EUROPE-RS 3:1133 CERN/DANTE 4:1240 ICM-Pacific ------------- 193.185.26/24 TEKES-PUB-NET (FI) France ------ Centre Scientifique Joseph Fourier, 38 rue Barthelemy de Laffemas, 26000 Valence, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ------------ 193.48.34/24 CSJF-ADMIN (FR) 193.48.35/24 CSJF-ENS (FR) Etablissement Principal du Service Hydro-Oceanique de la Marine (EPSHOM) - CMO, 13 rue du Chatellier, BP 426, 29275 Brest CEDEX, FRANCE 1:701 Alternet 2:1800 ICM-Atlantic -------------- 193.104.212/24 FR-EPSHOM-GB (FR) 193.104.213/24 FR-EPSHOM-NB1 (FR) 193.104.214/24 FR-EPSHOM-NB2 (FR) 193.104.215/24 FR-EPSHOM-NB3 (FR) Faculte de Droit - Universite de NANCY 2, 13, place Carnot - Case officielle numero 26, 54035 Nancy CEDEX, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ------------- 193.48.210/24 NCY-DROIT-R (FR) 193.48.211/24 NCY-DROIT-A (FR) France Telecom, 9 Rue de Nanteuil, 75015 Paris, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ------------- 193.55.156/24 FR-NORD-LI1 (FR) 193.55.157/24 FR-ALSA-ST1 (FR) 193.55.158/24 FR-POIT-P1 (FR) 193.55.159/24 FR-RHONEALP (FR) INSERM - U292, Hopital de Bicetre, 78 rue du General Leclerc, 94275 Le Kremlin Bicetre CEDEX, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ----------- 193.55.5/24 FR-KBU292 (FR) MRES - Ministere de l'Enseignement Superieur et de la Recherche, 1 rue Descartes BITI, 75005 Paris, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ------------ 193.49.68/24 FR-BITI-03 (FR) 193.49.69/24 FR-BITI-04 (FR) 193.49.70/24 FR-BITI-05 (FR) 193.49.71/24 FR-BITI-06 (FR) Thomson Facilities Management, 3/5 Avenue Morane Saulnier, 78140 Velizy Villacoublay, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ------------ 193.48.25/24 FR-THOMNET (FR) Universite d'Evry Val d'Essonne, Boulevard des Coquibus, 91025 Evry CEDEX, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ------------- 193.105.81/24 FR-UNIV-EVE2 (FR) 193.105.82/24 FR-UNIV-EVE3 (FR) Universite de NANCY 2, 25 rue Baron Louis BP 454, 54001 Nancy CEDEX, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ------------- 193.49.142/24 NCY-LETTRE-R (FR) Universite de NANCY 2, 25, rue Baron Louis BP 454, 54001 Nancy CEDEX, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ----------- 193.54.1/24 FR-NCY-LET-G (FR) Germany ------- AEG Electrocom GmbH, AEC/K43, Buecklestrasse 1-5, D-78467 Konstanz, GERMANY 1:701 Alternet 2:1800 ICM-Atlantic -------------- 193.100.166/24 ATM-NET (DE) ANT Nachrichtentechnik GmbH, Gerberstr. 33, D-71522 Backnang, GERMANY 1:1324 ANS New York City - DNSS 35 2:1800 ICM-Atlantic 3:1240 ICM-Pacific 4:1133 CERN/DANTE ------------ 194.45.11/24 TREFZ (DE) ECRC, Arabellastr. 17, 81927 Munich, Bavaria, GERMANY 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:701 Alternet ----------- 194.55.6/24 ECRCTRAN2 (DE) EUnet Deutschland GmbH, Emil-Figge-Str. 80, D-44227 Dortmund, GERMANY 1:701 Alternet 2:1800 ICM-Atlantic -------------- 193.101.222/24 EUNET-PPP (DE) Infratest Burke AG, Landsberger Strasse 338, D-80687 Muenchen, GERMANY 1:1324 ANS New York City - DNSS 35 2:1800 ICM-Atlantic 3:1240 ICM-Pacific 4:1133 CERN/DANTE ------------- 193.202.28/24 INFBRKM (DE) Hong Kong --------- Duke Energy Asia Ltd., 11th Floor, Central Building, 1 Pedder Street, Central, HONG KONG 1:1321 ANS San Francisco - DNSS 11 ------------- 202.40.147/24 DEAL (HK) Hong Kong Supernet, Hong Kong University, Clear Water Bay, Kowloon, HONG KONG 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI --------- 202.64/16 HKSUPER-BLK (HK) Team Concepts, 5/F, Yan Hing Centre, 9-13 Wong Chuk Yeung Street, Fotan, HONG KONG 1:1321 ANS San Francisco - DNSS 11 ------------- 202.40.141/24 NETBLK-TCHK-C-40-141 (HK) 202.40.142/24 NETBLK-TCHK-C-40-142 (HK) Italy ----- Biesse S.p.A., Via Toscana, 75, I-61100 Pesaro, ITALY 1:701 Alternet 2:1800 ICM-Atlantic ------------- 193.70.238/24 BIESSE-NET (IT) Japan ----- Building Research Institute, Ministry of Construction, 1 Tatehara, Tsukuba-shi, Ibaraki 305, JAPAN 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ------------ 202.23.80/24 BRINET (JP) 202.23.81/24 BRINET (JP) 202.23.82/24 BRINET (JP) 202.23.83/24 BRINET (JP) Internet Initiative Japan, Inc., 2-11-2 Nagatacho, Chiyoda-Ku, Tokyo, 100, JAPAN 1:701 Alternet 2:702 Alternet -------------- 192.244.176/20 IIJNET (JP) Internet Initiative Japan, Inc., 2-11-2 Nagatacho, Chiyoda-ku, Tokyo, 100, JAPAN 1:701 Alternet 2:702 Alternet --------- 202.32/16 NETBLK-JP-SP-BLOCK (JP) Mochida Pharmaceutical Co., Ltd., Yotsuya 1-7, Shinjuku-ku, Tokyo, 160, JAPAN 1:701 Alternet 2:702 Alternet ------------- 202.17.236/22 NETBLK-MOCHIDANET (JP) NIFTY Corporation, OMORI BELLPORT A, 26-1, MINAMI-OI 6CHOME, SHINAGAWA-KU, TOKYO, 140, JAPAN 1:701 Alternet 2:702 Alternet ------------ 192.47.24/24 NIFTY-SERVE (JP) Sweden ------ SUNET, Royal Institute of Technology, S-100 44 Stockholm, SWEDEN 1:1800 ICM-Atlantic 2:1879 EUROPE-RS 3:1133 CERN/DANTE 4:1240 ICM-Pacific --------- 193.10/16 SUNET-CIDR10 (SE) Statsradsberedningen, S-103 33 Stockholm, SWEDEN 1:1800 ICM-Atlantic 2:1879 EUROPE-RS 3:1133 CERN/DANTE 4:1240 ICM-Pacific ------------ 193.10.46/24 SE-SBGOV (SE) Switzerland ----------- AO-Forschungsinstitut, Clavadelerstrasse, CH-7270 Davos-Platz, SWITZERLAND 1:1133 CERN/DANTE 2:1674 CERN/DANTE 3:1800 ICM-Atlantic ----------- 193.5.56/23 ARINET (CH) 193.5.57/24 ARINET (CH) Swiss Federal Post and Telephone (Swiss PTT), Bern, SWITZERLAND 1:1133 CERN/DANTE 2:1674 CERN/DANTE 3:1800 ICM-Atlantic ---------- 138.187/16 INFNET-PTT1 (CH) United Kingdom -------------- Algorithmics Ltd, 3 Drayton Park, London, N5 1NU, UNITED KINGDOM 1:1800 ICM-Atlantic 2:1240 ICM-Pacific -------------- 193.117.190/24 ALGORITHMICS (GB) United States ------------- ATT, 2000 N. NAPERVILLE RD PO BOX 3033, NAPERVILLE, IL 60566, USA 1:1321 ANS San Francisco - DNSS 11 2:2386 INS-AS ------------- 198.152.92/24 NETBLK-ATT-CBLOCK (US) 198.152.93/24 NETBLK-ATT-CBLOCK (US) 198.152.94/24 NETBLK-ATT-CBLOCK (US) 198.152.95/24 NETBLK-ATT-CBLOCK (US) 198.152.96/24 NETBLK-ATT-CBLOCK (US) Ackerman McQueen, 1601 NW Expressway, Oklahoma City, OK 73118, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.186/24 PSINET-C5 (US) Advanced Research Technologies, 1062 Lancaster Avenue, Suite 18C, Rosemont, PA 19010, USA 1:204 PSCNET Regional Network 2:1206 PSCNET Regional Network -------------- 192.204.252/24 ART-NET (US) Aris Corp., 6840 Southcenter Blvd., Seattle, WA 98188-2555, USA 1:1982 Northwest Nexus -------------- 199.184.186/24 ARISCORP-NET (US) Atlantic Computing Technology Corp., 84 Round Hill Rd., Wethersfield, CT 06109, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI -------------- 198.252.200/24 ATLANTIC-C (US) BTG, Inc., 1945 Old Gallows Road, Suite 700, Vienna, VA 22182, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.125/24 PSINET-C5 (US) Books That Work, 285 Hamilton Ave., Ste 260, Palo Alto, CA 94301, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ----------- 199.2.31/24 BTW-DOM (US) CICNet, Inc., 2901 Hubbard Rd, Ann Arbor, MI 48105, USA 1:1225 CICNET at Argonne Labs 2:267 CICNET at UIUC 3:266 CICNET at MERIT ---------- 192.217/16 NETBLK-CICNET-BLOCK (US) CONCERT / NC-REN Network, P.O. Box 12889, Research Triangle Park, NC 27709, USA 1:1329 ANS Greensboro - DNSS 75 -------- 152.2/15 NCREN-AGG-002 (US) 152.4/14 NCREN-AGG-003 (US) 152.8/13 NCREN-AGG-004 (US) 152.16/12 NCREN-AGG-005 (US) 152.32/12 NCREN-AGG-006 (US) 152.48/14 NCREN-AGG-007 (US) 192.35.236/23 NCREN-AGG-116 (US) 192.58.204/23 NCREN-AGG-023 (US) 192.101.22/23 NCREN-AGG-001 (US) 192.154.36/22 NCREN-AGG-008 (US) 192.154.40/22 NCREN-AGG-009 (US) 192.154.46/23 NCREN-AGG-010 (US) 192.154.48/23 NCREN-AGG-101 (US) 192.154.50/23 NCREN-AGG-011 (US) 192.154.52/23 NCREN-AGG-012 (US) 192.154.56/23 NCREN-AGG-103 (US) 192.154.60/22 NCREN-AGG-013 (US) 192.154.64/23 NCREN-AGG-014 (US) 192.154.68/22 NCREN-AGG-104 (US) 192.154.76/23 NCREN-AGG-105 (US) 192.154.78/23 NCREN-AGG-015 (US) 192.154.82/23 NCREN-AGG-106 (US) 192.154.84/22 NCREN-AGG-107 (US) 192.154.88/23 NCREN-AGG-108 (US) 192.154.92/22 NCREN-AGG-016 (US) 198.85.0/21 NCREN-AGG-109 (US) 198.85.16/20 NCREN-AGG-017 (US) 198.85.32/20 NCREN-AGG-110 (US) 198.85.48/20 NCREN-AGG-018 (US) 198.85.64/20 NCREN-AGG-111 (US) 198.85.80/23 NCREN-AGG-112 (US) 198.85.84/23 NCREN-AGG-113 (US) 198.85.102/23 NCREN-AGG-114 (US) 198.85.104/22 NCREN-AGG-115 (US) 198.85.114/23 NCREN-AGG-019 (US) 198.85.220/22 NCREN-AGG-020 (US) 198.85.224/19 NCREN-AGG-021 (US) 198.86/16 NCREN-AGG-022 (US) 198.187.178/23 NCREN-AGG-117 (US) 198.187.180/22 NCREN-AGG-118 (US) 198.187.184/22 NCREN-AGG-119 (US) Cadmus Journal Services, 1314 Guilford Avenu, Baltimore, MD 21202, USA 1:701 Alternet 2:702 Alternet ------------- 199.170.24/24 CADMUS-NET (US) 199.170.25/24 CADMUS-NET (US) 199.170.26/24 CADMUS-NET (US) 199.170.27/24 CADMUS-NET (US) 199.170.28/24 CADMUS-NET (US) 199.170.29/24 CADMUS-NET (US) 199.170.30/24 CADMUS-NET (US) 199.170.31/24 CADMUS-NET (US) Clark Internet Services, Inc., 10600 Route 108, Ellicott City, MD 21042, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ------------- 199.245.16/24 CLARKNET-CBLK2 (US) Commerical Software INC, 607 Lee St., Seattle, WA 98109, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic -------------- 199.184.216/24 EPAN.COM (US) Community News Service, 1155 Kelly Johnson Blvd., Suite 400, Colorado Springs, CO 80920, USA 1:1332 ANS Denver - DNSS 99 -------------- 199.190.131/24 CSCNS-NET4 (US) 199.190.133/24 CSCNS-NET3 (US) Constellation Technology Corp., 9887 Gandy Blvd #100, St. Petersburg, FL 33702, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.183/24 PSINET-C5 (US) DOD DEPENDENTS SCHOOLS, 200 N. GLEBE RD. #702, Arlington, VA 22203, USA 1:701 Alternet 2:702 Alternet -------------- 192.156.209/24 ODS-HOFF-NET (US) DOD EDUCATION ACTIVITY, MIS DIVISION - 7TH FLOOR, 4040 N FAIRFAX DR, Arlington, VA 22203, USA 1:701 Alternet 2:702 Alternet ------------ 198.6.222/24 ODEDODEA (US) 198.6.223/24 ODEDODEA (US) Deatech Research Inc, 12322 202nd PL SE, Issaquah, WA 98027, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic -------------- 199.164.227/24 DEATECH.COM (US) EG&G Automotive Research, 5404 Bandera Rd, San Antonio, TX 78238, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.97.187/24 NETBLK-PSINET-C5 (US) Exchange Data Incorporated, 60 South 6th Street, Suite 2300, Minneapolis, MN 55402, USA 1:1225 CICNET at Argonne Labs 2:267 CICNET at UIUC 3:266 CICNET at MERIT 4:555 Minnesota Supercomputer Center Network (MSCNet) -------------- 199.181.144/24 EDI-NET (US) Fritz Companies, Inc., 455 Forbes Blvd., San Francisco, CA 94080, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ---------- 156.134/16 FRITZ (US) General Research Corporation, 5383 Hollister Ave, Santa Barbara, CA 93111, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ------------- 198.22.152/24 BLK-GRCNET5 (US) 199.79.216/24 GRCNET4 (US) 199.89.132/24 GRC (US) 199.89.133/24 NETBLK-GRCNET6 (US) General Research Corporation, International, 5383 Hollister Ave, Santa Barbara, CA 93111, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ------------- 199.74.244/24 GRCNET3 (US) Genesee Intermediate School District, 2413 West Maple Avenue, Flint, MI 48507, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.26.150/24 GISD-NET (US) Golden Gate University, P.O. Box 85608, San Diego, CA 92186-9784, USA 1:1740 CERFnet ------------- 192.251.73/24 GOLDGATE (US) 192.251.74/24 GOLDGATE3 (US) Happy Harry's, Inc., 315 Ruthar Drive, Newark, DE 19711, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.185/24 PSINET-C5 (US) IDC Government/Federal Computer Week, 3110 Fairview Park Dr. Suite 1100, Falls Church, VA 22042, USA 1:701 Alternet 2:702 Alternet ------------- 199.170.78/24 FCW-NET (US) 199.170.79/24 FCW-NET (US) InfoCom, Box 54, 101 West Main, Boston, IN 47324, USA 1:1332 ANS Denver - DNSS 99 -------------- 199.120.185/24 INFOCOM (US) Intelligence Network, Inc., 1224 Rogers Street, Clearwater, FL 34616, USA 1:2386 INS-AS 2:1321 ANS San Francisco - DNSS 11 ---------- 168.151/16 INTNET2-B1 (US) 198.252.33/24 NETBLK-INTNET (US) 198.252.34/24 NETBLK-INTNET (US) Interpath, P.O. Box 12800, Raleigh, NC 27605, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ------------ 199.72.12/24 NETBLK-INTERPATH (US) James River Group Inc., 125 N First St, Minneapolis, MN 55401, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic -------------- 192.146.151/24 JRIVER (US) LSU Medical Center, 433 Bolivar Street, New Olreans, LA 70112, USA 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) ------------ 198.55.35/24 DEC-SHOWNET (US) 198.55.41/24 DEC-SHOWNET-C-55-41 (US) Library Management Network, Inc., P.O. Box 443, Huntsville, AL 35804, USA 1:93 MIDnet ------------ 198.247.7/24 LMN (US) MCC Behavioral Care, 11095 Viking Dr, Ste 350, Eden Prairie, MN 55344, USA 1:1225 CICNET at Argonne Labs 2:267 CICNET at UIUC 3:266 CICNET at MERIT ------------ 199.199.4/24 MCCCARE1 (US) 199.199.5/24 MCCCARE2 (US) 199.199.6/24 MCCCARE3 (US) 199.199.7/24 MCCCARE4 (US) McCabe & Associates, 5501 Twin Knolls Road Suite 101, Columbia, MD 21045, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ------------ 199.73.37/24 MCCABE-NET (US) Minnesota Regional Network, 511 11th Ave. S., Minneapolis, MN 55415, USA 1:1225 CICNET at Argonne Labs 2:267 CICNET at UIUC 3:266 CICNET at MERIT 4:555 Minnesota Supercomputer Center Network (MSCNet) ------------ 199.86.65/24 MRNET-BLOCK3 (US) 199.199.3/24 MRNET-C-BLOCK4 (US) Montgomery County Intermediate Unit, 1605B W. Main St., Norristown, PA 19403, USA 1:204 PSCNET Regional Network 2:1206 PSCNET Regional Network -------------- 192.204.190/24 MCIU (US) NAVSEA CAD/CAM OPERATIONS SUPPORT DETACHMENT, P.O. BOX 2055, VALLEJO, CA 94592, USA 1:568 Milnet (FIX-West) 2:19 Milnet (FIX-East) ------------- 199.10.231/24 SEACOSD-NET (US) Networking Technologies Department, General Research Corporation, 1900 Gallows Road, Vienna, VA 22182, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ------------- 199.89.158/24 GRCI-VIENNA-C-89-158 (US) 199.89.159/24 GRCI-VIENNA-C-89-159 (US) 199.89.160/24 GRCI-VIENNA-C-89-160 (US) NorthWestNet, 15400 SE 30th Place, Suit 202, Bellevue, WA 98007, USA 1:685 NorthWestNet Regional Network 2:73 NorthWestNet Regional Network 3:101 NorthWestNet Regional Network ---------- 198.104/14 NWNET-BLK2 (US) NorthWestNet, 15400 SE 30th Place, Suite 202, Bellevue, WA 98007, USA 1:685 NorthWestNet Regional Network 2:73 NorthWestNet Regional Network 3:101 NorthWestNet Regional Network ---------- 198.236/14 NWNET-BLK3 (US) Powell Tate, 700 Thirteeth St, NW, Washington, DC 20005, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.187/24 NETBLK-PSINET-C5 (US) PowerCerv Corporation, Two Appletree Square, Ste 240, Bloomington, MN 55425, USA 1:1225 CICNET at Argonne Labs 2:267 CICNET at UIUC 3:266 CICNET at MERIT 4:555 Minnesota Supercomputer Center Network (MSCNet) ------------ 199.199.2/24 POWERCERV1 (US) Prototype Express, Inc., 2301 Hammond Drive, Schaumburg, IL 60173, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.184/24 PSINET-C5 (US) Public Access Networks, Corporation, c/o Alexis Rosen, 110 Riverside Drive, New York, NY 10024, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ---------- 198.7.0/21 NETBLK-ACCESS-NET1 (US) Pueblo Library District, 100 East Abrendo Ave., Pueblo, CO 81004, USA 1:93 MIDnet ------------ 198.247.6/24 PUEBLO (US) Pulse Communications, Inc., 2900 Towerview Rd., Herndon, VA 22071, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 199.98.182/24 PULSE-NET (US) R. W. Beck & Associates, 2101 Fourth Avenue, Suite 600, Seattle, WA 98121-2375, USA 1:2551 NETCOM ------------- 192.247.16/20 NETBLK-RWBECK (US) Relax PC, 34 Mountain St., Bristol, VT 05443-1307, USA 1:1332 ANS Denver - DNSS 99 -------------- 199.190.172/24 RELAXNET (US) Seattle University, Broadway & Madison, Seattle, WA 98122, USA 1:685 NorthWestNet Regional Network 2:73 NorthWestNet Regional Network 3:101 NorthWestNet Regional Network ------------- 192.222.32/19 SEATTLEU-BLK (US) Sonalysts, Inc., 215 Parkway North, Waterford, CT 06385, USA 1:701 Alternet 2:702 Alternet ------------ 198.6.208/24 SONALYSTS-NET (US) 198.6.209/24 SONALYSTS-NET (US) 198.6.210/24 SONALYSTS-NET (US) 198.6.211/24 SONALYSTS-NET (US) 198.6.212/24 SONALYSTS-NET (US) 198.6.213/24 SONALYSTS-NET (US) 198.6.214/24 SONALYSTS-NET (US) 198.6.215/24 SONALYSTS-NET (US) 198.6.216/24 SONALYSTS-NET (US) 198.6.217/24 SONALYSTS-NET (US) St. Ambrose University, 518 W. Locust St., Davenport, IA 52803, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1323 ANS Chicago - DNSS 27 -------------- 198.179.128/24 NET-SAU-2 (US) State of Washington, DOL PO Box 48091, Olympia, WA 98504-8091, USA 1:685 NorthWestNet Regional Network 2:73 NorthWestNet Regional Network 3:101 NorthWestNet Regional Network ----------- 198.7.64/19 WA-DEPT-LIC-BLK (US) The W8HD Group, 1920 Elsie Drive, West Bloomfield, MI 48324, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI -------------- 198.252.159/24 W8HDNET (US) 199.184.171/24 W8HDNET-C-184-171 (US) 199.184.172/24 W8HDNET-C-184-172 (US) Westnet, 3645 Marine Street, U. of Colorado, Boulder, AZ 86301, USA 1:210 Westnet Regional Network (Utah Attachment) - ENSS 142 2:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 ------------- 198.60.122/24 NETBLK-WESTNET (US) Westnet, 3645 Marine Street, U. of Colorado, Boulder, CO 80309-0455, USA 1:210 Westnet Regional Network (Utah Attachment) - ENSS 142 2:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 ----------- 198.60.8/24 NETBLK-WESTNET (US) 198.60.121/24 NETBLK-WESTNET (US) 198.60.123/24 NETBLK-WESTNET (US) 198.60.124/24 NETBLK-WESTNET (US) 198.60.125/24 NETBLK-WESTNET (US) 198.60.126/24 NETBLK-WESTNET (US) 198.60.127/24 NETBLK-WESTNET (US) 198.60.128/24 NETBLK-WESTNET (US) Wharton County Junior College, 911 Boling Highway, Wharton, TX 77488, USA 1:3354 THENET-AS-1 2:114 SESQUINET Regional Network ------------- 198.135.74/24 WCJC (US) XCaliber Trading Systems, 440 S. LaSalle Suite 3904, Chicago, IL 60614, USA 1:2551 NETCOM ------------- 199.88.171/24 XCALIBER (US) AS690 CIDR Squeezings Report: 2660 Nets, 40 ASs, 378 Aggregates ---------------------------------------------------------------- 2660 (55%) of the ever-announced more-specific routes within aggregates have been withdrawn. 649 of those were withdrawn within the last week. 1232 the week before that. 329 the week before that. 40 ASs have registered aggregates in the PRDB. 33 of those are announcing aggregates. 21 have withdrawn at least one more specific route. 378 Aggregates are configured. 351 of these were Top-Level Aggregates (not nested in another aggregate). 187 of these are being announced to AS690. 166 of those have at least one subnet configured (the other 21 may be saving. the Internet future subnet announcements). 130 have stopped announcing at least one configured more specific route. 123 have stopped announcing half of their configured more specific routes. 105 have stopped announcing most (80%) of their more specific routes. See 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.t3p Information is also avaiable through the PRDB whois server. Type "whois -h prdb.merit.edu help" for details. -------------------------------------------------------------------------- REPORT CHANGES: (Updated March 24, 1994) Metric:AS(NSS) - Historically, peer networks with multiple connections to AS 690 could only select which of those connections their networks would take by creating "Fake" AS numbers, and using those in the PRDB Metric:AS announcement lists. Some time in the next few weeks we will begin supporting an expanded syntax, where the AS may be followed by an optional NSS peer number in parentheses. Eventually, this syntax will be used to replace most or all of the current Fake ASs. This change will affect *all* places that the announcement lists are reported: all whois queries, all network reports, this "NWG" report, and the Auto-NACR. If you have code which parses these announcement lists, please be aware that that code may need modifications soon. CIDR Reports: There is a new "whois" option to list aggregates in the PRDB: whois -h prdb.merit.edu listaggs will produce a listing of the currently registered aggregates. There is also a new report on "nestings" of PRDB-registered aggregates with their more specific routes: nets.non-classful. Anyone considering configuring an aggregate into the PRDB (and you all should be!) is encouraged to pre-check that aggregate by typing the command: whois -h prdb.merit.edu 'aggchk ' (where "" is the aggregate description). This command will list all of the other entries in the PRDB that are more specific routes of , as well as any aggregates all ready configured that contain . The output includes the AUP and announcement lists of each of the nets printed, with discrepancies flagged. This is the same program that we use for sanity-checking the NACRs that you submit. The archived discussion list "db-disc@merit.edu" exists for discussion of PRDB issues. Send a message to "db-disc-request@merit.edu" to subscribe. --Dale Johnson (dsj@merit.edu) -------------------------------------------------------------------------- Please send all requests for configuration changes to nsfnet-admin@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. ******************************* --Steven J. Richardson Merit/NSFNET sjr@merit.edu --Steve Widmayer Merit/NSFNET skw@merit.edu --Enke Chen Merit/NSFNET enke@merit.edu - - - - - - - - - - - - - - - - - From list-admin Fri Apr 29 16:04:27 1994 Received: from localhost (jyy@localhost) by merit.edu (8.6.8.1/merit-1.0) with SMTP id QAA16008; Fri, 29 Apr 1994 16:04:26 -0400 Message-Id: <199404292004.QAA16008@merit.edu> To: bgpd@merit.edu, regional-techs@merit.edu cc: jyy@merit.edu Subject: this week's cidr progress Date: Fri, 29 Apr 1994 16:04:26 -0400 From: Jessica Yu This past week's CIDR progress from AS690's point view. Route table growth: -248 routes (yes, decreased by 248 routes) Route withdrawn: 704 routes The following ASs and/or ASs behind them have withdrawn more specific routes during the period: AS1324 ANS-NYC-CONNECTION 194 AS701 Alternet 140 AS200 Barrnet 96 AS204 PSCNet 86 AS237 MichNet 72 AS685 NorthWestNet 71 AS1957 ANSCIX 30 AS1800 ICM-Atlantic 6 AS560 NearNet 5 AS1133 CERN/DANTE 2 AS1740 CERFNet 2 New challenges: There are 1001 routes co-existing with its aggregate in the routing table currently, that is they can be withdrawn as we speak. ASs who advertise these nets PLEASE withdrawn them. --jessica - - - - - - - - - - - - - - - - - From list-admin Fri Apr 29 23:00:58 1994 Received: from Root.COM ([198.145.90.241]) by merit.edu (8.6.8.1/merit-1.0) with ESMTP id XAA10560 for ; Fri, 29 Apr 1994 23:00:53 -0400 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.2]) by Root.COM (8.6.8/8.6.5) with ESMTP id UAA00380; Fri, 29 Apr 1994 20:02:29 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.8/8.6.5) with SMTP id UAA00632; Fri, 29 Apr 1994 20:00:25 -0700 Message-Id: <199404300300.UAA00632@corbin.Root.COM> X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol To: Curtis Villamizar cc: regional-techs@merit.edu Subject: Re: More on PC Routers from BGPD In-reply-to: Your message of "Thu, 28 Apr 94 10:17:44 CDT." <199404281417.AA33001@foo.ans.net> From: David Greenman Reply-To: davidg@Root.COM Date: Fri, 29 Apr 1994 20:00:11 -0700 Sender: root@corbin.Root.COM >My comment was incorrect on T1/E1. We were trying to do full DES >encryption of a T1 stream and couldn't saturate the link using a >modified BSDI kernel and a 486/66. Full T1/E1 is possible using >existing cards if you don't try to encrypt. Additionally, some early versions of BSDI had problems with doing the processing of the protocol queues via netisr in a timely manner and this limited the maximum packet rate. I haven't tested more recent versions of BSDI for this problem. >Wrt ethernet - I was under the impression that the fastest EISA card >was the 3C579 and the fastest ISA the TN-1500. I've never benchmarked a 3c579 (or seen one for that matter), but if it's anything like other recent boards from 3COM...I would be surprised if it actually worked very well. perhaps the important point that I should make here is that bus master DMA does not necessarily mean fast or low overhead. > I'd be surprised to >hear that a WD/SMC EISA card can saturate 2-3 ethernets at small >packet sizes (typical traffic seen by a router). This is more a >reflection of my opinion of PC card technology, not FreeBSD or BSDI. Actually, I think it could saturate 2 ethers with an SMC ISA (not EISA) board. Maybe I should actually try this. :-) The driver I wrote for FreeBSD is actually quite well done (I'm patting myself on the back :-)) and uses a multi buffering technique I invented that has to my knowledge never been previously implemented. A typical "ttcp" run looks like this: (transmitter) [corbin:davidg]> ttcp -t implode ttcp-t: buflen=8192, nbuf=2048, align=16384/+0, port=5001 tcp -> implode ttcp-t: socket ttcp-t: connect ttcp-t: 16777216 bytes in 14.95 real seconds = 1096.08 KB/sec +++ ttcp-t: 2048 I/O calls, msec/call = 7.47, calls/sec = 137.01 ttcp-t: 0.0user 3.6sys 0:14real 24% 32i+188d 110maxrss 0+2pf 5602+9csw (receiver) [implode:davidg]> ttcp -r ttcp-r: buflen=8192, nbuf=2048, align=16384/+0, port=5001 tcp ttcp-r: socket ttcp-r: accept from 198.145.90.2 ttcp-r: 16777216 bytes in 14.96 real seconds = 1095.00 KB/sec +++ ttcp-r: 11372 I/O calls, msec/call = 1.35, calls/sec = 760.03 ttcp-r: 0.0user 2.4sys 0:14real 16% 32i+188d 152maxrss 0+2pf 11265+33csw I think the most important thing above is the (low) percent CPU time. The actual consumed CPU time is somewhat higher (not all of the system time is reflected in the percentage) - kernel profiling shows it to be about 30%. >If anyone has measured troughput under small packet load, I'd be >interested in hearing the result. Do you have a suggestion on how I might do such a test? It's a problem because TCP will coalesce socket writes until a full frame is gathered unless the TCP_NODELAY socket option is used. I believe setting this option will have other bad side effects (like setting the PUSH bit, and thus might solicit an immediate acknowledge). I'd be tempted to do a UDP test, but due to bugs in the UDP layer of all Net/2 derived code I've seen (including BSDI, NetBSD, and FreeBSD), the UDP performance is rather low - and additionally is difficult to test because of the lack of connection flow control. In fact, BSDI and NetBSD have a bug that causes a pathological condition whereby partial UDP datagrams will be fragmented/sent and resent repeatedly should a client application attempt to write packets too quickly to the socket. >Wrt DS3 - I didn't think a HSSI card for EISA existed. Does one >exist? I don't know; I did say that "this assertion is unproven". I based the opinion on extensive kernel profiling analysis of the socket and TCP performance. > Also, keep in mind that routers see an average packet size on >the order of 200 bytes. Do you really think an EISA bus can handle >the small packet throughput? Big packets are easy, too bad real >traffic isn't all big packets. All the analysis I've done of bottlenecks in FreeBSD has shown that the actual overhead of packet handling was fairly low compared to the time to get/put data out to ISA shared memory. Unlike BSDI, FreeBSD's interrupt overhead is extremely low and would not be significantly affected by the increased interrupt rate. This isn't the only factor of course, and the large number of variables makes it difficult to guess how well it might work without actually testing specific hardware. >BTW - I've corrected my own untruths by way of Cc. Thanks for the >note and the good work that you are doing on FreeBSD. Thanks. I hope this rather lengthy reply isn't totally boring other folks on this mailing list. BTW, is this a list I should be subscribed to? -DG - - - - - - - - - - - - - - - - -