- Test - lists.nanog.org

Re: PRDB Retirement next Monday, May 8
by M.H.Behringer＠dante.org.uk 03 May '95

03 May '95

My understanding of the situation for Europe is (and I'm sure Merit or ANS or somebody else will correct me if I'm wrong): - Currently we (Europe) have to register in the RIPE DB and send NACRs - As of next monday... ... we won't need to send NACRs any more. (nor something to the RADB) ... Merit will mirror the RIPE DB into the RADB, so that the RADB contains the RIPE data as well. This will be done on a, say, daily basis. (that was the assumption, right?) ... ANS (and others) access the RADB, which contains all information - At a later stage the whole system should be fully distributed, as discussed several times. Now, the one possible problem I can think of is that Merit is not able to do the mirroring until next Monday. In that case we (Europe) would have to send the route objects to the two DBes (RIPE and RADB) for a certain time to be defined. This would be not optimal, but it would work. Still I very much hope that we don't have to go for this. Comments? Michael

2 1

Re: Topics for the May 22-23 NANOG
by Scott Bradner 03 May '95

03 May '95

> How about resurecting the idea of reviewing RFC's and drafts for operational impact? as one of the OPS ADs I'd welcome anyone who would be willing to help in this task Scott

2 1

Re: PRDB Retirement next Monday, May 8
by Hank Nussbacher 03 May '95

03 May '95

On Mon, 1 May 1995 20:20:22 -0400 you said: >WILL YOU BE AUTHORIZED TO UPDATE THE RADB AFTER MAY 8? > >Under the old NACR/PRDB system, each AS maintained a list of "valid >requestors" who could make routing changes for that AS. Under the new >Route object/RADB system, each network has an Origin AS ("Home AS"); the >individuals who can make routing changes for that AS's networks are >listed in the Maintainer object for that AS. Initial versions of >Maintainer objects were created from the PRDB "valid requestor" >information on February 1, and many more Maintainer objects have been >added to the RADB since then. Thus it is very likely that your >authorization in the RADB has already been established. If you have >successfully submitted a NACR since February 1, then you are already >authorized to submit Route objects for that AS. The RADB has my entry as follows: mntner: MAINT-AS378 descr: ILAN admin-c: Hank Nussbacher tech-c: Hank Nussbacher upd-to: hank(a)vm.tau.ac.il auth: MAIL-FROM HANK(a)taunivm.tau.ac.il mnt-by: MAINT-AS378 changed: DB-admin(a)ra.net 940302 source: RADB The RIPE DB has my entry as follows: mntner: AS378-MNT descr: ILAN upd-to: hank(a)vm.tau.ac.il mnt-nfy: hank(a)vm.tau.ac.il auth: CRYPT-PW somecryptstring mnt-by: AS378-MNT admin-c: Hank Nussbacher tech-c: Hank Nussbacher changed: hank(a)vm.tau.ac.il 941122 source: RIPE I would assume that everyone in Europe has updated their mntner object and customized as they please. Now we have to do it again? Couldn't the RADB just copy all the mntner objects as listed in RIPE? > --Dale Johnson > Merit/RA Thanks, Hank Nussbacher Israel

2 1

Re: PRDB Retirement next Monday, May 8
by Steve Heimlich 02 May '95

02 May '95

Daniel, >does this mean that after May 8th European operators will have to submit >route objects to the RADB even though they have registered route objects >in the RIPE RR? If yes, how do we proceed to eliminate the need for this >double registration requirement? Let me give you the ANS perspective on this one: We hope to take RIPE RR registrations as authoritative for European operators, eliminating need for redundant registrations. This just seems to make sense, assuming that the RIPE registry is at least as valid a place from which to pull European route objects as the RADB. Almost certainly we will not be able to flash cut this on 5/8 (one thing at a time), but it's definitely part of the process. We'll do this by sucking routes out of radb.ra.net, but that should include the "latest" info mirrored with source:RIPE as I understand it. Steve

1 0

MAE-WEST
by bmanning＠ISI.EDU 02 May '95

02 May '95

Hi, The folks at AMES and I cabled up the MAE-WEST facilities there today and are waiting on MFS to enable the port so that the two parts of MAE-WEST will talk to each other. MCI is scheduled to come up early in the morning (03:00 ET! :) and Sprint to follow shortly there after. NET99, Alternet, ESnet, NSI, and the RA Route Server are already present. -- --bill

4 4

PRDB Retirement next Monday, May 8
by Dale S. Johnson 02 May '95

02 May '95

What Networks Need to Do When the PRDB Is Retired On Monday, May 8, the Policy Routing Database (PRDB) will be turned off. The PRDB has been used to configure the NSFNET Backbone Service and ANSNET (AS690) since 1989. After May 8, configurations for the ANSNET backbone will be generated from the Routing Arbiter Database (RADB). The PRDB and the RADB have been running with parallel data for over a year. As of May 8, the last data from the PRDB will be transferred to the RADB, and the PRDB will be permanently retired. FROM NACRS TO ROUTE OBJECTS Starting 09:00 EST May 8, NACRs will no longer be accepted for AS690 configurations; the way to submit additions or changes of route announcements for AS690 will be to submit Route objects by e-mail to auto-dbm(a)ra.net. If you submit a NACR after 09:00 May 8, you will receive a reply that gives you a translation of that NACR into a Route object and explains how to mail that Route object to auto-dbm(a)ra.net for immediate inclusion in the RADB. For an overview of the RADB and more information about creating and submitting Route objects, see: http://www.ra.net (select Routing Arbiter from the Projects menu) ftp://ftp.ra.net/routing.arbiter/radb/OVERVIEW ftp://ftp.ra.net/routing.arbiter/radb/doc/how_to_register WILL YOU BE AUTHORIZED TO UPDATE THE RADB AFTER MAY 8? Under the old NACR/PRDB system, each AS maintained a list of "valid requestors" who could make routing changes for that AS. Under the new Route object/RADB system, each network has an Origin AS ("Home AS"); the individuals who can make routing changes for that AS's networks are listed in the Maintainer object for that AS. Initial versions of Maintainer objects were created from the PRDB "valid requestor" information on February 1, and many more Maintainer objects have been added to the RADB since then. Thus it is very likely that your authorization in the RADB has already been established. If you have successfully submitted a NACR since February 1, then you are already authorized to submit Route objects for that AS. Note, however, that if another organization has been submitting NACRs for you, that organization may no longer be authorized to do this under the RADB unless you specifically include e-mail addresses for that organization in your Maintainer object. Here is the breakdown of authorized submitters: Date Who Can Make Routing Changes ------ ------------------------------ Before Feb. 1 Any valid requester of any AS in the network's announcements ("aslist"), including the Primary AS Feb. 1 - May 8 Persons specified by the Maintainer objects of *either* the network's Primary AS or its Home AS After May 8 *Only* persons specified by the Maintainer object of the network's Home AS The e-mail addresses for people authorized to make changes for your network must be listed on separate MAIL-FROM lines in your Maintainer object. (A more elaborate system can be used after May 8.) To verify that your Maintainer object contains the correct information, enter a command such as the following: whois -h whois.ra.net MAINT-AS690 For more information on checking, submitting or updating Maintainer objects, see: http://www.ra.net (select Routing Arbiter from the Projects menu) ftp://ftp.ra.net/routing.arbiter/radb/doc/updating_maintainers If you have further questions about registering in the RADB, send e-mail to DB-admin(a)ra.net. --Dale Johnson Merit/RA

2 1

Re: Has PSI been assigned network 1?
by Eric Kozowski 02 May '95

02 May '95

>You would think the words "Silicon Switch Processor" might >clue people in that the board in question has nice little >chips on it doing routing/switching, leaving the 68040 >free to process BGP updates etc. > >Unfortunately, the 68040 is unable to keep up in ugly >situations... Xyplex has a router card for their 9000 chassis that uses the 68060 and had BGP4 support in the alpha phase. We are looking at doing beta testing of this product. -- Eric Kozowski Structured Network Systems, Inc. kozowski(a)structured.net Better, Cheaper, Faster -- pick any two. (503)656-3530 Voice "Providing High Quality, Reliable Internet Service" (800)881-0962 Voice 56k to DS3

1 0

Topics for the May 22-23 NANOG
by Susan R. Harris 02 May '95

02 May '95

Greetings - here's are the NANOG topics we've come up with so far. Are there other subjects you'd like to hear about? ------------------------------------------- --Symmetric routing in a multi-provider Internet --RA project update --NAP status reports --InterNIC registration procedures --Coordination issues for distributed routing registries --IP Provider Metrics WG update --RPS (Routing Policy System) WG update --ATM networking in Oregon --Route flapping analyses --IPv6 autoconfiguration: implications for network operators --New SNMP management capabilities in MRouteD --Overview of the Multi-Threaded Routing Toolkit --GateD update ------------------------------------------------------------------------ Susan R. Harris Merit Network, Inc. srh(a)merit.edu Phone: (313) 936-2100 Fax: (313) 747-3185 ------------------------------------------------------------------------

2 1

AS690 routing policy changes
by Steve Heimlich 01 May '95

01 May '95

Folks, The final NSFnet configuration took place on Friday, 4/28. Starting this week and continuing over the course of the next few weeks, ANS will be migrating AS690 policy away from NSFnet policy and toward something new and improved. There may be some providers at interchange points who are still using AS 690 peer routers as route servers (e.g., to learn another provider's routes from us with no extra peering sessions needed). We expect to eliminate third party routing at interchange points early this month; this change will not affect connectivity with ANS, but may affect connectivity between other ASes. Those providers still in need of a route server should contact the Routing Arbiter (DB-admin(a)ra.net) to set up peering arrangements. As an import policy aid for peer providers at these interchange points, I have registered an AS macro object in the RADB. This macro is recursively defined (from the root identifier of "AS-ANS") and lists the ASes for which ANS provides transit. It's defined in such a way as to make "cold potato" routing easy to set up for those peers to whom we speak at multiple U.S. interchange points; those providers interested in doing mutual cold potato routing can send me a note. ANS would like to use corresponding AS macros registered by other providers to ease such a configuration. Content of this recursively defined macro can be examined using whois: whois -h whois.ra.net AS-ANS ANS will update this macro in the RADB as needed. It is expected to show up in the RADB shortly, though I've included it below. Steve ---------------------- as-macro: AS-ANS descr: List of ANS ASes by U.S. region as-list: AS-ANS-EAST AS-ANS-CENTRAL AS-ANS-WEST guardian: rtmonger(a)ans.net rtmonger(a)noc.ans.net tech-c: Selina Priestley admin-c: Steve Heimlich notify: ans-admin(a)ans.net notify: heimlich(a)ans.net mnt-by: ANS changed: heimlich(a)ans.net 950430 source: ANS as-macro: AS-ANS-EAST descr: List of ANS U.S. Eastern ASes as-list: AS-ANS-NY AS-ANS-CT AS-ANS-DC AS-ANS-NC AS-ANS-PA AS-ANS-GA guardian: rtmonger(a)ans.net rtmonger(a)noc.ans.net tech-c: Selina Priestley admin-c: Steve Heimlich notify: ans-admin(a)ans.net notify: heimlich(a)ans.net mnt-by: ANS changed: heimlich(a)ans.net 950430 source: ANS as-macro: AS-ANS-CENTRAL descr: List of ANS U.S. Central ASes as-list: AS-ANS-TX AS-ANS-MO AS-ANS-IL AS-ANS-OH guardian: rtmonger(a)ans.net rtmonger(a)noc.ans.net tech-c: Selina Priestley admin-c: Steve Heimlich notify: ans-admin(a)ans.net notify: heimlich(a)ans.net mnt-by: ANS changed: heimlich(a)ans.net 950430 source: ANS as-macro: AS-ANS-WEST descr: List of ANS U.S. Western ASes as-list: AS-ANS-CO AS-ANS-WA AS-ANS-SF AS-ANS-LA AS-ANS-NM AS-ANS-HA guardian: rtmonger(a)ans.net rtmonger(a)noc.ans.net tech-c: Selina Priestley admin-c: Steve Heimlich notify: ans-admin(a)ans.net notify: heimlich(a)ans.net mnt-by: ANS changed: heimlich(a)ans.net 950430 source: ANS as-macro: AS-ANS-NY descr: List of ANS NY ASes as-list: AS1324 AS238 AS689 AS1128 AS1660 AS1662 AS1665 AS1670 as-list: AS1680 AS1683 AS1690 as-list: AS1747 AS2019 AS2020 AS2386 AS2493 AS2514 AS2685 AS3065 AS3397 as-list: AS3670 AS3769 AS3792 AS3800 AS3903 AS3997 AS4019 guardian: rtmonger(a)ans.net rtmonger(a)noc.ans.net tech-c: Selina Priestley admin-c: Steve Heimlich notify: ans-admin(a)ans.net notify: heimlich(a)ans.net mnt-by: ANS changed: heimlich(a)ans.net 950430 source: ANS as-macro: AS-ANS-CT descr: List of ANS CT ASes as-list: AS1326 AS2002 AS2538 AS2752 AS3723 guardian: rtmonger(a)ans.net rtmonger(a)noc.ans.net tech-c: Selina Priestley admin-c: Steve Heimlich notify: ans-admin(a)ans.net notify: heimlich(a)ans.net mnt-by: ANS changed: heimlich(a)ans.net 950430 source: ANS as-macro: AS-ANS-DC descr: List of ANS DC ASes as-list: AS1327 AS1133 AS1686 AS1693 AS1972 AS1934 AS2056 AS2548 as-list: AS2631 AS2649 AS3358 AS3360 AS3394 AS4018 AS4252 guardian: rtmonger(a)ans.net rtmonger(a)noc.ans.net tech-c: Selina Priestley admin-c: Steve Heimlich notify: ans-admin(a)ans.net notify: heimlich(a)ans.net mnt-by: ANS changed: heimlich(a)ans.net 950430 source: ANS as-macro: AS-ANS-PA descr: List of ANS PA ASes as-list: AS1336 AS3576 guardian: rtmonger(a)ans.net rtmonger(a)noc.ans.net tech-c: Selina Priestley admin-c: Steve Heimlich notify: ans-admin(a)ans.net notify: heimlich(a)ans.net mnt-by: ANS changed: heimlich(a)ans.net 950430 source: ANS as-macro: AS-ANS-NC descr: List of ANS NC ASes as-list: AS1329 AS1312 AS1278 AS2916 AS4188 guardian: rtmonger(a)ans.net rtmonger(a)noc.ans.net tech-c: Selina Priestley admin-c: Steve Heimlich notify: ans-admin(a)ans.net notify: heimlich(a)ans.net mnt-by: ANS changed: heimlich(a)ans.net 950430 source: ANS as-macro: AS-ANS-GA descr: List of ANS GA ASes as-list: AS1333 AS1697 AS1969 AS2560 AS3595 AS4236 guardian: rtmonger(a)ans.net rtmonger(a)noc.ans.net tech-c: Selina Priestley admin-c: Steve Heimlich notify: ans-admin(a)ans.net notify: heimlich(a)ans.net mnt-by: ANS changed: heimlich(a)ans.net 950430 source: ANS as-macro: AS-ANS-TX descr: List of ANS TX ASes as-list: AS1328 AS2139 guardian: rtmonger(a)ans.net rtmonger(a)noc.ans.net tech-c: Selina Priestley admin-c: Steve Heimlich notify: ans-admin(a)ans.net notify: heimlich(a)ans.net mnt-by: ANS changed: heimlich(a)ans.net 950430 source: ANS as-macro: AS-ANS-MO descr: List of ANS MO ASes as-list: AS1330 AS1657 AS1689 AS2552 AS3145 guardian: rtmonger(a)ans.net rtmonger(a)noc.ans.net tech-c: Selina Priestley admin-c: Steve Heimlich notify: ans-admin(a)ans.net notify: heimlich(a)ans.net mnt-by: ANS changed: heimlich(a)ans.net 950430 source: ANS as-macro: AS-ANS-IL descr: List of ANS IL ASes as-list: AS1323 AS17 AS1676 AS1681 AS1686 AS1688 AS1692 AS1757 as-list: AS2489 AS3789 AS4053 AS4181 AS4249 guardian: rtmonger(a)ans.net rtmonger(a)noc.ans.net tech-c: Selina Priestley admin-c: Steve Heimlich notify: ans-admin(a)ans.net notify: heimlich(a)ans.net mnt-by: ANS changed: heimlich(a)ans.net 950430 source: ANS as-macro: AS-ANS-OH descr: List of ANS OH ASes as-list: AS1325 AS1678 AS1681 AS1757 AS1975 AS2138 AS2752 AS3552 as-list: AS3672 AS4373 guardian: rtmonger(a)ans.net rtmonger(a)noc.ans.net tech-c: Selina Priestley admin-c: Steve Heimlich notify: ans-admin(a)ans.net notify: heimlich(a)ans.net mnt-by: ANS changed: heimlich(a)ans.net 950430 source: ANS as-macro: AS-ANS-CO descr: List of ANS CO ASes as-list: AS1332 AS1744 AS2140 AS2941 AS3149 AS3364 AS3378 guardian: rtmonger(a)ans.net rtmonger(a)noc.ans.net tech-c: Selina Priestley admin-c: Steve Heimlich notify: ans-admin(a)ans.net notify: heimlich(a)ans.net mnt-by: ANS changed: heimlich(a)ans.net 950430 source: ANS as-macro: AS-ANS-WA descr: List of ANS WA ASes as-list: AS1331 AS1671 AS1684 AS1691 AS2022 AS2544 AS3818 guardian: rtmonger(a)ans.net rtmonger(a)noc.ans.net tech-c: Selina Priestley admin-c: Steve Heimlich notify: ans-admin(a)ans.net notify: heimlich(a)ans.net mnt-by: ANS changed: heimlich(a)ans.net 950430 source: ANS as-macro: AS-ANS-SF descr: List of ANS SF ASes as-list: AS1321 AS1280 AS1679 AS1688 AS1744 AS1957 AS2386 AS2551 AS2772 as-list: AS3462 AS3568 AS3605 AS3758 AS3768 guardian: rtmonger(a)ans.net rtmonger(a)noc.ans.net tech-c: Selina Priestley admin-c: Steve Heimlich notify: ans-admin(a)ans.net notify: heimlich(a)ans.net mnt-by: ANS changed: heimlich(a)ans.net 950430 source: ANS as-macro: AS-ANS-LA descr: List of ANS LA ASes as-list: AS1322 AS1671 AS2930 guardian: rtmonger(a)ans.net rtmonger(a)noc.ans.net tech-c: Selina Priestley admin-c: Steve Heimlich notify: ans-admin(a)ans.net notify: heimlich(a)ans.net mnt-by: ANS changed: heimlich(a)ans.net 950430 source: ANS as-macro: AS-ANS-NM descr: List of ANS NM ASes as-list: AS1334 AS175 AS377 AS3388 AS2901 guardian: rtmonger(a)ans.net rtmonger(a)noc.ans.net tech-c: Selina Priestley admin-c: Steve Heimlich notify: ans-admin(a)ans.net notify: heimlich(a)ans.net mnt-by: ANS changed: heimlich(a)ans.net 950430 source: ANS as-macro: AS-ANS-HA descr: List of ANS HA ASes as-list: AS1335 AS3381 guardian: rtmonger(a)ans.net rtmonger(a)noc.ans.net tech-c: Selina Priestley admin-c: Steve Heimlich notify: ans-admin(a)ans.net notify: heimlich(a)ans.net mnt-by: ANS changed: heimlich(a)ans.net 950430 source: ANS

1 0

Re: Pathways of the NSFNET - a poem
by Sean Doran 01 May '95

01 May '95

Actually, credit where it's due, it's Pope's poem, from _Essay on Man_, which was written in the early 1700s. Sean.

2 1