December 2001 - 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

RE: route object check-up
by Wilfried Woeber, UniVie/ACOnet 28 Dec '01

28 Dec '01

>while updating our database we've noticed some >inconsistency in ripe-db route object: 80.82.178.0/20 >so does anybody know why net and prefix combination for >route object could be invalid ? When the starting address is not properly aligned on a power of 2 for the block-size. The hint you are receiving, as attached below, is an indication for this, i.e. - 80.82.178.0 is only properly aligned for 2 consecutive Class Cs, 80.82.178.0 and 80.82.179.0), - whereas for a /20 (16 consecutive Class Cs) the proper alignment would be 80.82.176.0 Btw, the same issue might eventually arise when someone tries to do an aggregated announcement on the routing layer for this block. Possible solutions: - move the address block to the proper alignment - partiton the block into a set of smaller, consecutive, aligned chunks - try to register the address as a range (although this might trigger the same error message, depending on implementation of checks...) I guess the older versions of the software were less picky than the new implementation is... >With respect, >--- >RIPN Registry center >----- > >-------------------------------------------------------------------- > >Update [FAILED] > >dbupdate: >80.82.178.0/20 is an invalid net and prefix combination:- >length 20 (mask 255.255.240.0) is outside the range of 80.82.178.0 >Possible values with these combinates are: >based on length 80.82.176.0/20 >based on prefix 80.82.178.0/23 Regards, _________________________________:_____________________________________ 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 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

3 2

route object check-up
by Oleg N. Bondarev 28 Dec '01

28 Dec '01

Dear all, while updating our database we've noticed some inconsistency in ripe-db route object: 80.82.178.0/20 so does anybody know why net and prefix combination for route object could be invalid ? With respect, --- RIPN Registry center ----- -------------------------------------------------------------------- Update [FAILED] dbupdate: 80.82.178.0/20 is an invalid net and prefix combination:- length 20 (mask 255.255.240.0) is outside the range of 80.82.178.0 Possible values with these combinates are: based on length 80.82.176.0/20 based on prefix 80.82.178.0/23

1 0

Creating route-objects
by Ionut Murgoci 10 Dec '01

10 Dec '01

Hi, Could somebody tell me how can i create a route-object for an assigned IP class in RPSL format? Thx, Ionut.

2 1

RIPE Database Updates Off-line 2001-12-08
by RIPE Database Administration 09 Dec '01

09 Dec '01

RIPE Database Users: The RIPE database will be operating in query-only mode from 10:00 to 17:00 tommorrow, Saturday, 8 December 2001. Any updates that arrive during this time will be queued, and processed when the database returns to normal operation. All queries will be answered normally by our secondary server. We are adding a new disk to the server due to warnings reported by our SCSI controller. No data has been lost or damaged; this is simply a precaution. Apologies for any inconveniences. Sincerely, -- Shane Kerr RIPE Database Administration

2 1

mnt-routes in allocation objects
by Sabrina Waschke 05 Dec '01

05 Dec '01

Dear all, This is to inform you that the RIPE NCC Registration Services will update all inetnum objects representing allocations made by the RIPE NCC to Local IRs (status: ALLOCATED PA") adding a mnt-routes attribute. We will use the maintainer specified in the mnt-lower attribute of the particular inetnum object. We will only add a mnt-routes attribute to allocation objects that have exactly one mnt-lower attribute (*). The updates will start on Monday, 10th December 2001. Until the introduction of RPSL there was no mnt-routes attribute. Adding a mnt-routes attribute to the inetnum object representing your allocation will enable you to create route objects matching the exact size of your allocation object. (You might have to pass other authorisations.) For a graphical overview of "Route Object Creation - Getting Authorisation from IP Space" please see: <http://www.ripe.net/ripencc/faq/database/route-creation-IP-space-c heck.html>. For more information about route object please read: <http://www.ripe.net/ripe/docs/databaseref-manual.html#1.2.15> and <http://www.ripe.net/ripe/docs/databaseref-manual.html#3.6.5>. (*) In general: If you want to update an object maintained by the RIPE-NCC-HM-MNT please send a message to <lir-help(a)ripe.net> including your registry ID and the revised object. Please note that we only accept these requests from official LIR contacts who are registered in our RIPE NCC internal registry files. If you have any further questions please do not hesitate to contact <lir-help(a)ripe.net> including your registry ID. Kind regards, Sabrina Waschke -- o------------------------------------------o | Sabrina Waschke sabrina(a)ripe.net | | Registration Services Operations Manager | | | | RIPE NCC tel +31 20 535 4444 | | www.ripe.net fax +31 20 535 4445 | o------------------------------------------o

1 0

Can anyone shed some light on this?
by Stephen Burley 05 Dec '01

05 Dec '01

route: 212.249.0.0/16 descr: UUNET CH origin: AS702 mnt-by: AS702-MNT password: ********* changed: jsc(a)ch.uu.net 20011204 source: RIPE I send the above object to the DB and get the following error: New FAILED: [route] 212.249.0.0/16 route: 212.249.0.0/16 descr: UUNET CH origin: AS702 mnt-by: AS702-MNT changed: stephenb(a)uk.uu.net 20011204 source: RIPE ***Error: Hierarchical authorisation failed, request forwarded to maintainer. Objects in RIPE-181 format are no longer accepted. Please see http://www.ripe.net/rpsl for more information. RIPE Database Maintenance Department Which is strange as the mainainer is us AS702-mnt. Any help on this matter whould be appreciated as this is not the only one. Regards Stephen Burley UUNET EMEA Hostmaster SB855-RIPE

4 5

RE: Can anyone shed some light on this?
by Boyan Krosnov 05 Dec '01

05 Dec '01

http://www.ripe.net/ripe/docs/databaseref-manual.html 3.6.5 Protection of route object space The route object creation must satisfy several authentication criteria. It must match the authentication specified in the aut-num and the authentication specified in either a route object or, if no applicable route object is found, then an inetnum. Finally the creation must be authorised by the maintainer of the route object itself referenced by the "mnt-by:" attribute of the object. When checking for prefix authorisation, an exact route object prefix match is checked for first. If there is no exact match, then a longest prefix match that is less specific than the prefix is searched for. If the route prefix search fails, then a search is performed for an inetnum object that exactly matches the prefix or for the most specific inetnum object that is less specific than the route object submission. The aut-num object used for authentication checks is referenced by the "origin:" attribute of the route object. A route object must pass authorisation from both the referenced aut-num object and the route or inetnum object. Authorisation shall be tested using the maintainer(s) referenced in the "mnt-routes:" attribute(s) first. If that check fails, the "mnt-lower:" attributes are checked. If that check fails, the "mnt-by:" attributes are used for the authorisation check. ---------- aut-num: AS702 as-name: AS702 descr: UUNET - Commercial IP service provider in Europe .... mnt-routes: UUNETDK-MNT mnt-routes: AS1270-MNT mnt-routes: AS1849-MNT mnt-routes: AS1890-MNT mnt-routes: IWAY-NOC mnt-by: UUNET-MNT --------- I bet you didn't pass this authorization check. does this shed a light? :) BR, CCNP Boyan Krosnov Network Administrator Lirex Net phone: +359-2-91815 > -----Original Message----- > From: Stephen Burley [mailto:stephenb@uk.uu.net] > Sent: Wednesday, December 05, 2001 12:30 PM > To: lir-wg(a)ripe.net > Cc: db-wg(a)ripe.net > Subject: Can anyone shed some light on this? > > > route: 212.249.0.0/16 > descr: UUNET CH > origin: AS702 > mnt-by: AS702-MNT > password: ********* > changed: jsc(a)ch.uu.net 20011204 > source: RIPE > > I send the above object to the DB and get the following error: > > New FAILED: [route] 212.249.0.0/16 > route: 212.249.0.0/16 > descr: UUNET CH > origin: AS702 > mnt-by: AS702-MNT > changed: stephenb(a)uk.uu.net 20011204 > source: RIPE > ***Error: Hierarchical authorisation failed, request forwarded to > maintainer. > > Objects in RIPE-181 format are no longer accepted. > Please see http://www.ripe.net/rpsl for more information. > > RIPE Database Maintenance Department > > Which is strange as the mainainer is us AS702-mnt. Any help > on this matter > whould be appreciated as this is not the only one. > > Regards > Stephen Burley > UUNET EMEA Hostmaster > SB855-RIPE > > > >

1 0

New Document available: RIPE-201
by RIPE NCC Document Announcement Service 04 Dec '01

04 Dec '01

<Apologies for duplicate mails> New/Revised RIPE Document Announcement -------------------------------------- A revised/new document is available from the RIPE document store. Ref: ripe-201 Title: Routing Registry Consistency Check Author: Joachim Schmitz, Engin Gunduz, Shane Kerr, Andrei Robachevsky, Joao Luis Silva Damas Date: 4 December 2001 Format: PS=33719 TXT=15425 Obsoletes: Obsoleted by: Updates: Updated by: Short content description ------------------------- "Routing Registry Consistency Check" describes a project to crosscheck European Internet routing against data registered in the RIPE Routing Registry. This project was proposed as a new activity by the RIPE Routing Working Group. The document gives an overview of the project, discusses the implementation, and mentions some points that have to be addressed in future design documents. This document is intended to solicit input from interested parties. Accessing the RIPE document store --------------------------------- The RIPE document store is available via anonymous FTP to ftp.ripe.net, in the directory ripe/docs. The URLs for the new documents on the FTP-server are: ftp://ftp.ripe.net/ripe/docs/ripe-201.ps PostScript version ftp://ftp.ripe.net/ripe/docs/ripe-201.txt plain text version You can also access the RIPE documents in HTML format via WWW. RIPE-201 is available at the following URL: http://www.ripe.net/docs/rr-consistencycheck.html

1 0