- lir-wg - mailman.ripe.net

Announcement - Database Consistency and Statistics Project
by Can Bican 14 Jan '02

14 Jan '02

Dear Colleagues, [Apologies for multiple messages]. The new version of database consistency project, along with whois server usage statistics have been released on the RIPE NCC's web pages, with the following url: http://www.ripe.net/db/dbconstat/ The goal of this project is to find the objects with consistencies not enforced by the database, and provide reports and statistics to help users correct them. It also aims at checking for the necessary protection of objects and tracing the query and update statistics of the RIPE whois server to analyze the current trends of using the database. The goals of the consistency project do not include, for example, reality checks for inetnum objects, but it addresses only internal inconsistencies in the database, such as invalid references. Here are the types of inconsistencies which are addressed in this project: * Inetnum object related: * Inetnum objects without status attribute, * Assigned inetnum objects without allocations, * Overlapping inetnum objects, * Inetnum objects with suspicious boundaries to form a network, * Assigned inetnum objects from assignments, * Inetnum objects with wrong PA or PI status, * Wrongly allocated inetnum objects. * Person object related: * Person objects with multiple identical copies, * Person objects which do not have any references to them, * Person objects not having a valid nic-handle, * Objects which have references to invalid nic-handles. * Maintainer object related: * Maintainer objects which do not have any references to them. * Protection related: * Weak authentications schemes for maintainers. * Inetnum objects with no mnt-lower attribute. Reports about individual inconsistencies are sent only to the maintainers of objects. If you'd like to receive the report for your inconsistencies, send an e-mail to auto-dbcon(a)ripe.net containing the maintainer name in its body, and the appropriate authentication. * If the authentication of your maintainer is MAIL-FROM, mail should be sent from the appropriate e-mail address, and should contain the following in its body: mntner: <maintainer_name> * If the authentication of your maintainer is CRYPT-PW, mail should contain the following lines in its body: mntner: <maintainer_name> password: <password> * If the authentication of your maintainer is PGPKEY, mail should contain the following line and should be signed with the appropriate key: mntner: <maintainer_name> If you supply an existing maintainer and the proper authentication, the report of the inconsistencies related to the maintainer will be mailed back to you. For questions, comments and suggestions, please contact ripe-dbm(a)ripe.net. -- Can Bican RIPE NCC

1 0

Status and appologies from the Chair
by Hans Petter Holen 12 Jan '02

12 Jan '02

Dear lir-wg, Just to give you all a brief update on my whereabouts: The ICANN Address Council this week had its first phone conference his year, with the newly elected members on participating. The Secretariat has been transferred from the RIPE NCC where Mirjam and others have done an excellent job organizing the practical details for our work, to ARIN who will serve as ASO secretariat this year. After two years as chair of ICANNs address Council I was happy to pass the work on to Barbara Rosseman who was nominated and elected as chair for the upcoming year. I volunteered and was elected to serve as one of two vice chairs. Minutes from the AC meetings can be found at http://www.aso.icann.org/meetings/index.html For the upcoming RIPE meeting I will due to work commitments at Tiscali Norway unfortunately not be able to participate in the lir-wg meeting. James Aldridge, whom you elected as one of two co-chairs, has kindly stepped in, and will be chairing the meeting. I may still be able to attend at the end of the week. If not, I wish you all a constructive and interesting meeting! Best Regards, Hans Petter Holen

1 0

Revision of IPv4 policy doc - proposed timeline
by Nurani Nimpuno 11 Jan '02

11 Jan '02

Dear colleagues, We wish to draw your attention to the revision of the current IPv4 policy document and the first draft, posted on the web in August 2001: http://www.ripe.net/rs/ipv4policy.html A few comments were gathered after the publication of the draft, as summarised below: - ASN policy should be in a separate policy document. - Further clarification of the "Static assignments for services that are permanently connected to the Internet" possibly needed. - Clarification of policy on registration of End-User contact details in the RIPE db (with respect to privacy). - Re-wording (re-clarification) of the Reverse Delegation policy section. The public mailing list <ripe-185bis(a)ripe.net> was set up to facilitate the revision of this draft, but other than the comments listed above, there has been very little activity. The IPv4 policy draft has now been publicly available for comments for five months and I believe we are all keen to see a final version of this document out soon. We would therefore like to propose the following timeline to move forward with the publication of the new IPv4 policy document: 11-25 Jan : 1st revision period (2 weeks) - Public call for comments 25 Jan-7 Feb: Editing by the RIPE NCC (2 weeks) Comments to be incorporated by the RIPE NCC 7 Feb : 2nd draft to be published by the RIPE NCC 7 Feb-21 Feb: 2nd revision period (2 weeks) - Public call for comments 21-28 Feb : Final editing by the RIPE NCC (1 week) 28 Feb : Final version of the policy document to be published. We welcome any input on this draft and encourage you to send your comments to <ripe-185bis(a)ripe.net>. If you wish to subscribe to this mailing list, please send a mail to <majordomo(a)ripe.net> with "subscribe ripe-185(a)ripe.net" (without quotation marks) in the body of the message. The mailing list is also archived at: http://www.ripe.net/ripe/mail-archives/ripe-185bis/index.html Mirjam <mir(a)ripe.net> will be co-ordinating the revision process, should you have any specific questions regarding the policy draft document. We hope that the proposed timeline is acceptable to everyone and we look forward to your comments. Regards, Nurani Nimpuno Internet Address Policy Manager RIPE NCC

1 0

Hostmaster Centre at RIPE 41
by RIPE NCC Staff 09 Jan '02

09 Jan '02

Dear all, RIPE NCC Registrations Services are pleased to announce that during the RIPE 41 Meeting in Amsterdam, we will open a RIPE NCC Hostmaster Centre. RIPE NCC Hostmasters will be available for any IP and ASN request questions, and also any general policy questions. A timesheet at the centre will be made available for appointments, though 'walk-in's will also be welcome. Please note the following time-table: Monday January 14. 12:30 - 14:00 Tuesday January 15. 9:00 - 17:30 Wednesday January 16. 12:30 - 17:30 Thursday January 17. 9:00 - 17:00 Friday January 18. 9:00 - 14:00 (IP request Tutorial, 14.00 - 17.30) We look forward to meeting you. Regards, RIPE NCC Hostmasters

1 0

Draft Agenda for LIR WG at RIPE41
by James Aldridge 09 Jan '02

09 Jan '02

Greetings, It seems not unlikely that I'll be chairing the LIR-WG session next Wednesday. Here's a very slightly modified version of the draft agenda which has been up on the RIPE web site for some time. Regards, James ----- LIR WG @ RIPE41 - 16 Jan 2002 09:00-12:30 Draft Agenda A. Admin - scribe, participant list, charter, mailing-lists B. Agenda bashing C. RIPE 39+40 (minutes and actions) D. Report from the RIPE NCC Hostmasters E. RIPE 185 ("European Internet Registry Policies and Procedures") F. Change of policy for Portable address space G. RFC 2050 ("Internet Registry IP Allocation Guidelines") revision H. Report from the Address Council I. IPv6 interim policy J. IPv6 future policy Y. Any other business Z. Open microphone...

1 0

Registration RIPE 41 continues...
by RIPE NCC Meeting Registration 09 Jan '02

09 Jan '02

>Dear colleagues, > >As RIPE 41 will take place in Amsterdam, we will not close the >registration database, but will have this open till the >13th of January. This means that the registration form still can be submitted.>You can find the registration form on our website. > >For registration and RIPE 41 information please visit: > >http://www.ripe.net/ripe/meetings/current/ripe-41/ > >The fees are: >RIPE Meeting only (excluding discount): EUR 350 >RIPE Meeting plus RIPE dinner (excluding discount): EUR 415 > >If you have have any questions, do not hesitate to contact us: ><meeting(a)ripe.net> > >Best regards, > >Asha Raghoebarsing >Meeting Coordinator ------- End of Forwarded Message

1 0

Status of IRT object
by Gabriella Paolini 07 Jan '02

07 Jan '02

Dear all, which is the status of IRT object? Is the trial implementation available? This example shows again the need for a specific object. If someone uses whois information from cyberabuse.org, as many times people does, that information is wrong, because ciberabuse guys used Admin-c email without considering all other informations in inetnum object and in role object. Thanks and regards, Gabriella Paolini INFN-GARR [ Informations about 193.204.17.211 ] IP range : 193.204.16.0 - 193.204.23.255 Network name : UNIBAS-NET AS number : AS137 Infos : Universita' Degli Studi Di Basilicata Infos : Centro Interfacolta' Servizi Informatici E Telematici - Cisit Phone number : +39 06 49914352 Country : IT Abuse contact : enzo.valente(a)infn.it Source : RIPE right information are inetnum: 193.204.16.0 - 193.204.23.255 netname: UNIBAS-NET descr: Universita' degli Studi di Basilicata descr: Centro Interfacolta' Servizi Informatici e Telematici - CISIT country: IT admin-c: EV182-RIPE tech-c: GL965-RIPE tech-c: GM976-RIPE ... remarks: To notify abuse mailto: cert(a)garr.it remarks: Multiple lan of university departments remarks: GARR - Italian academic and research network mnt-by: GARR-LIR ... role: GARR LIR ... trouble: To notify abuse mailto: cert(a)garr.it trouble: Information at http://www.lir.garr.it/ ... person: Enzo Valente address: INFN - Dipartimento di Fisica address: Universita' La Sapienza address: Piazzale Aldo Moro,2 address: I-00185 Roma address: Italy phone: +39 06 49914352 fax-no: +39 06 4957697 e-mail: Enzo.Valente(a)infn.it ...

4 3

Registration RIPE 41 continues...
by RIPE NCC Meeting Registration 04 Jan '02

04 Jan '02

Dear colleagues, As RIPE 41 will take place in Amsterdam, we will not close the registration database today as planned, but will have this open till the 13th of January. This means that the registration form can be submitted for another week. You can find the registration form on our website. For registration and RIPE 41 information please visit: http://www.ripe.net/ripe/meetings/current/ripe-41/ Please note that the discount period DOES end today, the 4th of January. If you have have any questions, do not hesitate to contact us on: <meeting(a)ripe.net> Best regards, Asha Raghoebarsing Meeting Coordinator

1 0

Important information on RIPE 41
by RIPE NCC Meeting Registration 23 Dec '01

23 Dec '01

Dear all, Only two weeks left till the next RIPE meeting. Some of you maybe forgot to register or still has this on the to-do list, please make sure to register now. For your convenience you can register using our secure website at: https://www.ripe.net/cgi-bin/mtgreg (encrypted form) http://www.ripe.net/cgi-bin/mtgreg (non-encrypted form) We would also like to inform you about the accommodation: The Krasnapolsky Hotel has a special rate for all RIPE attendees. The price is EUR 140 for a single room incl. breakfast. Please mention RIPE 41 to the reservations department of the Krasnapolsky Hotel. With kind regards, Asha Raghoebarsing Meeting Coordinator <meeting(a)ripe.net>

1 0

Reminder RIPE 41 registration
by RIPE NCC Meeting Registration 17 Dec '01

17 Dec '01

Dear Colleagues, Herewith we like to remind you of the registration for the RIPE 41 meeting which has been opened. The meeting will be held from 14th January - 18th January 2002 at hotel Krasnapolsky in Amsterdam, The Netherlands. More information about this meeting and accommodations can be found on this page: http://www.ripe.net/ripe/meetings/current/ripe-41/ The online registration will close on Friday 4th January 2002 (10 workingdays fm now). On-site registration will open on Monday 14th January 2002. Please note the following: To avoid waiting queues at the registration desk on-site we encourage pre-payment by credit card. The registration fee for this meeting is EUR 350.00 (this includes refreshments and lunches) and the dinner fee is EUR 65.00. However, if payment is received before 4 January 2002, the pre-payment cut-off date, you will receive a pre-registration discount of EUR 50.00. Therefore, the fee for attendees paying before the cut-off date is EUR 300.00 for the meeting and 65.00 EUR for the RIPE dinner event. Confirmation of Registration: For your convenience you can register using our secure website at: https://www.ripe.net/cgi-bin/mtgreg (encrypted form) http://www.ripe.net/cgi-bin/mtgreg (non-encrypted form) If you still prefer not to send your credit card number using an encrypted transfer method, we have prepared a fax form. This form is attached to the acknowledgment of your registration. You will receive a second acknowledgment by e-mail as soon your payment has been processed. In addition, you will find the receipt for your payment in your conference envelope. Participants requiring a visa to enter The Netherlands are advised to begin the required procedures as soon as possible. The RIPE Meeting organizers are pleased to provide letters of invitation to those attendees requiring them. Should you have any further questions, please do not hesitate to contact us at <meeting(a)ripe.net>. Kind regards, Asha Raghoebarsing RIPE Meeting Co-ordinator <meeting(a)ripe.net>

1 0