- db-wg - mailman.ripe.net

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