January 2005 - db-wg - mailman.ripe.net

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

16 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

Deprecation of the NONE Authentication Scheme
by Ziya Suzen 07 Nov '05

07 Nov '05

Dear Colleagues, As announced at RIPE 47 the NONE authentication scheme will be deprecated. After 26 April 2004 the RIPE Whois Database will not accept updates using the NONE authentication scheme. If you have objects protected by a MNTNER object which has the NONE authentication scheme, please assign another authentication scheme or create another MNTNER object to protect these objects. If you are a RIPE NCC member you can create new MNTNER objects through the LIR Portal or send your update to <auto-dbm(a)ripe.net>. History and details: -------------------- 1. Motivation The RIPE Database protects data from unauthorised modification through the use of references to maintainer objects. The maintainer objects contain an "auth:" attribute which specifiy how a user is authenticated during updates to the database. One of the allowed authentication schemes is "NONE", which is actually not an authentication at all, but rather specifies that no authentication is necessary. NONE is intended to be used consciously, as a notification facility or as a means to tag objects. In April 2003, a proposal was sent to the Database Working Group by Hank Nussbacher: It has come lately to the attention in the Internet security realm that spammers as well as crackers are hijacking IP address space. One easy way to "steal" IP address space is via those that have auth=NONE on their objects. It is likely that in many cases NONE is used simply because it is easy. Currently approximately 500 maintainers use NONE - about 5% of all maintainers. 2. Plan Normally with a database cleanup effort, an announcement is sent to the appropriate mailing lists, posted to the RIPE web page, and also sent to the specific users affected. A period of time for cleanup is given. Finally, if the users have not fixed the data then it is modified. However, for the NONE deprecation, it is inadvisable to do this as it means announcing what is in effect a security vulnerability. Also, our operational experience with past cleanups shows that most users do not really participate through the phases of the effort. Therefore, the plan for MNTNER objects with the NONE authentication scheme is: o Announcement only to db-wg mailing list. (This announcement) o Remove "auth: NONE" attributes from all MNTNER objects, by changing them to a "remarks:" attribute with a URL explaining the change. o If that is the only authentication scheme, update the mntner objects, adding MD5-PW with a generated password. o E-mail the "admin-c:" and "tech-c:" of the objects, and the e-mail addresses listed in the "upd-to:" and "mnt-nfy:" attributes of the objects, explaining the change and including the new password if one is added. o Passwords can be requested via an e-mail to <ripe-dbm(a)ripe.net>. The reply with the password will be sent to the same contacts. After a certain period of time the service will be discontinued. Users wishing to use these maintainers may contact <ripe-dbm(a)ripe.net> for assistance. 3. RIPE-NCC-NONE-MNT A maintainer with NONE authentication, RIPE-NCC-NONE-MNT, was added to objects without any maintainer when the database was converted from RIPE-181 format to RPSL format in April 2001. There is a remark in these objects which includes the following: remarks: The RIPE NCC will never use this maintainer object to remarks: enforce any sort of control over user's objects. It is possible this could have been interpreted to mean that no restriction would ever be added to the object. One use of the RIPE-NCC-NONE-MNT has been to allow the creation of objects representing routing policy for resources not allocated or assigned by the RIPE NCC. This is done by using "mnt-routes: RIPE-NCC-NONE-MNT" or "mnt-lower: RIPE-NCC-NONE-MNT" as appropriate. A new maintainer object will be created for these cases, with a well- known password, published in the object: mntner: RIPE-NCC-RPSL-MNT descr: This maintainer may be used to create objects to represent descr: routing policy in the RIPE Database for number resources not descr: allocated or assigned from the RIPE NCC. admin-c: RD132-RIPE upd-to: ripe-dbm-notify(a)ripe.net auth: MD5-PW $1$GUExyzzy$XQtbZHGVqy9GW8BiAckBV1 remarks: ******************************************************* remarks: * The password for this object is 'RPSL', without the * remarks: * quotes. * remarks: ******************************************************* mnt-by: RIPE-DBM-MNT referral-by: RIPE-DBM-MNT changed: ripe-dbm(a)ripe.net 20040301 source: RIPE The main use of this maintainer is for INETNUM objects. There are approximately 60000 such objects - about 6% of the inetnums. Updates for objects with RIPE-NCC-NONE-MNT are rare, less than 2% of all updates. For objects using RIPE-NCC-NONE-MNT: o If there are other "mnt-by:" attributes it will be changed to a "remarks:" attribute. o Otherwise, the "mnt-by:" will be changed to RIPE-NCC-LOCKED-MNT, which has a locked password (or PGP key). o A "remarks:" attribute will be added explaining how to generate a maintainer. o An e-mail will be sent to the "admin-c:" and "tech-c:" of the objects, and the e-mail addresses listed in the "notify:" attributes of the objects, explaining the change and giving a URL which will help to generate a new maintainer or assign another existing maintainer. o At the URL, the object will be automatically updated to have a new maintainer. o After a certain period of time the service will be discontinued. Users wishing to use these maintainers may contact ripe-dbm(a)ripe.net for assistance. 4. Other maintainers with "auth: NONE" The RIPE-NCC-PN-NONE-MNT was used to mark PERSON objects not to be deleted in the 2001 person cleanup. It can be removed and the maintainer deleted. The LIM-MNT is used for limericks. It will have a well-known password similar to the RPSL maintainer. It will also be maintained by another maintainer (not itself, as currently). -- Ziya Suzen RIPE NCC

4 5

Re: [db-wg] whois_rip feature request, multiple inverse attribute queries needed
by Wilfried Woeber, UniVie/ACOnet 17 Feb '05

17 Feb '05

>To: av(a)nethead.de >CC: db-wg(a)ripe.net >Subject: Re: [db-wg] whois_rip feature request, multiple inverse attribute > queries needed >From: Havard Eidnes <he(a)uninett.no> >Date: Fri, 07 Jan 2005 16:59:42 +0100 (CET) > >> would it be possible to enhance the RDB query in a way that >> multiple inverse queries are possible?! I would like to be able >> to query objects which match a certain set of inverse >> attributes with only one whois-query. > >If I understood the question correctly, that's already possible. > >You can list the multiple attribute names (admin-c, tech-c, etc.) >separated by comma as the argument to the -i query option. > >Regards, > >- Håvard Supplying a list of arguments actually results in a logical .OR. operation. But at 1st reading, my interpretation of the request was a .AND. operation. I think we need more details, please! _________________________________:_____________________________________ Wilfried Woeber : e-mail: Woeber(a)CC.UniVie.ac.at UniVie Computer Center - ACOnet : Tel: +43 1 4277 - 140 33 Universitaetsstrasse 7 : Fax: +43 1 4277 - 9 140 A-1010 Vienna, Austria, Europe : RIPE-DB: WW144, PGP keyID 0xF0ACB369 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

5 5

RE: [db-wg] Draft minutes of DB-WG meeting RIPE 49 V2.0
by Titley, Nigel 19 Jan '05

19 Jan '05

Shane Kerr wrote: > We also plan on having the POEM object type implemented before the > next RIPE meeting, with work on that beginning as soon as the abuse > changes are completed. Excellent.... this is the *really* important work. Glad to see you have it scheduled so promptly. -- Nigel Titley Peering Coordinator, FLAG Telecom +44 20 8564 5812 ********************************************************************** This e-mail message is confidential and is intended only for the use of the individual or entity named above and contains information which is or may be confidential, non-public or legally privileged. Any dissemination or distribution of this message other than to its intended recipient is strictly prohibited. You should not copy it or use it for any purpose nor disclose the contents to any other person. If you have received this message in error, please notify us by email to postmaster(a)flagtelecom.com immediately and delete the original message and all copies from all locations in your computer systems. This e-mail has been swept by Mailsweeper TM for viruses. However, FLAG Telecom cannot accept liability for any damage which you may sustain as a result of software viruses. ********************************************************************** This message has been scanned for viruses by MailControl - www.mailcontrol.com

1 0

Draft minutes of DB-WG meeting RIPE 49 V2.0
by Titley, Nigel 19 Jan '05

19 Jan '05

Gentlefolk, Niall has pointed out some major inaccuracies in the draft minutes, which I have corrected. Apologies for this. However luckily none of the action points have been impacted. Best regards Nigel -- Nigel Titley Peering Coordinator, FLAG Telecom +44 20 7478 9579 ********************************************************************** This e-mail message is confidential and is intended only for the use of the individual or entity named above and contains information which is or may be confidential, non-public or legally privileged. Any dissemination or distribution of this message other than to its intended recipient is strictly prohibited. You should not copy it or use it for any purpose nor disclose the contents to any other person. If you have received this message in error, please notify us by email to postmaster(a)flagtelecom.com immediately and delete the original message and all copies from all locations in your computer systems. This e-mail has been swept by Mailsweeper TM for viruses. However, FLAG Telecom cannot accept liability for any damage which you may sustain as a result of software viruses. ********************************************************************** This message has been scanned for viruses by MailControl - www.mailcontrol.com

3 2

RE: [db-wg] Draft minutes of DB-WG meeting RIPE 49 V2.0
by Wilfried Woeber, UniVie/ACOnet 18 Jan '05

18 Jan '05

Yesterday I had a chat with Rodney T. about the same thing. I'll work with the NCC to come forward with an update on progress. Wilfried. ______________________________________________________________________ From: "Titley, Nigel" <NTitley(a)flagtelecom.com> To: "'MarcoH'" <marcoh(a)marcoh.net>, db-wg(a)ripe.net Subject: RE: [db-wg] Draft minutes of DB-WG meeting RIPE 49 V2.0 Date: Mon, 17 Jan 2005 16:17:21 -0000 MarcoH wrote: >> [AP49.3 RIPE NCC] To produce a document detailing the programme for >> introducing the changes. >> >> [AP49.4 RIPE NCC] To implement the abuse-email: attribute in the >> irt, person and role objects. > > Not that I want to push people, but is there any progress on this > topic or can anybody from the NCC give some indication on when this > is expected to get done ? I would be expecting both of these to be complete by next meeting, in the absence of any response to the contrary by the Ripe NCC. Nigel --

1 0

RE: [db-wg] Draft minutes of DB-WG meeting RIPE 49 V2.0
by Titley, Nigel 17 Jan '05

17 Jan '05

MarcoH wrote: >> [AP49.3 RIPE NCC] To produce a document detailing the programme for >> introducing the changes. >> >> [AP49.4 RIPE NCC] To implement the abuse-email: attribute in the >> irt, person and role objects. > > Not that I want to push people, but is there any progress on this > topic or can anybody from the NCC give some indication on when this > is expected to get done ? I would be expecting both of these to be complete by next meeting, in the absence of any response to the contrary by the Ripe NCC. Nigel -- Nigel Titley Peering Coordinator, FLAG Telecom +44 20 8564 5812 ********************************************************************** This e-mail message is confidential and is intended only for the use of the individual or entity named above and contains information which is or may be confidential, non-public or legally privileged. Any dissemination or distribution of this message other than to its intended recipient is strictly prohibited. You should not copy it or use it for any purpose nor disclose the contents to any other person. If you have received this message in error, please notify us by email to postmaster(a)flagtelecom.com immediately and delete the original message and all copies from all locations in your computer systems. This e-mail has been swept by Mailsweeper TM for viruses. However, FLAG Telecom cannot accept liability for any damage which you may sustain as a result of software viruses. ********************************************************************** This message has been scanned for viruses by MailControl - www.mailcontrol.com

1 0

CVS and Bugzilla for RIPE Whois Server
by RIPE Database Manager 17 Jan '05

17 Jan '05

Dear Colleagues, The RIPE NCC has the source codes of the RIPE Whois Database software available under CVS (a version control system) and is publishing the bugs via Bugzilla (a bug-tracking system). By doing so, this allows anyone to: * have early access to new features of the RIPE Database Whois Server Software and * submit patches to the RIPE Database Whois Server Software. It also provides an easy and accessible method for submitting and tracking bugs and enhancement requests. To accommodate this feature, a web interface is available to browse the source codes at: http://www.ripe.net/cgi-bin/cvsweb.cgi/whoisserver/ while you can submit and track bugs at: http://www.ripe.net/bugzilla/. Stable Source and Binary Releases are available at: ftp://ftp.ripe.net/ripe/dbase/software/. Getting the source codes: You should type the following commands to check out the latest source code under CVS: cvs -d :pserver:anonymous@cvs.ripe.net:/cvsroot login [ No password, so just press [ENTER] on password prompt ] cvs -d :pserver:anonymous@cvs.ripe.net:/cvsroot co whoisserver These commands apply to the command line version of the CVS client software. A directory of CVS clients is available at: http://dmoz.org/Computers/Software/Configuration_Management/Tools/Concurren… Any suggestions about the system can be directed to ripe-dbm(a)ripe.net . Best Regards, Related Links: More information about CVS is available at: http://www.gnu.org/software/cvs/#TOCintroduction More information about Bugzilla is available at: http://www.bugzilla.org/docs/ -- Can Bican RIPE NCC Software Engineering Department

1 0

whois_rip feature request, multiple inverse attribute queries needed
by Arnd Vehling 07 Jan '05

07 Jan '05

Hello, would it be possible to enhance the RDB query in a way that multiple inverse queries are possible?! I would like to be able to query objects which match a certain set of inverse attributes with only one whois-query. Right now i can only query one inverse attribute a time, which means i need to collect all objects which match one of the attributes and then sort out those who match both. This often results in very huge numbers of objects which i need to compare via a perl script. Would this enhancement be reasonable?! best regards, Arnd -- NetHead Network Design and Security Arnd Vehling av(a)nethead.De Gummersbacherstr. 27 Phone: +49 221 8809210 50679 Cologne, Germany Fax : +49 221 8809212

2 1