- lir-wg - mailman.ripe.net

Re: in-addr checking tools
by Geert Jan de Groot 05 May '95

05 May '95

Hi, This is in response to the request from the local-ir working group to investigate the possibility if the hostcount tools can be used to list problems in the in-addr domain. I hacked the hostcount tools to produce the same type of errorlist as made available each month as part of the hostcount results. I made sample results available; I don't think this is very usable. For the sample data and an evaluation, please refer to ftp.ripe.net:ripe/local-ir/inaddrcount. As a (IMHO) better proposal, I also made available the scripts I use to keep an eye on things; these can be found at ftp.ripe.net:ripe/local-ir/zonecheck, including sample output. I leave it up to the local-ir WG meeting in Rome to decide if the action-point is completed, or what should be done next. C u in Rome, Geert Jan

2 1

Actions RIPE20 meeting
by RIPE NCC Staff 03 May '95

03 May '95

List of Closed Action Items Action: 19.7 NCC To circulate the revised ripe-115 to the local-ir list for comments. Action: 20.1 Mike Norris To flag those countries wo could do their own hostcounting to the NCC. Action: 20.4 Mike Norris To send mail to the list asking for input on the content of the training material. Action: 20.7 Mike Norris To circulate to the local-ir(a)ripe.net mailing list a summary of the meeting between the Regional Registries. Action: 20.12 Havard Eidnes To publish the tool to check a primary zone file against registered domain objects, for the benefit of other top level registrars. Action: 20.16 Marten Terpstra To forward the new NACR procedure to the routing-wg mailing list List of Open Action Items Action: 17.7 Wilfried Woeber, NCC To produce the necessary documentation for the new DB software. Action: 19.6 Geert Jan de Groot To document new attribute "status" proposed to describe whether a network is delegated, reserved or assigned. Action: 19.10 Erik Jan Bos, Wilfried Woeber Written proposal to extend the "inet-rtr" object ready before RIPE 20. Action: 19.11 NCC To propose new domain object for in-addr.arpa Action: 19.12 Marten Terpstra (to be taken over by NCC) To write up the proposed "stored"/"processed" attribute. Action: 19.14 Erik-Jan Bos To write a short document describing how to use the rtr-obj to describe location of m-routers. Action: 20.2 Rob Blokzijl To bring up the CERT issue during the next TERENA Contributors Committee meeting Action: 20.3 Rob Blokzijl To start discussion on the IPv6 working group Action: 20.5 Daniel Karrenberg To draft outline "applciations document" to support the proposed plan on how to deal with address space requests from VSE's Action: 20.6 Mike Norris To recirculate to the local-ir(a)ripe.net mailing list the document on VSE's as drafted by Daniel Karrenberg. Action: 20.8 Geert Jan de Groot To summarise the RIPE handle tool and to distribute to the local-ir(a)ripe.net mailing list. Action: 20.9 RIPE NCC To do an implementation analysis on inverse lookups in the RIPE database. Action: 20.10 Havard Eidnes To write up a proposal with input from the Local-IR WG and the EOF (European Operators Forum) Action: 20.11 RIPE NCC To investigate (as time permits) distribution of the domain information in the RIPE database and to investigate a "private" approach for referrals. Action: 20.13 Milan Sterba To periodically send out a call to RIPE NCC contributors to publish in the Connectivity Document Store. Action: 20.14 Milan Starba To update the Connectivity Document Store home page Action: 20.15 Milan Starba To produce a metrics sheet for the Connectivity Document Store Action: 20.17 Merit To announce on the routing-wg mailing list when NACRs will stop being accepted Action: 20.18 RIPE NCC To compare the AS690 routing information for European routes as stored in the Merit RADB with the information on the RIPE DB and report on mismatches Action: 20.19 RIPE NCC To preload the advisory attribute from information in the Merit RADB shortly before Merit retires the PRDB. Action: 20.20 Merit To keep the RIPE community up-to-date on the transition process through the routing-wg mailing list. Action: 20.21 Herman van Dompseler To produce (and maintain) an European Mbone map. Action: 20.22 Francis Dupont To send a pointer to PIM for BSD 4.4 as soon as it is available. Action: 20.23 Nandor Horvath To inform the NIDUS working group about the decision that it had been disbanded. Action: 20.24 Daniele Bovio To set up the matrix to keep track of the RIPE meeting actions.

1 0

Re: Minutes from Danvers
by Mike Norris 02 May '95

02 May '95

Of interest to the Local IR group is the last paragraph, about RFCs 1597 and 1627. Cheers. Mike ------- Forwarded Message Return-Path: owner-eot(a)ebone.net Received: by sunic.sunet.se (8.6.8/2.03) id LAA10188; Tue, 2 May 1995 11:11:25 GMT Received: from nico.aarnet.edu.au by sunic.sunet.se (8.6.8/2.03) id NAA10178; Tue, 2 May 1995 13:11:18 +0200 Received: from greatdane.cisco.com ([171.69.1.141]) by nico.aarnet.edu.au (8.6.10/8.6.10) with SMTP id TAA15741 for <cidrd(a)iepg.org>; Tue, 2 May 1995 19:16:07 +1000 Received: (tli@localhost) by greatdane.cisco.com (8.6.8+c/8.6.5) id CAA26024; Tue, 2 May 1995 02:15:08 -0700 Date: Tue, 2 May 1995 02:15:08 -0700 From: Tony Li <tli(a)cisco.com> Message-Id: <199505020915.CAA26024(a)greatdane.cisco.com> To: cidrd(a)iepg.org Subject: Minutes from Danvers CIDRD Minutes Address Space Growth Report The usual report on the usage of the IPv4 address space was presented. A revised estimate of 2018 +/- 8 years was given. The cause for the recent decrease in the slope of the curve was discussed, but no firm conclusion was reached. Routing Table Size As of Danvers, 25452 routes are present in the backbone routing tables. CIDR routes have increased dramatically in the last year. (113 -> 2215, Seattle to Danvers). ASs doing CIDR have also increased dramatically. (35 - -> 289) More than 1/2 (56%) of the ASs are announcing CIDRerized routes, but there are also a high number (134 of 2215) are only annoucing only one route. Tony Bates has a report he used to produce that would show who has not CIDRiszed which should continue to be posted. It appears that the total number of routes is flattening out. It was noted that flaps are an ongoing, serious problem and that the flap rate of a prefix is proportional to the length of the prefix. CIDR has had a significant impact on the number of theoretical hosts/route. The effect also is different among the various blocks. There is even an effect in 192. Class-A Allocation The IANA has not yet released any Class A networks to be allocated. The working group would like to survey of the Class As to see which ones are actually in use and are globally routed and which are unused. There is also a need to provide a guideline document to IANA for the allocation of As. Scott said that IESG has discussed this, but it looking for a document that helps define the situation and the potential impact of using Class As. There has been a suggestion that a class A be leased to someone to do evaluations. Geoff Huston has an extensive note on the topic in the IEPG archives and Bill Manning will work on helping to document the IANA guideline. Why do this at all? Class A is the last 25% percent of the address space available. There is not a specific desire to allocate this space, but there is a desire to be sure it is possible before it is actually done. Matt Mattis suggests that each provider get a subnet out of a particular A and see if they can communicate with each other. There are also reverse lookup DNS issues. As of this writing, an experiment has already been undertaken to test routing of subnets of a Class A network. Address Ownership Yakov Rekhter gave a presentation on the effects of address ownership on the scalability of Internet routing. This talk concluded that address ownership is impractical if we intend to continue to use hierarchical routing within the Internet. This talk is to become an RFC under the CIDRD WG. There is consensus that renumbering is something that should be promoted. A proposal has been made to create a document that will advocate that providers filter out prefixes of a certain size. What does that mean for multi-homed networks? Yakov will create this document. There is also an idea that settlements should be based on number of routes or unaggregated routes. Progressing RFC 1597 to Proposed Standard There has been a suggestion that RFC1597 be moved to Proposed Standard. Revisions are necessary to incorporate the comments from RFC 1627 and to make the text classless. The authors of the respective RFCs have agreed to collaborate to produce the synthesized document. ------- End of Forwarded Message

1 0

NACRs are no more, RIPE RR is going to be sufficient
by Daniel Karrenberg 02 May '95

02 May '95

I forward these messages for the benefit of European operators not on the NANOG list. The upshot of this is that registration in the RIPE Routing Registry will be sufficient to get ANS routing configured correctly in the near future. (Of course you will need a transit agreement with someone who does if you do not peer with ANS directly). Daniel ------- Forwarded Messages Date: Mon, 1 May 1995 20:20:22 -0400 From: "Dale S. Johnson" <dsj(a)merit.edu> To: nanog(a)home.merit.edu Subject: PRDB Retirement next Monday, May 8 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 ------- Message 2 Date: Tue, 02 May 1995 00:05:14 -0400 From: Steve Heimlich <heimlich(a)ans.net> To: nanog(a)merit.edu Subject: PRDB retirement (and note about AS690 advisories) Folks, Thanks to Dale for the initial update. Let me add a further note on our transition of AS690 from NSFnet routing policy toward ANS routing policy... Shortly beyond retirement of the PRDB, ANS will halt our use of AS690 advisories. We hope to do this soon after retiring the PRDB, using a tool which converts existing announcements into policy expressable using "pure" RIPE-181; this resulting aut-num object will work with various standard RIPE/PRIDE tools. After that, we'll be culling our very large aut-num object into something smaller which is uses AS-based policy as much as possible, with a minimum of prefix-based exceptions. New registered prefixes will assume the current majority policy toward the home AS in which they're registered. The size of the aut-num object right now comes from handling the large number of exceptions for prefixes originating within a given AS (which we're using so that we disturb actual routing as little as possible initially). The configuration of metric:as lists has been a challenge to manage to say the least, particularly through the transition. As they are obviously burdensome for ANS as well, we have a mutual interest in witnessing their retirement, and we're working to do this as quickly as possible. In addition, info in the RADB which has as its source "PRDB" can be ignored on a per-provider basis, so that eventually the PRDB-derived info can go away entirely. So, if provider X tells us to prefer source:X over source:PRDB, we can work out migration details so the old PRDB info can be knocked out in one action, replaced by the preferrable RIPE-181 source. Steve - --------------- Dale's original follows ---------------- 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 ------- End of Forwarded Messages

1 0

Draft agenda for local IR mtg
by mnorris＠dalkey.hea.ie 29 Apr '95

29 Apr '95

Please see the following draft agenda for the meeting of the RIPE Local IR working group in Rome on 8th May 1995. I'd be glad to have your comments and suggested changes, if possible before Friday 5th May. Cheers. Mike Norris D R A F T A G E N D A 1. Select scribe 2. Agree agenda 3. Minutes of meeting at RIPE 20 4. Actions outstanding 5. Reports from registries - local registries - RIPE NCC - global coordination 6. Charging for services - report of position for 1995 - billing procedures - model for future years - ticketing system 7. Training of (new) registries 8. Tools 9. Other - ripe-104 - database issues - reverse domains 10. AOB Mike Norris 29th April 1995

1 0

Regional registries, report of meeting
by mnorris＠dalkey.hea.ie 29 Apr '95

29 Apr '95

Report on Meeting of Regional Registries Amsterdam, 27th January 1995 The meeting was convened on the initiative of the RIPE NCC and took place immediately after RIPE 20. The attenders were: David Conrad AP regional registry Elise Gerich MERIT Geert-Jan de Groot RIPE NCC Kim Hubbard InterNIC Daniel Karrenberg RIPE NCC Mark Kosters InterNIC Mike Norris RIPE In discussion, the following points were agreed: * There was need to exchange information about applications for IP address space and AS numbers. Regional registries would share such information, especially concerning applications for large amounts of resource. * The assign-review(a)ripe.net list would be used to discuss queries about assignment of address space. * Charging for address space should be broadly similar between regional registries. * Charging for name space would be considered in the light of any InterNIC decision thereon. * The regional registries would meet regularly and would also arrange collectively to meet Jon Postel. Mike Norris April 1995

1 0

RIPE21: Meeting announcement (REMINDER)
by RIPE NCC Staff 26 Apr '95

26 Apr '95

* * REMINDER * * REMINDER * * REMINDER * * REMINDER * * REMINDER * * Dear All, This message is to announce the 21th RIPE meeting in Rome. We would like to encourage everybody and especially our new contributors to come to the 21th RIPE meeting. The meeting is hosted and organised by GARR/CNR. Antonio Blasco Bonito is the organiser with help from colleagues at CNR. If you are planning to attend the coming RIPE meeting, please help us by registering for the meeting as soon as possible. This really helps in planning enough food, coffee and seats for everyone ie. if you want to get your Italian lunch (without milk ;-)) register now! Don't forget to book your hotel as long as possible in advance. May is an extremely busy conference month in Rome. Information about hotels and the meeting venue are available at the www site of CNR and the RIPE NCC ftp server. A draft agenda and an announcement about the traditional RIPE Meeting Evening Dinner has been sent out seperately and is available at the RIPE NCC ftp server. Kind regards, David Kessens RIPE NCC --------------------------------------------------------------------------- R I P E meeting announcement ============================ (This announcement can also be viewed using "finger meeting(a)ncc.ripe.net") This is to announce that the 21th RIPE meeting will take place: Dates: 8th May, 1995 begin: 09:00 9th May, 1995 10th May, 1995 end: 16:00 The Working Group and special interest group sessions will be scheduled for May 8 (full day) and May 9 (09:00-12:30). The plenary RIPE meeting will take place at May 9 (14:00-18:00) and May 10 (09:00-16:00). Venue: Consiglio Nazionale delle Ricerche P.le Aldo Moro, 7 (Old name: P. delle Scienze) I-00185 Roma Host: GARR/CNR Registration: Please use the registration form to give notice of your coming as soon as possible. The Registration form can be obtained from: ftp://ftp.ripe.net/ripe/Next-Meeting/ripe21.registration Agenda: The draft agenda will be published 2 weeks before the meeting starts. It will be available at: ftp://ftp.ripe.net/ripe/Next-Meeting/ripe21.draft.agenda General Information: -------------------- Currency information (950329): 1 ECU = L 2246,- 1 US$ = L 1700,- 1 DFL = L 1100,- 1 UK# = L 2742,- All information about the RIPE meeting can be obtained from: http://www.iasi.rm.cnr.it/ripe/ripe.html OR ftp://ftp.ripe.net/ripe/Next-Meeting/ The README file in this directory contains a short description about the files available in the ftp directory, the CHANGES file contains information about (important) updates of the general information regarding the meeting: ftp://ftp.ripe.net/ripe/Next-Meeting/README ftp://ftp.ripe.net/ripe/Next-Meeting/CHANGES Maps of Roma: http://www.iasi.rm.cnr.it/ripe/romemap.html http://www.iasi.rm.cnr.it/ripe/hotelmap.html OR ftp://ftp.ripe.net/ripe/Next-Meeting/ripe21.map.rome.ps ftp://ftp.ripe.net/ripe/Next-Meeting/ripe21.map.termini.ps How do I get there: ------------------- From the airport Fiumicino/Leonardo da Vinci: Take the direct non-stop train from the airport to Stazione di Termini. The train costs L 13,000 and will bring you within 30 minutes at the station. Trains depart about every 30 minutes but they might have some delays! On departure from Roma to the airport, get your train tickets from a special ticket office along platform 22. Taxis from the airport to the station (45 minutes) cost about L 60,000. The meeting site and hotels are all close to Stazione di Termini. Details of the hotels (less then 15 minute walk) to the meeting venue can be obtained from: http://www.iasi.rm.cnr.it/ripe/hotellist.html OR ftp://ftp.ripe.net/ripe/Next-Meeting/ripe21.hotels Check the following map how to get from the station to the venue/your hotel: http://www.iasi.rm.cnr.it/ripe/hotelmap.html OR ftp://ftp.ripe.net/ripe/Next-Meeting/ripe21.map.termini.ps Public Transport: ----------------- You can buy your bus/metro/train tickets from the automatic ticket machines *before* entering the bus/metro/train. One can pay with coins or bills. Bus/metro tickets cost L 1500,-. It might be easier to walk from most hotels to the venue. All recommended hotels are within a 15 minute walk distance to the venue. Taxis from the hotels to the meeting venue should cost about L 10,000,- depending in which hotel you stay. Tourist and other information about Roma is available from: ----------------------------------------------------------- http://campidoglio.caspur.it/ The text is in Italian but there are many pictures available which give a good impression of Roma. There will also be a document in the document store with some information about the more important touristic sites/museums in Roma: ftp://ftp.ripe.net/ripe/Next-Meeting/ripe21.tourist.info

1 0

RIPE21: Dinner announcement
by RIPE NCC Staff 26 Apr '95

26 Apr '95

* * ANNOUNCEMENT * * ANNOUNCEMENT * * ANNOUNCEMENT * * ANNOUNCEMENT * * 21th RIPE Meeting Dinner Date: Tuesday, May 9 1995 Venue: Cavallino Bianco Via E. Filiberto, 23 Roma (See map: 300m near IASI, in the Vittorio Emanuele's Place direction) Time: 20:00 Last date for reservations: Saturday, April 29 1995 The RIPE Evening Dinner will be held in restaurant "Cavallino Bianco". If you want to attend this dinner, please could you complete the http form at the following location before April 29: http://www.iasi.rm.cnr.it/ripe/party.html (Note: no special automagic RIPE forms this time ;-)) Please note that it will NOT be possible to attend the dinner without first making a reservation. If you would like to bring a guest with you, they are very welcome, but please complete a separate form for them. See you at the dinner, David Kessens RIPE NCC ------------- You can make your choice from three different menus: Fish dishes (price Lit. 50000, all-inclusive): Cocktail Insalata di mare Risotto alla pescatora, gnocchi al salmone Arrosto misto di pesce, insalata, patate fritte Macedonia con gelato Tiramisu', spumante, caffe' --**-- Meat dishes (price Lit. 45000, all-inclusive): Cocktail Bresaola con rughetta e parmigiano Crespelle ricotta e spinaci, risotto ai funghi porcini Scaloppine di vitella al limone, insalata, patate fritte Macedonia con gelato Tiramisu', spumante, caffe' --**-- Vegetarian (price Lit. 40000, all-inclusive): Cocktail Verdure gratinate Gnocchi all'ortica, risotto ai funghi Frittura mista di verdure, insalata, patate fritte Ananas fresca Macedonia con gelato Tiramisu', spumante, caffe' ===============================================================================

1 0

RIPE21 - Draft Agenda
by k13＠nikhef.nl 25 Apr '95

25 Apr '95

21sr RIPE Meeting Rome, 8 - 10 May 1995 Preliminary Agenda ------------------ Dear Colleagues, below you will find a first shot at the agenda for the 21st RIPE meeting. As always, it is a proposed agenda: please let me know of any changes and/or additions you might want to propose - dead line coming Friday 17:00h. A first try at scheduling the working group sessions will be distributed as a seperate mail. Last, but not least, a traditional RIPE dinner will be organised on Tuesday evening. Again, this will be seperately announced. See you all in Rome, Rob Blokzijl 21st RIPE Meeting Rome, 8-10 May 1995 Preliminary Agenda ------------------ o Opening and Welcome o Adoption of the Agenda o Minutes of the 20th RIPE Meeting o Outstanding Action Items o RIPE NCC Report o RIPE NCC Finances o Internet 1996 World Exposition o IETF Report o NSFnet: post mortem and the new world o Working Group Reports o Next Meetings o AOB o Closing

1 0

Useful tool
by RIPE NCC Hostmaster 20 Apr '95

20 Apr '95

In case it might be useful to others, Oliver at Demon Internet sent us the URL's for a tool he developed for checking assignments made from your block against entries in the RIPE database. You can contact him if you want more info <oliver(a)demon.net>. ------- It assumes you have a file called "ALLOCATIONS" or something which contains entries in the format: (Class C's specified a.b.c.0) <Begin Class C> [ - End Class C ] NETNAME {anything else} It reads this file, and then checks those addresses against the RIPE database, listing *all* entries, and emphasising gaps and entries where the ALLOCATIONS NETNAME doesn't match the returned one... Script is perl5... ftp://ftp.demon.co.uk/pub/perl/tools/ripe-check Also, re the ripe-hdl script... ftp://ftp.demon.co.uk/pub/perl/tools/ripe-hdl which converts a person: <Names> line into a person: <Names> line plus a nic-hdl: <handle> line. -------

1 0