From Anne.Lord at ripe.net Tue Jun 1 14:12:34 1993 From: Anne.Lord at ripe.net (Anne Lord) Date: Tue, 01 Jun 1993 14:12:34 +0200 Subject: Expiry and review of European IP number request form Message-ID: <9306011212.AA05935@ncc.ripe.net> Hi all, At the end of June we reach the expiry date for the European IP network number request form. I would like to review how useful this document has been to you so I would like your comments/suggestions for a revised document. Even if you have no comments I would be grateful if you would indicate to me whether you are using it so I can get an idea of how representative the comments are. Many thanks, -Anne From Anne.Lord at ripe.net Tue Jun 1 14:57:00 1993 From: Anne.Lord at ripe.net (Anne Lord) Date: Tue, 01 Jun 1993 14:57:00 +0200 Subject: IP network number template Message-ID: <9306011257.AA06071@ncc.ripe.net> Dear All For our accounting for the next Quarterly Report, and for our internal review we would like to have *exact* numbers on those of you who are/are not using the European IP network number request form (ripe-83). So for those of you who havent yet replied to my earlier message, could you please answer with a "YES we do use it" or a "NO" to me. Many thanks, -Anne From ncc at ripe.net Wed Jun 2 10:12:18 1993 From: ncc at ripe.net (RIPE NCC Staff) Date: Wed, 02 Jun 1993 10:12:18 +0200 Subject: Provider/non-provider network allocations in Ireland In-Reply-To: Your message of Wed, 02 Jun 1993 08:39:08 BST. <9306020739.AA07823@ncc.ripe.net> Message-ID: <9306020812.AA07955@ncc.ripe.net> Michael Nowlan writes: * I had a phone conversation with Mike Norris of HEANET yesterday and we * agreed that IEunet would take on the task of providing IP registry * services on a non-provider basis in Ireland. * * Obviously, we will continue to provide registry services on a provider * basis as well! * * We will do our best to act impartially in this task. Dear Michael, thank you very much for volunteering to provide this service to the Irish Internet community. We will use the same contact information for the non-provider registry as for the IEuNet one. Please let us know if we need to use different information and/or have to put additional people on the local-ir at ripe.net list. I trust you still have a copy of ripe-72, so I will not include it :-). Thanks again. Cheers Daniel From mnorris at dalkey.hea.ie Wed Jun 2 11:12:46 1993 From: mnorris at dalkey.hea.ie (Mike Norris) Date: Wed, 02 Jun 93 10:12:46 +0100 Subject: Provider/non-provider network allocations in Ireland In-Reply-To: Your message of "Wed, 02 Jun 93 10:12:18 +0200." <9306020812.AA07955@ncc.ripe.net> Message-ID: <9306020912.AA22934@dalkey> Michael my thanks too for your voluntary efforts. No better man! Cheers. Mike From renard at corton.inria.fr Wed Jun 2 12:54:16 1993 From: renard at corton.inria.fr (renard at corton.inria.fr) Date: Wed, 02 Jun 93 12:54:16 +0200 Subject: IP network number template In-Reply-To: Your message of "Tue, 01 Jun 93 14:57:00 +0200." <9306011257.AA06071@ncc.ripe.net> Message-ID: <199306021054.AA11907@corton.inria.fr> In your previous mail you wrote: Dear All For our accounting for the next Quarterly Report, and for our internal review we would like to have *exact* numbers on those of you who are/are not using the European IP network number request form (ripe-83 ). So for those of you who havent yet replied to my earlier message, could you please answer with a "YES we do use it" or a "NO" to me. >> YES we do use it, it's very usefull. Thanks, Annie From Daniel.Karrenberg at ripe.net Mon Jun 7 13:47:00 1993 From: Daniel.Karrenberg at ripe.net (Daniel Karrenberg) Date: Mon, 07 Jun 1993 13:47:00 +0200 Subject: RIPE NCC Review In-Reply-To: My message of Thu, 27 May 1993 14:37:42 +0200. Message-ID: <9306071147.AA19863@ncc.ripe.net> On May 27th I sent the message below. Noone has volunteered to represent the lcoal-IR WG. Unless someone comes forward now, the group will not be represented formally. Regards Daniel > Daniel Karrenberg writes: > > As agreed at the last RIPE meeting a review of the first year of NCC > operations as well as a review of the NCC activity plan will take place. > The review board will consist of the RIPE chair, the RIPE WG > chairpeople and the NCC manager. Any interested members of the RIPE > community will also be invited to paricipate. The RIPE chair is going > to announce this activity shortly. > > The local-ir WG has a problem here as the chairperson *is* the RIPE NCC > manager. To avoid any possibilities of a conflict of interests I would > appreciate if the local-ir group could agree on a different representative > for this purpose. > > If you are prepared to represent the local-ir group in this, > please identify yourself either to me or to the while group. > > Ragrads > > Daniel From Daniel.Karrenberg at ripe.net Mon Jun 7 13:53:22 1993 From: Daniel.Karrenberg at ripe.net (Daniel Karrenberg) Date: Mon, 07 Jun 1993 13:53:22 +0200 Subject: Local-IR Feedback on the PRIDE Project In-Reply-To: My message of Wed, 26 May 1993 13:44:10 +0200. Message-ID: <9306071153.AA19873@ncc.ripe.net> Since I have not reveived *any* comments on the PRIDE proposal from the local-IR WG, I will have to report back that there is neither support nor critisism of the project from the group. To me this is -to put it mildly- disappointing. If noone has the time to even read a six page proposal about a pressing problem and send a one line message back, we cannot achieve much in RIPE. Daniel From rv at deins.informatik.uni-dortmund.de Mon Jun 7 13:56:44 1993 From: rv at deins.informatik.uni-dortmund.de (rv at deins.informatik.uni-dortmund.de) Date: Mon, 07 Jun 93 13:56:44 N Subject: RIPE NCC Review In-Reply-To: Your message of Mon, 07 Jun 93 13:47:00 +0200. <9306071147.AA19863@ncc.ripe.net> Message-ID: <9306071156.AA03899@deins.informatik.uni-dortmund.de> Hi Daniel, > On May 27th I sent the message below. Noone has volunteered > to represent the lcoal-IR WG. Unless someone comes forward > now, the group will not be represented formally. if no one else steps up - everybody as busy as my humble self? - I will try to participate and represent the local IR point of view. Cheers, Ruediger Ruediger Volk Universitaet Dortmund, Informatik IRB DE-NIC Postfach 500 500 D-W-4600 Dortmund 50 Germany E-Mail: rv at Informatik.Uni-Dortmund.DE Phone: +49 231 755 4760 Fax: +49 231 755 2386 From larsha at nms.telepost.no Mon Jun 7 14:22:29 1993 From: larsha at nms.telepost.no (Lars H}kedal) Date: Mon, 7 Jun 1993 14:22:29 +0200 Subject: Local-IR Feedback on the PRIDE Project In-Reply-To: Daniel Karrenberg's message of Mon, 07 Jun 1993 13:53:22 +0200 <9306071153.AA19873@ncc.ripe.net> Message-ID: <199306071222.AAnms.telepost.no19031@nms.telepost.no> From: Daniel Karrenberg Since I have not reveived *any* comments on the PRIDE proposal from the local-IR WG, I will have to report back that there is neither support nor critisism of the project from the group. To me this is -to put it mildly- disappointing. If noone has the time to even read a six page proposal about a pressing problem and send a one line message back, we cannot achieve much in RIPE. I was added to the list just the other day. Where can I find the PRIDE proposal? Lars Haakedal larsha at telepost.no From Daniel.Karrenberg at ripe.net Tue Jun 8 12:52:32 1993 From: Daniel.Karrenberg at ripe.net (Daniel Karrenberg) Date: Tue, 08 Jun 1993 12:52:32 +0200 Subject: RIPE NCC Review In-Reply-To: Your message of Mon, 07 Jun 1993 13:56:44 MET. <9306071156.AA03899@deins.informatik.uni-dortmund.de> Message-ID: <9306081052.AA26596@ncc.ripe.net> > rv at deins.informatik.uni-dortmund.de writes: > > if no one else steps up - everybody as busy as my humble self? - > I will try to > participate and represent the local IR point of view. Since I have heared only positive reactions from the group, Ruediger will represent the local-IR WG in the review. Daniel From mnorris at dalkey.hea.ie Wed Jun 9 11:22:09 1993 From: mnorris at dalkey.hea.ie (Mike Norris) Date: Wed, 09 Jun 93 10:22:09 +0100 Subject: RIPE NCC Review In-Reply-To: Your message of "Mon, 07 Jun 93 13:56:44 +0100." <9306071156.AA03899@deins.informatik.uni-dortmund.de> Message-ID: <9306090922.AA27944@dalkey> Oh good, Ruediger has accepted. Phew! Mike From ripe-dbm at ripe.net Mon Jun 21 12:19:39 1993 From: ripe-dbm at ripe.net (RIPE Database Manager) Date: Mon, 21 Jun 1993 12:19:39 +0200 Subject: the difference between assign@ripe.net and ripe-dbm@ripe.net Message-ID: <9306211019.AA02723@ncc.ripe.net> Dear people, There seems to be some misunderstanding between the usage of assign at ripe.net and ripe-dbm at ripe.net. Please use these two addresses as follows: assign at ripe.net - only for NEW assignments made out of your 193.x block (so, they should not be in the RIPE or NIC database yet) ripe-dbm at ripe.net - all other nets new to the database, and all updates. x.193.in-addr.arpa requests should be send to hostmaster at ripe.net, because there is some additional action on behalf of the NCC needed. We will then forward the objects to ripe-dbm, when all set up. The reason we have a difference between the two is that assign at ripe.net has some additional consistency checking before it will forward to the database, since we found that many people made 192/193 typos, and also we are planning with InterNIC to automatically forward NEW 193 assignments directly to them in exchange format in the future. If a network send in to assign at ripe.net is already present in the NIC or RIPE database, the update is bounced back to the NCC for manual review. In most cases it will be forwarded to ripe-dbm after, but it would be nice if we could keep these kinds of "assignment errors" as we call them, to a minimum. PS contact people send in to either address are not checked, so you can simply include them in assign or ripe-dbm together with the network numbers they belong to. Cheers, -Marten From Marten.Terpstra at ripe.net Thu Jun 24 11:34:39 1993 From: Marten.Terpstra at ripe.net (Marten Terpstra) Date: Thu, 24 Jun 1993 11:34:39 +0200 Subject: New database software update Message-ID: <9306240934.AA11782@ncc.ripe.net> all, It's time to let you know what has happened wth RIPE database software development. After some more experimenting to check feasibility we have progressed quite far into a complete rewrite of the database software. We have completed the system design and started to implement various modules. The new design has the following features - fully (and we *mean* fully!) configurable from a config file - separate files (and indices) to store different databases - dynamic updates and deletes as opposed to batch only - possibility for update protocol other than e-mail - guarded fields designed in - dynamic update of secondary databases possible Features which have been requested but are not designed in: - preserve the order of tags within object - preserve the position of remark or comment lines within objects These two features turned out to be hard to specify in the light of updates and even harder to implement. They might go in the next release if someone can come up with a consistent and intuitive spec. The new software will be implemented in the perl language. So those of you who do not have it installed and want to use the RIPE database software should plan to install perl. Of course you won't need perl if you just want to use a whois client and send in updates by mail. Implementing in perl instead of shell, awk and C has three benefits: coding in perl ist fast, subroutines can be used (missing from std awk) and the result is portable. We have a copy of the alpha software running on a PC under UNIX. Together with a notebook this gives you a "portable" RIPE database. The first module completed is the whois server (net.c and netdbm.c replacement). This server runs as its own daemon process rather than under inetd. The measured performance on a SUN ELC before optimising is 5 queries/s on average and the server can sustain peaks of 50 queries arriving in parallel. The new server is compatible with the current one and has some added features: the source databases (RIPE, MERIT, NIC etc.) can be selected individually rather than either RIPE or all, the same connection can be used for multiple queries (nice for tools like prtraceroute), a grep type query as well as nice logging. We have an alpha version of the whois server and the database indexing tool running. The next part to be tackled is the update procedure including the guarded attributes. The last part will be the current mail interface for the update procedure. Impact: Sometime in the next few weeks (after another announcement) we will start using the new server on whois.ripe.net. This should be transparent. Once this is running we will implement the backlogged new tags such as the DMZ specifics in the network and the operatinal contacts. Sometime later we will start using the new update procedures. This will mean that updates mailed in will appear in the database more quickly. It will also mean that we will be more stringent in checking updates, because there will be less human intervention from NCC staff. So you should expect more bounced updates, but they will also happen much more quickly. Diagnostics will be better because the dynamic update procedure will have access to the current database. This will mean that heuristic checks of updates can be better. If you have any questions, please do not hesitate to ask them either puclicly for the benefit of all or privately. The NCC people working on this are me (design, coding and testing) and Daniel (design and testing). Cheers, -Marten From Anne.Lord at ripe.net Mon Jun 28 15:00:58 1993 From: Anne.Lord at ripe.net (Anne Lord) Date: Mon, 28 Jun 1993 15:00:58 +0200 Subject: ripe-83 update Message-ID: <9306281301.AA22648@ncc.ripe.net> Hi, I am currently updating the European IP template since the expiry date on the document is 30th June. I have received comments from some people already, and have made some changes (which comprise mostly typographical tidying up and word order changes - nothing huge). If anyone has any further suggestions, just let me know - by the end of the week please. Thanks, -Anne