- db-wg - mailman.ripe.net

Re: AS searching
by Andrei Robachevsky 01 May '01

01 May '01

Dear Hank, Hank Nussbacher wrote: > > I have read over all the documentation and still can't figure out how to > search the RPSL for aut-num objects that have either import or export lines > with ASnnnn. Can anyone give me an example? > Unfortunately, this is not possible via whois queries, as import/export are not lookup attributes. However, you can use "raw text search" to do this. Please try it at http://www.ripe.net/cgi-bin/ripedbsearch. > Thanks, > Hank Regards, Andrei Robachevsky DB Group Manager RIPE NCC

1 0

RE: RETRY: as-set syntax errors ?
by Low, Adam 27 Apr '01

27 Apr '01

Works fine, Many thanks! > -----Original Message----- > From: Engin Gunduz [mailto:engin@ripe.net] > Sent: 27 April 2001 14:49 > To: Low, Adam > Cc: 'kieber(a)gatel.net'; db-wg(a)ripe.net > Subject: RE: RETRY: as-set syntax errors ? > > > > Hi Adam, > > This was a problem in the update path and is fixed yesterday. Now > you should be able to update as-sets (and other object with descr > attributes) with multiple descr attributes. > > Sorry for any inconvenience, > > Best regards, > > Engin Gunduz > RIPE NCC Database Group > > > On Fri, 27 Apr 2001, Low, Adam wrote: > > > Thanks, do you think this is a mistake in the template or > bug in the database ? > > > > > -----Original Message----- > > > From: kieber(a)gatel.net [mailto:kieber@gatel.net] > > > Sent: 27 April 2001 13:46 > > > To: ALow(a)Prioritytelecom.com > > > Cc: db-wg(a)ripe.net > > > Subject: Re: RETRY: as-set syntax errors ? > > > > > > > > > Low, Adam writes: > > > > Sure but the template suggests multiple descr fields > are allowed ? > > > > > > > > descr: [mandatory] [multiple] [ ] > > > > > > > > If this isnt the case, the template should ideally be changed to > > > > avoid confusion. > > > > > > You are right. I didn't cross-check the template, sorry. > > > > > > > > -----Original Message----- > > > > > From: kieber(a)gatel.net [mailto:kieber@gatel.net] > > > > > Sent: 24 April 2001 20:49 > > > > > To: ALow(a)Prioritytelecom.com > > > > > Cc: db-wg(a)ripe.net > > > > > Subject: Re: RETRY: as-set syntax errors ? > > > > > > > > > > > > > > > Low, Adam writes: > > > > > > I seem to be having problems sending in an update for the > > > > > > following object, I've double checked it and I must be > > > > > > missing something, any suggestions ? > > > > > > > > > > > > Update FAILED: Syntax error in object > > > > > > as-set: AS-PRIORITY > > > > > > descr: Priority Telecom AS Macro > > > > > ^^^^^ > > > > > > descr: AS13646 and Global Customers > > > > > ^^^^^ > > > > > > members: AS13646 > > > > > > > > > > > ***Error: single-valued attribute descr occurs > multiple times. > > > > > > > > > > As it says, the descr: attribute is allowed only once in > > > an as-set. > > > > > > > > > > > The only differences to the previous object are the changed > > > > > > fields and the addition of AS10160. > > > > > > > > > > As as-sets are automatically converted from as-macros and > > > descr: was > > > > > allowed multiple times in as-macros you need to get rid of the > > > > > conflict now. > > > > > > -- > > > Ulf Kieber email: kieber(a)gatel.net > > > Network Engineer voice: +49-69-299896-21 > > > Global Access Telecommunications, Inc. fax : +49-69-299896-40 > > > internet solutions for business www : www.gatel.net > > > > > >

1 0

RE: RETRY: as-set syntax errors ?
by Low, Adam 27 Apr '01

27 Apr '01

Thanks, do you think this is a mistake in the template or bug in the database ? > -----Original Message----- > From: kieber(a)gatel.net [mailto:kieber@gatel.net] > Sent: 27 April 2001 13:46 > To: ALow(a)Prioritytelecom.com > Cc: db-wg(a)ripe.net > Subject: Re: RETRY: as-set syntax errors ? > > > Low, Adam writes: > > Sure but the template suggests multiple descr fields are allowed ? > > > > descr: [mandatory] [multiple] [ ] > > > > If this isnt the case, the template should ideally be changed to > > avoid confusion. > > You are right. I didn't cross-check the template, sorry. > > > > -----Original Message----- > > > From: kieber(a)gatel.net [mailto:kieber@gatel.net] > > > Sent: 24 April 2001 20:49 > > > To: ALow(a)Prioritytelecom.com > > > Cc: db-wg(a)ripe.net > > > Subject: Re: RETRY: as-set syntax errors ? > > > > > > > > > Low, Adam writes: > > > > I seem to be having problems sending in an update for the > > > > following object, I've double checked it and I must be > > > > missing something, any suggestions ? > > > > > > > > Update FAILED: Syntax error in object > > > > as-set: AS-PRIORITY > > > > descr: Priority Telecom AS Macro > > > ^^^^^ > > > > descr: AS13646 and Global Customers > > > ^^^^^ > > > > members: AS13646 > > > > > > > ***Error: single-valued attribute descr occurs multiple times. > > > > > > As it says, the descr: attribute is allowed only once in > an as-set. > > > > > > > The only differences to the previous object are the changed > > > > fields and the addition of AS10160. > > > > > > As as-sets are automatically converted from as-macros and > descr: was > > > allowed multiple times in as-macros you need to get rid of the > > > conflict now. > > -- > Ulf Kieber email: kieber(a)gatel.net > Network Engineer voice: +49-69-299896-21 > Global Access Telecommunications, Inc. fax : +49-69-299896-40 > internet solutions for business www : www.gatel.net >

2 1

RE: RETRY: as-set syntax errors ?
by Low, Adam 27 Apr '01

27 Apr '01

Hi Ulf, Sure but the template suggests multiple descr fields are allowed ? descr: [mandatory] [multiple] [ ] If this isnt the case, the template should ideally be changed to avoid confusion. Thanks, Adam > -----Original Message----- > From: kieber(a)gatel.net [mailto:kieber@gatel.net] > Sent: 24 April 2001 20:49 > To: ALow(a)Prioritytelecom.com > Cc: db-wg(a)ripe.net > Subject: Re: RETRY: as-set syntax errors ? > > > Low, Adam writes: > > I seem to be having problems sending in an update for the > > following object, I've double checked it and I must be > > missing something, any suggestions ? > > > > Update FAILED: Syntax error in object > > as-set: AS-PRIORITY > > descr: Priority Telecom AS Macro > ^^^^^ > > descr: AS13646 and Global Customers > ^^^^^ > > members: AS13646 > > > ***Error: single-valued attribute descr occurs multiple times. > > As it says, the descr: attribute is allowed only once in an as-set. > > > The only differences to the previous object are the changed > > fields and the addition of AS10160. > > As as-sets are automatically converted from as-macros and descr: was > allowed multiple times in as-macros you need to get rid of the > conflict now. > > -- > Ulf Kieber email: kieber(a)gatel.net > Network Engineer voice: +49-69-299896-21 > Global Access Telecommunications, Inc. fax : +49-69-299896-40 > internet solutions for business www : www.gatel.net >

2 1

The status of the migration iissues
by Andrei Robachevsky 26 Apr '01

26 Apr '01

Dear Colleagues, As some of you might have noticed, several problems showed up after the migration. Let me present an update on their status: 1. PGP signed messages sent to <auto-rpsl(a)ripe.net> didn't pass authorization checks This was fixed on 24th of April. Please note that PGP signed updates cannot be processed by <auto-dbm(a)ripe.net>. Until 14th of May, <auto-dbm(a)ripe.net> processes updates in RIPE-181 format and automatically translates them into RPSL, which voids PGP signatures. 2. Conversion problems of updates sent to <auto-dbm(a)ripe.net> Problematic objects were: - Objects with syntax errors - Indented objects (containing leading whitespace) In both cases objects were not converted to RPSL and user received an empty acknowledgement. This was fixed today, 26th of April. Please note that <auto-dbm(a)ripe.net> cannot reproduce all the behaviour of the v2 database. In particular, empty attribute is treated as a syntax error and Routing Policy System Security authorization rules apply. We strongly recommend you to switch to updates in RPSL format as soon as possible. Also note, that <auto-dbm(a)ripe.net> will process updates in RIPE-181 format until 14th of May. After that, updates in RIPE-181 format should be sent to the new address, <auto-181(a)ripe.net>, and <auto-dbm(a)ripe.net> will accept only RPSL syntax. 3. Due to above problems some of the updates were not processed. If you haven't received an acknowledgement from the database one day after you sent your update we would kindly ask to re-send it. We apologize for any inconvenience these problems caused. We are working on some minor problems and rely on your understanding. Please visit the "Migration Issues" link on the "Database Status" page (http://www.ripe.net/ripencc/pub-services/db/issues.html) for the up-to-date information. Regards, Andrei Robachevsky DB Group Manager RIPE NCC

3 2

whoisRIP -k
by Frank Bohnsack 26 Apr '01

26 Apr '01

hi, it seems that the new whois client doesn't support the -k option (open/close session (persistent connection)). after a query the connection is holding but the 'client' get no feedback after new queries. i tried this by 'telnet whois.ripe.net 43' and it's works fine. any comments ?! cheers frank

2 1

RETRY: as-set syntax errors ?
by Low, Adam 24 Apr '01

24 Apr '01

Hi, I seem to be having problems sending in an update for the following object, I've double checked it and I must be missing something, any suggestions ? Update FAILED: Syntax error in object as-set: AS-PRIORITY descr: Priority Telecom AS Macro descr: AS13646 and Global Customers members: AS13646 members: AS8758, AS9831, AS8928, AS12684 members: AS12708, AS15426, AS12825, AS4783, AS17108 members: AS9847, AS1742, AS13315, AS11, AS6395 members: AS10160 members: AS-GLOBIX members: AS-GRIDNINE members: AS-NILDRAMUS members: AS-MUNDI members: AS-ELIMNET members: AS-DREAMLINE members: AS-TRUESERVER members: AS-BDXNLBUYERS members: AS-BROADWING tech-c: PTNO1-RIPE admin-c: PTHM1-RIPE notify: hostmaster(a)prioritytelecom.com mnt-by: AS13646-RIPE-MNT changed: alow(a)prioritytelecom.com 20010330 changed: alow(a)prioritytelecom.com 20010402 changed: alow(a)prioritytelecom.com 20010410 changed: alow(a)prioritytelecom.com 20010421 changed: alow(a)prioritytelecom.com 20010424 source: RIPE ***Error: single-valued attribute descr occurs multiple times. The only differences to the previous object are the changed fields and the addition of AS10160. Thanks, Adam _____________________________________________________________ Adam J. Low Tel: +31 20 778 2740 Senior Network Architect Fax: +31 20 778 8601 Priority Telecom Corporate Email: alow(a)prioritytelecom.com

2 1

RE: RETRY: as-set syntax errors ?
by Low, Adam 24 Apr '01

24 Apr '01

The template allows multiple descr fields ? as-set: [mandatory] [single] [primary/look-up key] descr: [mandatory] [multiple] [ ] members: [optional] [multiple] [ ] mbrs-by-ref: [optional] [multiple] [inverse key] remarks: [optional] [multiple] [ ] tech-c: [mandatory] [multiple] [inverse key] admin-c: [mandatory] [multiple] [inverse key] notify: [optional] [multiple] [inverse key] mnt-by: [mandatory] [multiple] [inverse key] changed: [mandatory] [multiple] [ ] source: [mandatory] [single] [ ] > -----Original Message----- > From: Low, Adam [mailto:ALow@Prioritytelecom.com] > Sent: 24 April 2001 20:36 > To: 'db-wg(a)ripe.net' > Subject: RETRY: as-set syntax errors ? > > > Hi, > > I seem to be having problems sending in an update for the > following object, I've double checked it and I must be > missing something, any suggestions ? > > Update FAILED: Syntax error in object > as-set: AS-PRIORITY > descr: Priority Telecom AS Macro > descr: AS13646 and Global Customers > members: AS13646 > members: AS8758, AS9831, AS8928, AS12684 > members: AS12708, AS15426, AS12825, AS4783, AS17108 > members: AS9847, AS1742, AS13315, AS11, AS6395 > members: AS10160 > members: AS-GLOBIX > members: AS-GRIDNINE > members: AS-NILDRAMUS > members: AS-MUNDI > members: AS-ELIMNET > members: AS-DREAMLINE > members: AS-TRUESERVER > members: AS-BDXNLBUYERS > members: AS-BROADWING > tech-c: PTNO1-RIPE > admin-c: PTHM1-RIPE > notify: hostmaster(a)prioritytelecom.com > mnt-by: AS13646-RIPE-MNT > changed: alow(a)prioritytelecom.com 20010330 > changed: alow(a)prioritytelecom.com 20010402 > changed: alow(a)prioritytelecom.com 20010410 > changed: alow(a)prioritytelecom.com 20010421 > changed: alow(a)prioritytelecom.com 20010424 > source: RIPE > ***Error: single-valued attribute descr occurs multiple times. > > The only differences to the previous object are the changed > fields and the addition of AS10160. > > Thanks, > Adam > _____________________________________________________________ > > Adam J. Low Tel: +31 20 778 2740 > Senior Network Architect Fax: +31 20 778 8601 > Priority Telecom Corporate Email: alow(a)prioritytelecom.com >

1 0

as-set syntax errors ?
by Low, Adam 24 Apr '01

24 Apr '01

Hi, I seem to be having problems sending in an update for the following object, I've double checked it and I must be missing something, any suggestions ? as-set: AS-PRIORITY descr: Priority Telecom AS Macro descr: AS13646 and Global Customers members: AS13646 members: AS8758, AS9831, AS8928, AS12684 members: AS12708, AS15426, AS12825, AS4783, AS17108 members: AS9847, AS1742, AS13315, AS11, AS6395 members: AS10160 members: AS-GLOBIX members: AS-GRIDNINE members: AS-NILDRAMUS members: AS-MUNDI members: AS-ELIMNET members: AS-DREAMLINE members: AS-TRUESERVER members: AS-BDXNLBUYERS members: AS-BROADWING tech-c: PTNO1-RIPE admin-c: PTHM1-RIPE notify: hostmaster(a)prioritytelecom.com mnt-by: AS13646-RIPE-MNT changed: alow(a)prioritytelecom.com 20010330 changed: alow(a)prioritytelecom.com 20010402 changed: alow(a)prioritytelecom.com 20010410 changed: alow(a)prioritytelecom.com 20010421 changed: alow(a)prioritytelecom.com 20010424 source: RIPE The only differences to the previous object are the changed fiels and the addition of AS10160. Thanks, Adam _____________________________________________________________ Adam J. Low Tel: +31 20 778 2740 Senior Network Architect Fax: +31 20 778 8601 Priority Telecom Corporate Email: alow(a)prioritytelecom.com

1 0

PGP authentication in the RIPE Database.
by RIPE Database Administration 24 Apr '01

24 Apr '01

Dear Colleagues, PGP updates are now possible again in the RIPE Database. We traced the source of the problem to a subtle bug. Currently, PGP signed messages encoded in quoted-printable text are not supported, but if anyone feels strongly about this, then this mailing list is the appropriate place to discuss it. If you have questions about the operation of the RIPE Database or the software, please contact <ripe-dbm(a)ripe.net>. Regards, A. M. R. Magee ______________ RIPE NCC

2 1