- Test - lists.nanog.org

Re: Thank you
by Sean Doran 06 Feb '95

06 Feb '95

Actually, what happened in this case was a typo in a filter list on icm-dc-1 which blocked the announcement from the Dante 4000. One or more of us here is at fault for accidentally adjusting things in the wrong way. Chalk up another round to fat finger syndrome... Some automation for updating some of AS 1800's configuration is in the works, so hopefully this won't be a recurring problem after that's done. We did have some difficulty in tracking this down initially, as we had no idea who should have been announcing AS 3058 routes to AS 1800, and the filter-list appeared good at first glance. Dante looked into things on their end over the past couple of days, and informed us that they were announcing things to us OK and that things looked OK on the Dante 4000 in D.C., and asked us to re-check the filter list. Sure enough, they were right, and the 120 line filter-list had a botch near the end. This was fixed this morning (D.C. time) and routing in this case seems to be working OK. A note went out to the people directly involved earlier today. Sean. - -- Sean Doran <smd(a)icp.net> / <smd(a)sprint.net> - -- | From sgoldste(a)nsf.gov Mon Feb 6 11:51:29 1995 | Received: from note1.nsf.gov (note1.nsf.gov [128.150.11.1]) by tiny.sprintlink.net (8.6.9/8.6.9) with SMTP id LAA10630; Mon, 6 Feb 1995 11:51:11 -0500 | Received: from [128.150.55.4] (sgoldste.cise.nsf.gov) by note1.nsf.gov with SMTP id AA14281 | (5.65c/IDA-1.4.4); Mon, 6 Feb 1995 11:50:50 -0500 | X-Sender: sgoldste(a)128.150.11.1 | Message-Id: <ab5bfe9b0a021004a6a1(a)[128.150.55.4]> | Mime-Version: 1.0 | Content-Type: text/plain; charset="us-ascii" | Date: Mon, 6 Feb 1995 11:49:46 -0500 | To: "Vasenin Valery A" <vasenin(a)top.rector.msu.su> | From: sgoldste(a)nsf.gov (Steve Goldstein) | Subject: Re: Thank you | Cc: Sean Doran <smd(a)sprint.net>, avg(a)titan.sprintlink.net (Vadim Antonov), | nwg(a)home.merit.edu | Status: RO | | At 7:36 PM 2/06/95, Vasenin Valery A wrote: | > Dear Steven! | > | > I'm deeply grateful to you for the timely solution about the | >announcement MSUNet in NSF. | > | > Sincerely yours Valery Vasenin. | | Dear Valery, | | Actually I had not done ANYTHING...yet. I read your first message earlier | this morning, and had not yet had the opportunity to look into the exact | nature of the problem, and then I get this new message from you. So, | please let me try to explain a few things that might shed light on the | problems of MSU's inablilty to communicate with portions of the NSFNET | community from time to time. | | Two things are happening that are probably related to the problems you have | been experiencing: | | 1. The NSFNET is being decomissioned (abandoned, going away), and it | is being replaced with several interconnected national Internet | service providers: MCInet, SprintLink, and ANSnet. The transition | is taking place now and will last fur a few months, and things are | not always stable during the transition. Route that work one hour | may be replaced with routs that do not always work in the next hour, | and these have to be identified and corrected. | | 2. The routers on the East Coast of the United States, mainly around | Washington, D.C., are "glowing red hot" with traffic overloads. Some | new code has been written to improve their performance, and network | experts try to install the new code and observe its performance at | low traffic times here (around our midnignt), which correspond to | periods of high activity in Russia with the 8-hour time difference. | One by-product of all the attempts to upgrade the code is "route | flapping" instability,in which the connectivity and routing | information contained in the routing tables cannot keep up with the | changing physical realities of the network itself: there is just too | much work for the routers to do, and they cannot keep up with both | packet switching and routing table updating. | | So, if your problems corrected themselves without my intervention at all, | my guess is that one or both of the above mechanisms must be the culprits. | If you continue to experience intermittent problems, please have your | technical people write to Sean Doran <smd(a)sprint.net> and/or Vadim Antonov | <avg(a)titan.sprintlink.net> at Sprint with the precise description of the | problems as you see them. | | There is no policy reason of which I am aware that would cause the problems | that you have experienced. We have been routing traffic from Russia for at | least a year, and I recall having seen that a new MSU network has just been | added to the data base. MAYBE what you have observed is that the addition | of the newly registered MSU network entry has just taken effect. Below, i | will copy a notice about the [proposed] new procedures to replace the | current NSFNT procedures for registering routing information. | | Best wishes, | | Steve

1 0

Re: Thank you
by sgoldste＠nsf.gov 06 Feb '95

06 Feb '95

At 7:36 PM 2/06/95, Vasenin Valery A wrote: > Dear Steven! > > I'm deeply grateful to you for the timely solution about the >announcement MSUNet in NSF. > > Sincerely yours Valery Vasenin. Dear Valery, Actually I had not done ANYTHING...yet. I read your first message earlier this morning, and had not yet had the opportunity to look into the exact nature of the problem, and then I get this new message from you. So, please let me try to explain a few things that might shed light on the problems of MSU's inablilty to communicate with portions of the NSFNET community from time to time. Two things are happening that are probably related to the problems you have been experiencing: 1. The NSFNET is being decomissioned (abandoned, going away), and it is being replaced with several interconnected national Internet service providers: MCInet, SprintLink, and ANSnet. The transition is taking place now and will last fur a few months, and things are not always stable during the transition. Route that work one hour may be replaced with routs that do not always work in the next hour, and these have to be identified and corrected. 2. The routers on the East Coast of the United States, mainly around Washington, D.C., are "glowing red hot" with traffic overloads. Some new code has been written to improve their performance, and network experts try to install the new code and observe its performance at low traffic times here (around our midnignt), which correspond to periods of high activity in Russia with the 8-hour time difference. One by-product of all the attempts to upgrade the code is "route flapping" instability,in which the connectivity and routing information contained in the routing tables cannot keep up with the changing physical realities of the network itself: there is just too much work for the routers to do, and they cannot keep up with both packet switching and routing table updating. So, if your problems corrected themselves without my intervention at all, my guess is that one or both of the above mechanisms must be the culprits. If you continue to experience intermittent problems, please have your technical people write to Sean Doran <smd(a)sprint.net> and/or Vadim Antonov <avg(a)titan.sprintlink.net> at Sprint with the precise description of the problems as you see them. There is no policy reason of which I am aware that would cause the problems that you have experienced. We have been routing traffic from Russia for at least a year, and I recall having seen that a new MSU network has just been added to the data base. MAYBE what you have observed is that the addition of the newly registered MSU network entry has just taken effect. Below, i will copy a notice about the [proposed] new procedures to replace the current NSFNT procedures for registering routing information. Best wishes, Steve ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Date: Fri, 13 Jan 1995 13:16:12 -0500 From: Elise Gerich <epg(a)merit.edu> To: nwg(a)home.merit.edu Subject: Change in NACR procedures Cc: epg(a)home.merit.edu In preparation for the retirement of the PRDB and the move to the Routing Arbiter (RA) architecture, Merit proposes to change our NACR-handling procedures to more closely mimic the registration procedures of the Internet Routing Registries. We propose to implement these changes on January 20, 1995. Please send any comments regarding the changes to merit-ie(a)merit.edu as soon as possible. Procedural changes: 1. NACRs for a given net will only be accepted from designated email addresses from the net's home AS or from the AS which is currently listed as the primary path according to the PRDB. To verify what the designated email addresses are for your Autonomous System number, use the whois client: whois -h prdb.merit.edu contact <as number> To update the designated email addresses for an Autonomous System, send email to DB-admin(a)ra.net. Please register the exact email address which will be used to add or change information in the PRDB. For example, if the designated email address is epg(a)merit.edu and the NACR is received from epg(a)pepper.merit.edu, it will be bounced. In general we anticipate that this change should pose little or no problem. In the event that a net changes providers, one of the following two procedures will have to be followed. Either (a) the administration of the net's home AS sends a NACR specifying the new provider as primary (and possibly deleting the old), or (b) the administration of the old provider sends the NACR. If the new provider wants to submit the NACR, they will need to send it to the administration of the home AS for forwarding to Merit. Very few administrators of home ASs which are behind ASs that peer directly with AS 690 have designated individuals and their associated email addresses as authorized to update the PRDB. For more information in establishing an aslist with Merit, please send a message to DB-admin(a)merit.edu. 2. ACKs/NACKs for NACRs will no longer be required, and in fact, will be ignored if received. 3. Copies of accepted NACRs will be sent to all associated ASs. This includes notification of changes to nets already in the PRDB. Typically, we would expect that all the ASs which are associated with a net would be aware of any change in routing preferences. However, this notification procedure will alert ASs that a change has taken place even if they had not previously been informed about the change. NACR Processing As of January 20, 1995, Merit will begin to implement this change. If mail to nsfnet-admin(a)merit.edu contains a NACR originated from an authorized account as described in procedural change (1), it will be processed. If it didn't, the mail will be bounced. If for some reason you want your NACR to be read even if it would otherwise be deemed unacceptable, include a non-null comment: field in the NACR. Summary: This is the first step in providing a transition to the RA architecture. We have been experiencing an increase in the number of NACRs which are being submitted to the NSFNET Backbone Service, many of which pertain to the movement of networks from one provider to another. For the month of December, nsfnet-admin(a)merit.edu received more than 4200 messages. More than 1200 changes were made to the PRDB on January 13, 1995. These new procedures will help to make the registration process more manageable. For those organizations which are in the process of changing to another provider (autonomous system), the organization can improve its chances of having changes to the PRDB made in a timely fashion and to protect itself against loss of reachability by: a. sending NACRs in advance of your cutover (at least one week) b. adding the new provider as secondary (tertiary, etc) c. having the new provider start announcing the route d. testing the route by having previous provider stop announcing the route e. sending a NACR deleting the previous provider Please check that you have designated correct email addresses for your Autonomous System prior to January 20,1995. Mail to nsfnet-admin(a)merit.edu which is a valid template and originates from an undesignated email address will be bounced back to the originator of the message starting on January 20, 1995. Thank you in advance for your cooperation. --Elise ================================================================ Steven N. Goldstein Program Director, Interagency & International Networking Coordination Div. of Networking and Communications Research & Infrastructure National Science Foundation 4201 Wilson Boulevard, Room 1175 Arlington, VA 22230 Tel: +1-703-306-1949 (Extension 1119) FAX: +1-703-306-0621 sgoldste(a)NSF.GOV ================================================================

1 0

Additions to the NSFNET policy-based routing database
by smm＠twain.merit.edu 02 Feb '95

02 Feb '95

------------------------------------------------------------------------------ The PRDB and this "NWG report" will be retired very soon. 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 EST : Total = As + Bs + Cs + Aggs Registered Networks 46745 = 30 5261 38851 2603 Configured Networks 43691 = 30 5204 35918 2539 Added Networks 430 = 0 16 372 42 Deleted Networks 3 = 0 0 2 1 IP address Net name Country Priority:AS ---------- -------- ------- ----------- 137.42/16 NET-SSI C:US 1:1239 2:1800 3:1240 137.137/16 BOE-SREN-NET C:US 1:2551(136) 2:1321 137.172/16 NET-FALNET C:AU 1:297(144) 2:297(145) 140.187/16 NET-BRAGG-GW1 C:US 1:568(145) 143.217/16 NET-SYDKRAFT C:SE 1:701(136) 2:701(134) 3:1800 149.244/16 KNORRB-LAN C:DE 1:1800 2:1240 3:1133 150.49/16 CTINET C:JP 1:2149 2:174 150.66/16 SUN-DENSHI-C C:JP 1:2149 2:174 150.236/16 TELI-NET C:SE 1:701(136) 2:701(134) 3:1800 151.114/16 HARRISDRACO C:US 1:3561(218) 2:3561(11) 3:279 4:86 157.14/16 AXIS-IP-NET C:JP 1:2149 2:174 159.164/16 RJRNI C:US 1:1239 2:1800 3:1240 162.117/16 RJRNI2 C:US 1:1239 2:1800 3:1240 164.9/16 WM-NET C:SE 1:701(136) 2:701(134) 3:1800 170.125/16 WIDCNET C:US 1:3561(218) 2:3561(11) 3:1225(130) 4:1225(131) 5:1225(129) 170.162/16 RJRNI-I C:US 1:1239 2:1800 3:1240 192.6.37/24 HPA-NET C:SE 1:701(136) 2:701(134) 3:1800 192.36.121/24 LU-LDC2 C:SE 1:701(136) 2:701(134) 3:1800 192.36.194/24 SE-ABBATOM C:SE 1:701(136) 2:701(134) 3:1800 192.43.161/24 NET-CYLINK C:US 1:3561(11) 2:3561(218) 3:200(128) 4:200(144) 192.43.164/24 TVTLAN-NETS C:SE 1:701(136) 2:701(134) 3:1800 192.43.224/24 PF-NET C:JP 1:2149 2:174 192.66.92/24 VARIOUS-192-66-BLOCK- C:DK 1:701(136) 2:701(134) 3:1800 192.71.70/24 SE-KSJU C:SE 1:701(136) 2:701(134) 3:1800 192.71.139/24 SE-DATA16 C:SE 1:701(136) 2:701(134) 3:1800 192.71.157/24 SE-NDIST C:SE 1:701(136) 2:701(134) 3:1800 192.71.189/24 LM-LMV C:SE 1:701(136) 2:701(134) 3:1800 192.71.192/24 TVT-SVALL C:SE 1:701(136) 2:701(134) 3:1800 192.73.48/24 UMT-NET C:US 1:685 2:73 3:101 192.75.58/24 SPECTR C:CA 1:1324(36) 2:2493(35) 3:2493(91) 192.92.49/24 DLJ2 C:US 1:2149 2:174 192.104.200/24 HOWARD-PUBSNETS C:US 1:2551(136) 2:1321 192.105.174/24 HP22 C:SE 1:701(136) 2:701(134) 3:1800 192.111.121/24 YMI C:US 1:2551(136) 2:1321 192.115.68/24 RAD-NET-C-115-68 C:IL 1:2149 2:174 3:1800 4:1240 5:1133 192.115.69/24 RAD-NET-C-115-69 C:IL 1:2149 2:174 3:1800 4:1240 5:1133 192.115.70/24 RAD-NET-C-115-70 C:IL 1:2149 2:174 3:1800 4:1240 5:1133 192.115.71/24 RAD-NET-C-115-71 C:IL 1:2149 2:174 3:1800 4:1240 5:1133 192.121.48/24 SE-ADBKONT C:SE 1:701(136) 2:701(134) 3:1800 192.121.179/24 SE-TELESYD C:SE 1:701(136) 2:701(134) 3:1800 192.121.196/24 SE-SANDSJUK C:SE 1:701(136) 2:701(134) 3:1800 192.134.111/24 INRA-CL-MDSR C:FR 1:1800 2:1240 3:1133 4:1674 192.152.80/24 NET-AISDEVNET C:US 1:2548 192.152.148/24 YNHH1 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 192.165.7/24 SE-PERIDOT C:SE 1:701(136) 2:701(134) 3:1800 192.165.112/24 SE-SMR C:SE 1:701(136) 2:701(134) 3:1800 192.165.230/24 SE-BASLID C:SE 1:701(136) 2:701(134) 3:1800 192.171.198/24 NERC-NET71 C:GB 1:1800 2:1133 3:1240 192.190.77/24 NEKTONICS C:US 1:1239 2:1800 3:1240 192.195.198/24 FFG-NET C:US 1:114 192.203.178/24 NET-CRYNWR C:US 1:1239 2:1800 3:1240 192.206.171/24 SKC C:US 1:685 2:73 3:101 192.206.190/24 CSINET3 C:US 1:1239 2:1800 3:1240 192.223.1/24 NETBLK-MEREDITH C:US 1:1239 2:1800 3:1240 4:1323 192.223.2/24 NETBLK-MEREDITH C:US 1:1239 2:1800 3:1240 4:1323 192.223.3/24 NETBLK-MEREDITH C:US 1:1239 2:1800 3:1240 4:1323 192.223.4/24 NETBLK-MEREDITH C:US 1:1239 2:1800 3:1240 4:1323 192.223.5/24 NETBLK-MEREDITH C:US 1:1239 2:1800 3:1240 4:1323 192.223.6/24 NETBLK-MEREDITH C:US 1:1239 2:1800 3:1240 4:1323 192.223.7/24 NETBLK-MEREDITH C:US 1:1239 2:1800 3:1240 4:1323 192.223.8/24 NETBLK-MEREDITH C:US 1:1239 2:1800 3:1240 4:1323 192.231.122/23 NET-LEMOYNE C:US 1:2149 2:174 3:1239 4:1800 5:1240 192.245.150/24 UVAFBI C:CL 1:3561(218) 2:3561(11) 3:86 4:279 192.246.224/21 NET-BARD C:US 1:2149 2:174 3:1239 4:1800 5:1240 192.246.232/22 NET-BARD C:US 1:2149 2:174 3:1239 4:1800 5:1240 193.43.76/24 USIS-ITALY-NET C:IT 1:293(144) 2:293(145) 3:1133 4:1674 5:1800 193.46.238/24 APA-NET C:AT 1:701(136) 2:701(134) 3:1800 193.49.7/24 FR-ARCHAMPS2 C:FR 1:1800 2:1240 3:1133 4:1674 193.51.13/24 FR-EWEB02 C:FR 1:1800 2:1240 3:1133 4:1674 193.51.14/24 FR-EWEB03 C:FR 1:1800 2:1240 3:1133 4:1674 193.56.41/24 FR-AERO-TO C:FR 1:1800 2:1240 3:1133 4:1674 193.81.166/24 TOPCALL-NET C:AT 1:701(136) 2:701(134) 3:1800 193.81.186/24 EUNET-AT-DEMO C:AT 1:701(136) 2:701(134) 3:1800 193.81.187/24 EUNET-AT-DEMO C:AT 1:701(136) 2:701(134) 3:1800 193.81.188/24 SPOE-NET C:AT 1:701(136) 2:701(134) 3:1800 193.101.24/21 INFODATA2 C:DE 1:1800 2:1240 3:1133 193.124.55/24 ICON C:UA 1:701(136) 2:701(134) 3:1800 193.124.118/24 ANGARA C:RU 1:701(136) 2:701(134) 3:1800 193.124.122/23 INFORIS-NET C:RU 1:701(136) 2:701(134) 3:1800 193.124.124/23 INFORIS-NET C:RU 1:701(136) 2:701(134) 3:1800 193.125.40/24 IAE-OKI C:RU 1:701(136) 2:701(134) 3:1800 193.125.41/24 IAE311 C:RU 1:701(136) 2:701(134) 3:1800 193.125.136/22 INFORIS-NET C:RU 1:701(136) 2:701(134) 3:1800 193.140.52/23 DUT-NET C:TR 1:1800 2:1239 3:1240 193.140.140/24 SELCUK-NET C:TR 1:1800 2:1239 3:1240 193.140.253/24 SAKARYA-NET C:TR 1:1800 2:1239 3:1240 193.180.64/19 SE-GBGGYM C:SE 1:701(136) 2:701(134) 3:1800 193.180.96/21 SE-GBGGYM C:SE 1:701(136) 2:701(134) 3:1800 193.180.104/21 SE-HBENERGY C:SE 1:701(136) 2:701(134) 3:1800 193.180.112/22 SE-HBENERGY C:SE 1:701(136) 2:701(134) 3:1800 193.180.164/23 SE-DATA16 C:SE 1:701(136) 2:701(134) 3:1800 193.180.182/24 SE-CISLAN C:SE 1:701(136) 2:701(134) 3:1800 193.180.222/24 SE-VESTHOJ C:SE 1:701(136) 2:701(134) 3:1800 193.181.24/24 TELI-ERMES C:SE 1:701(136) 2:701(134) 3:1800 193.181.234/24 SE-HSSKOV C:SE 1:701(136) 2:701(134) 3:1800 193.182.123/24 SE-JKP-ENERGY C:SE 1:701(136) 2:701(134) 3:1800 193.182.128/20 UNION-NET C:SE 1:701(136) 2:701(134) 3:1800 193.182.238/24 SE-ADBKON238 C:SE 1:701(136) 2:701(134) 3:1800 193.183.20/23 SE-UNIQ C:SE 1:701(136) 2:701(134) 3:1800 193.183.192/19 SE-JONKOM C:SE 1:701(136) 2:701(134) 3:1800 193.183.224/22 SE-GBGEN C:SE 1:701(136) 2:701(134) 3:1800 193.221.44/23 SCA-EURO C:SE 1:701(136) 2:701(134) 3:1800 193.234.220/23 SE-SALF C:SE 1:701(136) 2:701(134) 3:1800 193.235.16/24 SE-SKOPRI C:SE 1:701(136) 2:701(134) 3:1800 194.14.168/24 SE-XINIT C:SE 1:701(136) 2:701(134) 3:1800 194.46.5/24 UNIBOL.ATL C:US 1:1333 194.57.117/24 FR-DRCNRS C:FR 1:1800 2:1240 3:1133 4:1674 194.58.198/24 UGTU-NET C:RU 1:701(136) 2:701(134) 3:1800 194.58.201/24 YOURFT C:RU 1:701(136) 2:701(134) 3:1800 194.58.252/24 IFC-NET C:RU 1:701(136) 2:701(134) 3:1800 194.68.216/24 SE-MODUL1 C:SE 1:701(136) 2:701(134) 3:1800 194.68.240/20 UNION-NET C:SE 1:701(136) 2:701(134) 3:1800 194.114.157/24 SKANDIA2-NET C:SE 1:701(136) 2:701(134) 3:1800 196.7.134/24 MECALC C:ZA 1:701(136) 2:701(134) 198.22.116/24 NET-MAS C:US 1:1324 2:3577 198.60.88/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.62.137/24 MICROBILT-1 C:US 1:1800 2:1239 3:1240 198.62.138/24 MICROBILT-2 C:US 1:1800 2:1239 3:1240 198.64.246/24 CONNECTIONSCOM-1 C:US 1:114 198.64.247/24 CONNECTIONSCOM-2 C:US 1:114 198.69.80/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.69.81/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.69.84/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.69.85/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.69.86/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.69.87/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.69.89/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.69.90/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.69.91/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.69.92/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.69.93/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.69.94/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.69.95/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.69.184/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.69.185/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.69.186/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.69.187/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.69.188/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.69.189/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.69.190/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.69.191/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.70.176/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.70.177/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.70.178/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.70.179/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.70.180/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.70.181/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.70.182/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.70.183/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.70.184/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.70.185/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.70.186/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.70.187/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.70.188/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.70.189/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.70.190/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.70.191/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 198.135.197/24 NET-MAS2 C:US 1:1324 2:3577 198.135.198/24 NET-MAS3 C:US 1:1324 2:3577 198.139.135/24 LCCC1 C:US 1:97 198.139.136/24 LCCC2 C:US 1:97 198.161.120/24 NETBLK-CAUC-AB C:CA 1:2493(91) 2:2493(35) 198.161.121/24 NETBLK-CAUC-AB C:CA 1:2493(91) 2:2493(35) 198.161.122/24 NETBLK-CAUC-AB C:CA 1:2493(91) 2:2493(35) 198.161.123/24 NETBLK-CAUC-AB C:CA 1:2493(91) 2:2493(35) 198.164.96/24 NET96-NBTEL-NB-CA C:CA 1:577(133) 2:577(137) 3:577(143) 4:3561(218) 5:3561(11) 198.164.97/24 NET97-NBTEL-NB-CA C:CA 1:577(133) 2:577(137) 3:577(143) 4:3561(218) 5:3561(11) 198.164.98/24 NET98-NBTEL-NB-CA C:CA 1:577(133) 2:577(137) 3:577(143) 4:3561(218) 5:3561(11) 198.169.172/24 NETBLK-SASKECDEV-CA C:CA 1:577(143) 2:577(133) 3:577(137) 4:3561(11) 5:3561(218) 198.169.173/24 NETBLK-SASKECDEV-CA C:CA 1:577(143) 2:577(133) 3:577(137) 4:3561(11) 5:3561(218) 198.169.174/24 NETBLK-SASK C:CA 1:1331 198.169.190/24 NETBLK-STC-CA C:CA 1:577(143) 2:577(133) 3:577(137) 4:3561(11) 5:3561(218) 198.180.70/24 DLJ-C-180-70 C:US 1:2149 2:174 198.180.71/24 DLJ-C-180-71 C:US 1:2149 2:174 198.180.72/24 DLJ-C-180-72 C:US 1:2149 2:174 198.180.73/24 DLJ-C-180-73 C:US 1:2149 2:174 198.186.174/24 NETBLK-MEREDITH-NET C:US 1:1239 2:1800 3:1240 4:1323 198.186.175/24 NETBLK-MEREDITH-NET C:US 1:1239 2:1800 3:1240 4:1323 198.186.176/24 NETBLK-MEREDITH-NET C:US 1:1239 2:1800 3:1240 4:1323 198.186.177/24 NETBLK-MEREDITH-NET C:US 1:1239 2:1800 3:1240 4:1323 198.186.178/24 NETBLK-MEREDITH-NET C:US 1:1239 2:1800 3:1240 4:1323 198.200.163/24 NET-KYCSEP C:US 1:3561(218) 2:3561(11) 3:279 4:86 198.232.211/24 RL-DMZ C:US 1:685 2:73 3:101 198.250.128/24 NETBLK-AMEDD-C-250-12 C:US 1:568(145) 198.250.129/24 NETBLK-AMEDD-C-250-12 C:US 1:568(145) 198.250.130/24 NETBLK-AMEDD-C-250-13 C:US 1:568(145) 198.250.131/24 NETBLK-AMEDD-C-250-13 C:US 1:568(145) 198.250.132/24 NETBLK-AMEDD-C-250-13 C:US 1:568(145) 198.250.133/24 NETBLK-AMEDD-C-250-13 C:US 1:568(145) 198.250.134/24 NETBLK-AMEDD-C-250-13 C:US 1:568(145) 198.250.135/24 NETBLK-AMEDD-C-250-13 C:US 1:568(145) 198.250.136/24 NETBLK-AMEDD-C-250-13 C:US 1:568(145) 198.250.137/24 NETBLK-AMEDD-C-250-13 C:US 1:568(145) 198.250.138/24 NETBLK-AMEDD-C-250-13 C:US 1:568(145) 198.250.139/24 NETBLK-AMEDD-C-250-13 C:US 1:568(145) 198.250.140/24 NETBLK-AMEDD-C-250-14 C:US 1:568(145) 198.250.141/24 NETBLK-AMEDD-C-250-14 C:US 1:568(145) 198.250.142/24 NETBLK-AMEDD-C-250-14 C:US 1:568(145) 198.250.143/24 NETBLK-AMEDD-C-250-14 C:US 1:568(145) 198.250.144/24 NETBLK-AMEDD-C-250-14 C:US 1:568(145) 198.250.145/24 NETBLK-AMEDD-C-250-14 C:US 1:568(145) 198.250.146/24 NETBLK-AMEDD-C-250-14 C:US 1:568(145) 198.250.147/24 NETBLK-AMEDD-C-250-14 C:US 1:568(145) 198.250.148/24 NETBLK-AMEDD-C-250-14 C:US 1:568(145) 198.250.149/24 NETBLK-AMEDD-C-250-14 C:US 1:568(145) 198.250.150/24 NETBLK-AMEDD-C-250-15 C:US 1:568(145) 199.1.176/24 NET-DVILLE C:US 1:1800 2:1239 3:1240 199.1.178/24 NET-LANYON C:US 1:1240 2:1800 199.10.112/24 EASYSW-DOM C:US 1:1800 2:1239 3:1240 199.20.49/24 NEIBLK-OGILVY-WW C:US 1:2386 2:1321 199.33.18/24 NETBLK-MDC-CBLK C:US 1:1740(218) 2:1740(135) 199.33.218/23 NETBLK-MCCAW-WDD-DEV C:US 1:1240 2:1800 3:1239 199.45.126/24 UUNETCA-TEST C:CA 1:701(136) 2:701(134) 199.77.192/18 US-STATE-DOM C:US 1:3561(218) 2:3561(11) 3:86 4:279 199.92.16/24 MSTF-ME C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.120.94/24 NET-DWX C:US 1:1239 2:1800 3:1240 4:1323 199.120.98/24 NET-WITCC C:US 1:1239 2:1800 3:1240 199.120.99/24 NET-WITCC C:US 1:1239 2:1800 3:1240 199.120.100/24 NET-WITCC C:US 1:1239 2:1800 3:1240 199.126.20/24 GLOBELLE-CA C:CA 1:577(137) 2:577(133) 3:577(143) 4:3561(218) 5:3561(11) 199.126.21/24 HALIFAX C:CA 1:577(137) 2:577(133) 3:577(143) 4:3561(218) 5:3561(11) 199.126.22/24 GRASSROOTS C:CA 1:577(137) 2:577(133) 3:577(143) 4:3561(218) 5:3561(11) 199.126.23/24 AUBURNDRIVE C:CA 1:577(137) 2:577(133) 3:577(143) 4:3561(218) 5:3561(11) 199.126.24/24 OPIN-SRCH C:CA 1:577(137) 2:577(133) 3:577(143) 4:3561(218) 5:3561(11) 199.126.25/24 LUNCC.NSCC.CA C:CA 1:577(137) 2:577(133) 3:577(143) 4:3561(218) 5:3561(11) 199.126.26/24 GLOBELLE-CA-C-126-26 C:CA 1:577(137) 2:577(133) 3:577(143) 4:3561(218) 5:3561(11) 199.126.27/24 GLOBELLE-CA-C-126-27 C:CA 1:577(137) 2:577(133) 3:577(143) 4:3561(218) 5:3561(11) 199.126.128/24 SCHOOL-NS-CA C:CA 1:577(137) 2:577(133) 3:577(143) 4:3561(218) 5:3561(11) 199.126.136/24 PIPSC-CA-C-126-136 C:CA 1:577(137) 2:577(133) 3:577(143) 4:3561(218) 5:3561(11) 199.126.137/24 PIPSC-CA-C-126-137 C:CA 1:577(137) 2:577(133) 3:577(143) 4:3561(218) 5:3561(11) 199.126.138/24 PIPSC-CA-C-126-138 C:CA 1:577(137) 2:577(133) 3:577(143) 4:3561(218) 5:3561(11) 199.126.139/24 PIPSC-CA-C-126-139 C:CA 1:577(137) 2:577(133) 3:577(143) 4:3561(218) 5:3561(11) 199.126.140/24 PIPSC-CA-C-126-140 C:CA 1:577(137) 2:577(133) 3:577(143) 4:3561(218) 5:3561(11) 199.126.141/24 PIPSC-CA-C-126-141 C:CA 1:577(137) 2:577(133) 3:577(143) 4:3561(218) 5:3561(11) 199.126.142/24 PIPSC-CA-C-126-142 C:CA 1:577(137) 2:577(133) 3:577(143) 4:3561(218) 5:3561(11) 199.126.143/24 PIPSC-CA-C-126-143 C:CA 1:577(137) 2:577(133) 3:577(143) 4:3561(218) 5:3561(11) 199.172.190/24 DIEX-NET C:US 1:701(136) 2:701(134) 199.172.197/24 MOT-NET C:BM 1:701(136) 2:701(134) 199.181.96/24 WINDSOR C:US 1:3830 2:1800 3:1240 199.208.144/24 NET-C903NET C:US 1:568(144) 199.208.145/24 NET-C903NETR C:US 1:568(144) 199.212.88/24 CANADORON-CA-C-212-88 C:CA 1:577(133) 2:577(137) 3:577(143) 4:3561(218) 5:3561(11) 199.212.89/24 CANADORON-CA-C-212-89 C:CA 1:577(133) 2:577(137) 3:577(143) 4:3561(218) 5:3561(11) 199.219.128/24 NYSERNET-CBLK1 C:US 1:1662 199.219.129/24 NYSERNET-CBLK1 C:US 1:1662 199.219.130/24 NYSERNET-CBLK1 C:US 1:1662 199.219.131/24 NYSERNET-CBLK1 C:US 1:1662 199.219.132/24 NYSERNET-CBLK1 C:US 1:1662 199.219.133/24 NYSERNET-CBLK1 C:US 1:1662 199.219.134/24 NYSERNET-CBLK1 C:US 1:1662 199.219.135/24 NYSERNET-CBLK1 C:US 1:1662 199.219.136/24 NYSERNET-CBLK1 C:US 1:1662 199.219.137/24 NYSERNET-CBLK1 C:US 1:1662 199.219.138/24 NYSERNET-CBLK1 C:US 1:1662 199.219.139/24 NYSERNET-CBLK1 C:US 1:1662 199.219.140/24 NYSERNET-CBLK1 C:US 1:1662 199.219.141/24 NYSERNET-CBLK1 C:US 1:1662 199.219.142/24 NYSERNET-CBLK1 C:US 1:1662 199.219.143/24 NYSERNET-CBLK1 C:US 1:1662 199.224.96/21 NET-EPIX C:US 1:1239 2:1800 3:1240 199.254.157/24 NET-COMM C:US 1:1239 2:1800 3:1240 199.254.159/24 NET-NTN-US C:US 1:2551(136) 2:1321 200.0.10/23 NETBLK-REDE-UFES-9 C:BR 1:1740(218) 2:1740(135) 200.14.95/24 SISACL C:CL 1:3561(218) 2:3561(11) 3:86 4:279 202.12.125/24 NET-TIGERBAY C:AU 1:297(144) 2:297(145) 202.13.6/23 NOVA-LAN C:JP 1:701(136) 2:701(134) 202.16.232/24 IBBSAL-NET C:JP 1:2149 2:174 202.24.253/24 SENET C:JP 1:2149 2:174 202.31.217/24 SGMINET1 C:KR 1:297(144) 2:297(145) 202.31.218/24 SGMINET3 C:KR 1:297(144) 2:297(145) 202.31.219/24 SGMINET4 C:KR 1:297(144) 2:297(145) 202.33.54/24 PARADIGM-NET C:JP 1:2149 2:174 202.33.58/24 NSGNET C:JP 1:2149 2:174 202.33.59/24 PALNET C:JP 1:2149 2:174 202.248.65/24 EBARA-NET C:JP 1:2149 2:174 202.252.113/24 MELFANSNET C:JP 1:2149 2:174 203.255.124/24 SGMINET5 C:KR 1:297(144) 2:297(145) 203.255.125/24 SGMINET6 C:KR 1:297(144) 2:297(145) 203.255.126/24 SGMINET7 C:KR 1:297(144) 2:297(145) 203.255.127/24 SGMINET8 C:KR 1:297(144) 2:297(145) 204.6.86/24 PSINET-C4 C:US 1:2149 2:174 204.6.87/24 PSINET-C5 C:US 1:2149 2:174 204.6.88/24 PSINET-C6 C:US 1:2149 2:174 204.6.89/24 PSINET-C7 C:US 1:2149 2:174 204.6.90/24 PSINET-C8 C:US 1:2149 2:174 204.6.94/24 PSINET-C4 C:US 1:2149 2:174 204.6.95/24 PSINET-C5 C:US 1:2149 2:174 204.6.96/24 PSINET-C6 C:US 1:2149 2:174 204.6.97/24 PSINET-C7 C:US 1:2149 2:174 204.19.192/24 STS-SYSTEMS-C-19-192 C:CA 1:577(137) 2:577(133) 3:577(143) 4:3561(218) 5:3561(11) 204.19.193/24 STS-SYSTEMS-C-19-193 C:CA 1:577(137) 2:577(133) 3:577(143) 4:3561(218) 5:3561(11) 204.19.194/24 STS-SYSTEMS-C-19-194 C:CA 1:577(137) 2:577(133) 3:577(143) 4:3561(218) 5:3561(11) 204.19.195/24 STS-SYSTEMS-C-19-195 C:CA 1:577(137) 2:577(133) 3:577(143) 4:3561(218) 5:3561(11) 204.19.196/24 STS-SYSTEMS-C-19-196 C:CA 1:577(137) 2:577(133) 3:577(143) 4:3561(218) 5:3561(11) 204.19.197/24 STS-SYSTEMS-C-19-197 C:CA 1:577(137) 2:577(133) 3:577(143) 4:3561(218) 5:3561(11) 204.19.198/24 STS-SYSTEMS-C-19-198 C:CA 1:577(137) 2:577(133) 3:577(143) 4:3561(218) 5:3561(11) 204.19.199/24 STS-SYSTEMS-C-19-199 C:CA 1:577(137) 2:577(133) 3:577(143) 4:3561(218) 5:3561(11) 204.19.206/24 MCDOUG-NET1 C:CA 1:1324(36) 2:2493(35) 3:2493(91) 204.19.207/24 MCDOUG-NET1 C:CA 1:1324(36) 2:2493(35) 3:2493(91) 204.19.220/24 LGSNET C:CA 1:1324 2:2493(35) 3:2493(91) 204.19.224/24 INFOROUTE-NET1 C:CA 1:1324(36) 2:2493(35) 3:2493(91) 204.19.225/24 INFOROUTE-NET1 C:CA 1:1324(36) 2:2493(35) 3:2493(91) 204.19.245/24 NETBLK-GRANBY-JRV C:CA 1:1324 2:2493(35) 3:2493(91) 204.19.246/24 NETBLK-GRANBY-JRV C:CA 1:1324 2:2493(35) 3:2493(91) 204.19.247/24 NETBLK-GRANBY-JRV C:CA 1:1324 2:2493(35) 3:2493(91) 204.27.64/18 COMMUNIQUE C:US 1:701(136) 2:701(134) 204.27.214/24 CKP C:US 1:1239 2:1800 3:1240 204.36.17/24 NEWNET-C-36-17 C:US 1:3830 2:1800 3:1240 204.36.18/24 NEWNET-C-36-18 C:US 1:3830 2:1800 3:1240 204.36.19/24 NEWNET-C-36-19 C:US 1:3830 2:1800 3:1240 204.36.20/24 NEWNET-C-36-20 C:US 1:3830 2:1800 3:1240 204.36.21/24 NEWNET-C-36-21 C:US 1:3830 2:1800 3:1240 204.36.22/24 NEWNET-C-36-22 C:US 1:3830 2:1800 3:1240 204.36.23/24 NEWNET-C-36-23 C:US 1:3830 2:1800 3:1240 204.36.24/24 NEWNET-C-36-24 C:US 1:3830 2:1800 3:1240 204.36.25/24 NEWNET-C-36-25 C:US 1:3830 2:1800 3:1240 204.36.26/24 NEWNET-C-36-26 C:US 1:3830 2:1800 3:1240 204.36.27/24 NEWNET-C-36-27 C:US 1:3830 2:1800 3:1240 204.36.28/24 NEWNET-C-36-28 C:US 1:3830 2:1800 3:1240 204.36.29/24 NEWNET-C-36-29 C:US 1:3830 2:1800 3:1240 204.36.30/24 NEWNET-C-36-30 C:US 1:3830 2:1800 3:1240 204.36.31/24 NEWNET-C-36-31 C:US 1:3830 2:1800 3:1240 204.40.149/24 DPRCSSB C:CA 1:577(133) 2:577(137) 3:577(143) 4:3561(218) 5:3561(11) 204.41.13/24 SCAR-C-41-13 C:CA 1:577(133) 2:577(137) 3:577(143) 4:3561(218) 5:3561(11) 204.41.14/24 SCAR-C-41-14 C:CA 1:577(133) 2:577(137) 3:577(143) 4:3561(218) 5:3561(11) 204.41.15/24 SCAR-C-41-15 C:CA 1:577(133) 2:577(137) 3:577(143) 4:3561(218) 5:3561(11) 204.41.16/24 SCAR-C-41-16 C:CA 1:577(133) 2:577(137) 3:577(143) 4:3561(218) 5:3561(11) 204.41.17/24 SCAR-C-41-17 C:CA 1:577(133) 2:577(137) 3:577(143) 4:3561(218) 5:3561(11) 204.41.18/24 SCAR-C-41-18 C:CA 1:577(133) 2:577(137) 3:577(143) 4:3561(218) 5:3561(11) 204.41.19/24 SCAR-C-41-19 C:CA 1:577(133) 2:577(137) 3:577(143) 4:3561(218) 5:3561(11) 204.41.20/24 SCAR-C-41-20 C:CA 1:577(133) 2:577(137) 3:577(143) 4:3561(218) 5:3561(11) 204.41.21/24 SCAR-C-41-21 C:CA 1:577(133) 2:577(137) 3:577(143) 4:3561(218) 5:3561(11) 204.41.22/24 SCAR-C-41-22 C:CA 1:577(133) 2:577(137) 3:577(143) 4:3561(218) 5:3561(11) 204.41.23/24 SCAR-C-41-23 C:CA 1:577(133) 2:577(137) 3:577(143) 4:3561(218) 5:3561(11) 204.41.24/24 SCAR-C-41-24 C:CA 1:577(133) 2:577(137) 3:577(143) 4:3561(218) 5:3561(11) 204.41.25/24 SCAR-C-41-25 C:CA 1:577(133) 2:577(137) 3:577(143) 4:3561(218) 5:3561(11) 204.41.26/24 SCAR-C-41-26 C:CA 1:577(133) 2:577(137) 3:577(143) 4:3561(218) 5:3561(11) 204.41.27/24 SCAR-C-41-27 C:CA 1:577(133) 2:577(137) 3:577(143) 4:3561(218) 5:3561(11) 204.41.28/24 SCAR-C-41-28 C:CA 1:577(133) 2:577(137) 3:577(143) 4:3561(218) 5:3561(11) 204.41.30/24 SCAR-C-41-28 C:CA 1:577(133) 2:577(137) 3:577(143) 4:3561(218) 5:3561(11) 204.41.31/24 SCAR-C-41-29 C:CA 1:577(133) 2:577(137) 3:577(143) 4:3561(218) 5:3561(11) 204.41.32/24 SCAR-C-41-30 C:CA 1:577(133) 2:577(137) 3:577(143) 4:3561(218) 5:3561(11) 204.41.33/24 SCAR-C-41-31 C:CA 1:577(133) 2:577(137) 3:577(143) 4:3561(218) 5:3561(11) 204.41.34/24 SCAR-C-41-32 C:CA 1:577(133) 2:577(137) 3:577(143) 4:3561(218) 5:3561(11) 204.52.238/24 SNEAKERNET C:US 1:1239 2:1800 3:1240 204.62.159/24 NET-FREDNET2 C:US 1:2548 204.62.201/24 SKC2 C:US 1:685 2:73 3:101 204.62.202/24 SKC3 C:US 1:685 2:73 3:101 204.62.203/24 SKC4 C:US 1:685 2:73 3:101 204.62.204/24 SKC5 C:US 1:685 2:73 3:101 204.62.205/24 SKC6 C:US 1:685 2:73 3:101 204.68.134/24 INFOGO C:US 1:1239 2:1800 3:1240 204.69.64/18 JPSS-LA C:US 1:701(136) 2:701(134) 204.79.53/24 INFOLAN-CBLK4 C:US 1:2149 2:174 204.87.150/24 GRISSOM-GEL C:US 1:1240 2:1800 3:1239 204.97.233/24 NET-FPC2 C:US 1:1239 2:1800 3:1240 204.101.50/24 NFLDTEL C:CA 1:1800 2:1239 3:1240 204.112.7/24 TELENIUM C:CA 1:577(137) 2:577(133) 3:577(143) 4:3561(218) 5:3561(11) 204.128.158/24 DEINET C:US 1:1240 2:1800 3:1239 204.138.36/24 NET-WESTVIEW2 C:CA 1:1239 2:1800 3:1240 204.138.38/24 NET-DAVGRO C:CA 1:1239 2:1800 3:1240 204.138.115/24 OPENTEXT-NET C:CA 1:1239 2:1800 3:1240 204.144.0/23 FDLESWC C:US 1:1800 2:1239 3:1240 204.145.8/24 LES C:US 1:93 204.145.9/24 LES C:US 1:93 204.145.10/24 LES C:US 1:93 204.145.11/24 LES C:US 1:93 204.145.12/24 LES C:US 1:93 204.145.13/24 LES C:US 1:93 204.145.14/24 LES C:US 1:93 204.145.15/24 LES C:US 1:93 204.145.138/24 CKP2 C:US 1:1239 2:1800 3:1240 204.145.153/24 BALLOWE-CONS C:US 1:1240 2:1800 3:1239 204.145.186/24 NSEA C:US 1:1239 2:1800 3:1240 204.145.211/24 CTIS-NET C:US 1:3561(218) 2:3561(11) 3:1225(130) 4:1225(129) 5:1225(131) 6:1239 7:1240 8:1800 204.147.143/24 NETBLK-VBNS-NET C:US 1:3561(218) 2:3561(11) 3:86 4:279 5:1879 204.150.152/24 ANS-C-BLOCK3 C:US 1:1324 204.150.153/24 ANS-C-BLOCK3 C:US 1:1324 204.150.180/24 ANS-C-BLOCK3 C:US 1:1327 204.164.74/24 GMPC-74 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.164.75/24 GMPC-75 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.164.184/24 OCLN-NET1 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 204.168.112/22 NET-GREATNECK.LIB.NY C:US 1:1239 2:1800 3:1240 204.168.120/24 NET-GREATNECK.LIB.NY C:US 1:1239 2:1800 3:1240 204.168.122/23 NET-BROOKLAW C:US 1:1239 2:1800 3:1240 204.168.126/23 NET-SIENA C:US 2:1800 3:1240 204.168.128/22 NET-NIO.LIB.NY C:US 1:1239 2:1800 3:1240 204.168.132/22 NET-UHS C:US 1:1239 2:1800 3:1240 204.174.206/24 NCP.BC.CA C:CA 1:1331 204.174.207/24 NCP.BC.CA C:CA 1:1331 204.174.208/24 NCP.BC.CA C:CA 1:1331 204.174.209/24 NCP.BC.CA C:CA 1:1331 204.174.210/24 NCP.BC.CA C:CA 1:1331 204.174.238/24 CTRS-BC-CA C:CA 1:2493(91) 2:2493(35) 204.176.212/24 DOWNEAST C:US 1:701(136) 2:701(134) 204.177.222/24 ICMEBS C:US 1:701(136) 2:701(134) 204.178.0/19 ATT-NET C:US 1:701(136) 2:701(134) 204.179.80/21 FYI C:US 1:701(136) 2:701(134) 204.179.97/24 NCB C:US 1:1957 204.179.104/24 DATAPROMPT-NET C:US 1:701(136) 2:701(134) 204.179.106/24 ARCTIC-NET C:US 1:701(136) 2:701(134) 204.179.107/24 METRICOM-NET1 C:US 1:701(136) 2:701(134) 204.179.109/24 UUNET-TEST C:US 1:701(136) 2:701(134) 204.181.84/24 CIS-CORP.COM C:US 1:1800 2:1239 3:1240 204.181.85/24 PEGALO C:US 1:1239 2:1800 3:1240 204.181.160/21 SPRINT-CCB5A7 C:US 1:1800 2:1239 3:1240 204.183.193/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 204.183.194/24 NET-MICROSERVE C:US 1:1239 2:1800 3:1240 204.187.48/24 NET-CHSHQ-CD-NET C:CA 1:577(133) 2:577(137) 3:577(143) 4:3561(218) 5:3561(11) 204.187.62/23 NETACCESS C:CA 1:1239 2:1800 3:1240 204.187.80/24 NET-JANSSEN C:CA 1:1240 2:1800 3:1239 204.198.144/24 FARINON-FR C:US 1:3561(218) 2:3561(11) 3:279 4:86 204.198.145/24 FARINON-FR C:US 1:3561(218) 2:3561(11) 3:279 4:86 204.198.146/24 FARINON-FR C:US 1:3561(218) 2:3561(11) 3:279 4:86 204.213.69/24 NET-INTEC C:US 1:1239 2:1800 3:1240 204.214.30/23 NET-EMASS C:US 1:1239 2:1800 3:1240 204.215.3/24 NET-CSG C:US 1:1239 2:1800 3:1240 204.220.3/24 SABRENET C:US 1:3561(218) 2:3561(11) 3:1225(130) 4:1225(129) 5:1225(131) 6:1239 7:1240 8:1800 204.220.8/21 EFJOHNSON1 C:US 1:3561(218) 2:3561(11) 3:1225(130) 4:1225(129) 5:1225(131) 6:1239 7:1240 8:1800 204.220.40/21 MPS C:US 1:3561(218) 2:3561(11) 3:1225(130) 4:1225(129) 5:1225(131) 6:1239 7:1240 8:1800 204.225.240/24 NETBLK2-INTERLOG C:CA 1:2493(35) 2:2493(91) 204.225.241/24 NETBLK2-INTERLOG C:CA 1:2493(35) 2:2493(91) 204.225.242/24 NETBLK2-INTERLOG C:CA 1:2493(35) 2:2493(91) 204.225.243/24 NETBLK2-INTERLOG C:CA 1:2493(35) 2:2493(91) 204.225.244/24 NETBLK2-INTERLOG C:CA 1:2493(35) 2:2493(91) 204.225.245/24 NETBLK2-INTERLOG C:CA 1:2493(35) 2:2493(91) 204.225.246/24 NETBLK2-INTERLOG C:CA 1:2493(35) 2:2493(91) 204.225.247/24 NETBLK2-INTERLOG C:CA 1:2493(35) 2:2493(91) 204.234/16 NEK12NET2 C:US 1:93 204.240/14 PSI-BLK-C2 C:US 1:2149 2:174 Deletions: --204.27.64/24 COMMUNIQUE C:US 1:701(136) 2:701(134) --204.27.65/24 LAITRAM-NET C:US 1:701(136) 2:701(134) --204.220.8/22 EFJOHNSON C:US 1:3561(218) 2:3561(11) 3:1225(130) 4:1225(129) 5:1225(131) 6:1239 7:1240 8:1800 Expanded listing, sorted by country, then by organization: ========================================================== The "Expanded Listings" section of this NWG report has been retired since it is sorted by countries and network organization addresses. The replacement configuration generation system is based on the Internet Routing Registry (briefly called the "Global Routing Registry"). See the file ftp.ra.net:pub/radb/OVERVIEW for more information. The remainder of this report will also be retired shortly. AS690 CIDR Squeezings Report: 9944 Nets, 172 ASs, 2727 Aggregates ------------------------------------------------------------------ 9944 (85%) of the ever-announced more-specific routes within aggregates have been withdrawn. 148 of those were withdrawn within the last week. 142 the week before that. 391 the week before that. 172 ASs have registered aggregates in the PRDB. 152 of those are announcing aggregates. 82 have withdrawn at least one more specific route. 2727 Aggregates are configured. 1947 of these were Top-Level Aggregates (not nested in another aggregate). 1499 of these are being announced to AS690. 1035 of those have at least one subnet configured (the other 464 may be saving the Internet future subnet announcements). 862 have stopped announcing at least one configured more specific route. 834 have stopped announcing half of their configured more specific routes. 773 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 EST : configuration reports -- nic.merit.edu:nsfnet/announced.networks: as-as.now as-gw.now ans_core.now country.now net-comp.now nets.doc nets.non-classful nets.tag.now nets.unl.now NSS routing software configuration files -- nic.merit.edu:nsfnet/backbone.configuration: gated.nss<NSS number>.t3p Information is also avaiable through the PRDB whois server. Type "whois -h prdb.merit.edu help" for details. -------------------------------------------------------------------------- PRDB CHANGES: (Updated January 19, 1994) As of 1/19/95, ACKs and NAKs will no loger be required (or even read) in the processing of NACRs. In early 1995, as part of the transition to the new Internet Routing Registry (IRR), 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)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 Internet 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 from the directory "ftp.ra.net:pub/radb". 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 and RADB 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. ******************************* --Steven J. Richardson Merit/NSFNET sjr(a)merit.edu

1 0

Re: RFC 1597/Firewalls
by Sean Doran 01 Feb '95

01 Feb '95

| (contrary to my previous | assertion, my boss is insisting I go to the NANOG meeting) I'm sorry for you personally, but I'm glad this is the case because I think this: | a small 'discussion' regarding the RFC | 1597/1627 swamp would be appropriate during the "CIDR/Aggregation/ | Allocation Policies" discussion on Thursday? would be extremely worthwhile. But you knew that already. :-) Sean.

1 0

Re: Test Route
by Robert E. Seastrom 01 Feb '95

01 Feb '95

> From: David R Conrad <davidc(a)iij.ad.jp> > > Yeah, there are 2^32 bits of address space, after all. There are? I always thought there were 32 bits of address space, not 2^32, and the code that I wrote even worked... :) > >After all, if we all do our jobs right, maybe someday we can make > >the firewalls go away.... > > If we all do our jobs right, it won't matter if someone uses 1597 > space. Firewalls will never go away -- they're too useful. Firewalls are a kludge; they're necessitated only by the lack of strong authentication in the stack. I daresay that if the current level of threat continues to escalate (to quote a friend, "it's a bad neighborhood out there"), I foresee that the need for Joe Everyman to run a firewall will diminish or disappear, and sooner - not later. Now, I won't dispute that there will be some places where either because of legacy systems in house or paranoia they continue to run a firewall. But the 95% solution will be in place, and if they previously chose to use 1597-style addresses, the 95% of the world who decided they didn't need firewalls anymore because of strong authentication will be forced to renumber. I am more than willing to admit that 1597 has its uses, and people who find rfcs 1597 and 1627 on their own, read them, and figure out whether they want to bear the risks and consequences should feel free to use the addresses. That *doesn't* mean, however, that it should be promoted or upgraded from "informational" to "recommended", and I no longer recommend it to "casual" IP users. The concept of globally unique addressing is simply far too powerful and far too useful for us to summarily and without further thought assert that firewalls are a fact of life that will be with us forever. ---Rob

3 2

Re: Test Route
by Robert E. Seastrom 31 Jan '95

31 Jan '95

> From: bmanning(a)ISI.EDU > > Hi, > Much as I like to debate RFC 1597 and Firewalls... That is not > the topic of this thread. > > I was pointing out a useful (to me) hack to verify BGP peering > and route generation w/o the need to "expose" routes that > I might not be authoritative for. > > I would like to know if others think this was/is worthwhile? If you don't propagate the route, why does it matter? ---Rob

2 1

Test Route
by bmanning＠ISI.EDU 31 Jan '95

31 Jan '95

Hi, I have recently come across the need to test BGP peering with a number of people and have found that it is occasionally useful to establish a peer and then send a test route. There were a number of options here: 1- Use a route that I should correctly source. 2- Send the loopback address 3- Use an RFC 1597 address 4- Use the TestNetwork address Due to certain vendors/ISPs desire to (correctly) squash RFC 1597 advertisments and my inability to verify routing correctness if I propogated via third-party my internal routes, I chose to use the TestNetwork. What is the TestNetwork? zed 30% whois 192.0.2.0 [No name] (NET-TEST) Netname: AMEX Netnumber: 192.0.2.0 Coordinator: Reynolds, Joyce K. (JKR1) JKRey(a)ISI.EDU (310) 822-1511 Record last updated on 24-Oct-94. This was a number allocated prior to RFC 1597 to assist people in correctly documenting how to configure IP in their documentation. (a fix for the infamous defaults SUN had in the config scripts for so many years) It's usefullness in testing devolves from its not being included in the RFC 1597 ban on forwarding. It seems to me that we should encourage any/all NSP/ISP types to block the following networks: 127.0.0/8 10.0.0/8 172.16.0/20 192.168.0/16 --bill

4 6

Re: Test Route
by postel＠ISI.EDU 30 Jan '95

30 Jan '95

Excuse me. This seems brain dead. I think the intent of 1597 was to say here are some numbers you can go play with privately. Since they are private they should never appear on the public Internet, anywhere, ever. If any router on the public Internet sees a packet to (or from) a 1597 network it can throw it in the bit bucket and forget it. It would be possible for some private experiment to use some 1597 addresses to exchange packets over a "wire". Such a wire could be implemented by some pretty complicated arrangements with conventional public Internet service providers -- but any packets with 1597 addresses would have to be encapsulated inside packets with acceptable addresses for the public Internet to go through public Internet exchange points. --jon.

5 4

Tentative NANOG agenda
by Susan R. Harris 30 Jan '95

30 Jan '95

Here's a draft of the NANOG agenda, to give you an idea of what we're planning. --Susan R. Harris, Merit -------------------------------------------------------------------- NANOG Agenda Thursday, February 9 Time Topic Presenter(s) ---- ----- ------------ 9:00 a.m. Welcome, Introductions, Elise Gerich Future Meetings 9:15 a.m. Transition Updates: NorthWestNet Steve Corbato CERFnet Pushpendra Mohta MichNet Mark Driscoll BARRNET Vince Fuller MCInet Sean Doran SprintLink Jack Waters 10:30 a.m. Break 10:45 a.m. ATM Testbeds: Kentrox ADSU status Rolf Hahn AADS Andy Schmidt PacBell Chin Yuan/Frank Liu Bellcore/ANS Curtis Villamizar MCI/ANS testing at Hayward Abir Ahnidi 12:15 p.m. Lunch 1:30 p.m Status of AADS Contingency NAP Mark Knopper 2:00 p.m. MAE-West Update Milo Medin 2:30 p.m. Traceroute for ATM PVC Topology Taso Devetzis 3:00 p.m. Break 3:15 p.m. InterNIC Update Mark Kosters 3:45 p.m. CIDR/Aggregation/Allocation Policies Sean Doran Friday, February 10 9:00 a.m. Route Server Status Yakov Rekhter 10:00 a.m. PRDB -> RADB Transition John Scudder 10:45 a.m. Break 11:00 a.m. Testing of IDRP Implementation Sue Hares/ Craig Labovitz 11:15 a.m. Route Flap Damping Algorithm Curtis Villamizer 11:30 p.m. End-to-end Problem Resolution Eric Carroll/ John Curran 12:00 p.m. Adjourn

5 6

Re: Test Route
by John Curran 30 Jan '95

30 Jan '95

At 7:15 PM 1/30/95, Jon Postel wrote: >Excuse me. > >This seems brain dead. I think the intent of 1597 was to say here >are some numbers you can go play with privately. Since they are >private they should never appear on the public Internet, anywhere, >ever. If any router on the public Internet sees a packet to (or >from) a 1597 network it can throw it in the bit bucket and forget it. > >It would be possible for some private experiment to use some 1597 >addresses to exchange packets over a "wire". Such a wire could be >implemented by some pretty complicated arrangements with conventional >public Internet service providers -- but any packets with 1597 addresses >would have to be encapsulated inside packets with acceptable addresses >for the public Internet to go through public Internet exchange points. RFC1597 addresses are those addresses whose routes do not have to be accepted from anything outside of the "local" scope. If you consider "local" to be your site, then great. If I consider "local" to be my network infrastructure (excluding your renegade site :-) that's also fine. Just as a site's network is "private" (and hence can use RFC1597 addresses), a provider's infrastructure is also "private" for those packets which do not leave their network. /John

1 0