From andrei at ripe.net Mon Apr 2 13:28:22 2001 From: andrei at ripe.net (Andrei Robachevsky) Date: Mon, 02 Apr 2001 13:28:22 +0200 Subject: Plan of the migration to the new RIPE Database Message-ID: <3AC86256.6896AAED@ripe.net> Dear Colleagues, [apologies for duplicate messages] Please find below a list of milestones related to the migration to the new version of the RIPE Database. Your comments and suggestions are welcome. Should you have any further question regarding the migration, please don't hesitate to contact me. Best regards, Andrei Robachevsky DB Group Manager RIPE NCC ------------------------------------------------------------------ Date Actions ------------------------------------------------------------------ 4.04 Final release of the v3.0 DB software 12.04 Advised mirror's switchover to rpsl.ripe.net. - Reminder is sent to NRTM clients on 9.04 - Starting from this date NRTM clients that mirror the RIPE Database are advised to use the new server at rpsl.ripe.net, port 4444 for mirroring. 17-18.04 Migration of the TEST database to v3.0 (RPSL) - TEST Database becomes a RPSL database. Updates are accepted in RPSL format at . - No RIPE-181 TEST database exists anymore. - Estimated downtime 6 hours. 22.04-23.04 Migration of the RIPE Database to v3.0 (RPSL) - New server becomes the official RIPE Database server at 00:00 23.04. - Updates received after 16:00, 22.04 are queued until the new server becomes operational. After that they are automatically converted to RPSL and processed by the new server. New syntax and authorization rules apply. - Downtime in queries will be deliberately introduced to mark the migration. Whois server downtime is planned from 18:00, 22.04 till 00:00 23.04. During this time a message explaining the migration process will be sent as a whois query reply. 23.04, 00:00 New server becomes the official RIPE Database server - Short (1-2 min) downtime is possible during final tests. 23.04, 02:00 New server starts processing updates - Two mail robots are available: - updates in RIPE-181 format (restrictions apply) - updates in RPSL format (recommended). From andrei at ripe.net Mon Apr 2 15:28:04 2001 From: andrei at ripe.net (Andrei Robachevsky) Date: Mon, 02 Apr 2001 15:28:04 +0200 Subject: Plan of the migration to the new RIPE Database References: <3AC86256.6896AAED@ripe.net> <20010402123312.A27033@whit.ja.net> Message-ID: <3AC87E64.DD64B1AB@ripe.net> Hi Rob, Rob Evans wrote: > > Hi Andrei, > > > Please find below a list of milestones related to the migration to the new > > version of the RIPE Database. > > Silly question; are the times UTC or CET? Sorry about this, all times are CEST (Central European Summer Time, UTC+2). > > Thanks, > Rob Regards, Andrei From andrei at ripe.net Tue Apr 3 11:04:24 2001 From: andrei at ripe.net (Andrei Robachevsky) Date: Tue, 03 Apr 2001 11:04:24 +0200 Subject: Another issue related to the migration References: Message-ID: <3AC99218.2B159D10@ripe.net> Dear Colleagues, "Lu, Ping" wrote: > > Andrei, > The existing ripe2rpsl tool will automatically translate "AS-" to "ASN-" > for the aut-num object and I think "ASN-" is more meaningful than "AS_". > If nobody objects against Ping's proposal, let's convert them to "ASN-". I agree that "_" is a bit uncommon. Regards, Andrei > Best Regards. > > Ping Lu > Cable & Wireless Global > Network Tools and Analysis Group, USA > W: +1-703-292-2359 > E: plu at cw.net > > > -----Original Message----- > > From: Andrei Robachevsky [mailto:andrei at ripe.net] > > Sent: Thursday, March 29, 2001 11:10 AM > > To: db-wg at ripe.net; routing-wg at ripe.net; Migration TF; lir-wg at ripe.net > > Subject: Another issue related to the migration > > > > > > Dear Colleagues, > > > > [Apologies for duplicate messages] > > > > One issue related to RIPE-181 to RPSL migration escaped our > > attention and has > > not been discussed. It is related to reserved prefixes that > > cannot appear in > > object names according to RPSL specification (RFC2622) which says: > > > > "Names starting with certain prefixes are reserved for > > certain object types. > > Names starting with "as-" are reserved for as set names. > > Names starting with > > "rs-" are reserved for route set names. Names starting with > > "rtrs-" are > > reserved for router set names. Names starting with "fltr-" > > are reserved for > > filter set names. Names starting with "prng-" are reserved > > for peering set > > names." > > > > Unfortunately "as-name:" attribute is an object name in RPSL > > and we have 133 > > aut-num objects with as-name starting with reserved 'AS-' prefix. > > > > Our suggestion how to deal with these objects is: > > > > 1. Send a message to the maintainers of these objects asking > > them to change the > > name to avoid conflict with RPSL specification. > > 2. Give two-week notice period after which ripe-dbm will > > convert non compliant > > as-names using the following mapping: AS-ASNAME -> AS_ASNAME. > > > > This is more a "cosmetic" change as as-name is not even a > > lookup key in the RIPE > > Database. > > > > Your comments and suggestions are appreciated. > > > > Best regards, > > > > > > Andrei Robachevsky > > DB Group Manager > > RIPE NCC > > -- Andrei Robachevsky DB Group Manager RIPE NCC From andrei at ripe.net Wed Apr 18 16:06:54 2001 From: andrei at ripe.net (Andrei Robachevsky) Date: Wed, 18 Apr 2001 16:06:54 +0200 Subject: Migration of the TEST database is delayed Message-ID: <3ADD9F7E.E87DD441@ripe.net> Dear colleagues, Unfortunately due to hardware problems with the computer running TEST database server we need to delay the migration of the TEST database that was planned on 17-18.04. We plan to start the migration of the TEST database tomorrow, 19.04. We will keep you informed. Sorry for any inconvenience this caused. Regards, Andrei Robachevsky DB Group Manager RIPE NCC From andrei at ripe.net Fri Apr 20 21:48:26 2001 From: andrei at ripe.net (Andrei Robachevsky) Date: Fri, 20 Apr 2001 21:48:26 +0200 Subject: Migration of the TEST database is completed Message-ID: <3AE0928A.F1840653@ripe.net> Dear Colleagues, The TEST database has been successfully migrated to v3 software. All objects in the TEST database were converted to RPSL compliant format. You can continue using the TEST database till 14 May as follows: - mail robot accepts updates in RIPE-181 format with some limitations. - mail robot accepts updates in RPSL format. After that day changes in robots' functionality will follow the plan fro the production database. Please see http://www/ripencc/pub-services/db/rpsl/announcement.html and http://www/ripencc/pub-services/db/rpsl/index.html for more information. Finding objects in the TEST Database: Do whois -h test-whois.ripe.net e.g. whois -h test-whois.ripe.net PB3-TEST The whois options that work in the RIPE Database also work in the TEST Database. We invite you to try them. Regards, Andrei Robachevsky DB Group Manager RIPE NCC From andrei at ripe.net Sun Apr 22 12:42:23 2001 From: andrei at ripe.net (Andrei Robachevsky) Date: Sun, 22 Apr 2001 12:42:23 +0200 Subject: rpsl bug? References: <4.3.2.7.2.20010422125331.00ac5df0@max.ibm.net.il> Message-ID: <3AE2B58F.C50EDBF9@ripe.net> Dear Hank, Thank you for spotting this. This will be fixed shortly. Regards, Andrei Robachevsky RIPE NCC Hank Nussbacher wrote: > > I am not an rpsl guru so if this is normal, please let me now: > > whois -h rpsl.ripe.net ynet.co.il > > % This is the RIPE Whois server. > % Rights restricted by copyright. > % See http://www.ripe.net/ripencc/pub-services/db/copyright.html > > % The object shown below is NOT in the RIPE database. > % It has been obtained by querying a remote server: > % (x17.ripe.net) at port 43434. > % To see the object stored in the RIPE database > % use the -R flag in your query > % > %REFERRAL START > %ERROR:304: referral host not responding > % > % Referral host not responding > %%REFERRAL END > > But this does work: > > whois -h whois.ripe.net ynet.co.il > > % Rights restricted by copyright. See > http://www.ripe.net/ripencc/pub-services/db/copyright.html > > % The object shown below is NOT in the RIPE database. > % It has been obtained by querying a remote server: > % (whois.isoc.org.il) at port 43. > % To see the object stored in the RIPE database > % use the -R flag in your query. > % > %%% Start of referred query result > > % The data in the WHOIS database of the .il registry is provided > % by ISOC-IL for information purposes, and to assist persons in > % obtaining information about or related to a domain name > % registration record. ISOC-IL does not guarantee its accuracy. > % By submitting a WHOIS query, you agree that you will use this > % Data only for lawful purposes and that, under no circumstances > % will you use this Data to: (1) allow, enable, or otherwise > % support the transmission of mass unsolicited, commercial > % advertising or solicitations via e-mail (spam); > % or (2) enable high volume, automated, electronic processes that > % apply to ISOC-IL (or its systems). > % ISOC-IL reserves the right to modify these terms at any time. > % By submitting this query, you agree to abide by this policy. > > domain: ynet.co.il > descr: Yedioth Internet Ltd. > descr: 127 Yigal alon st. > descr: Tel Aviv > descr: 67443 > descr: Israel > phone: +972 3 6932424 > fax-no: +972 3 6932466 > admin-c: GM6719-IL > tech-c: PL4687-IL > zone-c: PL4687-IL > nserver: dns01.ynet.co.il > nserver: dns02.ynet.co.il > changed: domain-registrar at isoc.org.il 20010107 (Transferred) > > person: Gadi Monsa > address: Yedioth Internet > address: 127 Yigal Alon > address: Tel-Aviv > address: Israel > phone: +972 3 6932454 > fax-no: +972 36932466 > e-mail: gadim at yedioth.co.il > nic-hdl: GM6719-IL > changed: registrar at ns.il 20000406 > > person: Pazi Levinson > address: Yedioth Internet Ltd. > address: 127 Yigal Alon st. > address: Tel Aviv > address: 67443 > address: Israel > phone: +972 3 6932424 > fax-no: +972 3 6932466 > e-mail: pazi at ynet.co.il > nic-hdl: PL4687-IL > changed: domain-registrar at isoc.org.il 20010107 > > % Rights to the data above are restricted by copyright. > > %%% End of referred query result > --- > > Thanks, > Hank From db-news at ripe.net Mon Apr 23 03:43:44 2001 From: db-news at ripe.net (DB-News) Date: Mon, 23 Apr 2001 03:43:44 +0200 Subject: First phase of the migration to the new RIPE Database is completed Message-ID: <200104230143.DAA04636@x43.ripe.net> Dear Colleagues, 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. The first phase of the migration has been successfully completed. The following mail robots accept updates to the RIPE Database: - updates are accepted in RIPE-181 format and automatically translated into RPSL. However, several restrictions apply to such updates: empty and misspelled attributes are not allowed, PGP auth is not supported. Also, RPSL authorization rules apply. - updates are accepted in RPSL format. This setup will be in place till 14 May, 2001. For more information about the migration please visit http://www.ripe.net/ripencc/pub-services/db/rpsl/announcement.html and http://www.ripe.net/ripencc/pub-services/db/rpsl/index.html Best Regards, Andrei Robachevsky DB Group RIPE NCC From hank at att.net.il Sun Apr 22 12:56:47 2001 From: hank at att.net.il (Hank Nussbacher) Date: Sun, 22 Apr 2001 12:56:47 +0200 Subject: rpsl bug? In-Reply-To: <3AE0928A.F1840653@ripe.net> Message-ID: <4.3.2.7.2.20010422125331.00ac5df0@max.ibm.net.il> I am not an rpsl guru so if this is normal, please let me now: whois -h rpsl.ripe.net ynet.co.il % This is the RIPE Whois server. % Rights restricted by copyright. % See http://www.ripe.net/ripencc/pub-services/db/copyright.html % The object shown below is NOT in the RIPE database. % It has been obtained by querying a remote server: % (x17.ripe.net) at port 43434. % To see the object stored in the RIPE database % use the -R flag in your query % %REFERRAL START %ERROR:304: referral host not responding % % Referral host not responding %%REFERRAL END But this does work: whois -h whois.ripe.net ynet.co.il % Rights restricted by copyright. See http://www.ripe.net/ripencc/pub-services/db/copyright.html % The object shown below is NOT in the RIPE database. % It has been obtained by querying a remote server: % (whois.isoc.org.il) at port 43. % To see the object stored in the RIPE database % use the -R flag in your query. % %%% Start of referred query result % The data in the WHOIS database of the .il registry is provided % by ISOC-IL for information purposes, and to assist persons in % obtaining information about or related to a domain name % registration record. ISOC-IL does not guarantee its accuracy. % By submitting a WHOIS query, you agree that you will use this % Data only for lawful purposes and that, under no circumstances % will you use this Data to: (1) allow, enable, or otherwise % support the transmission of mass unsolicited, commercial % advertising or solicitations via e-mail (spam); % or (2) enable high volume, automated, electronic processes that % apply to ISOC-IL (or its systems). % ISOC-IL reserves the right to modify these terms at any time. % By submitting this query, you agree to abide by this policy. domain: ynet.co.il descr: Yedioth Internet Ltd. descr: 127 Yigal alon st. descr: Tel Aviv descr: 67443 descr: Israel phone: +972 3 6932424 fax-no: +972 3 6932466 admin-c: GM6719-IL tech-c: PL4687-IL zone-c: PL4687-IL nserver: dns01.ynet.co.il nserver: dns02.ynet.co.il changed: domain-registrar at isoc.org.il 20010107 (Transferred) person: Gadi Monsa address: Yedioth Internet address: 127 Yigal Alon address: Tel-Aviv address: Israel phone: +972 3 6932454 fax-no: +972 36932466 e-mail: gadim at yedioth.co.il nic-hdl: GM6719-IL changed: registrar at ns.il 20000406 person: Pazi Levinson address: Yedioth Internet Ltd. address: 127 Yigal Alon st. address: Tel Aviv address: 67443 address: Israel phone: +972 3 6932424 fax-no: +972 3 6932466 e-mail: pazi at ynet.co.il nic-hdl: PL4687-IL changed: domain-registrar at isoc.org.il 20010107 % Rights to the data above are restricted by copyright. %%% End of referred query result --- Thanks, Hank From ripe-dbm at ripe.net Mon Apr 23 10:03:21 2001 From: ripe-dbm at ripe.net (RIPE Database Administration) Date: Mon, 23 Apr 2001 10:03:21 +0200 Subject: rpsl bug? In-Reply-To: Your message of Sun, 22 Apr 2001 12:56:47 +0200. <4.3.2.7.2.20010422125331.00ac5df0@max.ibm.net.il> References: <4.3.2.7.2.20010422125331.00ac5df0@max.ibm.net.il> Message-ID: <200104230803.KAA17225@office.ripe.net> Dear Hank, Thanks again for reporting this. It has been fixed. If you have anymore questions, please contact . Regards, A. M. R. Magee ______________ RIPE NCC Hank Nussbacher writes: * I am not an rpsl guru so if this is normal, please let me now: * * whois -h rpsl.ripe.net ynet.co.il * * % This is the RIPE Whois server. * % Rights restricted by copyright. * % See http://www.ripe.net/ripencc/pub-services/db/copyright.html * * % The object shown below is NOT in the RIPE database. * % It has been obtained by querying a remote server: * % (x17.ripe.net) at port 43434. * % To see the object stored in the RIPE database * % use the -R flag in your query * % * %REFERRAL START * %ERROR:304: referral host not responding * % * % Referral host not responding * %%REFERRAL END * * But this does work: * * whois -h whois.ripe.net ynet.co.il * * % Rights restricted by copyright. See * http://www.ripe.net/ripencc/pub-services/db/copyright.html * * * % The object shown below is NOT in the RIPE database. * % It has been obtained by querying a remote server: * % (whois.isoc.org.il) at port 43. * % To see the object stored in the RIPE database * % use the -R flag in your query. * % * %%% Start of referred query result * * * % The data in the WHOIS database of the .il registry is provided * % by ISOC-IL for information purposes, and to assist persons in * % obtaining information about or related to a domain name * % registration record. ISOC-IL does not guarantee its accuracy. * % By submitting a WHOIS query, you agree that you will use this * % Data only for lawful purposes and that, under no circumstances * % will you use this Data to: (1) allow, enable, or otherwise * % support the transmission of mass unsolicited, commercial * % advertising or solicitations via e-mail (spam); * % or (2) enable high volume, automated, electronic processes that * % apply to ISOC-IL (or its systems). * % ISOC-IL reserves the right to modify these terms at any time. * % By submitting this query, you agree to abide by this policy. * * domain: ynet.co.il * descr: Yedioth Internet Ltd. * descr: 127 Yigal alon st. * descr: Tel Aviv * descr: 67443 * descr: Israel * phone: +972 3 6932424 * fax-no: +972 3 6932466 * admin-c: GM6719-IL * tech-c: PL4687-IL * zone-c: PL4687-IL * nserver: dns01.ynet.co.il * nserver: dns02.ynet.co.il * changed: domain-registrar at isoc.org.il 20010107 (Transferred) * * person: Gadi Monsa * address: Yedioth Internet * address: 127 Yigal Alon * address: Tel-Aviv * address: Israel * phone: +972 3 6932454 * fax-no: +972 36932466 * e-mail: gadim at yedioth.co.il * nic-hdl: GM6719-IL * changed: registrar at ns.il 20000406 * * person: Pazi Levinson * address: Yedioth Internet Ltd. * address: 127 Yigal Alon st. * address: Tel Aviv * address: 67443 * address: Israel * phone: +972 3 6932424 * fax-no: +972 3 6932466 * e-mail: pazi at ynet.co.il * nic-hdl: PL4687-IL * changed: domain-registrar at isoc.org.il 20010107 * * % Rights to the data above are restricted by copyright. * * * %%% End of referred query result * --- * * Thanks, * Hank * * * * * * From ripe-dbm at ripe.net Mon Apr 23 11:24:41 2001 From: ripe-dbm at ripe.net (RIPE Database Administration) Date: Mon, 23 Apr 2001 11:24:41 +0200 Subject: New DB and line continuation? In-Reply-To: Your message of Mon, 23 Apr 2001 11:16:01 +0200. References: Message-ID: <200104230924.LAA29288@office.ripe.net> Hi, Berislav Todorovic, Thank you for reporting this. We are investigating. If you have anymore questions, please contact . Regards, A. M. R. Magee ______________ RIPE NCC Berislav Todorovic 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 at 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 at kpnqwest.net <=> beri at EU.net -- * --- _ _ ____ _ .--. ____ ____ __/_ --- * ----- /__/ /___/ /\ / / / | / /___/ /___ / ------ * ------ _/ \_ / _/ \/ (__.\ |/\/ /___ ____/ (__. ----- * * From andrei at ripe.net Mon Apr 23 12:16:27 2001 From: andrei at ripe.net (Andrei Robachevsky) Date: Mon, 23 Apr 2001 12:16:27 +0200 Subject: New DB and line continuation? References: Message-ID: <3AE400FB.781C177A@ripe.net> 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 mandatory, single-valued, class key members list of or optional, multi-valued 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 at 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 at kpnqwest.net <=> beri at EU.net -- > --- _ _ ____ _ .--. ____ ____ __/_ --- > ----- /__/ /___/ /\ / / / | / /___/ /___ / ------ > ------ _/ \_ / _/ \/ (__.\ |/\/ /___ ____/ (__. ----- -- Andrei Robachevsky DB Group Manager RIPE NCC From andrei at ripe.net Mon Apr 23 13:55:32 2001 From: andrei at ripe.net (Andrei Robachevsky) Date: Mon, 23 Apr 2001 13:55:32 +0200 Subject: New DB and line continuation? References: Message-ID: <3AE41834.2683F8E9@ripe.net> Berislav Todorovic wrote: > > On Mon, 23 Apr 2001, Andrei Robachevsky wrote: > > >> 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. > > OK - but will they be converted into multiple-members line format again or > stay in the RADB-like form? Just curious ... > No, they will not be converted. But you need to send them to robot. You may try... Regards, Andrei > 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 at kpnqwest.net <=> beri at EU.net -- > --- _ _ ____ _ .--. ____ ____ __/_ --- > ----- /__/ /___/ /\ / / / | / /___/ /___ / ------ > ------ _/ \_ / _/ \/ (__.\ |/\/ /___ ____/ (__. ----- -- Andrei Robachevsky DB Group Manager RIPE NCC From beri at kpnqwest.net Mon Apr 23 11:16:01 2001 From: beri at kpnqwest.net (Berislav Todorovic) Date: Mon, 23 Apr 2001 11:16:01 +0200 (CEST) Subject: New DB and line continuation? In-Reply-To: <200104230143.DAA04636@x43.ripe.net> Message-ID: 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 at 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 at kpnqwest.net <=> beri at EU.net -- --- _ _ ____ _ .--. ____ ____ __/_ --- ----- /__/ /___/ /\ / / / | / /___/ /___ / ------ ------ _/ \_ / _/ \/ (__.\ |/\/ /___ ____/ (__. ----- From beri at kpnqwest.net Mon Apr 23 12:31:51 2001 From: beri at kpnqwest.net (Berislav Todorovic) Date: Mon, 23 Apr 2001 12:31:51 +0200 (CEST) Subject: New DB and line continuation? In-Reply-To: <3AE400FB.781C177A@ripe.net> Message-ID: On Mon, 23 Apr 2001, Andrei Robachevsky wrote: >> 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. OK - but will they be converted into multiple-members line format again or stay in the RADB-like form? Just curious ... 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 at kpnqwest.net <=> beri at EU.net -- --- _ _ ____ _ .--. ____ ____ __/_ --- ----- /__/ /___/ /\ / / / | / /___/ /___ / ------ ------ _/ \_ / _/ \/ (__.\ |/\/ /___ ____/ (__. ----- From andrei at ripe.net Mon Apr 23 20:26:10 2001 From: andrei at ripe.net (Andrei Robachevsky) Date: Mon, 23 Apr 2001 20:26:10 +0200 Subject: First phase of the migration to the new RIPE Database is completed References: Message-ID: <3AE473C2.105AA346@ripe.net> Hi Pierre, Pierre Thibaudeau wrote: > > > Hi Andrei, > > Back in Febuary, we were proposed to test the new robot by emailing to > , which I did. After a few adjustments, it came out > fine, including PGP auth ("in line" style). > > Can you clarify the above statement. > > > > > - updates are accepted in RPSL format. > > Some 2h30m ago, I sent a update request to to update > our AS8297 & AS-GIEUROPE. No response from the robot yet, and no visible > change on rpsl.ripe.net. > Indeed, we experience problems with PGP signed messages - they do not pass authorization check. We are working on this and plan to resolve this tomorrow. You will receive NACK from the robot (with some delay, maybe, because we are still tuning the system). Sorry for any inconvenience this causes. Regards, Andrei > Date: Mon, 23 Apr 2001 11:26:17 -0400 (EDT) > From: Pierre Thibaudeau > To: rpsl-dbm at ripe.net > Subject: Reformatted for RPSL > > -----BEGIN PGP SIGNED MESSAGE----- > > aut-num: AS8297 > as-name: Teleglobe Europe > descr: Teleglobe Autonomous System in Europe > Send peering request to peering at teleglobe.net > [...] > > Regards. > __ > > Pierre Thibaudeau | e-mail: > TELEGLOBE CANADA | e-page: > 1000, rue de La Gauchetiere ouest | > Montreal, QC H3B 4X5 | Tel: +1-514-868-7257 > Canada | fax: +1-514-868-8446 > > > > > This setup will be in place till 14 May, 2001. > > > > For more information about the migration please visit > > http://www.ripe.net/ripencc/pub-services/db/rpsl/announcement.html and > > http://www.ripe.net/ripencc/pub-services/db/rpsl/index.html > > > > Best Regards, > > > > Andrei Robachevsky > > DB Group > > RIPE NCC > > -- Andrei Robachevsky DB Group Manager RIPE NCC From SchmitzJo at aol.com Tue Apr 24 07:34:27 2001 From: SchmitzJo at aol.com (SchmitzJo at aol.com) Date: Tue, 24 Apr 2001 01:34:27 EDT Subject: draft agenda routing/joint routing&db wg RIPE 39 Message-ID: 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 --- From prt at Teleglobe.net Mon Apr 23 20:03:20 2001 From: prt at Teleglobe.net (Pierre Thibaudeau) Date: Mon, 23 Apr 2001 14:03:20 -0400 (EDT) Subject: First phase of the migration to the new RIPE Database is completed In-Reply-To: <200104230143.DAA04636@x43.ripe.net> Message-ID: On Mon, 23 Apr 2001, DB-News wrote: > Date: Mon, 23 Apr 2001 03:43:44 +0200 > From: DB-News > To: reimp-mig-tf at ripe.net, db-wg at ripe.net, routing-wg at ripe.net, > lir-wg at ripe.net, local-ir at ripe.net > Cc: ripe-dbm at ripe.net > Subject: First phase of the migration to the new RIPE Database is > completed > > Dear Colleagues, > > 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. > > The first phase of the migration has been successfully completed. > > The following mail robots accept updates to the RIPE Database: > - updates are accepted in RIPE-181 format and > automatically translated into RPSL. However, several restrictions > apply to such updates: empty and misspelled attributes are not allowed, > PGP auth is not supported. Also, RPSL authorization rules apply. Hi Andrei, Back in Febuary, we were proposed to test the new robot by emailing to , which I did. After a few adjustments, it came out fine, including PGP auth ("in line" style). Can you clarify the above statement. > > - updates are accepted in RPSL format. Some 2h30m ago, I sent a update request to to update our AS8297 & AS-GIEUROPE. No response from the robot yet, and no visible change on rpsl.ripe.net. Date: Mon, 23 Apr 2001 11:26:17 -0400 (EDT) From: Pierre Thibaudeau To: rpsl-dbm at ripe.net Subject: Reformatted for RPSL -----BEGIN PGP SIGNED MESSAGE----- aut-num: AS8297 as-name: Teleglobe Europe descr: Teleglobe Autonomous System in Europe Send peering request to peering at teleglobe.net [...] Regards. __ Pierre Thibaudeau | e-mail: TELEGLOBE CANADA | e-page: 1000, rue de La Gauchetiere ouest | Montreal, QC H3B 4X5 | Tel: +1-514-868-7257 Canada | fax: +1-514-868-8446 > > This setup will be in place till 14 May, 2001. > > For more information about the migration please visit > http://www.ripe.net/ripencc/pub-services/db/rpsl/announcement.html and > http://www.ripe.net/ripencc/pub-services/db/rpsl/index.html > > Best Regards, > > Andrei Robachevsky > DB Group > RIPE NCC > From Karsten.Koepp at lambdanet.net Wed Apr 25 15:39:27 2001 From: Karsten.Koepp at lambdanet.net (Koepp, Karsten) Date: Wed, 25 Apr 2001 15:39:27 +0200 Subject: No answer from Robot auto-rpsl@ripe.net Message-ID: <39F27E3F569FD4119EF200508BAF85B9BED67F@CCGNT30> Hi Andrej, are there still problems with processing PGP signed updates? I sent several updates to auto-rpsl at ripe.net two days ago, but I got NO response at all yet. Objects are not updated in the database either. Regards Karsten ------------------------------------------------------------- Karsten Koepp Core network planning IP FirstMark Communications GmbH Guenther-Wagner-Allee 13 D-30177 Hannover (Germany) Phone +49 (0)511 / 84 88 - 12 55 Fax +49 (0)511 / 84 88 - 12 69 Mobile +49 (0)178 / 3 62 - 12 55 mailto:Karsten.Koepp at firstmark.de News & Facts finden Sie auf unserer Website: www.firstmark.de ------------------------------------------------------------- > -----Urspr?ngliche Nachricht----- > Von: Koepp, Karsten > Gesendet am: Montag, 23. April 2001 13:53 > An: 'auto-rpsl at ripe.net' > Cc: 'hostmaster at fmcs.net' > Betreff: eu.firstmark modify aut-num request 2001 > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > as-set: AS-LNCES > descr: Lambdanet Communications Spain > members: AS13237 > members: AS15732 > remarks: Customers of LNC Spain > tech-c: LNC-RIPE > admin-c: LNC-RIPE > notify: hostmaster at fmcs.net > notify: raquel.dejuanes at firstmark.es > mnt-by: LNC-MNT > changed: karsten.koepp at lambdanet.net 20010423 > source: RIPE > > -----BEGIN PGP SIGNATURE----- > Version: PGPfreeware 6.5.1 Int. for non-commercial use > > > iQA/AwUBOuQJpOYNfguPxE5tEQKhDwCgxrlcKM4kkvBGgt1UudomH6DSwC8AoJWE > ABmFJR7QK7Pz8rPckq2s91Po > =3cpZ > -----END PGP SIGNATURE----- > From Andreas.Roehling at lambdanet.net Wed Apr 25 15:57:58 2001 From: Andreas.Roehling at lambdanet.net (Roehling, Andreas) Date: Wed, 25 Apr 2001 15:57:58 +0200 Subject: bloody database ???? Message-ID: <39F27E3F569FD4119EF200508BAF85B9B5135E@CCGNT30> X-NCC-Regid: de.firstmark X-NCC-Regid: eu.firstmark Hi Guys, i think you have many problems? A very interesting answer. What wants the data base to say me? Regards Andreas -----Ursprungliche Nachricht----- Von: RIPE Database Management [mailto:ripe-dbm at ripe.net] Gesendet: Mittwoch, 25. April 2001 15:49 An: Andreas.Roehling at lambdanet.net Betreff: Re: New Acknowledgement message from database software Your e-mail: > From: "Roehling, Andreas" > Cc: > Subject: New > Date: Wed, 25 Apr 2001 15:47:46 +0200 > Msg-Id: <39F27E3F569FD4119EF200508BAF85B9B5135D at CCGNT30> has been processed by the automatic update procedure at the RIPE NCC. Diagnostic output follows: ------------------------------------------------------------------------ RIPE Database Maintenance Department (Automatic Section) From andrei at ripe.net Thu Apr 26 16:07:47 2001 From: andrei at ripe.net (Andrei Robachevsky) Date: Thu, 26 Apr 2001 16:07:47 +0200 Subject: The status of the migration iissues Message-ID: <3AE82BB3.8BFCFF7F@ripe.net> 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 didn't pass authorization checks This was fixed on 24th of April. Please note that PGP signed updates cannot be processed by . Until 14th of May, processes updates in RIPE-181 format and automatically translates them into RPSL, which voids PGP signatures. 2. Conversion problems of updates sent to 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 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 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, , and 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 From ripe-dbm at ripe.net Thu Apr 26 16:07:47 2001 From: ripe-dbm at ripe.net (ripe-dbm at ripe.net) Date: Thu, 26 Apr 2001 16:07:47 +0200 Subject: The status of the migration iissues In-Reply-To: <3AE82BB3.8BFCFF7F@ripe.net> References: <3AE82BB3.8BFCFF7F@ripe.net> Message-ID: 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 didn't pass authorization checks This was fixed on 24th of April. Please note that PGP signed updates cannot be processed by . Until 14th of May, processes updates in RIPE-181 format and automatically translates them into RPSL, which voids PGP signatures. 2. Conversion problems of updates sent to 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 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 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, , and 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