Test
Threads by month
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2008 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2007 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2006 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2005 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2004 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2003 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2002 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2001 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2000 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 1999 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 1998 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 1997 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 1996 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 1995 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 1994 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 1993 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 1992 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- 1 participants
- 54023 discussions
> Date: Thu, 27 Oct 1994 14:43:37 -0400
> From: Vadim Antonov <avg(a)sprint.net>
> To: nanog(a)merit.edu, schoff(a)us.psi.com, sesqui-all(a)ns.sesqui.net,
> sob(a)academ.com
> Subject: Re: wiretapping continues....
> Cc: psieng(a)psi.com
> [...]
> We will hit limitations of the present/then-future routing technology
> long before we'll exhaust the possibilities to increase the
> NAP aggregate and access bandwidth by cheap incremental upgrades.
> That's the whole point of Sprint NAP architecture. ATM/SMDS/Flame Delay
> do not get even close to what we achieve (and ATM is not useful yet).
> [...]
I believe that ATM, even in its perhaps immature state, is useful and
cost-effective in a number of applications today. In particular,
the cost of wide-area DS-3 ATM services can be very attractive
when compared to a number of point-to-point DS-3s.
-tjs
2
1
At 12:38 PM 10/28/94, John Scudder wrote:
>Mark writes:
>> Since it is not possible or desirable for NAP providers to collect
>> statistics on IP source/destination pairs, protocol types, or per-NSP
>> datagram counts,
>[...]
>
>Reasonable people disagree as to whether it's desirable.
John,
This is actually an important point. It may be desirable to the
community, but not to our customers who are buying NAP service. Our first
priority has to be to our customers, though we hope we can fulfill the goal
of assisting the Internet community in the process.
>
>Possible (or at least feasible) I'll give you, so the point is pretty
>much moot.
Not totally sure if you were agreeing or disagreeing. ATM NAP providers
at least would have a hard time looking at datagrams as a whole to do
"wiretapping". Maybe we can give you the average number of 1's and 0's in
each cell?
>
>--John
Mark
2
1
> John Scudder then discussed some modeling he and Sue Hares have done
> on the projected load at the NAPs. The basic conclusions are that the
> FDDI technology (at Sprint) will be saturated sometime next year and
> that load-balancing strategies among NSPs across the NAPS is
> imperative for the long term viability of the new architecture. John
> also expressed concern over the lack of expressed policy for
> the collection of statistical data by the NAP operators. All of the
> NAP operator are present and stated that they will collect data, but
> that there are serious and open questions concerning the privacy of
> that data and how to publish it appropriately. John said that
> collecting the data was most important. Without the data, there is
> no source information from which publication become possible. He said
> that MERIT/NSFNET had already tackled these issues. Maybe the
> NAP operators can use this previous work as a model to develop their
> own policies for publication.
>
Merit/NSFNet already tackled these issues in an insufficent and unopen manner.
MarkFedor/ColeLibby from PSI said there was a "quiet" admission that the old
methodology was already "approved" for the SPRINT NAP.
Marty
4
3
At 9:48 AM 10/27/94, Martin L. Schoffstall wrote:
>Merit/NSFNet already tackled these issues in an insufficent and unopen manner.
>
>MarkFedor/ColeLibby from PSI said there was a "quiet" admission that the old
>methodology was already "approved" for the SPRINT NAP.
>
>Marty
Since it is not possible or desirable for NAP providers to collect
statistics on IP source/destination pairs, protocol types, or per-NSP
datagram counts, it seems that a different mechanism would be needed to do
engineering analyses to manage Internet performance and growth. The NSFNET
mechanism which used a device at each regional DMZ (nnstat or equivalent)
seemed like a good mechanism to do that, especially given the
research/education focus of the regionals. I suggest that it would be very
difficult to do this sort of monitoring on commercial networks. Why not
continue the NSFNET sponsored and approved method of placing collectors at
NSF-supported regional network DMZs even after the NSFNET transition, so
that we have at least a sampling of Internet traffic measurements.
Mark
2
1
Guy,
Thanks for your support. We were able to use the test results to define
PacBell's next phase NAP requirements.
Frank
1
0
------------------------------------------------------------------------------
The PRDB and this "NWG report" will be retired in December. 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 41519 = 30 5063 34514 1912
Configured Networks 39004 = 30 5008 32076 1890
Added Networks 258 = 0 7 219 32
Deleted Networks 0 = 0 0 0 0
IP address Net name Country Priority:AS
---------- -------- ------- -----------
141.171/16 SULZERCH C:CH 1:701(136) 2:701(134) 3:1800
142.135/16 ALCIDE-2 C:CA 1:577(137) 2:577(133) 3:577(143)
147.67/16 EC-RD-NETWORK C:BE 1:1800 2:1133 3:1674 4:1240
148.56/16 VAINET C:AT 1:701(136) 2:701(134) 3:1800
151.208/16 GILLETTE C:US 1:1957
162.73/16 MOLSON-NET C:CA 1:2493(35) 2:2493(91)
168.98/16 NET-JDNET C:US 1:1239 2:1800 3:1240
192.26.135/24 RATOL1 C:FI 1:701(136) 2:701(134) 3:1800
192.45/16 TRW-CNETS C:US 1:1740
192.81.166/24 MSPB-HP C:US 1:1800 2:1240 3:1239
192.84.222/24 NET-TRIBASE C:US 1:93
192.89.108/24 KUNTALIITTO-NET C:FI 1:701(136) 2:701(134)
192.104.165/24 MAACO C:US 1:701(136) 2:701(134)
192.111.112/24 ALASU C:US 1:279 2:86
192.160.233/24 SU-IHEP C:RU 1:701(136) 2:701(134) 3:1800
192.251.193/24 NET-HAVEN-NET C:US 1:1239 2:1800 3:1240
193.28.96/21 DETDSH71 C:DE 1:1324(32) 2:1324(35) 3:1800 4:1240
5:1133
193.50.209/24 FR-URCA2 C:FR 1:1800 2:1240 3:1133 4:1674
193.50.210/24 FR-URCA3 C:FR 1:1800 2:1240 3:1133 4:1674
193.50.211/24 FR-URCA4 C:FR 1:1800 2:1240 3:1133 4:1674
193.50.212/24 FR-URCA5 C:FR 1:1800 2:1240 3:1133 4:1674
193.50.213/24 FR-URCA6 C:FR 1:1800 2:1240 3:1133 4:1674
193.50.214/24 FR-URCA7 C:FR 1:1800 2:1240 3:1133 4:1674
193.76.255/24 IUNET-NET-3 C:IT 1:701(136) 2:701(134) 3:1800
193.80.190/24 OKA-NET C:AT 1:701(136) 2:701(134) 3:1800
193.80.202/24 OKA-NET C:AT 1:701(136) 2:701(134) 3:1800
193.125.170/24 LVS C:RU 1:701(136) 2:701(134) 3:1800
193.125.171/24 LVS C:RU 1:701(136) 2:701(134) 3:1800
193.130.226/23 RADSTONE C:GB 1:1849 2:701(136) 3:701(134) 4:1800
193.146/16 REDIRIS-PROVIDER-BLK3 C:ES 1:1800 2:1133 3:1674 4:1240
193.185.155/24 RAUMA-NET3 C:FI 1:701(136) 2:701(134) 3:1800
193.188.7/24 INRA-NET C:MA 1:1800 2:1240 3:1133 4:1674
193.224.128/24 SZIF-NET C:HU 1:1800 2:1133 3:1674 4:1240
193.224.129/24 SZIF-NET C:HU 1:1800 2:1133 3:1674 4:1240
193.224.130/24 SZIF-NET C:HU 1:1800 2:1133 3:1674 4:1240
193.224.131/24 SZIF-NET C:HU 1:1800 2:1133 3:1674 4:1240
193.232.226/24 COMPNET C:RU 1:701(136) 2:701(134) 3:1800
194.51.17/24 FR-AFNOR C:FR 1:1800 2:1240 3:1133 4:1674
194.51.20/24 FR-UPLIFT C:FR 1:1800 2:1240 3:1133 4:1674
194.57.52/24 FR-CCIP-1 C:FR 1:1800 2:1240 3:1133 4:1674
194.57.53/24 FR-CCIP-1 C:FR 1:1800 2:1240 3:1133 4:1674
194.57.54/24 FR-CCIP-1 C:FR 1:1800 2:1240 3:1133 4:1674
194.57.55/24 FR-CCIP-1 C:FR 1:1800 2:1240 3:1133 4:1674
194.57.56/24 FR-CCIP-1 C:FR 1:1800 2:1240 3:1133 4:1674
194.57.58/24 FR-CCIP-1 C:FR 1:1800 2:1240 3:1133 4:1674
194.57.59/24 FR-CCIP-1 C:FR 1:1800 2:1240 3:1133 4:1674
194.57.92/24 FR-CCIP-2 C:FR 1:1800 2:1240 3:1133 4:1674
194.57.93/24 FR-CCIP-2 C:FR 1:1800 2:1240 3:1133 4:1674
194.57.94/24 FR-CCIP-2 C:FR 1:1800 2:1240 3:1133 4:1674
194.57.95/24 FR-CCIP-2 C:FR 1:1800 2:1240 3:1133 4:1674
194.57.96/24 FR-CCIP-2 C:FR 1:1800 2:1240 3:1133 4:1674
194.57.97/24 FR-CCIP-2 C:FR 1:1800 2:1240 3:1133 4:1674
194.57.98/24 FR-CCIP-2 C:FR 1:1800 2:1240 3:1133 4:1674
194.57.99/24 FR-CCIP-2 C:FR 1:1800 2:1240 3:1133 4:1674
194.57.100/24 FR-CCIP-2 C:FR 1:1800 2:1240 3:1133 4:1674
194.57.101/24 FR-CCIP-2 C:FR 1:1800 2:1240 3:1133 4:1674
194.57.102/24 FR-CCIP-2 C:FR 1:1800 2:1240 3:1133 4:1674
194.57.103/24 FR-URCA C:FR 1:1800 2:1240 3:1133 4:1674
194.57.104/24 FR-URCA C:FR 1:1800 2:1240 3:1133 4:1674
194.57.105/24 FR-URCA C:FR 1:1800 2:1240 3:1133 4:1674
194.86/16 EUNET-FI-194.86-AGG C:FI 1:701(136) 2:701(134) 3:1800
194.98.0/21 IWAY-NET C:FR 1:1800 2:1240 3:1133 4:1674
198.5.244/24 NAECKER-NET C:US 1:701(136) 2:701(134)
198.5.245/24 NAECKER-NET C:US 1:701(136) 2:701(134)
198.5.246/24 NAECKER-NET C:US 1:701(136) 2:701(134)
198.5.247/24 NAECKER-NET C:US 1:701(136) 2:701(134)
198.98.33/24 ROCKHURST1 C:US 1:93
198.152.97/24 NETBLK-ATT-CBLOCK C:US 1:1321 2:2386
198.189.146/24 CSUNET-NORTH-189-146 C:US 1:2150
198.189.147/24 CSUNET-NORTH-189-147 C:US 1:2150
198.189.148/24 CSUNET-NORTH-189-148 C:US 1:2150
198.189.149/24 CSUNET-NORTH-189-149 C:US 1:2150
198.189.150/24 CSUNET-NORTH-189-150 C:US 1:2150
198.189.151/24 CSUNET-NORTH-189-151 C:US 1:2150
198.189.152/24 CSUNET-NORTH-189-152 C:US 1:2150
198.189.153/24 CSUNET-NORTH-189-153 C:US 1:2150
198.189.154/24 CSUNET-NORTH-189-154 C:US 1:2150
198.189.155/24 CSUNET-NORTH-189-155 C:US 1:2150
198.189.156/24 CSUNET-NORTH-189-156 C:US 1:2150
198.189.159/24 CSUNET-NORTH-189-159 C:US 1:2150
198.189.160/24 CSUNET-NORTH-189-160 C:US 1:2150
198.189.161/24 CSUNET-NORTH-189-161 C:US 1:2150
198.189.163/24 CSUNET-NORTH-189-163 C:US 1:2150
198.189.164/24 CSUNET-NORTH-189-164 C:US 1:2150
198.189.165/24 CSUNET-NORTH-189-165 C:US 1:2150
198.235.51/24 NETRON C:CA 1:1240 2:1800 3:1239
198.235.70/24 NET-BELLCAN33 C:CA 1:701(136) 2:701(134)
198.246.177/24 NMS01 C:US 1:1225 2:267 3:266 4:555
199.0.158/23 GLOBALNET2-DOM C:US 1:1800 2:1240 3:1239
199.1.158/24 NET-EDSWORLD C:US 1:1800 2:1240 3:1239
199.1.204/24 SPRINT-C701CF C:US 1:1240 2:1800
199.1.205/24 SPRINT-C701CF C:US 1:1240 2:1800
199.48.8/22 NETBLK-STARNET3 C:US 1:1240 2:1800 3:1239
199.48.12/24 NETBLK-STARNET3 C:US 1:1240 2:1800 3:1239
199.60.117/24 NETINTERIOR C:CA 1:577(143) 2:577(133) 3:577(137)
199.60.121/24 BCFORESTS C:CA 1:577(143) 2:577(133) 3:577(137)
199.60.124/24 NETBLK-TELESERVE C:CA 1:577(143) 2:577(133) 3:577(137)
199.60.125/24 NETBLK-TELESERVE C:CA 1:577(143) 2:577(133) 3:577(137)
199.60.126/24 NETBLK-TELESERVE C:CA 1:577(143) 2:577(133) 3:577(137)
199.60.127/24 NETBLK-TELESERVE C:CA 1:577(143) 2:577(133) 3:577(137)
199.60.230/24 NETBLK-ISLAND-NET1 C:CA 1:577(143) 2:577(133) 3:577(137)
199.77.42/24(U) GSA-TUSCALOOSA-AL-US C:US 1:279 2:86
199.77.44/23(U) NETBLK-EBSCO-CIDR1 C:US 1:279 2:86
199.78.224/24(U) NASHVILLE-COM C:US 1:279 2:86
199.78.226/24(U) PLANETC-COM C:US 1:279 2:86
199.93.162/24 BOSNET C:US 1:560 2:701(136) 3:701(134)
199.93.200/24 FIDELITY C:US 1:560 2:701(136) 3:701(134)
199.94.65/24 EMERSON-65 C:US 1:560
199.94.66/24 EMERSON-66 C:US 1:560
199.94.128/24 NET-JCP1 C:US 1:560 2:701(136) 3:701(134)
199.94.129/24 NET-JCP2 C:US 1:560 2:701(136) 3:701(134)
199.94.152/24 JACKSON-152 C:US 1:560
199.94.153/24 JACKSON-153 C:US 1:560
199.94.154/24 JACKSON-154 C:US 1:560
199.94.155/24 JACKSON-155 C:US 1:560
199.94.156/24 JACKSON-156 C:US 1:560
199.164.64/18 PASCO-K12-FL C:US 1:279 2:86
199.166.230/24 NETBLK-MAGIC-ONLINE C:CA 1:701(136) 2:701(134)
199.166.231/24 NETBLK-MAGIC-ONLINE C:CA 1:701(136) 2:701(134)
199.166.232/24 NETBLK-MAGIC-ONLINE C:CA 1:701(136) 2:701(134)
199.166.233/24 NETBLK-MAGIC-ONLINE C:CA 1:701(136) 2:701(134)
199.170.210/24 GFN-NET C:US 1:701(136) 2:701(134)
199.171.220/24 DIAMOND-NET C:US 1:701(136) 2:701(134)
199.172.61/24 AVICENNA-NET C:US 1:701(136) 2:701(134)
199.172.191/24 WSNET C:US 1:701(136) 2:701(134)
199.173.152/24 STRATEGY-NET C:US 1:701(136) 2:701(134)
199.174.45/24 NET-COMSOFT-MGMT C:US 1:1240 2:1800 3:1239
199.199.25/24 EXYSNICHE C:US 1:1225 2:267 3:266 4:555
199.199.26/24 NEWSTANDARDS-NET C:US 1:1225 2:267 3:266 4:555
199.199.28/24 NCBC C:US 1:1225 2:267 3:266 4:555
199.199.29/24 GLOBELLE C:US 1:1225 2:267 3:266 4:555
199.199.30/24 NMS02 C:US 1:1225 2:267 3:266 4:555
199.202.116/24 INTERLINK C:CA 1:2493(35) 2:2493(91)
199.202.117/24 INTERLINK C:CA 1:2493(35) 2:2493(91)
199.202.118/24 INTERLINK C:CA 1:2493(35) 2:2493(91)
199.202.119/24 INTERLINK C:CA 1:2493(35) 2:2493(91)
199.202.120/24 INTERLINK C:CA 1:2493(35) 2:2493(91)
199.202.121/24 INTERLINK C:CA 1:2493(35) 2:2493(91)
199.202.122/24 INTERLINK C:CA 1:2493(35) 2:2493(91)
199.202.123/24 INTERLINK C:CA 1:2493(35) 2:2493(91)
199.202.124/24 INTERLINK C:CA 1:2493(35) 2:2493(91)
199.202.125/24 INTERLINK C:CA 1:2493(35) 2:2493(91)
199.202.126/24 INTERLINK C:CA 1:2493(35) 2:2493(91)
199.202.127/24 INTERLINK C:CA 1:2493(35) 2:2493(91)
199.202.128/24 INTERLINK C:CA 1:2493(35) 2:2493(91)
199.202.129/24 INTERLINK C:CA 1:2493(35) 2:2493(91)
199.202.130/24 INTERLINK C:CA 1:2493(35) 2:2493(91)
199.202.131/24 INTERLINK C:CA 1:2493(35) 2:2493(91)
199.202.132/24 INTERLINK C:CA 1:2493(35) 2:2493(91)
199.202.133/24 INTERLINK C:CA 1:2493(35) 2:2493(91)
199.202.134/24 INTERLINK C:CA 1:2493(35) 2:2493(91)
199.202.135/24 INTERLINK C:CA 1:2493(35) 2:2493(91)
199.202.254/24 INTERLINK-NETS C:CA 1:2493(35) 2:2493(91)
199.202.255/24 INTERLINK-NETS C:CA 1:2493(35) 2:2493(91)
199.211.197/24 FTSCPEARLMAIN C:US 1:568 2:19
199.211.198/24 SPECWAR-NET C:US 1:19 2:568
199.212.57/24 CASPAR-NET C:CA 1:577(133) 2:577(137) 3:577(143)
199.212.58/24 OSC-ON-CA-C-212-58 C:CA 1:577(133) 2:577(137) 3:577(143)
199.212.59/24 OSC-ON-CA-C-212-59 C:CA 1:577(133) 2:577(137) 3:577(143)
199.221.26/24 BANAMEX-DMZ C:US 1:1328
199.222.18/24 CENT-NET C:US 1:1333
199.222.19/24 MTC-DMZ1 C:US 1:1333
199.222.20/24 MCT-DMZ2 C:US 1:1333
199.234.106/23 BLACKBOX C:US 1:3577 2:1324(32) 3:1324(35)
199.234.106/24(U) BLACKBOX C:US 1:3577 2:1324(32) 3:1324(35)
199.234.107/24(U) BLACKBOX C:US 1:3577 2:1324(32) 3:1324(35)
199.234.200/22 VOICENET1 C:US 1:1324(32) 2:1324(35) 3:3577
199.234.200/24(U) VOICENET1 C:US 1:1324(32) 2:1324(35) 3:3577
199.234.201/24(U) VOICENET1 C:US 1:1324(32) 2:1324(35) 3:3577
199.234.202/24(U) VOICENET1 C:US 1:1324(32) 2:1324(35) 3:3577
199.234.203/24(U) VOICENET1 C:US 1:1324(32) 2:1324(35) 3:3577
199.234.208/22 PHILSCH C:US 1:1324(32) 2:1324(35) 3:3577
199.234.208/24(U) PHILSCH C:US 1:1324(32) 2:1324(35) 3:3577
199.234.209/24(U) PHILSCH C:US 1:1324(32) 2:1324(35) 3:3577
199.234.210/24(U) PHILSCH C:US 1:1324(32) 2:1324(35) 3:3577
199.234.211/24(U) PHILSCH C:US 1:1324(32) 2:1324(35) 3:3577
199.235.57/24 HALTON-NET C:CA 1:2493(35) 2:2493(91)
199.243.246/23 NETBLK-WORLDLINX C:CA 1:1240 2:1800 3:1239
199.248.165/24 NETBLK-OXY-3 C:US 1:93
199.249.183/24 LAITRAM-NET C:US 1:701(136) 2:701(134)
200.11.32/24 PROMPERU C:PE 1:1800 2:1240 3:1239
200.12.132/24 CECS C:CL 1:86 2:279
202.24.128/24 OKM-NET C:JP 1:2149 2:174
202.24.192/24 NSNET C:JP 1:2149 2:174
202.33.45/24 CYBER-NET C:JP 1:2149 2:174
202.44.68/24 SPU-TH C:TH 1:701(136) 2:701(134)
202.248.30/24 ANDO-NET-C-248-30 C:JP 1:2149 2:174
202.248.31/24 ANDO-NET-C-248-31 C:JP 1:2149 2:174
203.254.53/24 KOISNET1 C:KR 1:372 2:297
203.254.55/24 KOISNET2 C:KR 1:372 2:297
204.4.108/24 PSINET-C4 C:US 1:2149 2:174
204.50.19/24 NET-BRADSON C:CA 1:1240 2:1800 3:1239
204.50.20/24 NET-HMTNET C:CA 1:1240 2:1800 3:1239
204.69.234/24 MAILORDER3 C:US 1:1957
204.72.192/18 METROII1 C:US 1:1225 2:267 3:266 4:555
204.72.196/22 STPAULPS C:US 1:1225 2:267 3:266 4:555
204.72.200/21 STPAULPS C:US 1:1225 2:267 3:266 4:555
204.72.208/20 STPAULPS C:US 1:1225 2:267 3:266 4:555
204.72.224/23 STPAULPS C:US 1:1225 2:267 3:266 4:555
204.72.226/23 ISD621 C:US 1:1225 2:267 3:266 4:555
204.72.228/22 ISD621 C:US 1:1225 2:267 3:266 4:555
204.72.232/22 ISD621 C:US 1:1225 2:267 3:266 4:555
204.72.236/22 RDALEPS C:US 1:1225 2:267 3:266 4:555
204.72.240/22 RDALEPS C:US 1:1225 2:267 3:266 4:555
204.72.244/23 RDALEPS C:US 1:1225 2:267 3:266 4:555
204.73.70/23 PSB1 C:US 1:1225 2:267 3:266 4:555
204.73.73/24 FALLON2 C:US 1:1225 2:267 3:266 4:555
204.73.76/24 FALLON3 C:US 1:1225 2:267 3:266 4:555
204.84/15 NCREN-CIDR3 C:US 1:1329
204.94.69/24 CLONETICS-NET C:US 1:1240 2:1800
204.94.70/24 CYKIC-NET C:US 1:1240 2:1800
204.96.214/24 NET-DATARACE C:US 1:1800 2:1240 3:1239
204.96.224/19 RAIN1-NET C:US 1:1240 2:1800 3:1239
204.107.130/24 SGT C:US 1:1740
204.108.0/24 APM-HQ-FAA C:US 1:1327
204.108.128/17 CHESCONET-2 C:US 1:3577 2:1324(32) 3:1324(35)
204.117.71/24 NET-PEACHWEB C:US 1:1800 2:1240 3:1239
204.117.209/24 NET-IS5 C:US 1:1800 2:1240 3:1239
204.118.132/24 FTVCVR-A C:US 1:1240 2:1800 3:1239
204.118.133/24 FTVCVR-B C:US 1:1240 2:1800 3:1239
204.138.237/24 JMG-COM C:CA 1:1240 2:1800 3:1239
204.138.238/24 SHOPEX-COM C:CA 1:1240 2:1800 3:1239
204.168/16 NYSERNET-III-A C:US 1:1239 2:1800 3:1240
204.176.5/24 DIALUP-NSF-024 C:US 1:701(136) 2:701(134)
204.180.32/19(U) IQUEST3-NETBLK C:US 1:1239 2:1800 3:1240
204.180.64/24 TIAC5-DOM1 C:US 1:1800 2:1240 3:1239
204.180.65/24 TIAC5-DOM2 C:US 1:1800 2:1240 3:1239
204.180.66/24 TIAC5-DOM3 C:US 1:1800 2:1240 3:1239
204.180.67/24 TIAC5-DOM4 C:US 1:1800 2:1240 3:1239
204.180.68/24 TIAC5-DOM5 C:US 1:1800 2:1240 3:1239
204.180.69/24 TIAC5-DOM6 C:US 1:1800 2:1240 3:1239
204.180.70/24 TIAC5-DOM7 C:US 1:1800 2:1240 3:1239
204.180.71/24 TIAC5-DOM8 C:US 1:1800 2:1240 3:1239
204.180.72/24 TIAC5-DOM9 C:US 1:1800 2:1240 3:1239
204.180.73/24 TIAC5-DOM10 C:US 1:1800 2:1240 3:1239
204.180.74/24 TIAC5-DOM11 C:US 1:1800 2:1240 3:1239
204.180.75/24 TIAC5-DOM12 C:US 1:1800 2:1240 3:1239
204.180.76/24 TIAC5-DOM13 C:US 1:1800 2:1240 3:1239
204.180.77/24 TIAC5-DOM14 C:US 1:1800 2:1240 3:1239
204.180.78/24 TIAC5-DOM15 C:US 1:1800 2:1240 3:1239
204.180.79/24 TIAC5-DOM16 C:US 1:1800 2:1240 3:1239
204.180.80/24 TIAC5-DOM17 C:US 1:1800 2:1240 3:1239
204.180.81/24 TIAC5-DOM18 C:US 1:1800 2:1240 3:1239
204.180.82/24 TIAC5-DOM19 C:US 1:1800 2:1240 3:1239
204.180.83/24 TIAC5-DOM20 C:US 1:1800 2:1240 3:1239
204.180.84/24 TIAC5-DOM21 C:US 1:1800 2:1240 3:1239
204.180.85/24 TIAC5-DOM22 C:US 1:1800 2:1240 3:1239
204.180.86/24 TIAC5-DOM23 C:US 1:1800 2:1240 3:1239
204.180.87/24 TIAC5-DOM24 C:US 1:1800 2:1240 3:1239
204.180.88/24 TIAC5-DOM25 C:US 1:1800 2:1240 3:1239
204.180.89/24 TIAC5-DOM26 C:US 1:1800 2:1240 3:1239
204.180.90/24 TIAC5-DOM27 C:US 1:1800 2:1240 3:1239
204.180.91/24 TIAC5-DOM28 C:US 1:1800 2:1240 3:1239
204.180.92/24 TIAC5-DOM29 C:US 1:1800 2:1240 3:1239
204.180.93/24 TIAC5-DOM30 C:US 1:1800 2:1240 3:1239
204.180.94/24 TIAC5-DOM31 C:US 1:1800 2:1240 3:1239
204.180.95/24 TIAC5-DOM32 C:US 1:1800 2:1240 3:1239
204.181.32/23 NET-GAN C:US 1:1800 2:1240 3:1239
Deletions:
<none>
Expanded listing, sorted by country, then by organization:
==========================================================
Austria
-------
Oberoesterreichische Kraftwerke AG, Bahnhofstrasse 67, A-4810 Gmunden,
AUSTRIA
1:701(136) Alternet
2:701(134) Alternet
3:1800 ICM-Atlantic
-------------
193.80.190/24 OKA-NET (AT)
193.80.202/24 OKA-NET (AT)
Voest-Alpine Industrieanlagenbau, Turmstrasse 44, A-4031 Linz, AUSTRIA
1:701(136) Alternet
2:701(134) Alternet
3:1800 ICM-Atlantic
---------
148.56/16 VAINET (AT)
Belgium
-------
CEC, Rue de la Loi 200, B-1049 Brussels, BELGIUM
1:1800 ICM-Atlantic
2:1133 CERN/DANTE
3:1674 CERN/DANTE
4:1240 ICM-Pacific
---------
147.67/16 EC-RD-NETWORK (BE)
Canada
------
Bell Canada Inc. (Bell Sygma), 100 Wynford Drive 1st Floor, Don Mills,
Ontario, M3C 1K4, CANADA
1:701(136) Alternet
2:701(134) Alternet
-------------
198.235.70/24 NET-BELLCAN33 (CA)
Bradson Personnel Services, 440 Laurier Avenue West, Ottawa, Ontario, K1R
7X6, CANADA
1:1240 ICM-Pacific
2:1800 ICM-Atlantic
3:1239 SprintLink
------------
204.50.19/24 NET-BRADSON (CA)
Caspar Computer Services, Inc., 66 Mansfield Street, Brampton, ON, L6S 2Y6,
CANADA
1:577(133) CA-NET-AS
2:577(137) CA-NET-AS
3:577(143) CA-NET-AS
-------------
199.212.57/24 CASPAR-NET (CA)
Environment Canada (A.E.S.), 2121 Trans-Canada Hgwy, Dorval, QC, H9P 1J3,
CANADA
1:577(137) CA-NET-AS
2:577(133) CA-NET-AS
3:577(143) CA-NET-AS
----------
142.135/16 ALCIDE-2 (CA)
Forest Alliance of BC, PO Box 49312, 1055 Dunsmuir Street, Vancouver, BC,
V7X 1L3, CANADA
1:577(143) CA-NET-AS
2:577(133) CA-NET-AS
3:577(137) CA-NET-AS
-------------
199.60.121/24 BCFORESTS (CA)
Harvest Moon Technologies, 36-2nd Avenue North, Yorkton, Saskatchewan, S3N
1G2, CANADA
1:1240 ICM-Pacific
2:1800 ICM-Atlantic
3:1239 SprintLink
------------
204.50.20/24 NET-HMTNET (CA)
Information Technology, 13th Floor, North Tower, 175 Bloor St. E., Toronto,
Ontario, M4W 3S4, CANADA
1:2493(35) FONOROLA-EAST
2:2493(91) FONOROLA-EAST
---------
162.73/16 MOLSON-NET (CA)
InterLink, 500 Rene-Levesque West, Montreal, Quebec, H2Z 1W7, CANADA
1:2493(35) FONOROLA-EAST
2:2493(91) FONOROLA-EAST
--------------
199.202.116/24 INTERLINK (CA)
199.202.117/24 INTERLINK (CA)
199.202.118/24 INTERLINK (CA)
199.202.119/24 INTERLINK (CA)
199.202.120/24 INTERLINK (CA)
199.202.121/24 INTERLINK (CA)
199.202.122/24 INTERLINK (CA)
199.202.123/24 INTERLINK (CA)
199.202.124/24 INTERLINK (CA)
199.202.125/24 INTERLINK (CA)
199.202.126/24 INTERLINK (CA)
199.202.127/24 INTERLINK (CA)
199.202.128/24 INTERLINK (CA)
199.202.129/24 INTERLINK (CA)
199.202.130/24 INTERLINK (CA)
199.202.131/24 INTERLINK (CA)
199.202.132/24 INTERLINK (CA)
199.202.133/24 INTERLINK (CA)
199.202.134/24 INTERLINK (CA)
199.202.135/24 INTERLINK (CA)
199.202.254/24 INTERLINK-NETS (CA)
199.202.255/24 INTERLINK-NETS (CA)
Island Internet, 515B Campbell Street, Nanaimo, BC, V9R 3G9, CANADA
1:577(143) CA-NET-AS
2:577(133) CA-NET-AS
3:577(137) CA-NET-AS
-------------
199.60.230/24 NETBLK-ISLAND-NET1 (CA)
JMG Compushoppe, 892 Upper James St, Hamilton, ON, L9C 3A5, CANADA
1:1240 ICM-Pacific
2:1800 ICM-Atlantic
3:1239 SprintLink
--------------
204.138.237/24 JMG-COM (CA)
Magic Online Services Toronto Inc., 100 Wynford Drive 1st Floor, Don Mills,
Ontario, M3C 1K4, CANADA
1:701(136) Alternet
2:701(134) Alternet
--------------
199.166.230/24 NETBLK-MAGIC-ONLINE (CA)
199.166.231/24 NETBLK-MAGIC-ONLINE (CA)
199.166.232/24 NETBLK-MAGIC-ONLINE (CA)
199.166.233/24 NETBLK-MAGIC-ONLINE (CA)
MemberTech Management Inc., 19 King St. West, Stoney Creek, ON, L8G 1H1,
CANADA
1:1240 ICM-Pacific
2:1800 ICM-Atlantic
3:1239 SprintLink
--------------
204.138.238/24 SHOPEX-COM (CA)
NETinterior ComputerLinks Ltd, 2167 Shaughnessy Hill, Kamloops, BC, V1S
1B9, CANADA
1:577(143) CA-NET-AS
2:577(133) CA-NET-AS
3:577(137) CA-NET-AS
-------------
199.60.117/24 NETINTERIOR (CA)
Netron Inc, 99 St Regis Crescent North, Toronto, ON, M3J 1Y9, CANADA
1:1240 ICM-Pacific
2:1800 ICM-Atlantic
3:1239 SprintLink
-------------
198.235.51/24 NETRON (CA)
Ontario Science Centre, 770 Don Mills Road, Toronto, ON, M3C 1T3, CANADA
1:577(133) CA-NET-AS
2:577(137) CA-NET-AS
3:577(143) CA-NET-AS
-------------
199.212.58/24 OSC-ON-CA-C-212-58 (CA)
199.212.59/24 OSC-ON-CA-C-212-59 (CA)
Teleserve Canada Inc., 2808 - 1323 Homer Street, Vancouver, BC, V6B 5T1,
CANADA
1:577(143) CA-NET-AS
2:577(133) CA-NET-AS
3:577(137) CA-NET-AS
-------------
199.60.124/24 NETBLK-TELESERVE (CA)
199.60.125/24 NETBLK-TELESERVE (CA)
199.60.126/24 NETBLK-TELESERVE (CA)
199.60.127/24 NETBLK-TELESERVE (CA)
The Halton Board of Education, 2050 Guelph Line, P.O. Box 5005, Burlington,
Ontario, L7R 3Z2, CANADA
1:2493(35) FONOROLA-EAST
2:2493(91) FONOROLA-EAST
-------------
199.235.57/24 HALTON-NET (CA)
WorldLinx Telecommunications, Inc., 160 Elgin Street, Floor 12, Ottawa, ON,
K1G 3J4, CANADA
1:1240 ICM-Pacific
2:1800 ICM-Atlantic
3:1239 SprintLink
--------------
199.243.246/23 NETBLK-WORLDLINX (CA)
Chile
-----
Centro de Estudios Cientificos de Santiago., Avda Presidente Errazuriz
#3132, Santiago, CHILE
1:86 SURANET Regional Network (College Park)
2:279 SURANET Regional Network (Georgia Tech)
-------------
200.12.132/24 CECS (CL)
Finland
-------
EUnet Finland, Punavuorenkatu 1, FI-00120 HELSINKI, FINLAND
1:701(136) Alternet
2:701(134) Alternet
3:1800 ICM-Atlantic
---------
194.86/16 EUNET-FI-194.86-AGG (FI)
Raahe Institute of Computer Engineering, PO Box 82, FI-92101 Raahe, FINLAND
1:701(136) Alternet
2:701(134) Alternet
3:1800 ICM-Atlantic
-------------
192.26.135/24 RATOL1 (FI)
Rauman Kaupunki, Kanalinranta 3, FI-26100 Rauma, FINLAND
1:701(136) Alternet
2:701(134) Alternet
3:1800 ICM-Atlantic
--------------
193.185.155/24 RAUMA-NET3 (FI)
Suomen Kuntaliitto, II Linja 4, Helsinki, 00100, FINLAND
1:701(136) Alternet
2:701(134) Alternet
-------------
192.89.108/24 KUNTALIITTO-NET (FI)
France
------
AFNOR, FRANCE
1:1800 ICM-Atlantic
2:1240 ICM-Pacific
3:1133 CERN/DANTE
4:1674 CERN/DANTE
------------
194.51.17/24 FR-AFNOR (FR)
Centre de Ressources Informatiques, Universiti de Reims, FRANCE
1:1800 ICM-Atlantic
2:1240 ICM-Pacific
3:1133 CERN/DANTE
4:1674 CERN/DANTE
-------------
194.57.103/24 FR-URCA (FR)
194.57.104/24 FR-URCA (FR)
194.57.105/24 FR-URCA (FR)
Internet and WWW Service Provider, 204 Bd. Bineau, 92200 Neuilly, FRANCE
1:1800 ICM-Atlantic
2:1240 ICM-Pacific
3:1133 CERN/DANTE
4:1674 CERN/DANTE
-----------
194.98.0/21 IWAY-NET (FR)
Resau IP de la Chambre de Commerce, et d'Industrie de Paris, FRANCE
1:1800 ICM-Atlantic
2:1240 ICM-Pacific
3:1133 CERN/DANTE
4:1674 CERN/DANTE
------------
194.57.52/24 FR-CCIP-1 (FR)
194.57.53/24 FR-CCIP-1 (FR)
194.57.54/24 FR-CCIP-1 (FR)
194.57.55/24 FR-CCIP-1 (FR)
194.57.56/24 FR-CCIP-1 (FR)
194.57.58/24 FR-CCIP-1 (FR)
194.57.59/24 FR-CCIP-1 (FR)
194.57.92/24 FR-CCIP-2 (FR)
194.57.93/24 FR-CCIP-2 (FR)
194.57.94/24 FR-CCIP-2 (FR)
194.57.95/24 FR-CCIP-2 (FR)
194.57.96/24 FR-CCIP-2 (FR)
194.57.97/24 FR-CCIP-2 (FR)
194.57.98/24 FR-CCIP-2 (FR)
194.57.99/24 FR-CCIP-2 (FR)
194.57.100/24 FR-CCIP-2 (FR)
194.57.101/24 FR-CCIP-2 (FR)
194.57.102/24 FR-CCIP-2 (FR)
UPLIFT Technologie, FRANCE
1:1800 ICM-Atlantic
2:1240 ICM-Pacific
3:1133 CERN/DANTE
4:1674 CERN/DANTE
------------
194.51.20/24 FR-UPLIFT (FR)
Universite de Reims Champagne-Ardenne - URCA, Centre de Calcul, BP 347,
51062 Reims CEDEX, FRANCE
1:1800 ICM-Atlantic
2:1240 ICM-Pacific
3:1133 CERN/DANTE
4:1674 CERN/DANTE
-------------
193.50.209/24 FR-URCA2 (FR)
193.50.210/24 FR-URCA3 (FR)
193.50.211/24 FR-URCA4 (FR)
193.50.212/24 FR-URCA5 (FR)
193.50.213/24 FR-URCA6 (FR)
193.50.214/24 FR-URCA7 (FR)
Germany
-------
tele-daten-service GmbH, Titotstrasse 7-9, D-74072 Heilbronn, GERMANY
1:1324(32) ANS New York City - DNSS 35
2:1324(35) ANS New York City - DNSS 35
3:1800 ICM-Atlantic
4:1240 ICM-Pacific
5:1133 CERN/DANTE
------------
193.28.96/21 DETDSH71 (DE)
Hungary
-------
Szechenyi Istvan College, Hedervari u. 3., H-9026 Gyor, HUNGARY
1:1800 ICM-Atlantic
2:1133 CERN/DANTE
3:1674 CERN/DANTE
4:1240 ICM-Pacific
--------------
193.224.128/24 SZIF-NET (HU)
193.224.129/24 SZIF-NET (HU)
193.224.130/24 SZIF-NET (HU)
193.224.131/24 SZIF-NET (HU)
Italy
-----
IUnet NOC, Viale Monza 253, I-20126 Milano, ITALY
1:701(136) Alternet
2:701(134) Alternet
3:1800 ICM-Atlantic
-------------
193.76.255/24 IUNET-NET-3 (IT)
Japan
-----
ANDO ELECTRIC Co.,LTD, 19-7, KAMATA 4-CHOME, OTA-KU, TOKYO, JAPAN
1:2149 PSINET-2
2:174 NYSERNet Regional Network / PSI
-------------
202.248.30/24 ANDO-NET-C-248-30 (JP)
202.248.31/24 ANDO-NET-C-248-31 (JP)
Cyber Technologies International, Otake Dai-5 Building, 304, Daikyo-cho,
Shinjuku-ku, Tokyo, 160, JAPAN
1:2149 PSINET-2
2:174 NYSERNet Regional Network / PSI
------------
202.33.45/24 CYBER-NET (JP)
Nissen Co., Ltd, 79, Nishinochaya-Cho, Kisshoin, Kyoto, 601, JAPAN
1:2149 PSINET-2
2:174 NYSERNet Regional Network / PSI
-------------
202.24.192/24 NSNET (JP)
Okamura Corporation, World-Plaza Building 19F,Kitasaiwai,Nishi-ku,
Yokohama, 601, JAPAN
1:2149 PSINET-2
2:174 NYSERNet Regional Network / PSI
-------------
202.24.128/24 OKM-NET (JP)
Korea, South
------------
Korean Overseas Information Service, 82-1 Sejongro Jongrogu, Seoul,
110-050, KOREA, REPUBLIC OF
1:372 Nasa Science Network (FIX-West)
2:297 Nasa Science Network (FIX-East)
-------------
203.254.53/24 KOISNET1 (KR)
203.254.55/24 KOISNET2 (KR)
Morocco
-------
INRA, Division Informatique et Formation, BP 6512 RI RABAT, FRANCE
1:1800 ICM-Atlantic
2:1240 ICM-Pacific
3:1133 CERN/DANTE
4:1674 CERN/DANTE
------------
193.188.7/24 INRA-NET (MA)
Peru
----
PROMPERU, Ministerio de Industrias Piso 13 Calle 1 s/n, Urb. Corpac, Lima,
PERU
1:1800 ICM-Atlantic
2:1240 ICM-Pacific
3:1239 SprintLink
------------
200.11.32/24 PROMPERU (PE)
Russian Federation
------------------
IHEP, SU-142284 Serpukhov, RUSSIAN FEDERATION
1:701(136) Alternet
2:701(134) Alternet
3:1800 ICM-Atlantic
--------------
192.160.233/24 SU-IHEP (RU)
Joint-Stock Company SELF, korp.1432 Zelenograd, 103617 Moscow, RUSSIAN
FEDERATION
1:701(136) Alternet
2:701(134) Alternet
3:1800 ICM-Atlantic
--------------
193.232.226/24 COMPNET (RU)
LVS Corporation, Prophsoyuznaya ul., 65, 117806 Moscow, RUSSIAN FEDERATION
1:701(136) Alternet
2:701(134) Alternet
3:1800 ICM-Atlantic
--------------
193.125.170/24 LVS (RU)
193.125.171/24 LVS (RU)
Spain
-----
RedIRIS, Serrano 142, Madrid, E-28006, SPAIN
1:1800 ICM-Atlantic
2:1133 CERN/DANTE
3:1674 CERN/DANTE
4:1240 ICM-Pacific
----------
193.146/16 REDIRIS-PROVIDER-BLK3 (ES)
Switzerland
-----------
Sulzer Informatik AG, Postfach, CH-8401 Winterthur, SWITZERLAND
1:701(136) Alternet
2:701(134) Alternet
3:1800 ICM-Atlantic
----------
141.171/16 SULZERCH (CH)
Thailand
--------
Sripatum University, 61 Phahonyothin Rd., Jatujak, Bangkok, 10400, THAILAND
1:701(136) Alternet
2:701(134) Alternet
------------
202.44.68/24 SPU-TH (TH)
United Kingdom
--------------
Radstone Technology Plc, Water Lane, Towcester, Northants, England, NN12
6JN, UNITED KINGDOM
1:1849 PIPEX-AS
2:701(136) Alternet
3:701(134) Alternet
4:1800 ICM-Atlantic
--------------
193.130.226/23 RADSTONE (GB)
United States
-------------
ATT BELL LABORATORIES, 2000 N. NAPERVILLE RD., NAPERVILLE, IL 60566-7033,
USA
1:1321 ANS San Francisco - DNSS 11
2:2386 INS-AS
-------------
198.152.97/24 NETBLK-ATT-CBLOCK (US)
Alabama State University, 915 South Jackson Street, Montgomery, AL 36101,
USA
1:279 SURANET Regional Network (Georgia Tech)
2:86 SURANET Regional Network (College Park)
--------------
192.111.112/24 ALASU (US)
Banco Nacional de Mexico, 4605 Post Oak Place (Suite 230), Houston, TX
77027, USA
1:1328 ANS Houston - DNSS 67
-------------
199.221.26/24 BANAMEX-DMZ (US)
Black Box Corporation, 1000 Park Drive, Lawrence, PA 15055, USA
1:3577 PREPnet-WEST
2:1324(32) ANS New York City - DNSS 35
3:1324(35) ANS New York City - DNSS 35
--------------
199.234.106/23 BLACKBOX (US)
199.234.106/24(U) BLACKBOX (US)
199.234.107/24(U) BLACKBOX (US)
Boston Public Library, 666 Boylston Street, Boston, MA 02116, USA
1:560 NEARnet Regional Network
2:701(136) Alternet
3:701(134) Alternet
-------------
199.93.162/24 BOSNET (US)
COMSOFT MANAGEMENT SYSTEMS, INC., 200 WEST SUNSET WAY, ISSAQUAH, WA 98027,
USA
1:1240 ICM-Pacific
2:1800 ICM-Atlantic
3:1239 SprintLink
-------------
199.174.45/24 NET-COMSOFT-MGMT (US)
Call America, 4251 So. Higuera Street Suite 800, San Luis Obispo, CA 93401,
USA
1:1240 ICM-Pacific
2:1800 ICM-Atlantic
------------
199.1.204/24 SPRINT-C701CF (US)
199.1.205/24 SPRINT-C701CF (US)
Center for the Study of Connectivity and Data, West Chester University, 127
E.O. Bull Center, West Chester, PA
19383, USA
1:3577 PREPnet-WEST
2:1324(32) ANS New York City - DNSS 35
3:1324(35) ANS New York City - DNSS 35
--------------
204.108.128/17 CHESCONET-2 (US)
Centurion Technology, 3001 Executive Center Drive, Suite 200A, Clearwater,
FL 34622, USA
1:1333 ANS Atlanta - DNSS 107
-------------
199.222.18/24 CENT-NET (US)
City of Lincoln Nebraska, 233 South 10th Street - 2nd floor, Lincoln, NE
68508, USA
1:1240 ICM-Pacific
2:1800 ICM-Atlantic
3:1239 SprintLink
-----------
199.48.8/22 NETBLK-STARNET3 (US)
199.48.12/24 NETBLK-STARNET3 (US)
Clonetics Corporation, 9620 Chesapeake Drive #201, San Diego, CA 92123, USA
1:1240 ICM-Pacific
2:1800 ICM-Atlantic
------------
204.94.69/24 CLONETICS-NET (US)
Cykic Software Inc., 3944 Third Avenue, San Diego, CA 92103, USA
1:1240 ICM-Pacific
2:1800 ICM-Atlantic
------------
204.94.70/24 CYKIC-NET (US)
DataBase Consultants Inc., 4835 LBJ Freeway, Suite 900, Dallas, TX 75244,
USA
1:2149 PSINET-2
2:174 NYSERNet Regional Network / PSI
------------
204.4.108/24 PSINET-C4 (US)
Datarace, 11550 Interstate Hwy. 10 west, San Antonio, TX 78230, USA
1:1800 ICM-Atlantic
2:1240 ICM-Pacific
3:1239 SprintLink
-------------
204.96.214/24 NET-DATARACE (US)
EDS, 5400 Legacy Dr MS:B42A15, Plano, TX 75024, USA
1:1800 ICM-Atlantic
2:1240 ICM-Pacific
3:1239 SprintLink
------------
199.1.158/24 NET-EDSWORLD (US)
Ebsco Industries, Inc., 5724 Highway 280 East, Birmingham, AL 35242, USA
1:279 SURANET Regional Network (Georgia Tech)
2:86 SURANET Regional Network (College Park)
------------
199.77.44/23(U) NETBLK-EBSCO-CIDR1 (US)
Emerson College, 100 Beacon Street, Boston, MA 02116, USA
1:560 NEARnet Regional Network
------------
199.94.65/24 EMERSON-65 (US)
199.94.66/24 EMERSON-66 (US)
Exchange Systems, 4215 Winnetka Ave N, Suite 133, New Hope, MN 55428, USA
1:1225 CICNET at Argonne Labs
2:267 CICNET at UIUC
3:266 CICNET at MERIT
4:555 Minnesota Supercomputer Center Network (MSCNet)
-------------
199.199.25/24 EXYSNICHE (US)
FLEET TECHNICAL SUPPORT CENTER DET PEARL HARBOR, P.O. Box 109, PEARL
HARBOR, HI 96860, USA
1:568 Milnet (FIX-West)
2:19 Milnet (FIX-East)
--------------
199.211.197/24 FTSCPEARLMAIN (US)
Fallon McElligott, 901 Marquette Av. S, Ste 3200, Minneapolis, MN 55402,
USA
1:1225 CICNET at Argonne Labs
2:267 CICNET at UIUC
3:266 CICNET at MERIT
4:555 Minnesota Supercomputer Center Network (MSCNet)
------------
204.73.73/24 FALLON2 (US)
204.73.76/24 FALLON3 (US)
Federal Aviation Administration, 1250 Maryland Avenue, SW, Suite 170,
Washington, DC 20024, USA
1:1327 ANS Washington D.C. - DNSS 59
------------
204.108.0/24 APM-HQ-FAA (US)
Fidelity Investments, 82 Devonshire St., Boston, MA 02109, USA
1:560 NEARnet Regional Network
2:701(136) Alternet
3:701(134) Alternet
-------------
199.93.200/24 FIDELITY (US)
Galaxy Access Network, 5401 North Central Expressway, Dallas, TX 75205, USA
1:1800 ICM-Atlantic
2:1240 ICM-Pacific
3:1239 SprintLink
-------------
204.181.32/23 NET-GAN (US)
Geological Survey of Alabama, 420 Hackberry Lane, Tuscaloosa, AL
33486-9780, USA
1:279 SURANET Regional Network (Georgia Tech)
2:86 SURANET Regional Network (College Park)
------------
199.77.42/24(U) GSA-TUSCALOOSA-AL-US (US)
Global Financial Network, Inc., 1908 Blue Knob Road, Virginia Beach, VA
23464, USA
1:701(136) Alternet
2:701(134) Alternet
--------------
199.170.210/24 GFN-NET (US)
Global Net, 999 Woodcock Road, Suite 312, Orlando, FL 32803, USA
1:1800 ICM-Atlantic
2:1240 ICM-Pacific
3:1239 SprintLink
------------
199.0.158/23 GLOBALNET2-DOM (US)
Globelle Corp, 6410 W. Old Shakopee Rd, MPLS, MN 55438, USA
1:1225 CICNET at Argonne Labs
2:267 CICNET at UIUC
3:266 CICNET at MERIT
4:555 Minnesota Supercomputer Center Network (MSCNet)
-------------
199.199.29/24 GLOBELLE (US)
Haven Communication Technologies, 15 E. Milton Rd., #1, Brookline, MA
02146, MA 02146, USA
1:1239 SprintLink
2:1800 ICM-Atlantic
3:1240 ICM-Pacific
--------------
192.251.193/24 NET-HAVEN-NET (US)
Internet Media Network, Inc., 20417 Nordhoff St, Chatsworth, CA 91311, USA
1:1957 ANSCIX-AS
-------------
204.69.234/24 MAILORDER3 (US)
Internet Services of Atlanta, 103 Perimeter Park, Atlanta, GA 30301, USA
1:1800 ICM-Atlantic
2:1240 ICM-Pacific
3:1239 SprintLink
-------------
204.117.71/24 NET-PEACHWEB (US)
204.117.209/24 NET-IS5 (US)
Jacobson Capital Management, 575 Broadway, New York, NY 10012, USA
1:560 NEARnet Regional Network
2:701(136) Alternet
3:701(134) Alternet
-------------
199.94.128/24 NET-JCP1 (US)
199.94.129/24 NET-JCP2 (US)
Jones, Day, Reavis & Pogue, 901 Lakeside Avenue, Cleveland, OH 44114, USA
1:1239 SprintLink
2:1800 ICM-Atlantic
3:1240 ICM-Pacific
---------
168.98/16 NET-JDNET (US)
King County Office of Education, 1144 W. Lacey Blvd., Hanford, CA 93230,
USA
1:2150 CSUNET-SW
--------------
198.189.146/24 CSUNET-NORTH-189-146 (US)
198.189.147/24 CSUNET-NORTH-189-147 (US)
198.189.148/24 CSUNET-NORTH-189-148 (US)
198.189.149/24 CSUNET-NORTH-189-149 (US)
198.189.150/24 CSUNET-NORTH-189-150 (US)
198.189.151/24 CSUNET-NORTH-189-151 (US)
198.189.152/24 CSUNET-NORTH-189-152 (US)
198.189.153/24 CSUNET-NORTH-189-153 (US)
198.189.154/24 CSUNET-NORTH-189-154 (US)
198.189.155/24 CSUNET-NORTH-189-155 (US)
198.189.156/24 CSUNET-NORTH-189-156 (US)
198.189.159/24 CSUNET-NORTH-189-159 (US)
198.189.160/24 CSUNET-NORTH-189-160 (US)
198.189.161/24 CSUNET-NORTH-189-161 (US)
198.189.163/24 CSUNET-NORTH-189-163 (US)
198.189.164/24 CSUNET-NORTH-189-164 (US)
198.189.165/24 CSUNET-NORTH-189-165 (US)
Lancet Technology, 1 Kendall Square, Bldg 200, Cambridge, MA 02139, USA
1:701(136) Alternet
2:701(134) Alternet
-------------
199.172.61/24 AVICENNA-NET (US)
Maaco Enterprises, 381 Brooks Road, King of Prussia, PA 19406, USA
1:701(136) Alternet
2:701(134) Alternet
--------------
192.104.165/24 MAACO (US)
Metro II, 1300 Mendota Heights Road, Mendota Heights, MN 55120, 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.192/18 METROII1 (US)
Micro Training Centers, 560 Village Road, West Palm Beach, FL 33409, USA
1:1333 ANS Atlanta - DNSS 107
-------------
199.222.19/24 MTC-DMZ1 (US)
199.222.20/24 MCT-DMZ2 (US)
Microstrategy, Inc., 8000 Towers Crescent Drive, Suite 1400, Vienna, VA
22182, USA
1:701(136) Alternet
2:701(134) Alternet
--------------
199.173.152/24 STRATEGY-NET (US)
Mounds View Schools, 2959 Hamline Ave, St Paul, MN 55113, 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.226/23 ISD621 (US)
204.72.228/22 ISD621 (US)
204.72.232/22 ISD621 (US)
Naval Air Warfare Center Aircraft Division, Special Warfare Branch,Building
141, , Code 4.12.4, St. Inigoes, MD
10684-0010, USA
1:19 Milnet (FIX-East)
2:568 Milnet (FIX-West)
--------------
199.211.198/24 SPECWAR-NET (US)
Network Management Services, 5500 Wayzata Blvd., Suite 290, Minneapolis, 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)
--------------
198.246.177/24 NMS01 (US)
199.199.30/24 NMS02 (US)
New Standards Inc, 1080 Montreal Ave, St Paul, MN 55116, USA
1:1225 CICNET at Argonne Labs
2:267 CICNET at UIUC
3:266 CICNET at MERIT
4:555 Minnesota Supercomputer Center Network (MSCNet)
-------------
199.199.26/24 NEWSTANDARDS-NET (US)
North Carolina Research and Education Network, P.O. Box 12889, Research
Triangle Park, NC 27709, USA
1:1329 ANS Greensboro - DNSS 75
---------
204.84/15 NCREN-CIDR3 (US)
North Central Bible College, 910 Elliot Ave S, MPLS, MN 55404, USA
1:1225 CICNET at Argonne Labs
2:267 CICNET at UIUC
3:266 CICNET at MERIT
4:555 Minnesota Supercomputer Center Network (MSCNet)
-------------
199.199.28/24 NCBC (US)
Occidental Petroleum Corporation, 4500 S. 129 E. Ave, Tulsa, OK 74134, USA
1:93 MIDnet
--------------
199.248.165/24 NETBLK-OXY-3 (US)
Padilla Speer Beardsley, Inc., 224 Franklin Ave W, Minneapolis, MN 55404,
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.73.70/23 PSB1 (US)
Pasco County Public Schools, 7227 Land O'Lakes Blvd., Land O'Lakes, FL
34639, USA
1:279 SURANET Regional Network (Georgia Tech)
2:86 SURANET Regional Network (College Park)
-------------
199.164.64/18 PASCO-K12-FL (US)
Philip A Naecker Consulting, 1010 East Union Street, Suite 101, Pasadena,
CA 91106-1756, USA
1:701(136) Alternet
2:701(134) Alternet
------------
198.5.244/24 NAECKER-NET (US)
198.5.245/24 NAECKER-NET (US)
198.5.246/24 NAECKER-NET (US)
198.5.247/24 NAECKER-NET (US)
Planet Systems, 1063 Cosby Hwy, Newport, TN 37821, USA
1:279 SURANET Regional Network (Georgia Tech)
2:86 SURANET Regional Network (College Park)
-------------
199.78.226/24(U) PLANETC-COM (US)
RAIN Network, P.O. Box 2683, Santa Barbara, CA 93120-2683, USA
1:1240 ICM-Pacific
2:1800 ICM-Atlantic
3:1239 SprintLink
-------------
204.96.224/19 RAIN1-NET (US)
Rapaport Corp., 15 W. 47th St. #600, New York, NY 10036, USA
1:701(136) Alternet
2:701(134) Alternet
--------------
199.171.220/24 DIAMOND-NET (US)
Robbinsdale Area Schools, 4148 Winnetka Avenue North, New Hope, MN 55427,
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.236/22 RDALEPS (US)
204.72.240/22 RDALEPS (US)
204.72.244/23 RDALEPS (US)
Rockhurst College, 1100 Rockhurst Rd., Kansas City, MO 64110, USA
1:93 MIDnet
------------
198.98.33/24 ROCKHURST1 (US)
School District of Philadelphia, 734 Schuylkill Avenue, Room 614,
Philadelphia, PA 19146, USA
1:1324(32) ANS New York City - DNSS 35
2:1324(35) ANS New York City - DNSS 35
3:3577 PREPnet-WEST
--------------
199.234.208/22 PHILSCH (US)
199.234.208/24(U) PHILSCH (US)
199.234.209/24(U) PHILSCH (US)
199.234.210/24(U) PHILSCH (US)
199.234.211/24(U) PHILSCH (US)
Small Systems Specialists, 2035 E. 46th Street, Indianapolis, IN 46205, USA
1:1239 SprintLink
2:1800 ICM-Atlantic
3:1240 ICM-Pacific
-------------
204.180.32/19(U) IQUEST3-NETBLK (US)
Southern Geographics Technologies Network Services, 609 Glen Willow Drive,
Knoxville, TN 37922, USA
1:1740 CERFnet
--------------
204.107.130/24 SGT (US)
St Paul Public Schools, 360 Colborne, St Paul, MN 55105, 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.196/22 STPAULPS (US)
204.72.200/21 STPAULPS (US)
204.72.208/20 STPAULPS (US)
204.72.224/23 STPAULPS (US)
TRW Space and Defense Sector, One Space Park R3/2089, Redondo Beach, CA
90278, USA
1:1740 CERFnet
---------
192.45/16 TRW-CNETS (US)
The Gillette Company, 1 Gillette Park, Boston, MA 02127, USA
1:1957 ANSCIX-AS
----------
151.208/16 GILLETTE (US)
The Internet Access Company, 7 Railroad Avenue, Suite G, Bedford, MA 01730,
USA
1:1800 ICM-Atlantic
2:1240 ICM-Pacific
3:1239 SprintLink
-------------
204.180.64/24 TIAC5-DOM1 (US)
204.180.65/24 TIAC5-DOM2 (US)
204.180.66/24 TIAC5-DOM3 (US)
204.180.67/24 TIAC5-DOM4 (US)
204.180.68/24 TIAC5-DOM5 (US)
204.180.69/24 TIAC5-DOM6 (US)
204.180.70/24 TIAC5-DOM7 (US)
204.180.71/24 TIAC5-DOM8 (US)
204.180.72/24 TIAC5-DOM9 (US)
204.180.73/24 TIAC5-DOM10 (US)
204.180.74/24 TIAC5-DOM11 (US)
204.180.75/24 TIAC5-DOM12 (US)
204.180.76/24 TIAC5-DOM13 (US)
204.180.77/24 TIAC5-DOM14 (US)
204.180.78/24 TIAC5-DOM15 (US)
204.180.79/24 TIAC5-DOM16 (US)
204.180.80/24 TIAC5-DOM17 (US)
204.180.81/24 TIAC5-DOM18 (US)
204.180.82/24 TIAC5-DOM19 (US)
204.180.83/24 TIAC5-DOM20 (US)
204.180.84/24 TIAC5-DOM21 (US)
204.180.85/24 TIAC5-DOM22 (US)
204.180.86/24 TIAC5-DOM23 (US)
204.180.87/24 TIAC5-DOM24 (US)
204.180.88/24 TIAC5-DOM25 (US)
204.180.89/24 TIAC5-DOM26 (US)
204.180.90/24 TIAC5-DOM27 (US)
204.180.91/24 TIAC5-DOM28 (US)
204.180.92/24 TIAC5-DOM29 (US)
204.180.93/24 TIAC5-DOM30 (US)
204.180.94/24 TIAC5-DOM31 (US)
204.180.95/24 TIAC5-DOM32 (US)
The Jackson Laboratory, 600 Main Street, Bar Harbor, ME 04609, USA
1:560 NEARnet Regional Network
-------------
199.94.152/24 JACKSON-152 (US)
199.94.153/24 JACKSON-153 (US)
199.94.154/24 JACKSON-154 (US)
199.94.155/24 JACKSON-155 (US)
199.94.156/24 JACKSON-156 (US)
The Laitram Corporation, 220 Laitram Lane, New Orleans, LA 70123, USA
1:701(136) Alternet
2:701(134) Alternet
--------------
199.249.183/24 LAITRAM-NET (US)
The Nashville Exchange, 2500 Hillsboro Road, Nashville, TN 37212, USA
1:279 SURANET Regional Network (Georgia Tech)
2:86 SURANET Regional Network (College Park)
-------------
199.78.224/24(U) NASHVILLE-COM (US)
Tribase Corporation, 751 Laurel Street, Suite 620, San Carlos, CA 94070,
USA
1:93 MIDnet
-------------
192.84.222/24 NET-TRIBASE (US)
US Merit Systems Protection Board, 1100 Vermont Ave, WASHINGTON, DC 20419,
USA
1:1800 ICM-Atlantic
2:1240 ICM-Pacific
3:1239 SprintLink
-------------
192.81.166/24 MSPB-HP (US)
US Sprint, BSG, 13221 Woodland Rd, Herndon, VA 22071, USA
1:1239 SprintLink
2:1800 ICM-Atlantic
3:1240 ICM-Pacific
----------
204.168/16 NYSERNET-III-A (US)
UUNET Technologies, Inc., 3110 Fairview Park Drive, Suite 570, Falls
Church, VA 22042, USA
1:701(136) Alternet
2:701(134) Alternet
------------
204.176.5/24 DIALUP-NSF-024 (US)
Voicenet, 17 Richard Road, Ivyland, PA 18974-1512, USA
1:1324(32) ANS New York City - DNSS 35
2:1324(35) ANS New York City - DNSS 35
3:3577 PREPnet-WEST
--------------
199.234.200/22 VOICENET1 (US)
199.234.200/24(U) VOICENET1 (US)
199.234.201/24(U) VOICENET1 (US)
199.234.202/24(U) VOICENET1 (US)
199.234.203/24(U) VOICENET1 (US)
WLN, PO Box 3888, Lacey, WA 98503-0888, USA
1:1240 ICM-Pacific
2:1800 ICM-Atlantic
3:1239 SprintLink
--------------
204.118.132/24 FTVCVR-A (US)
204.118.133/24 FTVCVR-B (US)
WSNetwork Communication Services, 448 South Lawrence Street, Montgomery, AL
36104, USA
1:701(136) Alternet
2:701(134) Alternet
--------------
199.172.191/24 WSNET (US)
==========================================================
The following Midlevel/Regional peering sessions have also been added:
AS 1206 - PSCNET Regional Network (US) - ENSS 132
Peer: 192.5.146.11 - Pittsburgh Supercomputing Center, 4400 5th Avenue,
Pittsburgh, PA 15213, USA - whaler.psc.edu
==========================================================
AS690 CIDR Squeezings Report: 9229 Nets, 100 ASs, 1881 Aggregates
------------------------------------------------------------------
9229 (88%) of the ever-announced more-specific routes within aggregates have
been withdrawn. 414 of those were withdrawn within the last week.
127 the week before that.
90 the week before that.
100 ASs have registered aggregates in the PRDB.
94 of those are announcing aggregates.
77 have withdrawn at least one more specific route.
1881 Aggregates are configured.
1563 of these were Top-Level Aggregates (not nested in another aggregate).
1241 of these are being announced to AS690.
976 of those have at least one subnet configured (the other 265 may be saving
the Internet future subnet announcements).
903 have stopped announcing at least one configured more specific route.
892 have stopped announcing half of their configured more specific routes.
835 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.
--------------------------------------------------------------------------
PRDB CHANGES: (Updated October 25, 1994)
In early December 1994, as part of the transition to the new Global
Routing Registry (GRR), the Policy Routing Database (PRDB) will be retired.
Many of the functions of the PRDB (including generation of router
configurations for NSFNET) will be produced based on data from the
Global Routing Registry.
This change to the NSFNET Backbone service will involve the following changes:
- The method for submitting new nets to be routed over AS690 will
change. Instead of submitting a NACR to nsfnet-admin(a)merit.edu,
you will need to submit a "route template" to auto-dbm(a)radb.ra.net .
- Additions and entries to the new registry will be made by the Home
AS which creates the route for each net, rather than being
submitted by a AS690 peer AS.
- Most of the PRDB reports (listed above) will no longer be produced.
Equivalent information for most of these reports is available
from the global Routing Registry.
These are major changes to the system. These changes are being made in
order to migrate NSFNET customers and the global user community to a
Global Routing Registry system, which will be more capable of supporting
user needs after the termination of the NSFNET Backbone services in
April 1995.
For more information, set your web browser to http://www.ra.net/rrinfo.html ,
or use anonymous ftp to obtain the files "OVERVIEW" and "transition.plan"
from the directory "ftp.ra.net:pub/ra".
Merit would like to minimize the number of problems that this transition
may cause you. In order to help us help you through the transition,
please send your concerns, your needs, and suggestions on how we can
make this happen smoothly to merit-ie(a)merit.edu.
The archived discussion list "db-disc(a)merit.edu" also exists for discussion of
PRDB 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
In message <199410272114.RAA01925(a)curtis.ansremote.com>, Curtis Villamizar writ
es:
| If I recall correctly, Sprint a while back had some routers roll over
| for a similar reason during a PSI transition of some sort.
Yes, one of the things I didn't get to in my NANOG presentation
due to lack of time is the fact that we still have several AGS+es
and a couple of 16Mbyte 7000s in the field.
We have upgrades scheduled and RPs in hand for the 7000s, so they will
be fixed soon.
The AGS+es are currently not doing backbone routing, and are all
being migrated into customer-access ASes so that they eventually
will be able to default to the 64Mbyte 7000s doing backbone routing.
The AGS+es eventually will be withdrawn as we will move customers
attached to them to 64Mbyte 7000s.
Anyway, the 16Mbyte routers that are out there now and participating
in AS 1239 iBGP mesh (older boxes that antedate the current engineering
plan) can and do keel over due to memory shortages. We have at least
one multihomed customer in a similar situation.
We appreciate several of our peers' efforts to keep routing tables
small, and take defensive steps against those who do not.
Sean.
P.S.: Numbers wise SL/ICM has 14 AGS+es, one of which will be
decommissioned and replaced with a 7010 tonight. There
are five 7000s with 16Mbytes still and they will be upgraded
soon. There are 25 64Mbyte routers turned up and active now,
and a few others that in the being-installed phase, and
considerably more on order and in the current engineering plan.
1
0
In the transition planning, Merit and ANS had anticipated that many of the
regionals which use the NSFNET Backbone Service for inter-regional
connectivity would have completed their migration to new service providers
by October 31, 1994. No regionals have yet completed this migration.
Anticipating the retirement of the NSFNET Backbone Service at College Park,
Alternet issued a termination notice for the MAE-East connection for October
31st. In addition, the MAE-East Ethernet segment is saturated and the new
MAE-East+ FDDI colocation facility exists. In response to all these
issues, Merit and ANS plan to maintain support for SURAnet and upgrade
the NSFNET Backbone Service to MAE-East+.
In the interim, since the NSFNET Backbone Service to SURAnet at College
Park will continue for the near term and since it is important to
maintain the continuity of service to MAE-East, ANS has offered to
support the MAE-East connection at College Park.
On behalf of the NSFNET project, Merit thanks Alternet for its previous
support to the project and ANS for its continuing support.
--Elise
1
0
NANOG, October 24 & 25, 1994
(version 2)
Notes by Stan Barber <sob(a)academ.com>
Thanks to Guy Almes and Stan Borinski for their corrections and additions to
these notes.
[Please note that any errors are mine, and I'd appreciate corrections being
forwarded to me. The first version of this document is now available at the
following URL: http://rrdb.merit.edu/nanaog.octminutes.html]
Elise Gerich opened the meeting with Merit's current understanding of the
state of the transition. THENET , CERFNET and MICHNET have expressed
specific dates for transition. The current NSFNET contract with Merit will
terminate on April 30, 1995.
John Scudder then discussed some modeling he and Sue Hares have done on the
projected load at the NAPs. The basic conclusions are that the FDDI
technology (at Sprint) will be saturated sometime next year and that
load-balancing strategies among NSPs across the NAPS is imperative for the
long term viability of the new architecture. John also expressed concern
over the lack of expressed policy for the collection of statistical data by
the NAP operators. All of the NAP operator are present and stated that they
will collect data, but that there are serious and open questions concerning
the privacy of that data and how to publish it appropriately. John said
that collecting the data was most important. Without the data, there is no
source information from which publication become possible. He said that
MERIT/NSFNET had already tackled these issues. Maybe the NAP operators can
use this previous work as a model to develop their own policies for
publication.
After the break, Paul Vixie discussed the current status of the DNS and
BIND. Specifically, he discusses DNS security. There are two reasons why
DNS are not secure. There are two papers on this topic and they are both in
the current BIND kit. So the information is freely available.
Consider the case of telneting across the Internet and getting what appears
to be your machine's login banner. Doing a double check (host->address,
then address->host) will help eliminate this problem. hosts.equiv and
.rhosts are also sources of problems. Polluting the cache is a real
problem. Doing UDP flooding is another problem. CERT says that doing rlogin
is bad, but that does not solve the cache pollution problem.
How to defend?
1. Validate the packets returned in a response to the query. Routers should
drop UDP packets on which the source address don't match what it should be.
(e.g. a udp packet comes in on a WAN link that should have come in via an
ethernet interface). TCP is harder to spoof because of the three-way
handshake, however running all DNS queries over TCP will add too much
overhead to this process.
2. There are a number of static validations of packet format that can be
done. Adding some kind of cryptographic information to the DNS would help.
Unfortunately, this moves very slowly because there are a number of strong
conflicting opinions.
What is being done?
The current BETA of BIND has almost everything fixed that can be fixed
without a new protocol. Versions prior 4.9 are no longer supported.
Paul may rewrite this server in the future, but it will still be called
named because vendors have a hard time putting it into their releases if it
is called something else.
Paul is funded half-time by the Internet Software Consortium. Rick Adams
funds it via UUNET's non-profit side. Rick did not want to put it under
GNU.
ISC also is now running a root server and in doing this some specific
issues related to running root servers are now being addressed in fixes to
BIND.
DNS version 2 is being discussed. This is due to the limit in the size of
the udp packet. Paul M. and Paul V. are working to say something about
this at the next IETF.
HP, Sun, DEC and SGI are working with Paul to adopt the 4.9.3 BIND once it
is productional.
After this comes out, Paul will start working on other problems. One
problem is the size of BIND in core. This change will include using the
Berkeley db routing to feed this from a disk-based database.
There will also be some effort for helping doing load-balancing better and
perhaps implementing policy features.
What about service issues? Providing name service is a start.
DEC and SGI will be shipping BIND 4.9.3 will be shipping it with the next
release.
Paul has talked to Novell, but noone else....Novell has not been a helpful
from the non-Unix side.
RA Project : Merit and ISI with a subcontract with IBM
ISI does the Route Server Development and the RA Futures
Merit does the Routing Registry Databases and Network Management
The Global Routing Registry consists of the RADB, various private routing
registries, RIPE and APNIC. The RADB will be used to generate route server
configurations and potentially router configurations.
1993 -- RIPE 81
1994 -- PRIDE tools
April 1994 -- Merit Routing Registry
September 1994 -- RIPE-181
October 1994 -- RIPE-181 Software implementation
November 1994 -- NSP Policy Registrations/Route Server Configurations
Why use the RADB? Troubleshooting, Connectivity, Stability
The Route Server by ISI with IBM
They facilitate routing information exchange. They don't forward packets.
There are two at each NAP with one AS number. They provide routing
selection and distribution on behalf of clients (NSPs). [Replication of
gated single table use = view] Multiple views to support clients with
dissimilar route selection and/or distribution policies. BGP4 and BGP4 MIB
are supported. RS's AS inserted in AS path, MED is passed unmodified (this
appears controversial). Yakov said that Cisco has a hidden feature to
ignore AS_PATH and trust MED.
The Route Servers are up and running on a testbed and have been tested with
up to 8 peers and 5 views. Target ship date to 3 NAPS is October 21. The
fourth will soon follow.
The Network Management aspect of the RA project uses a Hierarchically
Distributed Network Management Model. At the NAP, only local NM Traffic,
externalizes NAP Problems, SNMPv1 and SNMPv2 are supported. OOB Access
provides seamless PPP backup & console port access. Remote debugging
environment is identical to local debugging environment.
The Centralized Network Management System at Merit polls distributed rovers
for problems, consolidates the problems into ROC (Routing Operations
Center) alert screen. It was operational on August 1st which is operated by
the University of Michigan Network Systems at the same location as the
previous NSFNET NOC. This group current provides support for MichNet and
UMNnet. It is expected to provide service to CICnet. Currently, it provides
24/7 human operator coverage.
Everything should be operational by the end of November.
Routing Futures -- Route Server decoupling packet forwarding from routing
information exchange, scalability and modularity. For example, explicit
routing will be supported (with the development of ERP). IPv6 will be
provided. Doing analysis of RRDB and define a general policy language
(backward compatible with RIPE 181). Routing policy consistency and
aggregation will be developed.
Securing the route servers -- All of the usual standard mechanisms are
being applied. Single-use passwords.... mac-layer bridges .... etc....How
do we keep the routes from getting screwed intentionally? Denial of service
attacks are possible.
A design document on the route server will be available via the
RRDB.MERIT.EDU WWW server.
There is a serious concern to synchronization of the route servers and the
routing registries. No solution has been implemented currently. Merit
believes that will do updates at least once a day.
There was mention of using the rwhois from the InterNIC as a possible way
to configure the routing DB by pooling local information.
Conversion from PRDB to RRDB
The PRDB is AS 690 specific, NACRs, twice weekly and AUP constrained.
The RADB has none of these features.
Migration will occur before April of 1995. The PRDB will be temporarily
part of the Global Routing Registry during transition.
Real soon now -- Still send NACR and it will be entered into PRDB and RRDB.
Constancy checking will be more automated. Output for AS 690 will be
compared from both to check consistency. While this is happening, users
will do what they always have. [Check ftp.ra.net for more information.]
There is alot of concern among the NANOG participants about the correctness
of all the information in the PRDB. Specifically, there appears to be some
inaccuracy (homeas) of the information. ESnet has a special concern about
this.
[Operators should send mail to dsj(a)merit.edu to fix the missing homeas problem.]
Transition Plan:
1. Continue submitting NACRs
2. Start learning RIPE 181
3. Set/Confirm your AS's Maintainer object for future security
4. Switch to using Route Templates (in December)
When it all works --RADB will be source for AS690 configuration, NACRs will
go away, use local registries
RADB to generate AS690 on second week of December.
NACRs to die at the end of that week.
European Operators' Forum Overview -- Peter Lothberg
[I missed this, so this information is from Stan Borinski]
Peter provided some humorous, yet interesting observations on the status of
the Internet in Europe.
To show the tremendous growth occurring in Europe as well, he gave an
example. After being out of capacity on their Stockholm E1 link for some
time, they finally installed another. It took one day for it to get it to
capacity! Unfortunately, the E1 costs $700,000/year.
[Back to my notes.... -- Stan Barber]
Proxy Aggregation -- CIDR by Yakov Rekhter
Assumptions -- Need to match the volume of routing information with the
available resources, while providing connectivity server -- on a per
provider basis. Need to match the amount of resource with the utility of
routing information -- on a per provider basis.
But what about "MORE THRUST?" It's not a good answer. Drives the costs up,
doesn't help with complexity of operations, eliminates small providers
Proxy aggregation -- A mechanism to allow aggregation of routing
information originated by sites that are BGP-4 incapable.
Proxy aggregation -- problems -- full consensus must exist for it to work.
Local aggregation -- to reconnect the entity that benefits from the
aggregation and the party that creates the aggregation. Bilateral
agreements would control the disposition of doing local aggregation. Doing
the aggregation at exit is better, but harder than doing it at entry.
Potential Candidates for Local Aggregation -- Longer prefix in presence of
a shorter prefix, Adjacent CIDR Blocks, Aggregation over known holes.
Routing in the presence of Local Aggregation --
AS and router that did the aggregation is identified via BGP
(AGGREGATOR attribute)
Should register in RRDB
Summary -- adding more memory to routers is not an answer
Regionals should aggregate their own CIDR blocks
An NSP may do local aggregation and register it in the RRDB.
Optimal routing and large scale routing are mutually exclusive.
CIDR is the only known technique to provide scalable routing in the Internet.
Large Internet and the ability of every site to control its own routing are
mutually exclusive.
Yakov also noted that 64Mb routers won't last as long as IPv4.
[More notes from Stan Borinski, while I was out again.]
Ameritech NAP Labs by Andy Schmidt
Ameritech performed tests with RFC 1323 kernel modifications on Sun Sparc
machines. A window of 32k was enabled at line speed. The AT&T switch used
by Ameritech has buffers that are orders of magnitude larger than other
vendors. All studies discussed showed bigger buffers were the key to
realizing ATM's performance capabilities.
[Back to my notes -- Stan Barber]
Sprint Network Reengineering -- Sean Doran
T-3 Network with sites in DC, Atlanta, Ft.Worth and Stockton currently.
Will be expanding to Seattle, Chicago and Sprint NAP in the next several
months. ICM uses this network for transit from one coast to the other. They
expect to create a separate ICM transit network early next year.
Next NANOG will be at NCAR in February.
PacBell NAP Status--Frank Liu
The Switch is a Newbridge 36-150.
NSFNET/ANS connected via Hayward today.
MCINET via Hayward today.
PB Labs via Concord today.
Sprintlink connected via San Jose (not yet).
NETCOM connected via Santa Clara in the next Month.
APEX Global Information Services (based in Chicago) will connect via Santa
Clara, but not yet.
The Packet Clearing House (consortium) for small providers connected via
Frame Relay to PB NAP. They will connect via one router to the NAP. It is
being led by Electric City's Chris Allen.
CIX connections are also in the cloud, but not in the same community yet.
Testing done by Bellcore and PB.
[TTCP was used for testing. The data was put up and removed quickly, so I
did lose some in taking notes.]
One source (TAXI/Sonet) -> One sink
Two Sources (TAXI/Sonet) -> One Sink
Five Sources (ethernet connected) ->One Sink (ethernet connected)
Equipment issues -- DSU HSSI Clock mismatch with the data rate (37 DSSI
clock rate versus 44 data rate versus a theoretical 52). Sink devices does
not have enough processing power to deal with large numbers of 512 byte
packets. Also, there was MTU mismatch issues between the SunOS (512 bytes)
machines used and the Solaris (536 bytes) machines used.
One Source-> One Sink
MSS Window Throughput (out of 40Mb/sec)
4470 51000 33.6
4470 25000 22.33
Two Source -> One Sink
4470 18000 33.17 (.05% cell loss, .04%
packet restrans)
1500 51000 15.41 (.69% cell loss, 2.76%
packet restrans)
Conclusions
Maximum throughput is 33.6 Mbps for the 1:1 connection.
Maximum throughput will be higher when the DSU HSSI clock and data-rate
mismatch is corrected.
Cell loss rate is low (.02% -- .69%).
Throughput degraded with the TCP window size is greater than 13000 bytes.
Large switch buffers and router traffic shaping are needed.
[The results appear to show TCP backing-off strategy engaging.]
Future Service Plan of the SF-NAP-- Chin Yuan
Currently, the NAP does best effort with RFC 1490 encapsulation.
March 1995 -- Variable Bit Rate, Sub-Rate Tariff (4,10,16,25,34 and 40Mbps
on 51, 100 and 140Mbps on OC3c). At CPE: Static Traffic Shaping and RFC
1483 and 1577 support [Traffic Shaping to be supported by Cisco later this
year in API card for both OC3c and T3.]
June 1995 -- Support for DS1 ATM (DXI and UNI at 128, 384 kbps and 1.4Mbps)
1996 or later -- Available Bit Rate and SVCs. At CPE: Dynamic Traffic Shaping
Notes on Variable Bit Rate:
Sustainable Cell Rate(SCR) and Maximum Burst Size (MBS)---
* Traffic Policing
* Aggregated SCR is no greater than the line rate
* MBS = 32, 100, 200 cells (Negotiable if > 200 cells)
Peak Cell Rate (possible)
* PCR <=line rate
Traffic shaping will be required for the more advanced services. Available
Bit Rate will require feedback to the router.
ANS on performance --- Curtis Villamizar
There are two problems: aggregation of lower-speed TCP flows, support for
high speed elastic supercomputer application.
RFC 1191 is very important as is RFC-1323 for these problems to be addressed.
RFC 1191 -- Path MTU discovery
RFC 1323 -- High Performance Extensions for TCP
The work that was done -- previous work showed that top speed for TCP was 30Mbs.
The new work -- TCP Single Flow, TCP Multiple Flow, using TCP RED
modifications (more Van Jacobson majic!) to handle multi-size windows.
Environment -- two different DS3 paths (NY->MICH: 20msec; NY->TEXAS->MICH:
68msec), four different versions of the RS6000 router software and Indy/SCs
Conditions -- Two background conditions (no background traffic, reverse TCP
flow intended to achieve 70-80% utilization)
Differing numbers of TCP flows.
Results are available on-line via http. Temporarily it is located at:
http://tweedledee.ans.net:8001:/
It will be on line rrdb.merit.edu more permanently.
It is important that vendors support RED and the two RFCs previously
mentioned to handle this problem. Also, Curtis believes that the results
presented by the NAP operators has little validity because there is no
delay as a component of their tests.
ATM -- What Tim Salo wants from ATM....
[I ran out of alertness, so I apologize to Tim for having extremely sketchy
notes on this talk.]
MAGIC -- Gigabit TestBed
Currently Local Area ATM switches over SONET. Mostly FORE switches.
LAN encapsulation (ATM Forum) versus RFC 1537
Stan | Academ Consulting Services |internet: sob(a)academ.com
Olan | For more info on academ, see this |uucp: bcm!academ!sob
Barber | URL- http://www.academ.com/academ |Opinions expressed are only mine.
3
2
Curtis,
Thanks for helping Stan build more comprehensive notes on what was, for me
at least, the most interesting RegionalTechs/NANOG meeting in recent memory.
I disagree with one statement you make several times...
(In the context of the Ameritech presentation)
> ... It was pointed out that with no delay in the tests,
> the delay bandwidth product of the TCP flows was near zero and it was
> asserted (by me actually) that results from such testing is not useful
> since real TCP flows going through a NAP have considerable delays.
I disagree that the lack of delay makes the tests 'not useful'. Yes, the
tests were much weaker than tests with delay. But such tests could still be
useful, since they demonstrate the presence or absence of problems other than
the problems caused by the bursty nature of wide-area high-speed TCP flows.
Actually, my criticism of the Ameritech presentation was that there was an
insufficiently clear statement of what they *had* learned. There were
allusions to problems with Cisco and workstations, but they were not specific
enough to be as helpful as they might have been.
>
> > PacBell NAP Status--Frank Liu
> >
> > [ ... ]
> >
> Again, no delay was added. Measured delay (ping time) was said to be
> 3 msec (presumably due to switching or slow host response). Again -
> It was pointed out that with no delay in the tests, the delay
> bandwidth product of the TCP flows was near zero and asserted that
> results from such testing is not useful.
>
Again, I disagree. Even in the absence of delay, some problems, including the
Kentrox bit-rate mismatch, could be observed and the loads that caused packet
loss could be observed.
> > ANS on performance --- Curtis Vallamizar
>
> The difficulty in carrying TCP traffic is proportional to the delay
> bandwidth product of the traffic, not just the bandwidth. Adding
> delay makes the potential for bursts sustained over a longer period.
> Real networks have delay. US cross continent delay is 70 msec.
>
> ANSNET results were given using improved software which improved
> buffer capacity, intentionally crippled software (artificially limited
> buffering), and software which included Random Early Detection (RED -
> described in a IEEE TON paper by Floyd and Jacobson). Sustained
> goodput rates of up to 40-41 Mb/s were acheived using ttcp and 1-8 TCP
> flows. Some pathelogical cases were demonstrated in which much worse
> performace was acheived. These case mostly involve too little
> buffering at the congestion point (intentionally crippled router code
> was used to demostrate this) or using a single TCP flow and setting
> the TCP window much too large (3-5 times the delay bandwidth product).
> The latter pathelogic case can be avoided if the routers implement
> RED. The conclusions were: 1) routers need buffer capacity as large
> as the delay bandwidth product and 2) routers should impement RED.
>
> Only a 20 msec delay was added to the prototype NAP testing. Results
> with the prototype NAP and 20 msec delay were very poor compared to
> the performance of unchannelized DS3. Prototype NAP testing results
> were poor compared to Ameritec and Pacbell results due to the more
> realistic delay bandwidth product. Worse results can be expected with
> a 70 msec delay and may be better indications of actual performance
> when forwarding real traffic. More testing is needed after fixes to
> ADSUs are applied. A sufficient bottleneck can not be created at the
> switch until ADSU problems are addressed.
>
> There was some discussion (at various times during the presentations)
> of what this all means for the NAPs. If I may summarize - On the
> positive side the Ameritec switch has more buffering than the Fore
> used in the Bellcore prototype NAP. On the negative side, Ameritec
> didn't include any delay in their testing. NAP testing results (both
> positive results from Amertic, mixed results from PacBel and negative
> results from ANS) are inconclusive so far.
Right. I really hope that everyone at the NANOG meeting took your results to
heart. It will be very important for the success of the multi-backbone
NSFnet world.
I agree that all three sets of tests should currently be regarded as partial
and, to some extent, inconclusive as you say. I hope that all those,
including BellCore, Ameritech, PacBell, and ANS continue with these tests and
with the sharing of the testing results.
One quibble: pathelogical should be spelled 'pathological'.
The root word is pathos, from which we also get the word sympathy. I guess
that those engaged in testing pathological ATM NAP situations should have more
sympathy for each other.
Cheers,
-- Guy
2
1