- Test - lists.nanog.org

Change in NACR process (fwd)
by Ed Cho 15 Dec '94

15 Dec '94

Steve, Good luck. Thanks for all your help. Edward Cho ---------- Forwarded message ---------- Date: Thu, 15 Dec 1994 16:11:25 -0500 From: Elise Gerich <epg(a)merit.edu> To: regional-techs(a)merit.edu Cc: epg(a)merit.edu Subject: Change in NACR process Merit has been fortunate to have the same person handling our routing configurations for the last 5 or so years, Steve Widmayer. He has sheparded us all through the hugh growth of routing announcments and he understood the system better than anyone. to our great dismay, Steve has decided to move on, and we will miss him greatly. Since Steve's last day was Tuesday, December 13, we are now depending on Steve Richardson to help us train a new person (yet to be hired) to handle the NACRs and to help with the configuration process. Until the new person comes on board and is fully trained, we will have to move the cutoff for accepting NACRS to 09:00 EST on the day preceeding the configuration run. Please join us in wishing Steve Widmayer well in his future endeavors, and please have patience with us as we try to fill his shoes (not an easy task). --Elise

1 0

Merit has moved
by Elise Gerich 15 Dec '94

15 Dec '94

As of today, Merit has moved to: 4251 Plymouth Road Ann Arbor, MI 48105-2785 Our main phone numbers have changed to: telephone: 313-764-9430 FAX: 313-747-3185 You are welcome to come visit our new offices anytime. --Elise

1 0

Change in NACR process
by Elise Gerich 15 Dec '94

15 Dec '94

Merit has been fortunate to have the same person handling our routing configurations for the last 5 or so years, Steve Widmayer. He has sheparded us all through the hugh growth of routing announcments and he understood the system better than anyone. to our great dismay, Steve has decided to move on, and we will miss him greatly. Since Steve's last day was Tuesday, December 13, we are now depending on Steve Richardson to help us train a new person (yet to be hired) to handle the NACRs and to help with the configuration process. Until the new person comes on board and is fully trained, we will have to move the cutoff for accepting NACRS to 09:00 EST on the day preceeding the configuration run. Please join us in wishing Steve Widmayer well in his future endeavors, and please have patience with us as we try to fill his shoes (not an easy task). --Elise

1 0

Re: February Meeting
by Guy Almes 15 Dec '94

15 Dec '94

Bill, I agree that we would not be able to co-opt the ISoc meeting to be specifically North America focused. I also agree, of course, that NANOG, EOF, and the IEPG are distinct groups with distinct charters. I do not advocate any merger. But I *do* believe that it would be in the best interests of NANOG (and IEPG) for us to take advantage of this opportunity. -- Guy

2 1

Re: February Meeting
by Guy Almes 15 Dec '94

15 Dec '94

Tim, I agree with your call for co-locating/coordinating the conferences. I believe that the NANOG community will be able to positively influence the ISoc conference agenda, content, and sense of reality. -- Guy

2 2

Re: February Meeting
by tjs＠msc.edu 15 Dec '94

15 Dec '94

It appears that the advertised "ops-program(a)isoc.org" doesn't exist. Is this conference still on? Or perhaps, I was supposed to say ops-programme(a)isoc.org? (Who was it that translated some IETF document to British spelling in a fit of some-or- other?) -tjs Date: Thu, 15 Dec 94 01:17:37 -0600 From: Mailer-Daemon (Mail Delivery Subsystem) Subject: Returned mail: User unknown ----- Transcript of session follows ----- >>> RCPT To:<ops-program(a)isoc.org> <<< 550 (USER) Unknown user name in "ops-program(a)isoc.org" 550 <ops-program(a)isoc.org>... User unknown

2 1

Re: February Meeting
by tjs＠msc.edu 15 Dec '94

15 Dec '94

> Date: Fri, 9 Dec 1994 01:27:52 -0500 > From: Elise Gerich <epg(a)merit.edu> > To: nanog(a)merit.edu > Subject: February Meeting > Cc: epg(a)merit.edu, pam(a)merit.edu > > At the last NANOG meeting in Ann Arbor, we decided to have a winter > meeting in Boulder, CO. NCAR kindly offered to host the meeting > and plans were finalized to have the meeting on Thursday and Friday, > February 9 and 10, 1995. > > ISOC has proposed to host a Operations Conference in February (21-22) > in San Diego, CA. The Description and Objectives of the > conference are: > [...] > ISOC has offered to provide meeting rooms for the winter > NANOG meeting if we would like to hold the NANOG meeting > on the Monday preceeding the Conference. > [...] Without having seen an agenda for either conference, it appears to me that these two conferences are likely to have similar missions, prospective attendees, and agenda. It is not clear to me that two such [apparently] similar conferences can both thrive; one may die, or worse, both may wither as people choose one forum or the other. In particular, it may be hard to justify the travel time and expense to attend both conferences. I recommend that either: o The two conferences be collocated (in time and space) and coordinate their agendas; o The conference organizers clearly articulate how the two conferences differ and why attendance at both would be useful. The February meetings seem like a good time to start. By the way, does either conference have agenda yet? -tjs

1 0

CERT Advisory VB-94:02.dec
by cert-advisory＠cert.org 14 Dec '94

14 Dec '94

CERT Vendor-Initiated Bulletin VB-94:02 December 14, 1994 Topic: Security Advisory #0505 ULTRIX and DEC OSF/1 Source: Digital Equipment Corporation, Software Security Response Team Related CERT documents: CERT Advisory CA-94:12 "Sendmail Vulnerabilities" To aid in the wide distribution of essential security information, the CERT Coordination Center is forwarding the following information from Digital Equipment Corp. Digital urges you to act on this information as soon as possible. Digital contact information is included in the forwarded text below; please contact them if you have any questions or need further information. ===========================FORWARDED TEXT STARTS HERE========================= SOURCE: Digital Equipment Corporation - ( DSIN / DSNlink FLASH MAIL ) Software Security Response Team 17.MAY.94 PRODUCT: ULTRIX Versions 4.3, 4.3A, V4.4 DECnet-ULTRIX Version 4.2 DEC OSF/1 Versions 1.2, 1.3, 1.3A, 2.0 ADVISORY INFORMATION: SUBJECT: Security Enhanced Kit for DECNET-ULTRIX V4.2, ULTRIX V4.3 (VAX/RISC), ULTRIX V4.3A (RISC), ULTRIX V4.4 (VAX/RISC), ULTRIX Worksystem Software and DEC OSF/1 V1.2 - V2.0 IMPACT: Potential security vulnerabilities exist where, under certain circumstances user access or privilege may be expanded. SOLUTION: ULTRIX: Upgrade/Install ULTRIX to an minimum of V4.4 and install the Security Enhanced Kit DEC OSF/1: Upgrade/Install to a minimum of V1.2 and install the Security Enhanced Kit [Note: In the text below, Digital identifies OSF/1 V2.0 as the minimum. Digital has confirmed that 2.0 is correct. --CERT staff] _______________________________________________________________________________ These kits are available from Digital Equipment Corporation by contacting your normal Digital support channel or by request via DSNlink for electronic transfer. _______________________________________________________________________________ IMPACT: Digital has discovered the existence of potential security vulnerabilities in the ULTRIX V4.3, V4.3a, V4.4 and DEC OSF/1 V1.2, V1.3, V2.0 Operating Systems, and DECnet-ULTRIX V4.2. These potential vulnerabilities were discovered as a result of evaluating recent reports of potential security vulnerabilities which were distributed on the INTERNET and as a result of Digital's continued engineering efforts. The solutions to these vulnerabilities have been included in the next release of ULTRIX and DEC OSF/1. The kits have been created to correct potential security vulnerabilities which, under certain circumstances may expand user access or privilege. Digital Equipment Corporation strongly urges Customers to upgrade to a minimum of ULTRIX V4.4 and DEC OSF/1 V2.0 then apply the Security Enhanced Kit. - Please refer to the applicable Release Note information prior to upgrading your installation. _______________________________________________________________________________ KIT PART NUMBERS and DESCRIPTIONS CSC PATCH # CSCPAT_4060 V1.0 ULTRIX V4.3 thru V4.4 (Includes DECnet-ULTRIX V4.2) CSCPAT_4061 V1.0 DEC OSF/1 V1.2 thru V2.0 _______________________________________________________________ These kits will not install on versions previous to ULTRIX V4.3 or DEC OSF/1 V1.2. _______________________________________________________________ _______________________________________________________________________________ _______________________________________________________________________________ The ULTRIX Security Enhanced kit replaces the following images: /usr/etc/comsat ULTRIX V4.3, V4.3a, V4.4 /usr/ucb/lpr " " /usr/bin/mail " " /usr/lib/sendmail " " /usr/etc/telnetd ULTRIX V4.3, V4.3a only ______________________________________ for DECnet-ULTRIX V4.2 installations: /usr/etc/dlogind /usr/etc/telnetd.gw *sendmail - is a previously distributed solution. _______________________________________________________________________________ The DEC OSF/1 Security Enhanced kit replaces the following images: /usr/sbin/comsat DEC OSF/1 V1.2, V1.3 V2.0 /usr/bin/binmail /usr/bin/lpr " " /usr/sbin/sendmail DEC OSF/1 V1.2, V1.3 only /usr/bin/rdist " " /usr/shlib/libsecurity.so DEC OSF/1 V2.0 only *sendmail - is a previously distributed solution. _______________________________________________________________________________ Digital urges you to periodically review your system management and security procedures. Digital will continue to review and enhance the security features of its products and work with customers to maintain and improve the security and integrity of their systems. _______________________________________________________________________________ NOTE: For non-contract/non-warranty customers contact your local Digital support channels for information regarding these kits. ______________________________________________________________________________ ======================FORWARDED TEXT ENDS HERE=============================== CERT bulletins, CERT advisories, information about FIRST representatives, and other information related to computer security are available for anonymous FTP from info.cert.org. If you wish to send sensitive incident or vulnerability information to CERT staff by electronic mail, we strongly advise that the e-mail be encrypted. The CERT Coordination Center can support a shared DES key, PGP (public key available via anonymous FTP on info.cert.org) or PEM (contact CERT staff for details). Internet E-mail: cert(a)cert.org Telephone: +1 412-268-7090 (24-hour hotline) CERT personnel answer 8:30 a.m.-5:00 p.m. EST(GMT-5)/EDT(GMT-4), and are on call for emergencies during other hours. Fax: +1 412-268-6989 CERT Coordination Center Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213-3890 USA CERT is a service mark of Carnegie Mellon University.

1 0

Additions to the NSFNET policy-based routing database
by sjr＠twain.merit.edu 14 Dec '94

14 Dec '94

------------------------------------------------------------------------------ The PRDB and this "NWG report" will be retired in December. Details below. ------------------------------------------------------------------------------ The following changes have been made to the NSFNET policy-based routing database and will be installed on the backbone by 08:00 EST : Total = As + Bs + Cs + Aggs Registered Networks 43894 = 30 5161 36357 2346 Configured Networks 40945 = 30 5106 33497 2312 Added Networks 24 = 0 0 19 5 Deleted Networks 27 = 0 2 25 0 IP address Net name Country Priority:AS ---------- -------- ------- ----------- 192.94.236/24 NET-COMSYS1 C:US 1:1240 2:1800 3:1239 193.195.13/24 KAINOS C:GB 1:3561(218) 2:3561(11) 198.14.32/21 ASN-PLE C:US 1:668 2:175 3:22 198.97.67/24 AFMCC2SU C:US 1:668 2:175 3:22 198.187.210/24 NETBLK-UNITRENDIX C:US 1:1321 2:2551(136) 198.188/16 NETBLK-CSUNET-SOUTH C:US 1:2150 2:200(128) 3:200(144) 198.189/16 NETBLK-CSUNET-NORTH C:US 1:200(128) 2:200(144) 3:2150 198.231.108/24 ROGERS-NET C:CA 1:701(136) 2:701(134) 3:2493(35) 4:2493(91) 198.231.110/24 ROGERS-NET C:CA 1:701(136) 2:701(134) 3:2493(35) 4:2493(91) 198.231.111/24 ROGERS-NET C:CA 1:701(136) 2:701(134) 3:2493(35) 4:2493(91) 198.231.116/24 ROGERS-NET C:CA 1:701(136) 2:701(134) 3:2493(35) 4:2493(91) 198.231.117/24 ROGERS-NET C:CA 1:701(136) 2:701(134) 3:2493(35) 4:2493(91) 198.231.118/24 ROGERS-NET C:CA 1:701(136) 2:701(134) 3:2493(35) 4:2493(91) 198.231.119/24 ROGERS-NET C:CA 1:701(136) 2:701(134) 3:2493(35) 4:2493(91) 198.231.121/24 ROGERS-NET C:CA 1:701(136) 2:701(134) 3:2493(35) 4:2493(91) 198.231.122/24 ROGERS-NET C:CA 1:701(136) 2:701(134) 3:2493(35) 4:2493(91) 198.231.123/24 ROGERS-NET C:CA 1:701(136) 2:701(134) 3:2493(35) 4:2493(91) 198.231.124/24 ROGERS-NET C:CA 1:701(136) 2:701(134) 3:2493(35) 4:2493(91) 198.231.125/24 ROGERS-NET C:CA 1:701(136) 2:701(134) 3:2493(35) 4:2493(91) 198.231.126/24 ROGERS-NET C:CA 1:701(136) 2:701(134) 3:2493(35) 4:2493(91) 198.231.127/24 ROGERS-NET C:CA 1:701(136) 2:701(134) 3:2493(35) 4:2493(91) 199.77.84/24(U) WSMV-DOM C:US 1:3561(218) 2:3561(11) 3:279 4:86 199.177.64/18 NETBLK-AADSNET-CIDR C:US 1:237 2:233 3:266 4:267 5:1225 199.187.208/23 NETBLK-UNITRENDIX C:US 1:1321 2:2551(136) Deletions: --146.193/16 INESC C:PT 1:1800 2:297(145) 3:297(144) 4:372 5:1133 6:1240 --155.252/16 PWCPH C:US 1:114 --192.12.232/24 PT-INESC-LIS C:PT 1:1800 2:297(145) 3:297(144) 4:372 5:1133 6:1240 --192.16.229/24 LOCKHEED-NET C:CA 1:2699(145) 2:2699(144) --192.16.234/24 DRE-DOC1 C:CA 1:2699(145) 2:2699(144) --192.35.246/24 INESCP-NET C:PT 1:1800 2:297(145) 3:297(144) 4:372 5:1133 6:1240 --192.67.76/24 PTUNET-DI-FCUL C:PT 1:1800 2:297(145) 3:297(144) 4:372 5:1133 6:1240 --192.68.221/24 NET-FCL-RCCN C:PT 1:1800 2:297(145) 3:297(144) 4:372 5:1133 6:1240 --193.136.48/24 INESCP-NET-SUPER C:PT 1:1800 2:1133 3:1240 --193.136.49/24 INESCP-NET-SUPER C:PT 1:1800 2:1133 3:1240 --193.136.50/24 INESCP-NET-SUPER C:PT 1:1800 2:1133 3:1240 --193.136.51/24 INESCP-NET-SUPER C:PT 1:1800 2:1133 3:1240 --193.136.52/24 INESCP-NET-SUPER C:PT 1:1800 2:1133 3:1240 --193.136.160/24 NET-FCUL-RCCN-1 C:PT 1:1800 2:1133 3:1240 --193.136.161/24 NET-FCUL-RCCN-2 C:PT 1:1800 2:1133 3:1240 --193.136.162/24 NET-FCUL-RCCN-3 C:PT 1:1800 2:1133 3:1240 --193.136.163/24 NET-FCUL-RCCN-4 C:PT 1:1800 2:1133 3:1240 --193.136.165/24 NET-FCUL-RCCN-6 C:PT 1:1800 2:297(145) 3:297(144) 4:372 5:1133 6:1240 --193.136.166/24 NET-FCUL-RCCN-7 C:PT 1:1800 2:297(145) 3:297(144) 4:372 5:1133 6:1240 --193.136.176/24 INESC-LX C:PT 1:1800 2:1133 3:1240 --193.136.177/24 INESC-LX-C-136-177 C:PT 1:1800 2:1133 3:1240 --193.136.178/24 INESC-LX-C-136-178 C:PT 1:1800 2:1133 3:1240 --193.136.179/24 INESC-LX-C-136-179 C:PT 1:1800 2:1133 3:1240 --198.52.4/24 LACCD2 C:US 1:200(128) 2:200(144) --198.52.5/24 LACCD3 C:US 1:200(128) 2:200(144) --198.52.6/24 LACCD4 C:US 1:200(128) 2:200(144) --198.52.7/24 LACCD5 C:US 1:200(128) 2:200(144) Expanded listing, sorted by country, then by organization: ========================================================== Canada ------ Rogers Data Services, 45 Esna Park Drive, Markham, ON, L3R 1C9, CANADA 1:701(136) Alternet 2:701(134) Alternet 3:2493(35) FONOROLA-EAST 4:2493(91) FONOROLA-EAST -------------- 198.231.108/24 ROGERS-NET (CA) 198.231.110/24 ROGERS-NET (CA) 198.231.111/24 ROGERS-NET (CA) 198.231.116/24 ROGERS-NET (CA) 198.231.117/24 ROGERS-NET (CA) 198.231.118/24 ROGERS-NET (CA) 198.231.119/24 ROGERS-NET (CA) 198.231.121/24 ROGERS-NET (CA) 198.231.122/24 ROGERS-NET (CA) 198.231.123/24 ROGERS-NET (CA) 198.231.124/24 ROGERS-NET (CA) 198.231.125/24 ROGERS-NET (CA) 198.231.126/24 ROGERS-NET (CA) 198.231.127/24 ROGERS-NET (CA) United Kingdom -------------- Kainos Software Ltd, 8-14 Mt Charles, Belfast, N.Ireland, BT7 1NZ, UNITED KINGDOM 1:3561(218) MCI-RESTON 2:3561(11) MCI-RESTON ------------- 193.195.13/24 KAINOS (GB) United States ------------- Alex Huppenthal, 6605 West Burnside Rd, Portland, OR 97210, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic 3:1239 SprintLink ------------- 192.94.236/24 NET-COMSYS1 (US) Ameritech Advanced Data Services, 339 E. Liberty, Suite 300, Ann Arbor, MI 48104, US 1:237 MichNet (MERIT) 2:233 UMnet (University of Michigan) 3:266 CICNET at MERIT 4:267 CICNET at UIUC 5:1225 CICNET ------------- 199.177.64/18 NETBLK-AADSNET-CIDR (US) CSUnet CIDR Block 1 serving No Cal, 4665 Lampson Avenue, Los Alamitos, CA 90720, USA 1:200(128) BARRNet 2:200(144) BARRNet 3:2150 CSUNET-SW ---------- 198.189/16 NETBLK-CSUNET-NORTH (US) CSUnet CIDR Block 1 serving So Cal, 4665 Lampson Avenue, Los Alamitos, CA 90720, USA 1:2150 CSUNET-SW 2:200(128) BARRNet 3:200(144) BARRNet ---------- 198.188/16 NETBLK-CSUNET-SOUTH (US) Cook Inlet Television Partners, LP d/b/a WSMV-TV, 5700 Knob Road, P.O. Box Four, Nashville, TN 37202, USA 1:3561(218) MCI-RESTON 2:3561(11) MCI-RESTON 3:279 SURANET Regional Network (Georgia Tech) 4:86 SURANET Regional Network (College Park) ------------ 199.77.84/24(U) WSMV-DOM (US) MSC/SXH (NET-AFMCC2SU), Logistics Systems Operations Center, Bldg 271, Wright Patterson AFB, OH 45433, USA 1:668 DREN (U.S. DoD Defense Research and Engineering Network) 2:175 AFWL-AS (Air Force Weapons Laboratory) 3:22 NOSC (Naval Ocean Systems Center) ------------ 198.97.67/24 AFMCC2SU (US) Phillips Laboratory (ASN-PLE), OLAC PL/ADO, Edwards AFB, CA 93523, USA 1:668 DREN (U.S. DoD Defense Research and Engineering Network) 2:175 AFWL-AS (Air Force Weapons Laboratory) 3:22 NOSC (Naval Ocean Systems Center) ------------ 198.14.32/21 ASN-PLE (US) Unitrendix Corp., 19300S Hamilton Ave #165, Gardena, CA 90248, USA 1:1321 ANS San Francisco - DNSS 11 2:2551(136) NETCOM -------------- 198.187.210/24 NETBLK-UNITRENDIX (US) 199.187.208/23 NETBLK-UNITRENDIX (US) ========================================================== The following Midlevel/Regional peering sessions have also been added: AS 2041 - CRL-GATE - DNSS 11 Peer: 198.32.128.20 - CR Laboratories, Box 326, Larkspur, CA 94977, USA - gw.crl.com AS690 CIDR Squeezings Report: 9648 Nets, 150 ASs, 2350 Aggregates ------------------------------------------------------------------ 9648 (85%) of the ever-announced more-specific routes within aggregates have been withdrawn. 180 of those were withdrawn within the last week. 854 the week before that. 490 the week before that. 150 ASs have registered aggregates in the PRDB. 100 of those are announcing aggregates. 77 have withdrawn at least one more specific route. 2350 Aggregates are configured. 1721 of these were Top-Level Aggregates (not nested in another aggregate). 1280 of these are being announced to AS690. 930 of those have at least one subnet configured (the other 350 may be saving the Internet future subnet announcements). 785 have stopped announcing at least one configured more specific route. 768 have stopped announcing half of their configured more specific routes. 708 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 October 25, 1994) In early December 1994, as part of the transition to the new Global Routing Registry (GRR), the Policy Routing Database (PRDB) will be retired. Many of the functions of the PRDB (including generation of router configurations for NSFNET) will be produced based on data from the Global Routing Registry. This change to the NSFNET Backbone service will involve the following changes: - The method for submitting new nets to be routed over AS690 will change. Instead of submitting a NACR to nsfnet-admin(a)merit.edu, you will need to submit a "route template" to auto-dbm(a)radb.ra.net . - Additions and entries to the new registry will be made by the Home AS which creates the route for each net, rather than being submitted by a AS690 peer AS. - Most of the PRDB reports (listed above) will no longer be produced. Equivalent information for most of these reports is available from the global Routing Registry. These are major changes to the system. These changes are being made in order to migrate NSFNET customers and the global user community to a Global Routing Registry system, which will be more capable of supporting user needs after the termination of the NSFNET Backbone services in April 1995. For more information, set your web browser to http://www.ra.net/rrinfo.html , or use anonymous ftp to obtain the files "OVERVIEW" and "transition.plan" from the directory "ftp.ra.net:pub/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: Additions to the NSFNET policy-based routing database
by Steven J. Richardson 13 Dec '94

13 Dec '94

Tonight's NACR activity included all correct Add NACRs received by noon Monday; tomorrow the correct changes/deletes will be processed. --Steven J. Richardson Merit/NSFNET sjr(a)merit.edu

1 0