- db-wg - mailman.ripe.net

RE: Proposal for extended syntax for the 'country:' attribute
by Wilfried Woeber, UniVie/ACOnet 19 Jan '96

19 Jan '96

>Please advise us. We have the idea that this topic is really something >for an interesting academic debate ;-), I wonder - do you (actually the software :-) currently check against some sort of list? iso3166? Wilfried.

2 1

Proposal for extended syntax for the 'country:' attribute
by David.Kessens＠ripe.net 19 Jan '96

19 Jan '96

Dear all, Recently, we ran into some inconsistencies that resulted from the 'country:' attribute as used in 'inetnum:' objects. Hereby, I want to describe the (small) problems we found and propose possible solutions. Problem description: The RIPE NCC currently gets address space allocated from IANA for assignment to local registries in our working area. This allocated address space needs to registered in the RIPE database. Currently, we fill the country attribute with the value 'EU', but we feel that it is not the right representation since the address space is meant to be used for the whole working area of RIPE. Example: inetnum: 193.0.0.0 - 193.255.255.255 country: EU [ ... stuff deleted... ] The same problem exists for multinational registries that get address space allocated that is used in more then one country. Solutions: Since we are dealing with a small, though highly visible problem we need easy and quick fixes to avoid putting too much work in something that's not really worth it ;-). We present them here in order of our preference: 1) we allow multiple country codes in the 'country:' attribute and allow for multiple line 'country:' code attributes for long lists of country codes. Pros: Solves the problem completely, is politically correct, easy to implement Cons: Might be a little bit overkill, especially if you look at the number of countries in the RIPE area. 2) Make country attribute optional since it doesn't really matter were the address space is used Pros: Solves the problem completely, is politically correct, very easy to implement Cons: We loose some information that might be useful (for what?) 3) We invent new country codes for non-existing entities like EU. Pros: Solves the problem. Cons: not politically correct, we might need to define more names. We get discussions like EU is something else then the RIPE working area that is much bigger. We might need more different codes. We might get funny things when ISO is defining new country codes (that might be the same as our pseudo codes), which happens all to often in Europe and around... 4) A combination of the proposed solutions, e.g. make the attribute optional *and* allow multiple country codes. 5) We leave it as it is Pros: The easiest thing Cons: We keep the inconsistencies Please advise us. We have the idea that this topic is really something for an interesting academic debate ;-), though we feel that we need to do something to solve this problem! David Kessens RIPE NCC

1 0

Proposal for the stored/processed attribute (action 19.12)
by David.Kessens＠ripe.net 19 Jan '96

19 Jan '96

Dear all, When I published the release notes of the RIPE database v1.1 beta version I also made some small notes regarding the format of the serial numbers that are needed for the (nearly) real-time mirroring of the RIPE database. Though, I know that you all like debating I didn't get any reactions :-(. Therefore I would like to stir up the discussion somewhat by highlighting the point (again) and formulate a (not the) proposal. If I understand our action list correct, the proposal will also make the historic action point on Marten Terpstra (19.12) about the 'stored:/processed:' attribute obsolete. What is (nearly) real-time mirroring support: The RIPE database software now labels all incoming (atomic) updates with an ever increasing serial number and stores the updates. It is now possible to retrieve all the changes to the database every ten minutes by use of a program that has been added to the RIPE database distribution. Before using the program it is required that you ask the people that maintain the database server near you (at RIPE: <ripe-dbm(a)ripe.net>), to be put in an accessslist. We haven't had any major problems with the beta version software (so far) except for some small bugs and support files that needed some more explanation. We are now using the software for a mirror server at RIPE and plan to change the roles of mirror and backup somewhere at the end of January. Also, some registries (GARR-NIS, SWITCH, ANS) have already such a mirror server running. Problem description: The current real-time mirroring system stores all updates together with an ever increasing serial number in separate files. Although it works, it doesn't allow for growth (computers tend not to be able to handle ever increasing integer values). Also other features like building a history of an object are not possible and system failures are difficult to handle. From the start of the real-time mirror project we intended to first get the thing working and to make a design that would make adding these features possible. Since it appears to work now, I want to publish a proposal. There are two important things that needs to be addressed: - We need a reliable and unique serial number. - We want to be able to roll back *and* forth to a random date/serial by using the collection of all updates Proposal: We add a 'stored:' attribute to every object in the database that will contain the following information: stored: (NEW|UPD) DATE TIME serialnumber NEW|UPD - are we dealing with a new object or is it already updated once ? DATE - YYYYMMDD date of storing including the leading 19 or 20 TIME - time in HH:MM.SS, UTC time zone SERIAL - serial number to avoid updates with same time & date This should be an (nearly) ever increasing number. It could start from 0 for every date & time combination, but then we still need another ever increasing number for finding out if we missed updates or not. Of course every detail is open to discussion, I just wrote down one of the possibilities. In addition to the stored attribute we need a 'replaced:' attribute that will point to the object that it replaced and will thus nearly have the same syntax: replaced: SOURCE DATE TIME SERIAL We add the SOURCE here, for the time when we start integrating the different registry databases. Furthermore, we need to decide if we want to have both attributes to be visible when doing a whois query, one of them visible or all hidden except when using a special option. As always, please advise! David Kessens RIPE NCC

1 0

RE: Unauthorized modifications of RIPEDB
by Wilfried Woeber, UniVie/ACOnet 15 Jan '96

15 Jan '96

Looking at this incident with my DB-WG hat on - = > Last week the following new 219 domains appeared in RIPEDB. = > I can't believe that all of European TLD administrators = > registered this domains at the same time. Moreover with and without CO. I wonder who's going to remove these mis-leading entries? ...could become an interesting game if this becomes popular :-) Wilfried. -------------------------------------------------------------------------- Wilfried Woeber : e-mail: Woeber(a)CC.UniVie.ac.at Computer Center - ACOnet : Vienna University : Tel: +43 1 4065822 355 Universitaetsstrasse 7 : Fax: +43 1 4065822 170 A-1010 Vienna, Austria, Europe : NIC: WW144 --------------------------------------------------------------------------

2 1

FYI: RIPE DB and Domain Names
by Daniel Karrenberg 15 Jan '96

15 Jan '96

------- Forwarded Message Date: Mon, 15 Jan 1996 10:23:15 +0100 From: Daniel Karrenberg <Daniel.Karrenberg(a)ripe.net> Sender: dfk(a)ripe.net To: Domain registration staff <hostmaster(a)sztaki.hu> cc: ripe-op(a)ripe.net Subject: Unauthorized modifications of RIPEDB > Domain registration staff <hostmaster(a)sztaki.hu> writes: > Dear NCC, > > > Last week the following new 219 domains appeared in RIPEDB. > I can't believe that all of European TLD administrators > registered this domains at the same time. Moreover with and without CO. There are two basic problems here: 1) Confusion about the role of the RIPE database in *domain names*. The database is not authoritative about domain names. It is just informational for these. The authoritative registry of domain names for TLDs is kept by TLD administrators. They are encouraged use the ripe database to make their registry accessible. This is *not* mandatory. 2) Lack of authorisation in the RIPE database for the *creation* of objects. As David Kessens has pointed out already we are working on this. Once this is implemented TLD administrators can control the creation of objects within their namespace. This is the top priority database development item at the moment. We are also working on a simple referral method so that TLD administrators can run their own whois services, as the NL TLD administrator does. Until these problems are solved the RIPE database can be nothing more than informational about TLDs. Oncve they are solved TLD administrators have the means to keep their data clean if they wish. Daniel ------- End of Forwarded Message

1 0

Re: Modification of RIPE-181's as-in/as-out attributes
by Steven J. Richardson 29 Nov '95

29 Nov '95

Actually, I'd like to even extend this further; it would be wonderful to have the "<aut-num>" of both the "as-in" and "as-out" attributes become an expression--called, say, "<as-list expression>"--more like the "<routing policy expression>" which appears later in these attributes. Whereas the <routing policy expression> evaluates to "a list of one or more ASes, AS Macros, Communities, Route Lists," the <as-list expression> would evaluate to one or more ASs, and would allow the Boolean operators which can be used in the <routing policy expression>. This is particularly usefule for customers of rps/RIPE-181 who wish to express their policy in the easiest manner--e.g., with NOT, one can specify the set one does _not_ want, as well as the set one wants, and there are a lot of cases where the use of NOT (ASxx ) would be very helpful. If the <aut-num> -> <as-list> transition makes sense, I think we should wrap the addition of the Boolean operators into this, as well, so that there is a nice, complete syntax for this element of the as-in/as-out attributes (or their equivalent), rather than a "half-baked" version. How does this sound? Steve R. == >Date: Tue, 24 Oct 1995 16:11:59 -0400 >From: "Steven J. Richardson" <sjr(a)merit.edu> >Message-Id: <199510242011.QAA26472(a)home.merit.edu> >To: rps(a)isi.edu >Subject: Modification of RIPE-181's as-in/as-out attributes >Cc: db-wg(a)ripe.net, sjr(a)home.merit.edu >Status: RO > >In the process of reviewing RIPE-181-represented policies, I've >noticed an opportunity for what I think would be a useful >modification of the as-in/as-out attributes of the aut-num >object. > >Currently, the syntax for these attributes is given as: > > as-in: from <aut-num> <cost> accept <routing policy expression> > > as-out: to <aut-num> announce <routing policy expression> > >I see policies which would be usefully condensed via allowing >the <aut-num> to be an AS *macro*, too. > >E.g.: > >aut-num: 99999 >as-name: SOMEAS >... >as-in: from AS10 100 accept ANY AND NOT {0.0.0.0/0} >as-in: from AS20 100 accept ANY AND NOT {0.0.0.0/0} >as-in: from AS30 100 accept ANY AND NOT {0.0.0.0/0} >as-in: from AS40 100 accept ANY AND NOT {0.0.0.0/0} >as-in: from AS50 100 accept ANY AND NOT {0.0.0.0/0} >as-in: from AS60 100 accept ANY AND NOT {0.0.0.0/0} >as-in: from AS70 100 accept ANY AND NOT {0.0.0.0/0} >as-in: from AS110 150 accept ANY AND NOT {0.0.0.0/0} >as-in: from AS120 150 accept ANY AND NOT {0.0.0.0/0} >as-in: from AS130 150 accept ANY AND NOT {0.0.0.0/0} >as-in: from AS140 150 accept ANY AND NOT {0.0.0.0/0} >as-in: from AS150 150 accept ANY AND NOT {0.0.0.0/0} >as-in: from AS160 150 accept ANY AND NOT {0.0.0.0/0} >as-in: from AS170 150 accept ANY AND NOT {0.0.0.0/0} > > >could be equivalent to: > >aut-num: 99999 >... >as-in: from AS-SOMEAS-100-NO-DEFAULT 100 accept ANY AND NOT {0.0.0.0/0} >as-in: from AS-SOMEAS-150-NO-DEFAULT 150 accept ANY AND NOT {0.0.0.0/0} > > >with the macro definitions: > >as-macro: AS-SOMEAS-100-NO-DEFAULT >descr: ASs which AS-99999 accepts at pref. 100 (any but >descr: the default route) >as-list: AS110 AS120 AS130 AS140 AS150 AS160 AS170 >... > >as-macro: AS-SOMEAS-150-NO-DEFAULT >descr: ASs which AS-99999 accepts at pref. 150 (any but >descr: the default route) >as-list: AS10 AS20 AS30 AS40 AS50 AS60 AS70 >... > >(The same could be said of as-out lines.) > >What do you think? > > >Steve Richardson/Merit

3 4

URL mixup
by Susan R. Harris 29 Nov '95

29 Nov '95

My apologies for mixing up the URLs in this afternoon's "new RA tools" message. The tools for generating NAP routing table and route flap reports are both available at: http://www.ra.net/~ra/statistics/ --Susan Harris

1 0

New tools from the RA project (fwd)
by Elise Gerich 28 Nov '95

28 Nov '95

FYI....just in case you all aren't on these other lists. --Elise >Susan R. Harris writes: > From owner-cidrd(a)aarnet.edu.au Tue Nov 28 17:01:20 1995 > Date: Tue, 28 Nov 1995 16:47:35 -0500 (EST) > From: "Susan R. Harris" <srh(a)merit.edu> > To: cidrd(a)iepg.org, bgp(a)ans.net > Subject: New tools from the RA project > Message-ID: <Pine.SUN.3.91.951128164516.1874K-100000(a)home.merit.edu> > MIME-Version: 1.0 > Content-Type: TEXT/PLAIN; charset=US-ASCII > > Greetings - Just a quick note to let you know about some new tools > available from the Routing Arbiter project. Comments and bug reports > welcome; please send 'em to ra-team(a)ra.net. > > > A new RADB tool tells you which RADB routes in an AS are duplicated or > covered by less specific routes in the IRR: > > http://www.ra.net/~ra/RADB.tools.docs/.reports.html > > > A new tool to generate Internet routing table reports for each NAP > tells you (1) the maximum number of announced routes in the Route > Server's routing tables, (2) the complete Internet routing table, > listed by prefix and associated AS path, as seen by the NAP's Route > Servers, or (3) the number of routes seen by each Route Server, listed > by RS peer and origin AS. > > The reports in (2) from the Washington, D.C. NAP (MAE-East) have shown > some interesting numbers, like 32-bit host announcements and prefixes > reserved by RFC 1597 (private internet address allocation). > > > You can now generate NAP route flap reports by RS peer as well as by > AS origin, prefix, and specific AS: > > http://www.ra.net/~ra/statistics/.routes.html > ------------------------------------------------------------------------ > Susan R. Harris, Ph.D. Merit Network, Inc. srh(a)merit.edu > Phone: (313) 936-2100 Fax: (313) 747-3185 > ------------------------------------------------------------------------ > > > >

1 0

NEW *BETA* release RIPE database: ripe-dbase-1.1beta.tar.gz
by RIPE Database Manager 20 Nov '95

20 Nov '95

Dear all, This message is to announce the new *beta* version of the RIPE database. Most interesting new features are: - the new release supports nearly real time mirroring of the RIPE database - BSD DB dbm package is fully supported - Network updates, a method for directly updating objects by use of 'whois -U'. The use of this method is restricted by use of an accesslist and intended for the people that maintain a database. - new database help file and many more small changes and fixes. Please read the release notes at the bottom of this message for more information and discussion about these topics. Since the number of changes is quite large (core routines like 'enread' have been rewritten), we decided to bring out a beta version first. Please don't use this software (yet) for your core activities, we don't either ;-), The software is available from: ftp://ftp.ripe.net/ripe/dbase/software/ripe-dbase-1.1beta.tar.gz Please send bug reports/fixes directly to <ripe-dbm(a)ripe.net> and I will fix the problem, Kind regards, David Kessens RIPE NCC database software maintainer ********************************************************************** NOTE: This is a *BETA* version of the RIPE database. Please only use this version of the software for test purposes. ********************************************************************** RELEASE NOTES: - Nearly real time mirroring support: What is it: The database software now keeps serial numbers of all updates. If you have been added to an accesslist, it it possible to retrieve all the changes to the database. A program 'backupupd' has been added to the distribution that can retrieve these changes and update your mirror database automatically. This program is intended to be put in a cronjob. The whois erver has an access list so you first need to ask the site to be mirrored to add your host to the access list. Please let me now <ripe-dbm(a)ripe.net> if you are interested in testing this feature, and I will add your test site to the access list. Short discussion: Note that this is the first version, it currently uses seperate files internally for every update. I plan to change this since this is not really what we want with 2000 (atomic) updates on some days. Furthermore, we use currently an ever increasing integer serial number, I personnally think that it is better to use another format and store the information in a special not visible (only with a whois option) attribute: stored: (NEW|UPD) DATE TIME TIMEZONE serialnumber NEW|ADD - is this an older object ?!? or new... We probably also want an optional attribute 'replaced:' that points to the previous version of the object when the object was an UPD(date). DATE - YYYYMMDD date of storing including the leading 19 or 20 TIME - time in HH:MM.SS TIMEZONE - ?!? SERIAL - serial number to avoid updates with same time & date Of course this is open to discusssion, it is just one of the possibilities. - BSD berkeley DB support: The database software can now use the Berkeley DB dbm package. According to many people this package is superior to most other dbm packages that perl can use (unlimited size of keys/values, platform independent db files). We have put the current sources for this package at ftp://ftp.ripe.net/tools/db.1.85.tar.gz It should be possible with the BSD DB package to increase the OVERFLOWSIZE and as result get rid of (most) of the classless overflow files, however, this caused indexing problems on my BSDI test machine, but you might want to give it a try on other systems. - Problems with finding persons that have a very common first and last name (the problem we recently discussed on the 'db-wg' mail list can nearly disappear when: When you use dbm packages (e.g. BSD DB) that support much larger/unlimited size keys and values you can easily increase the MAXHITS config variable and the troubles that were recently discussed on the mailing list with persons having a very common first and last name will happen much less often. - a new help and HOWTO use the RIPE database file is available use 'whois -h whois.ripe.net HELP' to get the most recent version. The document gives a short introduction on the database, tells you how to create/update/delete objects, contains a section with tips and common problems and gives pointers to other documentation about the database. - Recent indexing problems and changes to 'netdbm' We recently experienced severe problems with the classless indexing of the RIPE database. Indexing just didn't work anymore due to index files that grew too large. This only happened when people used the '-p' option. Also no problems were reported when the BSD DB package was used. Solution: - Disabled the '-p' option because of the recent indexing problems we saw, professionals will be able to enable it by changing one line of code. - BSD DB dbm package is now fully supported. Important change: -c makes now a normal index as well as a classless index - BSDI/perl memory leak problems Due to a memory leak with perl on BSDI machines we needed to make the code more memory conscious. enread.pl has been rewritten completely and uses now less memory and as an (intended) side effect became faster when reading big objects. - Most patches (for greater speed and less memory consumption) that I received from Curtis Villamizar <curtis(a)ans.net> have been included. Thanks Curtis! - The direct network updating method is now fully supported. Currently this method is only intended for use by the registry itself, however it is possible to add support in the maintainer objects. You can now do you updates very rapidly by giving the command 'whois -U' and to input your object via STDIN. Of course, this is also protected with an access list. - The special magic to overrule the maintainer protection needs a password now. Syntax will be published after the main registries support this... - dbupdate -T Makes it very easy to install your own test database. The only difference with a normal update is that it doesn't need manual authorization for maintainer objects and that it will add a warning to your object that this is not the normal behavior... - status: attribute as described in ripe-127 fully supported - syntax check for email/domainnames/phonenumbers made stronger - perl5 patches. perl 5 is not supported yet. However, the biggest problems should be gone now. Most interesting problem was in the quad2int routine. Perl5 changed unsigned (IP numbers) int's to signed int's while we relied on having positive IP numbers. - Tony Bates <Tony.Bates(a)mci.net> recent patch for a problem with the maintainer notifications. Thanks you Tony. - many small fixes and clean up of the code to make above changes possible. - and yes the rumours that Daniel heard about a RIPE database running on a Linux machine (486-100, 12 Mb RAM, 6 hours indexing) are true ;-) So what are the OS's that we know that work with the RIPE database: - SUNOS - BSDI - Linux And that don't work: - Solaris (Please inform me with you own results so that I can update this list!) What didn't make it in this release: - Hierarchical authorization (we will first make a proposal on the database working group) - The auto nic handle generation support I have patches received from Gabor Kiss, but my part of the job is not ready yet. - Rewrite of the 'read a new object from a mail message' routine. This routine has memory size/speed problems with big objects. - Rewrite of some of the conversion routines between classless and classfull notation. There are known problems with these routines and missing parts: not all input routines as specified in ripe-121 are supported.

2 1

AS690 advisory update
by Steve Heimlich 16 Nov '95

16 Nov '95

Folks, As previously mentioned, ANS is moving to a new configuration system which will eliminate the need for registering AS690 advisories with RIPE-181 route objects. Our initial deployment described below has gone well, and as a result we will freeze our aut-num (currently still machine generated based on advisories) on Friday, 11/17, at midnight ET (Saturday, 11/18, 5am GMT). Tuesday morning's AS690 config run will use the frozen aut-num. After this time, AS690 advisories will be ignored. Policy toward routes registered in the IRR will be based solely on origin AS. The origin AS will be expanded to the set of route objects registered for that origin AS; the resulting list of prefixes will be used in generating router configurations, as today. Refinement of AS690 import policies will begin on a per AS basis next week, starting with large origin ASes. The human readable version of the 18,000 line AS690 aut-num is currently available at: ftp://ftp.ans.net/pub/info/routing-stats/aut-num-as-690 Steve -------- To: nanog(a)merit.edu Subject: AS690 policy configuration changes Date: Mon, 06 Nov 1995 18:43:22 -0500 From: Steve Heimlich <heimlich(a)kingbee.ans.net> All, Starting with Friday [11/10] morning's config run, AS690 will pick up any route listed in various routing registries, including both those routes with advisories and those routes without advisories. ANS customers will not be affected by this change. Routes without advisories will be examined for origin AS and will inherit the most popular policy currently used for that AS. For example, if a route for 147.225/16 (origin AS1660) were listed without an advisory, we would configure ourselves to listen for 147.225/16 in the same way that we listen to most other AS1660 routes (only from AS 1324 in this case). If a route is registered in an AS for which we don't have existing policy, it will not be routed. In the example above, if 147.225/16 were registered without an aggregate, and it were the only route registered with origin 1660, then we will not route it. We have a tool which flags such new ASes, and policy toward them will be created regularly. The rate of growth in number of ASes is not high, particularly relative to the rate of growth in number of routes. For now, we will continue to build our policy dynamically from the advisory attributes. Assuming that this hybrid deployment goes well, we intend to freeze our policy and convert to a system which ignores advisories altogether. With this system, the mechanics of shifting policy will be quite easy (essentially involving only ANS). I expect to announce that freeze and shift in the next week or so. At that point, those folks who want to strip AS690 advisories from any database may do so without a problem; as mentioned above, any advisories registered after that time will be ignored. Steve

4 5

Re: AS690 advisory update
by ser-rr＠ser.bbnplanet.net 14 Nov '95

14 Nov '95

What happens if policy changes for those AS'es? i.e., AS279 decides to no longer route to AS690 via AS3561, but changes to route through AS701. (*grin*) How is new policy to be determined, either for new ASes, or for existing ones that drastically change their routing policies? _k > Elliot, > > Ignore the advisory. If AS2 is the origin, we will route traffic > for that particular prefix/masklen using the most common policy > already in place for routes in AS2. > > If the common policy is for us to send traffic destined for AS2 > via our peer AS1, we will continue to do so for the new prefix/masklen. > > Steve > > > > > > After this time, AS690 advisories will be ignored. Policy toward > > > routes registered in the IRR will be based solely on origin AS. > > > The origin AS will be expanded to the set of route objects registered > > > for that origin AS; the resulting list of prefixes will be used in > > > generating router configurations, as today. > > > > in the case of AS#1 routing AS#2, suppose AS#2 sent in the route object > > and list themselves as the origin, and put AS#1 in the advisory. in the > > new scenario, will ANS now only allow routes coming via the ASN in the > > ORIGIN field? i.e. will AS#2 have to change the ANS in the origin field > > to AS#1 so ANS knows where to look for for the routes? > > > > - elliot alby/sprintlink implementation > >

2 1

Re: too many hits?
by Christian Panigl, ACOnet/UniVie +43 1 4065822-383 06 Nov '95

06 Nov '95

>So, no it's not an error or indexing problem. It is an design issue. >Changing this behavior can be done but might cause other unwanted effects >for people (or tools) that make use of this feature that look for more >objects at the same time. Dear David, if this is a design issue why doesn't give whois -h whois.ripe.net "panigl woeber" a result ? Both are valid person objects ! Or do I need a special whois client for this multi-object behaviour ? If it is a design issue (restricted by some DBM implementation) could you then please give us a hint how to specify in a whois query, that "Stefan Anders" isn't meant as multi-object but as single-object lookup (perhaps there is or could be a switch for running such a request in slow-mode without using the incomplete index) ? Daniel's suggestion "Please use handles" is nice but should we now go into querying for "SAn-RIPE" (for n=1..10000) and collect all "Stefan Anders" out of the result if we don't know the handle for a given person ? Doesn't sound very healthy ... Kind regards Christian --- Christian Panigl : Vienna University Computer Center - ACOnet --- --- VUCC - ACOnet : -------------------------------------------- --- --- Universitaetsstrasse 7 : Internet: Christian.Panigl(a)CC.UniVie.ac.at --- --- A-1010 Vienna / Austria : Tel: +43 1 4065822-383 (Fax: -170) ---

2 1

too many hits?
by Schmitz＠rus.uni-stuttgart.de 06 Nov '95

06 Nov '95

Dear all, lately I get messages from the RIPE database when querying it with whois that there are too many hits, e.g: jade$ whois -h whois.ripe.net "Stefan Anders" The index search returned too many hits. Please refine your search key. I had a look at the database and there are exactly three entries which contain the string "Stefan Anders": jade$ grep "Stefan Anders" ripe.db.pn *pn: Stefan Andersson *pn: Stefan Anders *pn: K A Stefan Andersson Does not seem to be a lot, does it? Is this an error of the database software or is it an indexing problem (there have been other problems reported on the indexing software in the last weeks...)? Regards Joachim _______________________________________________________________________________ Dr. Joachim Schmitz schmitz(a)rus.uni-stuttgart.de DFN Network Operation Center Rechenzentrum der Universitaet Stuttgart ++ 711 685 5576 voice Allmandring 30 ++ 711 678 7626 FAX D-70550 Stuttgart FRG (Germany) _______________________________________________________________________________

3 2

Re: Modification of RIPE-181's as-in/as-out attributes
by Curtis Villamizar 01 Nov '95

01 Nov '95

In message <199510311942.AA07667(a)cat.isi.edu>, Cengiz Alaettinoglu writes: > > I like this idea. There is only one problem that I see with it. The > as numbers in as-in and as-out lines are often used (by tools like > prpath and prtraceroute) to deduce the topology of the Internet. If an > AS only specifies a policy like: > > aut-num: AS2 > as-in: from (NOT AS1) 5 accept ANY > > then prpath has no way of deducing the neighbors of AS2. Doesn't that deduction belong in the inet-rtr ifaddr and peer lines? > aut-num: AS2 > neighbor-list: AS3, AS4, AS5, AS1 # pehaps with router addresses? This is reasonable for AS that don't provide inet-rtr records for their routers (I suspect most). Curtis

1 0

Draft minutes, DB-WG at RIPE #22
by Wilfried Woeber, UniVie/ACOnet 30 Oct '95

30 Oct '95

This is the draft minutes of the RIPE-DB - WG meeting. Many thanks to Hans Petter Holen for taking notes (any typos are mine :-)! Any additions, clarifications appreciated! Wilfried. ________________________________________________________________________________ Draft Minutes: Database-WG, RIPE 22, Amsterdam, NL ------------------------------------------------------ 0. Administrative stuff Hans Petter Holen, Oslonett AS, volunteered to take notes. 37 people subscribed to the circulated list of attenders. The proposed WG-agenda was accepted. 1. DB-SW review David Kessens went through the Database Development Report, covering new functionality that is either being proposed or already in test. As usaul the slides for this presentation are available at ftp://ftp.ripe.net/ripe/presentations/ripe-m22-david-DB-REPORT.ps.gz David reported that the NCC currently works towards making the RIPE-DB more reliable. On the hardware aspect the DB-machine is being fitted with a RAID system (to guard against single disk drives failures). At the same time a "shadow server" for the database is being implemented and tests have already begun. Some problems with portability and scaling of the database software have been reported recently. It was pointed out that the RIPE-NCC version of the database software is tested and supported for Perl4. There is a couple of known (minor) problems in trying to port the software to Perl5 (and to Solaris). Resolving of these problems is not the top priority, but will be tackled as soon as possible. In order to avoid the scaling problems David recommended to *not* use the -P option of netdbm and to eventually move to the Berkley db package. Tests are on-going. New functionality worth noting (for a comprehensive list please refer to the presentation slides): - Hierarchial authorisation schemes to be implemented - Referral mechanisms to be implemented, first tests with domain: objects - -t option plus -v should give more elaborate descriptive text for objects - The NOC-Object to be implemented soon, according to proposal from Havard Eidnes, as circulated shortly after RIPE-21 - "Synchronized DB" is running in test environment - There is a proposal to automate and inter-lock the assignment of RIPE-Handles. This should eventually remove the need to manually obtain unique handles (with the finger mechanism) and the potential race condition due to the delay between assignment of a handle and submitting/referencing the objects. - Inverse lookup, initially for person: objects The same functionality was requested for other object types during the discussion specifically to get better selection criteria for entries in the routing registry. While part of this functionality is available by accessing the data through wais, this was seen as not really adequate. Still this method should be improved as much as possible! - Authentication and Security This is currently under active consideration. In particular both PGP and MD5 should be available. There are both legal/logistic issues (see below) as well as software issues. In particular we have to decide on the method for registering keys and whether to use a "standard package" or to move functionality into the database software itself. During the discussion it was suggested to stick with "standard packages" because things are not yet stable. (Merit is using the "standard package" as well.) The RIPE-NCC is probably following the same path. 2. User interface(s) Encryption is probably going to be a legal problem in (at least) France. In addition to that there was a comment that part of the technology has recently been submitted for patent protection. Probably the first thing to be available shall be PGP protection for signing messages. The details to guard against snooping and re-play of updates are currently be solved. (Detailled input has been received after the WG meeting). A couple of WWW interfaces to the various databases have been made available recently. There is not yet consensus whether this is the right way to go, especially for submitting updates. The RIPE NCC thinks that the DB is not focussed toward the "end user" but towards ISPs. Other comments indicated that the WWW interface could be useful for all sorts of operational people as a well-known user interface. Both Brian Renaud <renaud@meritedu> as well as Paolo Bevilacqua <pab(a)uni.net> have recently made implementations available: - http://black.uni.net/cgi-bin/whois - http://www.ra.net/cgi-bin/ra/query-radb.pl 3. External interfaces Exchange of data with the InetNIC is still not happening. All the necessary agreements and good intentions are in place, still the InterNIC seems to regard it as a low priority issue. European ISPs want this to work really soon and regard it as *urgent*. There is not much the NCC can do right now. The different functionality of the auto-assign vs. auto-dbm mailboxes was briefly reviewed. The differences as not widely known, and the interlocks could be improved. The NCC thinks about moving towards keywords on the subject line, similar to "LONGACK". 4. Input from other WGs - MBone The expansion of the inet-rtr: object to cover multicast functionality is to be progressed now. - IPv6 There is a discussion going on how to handle and possibly abbreviate things for IPv6 (macros?). Input welcome. There was a comment that similar ideas are being (or have been) discussed in the RPS environment. 5. AOB None, thus the meeting was closed. ________________________________________________________________________________ List of new actions: David Kessens: To work with A. Blasco Bonito to improve the WAIS functionality for access to the database information on info.ripe.net. Geert-Jan de Groot: To try to follow up with the InterNIC about accepting person objects with RIPE-Handles. RIPE-NCC: To circulate a proposal how to progress the authentication (and encryption) method for the RIPE Database. RIPE-NCC: To analize the merits of implementing special keywords for the subject line of update messages, like ADD, MOD, DELETE, to possibly replace the functionality of special mailbox names (e.g. auto-assign). RIPE-NCC: To follow up on and implement the NOC-Object. WW, 27.10.95, yes I know, much too late...

1 0

Modification of RIPE-181's as-in/as-out attributes
by Steven J. Richardson 25 Oct '95

25 Oct '95

In the process of reviewing RIPE-181-represented policies, I've noticed an opportunity for what I think would be a useful modification of the as-in/as-out attributes of the aut-num object. Currently, the syntax for these attributes is given as: as-in: from <aut-num> <cost> accept <routing policy expression> as-out: to <aut-num> announce <routing policy expression> I see policies which would be usefully condensed via allowing the <aut-num> to be an AS *macro*, too. E.g.: aut-num: 99999 as-name: SOMEAS ... as-in: from AS10 100 accept ANY AND NOT {0.0.0.0/0} as-in: from AS20 100 accept ANY AND NOT {0.0.0.0/0} as-in: from AS30 100 accept ANY AND NOT {0.0.0.0/0} as-in: from AS40 100 accept ANY AND NOT {0.0.0.0/0} as-in: from AS50 100 accept ANY AND NOT {0.0.0.0/0} as-in: from AS60 100 accept ANY AND NOT {0.0.0.0/0} as-in: from AS70 100 accept ANY AND NOT {0.0.0.0/0} as-in: from AS110 150 accept ANY AND NOT {0.0.0.0/0} as-in: from AS120 150 accept ANY AND NOT {0.0.0.0/0} as-in: from AS130 150 accept ANY AND NOT {0.0.0.0/0} as-in: from AS140 150 accept ANY AND NOT {0.0.0.0/0} as-in: from AS150 150 accept ANY AND NOT {0.0.0.0/0} as-in: from AS160 150 accept ANY AND NOT {0.0.0.0/0} as-in: from AS170 150 accept ANY AND NOT {0.0.0.0/0} could be equivalent to: aut-num: 99999 ... as-in: from AS-SOMEAS-100-NO-DEFAULT 100 accept ANY AND NOT {0.0.0.0/0} as-in: from AS-SOMEAS-150-NO-DEFAULT 150 accept ANY AND NOT {0.0.0.0/0} with the macro definitions: as-macro: AS-SOMEAS-100-NO-DEFAULT descr: ASs which AS-99999 accepts at pref. 100 (any but descr: the default route) as-list: AS110 AS120 AS130 AS140 AS150 AS160 AS170 ... as-macro: AS-SOMEAS-150-NO-DEFAULT descr: ASs which AS-99999 accepts at pref. 150 (any but descr: the default route) as-list: AS10 AS20 AS30 AS40 AS50 AS60 AS70 ... (The same could be said of as-out lines.) What do you think? Steve Richardson/Merit

2 2

Re: Proposal on applying advisory attribute to "aut-num" object
by Christian Panigl, ACOnet/UniVie +43 1 4065822-383 24 Oct '95

24 Oct '95

>Date: Mon, 23 Oct 1995 15:19:25 -0400 >From: "Steven J. Richardson" <sjr(a)merit.edu> > > I think that this idea, while good, may be too restrictive unless > coupled with the ability to override this "global" advisory by > setting the "advisory" attribute of a specific prefix which originates > within the AS. Steve, I fully agree and I did mean and say this but didn't explicitely write it down in my proposal :-( Unfortunately the wording in RIPE-131 isn't that explicit either, because it was written before your comment has arrived (sometimes the RIPE-NCC is really too fast ;-) >Date: Tue, 24 Oct 1995 10:44:42 +0100 >From: Daniel Karrenberg <Daniel.Karrenberg(a)ripe.net> > >To sum up: > >ANS is not going to use advisories in aut-num since they will do away with >advisories in at most two weeks. > >The advisory attribute will stay in aut-num objects and we all hope noone >is going to use them again, ever. Daniel and David, is it worth the effort changing the one RIPE-131 paragraph to: The advisory attribute of a route object applies to the specific route. The advisory attribute of an aut-num object is intended to apply as default to all routes originated by the autonomous system in question providing a shorthand notation if the same advisory applies to most or all such routes. If both are present the advisory attribute of a route object takes precedence over the advisory attribute of the aut-num object. As with all advisories the specific semantics are defined by the 'target' AS. My feeling is, if you decided to keep it, it should be properly documented. Sorry for my incomplete proposal ! Regards Christian

2 1

Re: Proposal on applying advisory attribute to "aut-num" object
by zsako＠banknet.net 24 Oct '95

24 Oct '95

> From owner-db-wg(a)ripe.net Fri Oct 20 21:22:16 1995 Christian, > The famous "advisory" attribute which seems to be still needed by ANS to > get their routing done is especially cumbersome because it has to be > applied to and maintained for every single "route" object. If the > "advisory" attribute could be added to the "aut-num" object, entering an > "advisory" there could cover all routes originated by this AS. Of > course the ANS people will have to slightly modify their software. As far as I see David Kessens has already made the necessary changes in the DB software. :) zsako/banknet $ whois -h whois.ripe.net "-t aut-num" aut-num: [mandatory] [single] as-name: [optional] [single] descr: [mandatory] [multiple] as-in: [optional] [multiple] as-out: [optional] [multiple] advisory: [optional] [single] <<<<<<---------- interas-in: [optional] [multiple] interas-out: [optional] [multiple] as-exclude: [optional] [multiple] default: [optional] [multiple] guardian: [optional] [single] admin-c: [mandatory] [multiple] tech-c: [mandatory] [multiple] remarks: [optional] [multiple] notify: [optional] [multiple] mnt-by: [mandatory] [multiple] changed: [mandatory] [multiple] source: [mandatory] [single] > > Comments welcome ! I would like to make some comments on the above. First of all, with respect to the `[single]' qualifier. If we indeed allow only one such advisory attribute for the AS (aut-num), then the AS can express its advisory recommendations to only one other AS for ALL of it routes. I know that this is somewhat theoretical, since only ANS use the advisory... Nevertheless ripe-130 says it could be used by any other organisation, although *everybody* is discouraged from using it at all. An other approach to this problem would not need any change in the DB schema. We have the `remarks' attribute which can be used for any additional information related to the AS. I think it could also contain something like: "advisory: AS690 1:1800 2:1133 3:1239" which means, the aut-num would have the following remarks attribute: remarks: advisory: AS690 1:1800 2:1133 3:1239 In this case any AS could add as many remarks as needed for the advisories... This is true for the `route' object as well. I know it is not a good practice to use the attributes for other purpose than they are designed for, but in this case I feel the advisory is not more than a remark (actually an important one if you want to have NSFnet connectivity...). Two other arguments are in favour of this second solution: first is that RIPE descourages people from using the advisory, second is that ANS should be ready with the new software soon, and then nobody would (or at least should) use the advisory any more. As you said, ANS have to make some (probably minor) changes in their software in order to get the advisory from the aut-num for all the routes originating in the AS corresponding to the aut-num. I do not think these changes are significantly less in the case there is an `advisory' attribute in the aut-num object, than in the case they have to parse the `remarks' attributes of the aut-num. Further comments welcome! Best regards, Janos Janos Zsako zsako(a)banknet.net BankNet Tel: +36 1 160 16 42 Fax: +36 1 160 14 06

6 5

Re: Proposal on applying advisory attribute to "aut-num" object
by Steven J. Richardson 23 Oct '95

23 Oct '95

Christian: I think that this idea, while good, may be too restrictive unless coupled with the ability to override this "global" advisory by setting the "advisory" attribute of a specific prefix which originates within the AS. Steve Richardson/Merit >From owner-db-wg(a)ripe.net Fri Oct 20 16:13:34 1995 >Date: Fri, 20 Oct 1995 21:08:19 MET >From: "Christian Panigl, ACOnet/UniVie +43 1 4065822-383" > <panigl(a)cc.univie.ac.at> >To: db-wg(a)ripe.net >Cc: domain-admin(a)cc.univie.ac.at >Message-Id: <009982B8.A55165BA.3(a)cc.univie.ac.at> >Subject: Proposal on applying advisory attribute to "aut-num" object >Status: R > > Dear colleagues, > > at RIPE22 I made the following proposal which I would like to be built > into the RIPE-DB and other routing registry databases: > > The famous "advisory" attribute which seems to be still needed by ANS to > get their routing done is especially cumbersome because it has to be > applied to and maintained for every single "route" object. If the > "advisory" attribute could be added to the "aut-num" object, entering an > "advisory" there could cover all routes originated by this AS. Of > course the ANS people will have to slightly modify their software. > > Example: > >aut-num: AS760 >descr: University of Vienna, Austria >descr: AT >as-in: from AS679 100 accept AS679 >as-in: from AS1115 100 accept AS1115 >as-in: from AS1776 100 accept AS1776 AS1117 >as-in: from AS1853 100 accept ANY >as-in: from AS2494 100 accept AS2494 >as-out: to AS1853 announce AS-UDNVIE >as-out: to AS679 announce ANY >as-out: to AS1115 announce ANY >as-out: to AS1776 announce ANY >as-out: to AS2494 announce ANY >default: AS1853 100 >advisory: AS690 1:1800 2:1133 3:1239 <<<<<<<<<<<<<<< >guardian: domain-admin(a)univie.ac.at >admin-c: HS118 >tech-c: EJ63 >tech-c: FK17-RIPE >mnt-by: AS760-MNT >changed: panigl(a)univie.ac.at 951020 >source: RIPE > > Comments welcome ! > > Regards > Christian > > --- Christian Panigl : Vienna University Computer Center - ACOnet --- > --- VUCC - ACOnet : -------------------------------------------- --- > --- Universitaetsstrasse 7 : Internet: Christian.Panigl(a)CC.UniVie.ac.at --- > --- A-1010 Vienna / Austria : Tel: +43 1 4065822-383 (Fax: -170) ---

1 0

Re: Proposal on applying advisory attribute to "aut-num" object
by Wilfried Woeber, UniVie/ACOnet 23 Oct '95

23 Oct '95

>An other approach to this problem would not need any change in the DB schema. >We have the `remarks' attribute which can be used for any additional information >related to the AS. I think it could also contain something like: >"advisory: AS690 1:1800 2:1133 3:1239" which means, the aut-num would have >the following remarks attribute: >remarks: advisory: AS690 1:1800 2:1133 3:1239 >In this case any AS could add as many remarks as needed for the advisories... I think (mis-)using the remark: is a bad idea. It is already being used to e.g. describe DMZ configurations (ias-int:). It leaves too many things to bi-lateral agreements and there is just marginal syntax checking for the remark: attribute. A poor environment to base configuration decisions on.... But it might be appropriate to think about the advisory: as a remark, this might eventually discourage the use of it :-) Wilfried. -------------------------------------------------------------------------- Wilfried Woeber : e-mail: Woeber(a)CC.UniVie.ac.at Computer Center - ACOnet : Vienna University : Tel: +43 1 4065822 355 Universitaetsstrasse 7 : Fax: +43 1 4065822 170 A-1010 Vienna, Austria, Europe : NIC: WW144 --------------------------------------------------------------------------

1 0

Proposal on applying advisory attribute to "aut-num" object
by Christian Panigl, ACOnet/UniVie +43 1 4065822-383 20 Oct '95

20 Oct '95

Dear colleagues, at RIPE22 I made the following proposal which I would like to be built into the RIPE-DB and other routing registry databases: The famous "advisory" attribute which seems to be still needed by ANS to get their routing done is especially cumbersome because it has to be applied to and maintained for every single "route" object. If the "advisory" attribute could be added to the "aut-num" object, entering an "advisory" there could cover all routes originated by this AS. Of course the ANS people will have to slightly modify their software. Example: aut-num: AS760 descr: University of Vienna, Austria descr: AT as-in: from AS679 100 accept AS679 as-in: from AS1115 100 accept AS1115 as-in: from AS1776 100 accept AS1776 AS1117 as-in: from AS1853 100 accept ANY as-in: from AS2494 100 accept AS2494 as-out: to AS1853 announce AS-UDNVIE as-out: to AS679 announce ANY as-out: to AS1115 announce ANY as-out: to AS1776 announce ANY as-out: to AS2494 announce ANY default: AS1853 100 advisory: AS690 1:1800 2:1133 3:1239 <<<<<<<<<<<<<<< guardian: domain-admin(a)univie.ac.at admin-c: HS118 tech-c: EJ63 tech-c: FK17-RIPE mnt-by: AS760-MNT changed: panigl(a)univie.ac.at 951020 source: RIPE Comments welcome ! Regards Christian --- Christian Panigl : Vienna University Computer Center - ACOnet --- --- VUCC - ACOnet : -------------------------------------------- --- --- Universitaetsstrasse 7 : Internet: Christian.Panigl(a)CC.UniVie.ac.at --- --- A-1010 Vienna / Austria : Tel: +43 1 4065822-383 (Fax: -170) ---

1 0

Re: db under solaris
by Jose Sanchez-Seco. CSIC RedIRIS 19 Oct '95

19 Oct '95

Hi David, I use perl4 (GNU FSFperl package) on Solaris 2.4 and I have changed all the SOCK_STREAM's, but what's about the flock() function?? This function is available only on SunOS and BSD-style machines. At this moment, I am trying to emulate this function whith calls to fcntl(). Also, I have try to compile Perl4 whit /usr/ucblib/libucb but this an impossible task. I have read in the Perl4 FAQ's that it is better to forget about BSDism's like that :-(. If anyone know more about this matter, I will be happy to hear him. Regards, Jose Sanchez-Seco. On Oct 12, 18:12, RIPE Database Manager wrote: > Subject: Re: db under solaris > > Hi Tony, > > If you use perl4 and change the SOCK_STREAM variable to 2 instead of 1 > it should work. This value is used and hardcoded more then once in the > code. In the next distribution this will be handled from the Makefile but > that doesn't help you now ... > > Kind regards, > > David Kessens > RIPE NCC Database maintainer > -------- > > > > > tonyb <tonyb(a)pipex.net> writes: > * Hi, has anyone managed to tweak the perl whois server to run under > * Solaris ? Is it an easy fix ? > * > * Thanks > * > * > * ____ > * / \/ > * /<>/\// > * Tony Barber Phone : +44(0)1223 250122 > * Technical Support Email : support(a)pipex.net > * > * > * >-- End of excerpt from RIPE Database Manager -- __________________________ __ ________________________________________ /_/ Jose Sanchez-Seco __ __ Email: jose.sanchez(a)rediris.es RedIRIS/CSIC /_/ RedIRIS /_/ Tel: + 34 1 5854970 Serrano 142 __ Fax: + 34 1 5855146 E-28006 Madrid /_/ Centro de Gestion de RED de REDIRIS _____________ Spanish Academic & Research Network ___________________________

3 2

New RA Tools Announcement
by Brian Renaud 18 Oct '95

18 Oct '95

Here is some additional location information for a number of the tools I discussed at the last meeting. -Brian ------- Forwarded Message Date: Wed, 18 Oct 1995 13:34:21 -0400 From: labovit(a)merit.edu To: nanog(a)merit.edu Subject: New RA Tools Announcement New Routing Arbiter Tools Announce ---------------------------------- The Routing Arbiter welcomes comments, bug-reports and suggestions for new tools. Please direct email to ra-team(a)ra.net. Please feel free to redistribute this announcement. A web version of this page lives at http://www.ra.net/~ra/tools ------------------------ Online Tools and Reports ------------------------ IRRWeb This graphical interface into the Internet Routing Registry makes it possible to use the Web to query the IRR and update RADB AS objects, Route objects, and Maintainer objects. Users can enter any value that can be submitted through a whois query, such as an AS number, network IP address, or maintainer. IRRWeb then displays the corresponding AS objects, Route objects, or Maintainer objects from the various registries in the IRR. Authorized maintainers can edit the objects directly; IRRWeb performs a cursory pre-check and mails the revised object to auto-dbm(a)ra.net. The user then receives e-mail from auto-dbm confirming and displaying the revised object, or explaining why the object was rejected. See http://www.ra.net/cgi-bin/ra/query-radb.pl Source code is available at ftp://ftp.ra.net/routing.arbiter/tools/irrweb.tar.gz Daily NAP Route Flap Reports</A> This new tool set generates daily reports of route flaps (link failures at regular and short intervals) throughout the Internet. Modeled after the reports originally produced by Curtis Villamizar of ANS, the new reports are generated using tools packaged with Merit's Multi-Threaded Routing Toolkit. The data is obtained from peering sessions with Route Servers at the interconnection points. The reports note the last state of the route (up or down), the length of time that a route existed (or did not exist) for that prefix, and the number of times a route for the prefix transitioned from down to up, up to down, or was replaced by a new route with changed attribute information. AS-path-specific information is also provided for every path announced for the prefix. See http://www.ra.net/~ra/tools/flap.html Route History Server The Route History Server provides a mechanism for tracking the announce/withdraw history of a given prefix for the last 24 hours. The History Server peers with the route servers at each NAP and records all BGP updates in History Server/Route Server peering session. See http://www.ra.net/cgi-bin/ra/rshist.pl ----------------------- Tools Available for FTP ----------------------- RSd The Route Server daemon (RSd) is an enhanced version of the GateD routing software that provides multiples views of routing information. The software provides a mechanism for network service provides to off-load the computational complexity of routing policy calculations from their routers. RSd supports configuration and transparent passing of BGP MEDs. The software also supports BGP route flap dampening. Available at ftp://ftp.ra.net/routing.arbiter/tools/rsd.tar.gz Peval A policy evaluator that inputs a RIPE-181 policy expression, performs essential background calculations such as symbolic evaluations and expansions, and outputs another RIPE-181 policy expression that is used by other tools, such as RTConfig. Available as part of the RAToolSet at ftp://ftp.ra.net/routing.arbiter/tools/RAToolSet RTConfig A router configuration tool that can be used by providers to generate router configs directly from the RADB or other IRR registries. Currently in production use for the RA Route Servers, ANSNET, and CA*net, RTConfig is a front-end tool that uses peval and radbserver transparently to users. Available as part of the RAToolSet at ftp://ftp.ra.net/routing.arbiter/tools/RAToolSet rrc2r/rrmerge This Cisco-to-RIPE-181 conversion package makes it possible for users to convert Cisco router configuration files to RIPE-181 objects that can be submitted to the Internet Routing Registry (IRR). The Cisco access-list can be converted into an explicit set of nets embedded in an AS object or represented as a community. The RADBserver is queried for any missing or previously registered information. Available at ftp://ftp.ra.net/routing.arbiter/tools/RAToolSet/rrc2r-0.2.tar.gz CiscoBGP IRR users have long recognized the need for tools that check the IRR against routes actually propagated in the Internet. CiscoBGP obtains and analyzes routing information from production Ciscos, and compares the data with routes in the IRR. The software also flags prefixes that are reserved by RFC 1597, Address Allocation for Private Internets. Available as part of the MRT software distribution at http://www.merit.edu/~mrt BGPCheck BGPCheck obtains and analyzes routing information from BGP4 peering sessions, and compares the data with routes in the IRR. The software also flags prefixes that are reserved by RFC 1597, <em>Address Allocation for Private Internets</em>. Available as part of the MRT software distribution at http://www.merit.edu/~mrt PRtraceroute The 'prtraceroute' tool is a powerful form of traceroute that displays the Autonomous Systems that a packet traverses. PRtraceroute was developed by the Pride project. A version of prtraceroute that queries the RADB is available at ftp://ftp.ra.net/routing.arbiter/pride/prtraceroute-2.0beta2.shar.gz ------------------ Tool Announcements ------------------ PGP-Based Radb Authentication Follow these steps to take advantage of the new RADB support for PGP-based digital signatures: 1. Register your public key with the Routing Arbiter Service. 2. Modify your Maintainer object to reflect your use of digital signatures. 3. Use PGP to sign your RADB transactions. For detailed instructions, see: http://www.ra.net/routing.arbiter/RA/RADB.tools.docs/pgp.html -- Craig Labovitz labovit(a)merit.edu Merit Network, Inc. 4251 Plymouth Road, Suite C. (313) 764-0252 (office) Ann Arbor, MI 48105 (313) 747-3745 (fax) ------- End of Forwarded Message

1 0

Re: db under solaris
by RIPE Database Manager 18 Oct '95

18 Oct '95

Dear All, First of all: thanks for all your reports! I am not sure what to believe now ... I did some further research. I got a report from Chua Koon Teck at 20 Apr 1995 that it was possible to run at least the whois daemon on Solaris 2.4 with perl5 (yes!): > Anyway, I am using perl5.001 and it seem to be fine so far. But you will > need to edit the defines.pl and defaults.pl file under the lib > directory. The newer version of perl require a backslash before the @ > symbol. So Tony please also look at the defines.pl and defaults.pl files for the @ signs (will of course be changed in the next distribution). If you still don't succeed I am happy to help you further but then I need some more details about error messages and of course I want to hear from Chua Koon Tek about the current state of their database. Kind regards, David Kessens RIPE NCC Database maintainer PS I don't think the db-wg is the platform for this kind of implementation detail questions. Let we first try to find out what happened and send a report to the db-wg when (un)successfull! -------- tonyb <tonyb(a)pipex.net> writes: * RIPE Database Manager wrote: * > * > * >Hi Tony, * > * >If you use perl4 and change the SOCK_STREAM variable to 2 instead of 1 * >it should work. This value is used and hardcoded more then once in the * >code. In the next distribution this will be handled from the Makefile but * >that doesn't help you now ... * > * Hi David, thanks for the reply, I had managed to find the cause of that * one. Unfortunately as guy davies has now confirmed the dbdoesn't work on * solaris :-( * * We will have to wait for the next version. Any idea of the expected date * or release ? * * Thansk * ____ * / \/ * /<>/\// * Tony Barber Phone : +44(0)1223 250122 * Technical Support Email : support(a)pipex.net * *

1 0

Server updates for WWWhois
by Paolo Bevilacqua 16 Oct '95

16 Oct '95

Hello, As requested at the last WG meeting, i'm going to complete the list of the whois servers supported by the Web interface that is available at: http://black.uni.net/cgi-bin/whois After this step you're welcome to install this script at your site. Please mail me about the known servers and the associated email address for updates.

1 0