October 2006 - db-wg - mailman.ripe.net

<auto-dbm@ripe.net> is slow this afternoon.
by RIPE Database Administration 17 May '18

17 May '18

Dear Colleagues, Because of a very high level of use this afternoon, the response time of <auto-dbm(a)ripe.net> is longer than normal. I have made contact with those who are responsible and I expect the situation to improve as the machine works through the queue. Please be patient. Obviously we at the RIPE NCC Database Group are continuously working to make the performance of the database as good as possible. However, we cannot make improvements in zero time. We thank you for your co-operation up to now and we ask for your continued co-operation so that everyone receives the best possible service. If you have anymore questions, please contact <ripe-dbm(a)ripe.net>. Regards, Ambrose Magee ____________________________ RIPE Database Administration.

2 2

SSL/TLS at RIPE mail servers
by Max Tulyev 01 Nov '06

01 Nov '06

Hi! At the last meeting we had a talk about implementing TLS/SSL in RIPE mail servers to avoid sniffing clear-text passwords in RIPE DB update requests. Is there any news? ;) -- WBR, Max Tulyev (MT6561-RIPE, 2:463/253@FIDO)

3 2

Announcement Routing Registry Training Courses
by RIPE NCC Training Services 31 Oct '06

31 Oct '06

Dear Colleagues The RIPE NCC Training Services Department invites you to register for one of our upcoming Routing Registry Training Courses: Date: Friday 3 November 2006 Time: 09:00 - 17:00 Location: Amsterdam, Netherlands AND Date: Tuesday 6 February 2007 Time: 09:00 - 17:00 Location: Tel Aviv, Israel AND Date: Friday 23 February 2007 Time: 09:00 - 17:00 Location: Vienna, Austria AND Date: Thursday 8 March 2007 Time: 09:00 - 17:00 Location: Edinburgh, United Kingdom ND Date: Friday 23 March 2007 Time: 09:00 - 17:00 Location: Prague, Czech Republic The main objective of the "Routing Registry Training Course" is to familiarise the LIRs with the features of the Routing Registry, while introducing the relevant tools and services of the RIPE NCC. The course also offers practical exercises. OVERVIEW OF TOPICS COVERED IN THE COURSE: - Routing Registry as a part of the RIPE Whois Database and the Internet Routing Registry (IRR) - Specifying routing policies using (RPSL) Routing Policy Specification Language and the RtConfig tool - IRRToolSet - Routing Information Service (RIS) - Routing Registry Consistency Check Project Please note that this is an advanced course. It will: - NOT teach the basics of routing - NOT teach the basics of RIPE Database operations - NOT describe how to receive Internet resources from the RIPE NCC - NOT describe how to operate a Local Internet Registry (LIR) The target audience of the course are technical staff of LIRs: e.g. network operators, engineers etc. This course is not intended for administrative or management staff (e.g. Hostmasters) . It is assumed that all attendees will be familiar with Border Gateway Protocol routing and with the RIPE Database (i.e. creating/modifying objects). This course is based on interactive exercises in a local network set-up. Please bring your laptops equipped with the following: - A working Ethernet card, - Three meters of Ethernet cable, - A secure connection client, - A web browser. Please be prepared to share your laptop (or at least allow another attendee to "look over your shoulder") if necessary. The course is free of charge. We provide lunch and printed training materials. We do not cover any of your travel expenses or accommodation. We give all of our training courses in English. You can find more information about the course at: http://www.ripe.net/training/rr/ How to register: --------------------- You can register up to two people from your LIR for each course. (If there are places left nearer the time of the course, you can register more people). To register for this course, you can either use the LIR Portal at: https://lirportal.ripe.net/lirportal/training/course-list.html Or the online registration form on our website: http://www.ripe.net/cgi-bin/trainingform.pl.cgi If you have any questions, send an e-mail to <training(a)ripe.net>. Kind regards, Rumy Kanis Training Services Manager RIPE NCC

1 0

ISO Country Code Change
by Katie Petrusha 27 Oct '06

27 Oct '06

[Apologies for duplicate e-mails] Dear Colleagues, The ISO 3166 country codes list has been changed. The previous country code for Serbia and Montenegro (CS) has been replaced with two new country codes: RS - Serbia ME - Montenegro On Friday, 27 October 2006, the RIPE Database software and the LIR Portal will be altered to accept all three codes. The old CS country code will be deprecated at a later date. The full ISO 3166 country code list is available at: ftp://ftp.ripe.net/iso3166-countrycodes.txt http://www.iso.org/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/li… If you have any questions e-mail us at: ripe-dbm(a)ripe.net Kind regards, -- Katie Petrusha Software Engineer RIPE NCC

2 2

ASn32-compliant RIPE Database software available
by Katie Petrusha 25 Oct '06

25 Oct '06

[Apologies for duplicates] Dear Colleagues, The RIPE NCC has updated its database software to support the new ASN32 objects. As you may be aware, studies of Autonomous System Number (ASN) consumption rates show that the existing pool of unallocated 2-byte ASNs will run out somewhere between 2010 and 2014. >From 1 January 2007, it will be possible to request 32-bit ASNs (ASN32 objects). You can find the policy on these 4-byte ASNs at: http://www.ripe.net/ripe/docs/ripe-389.html Although the first of these will not appear in the RIPE Database until the start of next year, the revised code is available to download for testing purposes from: http://www.ripe.net/db/cvs-bugzilla.html (CVS branch name: asn32_changes_fixed) You can also find the list of modified files at the end of this mail. If you have any questions about this, please e-mail sw-bugs(a)ripe.net Regards, -- Katie Petrusha Software Engineer RIPE NCC List of changed files in RIPE whois software: ----------------------- src/defs/variants/RIPE/syntax.xml src/defs/variants/RIPE/classes.xml defs/variants/RIPE/attributes.xml all the lex/yacc parser files wk/which_keytypes.c wk/which_keytypes.h src/modules/ln/lu_whois.c src/modules/qi/query_instructions.c src/modules/qc/query_command.c conf/rip.config.sample.in src/modules/ca/ca_dictionary.h src/modules/ca/ca_macros.h src/modules/ca/dictGen.m4 src/modules/ud/ud_core.c src/SQL/create.tables.in src/SQL/create_asn32.patch.in dbupdate test-data files in tests/dbupdate/test-data src/modules/qc/query_command.h src/modules/ud/ud.h src/modules/ud/ud_command.c -------------------------

1 0

Webquery and Webupdates services were unavailable
by Trudy Prins 24 Oct '06

24 Oct '06

[Apologies for duplicate mails] Dear Colleagues, Between 14:30 - 14:50 (UTC) on Tuesday, 24 October 2006 our Webquery and Webupdates services were unavailable. This problem was due to performance issues on one of our servers and has now been resolved. We apologise for any inconvenience. If you have any questions or concerns regarding this issue, please contact us at: <ripe-dbm(a)ripe.net> Regards, -- Trudy Prins User Support Coordinator

1 0

Re: [enum-wg] Proposal for new org-type
by Niall O'Reilly 19 Oct '06

19 Oct '06

This message has two purposes. It is addressed to the ENUM WG with the purpose of determining consensus in this WG on the proposal from Antoin Verschuren. It is addressed to the DB and NCC-Services WGs as an inter-WG communication to alert these WG's to expect a consensus in the ENUM WG and a request from ENUM WG for related changes to the RIPE database. On 3 Oct 2006, at 10:35, Antoin Verschuren wrote: > In order for ENUM registries to be correctly distinguished in the RIPE > NCC database, I want to propose a new organization type to be used in > the organization object. > > Current organization types are: > IANA > RIR > NIR > LIR > NON-REGISTRY > > I would like this list to be extended with the term REGISTRY. > > I will note the issue tomorow in the ENUM WG, but need consensus to > take > place here, so please comment either here or tomorrow in the ENUM WG > session. On 4 Oct 2006, at 09:47, Antoin Verschuren wrote: > I can live with ENUM-REGISTRY, REGISTRY, OTHER or no org-type at all. > I cannot live with the org-type NON-REGISTRY. During his presentation in the ENUM WG, Antoin Verschuren made the following proposal. > In order for ENUM registries to not be misinterpreted in the RIPE > NCC database, I want to propose to change an organization type to be > used in the organization object. > Current organization types are: > > IANA > > RIR > > NIR > > LIR > > NON-REGISTRY > I would like this NON-REGISTRY to be changed to OTHER. I will declare consensus in the ENUM WG unless objections to Antoin's proposal are posted on the ENUM WG mailing list before 12:00 UTC on Thursday, 18 October 2006. Best regards, Niall O'Reilly Co-Chair, RIPE ENUM Working Group

2 3

org: question
by Max Tulyev 18 Oct '06

18 Oct '06

Hi! As a LIR, I have org: object (with org-type: LIR). But I can't use it in my objects, because of there is mnt-ref: RIPE-NCC-HM-MNT. The question is why? -- WBR, Max Tulyev (MT6561-RIPE, 2:463/253@FIDO)

1 0

Deprecation of CRYPT-PW authorisation from the RIPE Database
by Agoston Horvath 16 Oct '06

16 Oct '06

Dear colleagues, I would like to inform you that the project to deprecate CRYPT-PW authorisation in mntner objects in the RIPE Database is scheduled to start this week. Regards, Agoston Horvath Software Engineering Department RIPE NCC -------- Original Message -------- Subject: [db-wg] Proposal to deprecate CRYPT-PW authorisation in the RIPE Database Date: Wed, 4 Oct 2006 15:48:12 +0200 From: Katie Petrusha <katie(a)ripe.net> To: db-wg(a)ripe.net Dear colleagues, Here follows the proposal to deprecate CRYPT-PW authorisation in mntner objects in the RIPE Database. Comments would be appreciated. Background and motivation ------------------------- In the RIPE Database there are several authorisation types currently supported: CRYPT-PW, MD5-PW, PGPKEY and X509. These authorisation types define what kind of authorisation tokens can be used in "mntner" objects. CRYPT-PW authorisation type is based on UNIX crypt() functionality and is vulnerable to both dictionary and brute force attacks given the fixed password length and lack of cryptographic strength given today's computing power. While maintaining and protecting objects in the RIPE Database is the responsibility of the respective maintainer, the RIPE DB WG agreed that it's the responsibility of the community to ensure that only appropriate tools and algortihms are used and maintained. Since CRYPT-PW does no longer fulfill this requirements with the reasons given above, the WG also agreed to phase out CRYPT-PW. PGPKEY and X.509 have been the recommended authentication schemes for some time (http://www.ripe.net/db/support/security/security.html) MD5-PW shares two weaknesses with CRYPT-PW: passwords are sent in clear together with update requests and MD5 is vulnerable to dictionary attacks,as well. Still, MD5-PW will not be phased out together with CRYPT-PW, since at least the dictionary attack can be prevented by chosing passwords or pass phrases of appropriate length and entropy. MD5 offers a short path of migration away from CRYPT-PW without major change in processes. LIRs should, however, seriously consider a migration towards a public key based authentication scheme (PGPKEY or X.509). The MD5-PW method will be addressed separately. We propose to deprecate the CRYPT-PW authorisation step-by-step. Affected objects ---------------- There are currently ~3500 mntner objects in the RIPE Database that have only CRYPT-PW authorisation. There are about 300 mntner objects that have mixed authorisation of CRYPT-PW and some other authorisation types. Plan ---- 1. Gather mntner objects: group A: only CRYPT-PW authorisation group B: CRYPT-PW and (PGP or X509 or MD5) authorisation 1a. E-mail the contacts of those mntner objects (notify, admin-c, tech-c, mnt-nfy) to notify them about the coming change. 1b. notify the DB-WG mailing list 1 month later: 2. Modify the RIPE Database software: 1) reject any change to mntner object that adds new CRYPT-PW. 2) show a warning if CRYPT-PW was used during authorisation. 3) show a warning if object being updated still contains (existing) CRYPT-PW. 2a. E-mail the contacts of the mntner objects (notify, admin-c, tech-c, mnt-nfy) notifying them about the change and the next steps. 2b. notify the DB-WG mailing list 1 month later: 3. Modify the RIPE Database software: 1) disable CRYPT-PW in the syntax 2) disable CRYPT-PW in authorisation 3a. Modify mntner objects. group A: auth: is changed to MD5-PW, new password generated. group B: auth: CRYPT-PW is changed into "remarks" line "remarks: "your object was modified due to CRYPT-PW deprecation" is added 3b. Notify the contacts of the mntner objects: group A: explanation about the changes done, and URL with details on how to 'recover' the locked mntner object (similar to NONE deprecation process) group B: explanation about the changes done 3c. notify the DB-WG mailing list 4. Finished.

1 0

First draft of RIPE53 minutes
by Nigel Titley 06 Oct '06

06 Oct '06

Folks, Please find first rough draft of minutes of this morning's meeting. Comments welcome. Nigel <<Minutes.txt>>

1 0