- db-wg - mailman.ripe.net

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 26 Oct '95

26 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 24 Oct '95

24 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 21 Oct '95

21 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 20 Oct '95

20 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 19 Oct '95

19 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