RIPE-181 to RPSL Migration; Phase 2.
Dear Colleagues, (Apologies for multiple messages). On and from Monday, 14th May, 2001, <auto-dbm@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@ripe.net>, where they will be automatically converted to RPSL format. <auto-rpsl@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@ripe.net> - updates in RPSL format only <auto-rpsl@ripe.net> - updates in RPSL format only <auto-181@ripe.net> - updates in RIPE-181 format, automatically converted to RPS L format TEST Database: ------------- <test-dbm@ripe.net> - updates in RPSL format only <test-rpsl@ripe.net> - updates in RPSL format only <test-181@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@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@ripe.net> and that updates in RPSL format should be sent to <auto-rpsl@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@ripe.net>. Regards, A. M. R. Magee -------------- Database Group RIPE NCC
I've gone through all the RPSL pages listed at: http://www.ripe.net/ripencc/pub-services/db/rpsl/index.html and am starting to wonder if its me that can't work with RPSL or everyone else. The documents on that page above have no consistency. Some are PDF, some are HTML. Response time for getting a response to a reported problem is about 5-7 days. There is no page of bugs found and what is still a bug and what has been fixed (ala Cisco Release Notes). For example, I lost 5 days when I couldn't create a nic-hdl. Turns out I was sending it in as "nic-hdl: auto-1" and there is a bug where lower case "auto-1" doesn't work and one has to use all uppercase. Now I have lost a day on fixing up an aut-num. I am trying to send in an update as follows:
export: to AS2686 announce AS3339 AS6810 AS6875 AS8958 AS9117 AS12736
***Error: valid lines start with attribute names, spaces or #
I have tried with the export tag on one line as well as split on two lines as follows: export: to AS2686 announce AS3339 AS6810 AS6875 AS8958 AS9117 AS12736 I just can't get auto-rpsl to accept the export tags. Sorry for the crossposting but I am wondering whether I am the only one who is hitting all these problems? Thanks, Hank
Dear Hank, all, On Wed, 23 May 2001, Hank Nussbacher wrote:
I've gone through all the RPSL pages listed at: http://www.ripe.net/ripencc/pub-services/db/rpsl/index.html and am starting to wonder if its me that can't work with RPSL or everyone else.
The documents on that page above have no consistency. Some are PDF, some are HTML.
Response time for getting a response to a reported problem is about 5-7 days.
The response time on <ripe-dbm@ripe.net> mailbox is indeed higher than usual, but we are trying to give more priority to solving problems related to new software and urgent problems.
There is no page of bugs found and what is still a bug and what has been fixed (ala Cisco Release Notes). For example, I lost 5 days when I couldn't create a nic-hdl. Turns out I was sending it in as "nic-hdl: auto-1" and there is a bug where lower case "auto-1" doesn't work and one has to use all uppercase.
Such a bugs page will be prepared shortly in our external web site. For the record: The auto NIC handle problem has been solved already. Auto NIC handles are now case-insensitive.
Now I have lost a day on fixing up an aut-num. I am trying to send in an update as follows:
export: to AS2686 announce AS3339 AS6810 AS6875 AS8958 AS9117 AS12736
***Error: valid lines start with attribute names, spaces or #
I have tried with the export tag on one line as well as split on two lines as follows: export: to AS2686 announce AS3339 AS6810 AS6875 AS8958 AS9117 AS12736
I've digged our logs, and the object you've sent was something like: [..] import: from AS16370 action pref=100; accept ANY export: to AS2686 announce AS3339 AS6810 AS6875 AS8958 AS9117 AS12736 AS12818 AS15708 AS15975 AS16158 AS16370 export: to AS5585 announce AS3339 AS6810 AS6875 AS8958 AS9117 AS12736 AS12818 AS15708 AS15975 AS16158 AS16370 [..] Here, we must leave a white space in the beginning of continuation lines, for example, instead of: export: to AS2686 announce AS3339 AS6810 AS6875 AS8958 AS9117 AS12736 AS12818 AS15708 AS15975 AS16158 AS16370 we must say: export: to AS2686 announce AS3339 AS6810 AS6875 AS8958 AS9117 AS12736 AS12818 AS15708 AS15975 AS16158 AS16370 or it is also possible to put '+' in the beginning of the continuation lines, like: export: to AS2686 announce AS3339 AS6810 AS6875 AS8958 AS9117 + AS12736 AS12818 AS15708 AS15975 AS16158 AS16370 I hope this helps. We are trying our best to fix the problems you encounter, and sorry for any inconvenience caused, Best regards, Engin Gunduz RIPE NCC Database Group
I just can't get auto-rpsl to accept the export tags.
Sorry for the crossposting but I am wondering whether I am the only one who is hitting all these problems?
Thanks, Hank
Dear Colleagues, On Wed, 23 May 2001, Engin Gunduz wrote: [...]
There is no page of bugs found and what is still a bug and what has been fixed (ala Cisco Release Notes). For example, I lost 5 days when I couldn't create a nic-hdl. Turns out I was sending it in as "nic-hdl: auto-1" and there is a bug where lower case "auto-1" doesn't work and one has to use all uppercase.
Such a bugs page will be prepared shortly in our external web site.
As a followup: We have prepared a list of known bugs for v3 software, which is at: http://www.ripe.net/ripencc/pub-services/db/issues.html Best regards, Engin Gunduz RIPE NCC Database Group [...]
On Wed, 30 May 2001, Engin Gunduz wrote: EG> As a followup: We have prepared a list of known bugs for v3 software, EG> which is at: EG> EG> http://www.ripe.net/ripencc/pub-services/db/issues.html Great, thank you. Small question: is there a plan to implement support for a.b.c.d/len inetnums? surely we can write small wrapper, but... Sincerely, D.Marck [DM5020, DM268-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------
Dear Dmitry, On Wed, 30 May 2001, Dmitry Morozovsky wrote:
On Wed, 30 May 2001, Engin Gunduz wrote:
EG> As a followup: We have prepared a list of known bugs for v3 software, EG> which is at: EG> EG> http://www.ripe.net/ripencc/pub-services/db/issues.html
Great, thank you.
Small question: is there a plan to implement support for a.b.c.d/len inetnums? surely we can write small wrapper, but...
This would require some biggish changes in the structure, so not possible to implement right away. However we'll put this in our wish list. Regards, Engin Gunduz RIPE NCC Database Group
Sincerely, D.Marck [DM5020, DM268-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------
participants (4)
-
db-news＠ripe.net -
Dmitry Morozovsky -
Engin Gunduz -
Hank Nussbacher