- Test - lists.nanog.org

Re: CIDR
by Steven K. Widmayer 14 Mar '94

14 Mar '94

>Jessica >Do we still propagate through the Internet the individual network >numbers associated with these routes ? > > Yakov: I believe it is still the case at the moment (test and > trial stage). If anyone, at this point, replaced its classful routes > with an aggregate route, please speak up. > > --Jessica > > > Jessica, I can tell you about a case last week where I encouraged Sprint to only configure the aggregate with NSFNET for 199.44.0/17, rather than the 128 separate routes. Though I don't see the route in the NSFNET routing tables yet, so I assume they are not announcing it yet. Also, perhaps this isn't a good idea, since the gist of this conversation indicates we are still in the testing phase? --Steve Widmayer

1 0

CIDR deployment
by yakov＠watson.ibm.com 14 Mar '94

14 Mar '94

Jessica, >The issues, which I can think of for now, needs to be addressed here are: > 1. Make sure no non-private ASs which are neither CIDRized nor > defaulting to other ASs. Given the size and the distributed nature of today's Internet, what you proposing doesn't seem to be a tractable problem. A more relevant, and certainly more tractable problem would be to find out whether all the ASs *directly* attached to AS 690 are either (a) CIDR-capable, or (b) point default to AS 690 or some other AS, and whether these ASs can register their CIDR prefixes with the MERIT Routing Policy Database today. Could MERIT provide us with this information ? > 2. Gain more confidence with the newly deployed CIDR in the networks. > More aggressive testing; injecting test CIDR routes to the Internet... While I have nothing against the concept of gaining "more confidence", I think that the "more aggressive testing" phase is already in the past. At this point I don't see "injecting of test CIDR routes to the Internet" as a valuable way of spending our resources. A better way to spend our resources and to gain *real* confidence with the newly deployed CIDR is to follow the strategy used by Havard: 1. Announce a CIDR aggregate 2. Remove individual components of the aggregate and test its impact on the connectivity. I would assume that Havard already has some form of a script that allows to test the connectivity, and that this script could be easily modified for use by other sites. While the test done by Havard doesn't guarantees that removing the individual components has no impact on *any* of the hosts in the Internet, it tests for the impact on connectivity to a good sample of the Internet. We need to understand that providing the former (a priory information on whether removing the individual components would impact connectivity to *any* host in the Internet) is an intractable problem, while providing the latter (assessing the impact of removing the individual components on connectivity to some sample of the Internet) is certainly doable (as shown by Havard). > 3. Establish procedures for ASs to announce the replacement of individual > net routes to aid the detection of potential impact/of removing > such routes from the Internet. > .... > Is 3 days in advance reasonable ? Announcing the replacement of individual components to the BGPD mailing list is a fine idea, but it seem to me that we don't need any special procedures for doing this (after all, all what it takes is just a piece of e-mail, and that is exactly what Havard did). With respect to whether "3 days in advance" is reasonable, we'll be better off by sticking with Havard's strategy, instead of dwelling on this topic. Yakov.

1 0

Re: CIDR
by Jessica Yu 11 Mar '94

11 Mar '94

>>1. Make sure no non-private ASs (for lack of a better work) >>which are neigher CIDRized nor defaulting to other ASs. >Err, could you restate that? I'm having a bit of a problem parsing this. Should be 'word' instead of 'work'. A real bad typo. It means all the ASs (exclude the ones which have no Internet connection) should be either CIDR capable or defaulting. >>2. Gain more confidenece with the newly deployed CIDR in the networks >>More aggressive testing: injecting test CIDR routes to the >>Internet, announce it to the bgpd list along with a couple >>of pingable hosts in the aggregate. >Haven't we done enough of this already? I think that EVERY site should go >through this phase to verify their configurations and make sure their neighbors >aren't doing anything stupid, but I see no need for a site that has been >CIDR-clueful for 6 months to continue pussyfooting about. I guess the question should be asked is that if most people feel comfortable enough to advertise aggregate yet? Look at AS690's, many sites have already BGP4 with AS690, but few advertises aggregate. Look at the whole internet, how many ASs advertising aggregate right now? >>3. Establish procedures for ASs to announce the replacement of >>individual net routes to aid the detection of potential impact/probl >>of removing such routes from the Internet. >>Andrew(?) suggested that ASs announce to the bgpd mailing >>list the list of individual intented to be replaced by >>an aggregate route several days prior to the remove. >>This should be a good start, shall we agree on do >>that? Is 3 days in advance reasonable ? >Is everyone in the world (or at least on bgpd) going to go to the trouble >of checking to see if they have a -correct- aggregate route covering >the individual networks and report problems if they do not? Furthermore, >if they don't have the route, what tools are there in place for tracking >down the lack of said route? If I'm advertising >131.108.0.0 >and 131.109.0.0 >and I want to replace them with 131.108.0.0/15, we can't track down the >AS who is swallowing the CIDR route until we actually rip out one of >the less specific routes. Given that hurdle, I suggest cutting the >administriva and yanking the less specific routes at a nice slow managable >rate and watching the fireworks. >Then we send neutron tipped traceroutes to anyone who is still blackholing >CIDR connectivity. :-) If 131.108 is really critical to my user, I will hate to have my user loose connectivity and yell at me. I'd do some work to anticipate the problem if there is any. I will do a traceroute to see what ASs my traffic to 131.108 traverses and find out the potential CIDR blackhole. Knowing 131.108 will be pulled out proir to its happening does give me advantage. If I do not care the destination that much, then I could wait until my user cry like you suggested. So I am still in favor of to have the information available in advance. --Jessica

2 1

Re: CIDR
by Vince Fuller 11 Mar '94

11 Mar '94

I'll be happy to feed you an aggregate tonight if BARRnet is now CIDR capable. You have permission to withdraw our more specific routes the microsecond our other service providers announce that they are all prepared to advertise the aggregate. Does that mean I can switch the cisco-BARRNet BGP to version 4? We are running BGP4-capable code on all BARRNet routers which matter, so we're ready to go at any time. Longest match routing. Bet seen. Likewise. --Vince

3 2

Re: CIDR
by Jessica Yu 11 Mar '94

11 Mar '94

Yakov, I am not aware of any concrete plan. Anyone? If no, let's work out a plan. The issues, which I can think of for now, needs to be addressed here are: 1. Make sure no non-private ASs (for lack of a better work) which are neigher CIDRized nor defaulting to other ASs. Existence of such AS will break the reachability of CIDR routes if individual classful net routes are replaced with CIDR routes. We need to set up a date by which we can assume all the ASs are either CIDRing and/or defaulting. 2. Gain more confidenece with the newly deployed CIDR in the networks More aggressive testing: injecting test CIDR routes to the Internet, announce it to the bgpd list along with a couple of pingable hosts in the aggregate. 3. Establish procedures for ASs to announce the replacement of individual net routes to aid the detection of potential impact/problem of removing such routes from the Internet. Andrew(?) suggested that ASs announce to the bgpd mailing list the list of individual intented to be replaced by an aggregate route several days prior to the remove. This should be a good start, shall we agree on do that? Is 3 days in advance reasonable ? --jessica Date: Thu, 10 Mar 1994 11:52:12 EST To: jyy(a)merit.edu cc: regional-techs(a)merit.edu, bgpd(a)merit.edu From: yakov(a)watson.ibm.com Subject: CIDR Return-Path: yakov(a)watson.ibm.com Ref: Your note of Thu, 10 Mar 1994 10:50:24 -0500 Jessica, >I believe it is still the case at the moment (test & trial stage) Are there any plans to move beyond the "test & trial stage" ? If yes, then do we have any concrete dates for when the individual networks (that form a single prefix) will be removed from the routing ? Yakov.

3 2

Re: CIDR
by Vince Fuller 11 Mar '94

11 Mar '94

Haven't we done enough of this already? I think that EVERY site should go through this phase to verify their configurations and make sure their neighbors aren't doing anything stupid, but I see no need for a site that has been CIDR-clueful for 6 months to continue pussyfooting about. ... Is everyone in the world (or at least on bgpd) going to go to the trouble of checking to see if they have a -correct- aggregate route covering the individual networks and report problems if they do not? Furthermore, if they don't have the route, what tools are there in place for tracking down the lack of said route? If I'm advertising 131.108.0.0 and 131.109.0.0 and I want to replace them with 131.108.0.0/15, we can't track down the AS who is swallowing the CIDR route until we actually rip out one of the less specific routes. Given that hurdle, I suggest cutting the administriva and yanking the less specific routes at a nice slow managable rate and watching the fireworks. OK, so when will cisco be ready to run BGP4 to us? Bluff called and raised. --Vince

2 1

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

11 Mar '94

**Note: Today's reports on nic.merit.edu may be delayed. The following changes have been made to the NSFNET policy-based routing database and will be installed on the backbone by 08:00 EST : Total = */8 + */16 + */24 + Other Configured Networks 26738 = 28 4496 22197 17 Added Networks 145 = 0 7 128 10 Deleted Networks 24 = 0 0 23 1 IP address Net name Country Priority:AS ---------- -------- ------- ----------- 129.240/15 UIONET C:NO 1:1800 2:1879 3:1133 4:1240 145.89/16 HSUTNET C:NL 1:1800 2:1133 3:1674 4:1240 147.141/16 SSGA C:US 1:2149 2:174 152.165/16 AVIDTECH C:US 1:2386 155.150/16 CCAD-CADD C:US 1:19 2:568 192.6.52/24 HP-ENG C:US 1:200 2:201 192.88.233/24 GE-INTERNET22 C:US 1:2149 2:174 192.114.178/24 IL-EXPORT-NET C:IL 1:2149 2:174 3:1800 4:1240 5:1133 192.121.86/23 LIBRIS-EDS C:SE 1:1800 2:1879 3:1133 4:1240 192.216.166/24 NTTAM-C-216-166 C:US 1:200 2:201 192.216.167/24 NTTAM-C-216-167 C:US 1:200 2:201 192.217.212/24 CICNET-BLOCK-217-212 C:US 1:267 2:1225 3:266 192.217.213/24 CICNET-BLOCK-217-213 C:US 1:267 2:1225 3:266 192.217.214/24 CICNET-BLOCK-217-214 C:US 1:267 2:1225 3:266 192.220.249/24 NWNET-SHOW2 C:US 1:101 2:685 3:73 192.250.24/22 EUNET-NL-192.250.24-A C:NL 1:701 2:1800 193.10.6/23 SE-SPPB C:SE 1:1800 2:1879 3:1133 4:1240 193.44.24/22 NUTNET1 C:SE 1:1800 2:1879 3:1133 4:1240 193.49.73/24 FR-ORLEANS02 C:FR 1:1800 2:1240 3:1133 4:1674 193.49.74/24 FR-ORLEANS03 C:FR 1:1800 2:1240 3:1133 4:1674 193.50.168/24 FR-INSATDGE1 C:FR 1:1800 2:1240 3:1133 4:1674 193.50.169/24 FR-INSATDGE2 C:FR 1:1800 2:1240 3:1133 4:1674 193.50.170/24 FR-INSAT2 C:FR 1:1800 2:1240 3:1133 4:1674 193.50.171/24 FR-INSAT3 C:FR 1:1800 2:1240 3:1133 4:1674 193.62.48/24 WORC-NET-1 C:GB 1:1800 2:1133 3:1240 193.62.49/24 WORC-NET-2 C:GB 1:1800 2:1133 3:1240 193.62.50/24 WORC-NET-3 C:GB 1:1800 2:1133 3:1240 193.62.51/24 WORC-NET-4 C:GB 1:1800 2:1133 3:1240 193.63.90/24 BALONDON C:GB 1:701 2:1800 193.67.128/22 EUNET-NL-193.67.128-A C:NL 1:701 2:1800 193.78.32/21 EUNET-NL-193.78.32-AG C:NL 1:701 2:1800 193.78.72/22 EUNET-NL-193.78.72-AG C:NL 1:701 2:1800 193.78.104/22 EUNET-NL-193.78.104-A C:NL 1:701 2:1800 193.78.120/23 EUNET-NL-193.78.120-A C:NL 1:701 2:1800 193.92.145/24 FORTH C:GR 1:1800 2:1133 3:1240 193.141.21/24 FUN C:DE 1:1324 2:1800 3:1240 4:1133 193.166.162/24 VTYH-NET-2 C:FI 1:1800 2:1879 3:1133 4:1240 193.196.172/24 BA-HEIDENHEIM-196-172 C:DE 1:293 2:291 193.196.173/24 BA-HEIDENHEIM-196-173 C:DE 1:293 2:291 198.6.192/24 KAIPERMNET1 C:US 1:701 2:702 198.22.101/24 TRLGOLD C:US 1:86 2:279 198.27.54/24 JSC-B30S54 C:US 1:771 2:372 3:297 198.30.215/24 OAR215 C:US 1:600 2:1800 198.76.68/24 NTIA-MD-C-76-68 C:US 1:86 2:279 198.76.69/24 NTIA-MD-C-76-69 C:US 1:86 2:279 198.76.70/24 NTIA-MD-C-76-70 C:US 1:86 2:279 198.76.71/24 NTIA-MD-C-76-71 C:US 1:86 2:279 198.76.72/24 NTIA-MD-C-76-72 C:US 1:86 2:279 198.77.5/24 MOUNTAIN-NET5 C:US 1:86 2:279 198.77.6/24 NET-MOUNTAIN-NET6 C:US 1:86 2:279 198.80.25/24 MMD-DMZ C:US 1:1330 198.99.246/24 USDOE-METC-C-99-246 C:US 1:86 2:279 198.99.247/24 USDOE-METC-C-99-247 C:US 1:86 2:279 198.99.248/24 USDOE-METC-C-99-248 C:US 1:86 2:279 198.99.249/24 USDOE-METC-C-99-249 C:US 1:86 2:279 198.119.132/24 NSI-C-119-132 C:US 1:297 2:372 198.119.133/24 NSI-C-119-133 C:US 1:297 2:372 198.119.134/24 NSI-C-119-134 C:US 1:297 2:372 198.150.56/24 WIS-DNR-C-150-56 C:US 1:1225 2:266 3:267 198.150.57/24 WIS-DNR-C-150-57 C:US 1:1225 2:266 3:267 198.150.58/24 WIS-DNR-C-150-58 C:US 1:1225 2:266 3:267 198.150.59/24 WIS-DNR-C-150-59 C:US 1:1225 2:266 3:267 198.150.60/24 WIS-DNR-C-150-60 C:US 1:1225 2:266 3:267 198.150.61/24 WIS-DNR-C-150-61 C:US 1:1225 2:266 3:267 198.150.62/24 WIS-DNR-C-150-62 C:US 1:1225 2:266 3:267 198.150.63/24 WIS-DNR-C-150-63 C:US 1:1225 2:266 3:267 198.187.178/24 ISS-HEADQTRS C:US 1:1329 198.187.179/24 ISS-HEADQTRS C:US 1:1329 198.187.180/24 ISS-HEADQTRS C:US 1:1329 198.187.181/24 ISS-HEADQTRS C:US 1:1329 198.187.182/24 ISS-HEADQTRS C:US 1:1329 198.187.183/24 ISS-HEADQTRS C:US 1:1329 198.187.184/24 ISS-HEADQTRS C:US 1:1329 198.187.185/24 ISS-HEADQTRS C:US 1:1329 198.187.186/24 ISS-HEADQTRS C:US 1:1329 198.187.187/24 ISS-HEADQTRS C:US 1:1329 198.188.160/24 CSUNET-SOUTH-188-160 C:US 1:2150 2:200 3:201 198.188.161/24 CSUNET-SOUTH-188-161 C:US 1:2150 2:200 3:201 198.202.64/24 SDSC-SHOWNET1 C:US 1:195 2:1740 198.202.65/24 SDSC-SHOWNET2 C:US 1:195 2:1740 198.209.46/24 MORENET-C C:US 1:1800 2:1240 199.1/16 NETBLK-SPRINT-BLKA C:US 1:1240 2:1800 199.2/16 NETBLK-SPRINT-BLKA C:US 1:1240 2:1800 199.3/16 NETBLK-SPRINT-BLKA C:US 1:1800 2:1240 199.10.146/24 PAXRVERNET6 C:US 1:19 2:568 199.10.147/24 PAXRVERNET7 C:US 1:19 2:568 199.15.0/24 ILLSOS-C-15-0 C:US 1:267 2:1225 3:266 199.15.1/24 ILLSOS-C-15-1 C:US 1:267 2:1225 3:266 199.15.2/24 ILLSOS-C-15-2 C:US 1:267 2:1225 3:266 199.15.3/24 ILLSOS-C-15-3 C:US 1:267 2:1225 3:266 199.15.4/24 ILLSOS-C-15-4 C:US 1:267 2:1225 3:266 199.15.5/24 ILLSOS-C-15-5 C:US 1:267 2:1225 3:266 199.15.6/24 ILLSOS-C-15-6 C:US 1:267 2:1225 3:266 199.15.7/24 ILLSOS-C-15-7 C:US 1:267 2:1225 3:266 199.17.88/24 MSUS-BLOCK1 C:US 1:1225 2:267 3:266 4:555 199.17.89/24 MSUS-BLOCK2 C:US 1:1225 2:267 3:266 4:555 199.17.90/24 MSUS-BLOCK3 C:US 1:1225 2:267 3:266 4:555 199.17.91/24 MSUS-BLOCK4 C:US 1:1225 2:267 3:266 4:555 199.17.92/24 MSUS-BLOCK5 C:US 1:1225 2:267 3:266 4:555 199.17.93/24 MSUS-BLOCK6 C:US 1:1225 2:267 3:266 4:555 199.17.94/24 MSUS-BLOCK7 C:US 1:1225 2:267 3:266 4:555 199.17.114/24 MSUS-BLOCK1 C:US 1:1225 2:267 3:266 4:555 199.17.115/24 MSUS-BLOCK2 C:US 1:1225 2:267 3:266 4:555 199.17.116/24 MSUS-BLOCK3 C:US 1:1225 2:267 3:266 4:555 199.17.117/24 MSUS-BLOCK4 C:US 1:1225 2:267 3:266 4:555 199.17.118/24 MSUS-BLOCK5 C:US 1:1225 2:267 3:266 4:555 199.17.119/24 MSUS-BLOCK6 C:US 1:1225 2:267 3:266 4:555 199.17.120/24 MSUS-BLOCK7 C:US 1:1225 2:267 3:266 4:555 199.17.121/24 MSUS-BLOCK8 C:US 1:1225 2:267 3:266 4:555 199.17.122/24 MSUS-BLOCK9 C:US 1:1225 2:267 3:266 4:555 199.17.123/24 MSUS-BLOCK10 C:US 1:1225 2:267 3:266 4:555 199.17.124/24 MSUS-BLOCK11 C:US 1:1225 2:267 3:266 4:555 199.17.125/24 MSUS-BLOCK12 C:US 1:1225 2:267 3:266 4:555 199.17.126/24 MSUS-BLOCK13 C:US 1:1225 2:267 3:266 4:555 199.17.127/24 MSUS-BLOCK14 C:US 1:1225 2:267 3:266 4:555 199.18.219/24 OARNET-CBLK2-219 C:US 1:600 199.29.85/24 PSINET-C4-85 C:US 1:2149 2:174 199.31.8/24 NEWPORTNET-C-31-8 C:US 1:19 2:568 199.31.9/24 NEWPORTNET-C-31-9 C:US 1:19 2:568 199.31.10/24 NEWPORTNET-C-31-10 C:US 1:19 2:568 199.31.11/24 NEWPORTNET-C-31-11 C:US 1:19 2:568 199.31.12/24 NEWPORTNET-C-31-12 C:US 1:19 2:568 199.86.72/24 MRNET-BLOCK3 C:US 1:1225 2:267 3:266 4:555 199.86.73/24 MRNET-BLOCK4 C:US 1:1225 2:267 3:266 4:555 199.86.74/24 MRNET-BLOCK5 C:US 1:1225 2:267 3:266 4:555 199.86.75/24 MRNET-BLOCK6 C:US 1:1225 2:267 3:266 4:555 199.86.76/24 MRNET-BLOCK7 C:US 1:1225 2:267 3:266 4:555 199.86.77/24 MRNET-BLOCK8 C:US 1:1225 2:267 3:266 4:555 199.86.78/24 MRNET-BLOCK9 C:US 1:1225 2:267 3:266 4:555 199.86.79/24 MRNET-BLOCK10 C:US 1:1225 2:267 3:266 4:555 199.98.46/24 PSINET-C5 C:US 1:2149 2:174 199.98.47/24 PSINET-C5 C:US 1:2149 2:174 199.98.48/24 PSINET-C5-48 C:US 1:2149 2:174 199.98.49/24 PSINET-C5-49 C:US 1:2149 2:174 199.98.50/24 PSINET-C5-50 C:US 1:2149 2:174 199.98.51/24 PSINET-C5-51 C:US 1:2149 2:174 199.98.52/24 PSINET-C5-52 C:US 1:2149 2:174 199.98.53/24 PSINET-C5-53 C:US 1:2149 2:174 199.98.55/24 PSINET-C5-55 C:US 1:2149 2:174 199.98.56/24 PSINET-C5-56 C:US 1:2149 2:174 199.98.57/24 PSINET-C5-57 C:US 1:2149 2:174 199.98.59/24 PSINET-C5-59 C:US 1:2149 2:174 199.120.195/24 OLYMPUS C:US 1:1982 199.120.204/24 ANYWARE2 C:US 1:1800 2:1240 199.120.211/24 NET-NEI C:US 1:2149 2:174 Deletions: --192.67.191/24 KLICK-NET3 C:DE 1:1324 2:1800 3:1240 4:1133 --192.67.192/24 KLICK-NET4 C:DE 1:1324 2:1800 3:1240 4:1133 --192.67.193/24 KLICK-NET5 C:DE 1:1324 2:1800 3:1240 4:1133 --192.67.194/24 KLICK-NET6 C:DE 1:1324 2:1800 3:1240 4:1133 --192.67.195/24 KLICK-NET7 C:DE 1:1324 2:1800 3:1240 4:1133 --192.67.196/24 KLICK-NET8 C:DE 1:1324 2:1800 3:1240 4:1133 --192.67.197/24 KLICK-NET9 C:DE 1:1324 2:1800 3:1240 4:1133 --192.67.198/24 KLICK-NET10 C:DE 1:1324 2:1800 3:1240 4:1133 --192.67.199/24 KLICK-NET11 C:DE 1:1324 2:1800 3:1240 4:1133 --192.67.200/24 KLICK-NET12 C:DE 1:1324 2:1800 3:1240 4:1133 --192.67.201/24 KLICK-NET13 C:DE 1:1324 2:1800 3:1240 4:1133 --192.67.202/24 KLICK-NET14 C:DE 1:1324 2:1800 3:1240 4:1133 --192.67.203/24 KLICK-NET15 C:DE 1:1324 2:1800 3:1240 4:1133 --192.67.204/24 KLICK-NET16 C:DE 1:1324 2:1800 3:1240 4:1133 --192.67.205/24 KLICK-NET17 C:DE 1:1324 2:1800 3:1240 4:1133 --192.67.206/24 KLICK-NET18 C:DE 1:1324 2:1800 3:1240 4:1133 --192.67.207/24 KLICK-NET19 C:DE 1:1324 2:1800 3:1240 4:1133 --192.67.208/24 KLICK-NET20 C:DE 1:1324 2:1800 3:1240 4:1133 --192.87.89/24 PTT-RES-TEST C:NL 1:1133 2:1674 3:1800 --192.108.50/24 FHB-STGT C:DE 1:1324 2:1800 3:1240 4:1133 --192.129.5/24 BA-KARLSRUHE C:DE 1:1324 2:1800 3:1240 4:1133 --193.196.174/24 HEIDENHEIM-C-196-174 C:DE 1:1324 2:1800 3:1240 4:1133 --193.196.175/24 HEIDENHEIM-C-196-175 C:DE 1:1324 2:1800 3:1240 4:1133 --199.1.254/23 NETBLK-SPRINT-BLKA C:US 1:1800 2:1240 Expanded listing, sorted by country, then by organization: ========================================================== Finland ------- Vasa Tekniska Yrkeshogskola, Wolfskavaegen 33, P.O.Box 6, FIN-65201 Vasa, FINLAND 1:1800 ICM-Atlantic 2:1879 EUROPE-RS 3:1133 CERN/DANTE 4:1240 ICM-Pacific -------------- 193.166.162/24 VTYH-NET-2 (FI) France ------ CITU, Universite d'Orleans, BP 6102, 45061 Orleans CEDEX 2, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ------------ 193.49.73/24 FR-ORLEANS02 (FR) 193.49.74/24 FR-ORLEANS03 (FR) Institut National des Sciences Appliquees de Toulouse, Complexe Scientifique de Rangueil - Departement de Genie Electrique, F-31077 Toulouse CEDEX, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ------------- 193.50.168/24 FR-INSATDGE1 (FR) 193.50.169/24 FR-INSATDGE2 (FR) Institut National des Sciences Appliquees de Toulouse, Complexe Scientifique de Rangueil, F-31077 Toulouse CEDEX, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:1133 CERN/DANTE 4:1674 CERN/DANTE ------------- 193.50.170/24 FR-INSAT2 (FR) 193.50.171/24 FR-INSAT3 (FR) Germany ------- Berufsakademie Heidenheim, Wilhelmstr. 10, Heidenheim, D-89518, GERMANY 1:293 Energy Science Network (FIX-East) 2:291 Energy Science Network (FIX-West) -------------- 193.196.172/24 BA-HEIDENHEIM-196-172 (DE) 193.196.173/24 BA-HEIDENHEIM-196-173 (DE) FUN! Feulner und Nahr GbR, Schuetzenstr. 11, D-76137 Karlsruhe, GERMANY 1:1324 ANS New York City - DNSS 35 2:1800 ICM-Atlantic 3:1240 ICM-Pacific 4:1133 CERN/DANTE ------------- 193.141.21/24 FUN (DE) Greece ------ Foundation of Research and Technology Hellas, Computer Science Institute, Daidalou 36, P.O. Box 1385, Heraklion, Crete, 71110, GREECE 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific ------------- 193.92.145/24 FORTH (GR) Israel ------ Israel Export Institute, 29 Hamered St., Tel-Aviv, P.O.B 50084, 68125, ISRAEL 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI 3:1800 ICM-Atlantic 4:1240 ICM-Pacific 5:1133 CERN/DANTE -------------- 192.114.178/24 IL-EXPORT-NET (IL) Netherlands ----------- Hogeschool Utrecht, P.O. Box 573, NL - 3500 AN Utrecht, NETHERLANDS 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1674 CERN/DANTE 4:1240 ICM-Pacific --------- 145.89/16 HSUTNET (NL) Stichting NLnet, Kruislaan 413, NL-1098 SJ Amsterdam, NETHERLANDS 1:701 Alternet 2:1800 ICM-Atlantic ------------- 192.250.24/22 EUNET-NL-192.250.24-A (NL) 193.67.128/22 EUNET-NL-193.67.128-A (NL) 193.78.32/21 EUNET-NL-193.78.32-AG (NL) 193.78.72/22 EUNET-NL-193.78.72-AG (NL) 193.78.104/22 EUNET-NL-193.78.104-A (NL) 193.78.120/23 EUNET-NL-193.78.120-A (NL) Norway ------ Department of Informatics, University of Oslo, P.O. Box 1080 Blindern, N-0316 Oslo, NORWAY 1:1800 ICM-Atlantic 2:1879 EUROPE-RS 3:1133 CERN/DANTE 4:1240 ICM-Pacific ---------- 129.240/15 UIONET (NO) Sweden ------ Kungliga Biblioteket, LIBRIS-avdelningen, Box 5039, S-102 41 Stockholm, SWEDEN 1:1800 ICM-Atlantic 2:1879 EUROPE-RS 3:1133 CERN/DANTE 4:1240 ICM-Pacific ------------- 192.121.86/23 LIBRIS-EDS (SE) NUTEK, Liljeholmsvagen 32, S-11786 STOCKHOLM, SWEDEN 1:1800 ICM-Atlantic 2:1879 EUROPE-RS 3:1133 CERN/DANTE 4:1240 ICM-Pacific ------------ 193.44.24/22 NUTNET1 (SE) Statens Psykologisk-Pedagogiska Bibliotek, Box 50063, S-104 05 Stockholm, SWEDEN 1:1800 ICM-Atlantic 2:1879 EUROPE-RS 3:1133 CERN/DANTE 4:1240 ICM-Pacific ----------- 193.10.6/23 SE-SPPB (SE) United Kingdom -------------- The British Academy, 20-21 Cornwall Terrace, London, NW1 4QP, Great Britain, UNITED KINGDOM 1:701 Alternet 2:1800 ICM-Atlantic ------------ 193.63.90/24 BALONDON (GB) Worcester College of Higher Education, Henwick Grove, St Johns, Worcester, WR2 6AJ, UNITED KINGDOM 1:1800 ICM-Atlantic 2:1133 CERN/DANTE 3:1240 ICM-Pacific ------------ 193.62.48/24 WORC-NET-1 (GB) 193.62.49/24 WORC-NET-2 (GB) 193.62.50/24 WORC-NET-3 (GB) 193.62.51/24 WORC-NET-4 (GB) United States ------------- American Heuristics Corp., 1 Millenium Ctr, Tridelphia, WV 26059, USA 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) ----------- 198.77.6/24 NET-MOUNTAIN-NET6 (US) Anyware Associates, 32 Woodland Rd., Boston, MA 02130, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific -------------- 199.120.204/24 ANYWARE2 (US) Avid Technology, Inc., Metropolitan Technology Park, 1 Park West, Tewksbury, MA 01876, USA 1:2386 INS-AS ---------- 152.165/16 AVIDTECH (US) Bureau of Medicine and Surgery, Naval Hospital, Newport, RI 02041-5046, USA 1:19 Milnet (FIX-East) 2:568 Milnet (FIX-West) ----------- 199.31.8/24 NEWPORTNET-C-31-8 (US) 199.31.9/24 NEWPORTNET-C-31-9 (US) 199.31.10/24 NEWPORTNET-C-31-10 (US) 199.31.11/24 NEWPORTNET-C-31-11 (US) 199.31.12/24 NEWPORTNET-C-31-12 (US) Bureau of Medicine and Surgery, Naval Medical Clinic, Patuxent NAS, Bldg 1370, Patuxent River, MD 20670-5370, USA 1:19 Milnet (FIX-East) 2:568 Milnet (FIX-West) ------------- 199.10.146/24 PAXRVERNET6 (US) 199.10.147/24 PAXRVERNET7 (US) CICNet, Inc., 2901 Hubbard Rd, Ann Arbor, MI 48105, USA 1:267 CICNET at UIUC 2:1225 CICNET at Argonne Labs 3:266 CICNET at MERIT -------------- 192.217.212/24 CICNET-BLOCK-217-212 (US) 192.217.213/24 CICNET-BLOCK-217-213 (US) 192.217.214/24 CICNET-BLOCK-217-214 (US) Continental Computer Systems, 835 North Mountain Road, Newington, CT 06111, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------ 199.98.50/24 PSINET-C5-50 (US) Corpus Christi Army Depot, Installation Engineering Division, Process Support Team Branch, Corpus Christi, TX 78419-6020, USA 1:19 Milnet (FIX-East) 2:568 Milnet (FIX-West) ---------- 155.150/16 CCAD-CADD (US) Fidelity Management & Research Company, 1431 Greenway Dr, Suite 1000, Irving, TX 75038, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------ 199.98.52/24 PSINET-C5-52 (US) General Electric Computer Service, 2825 Pacific Drive, Norcross, GA 30071, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------- 192.88.233/24 GE-INTERNET22 (US) Hacienda La Puente Unified School District, 15959 East Gale Avenue, City of Industry, CA 91716-0002, USA 1:2150 CSUNET-SW 2:200 BARRNet 3:201 BARRNet -------------- 198.188.160/24 CSUNET-SOUTH-C-188-160 (US) 198.188.161/24 CSUNET-SOUTH-C-188-161 (US) Hewlett-Packard Company, 3000 Hanover Street, Palo Alto, CA 94304, USA 1:200 BARRNet 2:201 BARRNet ----------- 192.6.52/24 HP-ENG (US) Hewlett-Packard Federal Systems, 3141 Fairview Park Dr, 3rd Floor, Falls Church, VA 22042, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------ 199.98.55/24 PSINET-C5-55 (US) Ideal Scanners & Systems Inc, 11810 Parklawn Drive, Rockville, MD 20852, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------ 199.98.51/24 PSINET-C5-51 (US) Illinois Secretary of State, 2701 South Dirksen Parkway, Springfield, IL 62703, USA 1:267 CICNET at UIUC 2:1225 CICNET at Argonne Labs 3:266 CICNET at MERIT ----------- 199.15.0/24 ILLSOS-C-15-0 (US) 199.15.1/24 ILLSOS-C-15-1 (US) 199.15.2/24 ILLSOS-C-15-2 (US) 199.15.3/24 ILLSOS-C-15-3 (US) 199.15.4/24 ILLSOS-C-15-4 (US) 199.15.5/24 ILLSOS-C-15-5 (US) 199.15.6/24 ILLSOS-C-15-6 (US) 199.15.7/24 ILLSOS-C-15-7 (US) Integrated Silicon Systems, Inc., 2222 Chapel Hill-Nelson Highway, Durham, NC 27713, USA 1:1329 ANS Greensboro - DNSS 75 -------------- 198.187.178/24 ISS-HEADQTRS (US) 198.187.179/24 ISS-HEADQTRS (US) 198.187.180/24 ISS-HEADQTRS (US) 198.187.181/24 ISS-HEADQTRS (US) 198.187.182/24 ISS-HEADQTRS (US) 198.187.183/24 ISS-HEADQTRS (US) 198.187.184/24 ISS-HEADQTRS (US) 198.187.185/24 ISS-HEADQTRS (US) 198.187.186/24 ISS-HEADQTRS (US) 198.187.187/24 ISS-HEADQTRS (US) Integration Partners, Ltd, 1450 E. American Lane, Suite 1442, Schaumburg, IL 60173, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------ 199.98.47/24 PSINET-C5 (US) Kaiser Permanente, 25 North Via Monte, Walnut Creek, CA 94598, USA 1:701 Alternet 2:702 Alternet ------------ 198.6.192/24 KAIPERMNET1 (US) ManTech Services Corp., 1313 Locus Ave, Fairmount, WV 26554, USA 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) ----------- 198.77.5/24 MOUNTAIN-NET5 (US) Marion Merrell Dow, 10236 Marion Park Drive, Kansas City, MO 64134, USA 1:1330 ANS St. Louis - DNSS 83 ------------ 198.80.25/24 MMD-DMZ (US) Merkley, Newman, Harty, 200 Varick Street, New York, NY 10014, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------ 199.98.57/24 PSINET-C5-57 (US) Metro Business Group, Inc., 4011 SW 47th Ave, Suite 1108, Fort Lauderdale, FL 33314, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------ 199.98.49/24 PSINET-C5-49 (US) Minnesota Regional Network, 511 11th Ave S, Box 212, Minneapolis, MN 55415, USA 1:1225 CICNET at Argonne Labs 2:267 CICNET at UIUC 3:266 CICNET at MERIT 4:555 Minnesota Supercomputer Center Network (MSCNet) ------------ 199.86.72/24 MRNET-BLOCK3 (US) 199.86.73/24 MRNET-BLOCK4 (US) 199.86.74/24 MRNET-BLOCK5 (US) 199.86.75/24 MRNET-BLOCK6 (US) 199.86.76/24 MRNET-BLOCK7 (US) 199.86.77/24 MRNET-BLOCK8 (US) 199.86.78/24 MRNET-BLOCK9 (US) 199.86.79/24 MRNET-BLOCK10 (US) Minnesota State University System, Computer Services Box 45, Mankato State University, P.O. Box 8400, Mankato, MN 56002-8400, 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.17.88/24 MSUS-BLOCK1 (US) 199.17.89/24 MSUS-BLOCK2 (US) 199.17.90/24 MSUS-BLOCK3 (US) 199.17.91/24 MSUS-BLOCK4 (US) 199.17.92/24 MSUS-BLOCK5 (US) 199.17.93/24 MSUS-BLOCK6 (US) 199.17.94/24 MSUS-BLOCK7 (US) 199.17.114/24 MSUS-BLOCK1 (US) 199.17.115/24 MSUS-BLOCK2 (US) 199.17.116/24 MSUS-BLOCK3 (US) 199.17.117/24 MSUS-BLOCK4 (US) 199.17.118/24 MSUS-BLOCK5 (US) 199.17.119/24 MSUS-BLOCK6 (US) 199.17.120/24 MSUS-BLOCK7 (US) 199.17.121/24 MSUS-BLOCK8 (US) 199.17.122/24 MSUS-BLOCK9 (US) 199.17.123/24 MSUS-BLOCK10 (US) 199.17.124/24 MSUS-BLOCK11 (US) 199.17.125/24 MSUS-BLOCK12 (US) 199.17.126/24 MSUS-BLOCK13 (US) 199.17.127/24 MSUS-BLOCK14 (US) Missouri Research and Education Network (MOREnet), University of Missouri-Columbia, Campus Computing, 200 Heinkel Bldg, Columbia, MO 65211, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ------------- 198.209.46/24 MORENET-C (US) Morgantown Energy Technology Center, Collins Ferry rd., Morgantown, WV 26505, USA 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) ------------- 198.99.246/24 USDOE-METC-C-99-246 (US) 198.99.247/24 USDOE-METC-C-99-247 (US) 198.99.248/24 USDOE-METC-C-99-248 (US) 198.99.249/24 USDOE-METC-C-99-249 (US) NASA Ames Research Center, MS 233-8, Moffett Field, CA 95014, USA 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) -------------- 198.119.132/24 NSI-C-119-132 (US) 198.119.133/24 NSI-C-119-133 (US) 198.119.134/24 NSI-C-119-134 (US) NASA Johnson Space Center, Houston, TX 77058, USA 1:771 Nasa Science Network (Houston) 2:372 Nasa Science Network (FIX-West) 3:297 Nasa Science Network (FIX-East) ------------ 198.27.54/24 JSC-B30S54 (US) NTT Software Laboratories, 800 El Camino Real West, Suite #103, Mountain View, CA 94040, USA 1:200 BARRNet 2:201 BARRNet -------------- 192.216.166/24 NTTAM-C-216-166 (US) 192.216.167/24 NTTAM-C-216-167 (US) National Telecommunications and Information Admin., 179 Admiral Cochrane Drive, Annapolis, MD 21401, USA 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) ------------ 198.76.68/24 NTIA-MD-C-76-68 (US) 198.76.69/24 NTIA-MD-C-76-69 (US) 198.76.70/24 NTIA-MD-C-76-70 (US) 198.76.71/24 NTIA-MD-C-76-71 (US) 198.76.72/24 NTIA-MD-C-76-72 (US) Network Express, 4251 Plymouth Road, Ann Arbor, MI 48105, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI -------------- 199.120.211/24 NET-NEI (US) New Paradigm Software Corporation, 335 Madison Ave., 11th Floor, New York, NY 10017, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------ 199.98.59/24 PSINET-C5-59 (US) NorthWestNet, 15400 SE 30th Place, Suite 202, Bellevue, WA 98007, USA 1:101 NorthWestNet Regional Network 2:685 NorthWestNet Regional Network 3:73 NorthWestNet Regional Network -------------- 192.220.249/24 NWNET-SHOW2 (US) OARnet, 1224 Kinnear Rd, Columbus, OH 43212, USA 1:600 OARNET, Cleveland, OH 2:1800 ICM-Atlantic ------------- 198.30.215/24 OAR215 (US) OARnet, 1224 Kinnear Road, Columbus, OH 43212, USA 1:600 OARNET, Cleveland, OH ------------- 199.18.219/24 OARNET-CBLK2-219 (US) Omron Advanced Systems, 3945 Freedom Circle, Suite 700, Santa Clara, CA 95054, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------ 199.98.53/24 PSINET-C5-53 (US) Protocol Systems, Inc., 8500 SW Creekside Place, Beaverton, OR 97005, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------ 199.29.85/24 PSINET-C4-85 (US) San Diego Supercomputer Center, 10100 Hopkins Drive, La Jolla, CA 92093-0505, USA 1:195 SDSC Regional network 2:1740 CERFnet ------------- 198.202.64/24 SDSC-SHOWNET1 (US) 198.202.65/24 SDSC-SHOWNET2 (US) Select Technology, Inc., 246 First Street, Suite 401, San Francisco, CA 94105, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------ 199.98.56/24 PSINET-C5-56 (US) State Street Bank and Trust Company, 225 Franklin Street, Boston, MA 02101, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ---------- 147.141/16 SSGA (US) Tec Doc Pub Inc., 399 River Road, Hudson, MA 01749, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------ 199.98.48/24 PSINET-C5-48 (US) Touchstone Research Laboratory, Ltd., 1 Millenium Ctr, Tridelphia, WV 26059, USA 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) ------------- 198.22.101/24 TRLGOLD (US) Townsend Communications Inc., 537 Tyler St., Port Townsend, WA 98368, USA 1:1982 Northwest Nexus -------------- 199.120.195/24 OLYMPUS (US) UES, Inc., 5162 Blazer Memorial Parkway, Dublin, OH 43017-1339, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------------ 199.98.46/24 PSINET-C5 (US) US Sprint, BSG, 13221 Woodland Rd, Herndon, VA 22071, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic -------- 199.1/16 NETBLK-SPRINT-BLKA (US) 199.2/16 NETBLK-SPRINT-BLKA (US) US Sprint, BSG, 13221 Woodland Rd, Herndon, VA 22071, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific -------- 199.3/16 NETBLK-SPRINT-BLKA (US) Wisconsin Department of Natural Resources, 101 S. Webster St., (P.O. Box 7921), Madison, WI 53702, USA 1:1225 CICNET at Argonne Labs 2:266 CICNET at MERIT 3:267 CICNET at UIUC ------------- 198.150.56/24 WIS-DNR-C-150-56 (US) 198.150.57/24 WIS-DNR-C-150-57 (US) 198.150.58/24 WIS-DNR-C-150-58 (US) 198.150.59/24 WIS-DNR-C-150-59 (US) 198.150.60/24 WIS-DNR-C-150-60 (US) 198.150.61/24 WIS-DNR-C-150-61 (US) 198.150.62/24 WIS-DNR-C-150-62 (US) 198.150.63/24 WIS-DNR-C-150-63 (US) ========================================================== The following Midlevel/Regional peering sessions have also been added: AS 101 - NorthWestNet Regional Network (US) - ENSS 143 Peer: 192.147.179.202 - NorthWestNet, 15400 SE 30th Place, Suite 202, Bellevue, WA 98007, USA - agsmb.ietf29.nwnet.net Peer: 192.35.180.202 - NorthWestNet, 15400 SE 30th Place, Suite 202, Bellevue, WA 98007, USA - agsmb.ietf29.nwnet.net AS 185 - MERIT-OFFNET - DNSS 51 Peer: 35.1.1.31 - MERIT Computer Network, University of Michigan, 1075 Beal Avenue, Ann Arbor, MI 48109, USA - rs.merit.edu Peer: 35.42.1.56 - MERIT Computer Network, University of Michigan, 1075 Beal Avenue, Ann Arbor, MI 48109, USA - obelix.merit.edu AS 685 - NorthWestNet Regional Network (US) - ENSS 143 Peer: 192.147.179.201 - NorthWestNet, 15400 SE 30th Place, Suite 202, Bellevue, WA 98007, USA - agstr.ietf29.nwnet.net Peer: 192.35.180.201 - NorthWestNet, 15400 SE 30th Place, Suite 202, Bellevue, WA 98007, USA - agstr.ietf29.nwnet.net ========================================================== The configuration reports which reflect today's update will be available for anonymous ftp on nic.merit.edu by 08:00 EST : configuration reports -- nic.merit.edu:nsfnet/announced.networks: as-as.now as-gw.now ans_core.now country.now net-comp.now nets.doc nets.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 March 1, 1994) TRANSITION TO GATED: The "routed" routing software on AS 690 was successfully replaced by "gated" on the morning of February 28. The routed files that used to be posted on nic.merit.edu:nsfnet/announced.networks are no longer produced; a full set of gated configuration files is now posted on that directory. CIDR: The first non-classful networks appeared in the PRDB, in its reports, and in the gated configuration files on March 1. NACRs for aggregates may be submitted to nsfnet-admin(a)merit.edu starting Friday, March 4. Please be sure to use the new version of the networks template from nic.merit.edu:nsfnet/announced.networks/template.net.v7.1 . 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: CIDR
by Vince Fuller 10 Mar '94

10 Mar '94

With tonights db run, we will be removing more specific routes. Not all of them, just a few @ first. A suggestion: *don't* remove them from the NSFNET database right away, just stop announcing them. That way if you run in to trouble, you can always start announcing them again without having to wait two-to-three days for a database update. --Vince

2 1

CIDR
by yakov＠watson.ibm.com 10 Mar '94

10 Mar '94

Ref: Your note of Thu, 10 Mar 1994 10:50:24 -0500 Jessica, >I believe it is still the case at the moment (test & trial stage) Are there any plans to move beyond the "test & trial stage" ? If yes, then do we have any concrete dates for when the individual networks (that form a single prefix) will be removed from the routing ? Yakov.

1 0

CIDR
by yakov＠watson.ibm.com 10 Mar '94

10 Mar '94

Jessica, >Below are some aggregate routes.... Do we still propagate through the Internet the individual network numbers associated with these routes ? Yakov

3 2