- NANOG - lists.nanog.org

Re: Comments
by ltwu＠faline.bellcore.com 02 Sep '94

02 Sep '94

Bill, I am sympathetic to your sentiment on the proposed RFC1490 approach to build the NAPS particularly because so many people labored so hard to come up with RFC 1577. However, as one of the person involved in the NAP proposal, I would like to point out RFC 1483/1577 over AAL5 with LLC/SNAP has always been our goal since at least one year ago. Given that we have the same goal, it appears to me what you are objecting to is the use of a temporary solution to meet the time table imposed on us. Since changing the time table is not a viable option, I am curious if you have other suggestions in mind? I am asking this question just want to make sure that we did not miss anything significant in our collective decision process. > > The difficulties with the RFC 1490 approach were listed in the > Toronto meeting. I list them here: > > There is no clear migration path from this approach to > a more correct/robust implementation using RFC 1577 > encapsulation over native ATM (OC3c). My conversation with Cisco indicates that 1490/AAL5 software patch for AIP is available and 1483/AAL5 for ADSU and 1483/AAL5 for T3-AIP should be available withing about 6 months. So, indeed ther are several migration path available, not clear which is the best for all NAPs. Perhaps different NAP location may have different business needs based on what their customers desire. > > There are additional points of failure and additional costs > with the requirement for an ADSU. > I think HSSI is a proven technology. HSSI/ADSU probably has lower failure rate than AIP based on the typical bath tub curb for new product reliablity. > The listed approach requires manual configuration. I like the flexibility of AIP, but how to configure AIP to avoid congestion is still a research topic for me. > > This appears to lock the NAP into a top speed of 45Mbps > or DS3 speeds. > Hopefully, we can unlock this as soon as we feel comfortable with other approaches. BTW, I think the Merit paper is useful and good work as you said. Since RFC1490 is the only viable option exposed to Merit, saying it is one of those is a bit too harsh. Liang

9 19

Additions to the NSFNET policy-based routing database
by Steven K. Widmayer 02 Sep '94

02 Sep '94

------------------------------------------------------------------------------ CIDR Progress Report: 7167 Nets, 95 ASs, 1467 Aggregates. Details below. ------------------------------------------------------------------------------ The following changes have been made to the NSFNET policy-based routing database and will be installed on the backbone by 08:00 EDT: Total = As + Bs + Cs + Aggs Registered Networks 38470 = 30 4956 31991 1493 Configured Networks 36156 = 30 4901 29744 1481 Added Networks 186 = 0 7 150 29 Deleted Networks 24 = 0 1 22 1 IP address Net name Country Priority:AS ---------- -------- ------- ----------- 134.45/16 NET-EGSD C:US 1:1240 2:1800 137.58/16 METLAN C:FR 1:701(136) 2:1800 141.245/16 BAENET C:GB 1:701(136) 2:1800 146.56/16 NET-ORACLE C:JP 1:2149 2:174 153.92/14 XLINK-AGG-153-92 C:DE 1:1324 2:1800 3:1240 4:1133 153.96/14 XLINK-AGG-153-96 C:DE 1:1324 2:1800 3:1240 4:1133 156.79/16 INCASEOO C:US 1:2551(229) 2:2551(136) 3:1321 161.210/16 NET-DMACC C:US 1:1800 2:1240 3:1323 167.93/16 VOLUSIA C:US 1:279 2:86 192.33.120/21 PSI-NET3-10 C:CH 1:1133 2:1674 3:1800 192.36.170/24 SE-ABC C:SE 1:1800 2:1133 3:1240 192.42.200/23 SWITCH-AGGR.6 C:CH 1:1133 2:1674 3:1800 192.52.88/24 DMSTST17 C:US 1:771 2:372 3:297 192.52.89/24 DMSTST9 C:US 1:771 2:372 3:297 192.52.90/24 DMSTST16A1 C:US 1:771 2:372 3:297 192.52.91/24 DMSTST32 C:US 1:771 2:372 3:297 192.52.93/24 DMSTST36 C:US 1:771 2:372 3:297 192.52.94/24 DMSTSTB C:US 1:771 2:372 3:297 192.52.95/24 DMSTST16A2 C:US 1:771 2:372 3:297 192.75.59/24 SH1-NET C:CA 1:701(136) 2:701(134) 192.75.243/24 SFUNFS-NETS3 C:CA 1:577(143) 2:577(133) 3:577(137) 192.75.244/24 SFUNFS-NETS4 C:CA 1:577(143) 2:577(133) 3:577(137) 192.75.245/24 SFUNFS-NETS5 C:CA 1:577(143) 2:577(133) 3:577(137) 192.94.80/24 ACCELTECH C:US 1:1240 2:1800 192.101.181/24 HSII C:US 1:1225 2:267 3:266 4:555 192.114.242/24 IET-NET C:IL 1:2149 2:174 5:1133 192.114.243/24 SCANVEC-NET C:IL 1:2149 2:174 5:1133 192.114.247/24 MIGAL-NET C:IL 1:2149 2:174 5:1133 192.114.249/24 ISRANTIQUE-NET C:IL 1:2149 2:174 5:1133 192.124.159/24 ESI C:US 1:2551(229) 2:2551(136) 3:1321 192.128.121/24 XU-FDDI-MH1 C:US 1:97 192.128.161/24 XU-FDDI-MH2 C:US 1:97 192.135.77/24 EBA-ENG C:CA 1:577(143) 2:577(133) 3:577(137) 192.146.183/24 ISS-ETHERNET C:US 1:210 2:209 192.156.145/24 FUKUI-NCT C:JP 1:1240 2:1800 192.156.146/24 FUKUI-NCT2 C:JP 1:1240 2:1800 192.156.147/24 FUKUI-NCT3 C:JP 1:1240 2:1800 192.156.148/24 FUKUI-NCT4 C:JP 1:1240 2:1800 192.156.149/24 FUKUI-NCT5 C:JP 1:1240 2:1800 192.197.96/24 FSA-NET5 C:CA 1:577(143) 2:577(133) 3:577(137) 192.197.97/24 FSA-NET6 C:CA 1:577(143) 2:577(133) 3:577(137) 192.197.98/24 FSA-NET7 C:CA 1:577(143) 2:577(133) 3:577(137) 192.197.99/24 FSA-NET8 C:CA 1:577(143) 2:577(133) 3:577(137) 192.197.100/24 FSA-NET9 C:CA 1:577(143) 2:577(133) 3:577(137) 192.197.101/24 FSA-NET2 C:CA 1:577(143) 2:577(133) 3:577(137) 192.197.102/24 FSA-NET3 C:CA 1:577(143) 2:577(133) 3:577(137) 192.197.103/24 FSA-NET4 C:CA 1:577(143) 2:577(133) 3:577(137) 192.197.104/24 FSA-NET1 C:CA 1:577(143) 2:577(133) 3:577(137) 192.197.105/24 FSA-NET10 C:CA 1:577(143) 2:577(133) 3:577(137) 192.197.106/24 FSA-NET11 C:CA 1:577(143) 2:577(133) 3:577(137) 192.197.107/24 FSA-NET12 C:CA 1:577(143) 2:577(133) 3:577(137) 192.197.108/24 FSA-NET13 C:CA 1:577(143) 2:577(133) 3:577(137) 192.197.109/24 FSA-NET14 C:CA 1:577(143) 2:577(133) 3:577(137) 192.197.110/24 FSA-NET15 C:CA 1:577(143) 2:577(133) 3:577(137) 192.197.111/24 FSA-NET16 C:CA 1:577(143) 2:577(133) 3:577(137) 192.203.248/24 PPOC2 C:US 1:209 2:210 192.207.213/24 UMSMEDCTR4 C:US 1:279 2:86 192.218.90/23 IMPRESS-NET C:JP 1:701(136) 2:701(134) 192.218.92/22 AUNET1 C:JP 1:1240 2:1800 192.232.128/19 NETBLK-BOXHILLTAFE C:AU 1:372 2:297 192.239.186/24 FDE-FTM C:US 1:279 2:86 193.2.5/24 IJS-NET2 C:SI 1:1800 2:1133 3:1674 4:1240 193.2.8/24 NUK-NET C:SI 1:1800 2:1133 3:1674 4:1240 193.2.90/24 ZOO-BF-UNI-LJ-NET C:SI 1:1800 2:1133 3:1674 4:1240 193.2.157/24 GMB2-EDUS-NET C:SI 1:1800 2:1133 3:1674 4:1240 193.13.144/22 SE-MM C:SE 1:1800 2:1879 3:1133 4:1240 193.40/16 ESTNET-BLOCK C:EE 1:1800 2:1879 3:1133 4:1240 193.50.108/24 FR-BIBNAT01 C:FR 1:1800 2:1240 3:1133 4:1674 193.50.109/24 FR-BIBNAT02 C:FR 1:1800 2:1240 3:1133 4:1674 193.50.110/24 FR-BIBNAT03 C:FR 1:1800 2:1240 3:1133 4:1674 193.50.111/24 FR-BIBNAT04 C:FR 1:1800 2:1240 3:1133 4:1674 193.50.121/24 FR-BIBNAT05 C:FR 1:1800 2:1240 3:1133 4:1674 193.50.122/24 FR-BIBNAT06 C:FR 1:1800 2:1240 3:1133 4:1674 193.50.123/24 FR-BIBNAT07 C:FR 1:1800 2:1240 3:1133 4:1674 193.50.133/24 FR-BIBNAT08 C:FR 1:1800 2:1240 3:1133 4:1674 193.50.134/24 FR-BIBNAT09 C:FR 1:1800 2:1240 3:1133 4:1674 193.80.246/24 STK-NET C:AT 1:701(136) 2:1800 193.81.80/24 VRZ-NET C:AT 1:701(136) 2:1800 193.81.81/24 VRZ-NET C:AT 1:701(136) 2:1800 193.81.82/24 VRZ-NET C:AT 1:701(136) 2:1800 193.81.83/24 VRZ-NET C:AT 1:701(136) 2:1800 193.81.84/24 VRZ-NET C:AT 1:701(136) 2:1800 193.81.85/24 VRZ-NET C:AT 1:701(136) 2:1800 193.81.86/24 VRZ-NET C:AT 1:701(136) 2:1800 193.81.87/24 VRZ-NET C:AT 1:701(136) 2:1800 193.101.143/24 NAV-NET C:DE 1:701(136) 2:1800 193.102.209/24 ECO-NET C:DE 1:701(136) 2:1800 193.102.236/24 NAV-NET2 C:DE 1:701(136) 2:1800 193.102.237/24 NAV-NET2 C:DE 1:701(136) 2:1800 193.102.238/24 NAV-NET2 C:DE 1:701(136) 2:1800 193.102.239/24 NAV-NET2 C:DE 1:701(136) 2:1800 193.125.42/24 NZ-NET C:RU 1:701(136) 2:1800 193.125.81/24 COMTAT C:RU 1:701(136) 2:1800 194.41.60/24 VIAD-C-41-60 C:AT 1:1800 2:1133 3:1240 194.41.61/24 VIAD-C-41-61 C:AT 1:1800 2:1133 3:1240 194.44.1/24 GLUK C:UA 1:1800 2:1133 3:1240 194.51.15/24 FR-PLATINA C:FR 1:1800 2:1240 3:1133 4:1674 194.51.16/24 FR-ALTERN C:FR 1:1800 2:1240 3:1133 4:1674 194.55.176/22 RUECKER2-GMBH C:DE 1:1324 2:1800 3:1240 4:1133 198.15.32/19 NETBLK-AIDAB C:AU 1:372 2:297 198.17.195/24 RICHARDSON-NET2 C:US 1:3354 198.22.191/24 TCNET-2 C:US 1:701(136) 2:701(134) 198.22.192/24 TCNET-3 C:US 1:701(136) 2:701(134) 198.62.195/24 UGC-CONSULTING C:US 1:209 2:210 198.78.224/20 LEVY-K12-FL-US C:US 1:279 2:86 198.113.7/24 MMC-7 C:US 1:560 2:701(136) 198.113.8/24 MMC-8 C:US 1:560 2:701(136) 198.113.9/24 MMC-9 C:US 1:560 2:701(136) 198.113.190/24 EKSC-NET C:US 1:560 2:701(136) 198.161.220/24 TIC-AB C:CA 1:577(143) 2:577(133) 3:577(137) 198.161.228/24 INN-C-BLK C:CA 1:1240 2:1800 198.164.27/24 NBNET-NB-CA C:CA 1:577(133) 2:577(137) 3:577(143) 198.166.220/24 ACINSCA-C-166-220 C:CA 1:577(137) 2:577(133) 3:577(143) 198.166.221/24 ACINSCA-C-166-221 C:CA 1:577(137) 2:577(133) 3:577(143) 198.166.222/24 ACINSCA-C-166-222 C:CA 1:577(137) 2:577(133) 3:577(143) 198.166.223/24 ACINSCA-C-166-223 C:CA 1:577(137) 2:577(133) 3:577(143) 198.175.158/24 UCSFRESNO C:US 1:2150 198.189.194/24 NETBLK-CSUNET-NORTH C:US 1:2150 198.202.204/24 EVOLVING-2 C:US 1:2551(229) 2:2551(136) 3:1321 198.202.243/24 EVOLVING-3 C:US 1:2551(229) 2:2551(136) 3:1321 198.212.244/24 CHEVRY C:US 1:1740 199.71.76/24 NETBLK-ISM-ON-CA C:CA 1:2493 199.75.24/24 PIRE-ORG C:US 1:86 2:279 199.93.64/24 MASS-64 C:US 1:560 2:701(136) 199.93.65/24 MASS-65 C:US 1:560 2:701(136) 199.93.176/24 POWERSOFT-NET1176 C:US 1:560 2:701(136) 199.93.177/24 POWERSOFT-NET1177 C:US 1:560 2:701(136) 199.93.178/24 POWERSOFT-NET1178 C:US 1:560 2:701(136) 199.93.179/24 POWERSOFT-NET1179 C:US 1:560 2:701(136) 199.164.193/24 GOODCREATNET C:US 1:1225 2:267 3:266 4:555 199.165.191/24 SATEL-C C:US 1:210 2:209 199.171.174/24 DATANET-NET C:US 1:701(136) 2:701(134) 199.172.8/24 I-LINK C:US 1:701(136) 2:701(134) 199.172.9/24 I-LINK C:US 1:701(136) 2:701(134) 199.172.22/24 ATHENA-SPINE3 C:US 1:701(136) 2:701(134) 199.172.23/24 ATHENA-SPINE3 C:US 1:701(136) 2:701(134) 199.184.32/20 SI-HQ-CBLOCK C:US 1:1800 2:1240 199.184.48/21 SI-HQ-CBLOCK C:US 1:1800 2:1240 199.184.56/22 SI-HQ-CBLOCK C:US 1:1800 2:1240 199.184.60/23 SI-HQ-CBLOCK C:US 1:1800 2:1240 199.184.62/24 SI-HQ-CBLOCK C:US 1:1800 2:1240 199.184.63/24 SI-HQ-CBLOCK C:US 1:1800 2:1240 199.196.21/24 NYS-DCS C:US 1:1324 199.201.64/18 FULLFEED-WAN C:US 1:1800 2:1240 199.201.214/24 CUSTOMS-C3I C:US 1:2551(229) 2:2551(136) 3:1321 199.222.53/24 HEARST-NET C:US 1:1324 199.222.56/24 CIS-DMZ C:US 1:1324 199.235.124/24 HALTON-NET C:CA 1:2493 199.245.156/24 CSSD11 C:US 1:1332 199.246.8/24 CIM C:CA 1:1240 2:1800 199.249.165/24 NWURH2 C:US 1:1225 2:267 3:266 199.249.166/24 NWURH3 C:US 1:1225 2:267 3:266 199.249.167/24 NWURH4 C:US 1:1225 2:267 3:266 199.249.168/24 NWURH5 C:US 1:1225 2:267 3:266 199.249.169/24 NWURH6 C:US 1:1225 2:267 3:266 200.10.131/24 CULPUC C:PE 1:1800 2:1240 200.10.188/24 ULIMA1 C:PE 1:1800 2:1240 202.6.32/19 APNIC-CIDR-BLK C:AU 1:372 2:297 202.12.32/19 APNIC-CIDR-BLK C:AU 1:372 2:297 202.14.176/20 APNIC-CIDR-BLK C:AU 1:372 2:297 202.14.192/20 APNIC-CIDR-BLK C:AU 1:372 2:297 202.20.16/20 APNIC-CIDR-BLK C:AU 1:372 2:297 202.25.68/22 HCT-NET C:JP 1:1240 2:1800 202.31.220/24 KOREA-INET-31-220 C:KR 1:1800 2:1240 204.4.31/24 PSINET C:US 1:2149 2:174 204.4.32/24 PSINET C:US 1:2149 2:174 204.4.33/24 PSINET C:US 1:2149 2:174 204.4.34/24 PSINET C:US 1:2149 2:174 204.4.35/24 PSINET C:US 1:2149 2:174 204.4.36/24 PSINET C:US 1:2149 2:174 204.4.37/24 PSINET C:US 1:2149 2:174 204.17.221/24 MICROPATENT C:US 1:2551(229) 2:2551(136) 3:1321 204.40.118/24 SIMCOECBE C:CA 1:577(133) 2:577(137) 3:577(143) 204.52.207/24 BASIS-DOM C:US 1:209 2:210 204.56.3/24 MAMTC.GEN.MO.US C:US 1:1240 2:1800 204.56.4/24 CRN.GEN.MO.US C:US 1:1240 2:1800 204.56.5/24 NAMA.MUS.MO.US C:US 1:1240 2:1800 204.56.6/24 CENTRAL.KCSD.K12.MO C:US 1:1240 2:1800 204.62.213/24 JORTEC C:US 1:1332 204.68.182/24 BHHOME C:US 1:1240 2:1800 204.72.168/22 TRITICOM1 C:US 1:1225 2:267 3:266 4:555 204.72.172/22 ATCORP C:US 1:1225 2:267 3:266 4:555 204.95.64/20 A2I C:US 1:1957 2:1800 3:1240 204.131/16 CSN-BLOCK-6 C:US 1:209 2:210 204.132/16 CSN-BLOCK-6 C:US 1:209 2:210 204.133/16 CSN-BLOCK-6 C:US 1:209 2:210 Deletions: --153.93/16 BAW C:DE 1:1324 2:1800 3:1240 4:1133 --192.218.90/24 IMPRESS-NET1 C:JP 1:1957 --193.40.104/24 VS-NET-2 C:EE 1:1957 --193.40.106/24 VS-NET-1 C:EE 1:1957 --193.40.109/24 FXHIGHWAY-NET C:EE 1:1957 --193.40.111/24 ABS-NET C:EE 1:1957 --193.40.118/24 SM-NET C:EE 1:1957 --193.40.119/24 TIC-NET C:EE 1:1957 --193.40.120/24 HAR-NET C:EE 1:1957 --193.40.123/24 POSTIMEES-TLN C:EE 1:1957 --193.134/16 SWITCH-AGGR.4 C:CH 1:1133 2:1674 3:1800 --198.64.232/24 SESQUI-C-64-232 C:US 1:114 --198.64.239/24 SESQUI-C-64-239 C:US 1:114 --198.65.3/24 SESQUI-CIDR-C-65-3 C:US 1:114 --198.65.4/24 SESQUI-CIDR-C-65-4 C:US 1:114 --198.65.132/24 SESQUI-CIDR-C-65-132 C:US 1:114 --198.65.133/24 SESQUI-CIDR-C-65-133 C:US 1:114 --198.65.134/24 SESQUI-CIDR-C-65-134 C:US 1:114 --198.65.136/24 SESQUI-CIDR-C-65-136 C:US 1:114 --198.65.137/24 SESQUI-CIDR-C-65-137 C:US 1:114 --198.65.138/24 SESQUI-CIDR-C-65-138 C:US 1:114 --198.65.139/24 SESQUI-CIDR-C-65-139 C:US 1:114 --199.176.22/24 AADSNET-CIDR-C-176-22 C:US 1:1225 2:266 3:267 --199.176.23/24 AADSNET-CIDR-C-176-23 C:US 1:1225 2:266 3:267 Expanded listing, sorted by country, then by organization: ========================================================== Australia --------- Australian Academic and Research Network, GPO Box 1142, Canberra, ACT, 2904, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ----------- 202.6.32/19 APNIC-CIDR-BLK (AU) 202.12.32/19 APNIC-CIDR-BLK (AU) 202.14.176/20 APNIC-CIDR-BLK (AU) 202.14.192/20 APNIC-CIDR-BLK (AU) 202.20.16/20 APNIC-CIDR-BLK (AU) Australian International Development Assistance Bureau, GPO Box 887, Canberra, ACT, 2601, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) ------------ 198.15.32/19 NETBLK-AIDAB (AU) Box Hill College of TAFE, Private Bag 2014, Box Hill, Victoria, 3128, AUSTRALIA 1:372 Nasa Science Network (FIX-West) 2:297 Nasa Science Network (FIX-East) -------------- 192.232.128/19 NETBLK-BOXHILLTAFE (AU) Austria ------- Schablonentechnik Kufstein, Schaftenau, A-6330 Kufstein, AUSTRIA 1:701(136) Alternet 2:1800 ICM-Atlantic ------------- 193.80.246/24 STK-NET (AT) Vianet GesmbH, Barnabitengasse 9&9a, A-1060 Vienna, AUSTRIA 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific ------------ 194.41.60/24 VIAD-C-41-60 (AT) 194.41.61/24 VIAD-C-41-61 (AT) Vorarlberger Rechenzentrum, Abteilung Netzwerktechnik, Zollgasse 10, A-6850 Dornbirn, AUSTRIA 1:701(136) Alternet 2:1800 ICM-Atlantic ------------ 193.81.80/24 VRZ-NET (AT) 193.81.81/24 VRZ-NET (AT) 193.81.82/24 VRZ-NET (AT) 193.81.83/24 VRZ-NET (AT) 193.81.84/24 VRZ-NET (AT) 193.81.85/24 VRZ-NET (AT) 193.81.86/24 VRZ-NET (AT) 193.81.87/24 VRZ-NET (AT) Canada ------ Atlantic Computer Institute, Suite 201 5523 Spring Garden Rd, Halifax, NS, B3J 3T1, CANADA 1:577(137) CA-NET-AS 2:577(133) CA-NET-AS 3:577(143) CA-NET-AS -------------- 198.166.220/24 ACINSCA-C-166-220 (CA) 198.166.221/24 ACINSCA-C-166-221 (CA) 198.166.222/24 ACINSCA-C-166-222 (CA) 198.166.223/24 ACINSCA-C-166-223 (CA) Cimtegration Inc., 2525 Speers Road, Oakville, Ontario, L6L 5M2, CANADA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ------------ 199.246.8/24 CIM (CA) EBA Engineering, 14535 118 Ave, Edmonton, AB, T5L 2M7, CANADA 1:577(143) CA-NET-AS 2:577(133) CA-NET-AS 3:577(137) CA-NET-AS ------------- 192.135.77/24 EBA-ENG (CA) Freedman Sharp and Associates, 204 Woodglenn Place SW, Calgary, AB, T2W 4G3, CANADA 1:577(143) CA-NET-AS 2:577(133) CA-NET-AS 3:577(137) CA-NET-AS ------------- 192.197.96/24 FSA-NET5 (CA) 192.197.97/24 FSA-NET6 (CA) 192.197.98/24 FSA-NET7 (CA) 192.197.99/24 FSA-NET8 (CA) 192.197.100/24 FSA-NET9 (CA) 192.197.101/24 FSA-NET2 (CA) 192.197.102/24 FSA-NET3 (CA) 192.197.103/24 FSA-NET4 (CA) 192.197.104/24 FSA-NET1 (CA) 192.197.105/24 FSA-NET10 (CA) 192.197.106/24 FSA-NET11 (CA) 192.197.107/24 FSA-NET12 (CA) 192.197.108/24 FSA-NET13 (CA) 192.197.109/24 FSA-NET14 (CA) 192.197.110/24 FSA-NET15 (CA) 192.197.111/24 FSA-NET16 (CA) Information Systems Mgt Corp., 2220 Walkley Road, Ottawa, ON, K1G 5L2, CANADA 1:2493 FONOROLA-EAST ------------ 199.71.76/24 NETBLK-ISM-ON-CA (CA) Internode Networks, 112 Rivergreen Crescent SE, Calgary, Alberta, T2C 3V6, CANADA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic -------------- 198.161.228/24 INN-C-BLK (CA) NBTel, PO Box 1430, One Brunswick Sq, Saint John, NB, E2L 4K2, CANADA 1:577(133) CA-NET-AS 2:577(137) CA-NET-AS 3:577(143) CA-NET-AS ------------- 198.164.27/24 NBNET-NB-CA (CA) SHL Systemhouse Incorporated, 50 O'Connor Street, Suite 501, Ottawa, Ontario, K1P 6L2, CANADA 1:701(136) Alternet 2:701(134) Alternet ------------ 192.75.59/24 SH1-NET (CA) Simcoe County Board of Education, Hwy #26 W, Midhurst, ON, L0L 1X0, CANADA 1:577(133) CA-NET-AS 2:577(137) CA-NET-AS 3:577(143) CA-NET-AS ------------- 204.40.118/24 SIMCOECBE (CA) Simon Fraser University, Computing Services Operations, Strand Hall, Burnaby, British Columbia, V5A 1S6, CANADA 1:577(143) CA-NET-AS 2:577(133) CA-NET-AS 3:577(137) CA-NET-AS ------------- 192.75.243/24 SFUNFS-NETS3 (CA) 192.75.244/24 SFUNFS-NETS4 (CA) 192.75.245/24 SFUNFS-NETS5 (CA) The Halton Board of Education, 2050 Guelph Line, P.O. Box 5005, Burlington, Ontario, L7R 3Z2, CANADA 1:2493 FONOROLA-EAST -------------- 199.235.124/24 HALTON-NET (CA) The Internet Companion, 11729 97 Street, Edmonton, AB, T5G 1Y3, CANADA 1:577(143) CA-NET-AS 2:577(133) CA-NET-AS 3:577(137) CA-NET-AS -------------- 198.161.220/24 TIC-AB (CA) Estonia ------- Institute of Cybernetics, Akadeemia tee 21, EE0026 Tallinn, ESTONIA 1:1800 ICM-Atlantic 2:1879 EUROPE-RS 3:1133 CERN/DANTE 4:1240 ICM-Pacific --------- 193.40/16 ESTNET-BLOCK (EE) France ------ Altern B, 10 rue Francis de Pressense, 75014 Paris, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ------------ 194.51.16/24 FR-ALTERN (FR) Bibliotheque Nationale de France, 58 rue Richelieu, 75002 Paris, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ------------- 193.50.108/24 FR-BIBNAT01 (FR) 193.50.109/24 FR-BIBNAT02 (FR) 193.50.110/24 FR-BIBNAT03 (FR) 193.50.111/24 FR-BIBNAT04 (FR) 193.50.121/24 FR-BIBNAT05 (FR) 193.50.122/24 FR-BIBNAT06 (FR) 193.50.123/24 FR-BIBNAT07 (FR) 193.50.133/24 FR-BIBNAT08 (FR) 193.50.134/24 FR-BIBNAT09 (FR) Matra Ericsson Telecommunications - MET, 19 Avenue Carnot, 91348 Massy CEDEX, FRANCE 1:701(136) Alternet 2:1800 ICM-Atlantic --------- 137.58/16 METLAN (FR) Platina Limited, 14 Avenue de Bures, 91400 Orsay, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ------------ 194.51.15/24 FR-PLATINA (FR) Germany ------- ECO GmbH i.Gr., Emil-Figge-Str. 80, D-44227 Dortmund, GERMANY 1:701(136) Alternet 2:1800 ICM-Atlantic -------------- 193.102.209/24 ECO-NET (DE) MAV GmbH, Sedanstr. 13-17, D-50668 Koeln, GERMANY 1:701(136) Alternet 2:1800 ICM-Atlantic -------------- 193.101.143/24 NAV-NET (DE) 193.102.236/24 NAV-NET2 (DE) 193.102.237/24 NAV-NET2 (DE) 193.102.238/24 NAV-NET2 (DE) 193.102.239/24 NAV-NET2 (DE) NTG Netzwerk und Telematic GmbH, Vincenz-Priessnitz-Str. 3, D-76131 Karlsruhe, GERMANY 1:1324 ANS New York City - DNSS 35 2:1800 ICM-Atlantic 3:1240 ICM-Pacific 4:1133 CERN/DANTE --------- 153.92/14 XLINK-AGG-153-92 (DE) 153.96/14 XLINK-AGG-153-96 (DE) Ruecker GmbH, Siemensstr. 1, D-38518 Gifhorn, GERMANY 1:1324 ANS New York City - DNSS 35 2:1800 ICM-Atlantic 3:1240 ICM-Pacific 4:1133 CERN/DANTE ------------- 194.55.176/22 RUECKER2-GMBH (DE) Israel ------ Inteligent Electronics LTd., 14 Raul Wallenberg St, Ramat Hayal Tel-Aviv, ISRAEL 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI 5:1133 CERN/DANTE -------------- 192.114.242/24 IET-NET (IL) Israel Antiquities Authority, Rockefeller Museum Bldg.,P.O.B. 586, Jerusalem, 81004, ISRAEL 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI 5:1133 CERN/DANTE -------------- 192.114.249/24 ISRANTIQUE-NET (IL) MIGAL Galille Technology Center, Kiriat Shmona, 10200, ISRAEL 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI 5:1133 CERN/DANTE -------------- 192.114.247/24 MIGAL-NET (IL) Scanvec Co., Atidim, Bldg 7, P.O.B. 59159, Tel-Aviv, ISRAEL 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI 5:1133 CERN/DANTE -------------- 192.114.243/24 SCANVEC-NET (IL) Japan ----- Asahi University, School of Business Administration, 1851-1, Hozumi, Hozumi-chou, Motosu-gun, Gifu-ken, JAPAN 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ------------- 192.218.92/22 AUNET1 (JP) Fukui National College of Technology, Geshi-cho, Sabae-shi, Fukui 916, JAPAN 1:1240 ICM-Pacific 2:1800 ICM-Atlantic -------------- 192.156.145/24 FUKUI-NCT (JP) 192.156.146/24 FUKUI-NCT2 (JP) 192.156.147/24 FUKUI-NCT3 (JP) 192.156.148/24 FUKUI-NCT4 (JP) 192.156.149/24 FUKUI-NCT5 (JP) Hakodate National College of Technology, 14-1 Tokura-cho, Hakodate, JAPAN 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ------------ 202.25.68/22 HCT-NET (JP) Impress Corporation, 20 Sanban-cho, Chiyodaku, Tokyo, 102, JAPAN 1:701(136) Alternet 2:701(134) Alternet ------------- 192.218.90/23 IMPRESS-NET (JP) ORACLE CORPORATION JAPAN, 6-19-20, JINGU-MAE, SHIBUYA-KU, TOKYO, 150, JAPAN 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI --------- 146.56/16 NET-ORACLE (JP) Korea, South ------------ Information Comm. Institute attached FUTURE SYSTEMS Inc., 372-2, YangJae-Dong, SeoCho-Gu, Seoul, KOREA, REPUBLIC OF 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ------------- 202.31.220/24 KOREA-INET-31-220 (KR) Peru ---- Pontificia Universidad Catolica del Peru, Av. Universitaria s/n Cdra.18, Lima, Lima, PERU 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ------------- 200.10.131/24 CULPUC (PE) Universidad de Lima - PERU, Av. Javier Prado Este S/N - Monterrico, Lima, Lima, PERU 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ------------- 200.10.188/24 ULIMA1 (PE) Russian Federation ------------------ Comintat-Infotel Inc., 420053 Kazan, P/O Box 332, RUSSIAN FEDERATION 1:701(136) Alternet 2:1800 ICM-Atlantic ------------- 193.125.81/24 COMTAT (RU) Nienschanz Joint Stock Company, Zakharievskaya str., 25-12, Saint-Petersburg, RUSSIAN FEDERATION 1:701(136) Alternet 2:1800 ICM-Atlantic ------------- 193.125.42/24 NZ-NET (RU) Slovenia -------- II. Gimnazija Maribor, Maribor, SLOVENIA 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1674 CERN/DANTE 4:1240 ICM-Pacific ------------ 193.2.157/24 GMB2-EDUS-NET (SI) Jozef Stefan Institute, Ljubljana, SLOVENIA 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1674 CERN/DANTE 4:1240 ICM-Pacific ---------- 193.2.5/24 IJS-NET2 (SI) Narodna univerzitetna knjiznjica, Ljubljana, SLOVENIA 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1674 CERN/DANTE 4:1240 ICM-Pacific ---------- 193.2.8/24 NUK-NET (SI) University of Ljubljana, Zootechnical Dept., Ljubljana, SLOVENIA 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1674 CERN/DANTE 4:1240 ICM-Pacific ----------- 193.2.90/24 ZOO-BF-UNI-LJ-NET (SI) Sweden ------ ABC-Klubben, Box 14143, S-161 14 Bromma, SWEDEN 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific ------------- 192.36.170/24 SE-ABC (SE) MacMeckarna AB, Master Johansgatan 15, S-211 21 Malmo, SWEDEN 1:1800 ICM-Atlantic 2:1879 EUROPE-RS 3:1133 CERN/DANTE 4:1240 ICM-Pacific ------------- 193.13.144/22 SE-MM (SE) Switzerland ----------- Paul Scherrer Institute, Villigen, CH-5232 Villigen-PSI, SWITZERLAND 1:1133 CERN/DANTE 2:1674 CERN/DANTE 3:1800 ICM-Atlantic ------------- 192.33.120/21 PSI-NET3-10 (CH) SWITCH Geschaeftsstelle, Limmatquai 138, CH-8001 Zuerich, SWITZERLAND 1:1133 CERN/DANTE 2:1674 CERN/DANTE 3:1800 ICM-Atlantic ------------- 192.42.200/23 SWITCH-AGGR.6 (CH) Ukraine ------- GlasNet-Ukraine, Metrologicheskaya Str 14b, 252143 Kiev, UKRAINE 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific ----------- 194.44.1/24 GLUK (UA) United Kingdom -------------- British Aerospace, 2, Gladiator Way, Farnborough Aerospace Centre, Farnborough, Hants, England, Great Britain, UNITED KINGDOM 1:701(136) Alternet 2:1800 ICM-Atlantic ---------- 141.245/16 BAENET (GB) United States ------------- AT&T Bell Laboratories, 600 Mountain Avenue, PO Box 636, Murray Hill, NJ 07974-0636, USA 1:97 JvNCnet Regional Network -------------- 192.128.121/24 XU-FDDI-MH1 (US) 192.128.161/24 XU-FDDI-MH2 (US) Accel Technologies Incorporated, 6825 Flanders Drive, San Diego, CA 92121, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ------------ 192.94.80/24 ACCELTECH (US) Ackerman McQueen, 1601 N.W. Expressway, Oklahoma city, OK 73118, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ----------- 204.4.35/24 PSINET (US) 204.4.36/24 PSINET (US) Alpha Network Technologies, 9055 Comprint Ct., Gaithersburg, MD 20877, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ----------- 204.4.31/24 PSINET (US) American Crop Protection Association, 1156 15th Street N.W. Suite400, Washington, DC 20005, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ----------- 204.4.34/24 PSINET (US) Antares Alliance Group, 7171 Forest Ln. C210, Dallas, TX 75230, USA 1:2551(229) NETCOM 2:2551(136) NETCOM 3:1321 ANS San Francisco - DNSS 11 --------- 156.79/16 INCASEOO (US) Architecture Technology Corp., 11800 SingleTree Ln., Suite 300, Eden Prairie, MN 55344, USA 1:1225 CICNET at Argonne Labs 2:267 CICNET at UIUC 3:266 CICNET at MERIT 4:555 Minnesota Supercomputer Center Network (MSCNet) ------------- 204.72.172/22 ATCORP (US) Athena Programming, 24680 NW Dixie Mountain Rd., Hillsboro, OR 97124, USA 1:701(136) Alternet 2:701(134) Alternet ------------- 199.172.22/24 ATHENA-SPINE3 (US) 199.172.23/24 ATHENA-SPINE3 (US) BASIS International, Ltd., 5901 Jefferson Street NE, Albuquerque, NM 87109, USA 1:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 2:210 Westnet Regional Network (Utah Attachment) - ENSS 142 ------------- 204.52.207/24 BASIS-DOM (US) Bill Heiser, 8 Walden Dr., Natick, MA 01760, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ------------- 204.68.182/24 BHHOME (US) CIS Corporation, One Northern Concourse, North Syracuse, NY 13212, USA 1:1324 ANS New York City - DNSS 35 ------------- 199.222.56/24 CIS-DMZ (US) Central High School, 3221 Indiana, Kansas City, MO 64128, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ----------- 204.56.6/24 CENTRAL.KCSD.K12.MO (US) City of Richardson, P. O. Box 830309, 411 W. Arapaho Rd., Richardson, TX 75080, USA 1:3354 THENET-AS-1 ------------- 198.17.195/24 RICHARDSON-NET2 (US) Colorado Springs School District 11, 1036 N. Franklin, Colorado Springs, CO 80903, USA 1:1332 ANS Denver - DNSS 99 -------------- 199.245.156/24 CSSD11 (US) Colorado Supernet, Inc., 999 18th Street, Suite 2640 Denver, CO 80202, USA 1:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 2:210 Westnet Regional Network (Utah Attachment) - ENSS 142 ---------- 204.131/16 CSN-BLOCK-6 (US) 204.132/16 CSN-BLOCK-6 (US) 204.133/16 CSN-BLOCK-6 (US) Community Resource Network, 125 E. 31st Street, Kansas City, MO 64108, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ----------- 204.56.4/24 CRN.GEN.MO.US (US) Dataport Computer Services, 555 S. Palm Canyon Dr. Ste. A106, Palm Springs, CA 92264, USA 1:701(136) Alternet 2:701(134) Alternet -------------- 199.171.174/24 DATANET-NET (US) Des Moines Area Community College, 2006 S. Ankeny Blvd., Des Moines, IA 50021, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1323 ANS Chicago - DNSS 27 ---------- 161.210/16 NET-DMACC (US) Elk Grove School District, 9510 Elk Grove - Florin Road, Elk Grove, CA 95624, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic --------- 134.45/16 NET-EGSD (US) Eunice Kennedy Shriver Center, 200 Trapelo Road, Waltham, MA 02254, USA 1:560 NEARnet Regional Network 2:701(136) Alternet -------------- 198.113.190/24 EKSC-NET (US) Evolving Systems, 8000 E. Maplewood Ave., Englewood, CO 80111, USA 1:2551(229) NETCOM 2:2551(136) NETCOM 3:1321 ANS San Francisco - DNSS 11 -------------- 192.124.159/24 ESI (US) 198.202.204/24 EVOLVING-2 (US) 198.202.243/24 EVOLVING-3 (US) FDE Division of Blind Services, 2830 Winkler Ave, Suite 207, Fort Myers, FL 33916, USA 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) -------------- 192.239.186/24 FDE-FTM (US) FullFeed Communications, 359 Raven Lane, Madison, WI 53704-2488, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ------------- 199.201.64/18 FULLFEED-WAN (US) Good Creations, 3029 Blackstone Ave. So., St. Louis Park, MN 55416, USA 1:1225 CICNET at Argonne Labs 2:267 CICNET at UIUC 3:266 CICNET at MERIT 4:555 Minnesota Supercomputer Center Network (MSCNet) -------------- 199.164.193/24 GOODCREATNET (US) Health Systems Integration Incorporated, One Appletree Square, Suite 700, 8009 34th Avenue South, Bloomington, MN 55425-1616, USA 1:1225 CICNET at Argonne Labs 2:267 CICNET at UIUC 3:266 CICNET at MERIT 4:555 Minnesota Supercomputer Center Network (MSCNet) -------------- 192.101.181/24 HSII (US) Hearst Magazines Inc., 2nd Floor Communication Center,250 West 55th St, New York, NY 10019, USA 1:1324 ANS New York City - DNSS 35 ------------- 199.222.53/24 HEARST-NET (US) ILINK, Ltd., 16207 Braesgate Drive, Austin, TX 78717, USA 1:701(136) Alternet 2:701(134) Alternet ------------ 199.172.8/24 I-LINK (US) 199.172.9/24 I-LINK (US) Interbackup, 4764 Park Granada Ste 202, Calabasas, CA 91302, USA 1:1740 CERFnet -------------- 198.212.244/24 CHEVRY (US) Interlake Software Solutions, 4750 Wiley Post Rd. #110 Salt Lake, Salt Lake City, UT 84116, USA 1:210 Westnet Regional Network (Utah Attachment) - ENSS 142 2:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 -------------- 192.146.183/24 ISS-ETHERNET (US) JorTec Software, 2524 W. Colorado Ave. Ste. 202, Colorado Springs, CO 80904, USA 1:1332 ANS Denver - DNSS 99 ------------- 204.62.213/24 JORTEC (US) Maine Medical Center, 22 Bramhall Street, Portland, ME 04102, USA 1:560 NEARnet Regional Network 2:701(136) Alternet ------------ 198.113.7/24 MMC-7 (US) 198.113.8/24 MMC-8 (US) 198.113.9/24 MMC-9 (US) Mass. Education Computer Network, 75 Arlington Street, Boston, MA 02116, USA 1:560 NEARnet Regional Network 2:701(136) Alternet ------------ 199.93.64/24 MASS-64 (US) 199.93.65/24 MASS-65 (US) MicroPatent, 250 Dodge Avenue, East Haven, CT 06512, USA 1:2551(229) NETCOM 2:2551(136) NETCOM 3:1321 ANS San Francisco - DNSS 11 ------------- 204.17.221/24 MICROPATENT (US) Mid-America Manufacturing Technology Center, 4747 Troost Avenue, Kansas City, MO 64110, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ----------- 204.56.3/24 MAMTC.GEN.MO.US (US) NASA/Johnson Space Center, NASA Road 1, Building 17, Houston, TX 77058, USA 1:771 Nasa Science Network (Houston) 2:372 Nasa Science Network (FIX-West) 3:297 Nasa Science Network (FIX-East) ------------ 192.52.88/24 DMSTST17 (US) 192.52.89/24 DMSTST9 (US) 192.52.90/24 DMSTST16A1 (US) 192.52.91/24 DMSTST32 (US) 192.52.93/24 DMSTST36 (US) 192.52.94/24 DMSTSTB (US) 192.52.95/24 DMSTST16A2 (US) NYS Dept of Civil Service, Bldg 1 State Office Campus, Albany, NY 12239, USA 1:1324 ANS New York City - DNSS 35 ------------- 199.196.21/24 NYS-DCS (US) Nelson-Atkins Museum of Art, 4525 Oak Street, Kansas City, MO 64111, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ----------- 204.56.5/24 NAMA.MUS.MO.US (US) Northwestern University, 2129 N. Campus Drive, Evanston, IL 60208, USA 1:1225 CICNET at Argonne Labs 2:267 CICNET at UIUC 3:266 CICNET at MERIT -------------- 199.249.165/24 NWURH2 (US) 199.249.166/24 NWURH3 (US) 199.249.167/24 NWURH4 (US) 199.249.168/24 NWURH5 (US) 199.249.169/24 NWURH6 (US) Pacific Institute for Research and Evaluation, 7315 Wisconsin Avenue, Bethesda, MD 20814, USA 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) ------------ 199.75.24/24 PIRE-ORG (US) Plains Petroleum Operating Co, 12596 W. Bayaud Ste 250, Lakewood, CO 80228, USA 1:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 2:210 Westnet Regional Network (Utah Attachment) - ENSS 142 -------------- 192.203.248/24 PPOC2 (US) Powersoft Corp., 561 Virginia Road, Concord, MA 01742, USA 1:560 NEARnet Regional Network 2:701(136) Alternet ------------- 199.93.176/24 POWERSOFT-NET1176 (US) 199.93.177/24 POWERSOFT-NET1177 (US) 199.93.178/24 POWERSOFT-NET1178 (US) 199.93.179/24 POWERSOFT-NET1179 (US) RR Donnelley Database Technology Services, 7501 S.Quincy St., Willowbrook, IL 60521, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ----------- 204.4.33/24 PSINET (US) Satel Corporation, 5284 S 320 W Suite C-294, Salt Lake City, UT 84107, USA 1:210 Westnet Regional Network (Utah Attachment) - ENSS 142 2:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 -------------- 199.165.191/24 SATEL-C (US) School Board of Levy County, P.O. Box 220, Bronson, FL 32621, USA 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) ------------- 198.78.224/20 LEVY-K12-FL-US (US) School District of Volusia County, 200 N. Clara Avenue, Deland, FL 32720, USA 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) --------- 167.93/16 VOLUSIA (US) Solectron Corporation, 847 Gibraltar Drive, Milipitas, CA 95035, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ----------- 204.4.37/24 PSINET (US) SpaceCom Systems, 7140 South Lewis, Tulsa, OK 74136, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ----------- 204.4.32/24 PSINET (US) Sprint International, 12490 Sunrise Valley Drive, Reston, VA 22096, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ------------- 199.184.32/20 SI-HQ-CBLOCK (US) 199.184.48/21 SI-HQ-CBLOCK (US) 199.184.56/22 SI-HQ-CBLOCK (US) 199.184.60/23 SI-HQ-CBLOCK (US) 199.184.62/24 SI-HQ-CBLOCK (US) 199.184.63/24 SI-HQ-CBLOCK (US) Technetics Corporation, 5800 Arlington Avenue, Riverdale, NY 10471, USA 1:701(136) Alternet 2:701(134) Alternet ------------- 198.22.191/24 TCNET-2 (US) 198.22.192/24 TCNET-3 (US) The California State University Network CSU Office of the Chancellor, 2201 Blue Gum Ave., Modesto, CA 95352, USA 1:2150 CSUNET-SW -------------- 198.189.194/24 NETBLK-CSUNET-NORTH (US) Triticom, 11800 SingleTree Ln., Suite 310, Eden Prairie, MN 55344, USA 1:1225 CICNET at Argonne Labs 2:267 CICNET at UIUC 3:266 CICNET at MERIT 4:555 Minnesota Supercomputer Center Network (MSCNet) ------------- 204.72.168/22 TRITICOM1 (US) UCSF Medical Education Program, 2615 E Clinton Ave, Fresno, CA 93703, USA 1:2150 CSUNET-SW -------------- 198.175.158/24 UCSFRESNO (US) UGC Consulting, 6200 South Syracuse Way, Suite 222, Englewood, CO 80021, USA 1:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 2:210 Westnet Regional Network (Utah Attachment) - ENSS 142 ------------- 198.62.195/24 UGC-CONSULTING (US) University of Mississippi Medical Center, Computer Services 2500 N. State St., Jackson, MS 39216-4505, USA 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) -------------- 192.207.213/24 UMSMEDCTR4 (US) Us Customs, 5020 S. Meridian, Oklahoma City, OK 73119, USA 1:2551(229) NETCOM 2:2551(136) NETCOM 3:1321 ANS San Francisco - DNSS 11 -------------- 199.201.214/24 CUSTOMS-C3I (US) a2i communications, 1211 Park Avenue, Suite 202, San Jose, CA 95126, USA 1:1957 ANSCIX-AS 2:1800 ICM-Atlantic 3:1240 ICM-Pacific ------------ 204.95.64/20 A2I (US) AS690 CIDR Squeezings Report: 7167 Nets, 95 ASs, 1467 Aggregates ----------------------------------------------------------------- 7167 (77%) of the ever-announced more-specific routes within aggregates have been withdrawn. 509 of those were withdrawn within the last week. 527 the week before that. 263 the week before that. 95 ASs have registered aggregates in the PRDB. 87 of those are announcing aggregates. 50 have withdrawn at least one more specific route. 1467 Aggregates are configured. 1274 of these were Top-Level Aggregates (not nested in another aggregate). 1027 of these are being announced to AS690. 843 of those have at least one subnet configured (the other 184 may be saving the Internet future subnet announcements). 680 have stopped announcing at least one configured more specific route. 652 have stopped announcing half of their configured more specific routes. 615 have stopped announcing most (80%) of their more specific routes. See merit.edu:pub/nsfnet/cidr/cidr_savings for more detail. ----------------------------------------------------------- ========================================================== The configuration reports which reflect today's update will be available for anonymous ftp on nic.merit.edu by 08:00 EDT: configuration reports -- nic.merit.edu:nsfnet/announced.networks: as-as.now as-gw.now ans_core.now country.now net-comp.now nets.doc nets.non-classful nets.tag.now nets.unl.now NSS routing software configuration files -- nic.merit.edu:nsfnet/backbone.configuration: gated.nss<NSS number>.t3p Information is also avaiable through the PRDB whois server. Type "whois -h prdb.merit.edu help" for details. -------------------------------------------------------------------------- REPORT CHANGES: (Updated May 31, 1994) Anyone considering configuring an aggregate into the PRDB (and you all should be!) is encouraged to pre-check that aggregate by typing the command: whois -h prdb.merit.edu 'aggchk <agg>' (where "<agg>" is the aggregate description). This command will list all of the other entries in the PRDB that are more specific routes of <agg>, as well as any aggregates all ready configured that contain <agg>. The output includes the AUP and announcement lists of each of the nets printed, with discrepancies flagged. This is the same program that we use for sanity-checking the NACRs that you submit. The archived discussion list "db-disc(a)merit.edu" exists for discussion of PRDB issues. Send a message to "db-disc-request(a)merit.edu" to subscribe. --Dale Johnson (dsj(a)merit.edu) -------------------------------------------------------------------------- Please send all requests for configuration changes to nsfnet-admin(a)merit.edu using the NSFNET configuration forms. The forms are available on-line from the nic.merit.edu machine. Use ftp and the anonymous login to get on the machine. Do a "cd nsfnet/announced.networks" and get the files template.net, template.net.README, template.gate, and template.as. *** Note: As of March 1, 1994, NSFNET AUP NACRs must use the template.net *** (NACR) version 7.1, or the NACR will be returned unprocessed. ******************************* --Steve Widmayer Merit/NSFNET skw(a)merit.edu --Enke Chen Merit/NSFNET enke(a)merit.edu --Steven J. Richardson Merit/NSFNET sjr(a)merit.edu

1 0

Re: Comments
by tjs＠msc.edu 02 Sep '94

02 Sep '94

> From: bmanning(a)ISI.EDU > Subject: Re: Comments > To: ltwu(a)faline.bellcore.com (Liang T. Wu) > Date: Tue, 30 Aug 1994 08:07:28 -0700 (PDT) > Cc: bmanning(a)ISI.EDU, iepg(a)iepg.org, nanog(a)merit.edu, nap-info(a)merit.edu > > Thank you for your insightful comments. I would like to be enlightened > on exactly how a proposed migration from RFC1490 to RFC1483/1577 will > occur. As I understand it, there needs to be a translation method > between NLPID and LLC/SNAP. There seem to be other locations in the > stack where translation must occur. Is there capability today or even > planned that will do these translations? > [...] I would migrate, rather than translate. Depending on the Cisco 7000 HSSI and/or AIP microcode, an ATM NAP could migrate a PVC at a time or the whole NAP at once. I assume that this migration will occur before NAPs become very large. [By the way, translation between RFC 1490 (NLPID) and RFC 1577 (LLN/SNAP) is still an issue for frame relay interworking units, even if it isn't required for 1490-1577 migration in an ATM-only NAP.] -tjs

2 1

Re: Comments
by ltwu＠faline.bellcore.com 01 Sep '94

01 Sep '94

Curtis, We have done tests on two switches with various configurations - 10 sparcstaions, 3 7000's, AGS+, Kentrox, as well as other boxes for bridging protocol stacks. We have not yet artificially insert 70 msec delay. With your request, we will get on to that ASAP. One question here: since we are happy with what we found out so far in the lab it would be nice if we move the tests closer and closer to the real environment. I heard you have a test network. Can I connect my NAP prototype at Morristown NJ to your test network to study the effect of cross country delay? Liang

3 2

Re: Comments
by tjs＠msc.edu 01 Sep '94

01 Sep '94

> From: bmanning(a)ISI.EDU > Subject: Comments > To: nanog(a)merit.edu, iepg(a)iepg.org > Date: Tue, 30 Aug 1994 03:28:33 -0700 (PDT) > Cc: nap-info(a)merit.edu > > [...] > The difficulties with the RFC 1490 approach were listed in the > Toronto meeting. I list them here: > > There is no clear migration path from this approach to > a more correct/robust implementation using RFC 1577 > encapsulation over native ATM (OC3c). The migration from RFC 1490 to RFC 1577 is probably straight forward. Cisco has promised RFC 1577 microcode (for PVCs only) for their HSSI interface. Therefore, one [clear] migration path is to upgrade the HSSI microcode when it is available and stable, and then migrate from RFC 1490 to RFC 1577. By the way, it should be noted that the Cisco 7000-series router is the only router that any NSP has indicated that they will use to connect to an ATM NAP. Note that the router selection was made by the NSPs, not the NAP managers. > There are additional points of failure and additional costs > with the requirement for an ADSU. Compared to what? There is a strong desire to use existing, released products which can connect to a DS-3 ATM switch as soon as possible. This rather limits the options. > The listed approach requires manual configuration. Again, compared to what? There will be considerable manual configuration in the initial ATM NAPs, (e.g., PVCs). > This appears to lock the NAP into a top speed of 45Mbps > or DS3 speeds. I don't understand your point. The migration to OC-3c will be straight forward, (e.g., pull out board A, insert board B), particularly after the planned 1490/1577 migration. > In addition to these weaknesses, there were a number of assumptions > regarding specific hardware implementations of ATM protocols (use > of a very small selection of vendors and limited interfaces) and > the ability and/or willingness of the attaching ISPs to work toward > a more elegant, cheaper, robust solution at the possible expense of > some time while vendors address the implementation gaps. As I indicated above, the Cisco 7000 was the choice of the NSPs. There is also a strong desire among those involved to implement the new NSFNET architecture as soon as possible, (which implies using existing, released products). > Questions on the desirability of a native media support with RFC 1577 > support were posted to the IP-ATM wg of the IETF and the > email response was affirmative in recommending an approach with > RFC 1483/1577 over AAL5 with LLC/SNAP coding. > [...] As you know, everyone involved intends to migrate to RFC 1577. Initial deployment of RFC 1577, rather than RFC 1490, conflicts with the objectives of using existing, released products, implementing ATM NAPs as soon as possible, and supporting DS-3 ATM interfaces. -tjs

1 0

Re: Comments
by tjs＠msc.edu 01 Sep '94

01 Sep '94

> To: bmanning(a)isi.edu (Bill Manning) > Cc: ltwu(a)faline.bellcore.com, iepg(a)iepg.org, nanog(a)merit.edu, > nap-info(a)merit.edu > Subject: Re: Comments > Date: Wed, 31 Aug 94 16:18:23 -0700 > [...] > The issue behind the NAP's is that they could have been engineered to > use simpler and more mature interconnect technology at the start, but > are instead using immature technology to meet non-technical requirements > that the customers of the NAPs are not they themselves imposing. > [...] The Sprint NAP is using FDDI initially. -tjs

5 5

Re: Comments
by schnell＠sprintlink.net 01 Sep '94

01 Sep '94

At 04:51 09.01.94 -0700, Bill Manning wrote: >Actually, MFS is also playing the FDDI game. In addition, the have ethernet >attachments as well. IMHO, (and speaking just for me), this NAP has the >most flexable attachment policy. Thats 50% of the NAPS w/ something other >than ATM day one. > >-- >--bill Sprint's NAP also features support for Ethernet connections. steve

1 0

Aggis 2.0, for Manipulating CIDR Address Ranges
by Dale S. Johnson 30 Aug '94

30 Aug '94

I've posted a new version of "aggis" on merit.edu:pub/nsfnet/cidr/aggis (and a man page in aggis.l). Aggis is a small perl program for expanding CIDR aggregate notation into classful IP net ranges, and for helping to IP net ranges into aggregates. This version 2.1 handles all of the cases that the old version (released last February) would. In addition, it: - Handles full "x.x.x.x - y.y.y.y" notation - Expands subaggregates into host IP ranges, rather than only saying that they are subaggregates - Has "-q" flag for "produce full 4-byte dotted quad output", and "-r" for "always produce expansions in host address ranges" (instead of classful net ranges). If you would like to try the program without installing it locally, it can be run through the prdb.merit.edu whois server: >> $ whois -h prdb.merit.edu 'aggis 141.208.32/21' >> >> 141.208.32/21 is a subnet representing 1/32 of Class B network 141.208 >> >> Address Range 141.208.32.0 - 141.208.39.255 >> >> $ whois -h prdb.merit.edu 'aggis 141.208 - 141.216' >> >> The range of nets from 141.208 to 141.216/16 can be represented by: >> >> 141.208/13 ( 8 nets: 141.208 - 141.215 ) >> 141.216/16 ( 1 net: 141.216 ) --Dale Johnson Merit

1 0

Re: Comments
by ltwu＠faline.bellcore.com 30 Aug '94

30 Aug '94

>From bmanning(a)ISI.EDU Tue Aug 30 11:08:01 1994 >Subject: Re: Comments >To: ltwu(a)faline.bellcore.com (Liang T. Wu) > >Thank you for your insightful comments. I would like to be enlightened >on exactly how a proposed migration from RFC1490 to RFC1483/1577 will >occur. As I understand it, there needs to be a translation method >between NLPID and LLC/SNAP. There seem to be other locations in the >stack where translation must occur. Is there capability today or even >planned that will do these translations? > I understand Cascade claims to have such boxes. >> > There is no clear migration path from this approach to >> > a more correct/robust implementation using RFC 1577 >> > encapsulation over native ATM (OC3c). >> >> My conversation with Cisco indicates that 1490/AAL5 software patch for >> AIP is available and 1483/AAL5 for ADSU and 1483/AAL5 for T3-AIP should >> be available withing about 6 months. So, indeed ther are several migration >> path available, not clear which is the best for all NAPs. Perhaps different >> NAP location may have different business needs based on what their customers >> desire. > >True. > >> > There are additional points of failure and additional costs >> > with the requirement for an ADSU. >> >> I think HSSI is a proven technology. HSSI/ADSU probably has lower >> failure rate than AIP based on the typical bath tub curb for new product >> reliablity. > >The points of failure are the additional cables and connectors, not to mention >the electrionics of a seperate box (the ADSU) and power. These cost, plus >the extra rack space and potential co-location fees to accomodate this extra >gear. Your concerns wrt infant mortality on new hardware seem to apply >to the ATM switches in general. Most of the equipment, while being >"long in the tooth" as far as cell switching capability is concerned, has a >-very- limited exposure to data transmission. Even the closed ATM Forum >has trouble standardizing specs that appear to be needed to support full >interoperability (just when will UNI3.1 come out and when will the text >be available on-line?... but I digress) > We need to separate out issues regarding ATM switches and ATM interfaces for routers. We have been dealing with ATM switches since 1982, at that time we call it Fast Packet Switch. So, we know much more about it and have trained scores of experts to deal with it. The commercial grade ATM switch that we are dealing with now for NAP are designed based on CO requirement, meaning it is overbuild and modularized based on certain engineering practice and has been tested extensively by telcos. The biggest issue now is to regineering the equipment for AAL5 type traffic since most of the switches were designed for "isochronous" traffic at the beginning. Router interface is another story. They are new and they interface with heterogenous network world. So, new rules have to be established jointly by data networking and telecomm communities. >> > The listed approach requires manual configuration. >> >> I like the flexibility of AIP, but how to configure AIP to avoid congestion >> is still a research topic for me. > >As it is for everyone. The manual configuration specified here is the need >to code static routes and ARP entries to make BGP4 work. Traffic shaping >does not even come into this equation. > We/NAP people are knowledgeable on "layer 2" and are eager to learn about the layer 3 problems. We like to help if we can. Let me know how can we get involved with the BGP4 development from layer 2 point of view. >> > This appears to lock the NAP into a top speed of 45Mbps >> > or DS3 speeds. >> >> Hopefully, we can unlock this as soon as we feel comfortable with other >> approaches. > >HISSI at faster than 45Meg? I am very interested. >Please tell me more. > I did not mean that. But HISSI at SONET rate may have some nich in the market. It is a marketing decision for router guys. >> >> BTW, I think the Merit paper is useful and good work as you said. Since >> RFC1490 is the only viable option exposed to Merit, saying it is one of those >> is a bit too harsh. >> > >Perhaps. My biggest concern was that the Merit paper would be construed as >the -only- way an ATM NAP would work. They clearly did not indicate there >were potential choices nor did they indicate the assumptions that were made >for their test. > >-- >--bill >

1 0

Comments
by bmanning＠ISI.EDU 30 Aug '94

30 Aug '94

A commentary on "A Routing Design for ATM NAPS" Bill Manning bmanning(a)isi.edu 23 August 1994 Abstract: Attempts to clarify the important points in this document and proposes an alternative that can be deployed in a reasonable timeframe. Commentary: This is an interesting and useful paper. It covers what was current technology in 2q94 and points out one of several methods for supporting ATM in the context of a Routing Registry/Route Server. Several clever approaches were used to overcome gaps in standards implementation by vendors. The approach indicated in section two of the MERIT paper is a common approach that was generally approved in both the NANOG meeting and a NAP participant meeting that was held during the Toronto IETF. The difficulties with the RFC 1490 approach were listed in the Toronto meeting. I list them here: There is no clear migration path from this approach to a more correct/robust implementation using RFC 1577 encapsulation over native ATM (OC3c). There are additional points of failure and additional costs with the requirement for an ADSU. The listed approach requires manual configuration. This appears to lock the NAP into a top speed of 45Mbps or DS3 speeds. In addition to these weaknesses, there were a number of assumptions regarding specific hardware implementations of ATM protocols (use of a very small selection of vendors and limited interfaces) and the ability and/or willingness of the attaching ISPs to work toward a more elegant, cheaper, robust solution at the possible expense of some time while vendors address the implementation gaps. Questions on the desirability of a native media support with RFC 1577 support were posted to the IP-ATM wg of the IETF and the email response was affirmative in recommending an approach with RFC 1483/1577 over AAL5 with LLC/SNAP coding. A brief review of the European PNO pilots seems to indicate that this is the desired approach in that arena too. Even the vendors who were not invited to either meeting have expressed an interest in fixing these problems in the near term, where near term is the next 2 to 6 months. So, I suggest the MERIT paper should not be viewed as the only or desired method of connecting to an ATM NAP. It should be carefully read as the documentation of a successful experiment. --bill

2 1