- Test - lists.nanog.org

Let's clean up these configurations
by enke 16 Mar '93

16 Mar '93

Dear Regional/Midlevel Techs: At the January's MERIT/NSFNET Regional Tech Meeting, we discussed the anomaly that a number of networks configured in the NSFNET Policy Routing Database were announced constantly only by their non-primary AS's to the NSFNET backbone. The consensus at the meeting was that the configuration of such networks should be changed so that the database reflects the reality more closely. To facilitate that task, we are hereby sending you a list of such networks and we ask you to take one of the following actions: (1) Submit requests to nsfnet-admin(a)merit.edu to have their primary and/or secondary announcement configurations changed in the NSFNET Policy Routing Database. (2) Make necessary changes at the regional/midlevel configurations to enable their primary and/or secondary announcements of such networks to the NSFNET backbone. Please direct questions concerning this list to me at: enke(a)merit.edu or 313-764-0294. Thank you for your cooperation. -- Enke Chen Merit/NSFNET ======================================================================= *** The following networks are announced by tertiary/quadrinary/... AS, but not by primary or secondary AS: 192.54.38 MPIHD-LAN C:DE D:08/13/91 1:293 2:291 3:513 128.45 DEC-WRL-NET C:US D:06/22/91 1:189 2:200 3:201 4:701 5:702 6:279 192.6.78 HP-CUP C:US D:05/25/92 1:174 2:200 3:201 4:560 5:281 6:209 7:210 156.99 MINESOTADOA1 C:US D:01/20/93 1:267 2:1225 3:266 4:555 192.6.150 HP-AND C:US D:04/10/92 1:200 2:201 3:174 4:560 5:281 6:209 7:210 192.76.246 GMDTEST1-DE C:DE D:12/13/90 1:293 2:291 3:590 4:513 192.109.31 EMBNET-HH C:DE D:02/07/92 1:293 2:291 3:513 192.43.188 AGPS-WAN C:US D:01/29/90 1:291 2:293 3:68 4:209 192.131.254 NET-PHY C:US D:11/14/91 1:293 2:291 3:560 4:281 164.99 FIELD C:US D:03/01/93 1:200 2:201 3:210 4:209 ======================================================================= *** The following networks are announced by secondary AS, but not by primary AS: 130.180 DEC-ZK-NET C:US D:06/22/91 1:189 2:200 3:201 4:701 5:702 6:279 144.214 CPNET1 C:HK D:01/05/92 1:1740 2:372 3:297 130.251 UG-NET C:IT D:01/22/90 1:1800 2:701 3:274 4:60 144.252 LABCOM-ETDL C:US D:02/04/92 1:555 2:19 3:568 192.31.49 BARRNET-TEST3 C:US D:03/12/92 1:200 42:201 192.35.75 FOTLANMS C:US D:01/29/90 1:60 2:274 198.17.92 PORTSIS C:US D:02/25/93 1:22 2:568 3:19 192.86.111 BAYONNE-GW3 C:US D:01/28/92 1:19 2:568 192.26.119 FUUG-ETHER C:FI D:11/02/90 1:701 2:1800 192.121.155 LON-EBONE C:GB D:10/16/92 1:297 2:1800 3:1240 4:513 192.58.245 MDANET C:CA D:02/04/92 1:602 2:601 3:603 12:1391 13:1393 192.131.85 PSNET3 C:US D:12/21/92 1:1328 2:701 3:702 4:279 192.131.86 PSNET4 C:US D:12/21/92 1:1328 2:701 3:702 4:279 192.75.154 TWUNET1 C:CA D:07/25/91 1:602 2:601 3:603 12:1391 13:1393 192.75.155 TWUNET2 C:CA D:07/25/91 1:602 2:601 3:603 12:1391 13:1393

2 1

Additions to the NSFNET policy-based routing database
by Steven K. Widmayer 16 Mar '93

16 Mar '93

The following additions have been made to the NSFNET policy-based routing database and will be installed on the backbone by 08:00 EST Tuesday: Total configured networks: 10213 IP address Net name Country Date Priority:AS ---------- -------- ------- ---- ----------- 133.102 SHIGANET C:JP D:03/15/93 1:1240 2:1800 142.53 ISTCNET C:CA D:03/15/93 1:601 2:602 3:603 11:1391 13:1393 152.121 DOTNETA-121 C:US D:03/15/93 1:93 192.68.22 MELATL C:US D:03/15/93 1:1800 2:1240 192.70.179 UTINS-CNET C:JP D:03/15/93 1:1240 2:1800 192.75.17 FCMR C:CA D:03/15/93 1:601 2:602 3:603 11:1391 13:1393 192.83.68 RELEV-NET C:FI D:03/15/93 1:1957 192.109.76 SELRC-LAN C:DE D:03/15/93 1:1957 192.109.107 ATEG-NET C:DE D:03/15/93 1:1957 192.109.176 DK-VS C:DE D:03/15/93 1:1957 192.114.3 LANOPT1-NET C:IL D:03/15/93 1:2149 2:174 192.114.4 LANOPT2-NET C:IL D:03/15/93 1:2149 2:174 192.153.195 QUME C:US D:03/15/93 1:200 2:201 192.197.64 NORCOL C:CA D:03/15/93 1:601 2:602 3:603 11:1391 13:1393 192.197.67 GTAADMIN1 C:CA D:03/15/93 1:601 2:602 3:603 11:1391 13:1393 192.197.71 GTAADMIN5 C:CA D:03/15/93 1:601 2:602 3:603 11:1391 13:1393 192.197.72 GTAADMIN6 C:CA D:03/15/93 1:601 2:602 3:603 11:1391 13:1393 192.197.113 NCR-NET C:CA D:03/15/93 1:601 2:602 3:603 11:1391 13:1393 192.197.114 FCOR-NET C:CA D:03/15/93 1:601 2:602 3:603 11:1391 13:1393 192.197.115 CPL-NET C:CA D:03/15/93 1:601 2:602 3:603 11:1391 13:1393 192.197.140 DFOOTT C:CA D:03/15/93 1:601 2:602 3:603 11:1391 13:1393 192.197.167 UNIPISSING C:CA D:03/15/93 1:601 2:602 3:603 11:1391 13:1393 192.197.190 UBISHOP C:CA D:03/15/93 1:603 2:602 3:601 11:1393 13:1391 192.218.112 KASEINET C:JP D:03/15/93 1:1240 2:1800 198.3.4 STERLING-DC C:US D:03/15/93 1:701 2:702 198.3.132 BOSTIC C:US D:03/15/93 1:701 2:702 198.17.250 ARTISOFT C:US D:03/15/93 1:1240 2:1800 198.49.101 BASIX C:US D:03/15/93 1:1240 2:1800 198.49.146 MITRE-DMZ C:US D:03/15/93 1:701 2:702 200.6 AMERQ C:EC D:03/15/93 1:1800 2:1240 200.6.1 CIMSI C:EC D:03/15/93 1:1800 2:1240 200.6.2 CIDRALAS C:EC D:03/15/93 1:1800 2:1240 200.6.3 CENMEP C:EC D:03/15/93 1:1800 2:1240 200.6.4 BCC2 C:EC D:03/15/93 1:1800 2:1240 200.6.5 CM C:EC D:03/15/93 1:1800 2:1240 200.6.6 INP C:EC D:03/15/93 1:1800 2:1240 200.6.9 INEC C:EC D:03/15/93 1:1800 2:1240 200.6.10 HCK C:EC D:03/15/93 1:1800 2:1240 200.6.14 FEP C:EC D:03/15/93 1:1800 2:1240 200.6.15 HEE C:EC D:03/15/93 1:1800 2:1240 200.6.17 JEFF C:EC D:03/15/93 1:1800 2:1240 200.6.18 FOECUAT C:EC D:03/15/93 1:1800 2:1240 200.6.19 LIFE C:EC D:03/15/93 1:1800 2:1240 200.6.20 INCAP C:EC D:03/15/93 1:1800 2:1240 200.6.21 ECUANET2 C:EC D:03/15/93 1:1800 2:1240 200.6.23 TES C:EC D:03/15/93 1:1800 2:1240 200.6.25 COMWARE C:EC D:03/15/93 1:1800 2:1240 200.6.26 CAHGQUIL C:EC D:03/15/93 1:1800 2:1240 200.6.27 FUICE C:EC D:03/15/93 1:1800 2:1240 200.6.28 HCJBHCD C:EC D:03/15/93 1:1800 2:1240 200.6.29 FE C:EC D:03/15/93 1:1800 2:1240 200.6.30 FCDARWIN C:EC D:03/15/93 1:1800 2:1240 200.6.31 INAMHI C:EC D:03/15/93 1:1800 2:1240 200.6.32 INECEL C:EC D:03/15/93 1:1800 2:1240 200.6.33 PUCEPAA C:EC D:03/15/93 1:1800 2:1240 200.6.34 SOFTUNO C:EC D:03/15/93 1:1800 2:1240 Network IP: 133.102 Network Name: SHIGANET Location: Shiga University, Banba 1-1-1, Hikone-shi, Shiga 522, JAPAN Country Code: JP 1:1240 ICM-Pacific 2:1800 ICM-Atlantic Network IP: 142.53 Network Name: ISTCNET Location: Department of Industry, Science & Technology Canada, CD Howe, Room 346e, 235 Queen Street, Ottawa, ON K1A 0H5, CANADA Country Code: CA 1:601 CA*net in Toronto 2:602 CA*net in Montreal 3:603 CA*net in Quebec 11:1391 CA*net in Toronto 13:1393 CA*net in Quebec Network IP: 152.121 Network Name: DOTNETA-121 Location: U.S. Department of Transportation, 400 7th Street SW, Washington, DC 20590, USA Country Code: US 1:93 MIDnet Network IP: 192.68.22 Network Name: MELATL Location: Melita Electronic Labs, Inc., 6630 Bay Circle, Norcross, GA 30071, USA Country Code: US 1:1800 ICM-Atlantic 2:1240 ICM-Pacific Network IP: 192.70.179 Network Name: UTINS-CNET Location: Regional Internet Connection-Tsukuba Committee, c/o Science Information Processing Center, University of Tsukuba, 1-1-1 Tennoudai, Tsukuba, Ibaraki 305, JAPAN Country Code: JP 1:1240 ICM-Pacific 2:1800 ICM-Atlantic Network IP: 192.75.17 Network Name: FCMR Location: Forestry Canada - Maritimes Region, P.O. Box 4000, Fredericton, NB E3B 5P7, CANADA Country Code: CA 1:601 CA*net in Toronto 2:602 CA*net in Montreal 3:603 CA*net in Quebec 11:1391 CA*net in Toronto 13:1393 CA*net in Quebec Network IP: 192.83.68 Network Name: RELEV-NET Location: ANS-CIX Country Code: FI 1:1957 ANSCIX-AS Network IP: 192.109.76 Network Name: SELRC-LAN Location: ANS-CIX Country Code: DE 1:1957 ANSCIX-AS Network IP: 192.109.107 Network Name: ATEG-NET Location: ANS-CIX Country Code: DE 1:1957 ANSCIX-AS Network IP: 192.109.176 Network Name: DK-VS Location: ANS-CIX Country Code: DE 1:1957 ANSCIX-AS Network IP: 192.114.3 Network Name: LANOPT1-NET Location: Lanoptic Ltd., Ramat Gabriel Ind. Park, P.O. Box 184, Migdal Haemek, ISRAEL Country Code: IL 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI Network IP: 192.114.4 Network Name: LANOPT2-NET Location: Lanoptic Ltd., Ramat Gabriel Ind. Park, P.O. Box 184, Migdal Haemek, ISRAEL Country Code: IL 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI Network IP: 192.153.195 Network Name: QUME Location: Qume Corporation, 260 S. Milpitas Blvd., Milpitas, CA 95035, USA Country Code: US 1:200 BARRNet 2:201 BARRNet Network IP: 192.197.64 Network Name: NORCOL Location: Northern College, Northern College of Applied Arts and Technology, Computer Studies, 140 Government Road East, Kirkland Lake, ON P2N 3L8, CANADA Country Code: CA 1:601 CA*net in Toronto 2:602 CA*net in Montreal 3:603 CA*net in Quebec 11:1391 CA*net in Toronto 13:1393 CA*net in Quebec Network IP: 192.197.67 Network Name: GTAADMIN1 Location: Government Telecomunications Agency, VPO/MOI Room 1020, Journal Tower North, 300 Slater Street, Ottawa, ON K1A 0C8, CANADA Country Code: CA 1:601 CA*net in Toronto 2:602 CA*net in Montreal 3:603 CA*net in Quebec 11:1391 CA*net in Toronto 13:1393 CA*net in Quebec Network IP: 192.197.71 Network Name: GTAADMIN5 Location: Government Telecomunications Agency, VPO/MOI Room 1020, Journal Tower North, 300 Slater Street, Ottawa, ON K1A 0C8, CANADA Country Code: CA 1:601 CA*net in Toronto 2:602 CA*net in Montreal 3:603 CA*net in Quebec 11:1391 CA*net in Toronto 13:1393 CA*net in Quebec Network IP: 192.197.72 Network Name: GTAADMIN6 Location: Government Telecomunications Agency, VPO/MOI Room 1020, Journal Tower North, 300 Slater Street, Ottawa, ON K1A 0C8, CANADA Country Code: CA 1:601 CA*net in Toronto 2:602 CA*net in Montreal 3:603 CA*net in Quebec 11:1391 CA*net in Toronto 13:1393 CA*net in Quebec Network IP: 192.197.113 Network Name: NCR-NET Location: Forestry Canada, National Capital Region, 351 St. Joseph Blvd., Hull, Quebec K1A 1G5, CANADA Country Code: CA 1:601 CA*net in Toronto 2:602 CA*net in Montreal 3:603 CA*net in Quebec 11:1391 CA*net in Toronto 13:1393 CA*net in Quebec Network IP: 192.197.114 Network Name: FCOR-NET Location: Forestry Canada, National Capital Region, 351 St. Joseph Blvd., Hull, Quebec K1A 1G5, CANADA Country Code: CA 1:601 CA*net in Toronto 2:602 CA*net in Montreal 3:603 CA*net in Quebec 11:1391 CA*net in Toronto 13:1393 CA*net in Quebec Network IP: 192.197.115 Network Name: CPL-NET Location: Forestry Canada, National Capital Region, 351 St. Joseph Blvd., Hull, Quebec K1A 1G5, CANADA Country Code: CA 1:601 CA*net in Toronto 2:602 CA*net in Montreal 3:603 CA*net in Quebec 11:1391 CA*net in Toronto 13:1393 CA*net in Quebec Network IP: 192.197.140 Network Name: DFOOTT Location: Government of Canada, Dept. of Fisheries and Oceans, 200 Kent Street, Ottawa, ON K1A 0E6, CANADA Country Code: CA 1:601 CA*net in Toronto 2:602 CA*net in Montreal 3:603 CA*net in Quebec 11:1391 CA*net in Toronto 13:1393 CA*net in Quebec Network IP: 192.197.167 Network Name: UNIPISSING Location: Nipissing University, Data Processing, A124, 100 College Drive, North Bay, ON P1B 8L7, CANADA Country Code: CA 1:601 CA*net in Toronto 2:602 CA*net in Montreal 3:603 CA*net in Quebec 11:1391 CA*net in Toronto 13:1393 CA*net in Quebec Network IP: 192.197.190 Network Name: UBISHOP Location: Bishop's University, College Street, Lennoxvile, QC J1M 1Z7, CANADA Country Code: CA 1:603 CA*net in Quebec 2:602 CA*net in Montreal 3:601 CA*net in Toronto 11:1393 CA*net in Quebec 13:1391 CA*net in Toronto Network IP: 192.218.112 Network Name: KASEINET Location: Tsukuba Junior College Tokyo Kasei Gakuin, 3-1 Azuma, Tsukuba-shi, Ibaraki-ken, JAPAN Country Code: JP 1:1240 ICM-Pacific 2:1800 ICM-Atlantic Network IP: 198.3.4 Network Name: STERLING-DC Location: Sterling Software, 8000 Towers Crescent Drive, Vienna, VA, 22182, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 198.3.132 Network Name: BOSTIC Location: Keith Bostic, 16 Rowena Road, Newton, MA 02159, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 198.17.250 Network Name: ARTISOFT Location: Artisoft, Inc., 691 East River Road, Tucson, AZ 85714, USA Country Code: US 1:1240 ICM-Pacific 2:1800 ICM-Atlantic Network IP: 198.49.101 Network Name: BASIX Location: Data Basix, 9460 E 39th Street, Tucson, AZ 85730, USA Country Code: US 1:1240 ICM-Pacific 2:1800 ICM-Atlantic Network IP: 198.49.146 Network Name: MITRE-DMZ Location: The MITRE Corporation, 7525 Colshire Drive, McLean, VA 22102, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 200.6 Network Name: AMERQ Location: Fundacion Colegio Americano de Quito, Casilla No. 17-01-157, Quito, ECUADOR Country Code: EC 1:1800 ICM-Atlantic 2:1240 ICM-Pacific Network IP: 200.6.1 Network Name: CIMSI Location: Fundacion Centro de Investigacion Medica Santa Ines, Casilla No. 980, Cuenca, ECUADOR Country Code: EC 1:1800 ICM-Atlantic 2:1240 ICM-Pacific Network IP: 200.6.2 Network Name: CIDRALAS Location: Centro de Investigacion Dr. Ramon Lazo, Ciudadela Kennedy Vieja, Calle Segunda oeste No. 121, Guayaquil, ECUADOR Country Code: EC 1:1800 ICM-Atlantic 2:1240 ICM-Pacific Network IP: 200.6.3 Network Name: CENMEP Location: Centro Medico Quirurgico Pichincha, Veintimilla No. 1259 y Paez, Quito, ECUADOR Country Code: EC 1:1800 ICM-Atlantic 2:1240 ICM-Pacific Network IP: 200.6.4 Network Name: BCC2 Location: Brookdale Community College, P.O. Box 09-06-2328, Guayaquil, ECUADOR Country Code: EC 1:1800 ICM-Atlantic 2:1240 ICM-Pacific Network IP: 200.6.5 Network Name: CM Location: Clinica Mariduena, Calle San Jorge 402 y Olimpo, Guayaquil, ECUADOR Country Code: EC 1:1800 ICM-Atlantic 2:1240 ICM-Pacific Network IP: 200.6.6 Network Name: INP Location: Instituto Nacional de Pesca, P.O. Box 09-04 15131, Guayaquil, ECUADOR Country Code: EC 1:1800 ICM-Atlantic 2:1240 ICM-Pacific Network IP: 200.6.9 Network Name: INEC Location: Instituto Nacional de Estadisticas y Censos, 10 de Agosto 229, Quito, ECUADOR Country Code: EC 1:1800 ICM-Atlantic 2:1240 ICM-Pacific Network IP: 200.6.10 Network Name: HCK Location: Hospital Clinica Kennedy, Casilla No. 10435, Guayaquil, ECUADOR Country Code: EC 1:1800 ICM-Atlantic 2:1240 ICM-Pacific Network IP: 200.6.14 Network Name: FEP Location: Fundacion Educativa Pestalozzi, Casilla No. 17-11-6370, Quito, ECUADOR Country Code: EC 1:1800 ICM-Atlantic 2:1240 ICM-Pacific Network IP: 200.6.15 Network Name: HEE Location: Hospital Eugenio Espejo Quito, Av. Colombia y Yaguachi s/n, Quito, ECUADOR Country Code: EC 1:1800 ICM-Atlantic 2:1240 ICM-Pacific Network IP: 200.6.17 Network Name: JEFF Location: Colegio Bilingue Jefferson, Casilla No. 09-01-4180, Guayaquil, ECUADOR Country Code: EC 1:1800 ICM-Atlantic 2:1240 ICM-Pacific Network IP: 200.6.18 Network Name: FOECUAT Location: Fundacion Oftalmologica Ecuatoriana, Casilla No. 09-01-4915, Guayaquil, ECUADOR Country Code: EC 1:1800 ICM-Atlantic 2:1240 ICM-Pacific Network IP: 200.6.19 Network Name: LIFE Location: Laboratorios Life, P.O. Box 17-001-00458, Guayaquil, ECUADOR Country Code: EC 1:1800 ICM-Atlantic 2:1240 ICM-Pacific Network IP: 200.6.20 Network Name: INCAP Location: Instituto Nacional de Cardiologia, Campus Politecnico - La Prosperina, Guayaquil, ECUADOR Country Code: EC 1:1800 ICM-Atlantic 2:1240 ICM-Pacific Network IP: 200.6.21 Network Name: ECUANET2 Location: Corp. Ecuatoriana de Informacion, P.Ycaza 200, Guayaquil, ECUADOR Country Code: EC 1:1800 ICM-Atlantic 2:1240 ICM-Pacific Network IP: 200.6.23 Network Name: TES Location: Instituto Tecnico Superior Espiritu Santo, Av. Juan Tanca Marengo Km. 2,5, Guayaquil, ECUADOR Country Code: EC 1:1800 ICM-Atlantic 2:1240 ICM-Pacific Network IP: 200.6.25 Network Name: COMWARE Location: SAE/COMWARE, P.O. Box 1716142, Quito, ECUADOR Country Code: EC 1:1800 ICM-Atlantic 2:1240 ICM-Pacific Network IP: 200.6.26 Network Name: CAHGQUIL Location: Colegio Aleman Humboldt, Casilla 4760, Guayaquil, ECUADOR Country Code: EC 1:1800 ICM-Atlantic 2:1240 ICM-Pacific Network IP: 200.6.27 Network Name: FUICE Location: Universidad Central del Ecuador, Apartado 20 Suc. 12 de Octubre, Quito, ECUADOR Country Code: EC 1:1800 ICM-Atlantic 2:1240 ICM-Pacific Network IP: 200.6.28 Network Name: HCJBHCD Location: Hospital Vozandes - Quito, Casilla 17-17-691, Quito, ECUADOR Country Code: EC 1:1800 ICM-Atlantic 2:1240 ICM-Pacific Network IP: 200.6.29 Network Name: FE Location: Fundacion Ecuador, Victor Manuel Rendon No. 401 y Cordova, Guayaquil, ECUADOR Country Code: EC 1:1800 ICM-Atlantic 2:1240 ICM-Pacific Network IP: 200.6.30 Network Name: FCDARWIN Location: Estacion Cientifica Charles Darwin, Casilla 17-01-5918, Guayaquil, ECUADOR Country Code: EC 1:1800 ICM-Atlantic 2:1240 ICM-Pacific Network IP: 200.6.31 Network Name: INAMHI Location: Instituto Nacional de Meteorologia e Hidrologia, Carrion No. 926 y Paez, Quito, ECUADOR Country Code: EC 1:1800 ICM-Atlantic 2:1240 ICM-Pacific Network IP: 200.6.32 Network Name: INECEL Location: Instituto Ecuatoriano de Electrificacion, Casilla 565-A, Guayaquil, ECUADOR Country Code: EC 1:1800 ICM-Atlantic 2:1240 ICM-Pacific Network IP: 200.6.33 Network Name: PUCEPAA Location: Pontificia Universidad Catolica de Ambato, Rocafuerte y Lalama, Esq., Ambato, ECUADOR Country Code: EC 1:1800 ICM-Atlantic 2:1240 ICM-Pacific Network IP: 200.6.34 Network Name: SOFTUNO Location: SOFTUNO S.A., Casilla 09-015539, Guayaquil, ECUADOR Country Code: EC 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ***************************************************************** The configuration reports which reflect today's update will be available for anonymous ftp on nis.nsf.net by 08:00 EST Tuesday: configuration reports -- nis.nsf.net:nsfnet/announced.networks: ans_core.now as-as.now as-gw.now as-site.now as.now country.now gate-gw.now net-comp.now net-ter.now net-net.now netcount.now non-us.now nss-as.now nss-gw.now nss.now networks sorted by AS -- nis.nsf.net:nsfnet/announced.networks: nets.as_<AS number> NSS routing software configuration files -- nis.nsf.net:nsfnet/backbone.configuration: nss<NSS number>.t3p Please send all requests for configuration changes to nsfnet-admin(a)merit.edu using the NSFNET configuration forms. The forms are available on-line from the nis.nsf.net 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.gate, and template.as. ******************************* --Steve Widmayer Merit/NSFNET skw(a)merit.edu --Riaz Taherzadeh-Yazdian NSFNET/ANSNET rty(a)ans.net

1 0

Additions to the NSFNET policy-based routing database
by Steven K. Widmayer 12 Mar '93

12 Mar '93

The following additions have been made to the NSFNET policy-based routing database and will be installed on the backbone by 08:00 EST: Total configured networks: 10167 IP address Net name Country Date Priority:AS ---------- -------- ------- ---- ----------- 130.131 GTE-CS C:US D:03/11/93 1:1240 152.160 NUG-NET C:US D:03/11/93 1:1325 155.226 ADC C:US D:03/11/93 1:1800 2:1240 158.113 UNICEFNYHQ C:US D:03/11/93 1:174 164.116 WEDNET-B C:US D:03/11/93 1:1331 164.119 NESTATENET C:US D:03/11/93 1:1800 2:1240 192.108.136 IPM C:CS D:03/11/93 1:513 2:1800 192.108.217 ARC-SIMEXPNET C:US D:03/11/93 1:372 2:297 192.108.219 ARC-KAOEXPNET C:US D:03/11/93 1:372 2:297 192.108.220 ARC-KAOFACNET C:US D:03/11/93 1:372 2:297 192.129.45 TOPOLOGIX C:DE D:03/11/93 1:1324 192.131.82 DICKENSNET C:US D:03/11/93 1:174 192.133.104 GAG-NET C:US D:03/12/93 1:560 2:281 192.150.161 PACBELL1 C:US D:03/11/93 1:200 2:201 192.187.174 NETBLK-NETCOM174 C:US D:03/11/93 1:200 2:201 192.187.175 NETBLK-NETCOM175 C:US D:03/11/93 1:200 2:201 192.207.186 ADACNTYLIB C:US D:03/11/93 1:210 2:209 192.216.52 BARRNET-216-52 C:US D:03/11/93 1:200 2:201 192.216.61 BARRNET-216-61 C:US D:03/12/93 1:200 2:201 192.216.136 BARRNET-216-136 C:US D:03/12/93 1:200 2:201 192.239.27 GIT-SUB12 C:US D:03/11/93 1:279 2:86 192.239.28 GIT-SUB13 C:US D:03/11/93 1:279 2:86 192.239.50 FIS-NET C:US D:03/11/93 1:86 2:279 193.60.224 BCC-ACUK-1 C:GB D:03/11/93 1:297 2:372 193.72.218 MICRO-FRAME-C1 C:CH D:03/12/93 1:1957 193.174.253 RD-VARTA C:DE D:03/11/93 1:293 2:291 193.196.1 PSYRES-STGT1 C:DE D:03/11/93 1:1324 193.196.2 FH-BIBERACH1 C:DE D:03/11/93 1:1324 193.196.3 FH-BIBERACH2 C:DE D:03/11/93 1:1324 193.196.4 BA-LOERRACH C:DE D:03/11/93 1:1324 193.196.8 IDS-MANNHEIM C:DE D:03/11/93 1:1324 193.196.10 ZUMANET C:DE D:03/11/93 1:1324 193.196.16 TUENET-C16 C:DE D:03/11/93 1:1324 193.196.17 TUENET-C17 C:DE D:03/11/93 1:1324 193.196.18 TUENET-C18 C:DE D:03/11/93 1:1324 193.196.19 TUENET-C19 C:DE D:03/11/93 1:1324 193.196.20 TUENET-C20 C:DE D:03/11/93 1:1324 193.196.21 TUENET-C21 C:DE D:03/11/93 1:1324 193.196.22 TUENET-C22 C:DE D:03/11/93 1:1324 193.196.23 TUENET-C23 C:DE D:03/11/93 1:1324 193.196.24 TUENET-C24 C:DE D:03/11/93 1:1324 193.196.25 TUENET-C25 C:DE D:03/11/93 1:1324 193.196.26 TUENET-C26 C:DE D:03/11/93 1:1324 193.196.27 TUENET-C27 C:DE D:03/11/93 1:1324 193.196.28 TUENET-C28 C:DE D:03/11/93 1:1324 193.196.29 TUENET-C29 C:DE D:03/11/93 1:1324 193.196.30 TUENET-C30 C:DE D:03/11/93 1:1324 193.196.31 TUENET-C31 C:DE D:03/11/93 1:1324 193.196.32 KLICK-C32 C:DE D:03/12/93 1:1324 193.196.33 KLICK-C33 C:DE D:03/12/93 1:1324 193.196.34 KLICK-C34 C:DE D:03/12/93 1:1324 193.196.35 KLICK-C35 C:DE D:03/12/93 1:1324 193.196.36 KLICK-C36 C:DE D:03/12/93 1:1324 193.196.37 KLICK-C37 C:DE D:03/12/93 1:1324 193.196.38 KLICK-C38 C:DE D:03/12/93 1:1324 193.196.39 KLICK-C39 C:DE D:03/12/93 1:1324 193.196.40 KLICK-C40 C:DE D:03/12/93 1:1324 193.196.41 KLICK-C41 C:DE D:03/12/93 1:1324 193.196.42 KLICK-C42 C:DE D:03/12/93 1:1324 193.196.43 KLICK-C43 C:DE D:03/12/93 1:1324 193.196.44 KLICK-C44 C:DE D:03/12/93 1:1324 193.196.45 KLICK-C45 C:DE D:03/12/93 1:1324 193.196.46 KLICK-C46 C:DE D:03/12/93 1:1324 193.196.47 KLICK-C47 C:DE D:03/12/93 1:1324 193.196.48 KLICK-C48 C:DE D:03/12/93 1:1324 193.196.49 KLICK-C49 C:DE D:03/12/93 1:1324 193.196.50 KLICK-C50 C:DE D:03/12/93 1:1324 193.196.51 KLICK-C51 C:DE D:03/12/93 1:1324 193.196.52 KLICK-C52 C:DE D:03/12/93 1:1324 193.196.53 KLICK-C53 C:DE D:03/12/93 1:1324 193.196.54 KLICK-C54 C:DE D:03/12/93 1:1324 193.196.55 KLICK-C55 C:DE D:03/12/93 1:1324 193.196.56 KLICK-C56 C:DE D:03/12/93 1:1324 193.196.57 KLICK-C57 C:DE D:03/12/93 1:1324 193.196.58 KLICK-C58 C:DE D:03/12/93 1:1324 193.196.59 KLICK-C59 C:DE D:03/12/93 1:1324 193.196.60 KLICK-C60 C:DE D:03/12/93 1:1324 193.196.61 KLICK-C61 C:DE D:03/12/93 1:1324 193.196.62 KLICK-C62 C:DE D:03/12/93 1:1324 193.196.63 KLICK-C63 C:DE D:03/12/93 1:1324 193.196.64 FH-KARL-C64 C:DE D:03/12/93 1:1324 193.196.65 FH-KARL-C65 C:DE D:03/12/93 1:1324 193.196.128 PH-LUDWIG1 C:DE D:03/11/93 1:1324 193.196.129 PH-LUDWIG2 C:DE D:03/11/93 1:1324 193.196.130 FHB-STGT-NEU C:DE D:03/11/93 1:1324 193.196.136 FHT-STGT-NEU136 C:DE D:03/11/93 1:1324 193.196.137 FHT-STGT-NEU137 C:DE D:03/11/93 1:1324 193.196.138 FHT-STGT-NEU138 C:DE D:03/11/93 1:1324 193.196.139 FHT-STGT-NEU139 C:DE D:03/11/93 1:1324 193.196.140 FHT-STGT-NEU140 C:DE D:03/11/93 1:1324 193.196.141 FHT-STGT-NEU141 C:DE D:03/11/93 1:1324 193.196.142 FHT-STGT-NEU142 C:DE D:03/11/93 1:1324 193.196.143 FHT-STGT-NEU143 C:DE D:03/11/93 1:1324 198.17.175 OSHA-SLC-NET C:US D:03/11/93 1:210 2:209 198.22.17 CALIPER C:US D:03/12/93 1:560 2:281 198.29.253 CECO126 C:US D:03/11/93 1:267 2:1225 3:266 198.37.32 RASTEROPS1 C:US D:03/12/93 1:701 2:702 198.37.33 RASTEROPS2 C:US D:03/12/93 1:701 2:702 198.37.34 RASTEROPS3 C:US D:03/12/93 1:701 2:702 198.37.35 RASTEROPS4 C:US D:03/12/93 1:701 2:702 198.37.36 RASTEROPS5 C:US D:03/12/93 1:701 2:702 198.37.37 RASTEROPS6 C:US D:03/12/93 1:701 2:702 198.37.38 RASTEROPS7 C:US D:03/12/93 1:701 2:702 198.37.39 RASTEROPS8 C:US D:03/12/93 1:701 2:702 198.37.40 RASTEROPS9 C:US D:03/12/93 1:701 2:702 198.37.41 RASTEROPS10 C:US D:03/12/93 1:701 2:702 198.37.42 RASTEROPS11 C:US D:03/12/93 1:701 2:702 198.37.43 RASTEROPS12 C:US D:03/12/93 1:701 2:702 198.37.44 RASTEROPS13 C:US D:03/12/93 1:701 2:702 198.37.45 RASTEROPS14 C:US D:03/12/93 1:701 2:702 198.37.46 RASTEROPS15 C:US D:03/12/93 1:701 2:702 198.37.128 NETSERV1 C:US D:03/11/93 1:1740 198.49.96 SOFTSOLUT-NET C:US D:03/11/93 1:209 2:210 198.49.246 NICHOLS-NET C:US D:03/11/93 1:209 2:210 198.52.32 UUNORTH-NET32 C:CA D:03/12/93 1:2493 198.62.158 IDRC-1 C:CA D:03/12/93 1:2493 198.62.159 IDRC-2 C:CA D:03/12/93 1:2493 198.67.16 FALCONBLK1 C:US D:03/11/93 1:1800 2:1240 198.67.17 FALCONBLK2 C:US D:03/11/93 1:1800 2:1240 198.67.18 FALCONBLK3 C:US D:03/11/93 1:1800 2:1240 198.67.19 FALCONBLK4 C:US D:03/11/93 1:1800 2:1240 Network IP: 130.131 Network Name: GTE-CS Location: GTE Communication Systems, 400 North Wolf Road, Northlake, IL 60164, USA Country Code: US 1:1240 ICM-Pacific Network IP: 152.160 Network Name: NUG-NET Location: Network Users Group, Ltd., 17 East Main Street, Milan, MI 48160, USA Country Code: US 1:1325 ANS Cleveland - DNSS 43 Network IP: 155.226 Network Name: ADC Location: ADC Telecommunications Inc., 4900 W. 78th Street, MS 85, Minneapolis, MN 55435, USA Country Code: US 1:1800 ICM-Atlantic 2:1240 ICM-Pacific Network IP: 158.113 Network Name: UNICEFNYHQ Location: UNICEF, 3 United Nations Plaza, MS 3F, New York, NY 10017, USA Country Code: US 1:174 NYSERNet Regional Network / PSI Network IP: 164.116 Network Name: WEDNET-B Location: Washington Schools Information Processing Cooperative, 2000 - 200th Place, SW, Lynnwood, WA 98036, USA Country Code: US 1:1331 ANS Seattle - DNSS 91 Network IP: 164.119 Network Name: NESTATENET Location: State of Nebraska, Division of Communications, 501 South 14th Street, Room 209, Lincoln, NE 68508, USA Country Code: US 1:1800 ICM-Atlantic 2:1240 ICM-Pacific Network IP: 192.108.136 Network Name: IPM Location: Institute of Physical Metallurgy, Zizkova 22, 612 62 Brno, CZECHO SLOVAKIA Country Code: CS 1:513 EASInet / CERN 2:1800 ICM-Atlantic Network IP: 192.108.217 Network Name: ARC-SIMEXPNET Location: NASA Ames Research Center, MS 233-8, Moffett Field, CA 94035, USA Country Code: US 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) Network IP: 192.108.219 Network Name: ARC-KAOEXPNET Location: NASA Ames Research Center, MS 233-8, Moffett Field, CA 94035, USA Country Code: US 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) Network IP: 192.108.220 Network Name: ARC-KAOFACNET Location: NASA Ames Research Center, MS 233-8, Moffett Field, CA 94035, USA Country Code: US 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) Network IP: 192.129.45 Network Name: TOPOLOGIX Location: Topologix GmbH - Hamburg, Grosse Bleichen 12, W-2000 Hamburg 36, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 192.131.82 Network Name: DICKENSNET Location: Dickens Data Systems, Inc., 1175 Northmeadow Parkway, Suite 150, Roswell, GA 30076, USA Country Code: US 1:174 NYSERNet Regional Network / PSI Network IP: 192.133.104 Network Name: GAG-NET Location: Garbee and Garbee, 4390 Darr Circle, Black Forest, CO 80908, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network Network IP: 192.150.161 Network Name: PACBELL1 Location: Pacific Bell, 2600 Camino Ramon, San Ramon, CA 94583, USA Country Code: US 1:200 BARRNet 2:201 BARRNet Network IP: 192.187.174 Network Name: NETBLK-NETCOM174 Location: Netcom - Online Communications Services, 4000 Moorpark Avenue - Suite 209, San Jose, CA 95117, USA Country Code: US 1:200 BARRNet 2:201 BARRNet Network IP: 192.187.175 Network Name: NETBLK-NETCOM175 Location: Netcom - Online Communications Services, 4000 Moorpark Avenue - Suite 209, San Jose, CA 95117, USA Country Code: US 1:200 BARRNet 2:201 BARRNet Network IP: 192.207.186 Network Name: ADACNTYLIB Location: Ada County Library, 1910 University Drive, Boise, ID 83725, USA Country Code: US 1:210 Westnet Regional Network (Utah Attachment) - ENSS 142 2:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 Network IP: 192.216.52 Network Name: BARRNET-216-52 Location: BARRNet, c/o Stanford University, Pine Hall 115, Stanford, CA 94305-4122, USA Country Code: US 1:200 BARRNet 2:201 BARRNet Network IP: 192.216.61 Network Name: BARRNET-216-61 Location: BARRNet, c/o Stanford University, Pine Hall 115, Stanford, CA 94305-4122, USA Country Code: US 1:200 BARRNet 2:201 BARRNet Network IP: 192.216.136 Network Name: BARRNET-216-136 Location: BARRNet, c/o Stanford University, Pine Hall 115, Stanford, CA 94305-4122, USA Country Code: US 1:200 BARRNet 2:201 BARRNet Network IP: 192.239.27 Network Name: GIT-SUB12 Location: Georgia Institute of Technology, Office of Computing Services, 258 4th Street, Rich Building, Atlanta, GA 30332, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Network IP: 192.239.28 Network Name: GIT-SUB13 Location: Georgia Institute of Technology, Office of Computing Services, 258 4th Street, Rich Building, Atlanta, GA 30332, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Network IP: 192.239.50 Network Name: FIS-NET Location: Indiana University, c/o American Management Systems, 4050 Legato Road, Network Computer Center, Fairfax, VA 22033, USA Country Code: US 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) Network IP: 193.60.224 Network Name: BCC-ACUK-1 Location: Birkbeck College Geology Department, Malet Street, London, UNITED KINGDOM Country Code: GB 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) Network IP: 193.72.218 Network Name: MICRO-FRAME-C1 Location: ANS-CIX Country Code: CH 1:1957 ANSCIX-AS Network IP: 193.174.253 Network Name: RD-VARTA Location: Varta Batterie AG, TZ 3, Gundelhardtstr. 72, D-W-6233 Kelkheim, GERMANY Country Code: DE 1:293 Energy Science Network (FIX-East) 2:291 Energy Science Network (FIX-West) Network IP: 193.196.1 Network Name: PSYRES-STGT1 Location: Forschungsstelle fuer Psychotherapie, Christian-Belser-Str. 79, D-W-7000 Stuttgart 70, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.2 Network Name: FH-BIBERACH1 Location: Fachhochschule Biberach, Karlstr. 9-11, D-W-7950 Biberach, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.3 Network Name: FH-BIBERACH2 Location: Fachhochschule Biberach, Karlstr. 9-11, D-W-7950 Biberach, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.4 Network Name: BA-LOERRACH Location: Berufsakademie Loerrach, BelWue, Hangstr. 48, D-W-7850 Loerrach, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.8 Network Name: IDS-MANNHEIM Location: Institut fuer Deutsche Sprache Mannheim, BelWue, R 5 6-13, D-W-6800 Mannheim 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.10 Network Name: ZUMANET Location: Zentrum fuer Umfragen, Methoden und Analysen (ZUMA), Mannheim, Postfach 122155, D-W-6800 Mannheim 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.16 Network Name: TUENET-C16 Location: University of Tuebingen, BelWue, Auf der Morgenstelle 10, D-7400 Tuebingen, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.17 Network Name: TUENET-C17 Location: University of Tuebingen, BelWue, Auf der Morgenstelle 10, D-7400 Tuebingen, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.18 Network Name: TUENET-C18 Location: University of Tuebingen, BelWue, Auf der Morgenstelle 10, D-7400 Tuebingen, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.19 Network Name: TUENET-C19 Location: University of Tuebingen, BelWue, Auf der Morgenstelle 10, D-7400 Tuebingen, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.20 Network Name: TUENET-C20 Location: University of Tuebingen, BelWue, Auf der Morgenstelle 10, D-7400 Tuebingen, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.21 Network Name: TUENET-C21 Location: University of Tuebingen, BelWue, Auf der Morgenstelle 10, D-7400 Tuebingen, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.22 Network Name: TUENET-C22 Location: University of Tuebingen, BelWue, Auf der Morgenstelle 10, D-7400 Tuebingen, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.23 Network Name: TUENET-C23 Location: University of Tuebingen, BelWue, Auf der Morgenstelle 10, D-7400 Tuebingen, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.24 Network Name: TUENET-C24 Location: University of Tuebingen, BelWue, Auf der Morgenstelle 10, D-7400 Tuebingen, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.25 Network Name: TUENET-C25 Location: University of Tuebingen, BelWue, Auf der Morgenstelle 10, D-7400 Tuebingen, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.26 Network Name: TUENET-C26 Location: University of Tuebingen, BelWue, Auf der Morgenstelle 10, D-7400 Tuebingen, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.27 Network Name: TUENET-C27 Location: University of Tuebingen, BelWue, Auf der Morgenstelle 10, D-7400 Tuebingen, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.28 Network Name: TUENET-C28 Location: University of Tuebingen, BelWue, Auf der Morgenstelle 10, D-7400 Tuebingen, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.29 Network Name: TUENET-C29 Location: University of Tuebingen, BelWue, Auf der Morgenstelle 10, D-7400 Tuebingen, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.30 Network Name: TUENET-C30 Location: University of Tuebingen, BelWue, Auf der Morgenstelle 10, D-7400 Tuebingen, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.31 Network Name: TUENET-C31 Location: University of Tuebingen, BelWue, Auf der Morgenstelle 10, D-7400 Tuebingen, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.32 Network Name: KLICK-C32 Location: Karlsruher Lichtleiter Kommunikationsnetz, University of Karlsruhe, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.33 Network Name: KLICK-C33 Location: Karlsruher Lichtleiter Kommunikationsnetz, University of Karlsruhe, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.34 Network Name: KLICK-C34 Location: Karlsruher Lichtleiter Kommunikationsnetz, University of Karlsruhe, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.35 Network Name: KLICK-C35 Location: Karlsruher Lichtleiter Kommunikationsnetz, University of Karlsruhe, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.36 Network Name: KLICK-C36 Location: Karlsruher Lichtleiter Kommunikationsnetz, University of Karlsruhe, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.37 Network Name: KLICK-C37 Location: Karlsruher Lichtleiter Kommunikationsnetz, University of Karlsruhe, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.38 Network Name: KLICK-C38 Location: Karlsruher Lichtleiter Kommunikationsnetz, University of Karlsruhe, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.39 Network Name: KLICK-C39 Location: Karlsruher Lichtleiter Kommunikationsnetz, University of Karlsruhe, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.40 Network Name: KLICK-C40 Location: Karlsruher Lichtleiter Kommunikationsnetz, University of Karlsruhe, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.41 Network Name: KLICK-C41 Location: Karlsruher Lichtleiter Kommunikationsnetz, University of Karlsruhe, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.42 Network Name: KLICK-C42 Location: Karlsruher Lichtleiter Kommunikationsnetz, University of Karlsruhe, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.43 Network Name: KLICK-C43 Location: Karlsruher Lichtleiter Kommunikationsnetz, University of Karlsruhe, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.44 Network Name: KLICK-C44 Location: Karlsruher Lichtleiter Kommunikationsnetz, University of Karlsruhe, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.45 Network Name: KLICK-C45 Location: Karlsruher Lichtleiter Kommunikationsnetz, University of Karlsruhe, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.46 Network Name: KLICK-C46 Location: Karlsruher Lichtleiter Kommunikationsnetz, University of Karlsruhe, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.47 Network Name: KLICK-C47 Location: Karlsruher Lichtleiter Kommunikationsnetz, University of Karlsruhe, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.48 Network Name: KLICK-C48 Location: Karlsruher Lichtleiter Kommunikationsnetz, University of Karlsruhe, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.49 Network Name: KLICK-C49 Location: Karlsruher Lichtleiter Kommunikationsnetz, University of Karlsruhe, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.50 Network Name: KLICK-C50 Location: Karlsruher Lichtleiter Kommunikationsnetz, University of Karlsruhe, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.51 Network Name: KLICK-C51 Location: Karlsruher Lichtleiter Kommunikationsnetz, University of Karlsruhe, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.52 Network Name: KLICK-C52 Location: Karlsruher Lichtleiter Kommunikationsnetz, University of Karlsruhe, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.53 Network Name: KLICK-C53 Location: Karlsruher Lichtleiter Kommunikationsnetz, University of Karlsruhe, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.54 Network Name: KLICK-C54 Location: Karlsruher Lichtleiter Kommunikationsnetz, University of Karlsruhe, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.55 Network Name: KLICK-C55 Location: Karlsruher Lichtleiter Kommunikationsnetz, University of Karlsruhe, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.56 Network Name: KLICK-C56 Location: Karlsruher Lichtleiter Kommunikationsnetz, University of Karlsruhe, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.57 Network Name: KLICK-C57 Location: Karlsruher Lichtleiter Kommunikationsnetz, University of Karlsruhe, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.58 Network Name: KLICK-C58 Location: Karlsruher Lichtleiter Kommunikationsnetz, University of Karlsruhe, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.59 Network Name: KLICK-C59 Location: Karlsruher Lichtleiter Kommunikationsnetz, University of Karlsruhe, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.60 Network Name: KLICK-C60 Location: Karlsruher Lichtleiter Kommunikationsnetz, University of Karlsruhe, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.61 Network Name: KLICK-C61 Location: Karlsruher Lichtleiter Kommunikationsnetz, University of Karlsruhe, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.62 Network Name: KLICK-C62 Location: Karlsruher Lichtleiter Kommunikationsnetz, University of Karlsruhe, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.63 Network Name: KLICK-C63 Location: Karlsruher Lichtleiter Kommunikationsnetz, University of Karlsruhe, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.64 Network Name: FH-KARL-C64 Location: Fachhochschule Karlsruhe, Moltkestr. 4, D-W-7500 Karlsruhe, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.65 Network Name: FH-KARL-C65 Location: Fachhochschule Karlsruhe, Moltkestr. 4, D-W-7500 Karlsruhe, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.128 Network Name: PH-LUDWIG1 Location: Paedagogische Hochschule Ludwigsburg, BelWue, Reuteallee 46, D-W-7140 Ludwigsburg, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.129 Network Name: PH-LUDWIG2 Location: Paedagogische Hochschule Ludwigsburg, BelWue, Reuteallee 46, D-W-7140 Ludwigsburg, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.130 Network Name: FHB-STGT-NEU Location: Fachhochschule fuer Bibliothekswesen Stuttgart, Wolframstr. 32, D-W-7000 Stuttgart 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.136 Network Name: FHT-STGT-NEU136 Location: FHT Stuttgart - Fachhochschule fuer Technik Stuttgart, Rechenzentrum, Schloss Strasse 26, D-W-7000 Stuttgart 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.137 Network Name: FHT-STGT-NEU137 Location: FHT Stuttgart - Fachhochschule fuer Technik Stuttgart, Rechenzentrum, Schloss Strasse 26, D-W-7000 Stuttgart 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.138 Network Name: FHT-STGT-NEU138 Location: FHT Stuttgart - Fachhochschule fuer Technik Stuttgart, Rechenzentrum, Schloss Strasse 26, D-W-7000 Stuttgart 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.139 Network Name: FHT-STGT-NEU139 Location: FHT Stuttgart - Fachhochschule fuer Technik Stuttgart, Rechenzentrum, Schloss Strasse 26, D-W-7000 Stuttgart 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.140 Network Name: FHT-STGT-NEU140 Location: FHT Stuttgart - Fachhochschule fuer Technik Stuttgart, Rechenzentrum, Schloss Strasse 26, D-W-7000 Stuttgart 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.141 Network Name: FHT-STGT-NEU141 Location: FHT Stuttgart - Fachhochschule fuer Technik Stuttgart, Rechenzentrum, Schloss Strasse 26, D-W-7000 Stuttgart 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.142 Network Name: FHT-STGT-NEU142 Location: FHT Stuttgart - Fachhochschule fuer Technik Stuttgart, Rechenzentrum, Schloss Strasse 26, D-W-7000 Stuttgart 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 193.196.143 Network Name: FHT-STGT-NEU143 Location: FHT Stuttgart - Fachhochschule fuer Technik Stuttgart, Rechenzentrum, Schloss Strasse 26, D-W-7000 Stuttgart 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 198.17.175 Network Name: OSHA-SLC-NET Location: U.S. Dept Of Labor OSHA - Salt Lake City, P.O. Box 65200, Salt Lake City, UT 84115, USA Country Code: US 1:210 Westnet Regional Network (Utah Attachment) - ENSS 142 2:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 Network IP: 198.22.17 Network Name: CALIPER Location: Caliper Corporation, 1172 Beacon Street, Newton, MA 02161, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network Network IP: 198.29.253 Network Name: CECO126 Location: Commonwealth Edison Company, 72 W. Adams, Chicago, IL 60603, USA Country Code: US 1:267 CICNET at UIUC 2:1225 CICNET at Argonne Labs 3:266 CICNET at MERIT Network IP: 198.37.32 Network Name: RASTEROPS1 Location: RasterOps Corporation, 2500 Walsh Avenue, Santa Clara, CA 95051, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 198.37.33 Network Name: RASTEROPS2 Location: RasterOps Corporation, 2500 Walsh Avenue, Santa Clara, CA 95051, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 198.37.34 Network Name: RASTEROPS3 Location: RasterOps Corporation, 2500 Walsh Avenue, Santa Clara, CA 95051, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 198.37.35 Network Name: RASTEROPS4 Location: RasterOps Corporation, 2500 Walsh Avenue, Santa Clara, CA 95051, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 198.37.36 Network Name: RASTEROPS5 Location: RasterOps Corporation, 2500 Walsh Avenue, Santa Clara, CA 95051, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 198.37.37 Network Name: RASTEROPS6 Location: RasterOps Corporation, 2500 Walsh Avenue, Santa Clara, CA 95051, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 198.37.38 Network Name: RASTEROPS7 Location: RasterOps Corporation, 2500 Walsh Avenue, Santa Clara, CA 95051, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 198.37.39 Network Name: RASTEROPS8 Location: RasterOps Corporation, 2500 Walsh Avenue, Santa Clara, CA 95051, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 198.37.40 Network Name: RASTEROPS9 Location: RasterOps Corporation, 2500 Walsh Avenue, Santa Clara, CA 95051, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 198.37.41 Network Name: RASTEROPS10 Location: RasterOps Corporation, 2500 Walsh Avenue, Santa Clara, CA 95051, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 198.37.42 Network Name: RASTEROPS11 Location: RasterOps Corporation, 2500 Walsh Avenue, Santa Clara, CA 95051, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 198.37.43 Network Name: RASTEROPS12 Location: RasterOps Corporation, 2500 Walsh Avenue, Santa Clara, CA 95051, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 198.37.44 Network Name: RASTEROPS13 Location: RasterOps Corporation, 2500 Walsh Avenue, Santa Clara, CA 95051, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 198.37.45 Network Name: RASTEROPS14 Location: RasterOps Corporation, 2500 Walsh Avenue, Santa Clara, CA 95051, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 198.37.46 Network Name: RASTEROPS15 Location: RasterOps Corporation, 2500 Walsh Avenue, Santa Clara, CA 95051, USA Country Code: US 1:701 Alternet 2:702 Alternet Network IP: 198.37.128 Network Name: NETSERV1 Location: NetServices, 3859 De La Cruz Blvd., Santa Clara, CA 95054, USA Country Code: US 1:1740 CERFnet Network IP: 198.49.96 Network Name: SOFTSOLUT-NET Location: 100 Percent Software Solutions, 24 Golden Eagle Lane, Littleton, CO 80127, USA Country Code: US 1:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 2:210 Westnet Regional Network (Utah Attachment) - ENSS 142 Network IP: 198.49.246 Network Name: NICHOLS-NET Location: Nichols Research Corporation, 5575 Tech Center Drive, Suite 304, Colorado Springs, CO 80919, USA Country Code: US 1:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 2:210 Westnet Regional Network (Utah Attachment) - ENSS 142 Network IP: 198.52.32 Network Name: UUNORTH-NET32 Location: UUNorth Incorporated, 3555 Don Mills Road, Suite 6-304, Willowdale, Ontario, M2H 3N3, CANADA Country Code: CA 1:2493 FONOROLA-EAST Network IP: 198.62.158 Network Name: IDRC-1 Location: Fonorola, 250 Albert Street, Suite 205, Ottawa, Ontario, K1P-6M1, CANADA Country Code: CA 1:2493 FONOROLA-EAST Network IP: 198.62.159 Network Name: IDRC-2 Location: Fonorola, 250 Albert Street, Suite 205, Ottawa, Ontario, K1P-6M1, CANADA Country Code: CA 1:2493 FONOROLA-EAST Network IP: 198.67.16 Network Name: FALCONBLK1 Location: Falcon Microsystems, 1100 Mercantile Lane, Landover, MD 2078, USA Country Code: US 1:1800 ICM-Atlantic 2:1240 ICM-Pacific Network IP: 198.67.17 Network Name: FALCONBLK2 Location: Falcon Microsystems, 1100 Mercantile Lane, Landover, MD 2078, USA Country Code: US 1:1800 ICM-Atlantic 2:1240 ICM-Pacific Network IP: 198.67.18 Network Name: FALCONBLK3 Location: Falcon Microsystems, 1100 Mercantile Lane, Landover, MD 2078, USA Country Code: US 1:1800 ICM-Atlantic 2:1240 ICM-Pacific Network IP: 198.67.19 Network Name: FALCONBLK4 Location: Falcon Microsystems, 1100 Mercantile Lane, Landover, MD 2078, USA Country Code: US 1:1800 ICM-Atlantic 2:1240 ICM-Pacific The following Midlevel/Regional peering sessions have also been added: AS Number: 114 AS Notes: SESQUINET Regional Network AS Country Code: US BkBn: 690 NSS: 140.222.139 - Rice University Houston, TX Gate: 192.67.13.81 - rice1 Rice University, Houston, TX Gate: 192.67.13.88 - rice4 Rice University, Houston, TX AS Number: 280 AS Notes: SESQUINET Regional Network AS Country Code: US BkBn: 690 NSS: 140.222.139 - Rice University Houston, TX Gate: 192.67.13.83 - rice2 Rice University, Houston, TX AS Number: 1700 AS Notes: SESQUINET Regional Network AS Country Code: US BkBn: 690 NSS: 140.222.139 - Rice University Houston, TX Gate: 192.67.13.86 - rice3.sesqui.net ENSS 139 - Rice University AS Number: 1757 AS Notes: Mead Data Central AS Country Code: US BkBn: 690 NSS: 140.222.226 - Mead Data Central, Miamisburg, Ohio - ENSS 226 Miamisburg, Ohio, USA Gate: 192.73.216.3 - peer.meaddata.com Mead Data Central, Miamisburg, OH AS Number: 2538 AS Notes: IBM-KINGS-AS AS Country Code: US BkBn: 690 NSS: 140.222.224 - IBM Kingston -- ENSS 224 Hartford, CT, USA Gate: 129.40.10.201 - Router Internet Name unknown IBM Kingston -- ENSS 224, Hartford, CT, USA ***************************************************************** The configuration reports which reflect today's update will be available for anonymous ftp on nis.nsf.net by 08:00 EST: configuration reports -- nis.nsf.net:nsfnet/announced.networks: ans_core.now as-as.now as-gw.now as-site.now as.now country.now gate-gw.now net-comp.now net-ter.now net-net.now netcount.now non-us.now nss-as.now nss-gw.now nss.now networks sorted by AS -- nis.nsf.net:nsfnet/announced.networks: nets.as_<AS number> NSS routing software configuration files -- nis.nsf.net:nsfnet/backbone.configuration: nss<NSS number>.t3p Please send all requests for configuration changes to nsfnet-admin(a)merit.edu using the NSFNET configuration forms. The forms are available on-line from the nis.nsf.net 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.gate, and template.as. ******************************* --Steve Widmayer Merit/NSFNET skw(a)merit.edu --Riaz Taherzadeh-Yazdian NSFNET/ANSNET rty(a)ans.net

1 0

Phone access to the ANS NOC
by John Labbe 12 Mar '93

12 Mar '93

>From sometime mid-morning 3/11/93 until a few minutes ago there were problems reaching the NOC number, 313-763-3448, due to IXC routing problems. These problems also affected 800-9NSFNOC, which forwards to it, until mid-afternoon when the 800 number was rerouted. John Labbe ANS NOC

1 0

please subscribe
by acharya＠watson.ibm.com 11 Mar '93

11 Mar '93

please subscribe thanks - Madhu K. Acharya

1 0

Phone access to the ANS NOC
by John Labbe 11 Mar '93

11 Mar '93

There are apparently some trunking problems which are affecting calls to the NOC's direct access number and the NSF 800 number. (313-763-3448 and 800-9NSFNOC) Please use 800-456-6300 which appears to be unaffected or email trouble(a)noc.ans.net. John Labbe ANS NOC

1 0

Conservation
by Mark Knopper 11 Mar '93

11 Mar '93

Silent Nets, CIDR, and Conservation of Routing Table Space Mark Knopper March 10, 1993 Merit has started a project to analyze the NSFNET Policy Routing Database (PRDB) to look for networks that are not being announced to the backbone. Enke Chen of Merit has been sending each regional or midlevel (AS administrator actually) a list of the "silent nets" for their autonomous system. Our goal is to prune out of the database any networks not being used and not expected to be used in the near future. This is important for a couple of reasons: 1) we are approaching a hard limit in the table size in the ANS backbone routers; and 2) storing information for the non-announced networks requires human resources and some router space resources since all of the configured nets are stored in the configuration file on each router. As of March 5, there are 10057 networks configured in the database. The number of silent nets for February was 1955, ie. 1955 networks which were in the database as of February 1 were never announced in the entire month. So far we have received requests to delete about 200 of the silent nets. The maximum number of nets that were announced to the backbone as of 2/28 was 7037. Historical growth in network announcements is summarized in the following table. MONTH MAX RATE(%) ===== ==== ====== 07/92 4596 08/92 4866 5.9 09/92 5070 4.2 10/92 5432 7.1 11/92 5772 6.3 12/92 6239 8.1 01/93 6654 6.7 02/93 7037 5.8 (Avg monthly growth rate: 6.3%) The interface forwarding tables on the ANSnet routers are currently configured to support 10000 destinations. In the near term, microcode changes will be deployed to support improved address compression in the forwarding tables which will support 12000 destinations. Later the gated software when deployed will support a number of enhancements that increase the forwarding table capacity. When Classless Inter-Domain Routing (CIDR) and Supernetting is available (target is June, 1993), regional and midlevel peer routers will begin announcing aggregated routing information to the backbone. The backbone will be configured to receive and redistribute aggregated routes to other networks that support the BGP-4 protocol. This will be possible since regionals/midlevels have been allocating network numbers to members and customers from contiguous blocks of network numbers allocated by the NIC. It is expected that this plan will significantly curtail the growth of routing table size for networks carrying full routing information. In the interim before aggregation can occur, we as regionals, midlevels and backbone operators must cooperate to conserve routing table size. We propose the following steps to help manage the problem, and would appreciate your feedback on them. Regional/Midlevels' Responsibilities: 1) Reply to the "silent nets" lists from Enke Chen and indicate your intent to delete any nets that are not planned to be announced in the next 30 days. 2) Send in delete requests to nsfnet-admin(a)merit.edu using the standard template.net. 3) Make sure you are using a CIDR block of class C net numbers obtained from the NIC for allocation to your member networks. Only send in requests for addition to the NSFNET database for those nets which will actually be used within 30 days. Merit's Responsibilities: 1) Merit will announce our intent to temporarily delete network numbers from the configuration files that have not been announced for 90 days. We will retain the nets in the database but will mark them as "inactive" and will not include them in the router configuration files. We will re-activate them at such time as the backbone routing table size limitation is resolved. We will also re-activate individual nets upon request. 2) If it would be convenient, Merit could set up a holding database so that network numbers can be submitted which would not actually be included in the router configuration files. The holding database could include all of the regular administrative and routing information associated with the network. Additional requests could be sent to Merit to have a network moved from holding status to active.

1 0

NSFNET Traffic Distribution Highlights
by Susan Horvath 10 Mar '93

10 Mar '93

NSFNET Traffic Distribution Highlights February 1993 Packet Total: 30,006,999,150 Byte Total: 5,437,317,967,750 Service Name Port Rank Packet Count % Pkts Rank Byte Count % Byts ============ ==== ==== ============ ====== ==== ============= ====== ftp-data 20 1 7115687250 23.713 1 2514638790500 46.248 telnet 23 2 4766186200 15.884 4 322953829050 5.940 nntp 119 3 2580606700 8.600 2 541514466350 9.959 smtp 25 4 2138597700 7.127 3 351940605500 6.473 domain 53 5 1616739000 5.388 5 145411803750 2.674 ftp 21 6 609081250 2.030 9 53725828050 0.988 irc 6667 7 601829250 2.006 8 55562910400 1.022 icmp -1 8 562605400 1.875 10 49872298650 0.917 vmnet 175 9 408769650 1.362 6 144729610150 2.662 gopher 70 10 256061750 0.853 7 60897391700 1.120 X0 6000 11 228771100 0.762 11 40003337350 0.736 login/who 513 12 195784900 0.652 13 19020881100 0.350 (unknown) 1023 13 164069000 0.547 14 17996807450 0.331 talk 517 14 159947200 0.533 15 16425401050 0.302 finger 79 15 144621300 0.482 19 13534490000 0.249 snmp 161 16 141282350 0.471 16 16166783150 0.297 ntp 123 17 114501900 0.382 22 8720814550 0.160 (unknown) 1022 18 85080150 0.284 17 15199132250 0.280 cmd/syslog 514 19 72135250 0.240 12 22025055400 0.405 uucp 540 20 54686850 0.182 20 10303646050 0.189 (unknown) 1021 21 45599150 0.152 21 8774225550 0.161 efs/router 520 22 44598000 0.149 18 14150743750 0.260 ntalk 518 23 43542850 0.145 29 4652704100 0.086 (unknown) 1020 24 32170700 0.107 24 7605114200 0.140 (unknown) 76 25 24301650 0.081 26 5919793000 0.109 (unknown) 700 26 22256250 0.074 25 5942729800 0.109 bgp 179 27 21648350 0.072 45 1270457000 0.023 (unknown) 703 28 18679650 0.062 27 5609950550 0.103 z39.50 210 29 16575600 0.055 30 4591203100 0.084 (unknown) 1019 30 15661300 0.052 35 2880455250 0.053 X1 6001 58 2969200 0.010 62 502135550 0.009 shilp/sun-nfs 2049 70 2047150 0.007 69 378441900 0.007 www 80 72 1969900 0.007 61 511666150 0.009 iso-ip -80 86 1203650 0.004 60 566187350 0.010 X2 6002 223 146050 0.000 309 15443300 0.000 X3 6003 470 47150 0.000 432 8786800 0.000 prospero 191 680 14250 0.000 389 9921450 0.000 Ordered by decreasing packet counts, this table includes the top 30 services and highlights other selected services. Information for this report is available only for TCP/UDP port numbers 0-1023, 2049, 6000-6003, 6667, and all Internet Protocols (differentiated from TCP/UDP ports by negating the protocol number). More detailed information is available for Anonymous FTP from NIC.MERIT.EDU (the Merit NIC Services machine) in the file "nsf-9302.ports" on the nsfnet/statistics/1993 directory.

1 0

Summary of Boulder Regional-Techs Meeting
by mak 10 Mar '93

10 Mar '93

Summary of NSFNET Regional-Techs Meeting, January 21-22, 1993 in Boulder, Colorado Merit sponsored a meeting of the NSFNET Regional-Techs in Boulder, Colorado during January 21-22, 1993. The meeting was generously hosted by Roy Perry of US West. FARNET met simultaneously in Denver. The attendance list for the meeting is appended. Most of the regionals and midlevels were represented, along with commercial network service providers, router vendors, government agency network providers and NSF. The purpose of this meeting was to allow the regional-techs to get together and have a focused discussion about networking plans. The Internet is evolving and direct action by the network operators and router vendors needs to take place in the near term (6-8 months) in order to provide a network architecture that allows for expected growth rates. Last November, The Internet Engineering Task Force discussions indicated that the NSFNET Backbone Service and regional networks move quickly to implementing an architecture called "Classless Inter-Domain Routing" (CIDR). This architecture suggests changes to the nature of the routing protocols and interactions between routing domains (eg. each regional is its own routing doman). The changes include moving to a new version of the Border Gateway Protocol which supports the grouping or aggregation of routing information when it is stored in routers and conveyed as protocol information between routing domains. The Merit staff nominated a person to lead each session covering the agenda items listed below, and "packed" the audience with friendly experts on the respective topics. Topics Covered in the Meeting 1.) GIX, NAPs, Route Servers Elise Gerich (Merit), discussion leader The NAP concept is not totally new. Any time you have multiple organizations homed on a shared medium, it might be considered a NAP. As more and more organizations interconnect it has become more necessary to better plan these interconnections and therefore, several pilots have emerged to test the functions needed at a NAP. Alternet, PSI, and Sprint initiated the MAE-East experiment which could be considered a distributed NAP. RIPE and Merit have both experimented with the concept of a route server. The purpose of the session was to discover what the regional technical representatives felt a route server should do and how it would compliment the system. Notes from Elise's talk: Introduction: What is a route server? How does it play in the NAP? How to test if it works? Goals: Maximal Connectivity Stable, Consistent Routing Manageable Routing NAPS: immature NAPs eg. cornell implementation (not planned) adolesent NAPs eg. fix-east (planned) coming of age of NAPs - mae-east RS design goals 2 proposed models: 1. single RS with world wide routing information or: 2. multiple RSs each with Regional (continental) routing information Ripe is doing #2, MERIT is working on #1. General feeling was that a merged form might be best, use the DNS model. The RS is actually two part, a policy engine and a route engine. GIX: looks & smells like a NAP, doesn't taste like one. has a worldwide flavor Questions: scope of policy - management visability move lvl2 to national cloud need route&policy filters where is the policy description language? need to distribute for disaster recovery. timing concerns. how to communicate changes to remote RS 2.) Implementation of CIDR and Supernetting Vince Fuller (BARRnet), discussion leader CIDR is billed as a short term solution, and to get started there are immediate operational actions needed. To quote V. Fuller, J. Yu, T. Li and K. Varadhan in RFC 1338, what is needed are "strategies for address assignment of the existing IP address space with a view to conserve the address space and stem the explosive growth of routing tables in default-route-free routers run by transit routing domain providers." The discussion included: how to phase in route aggregation, how to configure routing policy for aggregation, how aggregation will be used, test plans for the BGP-4 protocol, and the requirement for network renumbering. Jeff Honig of the Cornell "gated" group led a discussion about changes to the gateway daemon in support of CIDR. This was important since the ANS backbone will be using the gated program for its routing support. Notable results of discussion at this session included agreements that the regionals should cooperate to implement CIDR in multiple phases, with BGP-4 and route aggregation to be targeted for June, 1993. An Internet Draft should be written on deployment of CIDR in the NSFNET backbone and the regional networks. Configuration options will allow the backbone to accept route aggregates from regional networks, and then announce those aggregates to other regionals and midlevels. Vince's slides: Thoughts on CIDR in the NSFNET Regionals Address assignments in preparation for CIDR Obtaining a block of class-Cs from the NIC Assignment within the regional Multiply-connected regionals Backbone/regional responsibilities for aggregation policy Who maintains the policy configuration? Which peer implements aggregation? Configuring NSFNET to support aggregation How should routing policy be specified and conveyed between regionals and Merit/NSFNET? How should the current routing configuration process be modified to support aggregation configuration? what will gated support (Jeff H.) How should inter-domain routing protocols (ie. EGP BGP 1-3, BGP 4, and later IDRP) be used in the CIDR environment? ("CIDR, default, or die") IGP considerations - VLSM + Class A/B/C Impact of CIDR on mixed-use net (i.e. AUP) Multiple Supernet blocks for policies? 3.) Address allocation strategies with CIDR Dan Long (NEARnet), discussion leader This session covered the address administration aspects of CIDR. Regionals should be prepared to handle configuration of address blocks, and to do this there should be good communication between the network operators and those handing out the network numbers. The Regional-techs discussed methods of obtaining, handling and assigning network numbers to their members from blocks obtained from the NIC. Regionals and midlevels are advised to utilize CIDR address allocation in order to conserve routing table space in the Internet. Dan's slides: Dan Long Class C Allocation Rules Organizations should get contiguous blocks of C's based on the number of hosts: Hosts C's <256 1 <512 2 <1024 4 <2048 8 <4096 16 (<8192 32) upon request Organization should get contiguous blocks of C's based on the number of subnets: >1 C per subnet to max of 32 Subnetting C's is not required but is permitted, of course. ------------------------------------------------------------------------ Address Allocation Strategies with CIDR Goals: (Conflicting) Limit use of B:s Maximize aggregation (CIDR/Supernetting) Limit explosion of C's before CIDR is ready Don't break Lans or Land admins -------------------------------------------------------------------------- Status of A's 77 unassigned -64 Reserved -13 available IANA only Status of B's *9000 unassigned IANA says IR may allocate small blocks to regional (e.g. NIC) registries ------------------------------------------------------------------------ Status of C's *2,053,000 unassigned - 1,048,000 reserved - 1,005,000 available split into 8 blocks: 192 + 193 Pre-existing 194 + 195 Europe 196 + 197 Others 198 + 199 North America 200 + 201 Central + South America 202 + 203 Pacific Rim 204 + 205 Other 206 + 207 Other n-year blocks allocated to providers for customer use ------------------------------------------------------------------------ Class B Allocation Rules organizations with > 32 subnets or organizations with > 4096 hosts or organizations with a bridged LAN with stupid hosts 1. 1-->2 (ARP) 2. 2-->1 (via 3) ------------------------------------------------------------------------ Examples Company with 25 subnets Conglomerate with 35 subsidiaries and 100 LANs per subsidiary State with 400 K-12 school districts with 10 schools per district + 2 LANs per school Others? Questions Where's the best dividing line between B's + C's? Now? Later? How do regional registries + NSP's decide which addresses to assign out of a block of C's? Others? 4.) Transition to "Next Generation NSFNET" Dan Jordt (NorthWestNet), discussion leader Major transitions of internet operations need quite a lot of planning in order to happen smoothly. If nothing else, Merit has learned this over the last few years:-). Though it is too soon to know who the new players will be for the NSFNET vBNS, RA and NAP providers, enough is known to project some of the potential problem areas, forecast changes that may occur as a result of the new architecture, and suggest some preparations that can be made in advance. During this meeting, Peter Ford of the NSF Network Engineering Group presented an overview of NSF's latest thoughts about the upcoming solicitation for the follow-on NSFNET architecture. Dan Jordt Transition to the Next Generation NSFNET by Dan Jordt Director, Technical Services NorthWestNet MERIT's Annual Regional Techs Meeting Boulder, Colorado Thursday, January 21, 1993 -------------------------------------------------------------------------- Transition to the Next Generation NSFNET Review of NSF's Public Draft Program Solicitation Review of FARNET's Report What we know about the final solicitation What can we (the regionals techs) do to prepare for the transition Discussion ------------------------------------------------------------------------------ Review of NSF's Public Draft Program solicitation Division of Responsibilities Very high speed Backbone Network Services provider (vBNS) Network Access {point (NAP) manager Routing Authority (RA) Two separate awards (NAP?RA and vBNS) Funding: approximately $10M per year Timing: 5 year cooperative agreements to commence April 1994 ---------------------------------------------------------------------------- Very High Speed Backbone Network Services Provider (vBNS) must: Connect NAPs at 155 Mbps or better Switch both IP and CLNP Implement both BGP and IDRP Support multicasting and video teleconferencing Establish quality service metrics for network performance evaluation Establish Procedures to work with NAP/RA and other network personnel to resolve problems Participate in development of advanced routing technologies (e.g. TOS routing) ---------------------------------------------------------------------------- Network Access points (NAPs) manager and routing Authority "A NAP is defined as a high speed network or switch to which a number of router can be connected for the purpose of traffic exchange and interoperation" The NAP Manager?RA must : Establish and maintain 100 Mbps (or better) LANs or MANs as AUP-Free NAPs Develop attachment policies, procedures, and fee schedules for connecting to NAPs Specify and ensure reliability and security standards Establish and maintain a Route Server supporting both IDRP and BGP, and switching both CLNP and IP Ensure routing stability and provide for simplified routing strategies (e.f. default routing) Establish procedures to work with vBNS Provider and other network personnel to resolve problems -------------------------------------------------------------------------- Networks attaching to a NAP must: Connect at T1 or better Switch both IP{ and CLNP Support both BGP and IDRP Support Video Teleconferencing Pay pro-rated cost of maintaining NAP and RA Subscribe to policies set by the RA The Federation of American Research Networks (FARNET) Report on the NAP Manager/RA and vBNS Provider Draft Solicitation >From the FARNET report: "The transition from the current architecture to the new one will be extremely complex. A comprehensive transition plan must be developed and managed to protect stability, and existing providers must be represented in the planning process." Consensus opinions and Recommendations 12. NSF should place the new solicitation more clearly within the NREN context. 2. The plans for governance and management of the new infrastructure, and the process for achieving them, should be stronger and more explicit. 3. Transition planning must begin early and must include the provider community the organizations and institutions that furnish network services today. 4. Separate the Routing Arbiter function from that of the NAP Manager. 5. Enforcement of "appropriate use: policies will continue to be an issue under the new plan. 6. NSF's leadership role in extending networking to all of research and education should be reaffirmed and continued. 7. Criteria for attachment to NAPs and to the vBNS are critical and should be described by NSF in the solicitation. ---------------------------------------------------------------------------- The FARNET Report (cont.) 8. We recommend the following priorities in setting evaluation criteria for the review of responses to the final solicitation. GOAL Priority Promotion of broad infrastructure Very High Interaction with community, including Very High technology transfe Continuity and stability of services High QOS* measurement, accountability High Advancement of technology High/Medium Commercialization Medium Cost-effectiveness Medium CLNP availability Medium Facilitation of new applications Medium Provision of video services Low/Medium 9. NAP parameters should be based on multiple dimensions and should not be set solely on the basis of cost, which is only one component of the total NSFNET system. 10. We strongly recommend that the following technical requirement be included in the solicitation. The vBNS should provide redundancy among NAPs using proven technology. NSF should require connecting current T3 network to NAPs as part of the transition. The vBNS provider should carry full routing information (given the limitations of route server technology). The vBNS provider should have a publicly available MIB. ---------------------------------------------------------------------------- What we know about the current solicitation. Final version of solicitation made public by late Feb 93 Proposals due 75 days later Four supercomputer sites to be connected by vBNS Some number of NAPs (<<20) to be connected to vBNS Expect new language to firm up a few items from the draft solicitation, but intent is not to prescribe solutions Instead, NSF left requirements general enough to incent creative responses. Upside: NSF gets wide variety of responses, maximizing probability of technology and policy breakthroughs. Downside: Planners (technical and policy) must evolve within the structure prescribed by the award Timing becomes an issue. -------------------------------------------------------------------------- Timeline Comparisons NIS Solicitation T1 to T3 transition Transition to next NSFNET (estimates) * Jan 91 - Test T3 network * * deployed * * * * April 91 -T3 carries 1st * *'production' level traffic * * * * * * * * * Feb 93 - solicitation * * made public * * * * * * May 93-proposals due * * June 93-review panel * * July 93-NSB approval May 92-proposals due * * * April 92-T3 carries 1/2 of* Sept 92-award made * all NSFNet traffic * public * * Nov 93-prototype * * deployed * * * * Jan 94-First production * * * * Jan 93-Announcement* of Nov 92-All networks * April 94-Transition award to ATT, et,al. use T3 complete? -------------------------------------------------------------------------- REGIONALS Regionals will be given some funds for connecting to a Network Service Provider (NSP) of their choice (process t.b.d.) or to a NAP Subsidy funds for connecting to the NSP or a NAP will decline to $0 by 1996. (e.g. 100% 1st yr, 60% 2nd yr,...). Can change network provider selection ---------------------------------------------------------------------------- What can we do to prepare for the transition? We must focus early on communicating any technical concerns to our management and NSF, specifically relating to open issues that are yet unresolved and may affect each of our network's: Operational viability How do I coordinate inter-regional diagnosis and repair of end -to-end connectivity problems: Will I have to deploy new trouble ticket system? What are the performance and availability requirements for NAP participation: How will they be measured and reported: Who specifies these criteria: Who reviews submissions for connection? If I connect to NAP, will I have to deploy my own equipment there: If so, will there be someone there to act as my agent for repair and maintenance? Engineering plans How many NAPs will there be: (Will there be on close to me?) How should our network attach? Via a BB provider? Directly to the NAPs? Should I build a redundant connection to the NAPsL To my BB provider: Am I able to meet minimum requirements to connect to the Naps? (IDRP, CLNP, video, operations coverage) Do I need to negotiate, deploy, and manage N2 routing relationships if I connect directly to a NAP? To what extent must I be prepared to enforce policy routing: What choices will the RA provide my network or our clients regarding policy routing? policy routing? -------------------------------------------------------------------------- What can we do to prepare ...(cont.) Technical budgets - Personnel: How much extra operational staff will I need? Engineering staff? - Capital: Will I have to purchase new (or updated) boder routers: New network management stations and/or trouble ticket systems? - Operations: What new on-going costs must I budget for to pay for any new circuits? To pay for pro-rated NAP/RA costs? How will these costs be determined? We will need to significantly increase our intercommunications among attaching mid-levels and BB service providers to facilitate - technical transition planning and engineering - operations coordination, diagnoses and repair of peer routing instabilities, trouble ticket passing - end -to-end connectivity problem resolution - diagnosis and repair of peer routing instabilities After the contract has been awarded, we must be prepared to immediately participate in deployment engineering and planning with all other players (vBNS, NAP, RA awardees, NSF, other mid-levels). --------------------------------------------------------------------------- The view from a few steps back... Representative Boucher (chair of the House subcommittee that oversees NSF) from a speech made to National Net 92 on March 25: "In developing the detailed plan for transition to the NREN, I think a few basic principles must be observed. First, the benefits of this network should flow to the nation broadly and not just to a narrow few. The developments of markets and the involvement of industry [...] is essential. {The} development of the technology and management of the NREN should push the limits necessary to stimulate and meet the demand for services while ensuring reliability and stability to the users. And finally, the many communities that participate in the development and use of the NREN must have a voice in planning for the network and for its long-term management." 5.) Virtual Routes Presenter: Bilal Chinoy (SDSC) Bilal presented a paper that was published in ACM CCR in 1992, on his analysis of routing traffic on the NSFNET backbone. His premise was that one can take advantage of destination locality in Internet traffic to design more compact forwarding tables. That is, one can keep the size of forwarding tables at about 20% of the total potential destinations and yet deal efficiently with all offered traffic. 5.) Current Status /Problems Mark Knopper (Merit), discussion leader This session covered the NSFNET network status, including recent events such as dismantling the T1 backbone, deployment of FDDI cards, current status and future plans. Discussion focused on the routing table size in the backbone routers operated by ANS, and how to manage this by phasing in the CIDR architecture. Mark's slides: Mark Knopper Current Status/Problems -Traffic Statistics -T3 Network Status -Upcoming changes on backbone -MBONE routing -Policy Routing Database Changes -Discussion -------------------------------------------------------------------- T3 Network Status -FDDI installations: Installed: NEARnet (ENSS 134) 12/8 Argonne (ENSS 130) 12/8 FIX-E (ENSS 145) 12/11 SESQUInet (ENSS 139) 12/22 Cornell (ENSS 133) 12/24 FIX-W (ENSS 144) 12/29 NWnet (ENSS 143) 12/29 Merit (ENSS 131) 1/8 Scheduled: WestNet (ENSS 142) 2/1 -Rcp_Routed and FDDI interAS metrics -10000 route capacity on RS/960 cards ------------------------------------------------------------------------ Upcoming Changes - Near Term (Feb-March) Internal route aggregation ("CIDR") Route caching AIX 3.2 Gated with BGP 3 -Medium Term (March-June) CLNP forwarding Dual IS-IS BGP 4 -Longer Term (July-September) IDRP ----------------------------------------------------------------------- IETF and MBONE connectivity -ANS testing T1 data compression devices -Alternatively second T1 will be installed at OARnet -MBONE: Recommend that all NSFNET Regionals support MBONE mrouted machine attached to DMZ, Distribute multicast from that machine to sites on campus and within regional. Obtain feed from another site with direct T3 backbone connectivity. ------------------------------------------------------------------------- Policy Routing Database Changes -New Informix/RS6000 database system almost ready(really). -Merit is working on automating the configuration process: -Parsable NACR -Shared Whois Project (SWIP) -"Config Ticket" system -Upcoming work -Policy specification -Route server configuration and further experiments ------------------------------------------------------------------------- Problems? -Backbone performance and reliability is good. -What has not gone well? -What else should Merit/ANS be working on now? Organizations represented at the meeting: CNRI, 3com, Wellfleet, IBM, MILnet, NIST, Sprint, US West, PSI, AlterNet, ESnet, ANS, SDSC, Merit, MichNet, WestNet, CICNet, LANL/NSF, BARRnet, NorthWestNet, Cornell, NEARnet, SESQUInet, NCAR, Los Nettos/ISI, NCSA, SURAnet, and MSC.

1 0

Additions to the NSFNET policy-based routing database
by Steven K. Widmayer 09 Mar '93

09 Mar '93

The following additions have been made to the NSFNET policy-based routing database and will be installed on the backbone by 08:00 EST: Total configured networks: 10057 IP address Net name Country Date Priority:AS ---------- -------- ------- ---- ----------- 138.116 EMPIRE-STATE C:US D:03/08/93 1:174 143.243 DGTLSYSINTL C:US D:03/08/93 1:174 144.254 144.254 C:US D:03/08/93 1:703 2:701 3:702 160.37 LCH-NET C:US D:03/08/93 1:279 2:86 162.50 OHIOEDASSN C:US D:03/08/93 1:600 192.139.7 PA-NET C:CA D:03/08/93 1:602 2:1391 3:603 12:601 13:1393 192.156.204 VISIDYNE C:US D:03/08/93 1:560 2:281 5:701 192.197.141 STU1 C:CA D:03/08/93 1:1391 2:602 3:603 11:601 13:1393 192.197.142 STU2 C:CA D:03/08/93 1:1391 2:602 3:603 11:601 13:1393 192.197.143 STU3 C:CA D:03/08/93 1:1391 2:602 3:603 11:601 13:1393 192.203.52 ASANTE-NET1 C:US D:03/08/93 1:200 2:201 3:1957 192.203.53 ASANTE-NET2 C:US D:03/08/93 1:200 2:201 3:1957 192.203.54 ASANTE-NET3 C:US D:03/08/93 1:200 2:201 3:1957 192.203.55 ASANTE-NET4 C:US D:03/08/93 1:200 2:201 3:1957 192.204.19 ANSP-2 C:US D:03/08/93 1:204 2:1206 192.216.48 BARRNET-216-48 C:US D:03/08/93 1:200 2:201 192.216.49 BARRNET-216-49 C:US D:03/08/93 1:200 2:201 192.216.50 BARRNET-216-50 C:US D:03/08/93 1:200 2:201 192.216.56 BARRNET-216-56 C:US D:03/08/93 1:200 2:201 192.216.57 BARRNET-216-57 C:US D:03/08/93 1:200 2:201 192.216.58 BARRNET-216-58 C:US D:03/08/93 1:200 2:201 192.216.59 BARRNET-216-59 C:US D:03/08/93 1:200 2:201 192.219.29 TGS-SYSTEMS C:CA D:03/08/93 1:603 2:1391 3:602 11:1393 12:601 192.220.236 NETBLK-NWNET-236 C:US D:03/08/93 1:685 2:73 3:101 192.220.237 NETBLK-NWNET-237 C:US D:03/08/93 1:685 2:73 3:101 192.220.238 NETBLK-NWNET-238 C:US D:03/08/93 1:685 2:73 3:101 192.220.239 NETBLK-NWNET-239 C:US D:03/08/93 1:685 2:73 3:101 192.233.12 MEIKO-PPP-NET C:US D:03/08/93 1:560 2:281 5:701 192.233.14 VISIDYNE-1 C:US D:03/08/93 1:560 2:281 5:701 198.22.249 FHSU C:US D:03/08/93 1:93 198.30.12 OAR12 C:US D:03/08/93 1:600 198.30.13 OAR13 C:US D:03/08/93 1:600 198.30.14 OAR14 C:US D:03/08/93 1:600 198.30.15 OAR15 C:US D:03/08/93 1:600 198.30.16 OAR16 C:US D:03/08/93 1:600 198.30.17 OAR17 C:US D:03/08/93 1:600 198.30.18 OAR18 C:US D:03/08/93 1:600 198.30.19 OAR19 C:US D:03/08/93 1:600 198.30.21 OAR21 C:US D:03/08/93 1:600 198.30.22 OAR22 C:US D:03/08/93 1:600 198.30.23 OAR23 C:US D:03/08/93 1:600 198.30.24 OAR24 C:US D:03/08/93 1:600 198.30.25 OAR25 C:US D:03/08/93 1:600 198.30.27 OAR27 C:US D:03/08/93 1:600 198.60.129 NETBLK-WESTNET-129 C:US D:03/08/93 1:210 2:209 202.6.90 CUACC C:TH D:03/08/93 1:701 2:702 Network IP: 138.116 Network Name: EMPIRE-STATE Location: Empire State College, 2 Union Avenue, Saratoga, NY 12866, USA Country Code: US 1:174 NYSERNet Regional Network / PSI Network IP: 143.243 Network Name: DGTLSYSINTL Location: Digital Systems International, Incorporated, 7730 177th Place NE, Redmond, WA 98073-0908, USA Country Code: US 1:174 NYSERNet Regional Network / PSI Network IP: 144.254 Network Name: 144.254 Location: cisco Systems, 1525 Obrien Drive, Menlo Park, CA 94025, USA Country Code: US 1:703 AlterNet-Interop 2:701 Alternet 3:702 Alternet Network IP: 160.37 Network Name: LCH-NET Location: University of Tennessee, 877 Madison Avenue, Suite 789, Memphis, TN 38163, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Network IP: 162.50 Network Name: OHIOEDASSN Location: Ohio Education Association, P.O. Box 2550, 225 East Broad Street, Columbus, OH 43216, USA Country Code: US 1:600 OARNET, Cleveland, OH Network IP: 192.139.7 Network Name: PA-NET Location: Sask#net, University of Saskatchewan, Saskatoon, Saskatchewan S7N 0W0, CANADA Country Code: CA 1:602 CA*net in Montreal 2:1391 CA*net in Toronto 3:603 CA*net in Quebec 12:601 CA*net in Toronto 13:1393 CA*net in Quebec Network IP: 192.156.204 Network Name: VISIDYNE Location: Visidyne, Inc., South Bedford Street, Burlington, MA 01803-5129, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network 5:701 Alternet Network IP: 192.197.141 Network Name: STU1 Location: NBneta (New Brunswick Regional Net), Computing Services, Room D-11, Head Hall, University of New Brunswick, Fredericton, New Brunswick H3A 2K3, CANADA Country Code: CA 1:1391 CA*net in Toronto 2:602 CA*net in Montreal 3:603 CA*net in Quebec 11:601 CA*net in Toronto 13:1393 CA*net in Quebec Network IP: 192.197.142 Network Name: STU2 Location: NBneta (New Brunswick Regional Net), Computing Services, Room D-11, Head Hall, University of New Brunswick, Fredericton, New Brunswick H3A 2K3, CANADA Country Code: CA 1:1391 CA*net in Toronto 2:602 CA*net in Montreal 3:603 CA*net in Quebec 11:601 CA*net in Toronto 13:1393 CA*net in Quebec Network IP: 192.197.143 Network Name: STU3 Location: NBneta (New Brunswick Regional Net), Computing Services, Room D-11, Head Hall, University of New Brunswick, Fredericton, New Brunswick H3A 2K3, CANADA Country Code: CA 1:1391 CA*net in Toronto 2:602 CA*net in Montreal 3:603 CA*net in Quebec 11:601 CA*net in Toronto 13:1393 CA*net in Quebec Network IP: 192.203.52 Network Name: ASANTE-NET1 Location: Asante Technologies, Inc., 404 Tasman Drive, Sunnyvale, CA 94089, USA Country Code: US 1:200 BARRNet 2:201 BARRNet 3:1957 ANSCIX-AS Network IP: 192.203.53 Network Name: ASANTE-NET2 Location: Asante Technologies, Inc., 404 Tasman Drive, Sunnyvale, CA 94089, USA Country Code: US 1:200 BARRNet 2:201 BARRNet 3:1957 ANSCIX-AS Network IP: 192.203.54 Network Name: ASANTE-NET3 Location: Asante Technologies, Inc., 404 Tasman Drive, Sunnyvale, CA 94089, USA Country Code: US 1:200 BARRNet 2:201 BARRNet 3:1957 ANSCIX-AS Network IP: 192.203.55 Network Name: ASANTE-NET4 Location: Asante Technologies, Inc., 404 Tasman Drive, Sunnyvale, CA 94089, USA Country Code: US 1:200 BARRNet 2:201 BARRNet 3:1957 ANSCIX-AS Network IP: 192.204.19 Network Name: ANSP-2 Location: Academy of Natural Sciences, 1900 Benjamin Franklin Parkway, Philadelphis, PA 19103-1089, USA Country Code: US 1:204 PSCNET Regional Network 2:1206 PSCNET Regional Network Network IP: 192.216.48 Network Name: BARRNET-216-48 Location: BARRNet, c/o Stanford University, Pine Hall 115, Stanford, CA 94305-4122, USA Country Code: US 1:200 BARRNet 2:201 BARRNet Network IP: 192.216.49 Network Name: BARRNET-216-49 Location: BARRNet, c/o Stanford University, Pine Hall 115, Stanford, CA 94305-4122, USA Country Code: US 1:200 BARRNet 2:201 BARRNet Network IP: 192.216.50 Network Name: BARRNET-216-50 Location: BARRNet, c/o Stanford University, Pine Hall 115, Stanford, CA 94305-4122, USA Country Code: US 1:200 BARRNet 2:201 BARRNet Network IP: 192.216.56 Network Name: BARRNET-216-56 Location: BARRNet, c/o Stanford University, Pine Hall 115, Stanford, CA 94305-4122, USA Country Code: US 1:200 BARRNet 2:201 BARRNet Network IP: 192.216.57 Network Name: BARRNET-216-57 Location: BARRNet, c/o Stanford University, Pine Hall 115, Stanford, CA 94305-4122, USA Country Code: US 1:200 BARRNet 2:201 BARRNet Network IP: 192.216.58 Network Name: BARRNET-216-58 Location: BARRNet, c/o Stanford University, Pine Hall 115, Stanford, CA 94305-4122, USA Country Code: US 1:200 BARRNet 2:201 BARRNet Network IP: 192.216.59 Network Name: BARRNET-216-59 Location: BARRNet, c/o Stanford University, Pine Hall 115, Stanford, CA 94305-4122, USA Country Code: US 1:200 BARRNet 2:201 BARRNet Network IP: 192.219.29 Network Name: TGS-SYSTEMS Location: NSTN (Nova Scotia Technical Network), Dalhousie University, B505 Killam Library, West end of University Avenue, Halifax, Nova Scotia B3H 4H8, CANADA Country Code: CA 1:603 CA*net in Quebec 2:1391 CA*net in Toronto 3:602 CA*net in Montreal 11:1393 CA*net in Quebec 12:601 CA*net in Toronto Network IP: 192.220.236 Network Name: NETBLK-NWNET-236 Location: NorthWestNet, 15400 SE 30th Place, Suite 202, Bellevue, WA 98007, USA Country Code: US 1:685 NorthWestNet Regional Network 2:73 NorthWestNet Regional Network 3:101 NorthWestNet Regional Network Network IP: 192.220.237 Network Name: NETBLK-NWNET-237 Location: NorthWestNet, 15400 SE 30th Place, Suite 202, Bellevue, WA 98007, USA Country Code: US 1:685 NorthWestNet Regional Network 2:73 NorthWestNet Regional Network 3:101 NorthWestNet Regional Network Network IP: 192.220.238 Network Name: NETBLK-NWNET-238 Location: NorthWestNet, 15400 SE 30th Place, Suite 202, Bellevue, WA 98007, USA Country Code: US 1:685 NorthWestNet Regional Network 2:73 NorthWestNet Regional Network 3:101 NorthWestNet Regional Network Network IP: 192.220.239 Network Name: NETBLK-NWNET-239 Location: NorthWestNet, 15400 SE 30th Place, Suite 202, Bellevue, WA 98007, USA Country Code: US 1:685 NorthWestNet Regional Network 2:73 NorthWestNet Regional Network 3:101 NorthWestNet Regional Network Network IP: 192.233.12 Network Name: MEIKO-PPP-NET Location: Meiko Scientific Corporation, Reservoir Place, 1601 Trapelo Road, Waltham, MA 02154-7333, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network 5:701 Alternet Network IP: 192.233.14 Network Name: VISIDYNE-1 Location: Visidyne, Inc., South Bedford Street, Burlington, MA 01803-5129, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network 5:701 Alternet Network IP: 198.22.249 Network Name: FHSU Location: Fort Hays State University, 600 Park Street, Hays, KS 67601-4099, USA Country Code: US 1:93 MIDnet Network IP: 198.30.12 Network Name: OAR12 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212, USA Country Code: US 1:600 OARNET, Cleveland, OH Network IP: 198.30.13 Network Name: OAR13 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212, USA Country Code: US 1:600 OARNET, Cleveland, OH Network IP: 198.30.14 Network Name: OAR14 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212, USA Country Code: US 1:600 OARNET, Cleveland, OH Network IP: 198.30.15 Network Name: OAR15 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212, USA Country Code: US 1:600 OARNET, Cleveland, OH Network IP: 198.30.16 Network Name: OAR16 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212, USA Country Code: US 1:600 OARNET, Cleveland, OH Network IP: 198.30.17 Network Name: OAR17 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212, USA Country Code: US 1:600 OARNET, Cleveland, OH Network IP: 198.30.18 Network Name: OAR18 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212, USA Country Code: US 1:600 OARNET, Cleveland, OH Network IP: 198.30.19 Network Name: OAR19 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212, USA Country Code: US 1:600 OARNET, Cleveland, OH Network IP: 198.30.21 Network Name: OAR21 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212, USA Country Code: US 1:600 OARNET, Cleveland, OH Network IP: 198.30.22 Network Name: OAR22 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212, USA Country Code: US 1:600 OARNET, Cleveland, OH Network IP: 198.30.23 Network Name: OAR23 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212, USA Country Code: US 1:600 OARNET, Cleveland, OH Network IP: 198.30.24 Network Name: OAR24 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212, USA Country Code: US 1:600 OARNET, Cleveland, OH Network IP: 198.30.25 Network Name: OAR25 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212, USA Country Code: US 1:600 OARNET, Cleveland, OH Network IP: 198.30.27 Network Name: OAR27 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212, USA Country Code: US 1:600 OARNET, Cleveland, OH Network IP: 198.60.129 Network Name: NETBLK-WESTNET-129 Location: Westnet, 3645 Marine Street, U. of Colorado, Boulder, CO 80309-0455, USA Country Code: US 1:210 Westnet Regional Network (Utah Attachment) - ENSS 142 2:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 Network IP: 202.6.90 Network Name: CUACC Location: Faculty of Commerce and Accountancy, Chulalongkorn University, Computer Center, Bangkok 10330, THAILAND Country Code: TH 1:701 Alternet 2:702 Alternet The following Midlevel/Regional peering sessions have also been added: AS Number: 2149 AS Notes: PSINET-2 AS Country Code: US BkBn: 690 NSS: 140.222.136 - ENSS136 College Park, MD Gate: 192.41.177.246 - psi-nap2.psi.net MAE-EAST, Washington, DC ***************************************************************** The configuration reports which reflect today's update will be available for anonymous ftp on nis.nsf.net by 08:00 EST: configuration reports -- nis.nsf.net:nsfnet/announced.networks: ans_core.now as-as.now as-gw.now as-site.now as.now country.now gate-gw.now net-comp.now net-ter.now net-net.now netcount.now non-us.now nss-as.now nss-gw.now nss.now networks sorted by AS -- nis.nsf.net:nsfnet/announced.networks: nets.as_<AS number> NSS routing software configuration files -- nis.nsf.net:nsfnet/backbone.configuration: nss<NSS number>.t3p Please send all requests for configuration changes to nsfnet-admin(a)merit.edu using the NSFNET configuration forms. The forms are available on-line from the nis.nsf.net 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.gate, and template.as. ******************************* --Steve Widmayer Merit/NSFNET skw(a)merit.edu --Riaz Taherzadeh-Yazdian NSFNET/ANSNET rty(a)ans.net

1 0