June 1993 - lir-wg - mailman.ripe.net

ripe-83 update
by Anne Lord 28 Jun '93

28 Jun '93

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

1 0

New database software update
by Marten Terpstra 24 Jun '93

24 Jun '93

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

1 0

the difference between assign@ripe.net and ripe-dbm@ripe.net
by RIPE Database Manager 21 Jun '93

21 Jun '93

Dear people, There seems to be some misunderstanding between the usage of assign(a)ripe.net and ripe-dbm(a)ripe.net. Please use these two addresses as follows: assign(a)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(a)ripe.net - all other nets new to the database, and all updates. x.193.in-addr.arpa requests should be send to hostmaster(a)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(a)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(a)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

1 0

Re: RIPE NCC Review
by Daniel Karrenberg 09 Jun '93

09 Jun '93

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 <Daniel.Karrenberg(a)ripe.net> 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

3 3

Re: Local-IR Feedback on the PRIDE Project
by Daniel Karrenberg 07 Jun '93

07 Jun '93

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

2 1

IP network number template
by Anne Lord 02 Jun '93

02 Jun '93

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

2 1

Re: Provider/non-provider network allocations in Ireland
by RIPE NCC Staff 02 Jun '93

02 Jun '93

Michael Nowlan <mn(a)IEunet.ie> 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(a)ripe.net list. I trust you still have a copy of ripe-72, so I will not include it :-). Thanks again. Cheers Daniel

2 1

Expiry and review of European IP number request form
by Anne Lord 01 Jun '93

01 Jun '93

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

1 0