- db-wg - mailman.ripe.net

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

draft agenda routing/joint routing&db wg RIPE 39
by SchmitzJo＠aol.com 24 Apr '01

24 Apr '01

Dear colleagues, please find enclosed the first draft of the agenda for the session of the routing working rgoup at RIPE 39, Bologna. The session will be held Wednesday, 2-May, 14:00 Routing WG session Due to the importance of the subject and because it is affecting both working groups we are having again a joint session of the routing and database groups on the same day in the 2nd afternoon slot. Wednesday, 2-May, 16:00 Joint routing/db WG session I would also like to direct your attention to two interesting tutorials: For more information on these two tutorials, please refer to the RIPE meeting web pages. Monday, 30-Apr, 9:00 Full day tutorial on MPLS by Clarence Filsfils (Cisco) Tuesday, 1-May, 9:00 Half day tutorial on the RAToolSet by Cengiz Allaettinoglu (Packetdesign) As usual comments, additions, changes to the agenda of the Routing WG welcome! ---- R I P E 3 9 B O L O G N A Routing Working Group Session A. Preliminaries (Joachim Schmitz) (5min) - introduction - participants' list - volunteering of scribe - agenda bashing - RIPE 37 minutes - actions from earlier meetings B. Cengiz Allaettinoglu: Observations on ISIS Convergence (30min) C. Philip Smith: Update on RIPE-210 (Route Flap Damping) (20min) - update - discussion D. Henk Uijterwaal: Update from the RIS Project (15min) Joint Session with the Database WG E. Andrei Robachevsky: Migration to the new RIPE database (20min) F. Cengiz Allaettinoglu: Application of the RAToolSet (open end) Y. Input from other WGs Z. AOB ---- Thanks Joachim --- JS395-RIPE -- standard disclaimer ---

1 0

draft agenda (v1), for DB-WG meeting, RIPE 39, Bologna
by Wilfried Woeber, UniVie/ACOnet 23 Apr '01

23 Apr '01

Dear DB-WG list members, fellow chair persons, dear "meeting" account! Attached please find the 1st draft, proposed agenda for the DB-WG Meeting in Bologna, IT. As usual, comments, suggestions and additions are welcome. As a test (please let me know what you think!), any updates to the draft agenda and some supporting information can be found at http://members.aon.at/netcraft/DB-WG/d-agenda.html Looking forward to see many of you in Bologna, Wilfried. ______________________________________________________________________ Proposed Agenda for the Database Working Group Meeting RIPE-39, April 30-May 4 2001, Bologna, IT 1. Draft Wednesday, May 2nd, 2001 16:00 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Part 1: Joint Session with Routing-WG Thursday, May 3rd, 2001 09:00 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Part 2: DB-WG Meeting A. Administrative stuff (WW, chair) . volunteering a scribe . list of participants . agenda bashing . minutes distributed B. Actions Items . C. DB operations update (RIPE NCC, Andrei Robachevsky) 20min D. Report from Re-Implementation/Migration TF (tentative, Ulf Kieber, DB Group) 15 min E. "orphaned" person objects, potential legal implications (RIPE NCC, Joao LS Damas) 15 min F. Enhancements to IRRd to support an SQL backend, et.al. (Global Crossing and TimesTen, Jake Khuon) 30 min G. 'force:' attribute for changing a 'person:' object (tcpip-gmbh, Carsten Schiefner) 15 min H. Legacy object migration from ARIN to RIPE NCC (& APNIC) (tentative, N.N.) 20 min PI.Y. Input from other WGs . PI.Z. AOB: . ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ WW, 23-Apr-2001 19:20 UTC _________________________________:_____________________________________ 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 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1 0

PGP auth?
by Gert Doering 23 Apr '01

23 Apr '01

Hi, with the old RIPE DB, PGP auth did only work with "inline" signatures (the "classic" PGP way), not with "MIME/multipart" signatures (the way "mutt" does them, and maybe other programs, and as this e-mail is signed). I remember that the new DB software was supposed to do MIME, and also MIME/multipart PGP, but it didn't work when I tried that ("request denied, forwarded to maintainer"). Could you please elaborate what the current state regarding MIME and/or PGP support is? thanks, Gert Doering -- NetMaster -- SpaceNet AG Mail: netmaster(a)Space.Net Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0 80807 Muenchen Fax : +49-89-32356-299

2 1

Re: New DB and line continuation?
by Andrei Robachevsky 23 Apr '01

23 Apr '01

Dear Berislav, Berislav Todorovic wrote: > > On Mon, 23 Apr 2001, DB-News wrote: > > >> The new version of the RIPE Database is now up and running! > >> All objects have been automatically converted to RPSL and loaded into > >> the new version of the Database. > > Congratulations! However, I have a question: > > When an attribute needs multiple lines to be described, the standard > RPSL format requires the attribute name to be mentioned once, while > successive lines are separted by spaces or commas (like you defined > in the transition document as well). It used to be like that in the > previous version of rpsl.ripe.net. However, right now, it seems to > me there is a strange RIPE-181/RPSL mix in place. See example: > Indeed, we tried to introduce as little changes to objects look as possible, while staying RPSL compliant. In fact, RPSL defines members attribute as: Attribute Value Type as-set <object-name> mandatory, single-valued, class key members list of <as-numbers> or optional, multi-valued <as-set-names> which means that one can have multiple 'members:' attribute, each of them may have a list of members separated by commas. So, formally there is no RPSL syntax violation. You can update your object to make it look like in RADB, both examples are accepted and valid in the RIPE database. Regards, Andrei > * RADB and old REIMP.RIPE (standard RPSL): > > [beri@nix00 ~]$ rwhois -h whois.ra.net as-kq > as-set: AS-KQ > descr: KPNQwest European routes > Formerly AS-EUNET AND NOT AS-EUNETQWEST > members: AS286, AS719, AS1136, AS1137, AS1213, > AS1234, AS1889, AS1891, AS1902, AS2043, > AS2049, AS2110, AS2135, AS2857, AS3220, > ... > > * RIPE (new format, RPSL): > > as-set: AS-KQ > descr: KPNQwest European routes > descr: Formerly AS-EUNET AND NOT AS-EUNETQWEST > members: AS286, AS719, AS1136, AS1137, AS1213, AS1234, AS1889 > members: AS1891, AS1902, AS2043, AS2049, AS2110, AS2135, AS2857 > members: AS3220, AS3246, AS3262, AS3265, AS3286, AS3324, AS3333 > members: AS3347, AS3615, AS5385, AS5399, AS5403, AS5407, AS5419 > > While some of you might think this is not important, this is VERY > important to some of us who make scripts for automating our tasks with > the RIPE DB. > > Can anyone explain the reason of this RPSL syntax violation? Thanks! > > Regards, > Beri > > --------- Berislav Todorovic, Network Engineer --------- > ------- KPNQwest N.V. - IP NOC (formerly EUnet NOC) ------- > ---- Wilhelmina van Pruisenweg 78, 2595 AN Den Haag, NL ---- > --- Phone: +31-70-379-3990; Mobile: +31-651-333-641 --- > -- Email: beri(a)kpnqwest.net <=> beri(a)EU.net -- > --- _ _ ____ _ .--. ____ ____ __/_ --- > ----- /__/ /___/ /\ / / / | / /___/ /___ / ------ > ------ _/ \_ / _/ \/ (__.\ |/\/ /___ ____/ (__. ----- -- Andrei Robachevsky DB Group Manager RIPE NCC

1 0

update problems with auto-dbm@ripe.net
by Frank Bohnsack 23 Apr '01

23 Apr '01

Dear colleagues, Our last aut-num update doen't accepted from auto-dbm(a)ripe.net ;-( It seems that there is a problems with password authentification and/or legacy RIPE-181 attributes. Please let me know whats wrong ... cheers Frank > -----Original Message----- > From: RIPE Database Management [mailto:ripe-dbm@ripe.net] > Sent: Monday, April 23, 2001 11:04 AM > To: mz(a)de.uu.net > Subject: Re: LONGACK AS1270 > > > > Acknowledgement message from database software > > > Your e-mail: > >> From: "Martin Ziegler" <mz(a)de.uu.net> >> Cc: >> Subject: LONGACK AS1270 >> Date: Mon, 23 Apr 2001 11:04:47 +0200 >> Msg-Id: <GMEGIAOLKNDLPJFCBJGLKEDDCCAA.mz(a)de.uu.net> > > has been processed by the automatic update procedure at the RIPE NCC. > Diagnostic output follows: > > ------------------------------------------------------------------------ > > > Update FAILED: Syntax error in object > password: ******** > ***Error: syntax error > ***Error: Unknown class encountered. > > Update FAILED: Syntax error in object > ***Error: syntax error > aut-num: AS1270 > as-name: UUNET-DE > descr: UUNET Germany > as-in: from AS517 100 accept AS-KQ > as-in: from AS553 100 accept AS-BELWUE > as-in: from AS680 100 accept AS-DFNTOWINISP > as-in: from AS1273 100 accept AS-ECRC > as-in: from AS1275 100 accept AS1275 > as-in: from AS1889 100 accept AS1889 > as-in: from AS2125 100 accept AS2125 > as-in: from AS2686 100 accept AS-IGNEMEA > as-in: from AS2871 100 accept AS-ISION > as-in: from AS3257 100 accept AS-NACAMAR AS5459 AS-NDH > as-in: from AS3320 100 accept AS-DTAG > as-in: from AS3569 100 accept AS3569 > as-in: from AS3573 100 accept AS3573 > as-in: from AS5378 100 accept AS-INSNET > as-in: from AS5401 100 accept AS-POP > as-in: from AS5427 100 accept AS-CONTRIBNET > as-in: from AS5430 100 accept AS-MOBILCOM > as-in: from AS5496 100 accept AS-WIREHUB > as-in: from AS5521 100 accept AS-CITYLINE > as-in: from AS5539 100 accept AS-SPACENET > as-in: from AS5549 100 accept AS-TELENOR > as-in: from AS5605 100 accept AS5605 > as-in: from AS5621 100 accept AS-CPSEUROPE > as-in: from AS5627 100 accept AS5627 > as-in: from AS6705 100 accept AS-PROFI > as-in: from AS6735 100 accept AS-SDTDECIX AS-SDTMAEF > as-in: from AS6754 100 accept AS-VIA > as-in: from AS8072 100 accept AS8072 > as-in: from AS8196 100 accept AS-NETSCALIBURDE > as-in: from AS8208 100 accept AS-CAMELOT > as-in: from AS8220 100 accept AS-COLT > as-in: from AS8298 100 accept AS-IDNET > as-in: from AS8319 100 accept AS-IXREGIO > as-in: from AS8351 100 accept AS8351 > as-in: from AS8354 100 accept AS8354 > as-in: from AS8360 100 accept AS8360 > as-in: from AS8373 100 accept AS8373 > as-in: from AS8379 100 accept AS-CYBERNETEU > as-in: from AS8397 100 accept AS-ZETNET > as-in: from AS8422 100 accept AS-NETCOLOGNE > as-in: from AS8442 100 accept AS8442 > as-in: from AS8469 100 accept AS-PIRONETNDH > as-in: from AS8477 100 accept AS-TESIONGLOBAL AS-SWCMGLOBAL > as-in: from AS8602 100 accept AS8602 > as-in: from AS8650 100 accept AS-TLI > as-in: from AS8735 100 accept AS8735 > as-in: from AS8767 100 accept AS-MNETDE > as-in: from AS8794 100 accept AS8794 > as-in: from AS8827 100 accept AS8827 > as-in: from AS8852 100 accept AS-GINKO > as-in: from AS8864 100 accept AS8864 > as-in: from AS8879 100 accept AS8879 > as-in: from AS8925 100 accept AS-TEUTOCLIENTS > as-in: from AS8939 100 accept AS-ADTECH > as-in: from AS8950 100 accept AS8950 > as-in: from AS8957 100 accept AS8957 > as-in: from AS9007 100 accept AS9007 > as-in: from AS9059 100 accept AS9059 > as-in: from AS9066 100 accept AS-BCC > as-in: from AS9067 100 accept AS9067 > as-in: from AS9072 100 accept AS-NEFKOM > as-in: from AS9099 100 accept AS9099 > as-in: from AS9164 100 accept AS9164 > as-in: from AS9175 100 accept AS9175 > as-in: from AS9188 100 accept AS9188 AS9067 > as-in: from AS11660 100 accept AS11660 > as-in: from AS12288 100 accept AS12288 > as-in: from AS12291 100 accept AS12291 > as-in: from AS12292 100 accept AS-TRANSKOM > as-in: from AS12313 100 accept AS-VERSATELDE AS-VERSATELCUSTDE > as-in: from AS12331 100 accept AS12331 > as-in: from AS12343 100 accept AS12343 > as-in: from AS12355 100 accept AS12355 > as-in: from AS12371 100 accept AS12371 > as-in: from AS12379 100 accept AS12379 > as-in: from AS12437 100 accept AS12437 > as-in: from AS12466 100 accept AS12466 > as-in: from AS12470 100 accept AS12470 AS-TLKNET AS15909 > as-in: from AS12531 100 accept AS12531 > as-in: from AS12532 100 accept AS-DIZ > as-in: from AS12555 100 accept AS12555 > as-in: from AS12574 100 accept AS12574 > as-in: from AS12581 100 accept AS-TOPSNET > as-in: from AS12595 100 accept AS12595 > as-in: from AS12598 100 accept AS12598 > as-in: from AS12610 100 accept AS12610 > as-in: from AS12612 100 accept AS12612 > as-in: from AS12625 100 accept AS12625 > as-in: from AS12638 100 accept AS12638 > as-in: from AS12643 100 accept AS12643 > as-in: from AS12647 100 accept AS12647 > as-in: from AS12664 100 accept AS12664 > as-in: from AS12678 100 accept AS12678 > as-in: from AS12722 100 accept AS12722 > as-in: from AS12796 100 accept AS12796 > as-in: from AS12813 100 accept AS-WORNET > as-in: from AS12853 100 accept AS12853 > as-in: from AS12857 100 accept AS12857 > as-in: from AS12886 100 accept AS-LEWTELNET > as-in: from AS12888 100 accept AS12888 > as-in: from AS12892 100 accept AS12892 > as-in: from AS12899 100 accept AS12899 > as-in: from AS12915 100 accept AS12915 > as-in: from AS12916 100 accept AS12916 > as-in: from AS12919 100 accept AS12919 > as-in: from AS12930 100 accept AS12930 > as-in: from AS13003 100 accept AS13003 > as-in: from AS13006 100 accept AS13006 > as-in: from AS13012 100 accept AS13012 AS15456 > as-in: from AS13039 100 accept RS-NEW > as-in: from AS13040 100 accept AS13040 > as-in: from AS13043 100 accept AS13043 > as-in: from AS13045 100 accept AS13045 AS15790 > as-in: from AS13083 100 accept AS13083 > as-in: from AS13090 100 accept AS13090 AS15492 > as-in: from AS13101 100 accept AS-TNG > as-in: from AS13129 100 accept AS-GAT > as-in: from AS13152 100 accept AS13152 > as-in: from AS13157 100 accept AS13157 > as-in: from AS13237 100 accept AS13237 > as-in: from AS13247 100 accept AS13247 > as-in: from AS13270 100 accept AS13270 > as-in: from AS15374 100 accept AS15374 > as-in: from AS15392 100 accept AS15392 > as-in: from AS15438 100 accept AS15438 > as-in: from AS15465 100 accept AS15465 > as-in: from AS15486 100 accept AS15486 > as-in: from AS15563 100 accept AS15563 > as-in: from AS15579 100 accept AS15579 > as-in: from AS15622 100 accept AS15622 > as-in: from AS15698 100 accept AS15698 > as-in: from AS15709 100 accept AS15709 > as-in: from AS15763 100 accept AS15763 > as-in: from AS15781 100 accept AS15781 > as-in: from AS15813 100 accept AS15813 > as-in: from AS15889 100 accept AS15889 > as-in: from AS15894 100 accept AS15894 > as-in: from AS15904 100 accept AS15904 AND AS9115 > as-in: from AS15933 100 accept AS15933 > as-in: from AS15968 100 accept AS15968 > as-in: from AS15987 100 accept AS15987 > as-in: from AS16038 100 accept AS-COMCITY > as-in: from AS16103 100 accept AS-NETZTECHOUT > as-in: from AS16126 100 accept AS16126 > as-in: from AS16148 100 accept AS16148 > as-in: from AS16152 100 accept AS16152 > as-in: from AS16233 100 accept AS16233 > as-in: from AS16356 100 accept AS16356 > as-out: to AS517 announce AS-UUNETDE AS-UUNETEUDE (AS702 AND UUNETEUDE) > as-out: to AS553 announce AS-UUNETDE AS-UUNETEUDE (AS702 AND UUNETEUDE) > as-out: to AS680 announce AS-UUNETDE AS-UUNETEUDE (AS702 AND UUNETEUDE) > as-out: to AS1273 announce AS-UUNETDE AS-UUNETEUDE (AS702 AND UUNETEUDE) > as-out: to AS1275 announce AS-UUNETDE AS-UUNETEUDE (AS702 AND UUNETEUDE) > as-out: to AS1889 announce ANY > as-out: to AS2125 announce ANY > as-out: to AS2686 announce AS-UUNETDE AS-UUNETEUDE (AS702 AND UUNETEUDE) > as-out: to AS2871 announce AS-UUNETDE AS-UUNETEUDE (AS702 AND UUNETEUDE) > as-out: to AS3257 announce AS-UUNETDE AS-UUNETEUDE (AS702 AND UUNETEUDE) > as-out: to AS3320 announce AS-UUNETDE AS-UUNETEUDE (AS702 AND UUNETEUDE) > as-out: to AS3569 announce ANY > as-out: to AS3573 announce ANY > as-out: to AS5378 announce AS-UUNETDE AS-UUNETEUDE (AS702 AND UUNETEUDE) > as-out: to AS5401 announce AS-UUNETDE AS-UUNETEUDE (AS702 AND UUNETEUDE) > as-out: to AS5427 announce AS-UUNETDE AS-UUNETEUDE (AS702 AND UUNETEUDE) > as-out: to AS5430 announce AS-UUNETDE AS-UUNETEUDE (AS702 AND UUNETEUDE) > as-out: to AS5496 announce AS-UUNETDE AS-UUNETEUDE (AS702 AND UUNETEUDE) > as-out: to AS5521 announce ANY > as-out: to AS5539 announce AS-UUNETDE AS-UUNETEUDE (AS702 AND UUNETEUDE) > as-out: to AS5549 announce AS-UUNETDE AS-UUNETEUDE (AS702 AND UUNETEUDE) > as-out: to AS5605 announce ANY > as-out: to AS5621 announce ANY > as-out: to AS5627 announce ANY > as-out: to AS6705 announce AS-UUNETDE AS-UUNETEUDE (AS702 AND UUNETEUDE) > as-out: to AS6735 announce AS-UUNETDE AS-UUNETEUDE (AS702 AND UUNETEUDE) > as-out: to AS6754 announce AS-UUNETDE AS-UUNETEUDE (AS702 AND UUNETEUDE) > as-out: to AS8072 announce ANY > as-out: to AS8196 announce AS-UUNETDE AS-UUNETEUDE (AS702 AND UUNETEUDE) > as-out: to AS8208 announce ANY > as-out: to AS8220 announce AS-UUNETDE AS-UUNETEUDE (AS702 AND UUNETEUDE) > as-out: to AS8298 announce ANY > as-out: to AS8319 announce AS-UUNETDE AS-UUNETEUDE (AS702 AND UUNETEUDE) > as-out: to AS8351 announce ANY > as-out: to AS8354 announce AS-UUNETDE AS-UUNETEUDE (AS702 AND UUNETEUDE) > as-out: to AS8360 announce ANY > as-out: to AS8373 announce ANY > as-out: to AS8379 announce AS-UUNETDE AS-UUNETEUDE (AS702 AND UUNETEUDE) > as-out: to AS8397 announce AS-UUNETDE AS-UUNETEUDE (AS702 AND UUNETEUDE) > as-out: to AS8422 announce ANY > as-out: to AS8442 announce ANY > as-out: to AS8469 announce ANY > as-out: to AS8477 announce AS-UUNETDE AS-UUNETEUDE (AS702 AND UUNETEUDE) > as-out: to AS8602 announce ANY > as-out: to AS8650 announce AS-UUNETDE AS-UUNETEUDE (AS702 AND UUNETEUDE) > as-out: to AS8735 announce ANY > as-out: to AS8767 announce ANY > as-out: to AS8794 announce ANY > as-out: to AS8827 announce ANY > as-out: to AS8852 announce ANY > as-out: to AS8864 announce ANY > as-out: to AS8879 announce ANY > as-out: to AS8925 announce ANY > as-out: to AS8939 announce ANY > as-out: to AS8950 announce ANY > as-out: to AS8957 announce ANY > as-out: to AS9007 announce ANY > as-out: to AS9059 announce ANY > as-out: to AS9066 announce ANY > as-out: to AS9067 announce ANY > as-out: to AS9072 announce ANY > as-out: to AS9099 announce ANY > as-out: to AS9164 announce ANY > as-out: to AS9175 announce ANY > as-out: to AS9188 announce ANY > as-out: to AS11660 announce ANY > as-out: to AS12288 announce ANY > as-out: to AS12291 announce ANY > as-out: to AS12292 announce ANY > as-out: to AS12313 announce ANY > as-out: to AS12331 announce ANY > as-out: to AS12343 announce ANY > as-out: to AS12355 announce ANY > as-out: to AS12371 announce ANY > as-out: to AS12379 announce ANY > as-out: to AS12437 announce ANY > as-out: to AS12466 announce ANY > as-out: to AS12470 announce ANY > as-out: to AS12531 announce ANY > as-out: to AS12532 announce ANY > as-out: to AS12555 announce ANY > as-out: to AS12574 announce ANY > as-out: to AS12581 announce ANY > as-out: to AS12595 announce ANY > as-out: to AS12598 announce ANY > as-out: to AS12610 announce ANY > as-out: to AS12612 announce ANY > as-out: to AS12625 announce ANY > as-out: to AS12638 announce ANY > as-out: to AS12643 announce ANY > as-out: to AS12647 announce ANY > as-out: to AS12664 announce ANY > as-out: to AS12678 announce ANY > as-out: to AS12722 announce ANY > as-out: to AS12796 announce ANY > as-out: to AS12813 announce ANY > as-out: to AS12853 announce ANY > as-out: to AS12857 announce ANY > as-out: to AS12886 announce ANY > as-out: to AS12888 announce ANY > as-out: to AS12892 announce ANY > as-out: to AS12899 announce ANY > as-out: to AS12915 announce ANY > as-out: to AS12916 announce ANY > as-out: to AS12919 announce ANY > as-out: to AS12930 announce ANY > as-out: to AS13003 announce ANY > as-out: to AS13006 announce ANY > as-out: to AS13012 announce ANY > as-out: to AS13039 announce ANY > as-out: to AS13040 announce ANY > as-out: to AS13043 announce ANY > as-out: to AS13045 announce ANY > as-out: to AS13083 announce ANY > as-out: to AS13090 announce ANY > as-out: to AS13101 announce ANY > as-out: to AS13129 announce AS-UUNETDE AS-UUNETEUDE (AS702 AND UUNETEUDE) > as-out: to AS13152 announce ANY > as-out: to AS13157 announce ANY > as-out: to AS13237 announce ANY > as-out: to AS13247 announce ANY > as-out: to AS13270 announce ANY > as-out: to AS15374 announce ANY > as-out: to AS15392 announce ANY > as-out: to AS15438 announce ANY > as-out: to AS15465 announce ANY > as-out: to AS15486 announce ANY > as-out: to AS15563 announce ANY > as-out: to AS15579 announce ANY > as-out: to AS15622 announce ANY > as-out: to AS15698 announce ANY > as-out: to AS15709 announce ANY > as-out: to AS15763 announce ANY > as-out: to AS15781 announce ANY > as-out: to AS15813 announce ANY > as-out: to AS15889 announce ANY > as-out: to AS15894 announce ANY > as-out: to AS15904 announce ANY > as-out: to AS15933 announce ANY > as-out: to AS15968 announce ANY > as-out: to AS15987 announce ANY > as-out: to AS16038 announce ANY > as-out: to AS16103 announce ANY > as-out: to AS16126 announce ANY > as-out: to AS16148 announce ANY > as-out: to AS16152 announce ANY > as-out: to AS16233 announce ANY > as-out: to AS16356 announce ANY > remarks: Community definitions > remarks: > remarks: Communities for incoming customer routes > remarks: > remarks: Community Definition > remarks: ============================================== > remarks: 1270:80 Set LocalPref within AS1270 to 80 > remarks: 1270:120 Set LocalPref within AS1270 to 120 > remarks: > admin-c: OD3-RIPE > tech-c: AT51 > notify: neteng(a)de.uu.net > remarks: Peering requests should be send to peering(a)de.uu.net > mnt-by: AS1270-MNT > changed: mz(a)de.uu.net 20010423 > source: RIPE > ***Error: syntax error > ***Error: Unknown class encountered. > > RIPE Database Maintenance Department (Automatic Section) > -- Frank Bohnsack email fb(a)de.uu.net UUNET, A Worldcom Company phone +49 (0)231 972-1495 EMEA Access & Backbone Networks fax +49 (0)231 972-1188 Team Dortmund web www.de.uu.net

2 1

auto-rpsl@ripe.net MIME parser problem and auth failure
by Daniel Roesen 23 Apr '01

23 Apr '01

Hi, the auto-rpsl(a)ripe.net robot MIME parser doesn't understand quoted-printable encoding. I think it should. Second, all our updates are failing with "authorisation failed". Our objects are protected by a maintainer object with PGP-Auth. I guess there is a problem with signature verification Best regards, Daniel Roesen -- Entire Systems GmbH - Ferbachstrasse 12 - 56203 Hoehr-Grenzhausen, Germany InterNIC-Handle: ES1238-ORG RIPE-Handle: ESN10-RIPE Tel: +49 2624 9550-55 GnuPG/PGP Key-ID: 0xBF3C40C9 http://www.entire-systems.com/noc/noc-key.asc GnuPG/PGP Fingerprint: 1F3F B675 1A38 D87C EB3C 6090 C6B9 DF48 BF3C 40C9

1 0

Re: New DB and line continuation?
by RIPE Database Administration 23 Apr '01

23 Apr '01

Hi, Berislav Todorovic, Thank you for reporting this. We are investigating. If you have anymore questions, please contact <ripe-dbm(a)ripe.net>. Regards, A. M. R. Magee ______________ RIPE NCC Berislav Todorovic <beri(a)kpnqwest.net> writes: * On Mon, 23 Apr 2001, DB-News wrote: * * >> The new version of the RIPE Database is now up and running! * >> All objects have been automatically converted to RPSL and loaded into * >> the new version of the Database. * * Congratulations! However, I have a question: * * When an attribute needs multiple lines to be described, the standard * RPSL format requires the attribute name to be mentioned once, while * successive lines are separted by spaces or commas (like you defined * in the transition document as well). It used to be like that in the * previous version of rpsl.ripe.net. However, right now, it seems to * me there is a strange RIPE-181/RPSL mix in place. See example: * * * RADB and old REIMP.RIPE (standard RPSL): * * [beri@nix00 ~]$ rwhois -h whois.ra.net as-kq * as-set: AS-KQ * descr: KPNQwest European routes * Formerly AS-EUNET AND NOT AS-EUNETQWEST * members: AS286, AS719, AS1136, AS1137, AS1213, * AS1234, AS1889, AS1891, AS1902, AS2043, * AS2049, AS2110, AS2135, AS2857, AS3220, * ... * * * RIPE (new format, RPSL): * * as-set: AS-KQ * descr: KPNQwest European routes * descr: Formerly AS-EUNET AND NOT AS-EUNETQWEST * members: AS286, AS719, AS1136, AS1137, AS1213, AS1234, AS1889 * members: AS1891, AS1902, AS2043, AS2049, AS2110, AS2135, AS2857 * members: AS3220, AS3246, AS3262, AS3265, AS3286, AS3324, AS3333 * members: AS3347, AS3615, AS5385, AS5399, AS5403, AS5407, AS5419 * * While some of you might think this is not important, this is VERY * important to some of us who make scripts for automating our tasks with * the RIPE DB. * * Can anyone explain the reason of this RPSL syntax violation? Thanks! * * Regards, * Beri * * --------- Berislav Todorovic, Network Engineer --------- * ------- KPNQwest N.V. - IP NOC (formerly EUnet NOC) ------- * ---- Wilhelmina van Pruisenweg 78, 2595 AN Den Haag, NL ---- * --- Phone: +31-70-379-3990; Mobile: +31-651-333-641 --- * -- Email: beri(a)kpnqwest.net <=> beri(a)EU.net -- * --- _ _ ____ _ .--. ____ ____ __/_ --- * ----- /__/ /___/ /\ / / / | / /___/ /___ / ------ * ------ _/ \_ / _/ \/ (__.\ |/\/ /___ ____/ (__. ----- * *

1 0

New RPSL Query of aut-num objects
by Sascha E. Pollok 23 Apr '01

23 Apr '01

Dear Folks, apologies if this has been discussed before or is considered not being relevant to most of you but if I do a query like below, the main difference (beside the new RPSL-look-and-feel of course) is that the as-block: object is shown AND that there is one space missing as a separator between field-descriptors and the content of the field compared to all other objects. Again, this might be irrelevant to most of you that do /(\S+)\s+(.*)/ or whatever but I just wanted to ask. Regards, Sascha ----------- % whois AS12731 as-block: AS12288 - AS13311 descr: RIPE NCC ASN block remarks: These AS numbers are further assigned by RIPE NCC remarks: to LIRs and end-users in the RIPE NCC region remarks: Please refer to RIPE Document ripe-185 remarks: and RIPE Document ripe-147 admin-c: NN32-RIPE tech-c: OPS4-RIPE mnt-by: RIPE-NCC-HM-MNT mnt-lower: RIPE-NCC-HM-MNT changed: hostmaster(a)ripe.net 20010423 source: RIPE aut-num: AS12731 as-name: IPHH descr: IPHH Internet Port Hamburg GmbH descr: Global AS Routing-Policy import: from AS3300 action pref=100; accept ANY AND NOT {0.0.0.0/0}

1 0

Fwd: BLOCK: RIPE
by Christian Panigl, ACOnet/VIX/UniVie 23 Apr '01

23 Apr '01

Hmmm, reasonable diligence or epidemic paranoia ? Just got this one forwarded, thought it might be worth letting you know ... Cheers CP ================================ X-Mailer: Forte Agent 1.8/32.548 Message-ID: <6uu6ets5102thcbdrigof2l7urtmd2gmjl(a)4ax.com> Date: Sun, 22 Apr 2001 20:48:13 -0400 From: Daniel Norton <danorton(a)SUESPAMMERS.ORG> To: SPAM-L(a)PEACH.EASE.LSOFT.COM Reply-To: Daniel Norton <danorton(a)SUESPAMMERS.ORG> Sender: Spam Prevention Discussion List <SPAM-L(a)PEACH.EASE.LSOFT.COM> Organization: . Subject: BLOCK: RIPE RIPE's database is down for an indeterminate period of time. Since it might be impossible to determine an abuse contact address without the RIPE database, you might wish to consider blocking all RIPE traffic until they get things back in order. Here are the RIPE IP address ranges: 24.132/14 62/8 139.20/14 139.24/14 139.28/15 141.0/10 141.64/12 141.80/14 141.84/15 145.224/12 145.240/13 145.248/14 145.252/15 145.254/16 149.202/15 149.204/16 149.206/15 149.208/12 149.224/12 149.240/13 149.248/14 150.254/16 151.13/16 151.14/15 151.16/12 151.32/11 151.64/12 151.80/15 151.3/16 151.4/15 151.82/16 151.91/16 151.92/15 151.95/16 160.216/14 160.220/16 160.44/14 160.48/12 163.156/14 163.160/12 164.0/11 164.32/13 164.40/16 164.128/12 171.16/12 171.32/15 192.106.196/23 192.162/16 192.164/14 192.71/16 193/8 194/8 195/8 198.17.117/24 212/8 213/8 217/8 -- Daniel Norton ----- End of forwarded message from Daniel Norton -----

3 2