- NANOG - lists.nanog.org

10 Mar '92

Effective the afternoon of Sunday March 15th, the Merit/NSFNET Information Services machine (nis.nsf.net/nic.merit.edu, 35.1.1.48) will be moving to a new platform. With this move we will be changing the directory structure slightly. Of specific interest to you may be the new location of the directories currently called "nsfsites" and "nsfconfg". Following the move these directories will be found as follows: nsfsites --> nsfnet/announced.networks nsfconfg --> nsfnet/backbone.configuration In addition to these directory path/name changes, the "NETS.AS_*" files that are currently found in the "maps" directory will be found in the "nsfnet/announced.networks" directory. Sheri Repucci Merit/Internet Engineering

2 1

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

10 Mar '92

The following networks have been added to the NSFNET policy-based routing database: T1 Network: Net # Net Name Primary Secondary Location -------- ----------- ------- --------- -------- 129.38 IBMOTO 114 280 IBM AUSTIN, 11400 Burnet Rd., MS 4302, Houston, TX 77002, USA 149.155 AGRENET 274 60 Agricultural and Food Research Council, West Common, Harpenden, Herts AL5 2JE, UNITED KINGDOM 155.210 ARAGONET 274 60 Universidad de Zaragoza, Centro de Calculo, Ciudad Universitaria, 50009 Zaragoza, SPAIN 157.88 UNIDEVALL 274 60 Universidad de Valladolid, C.P.D., Prado de la Magdalena s/n, 47005 Valladolid, SPAIN 158.42 UPVNET 274 60 Politechnical Valencia University, Universidad Politecnica de Valencia, Centro de Calculo, Camino de Vera, 14, 46020 Valencia (Valencia), SPAIN 158.49 REDINEX 274 60 Universidad de Extremadura, Servicio de Informatica, Universidad de Extremadura, 06071 Badajoz, SPAIN 158.109 XIUAB 274 60 Universitat Autonoma de Barcelona, Centre de Calcul, Edifici C, E-08193 Bellaterra (Barcelona), SPAIN 192.108.131 UAKOMNET 590 Institute of Automation and Communication Net., Slovak Academy of Sciences, Severna 5; CS-97400 Banska Bystrica, CZECHOSLOVAKIA 192.112.247 CSN 274 60 Consejo De Seguridad Nuclear, Justo Dorado 11, 28040 Madrid, SPAIN 192.124.15 CONCORD-NET 1384 1383 Concord Communications, Inc., 753 Forest Street, Marlboro, MA 01752, USA 192.135.216 RFERL-NET 86 279 Radio Free Europe/Radio Liberty, Inc., RFE/RL, Incorporated, 1201 Connecticut Ave NW, Suite 1100, Washington, DC 20036, USA 192.148.201 REDIRIS1 274 60 RedIRIS, c/o FUNDESCO, Alcala, 61, 28014-Madrid, SPAIN 192.148.202 REDIRIS2 274 60 RedIRIS, c/o FUNDESCO, Alcala, 61, 28014-Madrid, SPAIN 192.148.203 REDIRIS3 274 60 RedIRIS, c/o FUNDESCO, Alcala, 61, 28014-Madrid, SPAIN 192.148.204 REDIRIS4 274 60 RedIRIS, c/o FUNDESCO, Alcala, 61, 28014-Madrid, SPAIN 192.148.205 REDIRIS5 274 60 RedIRIS, c/o FUNDESCO, Alcala, 61, 28014-Madrid, SPAIN 192.148.206 REDIRIS6 274 60 RedIRIS, c/o FUNDESCO, Alcala, 61, 28014-Madrid, SPAIN 192.148.207 REDIRIS7 274 60 RedIRIS, c/o FUNDESCO, Alcala, 61, 28014-Madrid, SPAIN 192.148.208 REDIRIS8 274 60 RedIRIS, c/o FUNDESCO, Alcala, 61, 28014-Madrid, SPAIN 192.148.209 REDIRIS9 274 60 RedIRIS, c/o FUNDESCO, Alcala, 61, 28014-Madrid, SPAIN 192.148.210 REDIRIS10 274 60 RedIRIS, c/o FUNDESCO, Alcala, 61, 28014-Madrid, SPAIN 192.148.211 REDIRIS11 274 60 RedIRIS, c/o FUNDESCO, Alcala, 61, 28014-Madrid, SPAIN 192.148.212 REDIRIS12 274 60 RedIRIS, c/o FUNDESCO, Alcala, 61, 28014-Madrid, SPAIN 192.148.213 REDIRIS13 274 60 RedIRIS, c/o FUNDESCO, Alcala, 61, 28014-Madrid, SPAIN 192.148.214 REDIRIS14 274 60 RedIRIS, c/o FUNDESCO, Alcala, 61, 28014-Madrid, SPAIN 192.148.215 REDIRIS15 274 60 RedIRIS, c/o FUNDESCO, Alcala, 61, 28014-Madrid, SPAIN 192.150.1 ADOBE-01 701 702 Adobe Systems Inc., 1585 Charleston Road, Mountain View, CA 94039, USA 192.184.4 BULLMINNNET 1384 1383 Bull HN Information Systems, Technology Park, Billerica, MA 01821-4119, USA Total NSFNET T1 announced networks: 4835 T3 Network: 89 T1 configured Nasa Science Network (AS 297) networks (not listed here) have been added to the T3 database. These will not be installed on the T3 backbone until later in the week. Network IP: 129.38 Network Name: IBMOTO Location: IBM AUSTIN, 11400 Burnet Rd., MS 4302, Houston, TX 77002 USA Country Code: US 1:114 SESQUINET Regional Network 2:280 SESQUINET Regional Network Network IP: 192.77.157 Network Name: PACBELL-SMDS Location: PAC Bell, Pacific Bell, 2600 Camino Ramon, San Ramon, CA 94583 USA Country Code: US 1:1321 ANS San Francisco - DNSS 11 Network IP: 192.124.15 Network Name: CONCORD-NET Location: Concord Communications, Inc., 753 Forest Street, Marlboro, MA 01752, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network Network IP: 192.135.216 Network Name: RFERL-NET Location: Radio Free Europe/Radio Liberty, Inc., RFE/RL, Incorporated, 1201 Connecticut Ave NW, Suite 1100, Washington, DC 20036, USA Country Code: US 1:86 SURANET Regional Network 2:279 Georgia Tech Network IP: 192.150.1 Network Name: ADOBE-01 Location: Adobe Systems Inc., 1585 Charleston Road, Mountain View, CA 94039 USA Country Code: US 42:702 Alternet Router 43:701 Alternet Router Network IP: 192.184.4 Network Name: BULLMINNNET Location: Bull HN Information Systems, Technology Park, Billerica, MA 01821-4119 USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network Total NSFNET T3 announced networks: 2501 T3 Special Additions: AS Number: 297 AS Notes: Nasa Science Network (FIX-East) AS Country Code: US ANS: No BkBn: 690 NSS: 140.222.145 - FIX-East College Park, MD Gate: 192.80.214.253 - umd.nsn.nasa.gov Nasa Science Network (FIX-East) The configuration reports, map information sheets, and configuration files which reflect these changes are available for anonymous ftp on nis.nsf.net as usual. nsfsites - configuration reports latest report for: - NSFNET T1 has the file extension .now - NSFNET T3 has the file extension 3.now nsfconfg - configuration files for the routing software for each NSS latest report for: - NSFNET T1 has the file format config.nss# - NSFNET T3 has the file extension .t3p Please send all requests for configuration changes to nsfnet-admin(a)merit.edu using the NSFNET configuration forms. The forms are available on-line from the nis.nsf.net machine. Use ftp and the anonymous login to get on the machine. Do a "cd nsfsites" and grab the files TEMPLATE.NET, TEMPLATE.GATE, and TEMPLATE.AS. --Steve Widmayer Merit/NSFNET

1 0

Re: Normal config window?
by Steven K. Widmayer 10 Mar '92

10 Mar '92

>What are the hours of the config window on Tues and Fri mornings? >Do you have a rough idea of the typical outage duration (i.e. do you upgrade >the boxes serially so a 5 minute restart occurs on each node one after the >other or do you hit the big red button and they all go at once or what?). Do >you usually start right at the beginning of the window or if nothing tricky is >going on do you wait till near the end? > >Thanks, >Dan Dan, I'm glad you asked. The current routing config install windows are from 05:00 - 08:00 EST on Tue and Fri mornings. Starting this week, we will be adding an additional window on Thur morning from 05:00 - 08:00 EST. We need the additional window for the next couple of months in order to complete the remaining T3 AS cutovers. We need to send one of two signals to the routing daemon in order to install the new configuration file: kill -USR1 or kill -USR2. A kill -USR1 just re-reads the new configuration file into the rcp_routed. A kill -USR2 is a little more severe and actually briefly stops and restarts the rcp_routed. This results in a brief period of down EGP/BGP sessions and loss of connectivity, and it usually takes about 5 minutes for all backbone routing to re-converge. These kills get done on the RCPs on the T1 backbone, and on the CNSS, DNSS, or ENSS boxes on the T3 backbone. The severity of the kill and whether a kill needs to be done at all depends on the type of change/addition made in the new configuration file for that node. Most sites running EGP will only need a kill -USR1, while most sites using BGP need a kill -USR2, or an equivalent (stopping and restarting the BGP session), to install the new changes. Adding or deleting a peer always takes a kill -USR2 to the node. Adding a new ENSS to the T3 backbone requires that a kill -USR2 be done on each backbone node to enable the new IBGP sessions. A few exceptions: On the T3 backbone, ENSS 134 (Boston) and ENSS 135 (San Diego) have explicitly configured outbound announcements in order to give them the T1 backbone route (129.140) without also sending them all the other routes coming in from the T1 backbone via the interconnects. Installing any new T3 routes always requires a kill -USR2 on E134 and E135 (usually each config day). The active T1/T3 interconnects in Ann Arbor and Houston also almost always need a kill -USR2 or the equivalent with each configuration update. The kills usually take place in a serial fashion but can begin at varying times during the window, depending on the workload, special problems, and when we or the NOC can schedule the time to do the kills. Each window is usually quite unique, except that the interconnects are usually done last. Sometimes we piggy-back the routing configuration installs on top of some other backbone-wide software update that gets scheduled on the same night, to minimize down time. Sometimes all the kills can be accomplished in 15-20 minutes, while other times we literally need the entire window, because we wait for routing to readjust on one node before disrupting routing on the next node. If we are doing kill -USR2s on the entire T3 backbone, we'll usually do all boxes at each POP at the same time. --Steve Widmayer Merit/NSFNET

1 0

CERFnet Weekly Report for the week of Monday, March 2, 1992.
by Donna Bigley 09 Mar '92

09 Mar '92

############################################################################### This is the CERFnet weekly activity report for the period of Monday, March 2nd through Sunday, March 8th, 1992. This report is also available through anonymous FTP from NIC.CERF.NET [192.102.249.3] in the cerfnet/cerfnet_stats subdirectory. The filename is: 08-march-92.txt All times are in Pacific Standard Time, and in the 24-hour format. Please direct any questions or comments to: donnab(a)cerf.net or help(a)cerf.net ****************************************************************************** NETWORK OUTAGES: TICKET #: 805 SITE: DATAPRODUCTS SITES AFFECTED: DATAPRODUCTS TIME STARTED: FRI. 2-28-92 12:16 TIME ENDED: MON. 3-9-92 09:40 TIME ELAPSED: 9 days 21 hours 24 min. (Intermittent Access) REASON: Link Failure TICKET #: 809 SITE: QUALCOMM SITES AFFECTED: QUALCOMM TIME STARTED: MON. 3-2-92 15:57 TIME ENDED: MON. 3-2-92 16:23 TIME ELAPSED: 26 min. REASON: Equipment Trouble TICKET #: 785 SITE: SERI/KOREA SITES AFFECTED: SERI/KOREA TIME STARTED: TUE. 3-3-92 00:49 TIME ENDED: TUE. 3-3-92 20:44 TIME ELAPSED: 19 hours 55 min. REASON: Link Failure TICKET #: 817 SITE: INTEL SITES AFFECTED: INTEL TIME STARTED: WED. 3-4-92 06:10 TIME ENDED: THU. 3-5-92 13:09 TIME ELAPSED: 30 hours 59 min. REASON: Link Failure TICKET #: 818 SITE: UCR SITES AFFECTED: UCR TIME STARTED: WED. 3-4-92 19:04 TIME ENDED: THU. 3-5-92 08:31 TIME ELAPSED: 13 hours 27 min. REASON: Power Outage (Affecting the San Diego T1 repeaters) TICKET #: 827 SITE: QUALCOMM SITES AFFECTED: QUALCOMM TIME STARTED: WED. 3-4-92 20:09 TIME ENDED: WED. 3-4-92 20:11 TIME ELAPSED: 2 min. REASON: Unscheduled Site Maintenance TICKET #: 785 SITE: SERI/KOREA SITES AFFECTED: SERI/KOREA TIME STARTED: THU. 3-5-92 06:43 TIME ENDED: THU. 3-5-92 17:01 TIME ELAPSED: 10 hours 18 min. REASON: Link Failure TICKET #: 828 SITE: UNOCAL SITES AFFECTED: UNOCAL TIME STARTED: THU. 3-5-92 22:03 TIME ENDED: THU. 3-5-92 22:17 TIME ELAPSED: 14 min. REASON: Unscheduled Site Maintenance TICKET #: 824 SITE: CIX-WEST SITES AFFECTED: CIX-WEST TIME STARTED: FRI. 3-6-92 05:55 TIME ENDED: FRI. 3-6-92 06:44 TIME ELAPSED: 49 min. REASON: Site Scheduled Maintenance TICKET #: 785 SITE: SERI/KOREA SITES AFFECTED: SERI/KOREA TIME STARTED: FRI. 3-6-92 06:24 TIME ENDED: FRI. 3-6-92 19:02 TIME ELAPSED: 12 hours 38 min. REASON: Link Failure TICKET #: 825 SITE: OXY SITES AFFECTED: OXY TIME STARTED: FRI. 3-6-92 07:46 TIME ENDED: FRI. 3-6-92 08:47 TIME ELAPSED: 1 hour 1 min. REASON: Unscheduled Outage TICKET #: 785 SITE: SERI/KOREA SITES AFFECTED: SERI/KOREA TIME STARTED: SAT. 3-7-92 00:42 TIME ENDED: SAT. 3-7-92 04:45 TIME ELAPSED: 4 hours 3 min. REASON: Link Failure TICKET #: 785 SITE: SERI/KOREA SITES AFFECTED: SERI/KOREA TIME STARTED: SUN. 3-8-92 03:26 TIME ENDED: SUN. 3-8-92 20:17 TIME ELAPSED: 16 hours 51 min. REASON: Link Failure TICKET #: 831 SITE: CADAM SITES AFFECTED: CADAM TIME STARTED: SUN. 3-8-92 10:25 TIME ENDED: SUN. 3-8-92 13:36 TIME ELAPSED: 3 hours 11 min. REASON: Unknown ------------------------------------------------------------------------ CERFNET TRAFFIC CAPACITY USAGE AT EACH CIRCUIT LINK LINK SPEED CAPACITY PEAK HOUR (PDT) SDSC/CALTECH 1.544 mbps 08.7% 11:00 SDSC/UCI 1.544 mbps 07.9% 13:00 SDSC/UCLA 1.544 mbps 06.4% 20:00 SDSC/UCOP 1.544 mbps 03.1% 12:00 UCI/UCLA 1.544 mbps 00.5% 16:00 SDSC/UCR 512 kbps 04.6% 17:00 UCLA/UCSB 512 kbps 05.9% 09:00 SDSC/AGI 1.544 mbps 00.1% 20:00 SDSC/BIOSYM 1.544 kbps 00.1% 13:00 SDSC/GA 1.544 mbps 00.2% 13:00 SDSC/GD 1.544 mbps No Capacities available for this week. SDSC/SAIC 1.544 mbps 01.2% 13:00 SDSC/SCAQMD 1.544 mbps 00.02% 10:00 SDSC/SDSU 1.544 mbps 01.2% 13:00 UCI/CSU CO(SWRL) 1.544 mbps 02.0% 15:00 UCOP/APPLE 1.544 mbps 00.9% 09:00 UCOP/CISCO 1.544 mbps 00.1% 15:00 UCR/LLUMC 1.544 mbps 00.2% 15:00 CALTECH/CADAM 56 kbps 00.5% 09:00 CALTECH/CLAREMONT 56 kbps 25.9% 11:00 CALTECH/DISNEY 56 kbps 04.0% 14:00 CALTECH/OXY 56 kbps 08.2% 21:00 SDSC/AJS 56 kbps 01.9% 13:00 SDSC/KOREA 56 kbps 07.1% 23:00 SDSC/QUALCOMM 56 kbps 17.1% 13:00 SDSC/SCIH 56 kbps 03.9% 11:00 SDSC/USD 56 kbps 06.6% 13:00 SDSC/USIU 56 kbps 00.8% 13:00 SDSC/XEROX 56 kbps 01.5% 16:00 UCI/CMD 56 kbps 05.6% 20:00 UCI/EMULEX 56 kbps 01.1% 14:00 UCI/FULLERTON 56 kbps 01.5% 11:00 UCI/HUGHES 56 kbps 13.3% 15:00 UCI/MTI 56 kbps 02.9% 11:00 UCI/SPARTA 56 kbps 06.9% 01:00 UCI/UNOCAL 56 kbps 07.3% 11:00 UCLA/ISX 56 kbps 01.3% 11:00 UCLA/PEPPERDINE 56 kbps 01.6% 12:00 UCLA/QUOTRON 56 kbps 06.0% 05:00 UCLA/SMC 56 kbps 01.1% 13:00 UCOP/FARALLON 56 kbps 04.4% 11:00 UCOP/INTEL 56 kbps 12.9% 14:00 UCOP/LSIL 56 kbps 07.6% 22:00 UCOP/NETLABS 56 kbps 11.6% 20:00 ------------------------------------------------------------------------------ SITE CISCO BOX UPTIME SINCE LAST REBOOT (as of 00:15 PST on Mar.9, 1992): CERFnet BACKBONE CALTECH [131.215.139.253] Up: 18 days 15 hours 51 minutes SDSC LongBoard [134.24.99.254] Up: 07 days 09 hours 33 minutes SDSC Drzog [132.249.16.13] Up: 08 days 05 hours 35 minutes SDSC Hang10 [132.249.16.15] Up: 08 days 05 hours 16 minutes UCI [128.200.1.101] Up: 59 days 16 hours 07 minutes UCLA [128.97.130.10] Up: 30 days 13 hours 42 minutes UCOP [134.24.52.112] Up: 13 days 17 hours 48 minutes UCR [134.24.108.105] Up: 114 days 12 hours 36 minutes CERF 1544 AGI [134.24.202.110] Up: 24 days 13 hours 54 minutes APPLE [134.24.70.200] Up: 133 days 06 hours 15 minutes BIOSYM [134.24.57.200] Up: 35 days 06 hours 48 minutes CISCO Systems [134.24.54.200] Up: 96 days 14 hours 09 minutes CSUCO/SWRL [130.150.102.200] Up: 12 days 04 hours 51 minutes GA [134.24.221.200] Up: 15 days 04 hours 41 minutes GD [134.24.60.200] Up: 07 days 13 hours 31 minutes LLUMC [134.24.208.200] Up: 110 days 12 hours 22 minutes SAIC [134.24.53.208] Up: 64 days 08 hours 34 minutes SCAQMD [134.24.234.200] Up: 80 days 14 hours 27 minutes SDSU [192.77.100.101] Up: 90 days 16 hours 31 minutes UCSB [134.24.107.107] Up: 110 days 07 hours 38 minutes CERF 56 AJS [134.24.225.101] Up: 51 days 14 hours 17 minutes CADAM [134.24.229.200] Up: 33 days 13 hours 01 minutes CLAREMONT [134.24.206.109] Up: 24 days 14 hours 02 minutes CMD [134.24.218.200] Up: 41 days 13 hours 14 minutes DATAPRODUCTS [134.24.211.104] Up: 11 days 15 hours 01 minutes DISNEY [134.24.207.211] Up: 39 days 00 hours 33 minutes EMULEX [134.24.209.212] Up: 85 days 15 hours 48 minutes FARALLON [134.24.56.200] Up: 10 days 17 hours 19 minutes FULLERTON [134.24.214.217] Up: 83 days 15 hours 33 minutes HUGHES [134.24.204.200] Up: 115 days 07 hours 21 minutes INTEL [134.24.55.200] Up: 71 days 03 hours 19 minutes LSIL [134.24.72.200] Up: 29 days 13 hours 08 minutes MTI [134.24.216.100] Up: 65 days 13 hours 39 minutes NETLABS [134.24.71.200] Up: 93 days 15 hours 07 minutes OXY [134.24.205.108] Up: 02 days 15 hours 26 minutes [Unscheduled Outage - Ticket #825] PEPPERDINE [134.24.203.218] Up: 15 days 13 hours 14 minutes QUALCOMM [134.24.200.201] Up: 03 days 07 hours 29 minutes [Unscheduled Site Maintenance - Ticket #827] QUOTRON [134.24.230.202] Up: 105 days 13 hours 44 minutes SANTA MONICA [134.24.210.219] Up: 59 days 01 hours 22 minutes SCI-HOR [134.24.109.205] Up: 00 days 11 hours 36 minutes [Power Outage] SERI/KOREA [134.24.223.200] Up: 01 days 23 hours 53 minutes [Link Failure - Ticket #785] SPARTA [134.24.215.200] Up: 24 days 19 hours 09 minutes UNOCAL [134.24.217.200] Up: 03 days 01 hours 57 minutes [Unscheduled Site Maintenance - Ticket #828] USD [134.24.201.106] Up: 39 days 15 hours 45 minutes USIU [134.24.222.215] Up: 246 days 17 hours 07 minutes XEROX [134.24.51.207] Up: 130 days 23 hours 22 minutes DIAL n' CERF DNC-SDSC [134.24.1.2] Up: 01 days 22 hours 36 minutes [Site Activity] DNC-UCI [134.24.2.2] Up: 61 days 03 hours 24 minutes DNC-UCLA [134.24.3.2] Up: 46 days 12 hours 38 minutes DNC-CALTECH [134.24.4.2] Up: 05 days 02 hours 37 minutes [Software Upgrade] DNC-UCOP [134.24.5.2] Up: 29 days 08 hours 58 minutes

1 0

BGP Deployment Group Meeting
by Jessica Yu 09 Mar '92

09 Mar '92

Hi, The BGP Deployment Group Meeting is scheduled at 7-10 pm Tue Mar. 17 at this comming IETF meeting at San Diego. One of the topics will be discussed in this session is the mechanism for each domain to describe its routing policy and share them. As you know, sharing routing policy information is a means in helping avoiding domains set contradictary routing policies which leads packets go nowhere. It is importand for the enviroment which use routing protocols supports policy routing. Developing the sharing mechanism is one of the goal of this group. As a start, in our meeting at this ietf, we are going to develope a routing policy description form which hopefully will include all the policy descriptions we think is necessary to share. The policy description language in this form will be plain English initially but will be evolving to a common description language understood by machine. we will also discuss the mechansim of gathering and destribution of the form. I came up with a draft form which include some suggests from Yakov (thanks Yakov). I am including this draft form below. Please read it before our meeting and bring your comments and suggestions. Thanks! By the way, I will post an agenda shortly. --Jessica Routing Policy Description Form (Draft) ------------------------------- A. General Description of your domain a. List your Domain and the AS number(s) b. List the Routing administrator of the Domain Name: Organization: e-mail: phone number: c. List the networks that belong to your domain and mark them with RE or non-RE type if applicable. d. List your direct neighbor domain(s) and its AS number(s) e. List each IP address of your border router(s) which interface with your neighbor border router(s) and the Exterior Routing Protocol(s) used respectivly. f. Are your domain a Stub domain? Multi-homed Stub domain? Transit domain? Pure Transit domain? g. List the IGP used within your domain (optional for a non-transit domain) h. Describe the average bandwidth of your domain (optional for a non-transit domain) i. Describe the delay characteristic of average physical links, e.g. satellite, terriestrial, of your domain (optional for a non-transit domain) B. Policy Descriptions If you are a stub domain: o Outbound advertisement filtering: list the set of nets belong to your domain that you do not advertise to your neighbor. o Inbound acceptance filtering: list the set of ASs whose nets you do or (do not) accept from your neighbor(s) If AS number is not a satisfactory granularity, list the set of nets. o Describe your routing policy based on your AUP (e.g. RE vs non-RE traffic, etc.) o Does your border router default to your neighbor border router? If you are a multi-homed stub domain: o Outbound advertisement filtering: list the nets belong to your domain that you do not advertise to your neighbors. o Inbound acceptance filtering: list the set of ASs whose nets you do or (do not) accept from your neighbor(s) If AS number is not a satisfactory granularity, list the set of nets. o List the prefrence/denial of the neighbor ASs which can route your traffic to the same destination. o Describe your routing policy based on your AUP (e.g. RE vs non-RE traffic, etc.) o Do you point default to your neighbor(s)? If yes, describe the mechanism. If you are a transit domain: o Outbound advertisement filtering: list the nets belong to you (not a pure transit domain) that you do not advertise advertise to your direct neighbors o Inbound acceptance filtering: list the set of ASs whose nets you do or (do not) accept from your neighbor(s) If AS number is not a satisfactory granularity, list the set of nets. o List the paris of source/destination ASs or nets that your domain does not provide transitivity with. o List the prefrence/denial of the ASs which can route your traffic to a certain destination. o Describe your routing policy based on your AUP (e.g. RE vs non-RE traffic, etc.) o Do you point default to your neighbor(s)? If yes, describe the mechanism.

1 0

Additions to the NSFNET policy-based routing database
by Belinda Sue Blair 06 Mar '92

06 Mar '92

The following networks have been added to the NSFNET policy-based routing database: T1 Network: Net # Net Name Primary Secondary Location -------- ----------- ------- --------- -------- 192.147.28 ITM 701 702 International TeleManagement, 1600 Spring Hill Road, Suite 400, Vienna, VA 22182, USA 151.120 ROCHE1 97 Hoffman-La Roche, 340 Kingsland St., Nutley, NJ 07110-1199, USA 144.81 ETS 97 Educational Testing Service, Rosedale Road, Mail Drop 34D, Princeton, NJ 08541, USA 131.224 RIVMNET 701 1238 National Institute of Public Health and Environmental Protection, Computer Center, P.O. Box 1, 3720 BA Bilthoven, NETHERLANDS 157.201 RICKS 210 209 Ricks College, Computer Center, Rexburg, ID 83460-4176, USA 156.14 CIRANET 590 C.I.R.A. Italian Research Aerospace Center, Via Maiorise, 81043 Capua (CE), ITALY 192.44.38 FHG-NET38 750 756 Fraunhofer Institut fuer Informations und Datenverarbeitung IITB, Fraunhofer-Strasse 1, D-7500 Karlsruhe 1, GERMANY 192.44.37 FHG-NET37 750 756 Fraunhofer Institut fuer Informations und Datenverarbeitung IITB, Fraunhofer-Strasse 1, D-7500 Karlsruhe 1,GERMANY 153.94 TRANSTEC 750 756 Transtec GmbH, Waldhoernlestrasse 18, D-7400 Tuebingen, GERMANY 140.202 PANAMA-NET1 184 164 1109th Signal Brigrade, Commander, 1109th Signal Battalion, Attn: ASQNP-BA-T, APO Miami, FL 34004-5000, USA 192.138.87 NRL-MONTEREY 200 754 Naval Research Laboratory (NRL), Code 400, Monterey, CA 93943-5006, USA 192.138.71 AMEDD-BRAGG 184 164 Womack Army Comm. Hosp., Ft. Bragg, NC 28307-5001, USA 192.138.58 AMEDD-KNOX 184 164 Ireland ARMY Comm Hosp., Cdr, USAMEDDAC, Attn. HSXM-IMD, Ft. Knox, KY 40121, USA 192.138.51 AMEDD-ORD 164 184 Hays Army Comm. Hosp., Ft. Ord, CA 93941-5800, USA 192.138.37 AMEDD-SF 164 184 Letterman Army Med. Cen., Presidio of San Francisco, CA 94129, USA 192.129.36 XLINK-ISDN 750 756 XLINK-Project, Uni Karlsruhe, GERMANY 192.102.177 FHG-IPK-177-NET 750 756 Fraunhofer Gesellschaft Deutschland, Fraunhofer Institut fuer Informations und Datenverarbeitung IITB, Fraunhofer-Strasse 1, D-7500 Karlsruhe 1, GERMANY 192.102.176 FHG-IPK-176-NET 750 756 Fraunhofer Gesellschaft Deutschland, Fraunhofer Institut fuer Informations und Datenverarbeitung IITB, Fraunhofer-Strasse 1, D-7500 Karlsruhe 1, GERMANY 192.147.249 PTLOMA 1740 754 Point Loma Nazarene College, 3900 Lomaland Drive, San Diego, CA 92106, USA Total NSFNET T1 announced networks: 4808 T3 Network: Network IP: 153.94 Network Name: TRANSTEC Location: Transtec GmbH, Waldhoernlestrasse 18, D-7400 Tuebingen, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 192.44.37 Network Name: FHG-NET37 Location: Fraunhofer Institut fuer Informations und Datenverarbeitung IITB, Fraunhofer-Strasse 1, D-7500 Karlsruhe, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 192.44.38 Network Name: FHG-NET38 Location: Fraunhofer Institut fuer Informations und Datenverarbeitung IITB, Fraunhofer-Strasse 1, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 192.102.176 Network Name: FHG-IPK-176-NET Location: Fraunhofer Gesellschaft Deutschland, Fraunhofer Institut fuer Informations und Datenverarbeitung IITB, Fraunhofer-Strasse 1, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 192.102.177 Network Name: FHG-IPK-177-NET Location: Fraunhofer Gesellschaft Deutschland, Fraunhofer Institut fuer Informations und Datenverarbeitung IITB, Fraunhofer-Strasse 1, D-7500 Karlsruhe 1, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 192.129.36 Network Name: XLINK-ISDN Location: XLINK-Project, Uni Karlsruhe, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 192.138.87 Network Name: NRL-MONTEREY Location: Naval Research Laboratory (NRL), Code 400, Monterey, CA 93943-5006, USA Country Code: US 1:200 BARRNet Network IP: 192.147.28 Network Name: ITM Location: International TeleManagement, 1600 Spring Hill Road, Suite 400, Vienna, VA 22182, USA Country Code: US 42:702 Alternet Router 43:701 Alternet Router Network IP: 192.147.249 Network Name: PTLOMA Location: Point Loma Nazarene College, 3900 Lomaland Drive, San Diego, CA 92106, USA Country Code: US 1:1740 CERFnet Total NSFNET T3 announced networks: 2407 The configuration reports, map information sheets, and configuration files which reflect these changes are available for anonymous ftp on nis.nsf.net as usual. nsfsites - configuration reports latest report for: - NSFNET T1 has the file extension .now - NSFNET T3 has the file extension 3.now nsfconfg - configuration files for the routing software for each NSS latest report for: - NSFNET T1 has the file format config.nss# - NSFNET T3 has the file extension .t3p Please send all requests for configuration changes to nsfnet-admin(a)merit.edu using the NSFNET configuration forms. The forms are available on-line from the nis.nsf.net machine. Use ftp and the anonymous login to get on the machine. Do a "cd nsfsites" and grab the files TEMPLATE.NET, TEMPLATE.GATE, and TEMPLATE.AS. ************** -B. Sue Blair Merit Network Operations

1 0

SURA Fix-East Scheduled outage
by Youthana Sivali 06 Mar '92

06 Mar '92

03/05/92 The FIX-East - The sites on sura's Federal Internet Exchange 23:00-23:15 will be unreachable tonight (3/5) for a period of approximately 15 minutes for maintainance to facilitate the installation of the new ENSS-145. The following site will be unreachable via suranet for the 15 minute anticipated outage. NASA - Nasa Goddard Space Flight Center TWB- The Terrestrial Wide Band Gateway ESNET - Lawrence Livermore National Laboratory Mitre - The Mitre/Milnet Mailbridge Apologies for the short notice, Youthana Sivali SURAnet Operations

1 0

CERT Advisory - AIX REXD Daemon Vulnerability
by CERT Advisory 05 Mar '92

05 Mar '92

=========================================================================== CA-92:05 CERT Advisory March 5, 1992 AIX REXD Daemon Vulnerability --------------------------------------------------------------------------- The Computer Emergency Response Team/Coordination Center (CERT/CC) has received information concerning a vulnerability with the rexd daemon in versions 3.1 and 3.2 of AIX for IBM RS/6000 machines. IBM is aware of the problem and it will be fixed in future updates to AIX 3.1 and 3.2. Sites may call IBM Support (800-237-5511) and ask for the patch for apar ix21353. Patches may be obtained outside the U.S. by contacting your local IBM representative. The fix is also provided below. --------------------------------------------------------------------------- I. Description In certain configurations, particularly if NFS is installed, the rexd (RPC remote program execution) daemon is enabled. Note: Installing NFS with the current versions of "mknfs" will re-enable rexd even if it was previously disabled. II. Impact If a system allows rexd connections, anyone on the Internet can gain access to the system as a user other than root. III. Solution CERT/CC and IBM recommend that sites take the following actions immediately. These steps should also be taken whenever "mknfs" is run. 1. Be sure the rexd line in /etc/inetd.conf is commented out by having a '#' at the beginning of the line: #rexd sunrpc_tcp tcp wait root /usr/etc/rpc.rexd rexd 100017 1 2. Refresh inetd by running the following command as root: refresh -s inetd --------------------------------------------------------------------------- The CERT/CC wishes to thank Darren Reed of the Australian National University for bringing this vulnerability to our attention and IBM for their response to the problem. --------------------------------------------------------------------------- If you believe that your system has been compromised, contact CERT/CC or your representative in FIRST (Forum of Incident Response and Security Teams). Internet E-mail: cert(a)cert.sei.cmu.edu Telephone: 412-268-7090 (24-hour hotline) CERT/CC personnel answer 7:30 a.m.-6:00 p.m. EST(GMT-5)/EDT(GMT-4), on call for emergencies during other hours. Computer Emergency Response Team/Coordination Center (CERT/CC) Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213-3890 Past advisories, information about FIRST representatives, and other information related to computer security are available for anonymous ftp from cert.sei.cmu.edu (192.88.209.5).

1 0

I am leaving SURAnet
by oleary＠sura.net 05 Mar '92

05 Mar '92

March 20th will be my last day working at SURAnet. During April and May I will be traveling around the country, visiting schools and looking for a place to live, work, and take classes. Please direct any technical inquiries regarding SURAnet to "noc(a)sura.net" rather than to me directly as my access to electronic mail will be intermittent at best. Working with each of you has been quite enjoyable, and I certainly hope to keep in touch with all of you in the future. It is safe to assume that the next place I will be working is on the Internet.... :-) Thanks, dave o'leary SURAnet Network Operations Mgr.

1 0

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

03 Mar '92

The following networks have been added to the NSFNET policy-based routing database: T1 Network: Net # Net Name Primary Secondary Location -------- ----------- ------- --------- -------- 40 LILLY-NET 750 756 Eli Lilly and Company, Lilly Corporate Center, Mail Stop 2257, Indianapolis, IN 46285 138.12 MEADDATA 750 756 Mead Data Central, 9333 Springboro Pike, Miamisburg, OH 45342 141.173 CYANAMID 97 American Cyanamid, P.O.Box 817, Hannibal, MO 63401 143.131 DOWJONES 97 Dow Jones, Route 1 and Ridge Road, Princeton, NJ 08543 147.2 USL 97 UNIX Systems Laboratories, 190 River Road, Summit, NJ 07901 192.35.156 QUALNET2 1740 754 Qualcomm, Inc., 10555 Sorrento Valley Road, San Diego, CA 92121 192.70.74 FNET-ENSFCL 1238 Ecole Normale Superieure de Fontenay/Saint-Cloud, 31 rue Lombart, 92266 Fontenay-aux-Roses, FRANCE 192.109.57 SIEERL-LAN 701 1238 SIEMENS AG, ANL A434-SD, Guenther-Scharowski-Str . 2, D-W-8520 Erlangen, GERMANY 192.109.81 MAINZ-IBM-DE 701 1238 IBM Deutschland, Geb. 6500-67 / Kst. 7977, Hechtsheimer Str. 2, 6500 Mainz, GERMANY 192.122.251 MARKV-NET 1740 754 Mark V Systems Limited, 16400 Ventura Boulevard, Suite 303, Encino, CA 91436 192.132.89 NMHU-NET 771 372 New Mexico Highlands University, New Mexico Highlands University, Computer Center, Las Vegas, NM 87701 192.138.205 FALCON2 233 177 G-4195 W. Pasadena Ave., Genessee District Library, Michigan 192.148.93 PNL-ARM 291 293 Pacific Northwest Laboratory, Battelle Pacific Northwest Laboratory, P.O. Box 999 MSIN K1-88, Richland, WA 99352 192.149.1 ANSOFT 1206 204 Ansoft Corporation, 4 Station Square, Suite 660, Pittsburgh, PA 15219 192.149.13 NETALBRIGHT 1206 204 Albright College, Union and Linden Streets, Reading, PA 19604 Total NSFNET T1 announced networks: 4789 T3 Network: Network IP: 40 Network Name: LILLY-NET Location: Eli Lilly and Company, Lilly Corporate Center, Mail Stop 2257, Indianapolis, IN 46285 Country Code: US 1:17 ENSS 152 Purdue - AS Network IP: 138.12 Network Name: MEADDATA Location: Mead Data Central, 9333 Springboro Pike, Miamisburg, OH 45342 Country Code: US 1:1325 ANS Cleveland - DNSS 43 Network IP: 140.214 Network Name: MP-RECNET Location: U.S. Bureau of Reclamation, 2800 Cottage Way, Sacramento, CA, 95825 Country Code: US 1:201 BARRNet Network IP: 192.35.156 Network Name: QUALNET2 Location: Qualcomm, Inc., 10555 Sorrento Valley Road, San Diego, CA 92121 Country Code: US 1:1740 CERFnet Network IP: 192.122.251 Network Name: MARKV-NET Location: Mark V Systems Limited, 16400 Ventura Boulevard, Suite 303, Encino, CA 91436 Country Code: US 1:1740 CERFnet Network IP: 192.138.205 Network Name: FALCON2 Location: G-4195 W. Pasadena Ave., Genessee District Library, Michigan Country Code: US 1:237 MERIT network Network IP: 192.149.1 Network Name: ANSOFT Location: Ansoft Corporation, 4 Station Square, Suite 660, Pittsburgh, PA 15219 Country Code: US 1:1206 PSCNET Network IP: 192.149.13 Network Name: NETALBRIGHT Location: Albright College, Union and Linden Streets, Reading, PA 19604 Country Code: US 1:1206 PSCNET Total NSFNET T3 announced networks: 2398 T3 Special Additions: AS Number: 195 AS Notes: SDSC Regional network AS Country Code: US ANS: No Gate: 132.249.32.33 - rosebud.sdsc.edu ENSS 135 - San Diego AS Number: 685 AS Notes: AS 685 - ENSS 143 / University of Washington AS Country Code: US ANS: No Gate: 192.35.180.9 - seattle3-gw.nwnet.net ENSS 143 - University of Washington The configuration reports, map information sheets, and configuration files which reflect these changes are available for anonymous ftp on nis.nsf.net as usual. nsfsites - configuration reports latest report for: - NSFNET T1 has the file extension .now - NSFNET T3 has the file extension 3.now nsfconfg - configuration files for the routing software for each NSS latest report for: - NSFNET T1 has the file format config.nss# - NSFNET T3 has the file extension .t3p Please send all requests for configuration changes to nsfnet-admin(a)merit.edu using the NSFNET configuration forms. The forms are available on-line from the nis.nsf.net machine. Use ftp and the anonymous login to get on the machine. Do a "cd nsfsites" and grab the files TEMPLATE.NET, TEMPLATE.GATE, and TEMPLATE.AS. --Steve Widmayer Merit/NSFNET

1 0