- db-wg - mailman.ripe.net

RIPE DB crash
by Magnus Karlsson 06 Jul '01

06 Jul '01

Yesterday there was a power outage at the NIKHEF. Following this outage the RIPE Database crashed. No objects or updates are lost! There is no need to resend your updates! The database will be fully restored during the day. All updates are queued and will be processed as soon as the database is fully restored. Thank you for your patience. -- Magnus Karlsson, RIPE NCC Database Group

2 1

Problems with WWW Whois ...
by Low, Adam 05 Jul '01

05 Jul '01

Hi, Is anybody working on the WWW whois on www.ripe.net ? I'm having inconsistent problems with numerous browsers, sometimes the query is successful but just as often I get an error message complaining about the URL and specifically the arguments passed to the script. It looks to me that someone's changed the code behind the submit button to add some trailing junk (submit=Submit) that the script cant pass. The Whois arguments are invalid ( AS13646&.submit=Submit+Query ). Please correct The Whois arguments are invalid ( AS13646&.submit= ). Please correct Anyone having problems with or have info ? Thanks, Adam

2 1

Publication of New RIPE Database Doc.
by Paul Rendek 03 Jul '01

03 Jul '01

Dear Colleagues, The RIPE NCC is pleased to announce that this week it will publish the "RIPE Database Reference Manual" on the RIPE NCC website. The new RIPE document is expected to answer many questions of Local Internet Registries and other users regarding the migration to version 3.0 of the RIPE Database software implemented on 23 April 2001. The new RIPE document obsoletes two previous documents: "RIPE Database Documentation Update" (ripe-189) and "RIPE Database Documentation" (ripe-157). The RIPE Database Reference Manual describes the functionality of the new version of the RIPE Database software that now uses the Routing Policy Specification Language (RPSL) to represent all database objects. RPSL defines an extended syntax for all database objects, mainly for the routing registry objects. Many new features have been implemented in this new version, such as Routing Policy System Security (RPSS) support specified in RFC 2725, fast IP lookups and automatic access control. RPSS provides authorisation mechanisms that enable a higher level of security for the Internet Routing Registries. Although the document is self-contained, it does not have examples of usage and illustrations of principles and concepts related to the RIPE Database functionality and implementation. This need will be filled by the "RIPE Database User's Manual" and the "RIPE Database Operations Manual" that are scheduled to be written. For more information and better understanding of the new document, the RIPE NCC encourages readers to brush up on RPSL (explained in RFC 2622), RPSS (explained in RFC 2725) and "Using RPSL in Practice" (the title of RFC 2650). Joao Luis Silva Damas, Chief Technical Officer of the RIPE NCC, wishes to acknowledge the contributions of past and present colleagues in the development of version 3.0 of the RIPE Database software: Andrei Robachevsky, Daniele Arena, Marek Bukowy, Engin Gunduz, Roman Karpiuk, Shane Kerr, A.M.R. Magee, Chris Ottrey and Filippo Portera. Paul Rendek RIPE NCC # # #

2 1

Unprocessed update mails to RIPE Whois Database
by RIPE Database Administration 25 Jun '01

25 Jun '01

Dear Colleagues, [apologies for duplicate messages] Between Thu Jun 14 16:19:15 2001 CEST and Fri Jun 15 10:34:29 2001 CEST, due to a failure in our systems which processes updates to RIPE Whois Database, the update message have not been processed, instead they were only stored. Most of the users who sent those messages noticed that they didn't get any acknowledgement from our system, and re-sent their updates. Realizing the failure on Friday Jun 22, we tried to find out those messages which were _not_ re-sent by the user, and we processed them. Thus, please don't be confused if you've got a late acknowledgement message. If you have any questions about the incident, please contact <ripe-dbm(a)ripe.net>. We are sorry about the inconvenience this caused. Best Regards, Engin Gunduz RIPE NCC Database Group

1 0

AW: AW: DB V3 feature request
by Andres Petralli 21 Jun '01

21 Jun '01

> > The real problem is the internal structs we use in the > software: they don't allow the programmer to change the object's text > representation easily. That's why it requires a biggish effort > to implement this. > If this is so, then we will run into many problems in future. I don't think ip-ranges will be the only things that will need to be stored in the db. Just think of routes, ases, whatever! This behaviour should be possibly avoided. Don't you think it would be wise to solve the problem now? Greets, Andres

1 0

AW: DB V3 feature request
by Andres Petralli 21 Jun '01

21 Jun '01

> a.b.c.d/xx > a.b.c.d 255.255.255.X > a.b.c.d - w.x.y.z > > I do not care if the object created always contains: > > a.b.c.d - w.x.y.z > Absolutely! It makes no sense that ripe changed to this dashed-only notation. I would also very much appreciate if at least the slashed notation would be re-introduced. This kind of notation is much more common than the other one! Greets Andres

3 2

RIPE-181 to RPSL Migration; Phase 2.
by db-news＠ripe.net 20 Jun '01

20 Jun '01

Dear Colleagues, (Apologies for multiple messages). On and from Monday, 14th May, 2001, <auto-dbm(a)ripe.net> shall only accept updates in RPSL format; updates in RIPE-181 format will no longer be accepted. Updates in RIPE-181 format can be sent to <auto-181(a)ripe.net>, where they will be automatically converted to RPSL format. <auto-rpsl(a)ripe.net> will continue to accept updates in RPSL format. The update path for the TEST database will also be changed. In summary, from 14th May, 2001: =============================== RIPE Database: ------------- <auto-dbm(a)ripe.net> - updates in RPSL format only <auto-rpsl(a)ripe.net> - updates in RPSL format only <auto-181(a)ripe.net> - updates in RIPE-181 format, automatically converted to RPS L format TEST Database: ------------- <test-dbm(a)ripe.net> - updates in RPSL format only <test-rpsl(a)ripe.net> - updates in RPSL format only <test-181(a)ripe.net> - updates in RIPE-181 format, automatically converted to RPS L format On Monday, 14th May, 2001, we cannot guarantee that an update message sent to <auto-dbm(a)ripe.net> will use a specific update path (RPSL or RIPE-181). Thus, we advise that updates in RIPE-181 format should be sent to <auto-181(a)ripe.net> and that updates in RPSL format should be sent to <auto-rpsl(a)ripe.net>. Please note that from Monday, 15th October, 2001, updates in RIPE-181 format will no longer be accepted by the RIPE Database. Further information is available from http://www.ripe.net/rpsl/. If you have any questions, please contact <ripe-dbm(a)ripe.net>. Regards, A. M. R. Magee -------------- Database Group RIPE NCC

7 8

cgi-bin/whois?query broken
by Heiko Blume 19 Jun '01

19 Jun '01

hello when inserting objects with <angle brackets> like this: import: from AS1273 action pref=100; accept <AS-ECRC> AND NOT {0.0.0.0/0} the query http://www.ripe.net/cgi-bin/whois?query=AS5427 will not display the data correctly: import: from AS1270 action pref=100; accept AND NOT {0.0.0.0/0} also, AFAIR previously the http output made the 'ASxxx' strings as links to the objects which was very convenient. will we see that again? regards, heiko -- Heiko Blume (HB21) mailto:heiko.blume@iprimus.de iPrimus Telecommunications GmbH http://www.iprimus.de Marienburger Str. 1, D-10405 Berlin Phone: +49.30/443366-0 Fax: -15 Core-l -- If you don't know then you don't need to know

2 1

Another one feature request
by Dmitry Morozovsky 19 Jun '01

19 Jun '01

Hello there colleagues, what about loosing requirements a little for inetnum ranges format? Specifically, do not require spaces around dash in the middle of two IPv4? I.e., 195.91.168.0-195.91.169.255 I suppose could be considered as valid range as 195.91.168.0 - 195.91.169.255 Thank you in advance :) Sincerely, D.Marck [DM5020, DM268-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck(a)rinet.ru *** ------------------------------------------------------------------------

3 3

Help upderstanding error while updating ripe mntner object ...
by Thomas C. Knoeller 19 Jun '01

19 Jun '01

Howdy, Sorry to waste bandwidth, but I was wondering if someone could explain to me this error I am getting while trying to update an object in the ripe database. I am updating a maintainer object, and it seems to get past the authentication state (pgp auth), and the parsing state, but gives me the error: ==== BEGIN PGP SIGNED PART (keyID(s): C9DD67B0) ==== Update FAILED: [mntner] GBLX-RIPE-MNT ***Error: Object is referenced from other objects ==== END PGP SIGNED PART ==== Since this is the maintainer object for the rest of my objects in the database, I would think having it references from other objects would be a good thing. Can you help me understand what I am missing here? Thanks, -Tom

2 1

Another one feature request (or bug report?) Re: (fwd)
by Dmitry Morozovsky 18 Jun '01

18 Jun '01

Hello there colleagues, I suppose it is not so hard to implement ignoring of leading whitespaces in update messages. Just because automatic RIPE-141 checker produce indented objects... Thank you as always for you cooperation. Sincerely, D.Marck [DM5020, DM268-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck(a)rinet.ru *** ------------------------------------------------------------------------ ---------- Forwarded message ---------- Date: Fri, 15 Jun 2001 15:50:14 +0200 (MEST) From: RIPE Database Management <ripe-dbm(a)ripe.net> To: marck(a)rinet.ru Subject: Re: Acknowledgement message from database software Your e-mail: > From: Dmitry Morozovsky <marck(a)rinet.ru> > Cc: > Subject: > Date: Fri, 15 Jun 2001 17:50:00 +0400 (MSD) > Msg-Id: <Pine.BSF.4.21.0106151749460.9594-100000(a)woozle.rinet.ru> has been processed by the automatic update procedure at the RIPE NCC. Diagnostic output follows: ------------------------------------------------------------------------ ==== BEGIN PGP SIGNED PART (keyID(s): 55C20C73) ==== Update FAILED: Syntax error in object inetnum: 195.91.162.208 - 195.91.162.223 netname: RINET-HANNA-NET descr: Development jail block country: RU admin-c: AUTO-1 tech-c: RHM-RIPE status: ASSIGNED PA mnt-by: RINET changed: marck(a)rinet.ru 20010615 source: RIPE ***Error: syntax error ***Error: Unknown class encountered. Update FAILED: Syntax error in object person: Anna E. Losovskaya address: Off. 111, Bld. 11a, 1st Khvostov Lane address: Moscow 109180 RU phone: +7 (095) 916-7009 fax-no: +7 (095) 916-7008 e-mail: hanna(a)rinet.ru nic-hdl: AUTO-1 mnt-by: RINET changed: marck(a)rinet.ru 20010615 source: RIPE ***Error: syntax error ***Error: Unknown class encountered. ==== END PGP SIGNED PART ==== Objects in RIPE-181 format must be sent to <auto-181(a)ripe.net>, which are converted into RPSL format before processing. This will be possible only until October 15, 2001. Please see http://www.ripe.net/rpsl for more information. RIPE Database Maintenance Department

4 3

New mailing list: db-help
by Andrei Robachevsky 15 Jun '01

15 Jun '01

Dear Colleagues, Following the request from the community the RIPE NCC created a new mailing list: db-help(a)ripe.net. The charter of the list is as follows: "The db-help mailing list is provided to facilitate exchange knowledge and expertise about the RIPE Database between more experienced users of the database and less experienced ones. The RIPE NCC provides their input on a best effort basis. In case one expects an answer from the RIPE NCC, the request should be directed to the RIPE Database Administration at ripe-dbm(a)ripe.net." The RIPE NCC will regularly publish the contents of the Database FAQ and other useful information. Put the line "subscribe db-help" in the body of the message to majordomo(a)ripe.net to add your address to the list. Alternatively, you can send the line "help" in the body to get a list of commands accepted by the majordomo mail server. Regards, Andrei Robachevsky DB Group Manager RIPE NCC

1 0

Announcement: RIPE Database software version 3.0.1
by RIPE Database Administration 14 Jun '01

14 Jun '01

Dear Colleagues, [Apologies for multiple messages]. The RIPE NCC is pleased to announce the release of Version 3.0.1 of the RIPE Database software. This software is compliant with both RPSL (RFC-2622) and RPS-Security (RFC-2725). This release is primarily a bug fix release. No new features were added to the server. You can download this release by anonymous FTP from the following URL: ftp://ftp.ripe.net/ripe/dbase/software/ripe-dbase-3.0.1.tar.gz If you do not intend to use the cross-reference files or prefer to build them yourself via "make docs", you can download the source without these files by anonymous FTP from the following URL: ftp://ftp.ripe.net/ripe/dbase/software/ripe-dbase-3.0.1-nocxref.tar.gz A new version of the Whois client is also included with this release, in the utils/whois3 directory. You can also download this client separately by anonymous FTP from the following URL: ftp://ftp.ripe.net/tools/ripe-whois-3.0.tar.gz If you have any more questions, please don't hesitate to contact <ripe-dbm(a)ripe.net>. Regards, --- Shane Kerr Database Software Engineer RIPE NCC

1 0

RE: RPSL route-set/as-set query.
by Low, Adam 11 Jun '01

11 Jun '01

Thanks for that insight, I guess we are going to have to replace our old as-macro/set with a route-set instead then, I wonder if it would be easier to change the RPSL specification than request all our peers to change there policy configurations! (c: Thanks, Adam > -----Original Message----- > From: Andrei Robachevsky [mailto:andrei@ripe.net] > Sent: 11 June 2001 11:49 > To: Low, Adam > Cc: db-wg(a)ripe.net; ripe-dbm(a)ripe.net > Subject: Re: RPSL route-set/as-set query. > > > Dear Adam, > > "Low, Adam" wrote: > > > > Hi Colleagues, > > > > I had a question that I am unable to find an answer for > within the RPSL RFC's, it seems that it is not possible to > nest route-set objects within as-set objects, would this be a > limitation of the RIPE DBM, RPSL or syntax ?! > > > > This is a limitation of RPSL. Members of an as-set are aut-nums and > as-sets. > > However, a route-set members could be prefixes, other > route-sets as well > as aut-nums and as-sets. In such cases an aut-num defines the set of > routes that are originated by that AS and an as-set defines the set of > routes that are originated by the ASes in that as-set. > > > The reason I ask is that we are migrating a customer onto > our network and whilst renumbering we will be advertising > there assigned blocks from another provider. We currently use > as-set's to depict our announcements to peers/providers so > would like to add these to our as-set using a route-set > object without having to replace our as-set object with a > route-set object for our peer/provider announcements. > > > > Thanks, > > Adam > > Regards, > > > Andrei Robachevsky > DB Group Manager > RIPE NCC >

1 0

RPSL route-set/as-set query.
by Low, Adam 11 Jun '01

11 Jun '01

Hi Colleagues, I had a question that I am unable to find an answer for within the RPSL RFC's, it seems that it is not possible to nest route-set objects within as-set objects, would this be a limitation of the RIPE DBM, RPSL or syntax ?! The reason I ask is that we are migrating a customer onto our network and whilst renumbering we will be advertising there assigned blocks from another provider. We currently use as-set's to depict our announcements to peers/providers so would like to add these to our as-set using a route-set object without having to replace our as-set object with a route-set object for our peer/provider announcements. Thanks, Adam

2 1

NAMEREGISTRY.COM - NICS.NET - DOMAINAMES.COM
by BucklesBW＠aol.com 10 Jun '01

10 Jun '01

DOMAIN PRICE 2000nic.net $1,000 800nic.net $1,500 888nic.net $1,500 abbreviaziones.com $3,500 abreger.com $3,000 abreviacao.com $4,500 abreviacao.net n/a abreviacao.org n/a abreviacaos.com $4,500 abreviacaos.net n/a abreviacaos.org n/a abreviacion.com $3,500 abreviaciones.com $4,000 abreviaciones.net n/a abreviar.com $3,000 abreviatura.com $4,000 abreviatura.net n/a abreviaturas.net $3,500 acronimo.net $3,500 acronyme.com $4,000 acronyme.net n/a acronymes.com $4,000 acronymes.net n/a addressmaster.com $3,500 addressregistry.com $12,000 aenic.com $1,500 afix.org $2,000 afrix.com $2,000 ahix.net $2,000 apix.org $2,500 ap-nic.net $2,000 arpanic.com $4,000 arpanic.net n/a arpanic.org n/a artsnic.com $2,500 artsnic.net n/a auix.com $3,000 auix.org n/a autonic.com $4,000 autonic.net n/a aznic.net $1,500 bankdirectory.com $10,000 banknic.net $3,000 bbnic.org $1,500 bdix.net $2,000 bdnic.org $1,500 bhnic.net $2,000 bhnic.org n/a bnnic.com $2,000 bnnic.org n/a boatnic.net $1,500 bonic.org $1,500 brnic.org $1,500 bynic.org $1,500 bznic.net $1,500 carnic.net $3,000 cctld.net $10,000 cctlds.com $15,000 cctlds.net n/a cfpnic.net $2,250 chironic.net $1,750 classifiedchannel.com $10,000 cnix.org $3,500 country-code.com $3,500 country-code.net n/a countrycode.net $4,000 countrycode.org n/a country-codes.com $3,000 countrycodes.net $4,000 countrycodes.org n/a cpanic.net $2,500 cparegistry.com $8,000 cunic.com $2,000 cunic.org n/a cyberegistry.com $5,000 cyberlocation.com $5,000 cybersecurity.com $15,000 cyberswamp.net $5,000 ddsnic.org $1,500 decimals.net $2,500 decimals.org n/a deix.net $2,000 digidomains.com $8,000 diginames.com $4,000 digitaladdress.com $5,000 digitalocation.com $5,000 digitalregistry.com $9,000 digitalwords.com $2,000 dknic.com $1,500 domainame.org $9,500 domainames.com $25,000 domainames.net n/a domainlogic.com $10,000 domainpower.com $13,000 domainshoppe.com $8,000 dznic.org $1,500 ecnic.com $3,500 ecnic.net n/a edunic.com $4,000 edunic.net n/a edunic.org n/a egnic.net $2,000 egnic.org n/a equations.net $4,000 equations.org n/a eurnic.com $3,500 eurnic.org n/a firmnic.com $2,000 firmnic.net n/a fjix.com $2,500 fjix.net n/a fjnic.com $1,500 fmnic.com $2,500 fxnic.com $1,500 gdix.net $2,000 gdnic.com $2,000 gdnic.net n/a grnic.com $1,500 gtnic.net $1,500 gzix.com $2,500 gzix.net n/a gznic.net $2,000 gznic.org n/a hbnic.com $2,500 hbnic.net n/a hbnic.org n/a healthnic.net $2,500 healthregistry.com $4,000 hillarygate.com $4,000 hlthnic.net $1,500 idix.org $2,000 ilix.net $2,000 ilnic.com $2,000 ilnic.net n/a indns.com $4,000 innic.com $4,500 innic.org n/a internetlocation.com $7,000 internetregistry.com $15,000 iprotocol.net $3,500 iqnic.net $1,750 irnic.net $2,000 irnic.org n/a iso3166.com $3,000 iso3166.net n/a iso3166code.com n/a iso-3166code.com n/a iso3166code.net n/a iso3166codes.com n/a iso-3166codes.com n/a iso3166codes.net n/a iso-3166codes.net n/a iso3166countrycode.com n/a iso-3166countrycode.com n/a iso3166countrycodes.com n/a iso-3166countrycodes.com n/a iso3166countrycodes.net n/a itldnic.net $1,500 itlds.com $13,000 itlds.net n/a iwords.net $4,000 jonic.net $1,500 jpix.org $2,000 kgnic.com $1,500 krix.org $2,000 kurzform.com $4,500 kurzform.net n/a kurzform.org n/a kwnic.com $2,500 kwnic.net n/a kwnic.org n/a laix.net $2,500 laix.org n/a lawnic.net $3,250 lawregistry.com $10,000 managedcare.org $10,000 mdnic.net $5,000 mednic.net $3,750 mednic.org n/a milnic.com $4,000 milnic.net n/a mindaddress.com $1,750 mnnic.com $1,500 moix.net $2,500 moix.org n/a movienic.org $1,500 myix.net $3,500 myix.org n/a name4sale.com $5,000 namechannel.com $6,000 namegiver.com $6,000 namehouse.com $4,000 namehut.com $6,000 namelogic.com $10,000 namemaster.com $10,000 nameregistry.com $18,000 namescape.com $10,000 nameservice.com $12,000 nameshoppe.com $6,000 namewarehouse.com $5,000 nanic.net $2,000 nanic.org n/a negatives.net $3,500 negatives.org n/a netlocation.com $10,000 newsnic.net $2,500 ngnic.net $1,500 nics.net $18,000 nlnic.com $2,000 ntlds.com $13,000 ntlds.net n/a numeral.net $3,000 numerals.net $3,000 numerals.org n/a numnic.com $1,750 numnic.net n/a orgnic.net $2,750 palabras.org $2,000 perfectdomains.com $10,000 perfectnames.com $6,000 perfectwords.com $2,000 phix.org $2,000 phnic.com $1,500 pknic.org $1,500 premierdomains.com $10,000 premiernames.com $6,000 premierwords.com $2,000 previewchannel.com $13,000 prnic.org $1,750 ptnic.net $1,500 qanic.com $1,750 qualitynames.com $6,000 qualitywords.com $2,000 recnic.org $2,000 ripe.org $6,000 ruix.com $3,000 ruix.net n/a ruix.org n/a runic.net $1,500 rxnic.com $2,750 rxnic.net n/a rxnic.org n/a sanic.org $1,500 sgix.net $3,500 sgix.org n/a shopnic.com $2,750 shopnic.net n/a siglas.net $4,000 siglas.org n/a storenic.com $2,750 storenic.net n/a strategicwords.com $2,000 superiordomains.com $10,000 superiornames.com $6,000 superiorwords.com $2,000 synic.net $1,500 thix.org $2,000 tjnic.com $2,000 tjnic.org n/a tmnic.com $3,000 tmnic.org n/a tpnic.org $1,500 trnic.org $1,500 tvdirectory.com $15,000 twnic.org $2,000 uanic.org $1,500 unnic.net $1,500 usadns.com $8,000 usadns.net n/a usaix.net $5,000 usaix.org n/a usanic.org $3,000 usanoc.com $4,000 usanoc.net n/a usnic.com $10,000 usnic.org n/a usnoc.net $4,000 uynic.com $1,500 uznic.com $1,500 venic.net $1,500 virtual-broker.com $8,000 vnix.net $2,500 vnix.org n/a vnnic.org $1,500 webword.net $5,000 wordbroker.com $2,000 wordirectory.com $4,000 wordlisting.com $3,000 wordlistings.com $3,000 wordshoppe.com $3,000 wordwarehouse.com $2,000 wordwizards.com $2,000 zaix.net $2,000 zanic.net $2,000 zanic.org n/a zjix.com $2,500 zjix.net n/a zjnic.com $2,500 zjnic.net n/a zjnic.org n/a zmnic.org $1,500 "N/A" indicates that the domain is part of a package. Contact: Brian Buckles 217-787-1701

1 0

analysis of changed flag
by Frank Bohnsack 31 May '01

31 May '01

Dear Colleagues, As global ISP we need to mirror all important IRRs like RIPE, ARIN and APNIC. Many object are registerd in more than one IRRs. Currently we decide which object is valid based on the last 'changed' flag (Ok we could compare the complete object but it is possible to have different version on each IRR). But it seems that this flag isn't really in use ;-( Could it be an option to check this flag on each update ? cheers frank here one example ... old version: > aut-num: AS12437 > as-name: UNSPECIFIED > descr: ICSmedia GmbH > descr: Full Service Internet Provider > descr: Muenster (Germany) > import: from AS6754 > action pref=100; > accept ANY > import: from AS8638 > action pref=100; > accept AS8638 > import: from AS1270 > action pref=100; > accept ANY > export: to AS6754 > announce AS12437 > export: to AS8638 > announce AS12437 > export: to AS1270 > announce AS12437 > default: to AS6754 > action pref=100; > networks ANY > admin-c: HR29-RIPE > tech-c: HR29-RIPE > mnt-by: ICSMEDIA-MNT > changed: hostmaster(a)ripe.net 19990520 > source: RIPE last version: > aut-num: AS12437 > as-name: ICSMEDIA-DE > descr: ICSmedia GmbH > descr: Full Service Internet Provider > descr: Muenster (Germany) > import: from AS6754 > action pref=100; > accept ANY > import: from AS8638 > action pref=100; > accept AS8638 > import: from AS1270 > action pref=100; > accept ANY > import: from AS702 > action pref=100; > accept ANY > export: to AS6754 > announce AS12437 > export: to AS8638 > announce AS12437 > export: to AS1270 > announce AS12437 > export: to AS702 > announce AS12437 > default: to AS6754 > action pref=100; > networks ANY > admin-c: HI638-RIPE > tech-c: HI638-RIPE > mnt-by: ICSMEDIA-MNT > changed: hostmaster(a)ripe.net 19990520 > source: RIPE

1 0

Questions on mirroring RIPE
by Andy Linton 31 May '01

31 May '01

In preparation for getting a RIPE mirror running at APNIC, I copied a copy of the RIPE database and started the loader scripts on this. That was 73 hours ago and we're still on the first pass through. At this stage the logfile recording the load is 182592742 bytes long and the the directory holding the MySQL database is 1063916 Kbytes in size. Will this job finish within the next week, month, year...? Since we're running the RPSL code I took the snapshot from /ripe/dbase3/snapshot. Was that a good call? Would an alternative option for priming a v3 server be to make a compressed snapshot of the MySQL database and remove the need to load the raw data into the MySQL database via the server? I suspect the machine we're using is too small for the task - any recommendations on minimum configurations? Should we give up until we've got a bigger machine or RIPE staff do the promised spring clean of the data (or both)? Answers appreciated. andy

4 3

Announcement: PGPi 5.0 licences
by Andrei Robachevsky 21 May '01

21 May '01

Dear Colleagues, Following the discussion at the RIPE-39 meeting, Aril 30 - May 4 2001, the RIPE NCC will discontinue issuing licenses for PGPi 5.0 software. No licenses will be issued after June 1, 2001. There are two main reasons for such decision: 1. The PGPi 5.0 software contains several bugs that may compromise the security of the generated keys. The RIPE NCC can issue licenses only for this version of the software. 2. The v3 of the RIPE Database supports GnuPG (GNU Privacy Guard) software, which is available free of charge and is proved to be a reliable and secure software. To learn more about GnuPG software, please visit http://www.gpg.org. Regards, Andrei Robachevsky DB Group Manager RIPE NCC

2 2

db-help Mailinglist
by Hank Hampel 18 May '01

18 May '01

Hi there! I just want to ask if there is going to be a db-help mailinglist to reduce the unnecessary traffic to hostmaster(a)ripe.net and to shorten the wait queue. I think this mailinglist would really be helpfull - at least if it's existence will be propagated at a prominent place (i.e. the RIPE website). Because nowadays many people tend not to actually read documentation and instead use the "easy" way of just asking questions to any mailaddress that seems suitable (and even to those not so suitable). Even so I think a FAQ and a step-by-step documentation of the "10 most frequent actions with the RIPE DB" is really a good idea I think we should also create this mailinglist - and if it's just for the sake of pointing people to the right documents. ;) So I propose, to get things going, to have something like a strawpoll/show of hands who is willing to participate on such a mailinglist. Count this mail as the first hand up. ;) Sincerely yours, Hank

2 1

route-set members
by Frank Bohnsack 17 May '01

17 May '01

Dear Colleagues, I have a simple question about route-set objects. <--RFC2622--> ... 5.2 route-set Class The attributes of the route-set class are shown in Figure 12. The route-set attribute defines the name of the set. It is an RPSL name that starts with "rs-". The members attribute lists the members of the set. The members attribute is a list of address prefixes or other route-set names. Note that, the route-set class is a set of route prefixes, not of RPSL route objects. ... </--RFC2622--> 1/ What is the reason that a route-set member can not be an aut-num or as-set object ? Because some registries allow this: route-set: RS-AS101-TO-ABILENE descr: routes that Abilene should accept from AS101 members: AS73, AS11808, AS7774, AS3807, AS13476, AS11995, AS14077, AS13476, AS11964, AS11827, 131.107.151.0/24, 131.252.0.0/16, 134.39.60.0/24, 161.55.0.0/16, 168.156.80.0/20, 168.156.96.0/19, 192.35.180.0/24, 192.46.80.0/24, 198.107.144.0/21, 198.32.40.0/24 admin-c: UW-NOC tech-c: UW-NOC mnt-by: MAINT-AS73 changed: aracine(a)cac.washington.edu 20010426 source: RADB 2/ Means the last phrase that there are no necessary is to existence of a related route object ? cheers frank

3 2

Inetnum Object
by Simeoli Enrico 17 May '01

17 May '01

Hi, I have some problem to make new registration at RIPE NCC DB from some allocated range because in the DB there is not its related inetnum object (for i.e 151.39.0.0/16). I know that this object is created by the RIPE at the first assignment, but I will already use this range because it was allocated to us by the ARIN in the past and we had made some assignment for our dial-up users without problem with the old Ripe-181 format. Now when we try to make a new registration we receive the following > message: > > > Acknowledgement message from database software > > Your e-mail: > > > From: "Infostrada Staff Internet" <staff(a)iunet.it > > <mailto:staff@iunet.it>> > > > Cc: > > > Subject: Aggiornamento > > > Date: Fri, 11 May 2001 16:29:24 +0200 > > > Msg-Id: <031d01c0da26$d913a690$19391197(a)infostrada.it > > <mailto:031d01c0da26$d913a690$19391197@infostrada.it>> > > > > has been processed by the automatic update procedure at the RIPE NCC. > > Diagnostic output follows: > > > > ------------------------------------------------------------------------ > > > > > > New FAILED: [inetnum] 151.39.51.0 - 151.39.51.255 > > Hierarchical authorisation failed, request forwarded to maintainer. > > > > New FAILED: [inetnum] 151.39.0.0 - 151.39.255.255 > > Hierarchical authorisation failed, request forwarded to maintainer. > > > > Update messages to <auto-dbm(a)ripe.net <mailto:auto-dbm@ripe.net>> are > > converted into > > RPSL format before processing. This will continue until > > May 14, 2001. Please see <http://www.ripe.net/rpsl> for > > more information. Can you tell me what I can do? Best regards

2 1

RIPE DB vs. IRRd
by Dmitry Safronov 16 May '01

16 May '01

Hello! Could you please describe the difference between RIPE DB and IRRd? Is there a necessity of moving to the RIPE DB version from IRRd? Thank you. -- Best regards, _____________________________________________________________________ Dmitry Safronov Rostelecom/Internet Centre Russia Tel: +007 (095) 334-9983 Fax: +007 (095) 339-2415

1 0

RIPE-181 to RPSL Migration; Completed switch-over to phase 2
by DB-News 14 May '01

14 May '01

Dear Colleagues, (Apologies for multiple messages). This is to announce that we have completed the phase 1 of migration. Starting from today, Monday, 14th May, 2001, <auto-dbm(a)ripe.net> shall only accept updates in RPSL format; updates in RIPE-181 format will no longer be accepted. Updates in RIPE-181 format can be sent to <auto-181(a)ripe.net>, where they will be automatically converted to RPSL format. <auto-rpsl(a)ripe.net> will continue to accept updates in RPSL format. The update path for the TEST database has also been changed. In summary, from 14th May, 2001: =============================== RIPE Database: ------------- <auto-dbm(a)ripe.net> - updates in RPSL format only <auto-rpsl(a)ripe.net> - updates in RPSL format only <auto-181(a)ripe.net> - updates in RIPE-181 format, automatically converted to RPSL format TEST Database: ------------- <test-dbm(a)ripe.net> - updates in RPSL format only <test-rpsl(a)ripe.net> - updates in RPSL format only <test-181(a)ripe.net> - updates in RIPE-181 format, automatically converted to RPSL format Please note that from Monday, 15th October, 2001, updates in RIPE-181 format will no longer be accepted by the RIPE Database. Further information is available from http://www.ripe.net/rpsl/. If you have any questions, please contact <ripe-dbm(a)ripe.net>. Regards, Engin Gunduz ____________________________ RIPE Database Administration.

1 0

RIPE-181 to RPSL Migration; Phase 2.
by DB-News 10 May '01

10 May '01

Dear Colleagues, (Apologies for multiple messages). On and from Monday, 14th May, 2001, <auto-dbm(a)ripe.net> shall only accept updates in RPSL format; updates in RIPE-181 format will no longer be accepted. Updates in RIPE-181 format can be sent to <auto-181(a)ripe.net>, where they will be automatically converted to RPSL format. <auto-rpsl(a)ripe.net> will continue to accept updates in RPSL format. The update path for the TEST database will also be changed. In summary, from 14th May, 2001: =============================== RIPE Database: - ------------- <auto-dbm(a)ripe.net> - updates in RPSL format only <auto-rpsl(a)ripe.net> - updates in RPSL format only <auto-181(a)ripe.net> - updates in RIPE-181 format, automatically converted to RP S L format TEST Database: - ------------- <test-dbm(a)ripe.net> - updates in RPSL format only <test-rpsl(a)ripe.net> - updates in RPSL format only <test-181(a)ripe.net> - updates in RIPE-181 format, automatically converted to RP S L format On Monday, 14th May, 2001, we cannot guarantee that an update message sent to <auto-dbm(a)ripe.net> will use a specific update path (RPSL or RIPE-181). Thus, we advise that updates in RIPE-181 format should be sent to <auto-181(a)ripe.net> and that updates in RPSL format should be sent to <auto-rpsl(a)ripe.net>. Please note that from Monday, 15th October, 2001, updates in RIPE-181 format will no longer be accepted by the RIPE Database. Further information is available from http://www.ripe.net/rpsl/. If you have any questions, please contact <ripe-dbm(a)ripe.net>. Regards, A. M. R. Magee - -------------- Database Group RIPE NCC

1 0